nanobsd boot slice selection does not work

[Nick Hibma]

Well,

This is really surprising. It just happened to me today. I found the 
following workaround if boot0cfg -s 2 ad0 does not boot the second slice. 
Use

	echo 'a 2' | fdisk -f /dev/stdin ad0
	boot0cfg -s 2 ad0

instead.

Cheers,

Nick

> Moguh,
>
> The only reference to booting problems I can find is the following svn
> log message:
>
> 	"Note: Do NOT use the 'noupdate' option to boot0cfg as this disables the
> 	selection of the boot partition through 'boot0cfg -s ...' due to a bug
> 	in boot0.S ."
>
> The diff suggests that I needed to revert a previous commit because it
> didn't work as advertised.
>
> Perhaps the problem was related to the BIOS version? I've used 1.28 -
> 1.33 succesfully now.
>
> Cheers,
>
> Nick
>
> > Moin,
> >
> > > I've seen this problem as well, but can't for the life of me remember
> > > what I
> >
> > I'm relieved to hear that.
> >
> > > did about it. Searching in our build environment does not yield an
> > > answer.
> >
> > I use fdisk to set the active slice as workaround.
> >
> > > Does changing boot image options change something?
> >
> > I don't think so. I've changed update/noupdate, packet/nopacket,
> > setdrv/nosetdrv without any success.
> >
> > > Or change to boot0sio. perhaps the fact that there is no keyboard
> > > confuses things.
> >
> > I use boot0sio all the time. I is the default in nanobsd.
> >
> > # grep boot0sio /usr/src/tools/tools/nanobsd/nanobsd.sh
> > NANO_BOOTLOADER="boot/boot0sio"
> >
> > I can reproduce the problem under KVM Emulation so I think it isn't
> > a soekris or CF problem. The problem is, that boot0cfg doesn't change
> > the flag for the active slice. In my example slice 2 is always flagged
> > as active.
> >
> > Many thanks
> > Matthias