From owner-freebsd-embedded@FreeBSD.ORG Tue Apr 21 20:39:38 2009 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29FF41065675 for ; Tue, 21 Apr 2009 20:39:38 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from baranao.anywi.com (baranao.anywi.com [213.207.101.176]) by mx1.freebsd.org (Postfix) with ESMTP id DD8318FC08 for ; Tue, 21 Apr 2009 20:39:37 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from hind.van-laarhoven.org (ip51cfcfde.direct-adsl.nl [81.207.207.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by baranao.anywi.com (Postfix) with ESMTPSA id EAF753F45C; Tue, 21 Apr 2009 22:39:33 +0200 (CEST) From: Nick Hibma To: freebsd-embedded@freebsd.org Date: Tue, 21 Apr 2009 22:39:27 +0200 User-Agent: KMail/1.9.10 References: <4b925570b9c69698b6eb029454ed29fa@mteege.de> <200904201644.35430.nick@van-laarhoven.org> In-Reply-To: <200904201644.35430.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904212239.28189.nick@van-laarhoven.org> X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,J_CHICKENPOX_43, UNPARSEABLE_RELAY autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on baranao.anywi.com Cc: Subject: Re: nanobsd boot slice selection does not work X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2009 20:39:38 -0000 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