From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 20 13:51:43 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 A6F421065673 for ; Mon, 20 Apr 2009 13:51:43 +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 67EB68FC1D for ; Mon, 20 Apr 2009 13:51:43 +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 37F3D3F41B; Mon, 20 Apr 2009 15:35:29 +0200 (CEST) From: Nick Hibma To: freebsd-embedded@freebsd.org Date: Mon, 20 Apr 2009 15:35:20 +0200 User-Agent: KMail/1.9.10 References: <0c9e7e64a8be8ddaf12a27ab43dbbf8c@mteege.de> In-Reply-To: <0c9e7e64a8be8ddaf12a27ab43dbbf8c@mteege.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904201535.21191.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: Mon, 20 Apr 2009 13:51:43 -0000 I've seen this problem as well, but can't for the life of me remember what I did about it. Searching in our build environment does not yield an answer. Does changing boot image options change something? Or change to boot0sio. perhaps the fact that there is no keyboard confuses things. Good luck. Nick > Moin, > > > Did you see correct output from dd and fsck at the end of the updatepX > > run? > > Yes, no error message. > > > What does 'boot0cfg -v ad0' tell you (change ad0 to you flash device if > > different)? > > # boot0cfg -v ad1 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 > 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 > 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 > > version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) > options=packet,update,nosetdrv > default_selection=F2 (Slice 2) > > reboot with slice 2, works > > # boot0cfg -s 1 -v ad1 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 494: 15:32 32 253408 > 2 0x80 495: 1: 1 0xa5 989: 15:32 253472 253408 > 3 0x00 990: 0: 1 0xa5 993: 15:32 506880 2048 > > version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) > options=packet,update,nosetdrv > default_selection=F1 (Slice 1) > > reboot with slice 2 to, but shows "Boot: 1" in Bootmanager. > > If I select "1" with keyboard/console it boots from slice 1. If I select > "2" with the keyboard it boots from slice 2. It autoboots the slice which > was last selected by keyboard. It doesn't matter which slice I select > with boot0cfg. > > Many thanks > Matthias > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to > "freebsd-embedded-unsubscribe@freebsd.org"