Date: Mon, 20 Apr 2009 16:44:35 +0200 From: Nick Hibma <nick@van-laarhoven.org> To: freebsd-embedded@freebsd.org Subject: Re: nanobsd boot slice selection does not work Message-ID: <200904201644.35430.nick@van-laarhoven.org> In-Reply-To: <4b925570b9c69698b6eb029454ed29fa@mteege.de> References: <4b925570b9c69698b6eb029454ed29fa@mteege.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904201644.35430.nick>