-On [20040907 23:52], Matthew Dillon (dillon@apollo.backplane.com) wrote:
> I can't make heads or tails of it. All I can think of is that maybe
> you are running a mix of different types of boot code?
I now know for 100% certainty I haven't gotten a mix.
Each and every time I made sure bootblocks were installed.
I also used fdisk with p 2 0 0 0 to remove the partition before I recreated
it with fdisk and p 2 165 255996720 142294320.
> If you are trying to boot a dragonfly slice, you must have dragonfly
> boot1/boot2 blocks installed on that slice. That is, you have to proper
> disklabel the slice, for example:
>
> disklabel -B ad0s2
Even used disklabel -Bi ad0 and supplied the information from my disk (which
is set to auto in BIOS, which is CHS - 65525/16/255, LBA being
16643/255/63).
> In the past we have found that 'garbage' in the slice can screw up
> booting, so to be totally safe I'd blow it away completely and reinstall.
>
> dd if=/dev/zero of=/dev/ad0s2 bs=32k count=16
> disklabel -r -w ad0s2 auto
> disklabel -B ad0s2
> ... reinstall dragonfly from scratch on that slice ...
Same issues.
DF just refuses to boot.
It gets as far as printing - and then scrolls a BTX error/dump and resets
just as fast, only because I see the remnant glow on the monitor I know it
said BTX halted.
--
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://www.tibet.nu/
http://www.tendra.org/ | http://www.in-nomine.org/
To the dull mind nature is leaden. To the illumined mind the whole world
burns and sparkles with light...