From owner-freebsd-embedded@FreeBSD.ORG Mon May 11 11:06:52 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 9DFFD1065677 for ; Mon, 11 May 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8AF058FC16 for ; Mon, 11 May 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4BB6qwB085908 for ; Mon, 11 May 2009 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4BB6pmm085904 for freebsd-embedded@FreeBSD.org; Mon, 11 May 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 May 2009 11:06:51 GMT Message-Id: <200905111106.n4BB6pmm085904@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org 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, 11 May 2009 11:06:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/15876 embedded [picobsd] PicoBSD message of the day problems 4 problems total. From owner-freebsd-embedded@FreeBSD.ORG Mon May 11 16:49:37 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 0491D1065678 for ; Mon, 11 May 2009 16:49:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C9E7D8FC15 for ; Mon, 11 May 2009 16:49:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7D25F46B2C; Mon, 11 May 2009 12:49:36 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 3763F8A027; Mon, 11 May 2009 12:49:35 -0400 (EDT) From: John Baldwin To: freebsd-embedded@freebsd.org Date: Mon, 11 May 2009 09:40:31 -0400 User-Agent: KMail/1.9.7 References: <200904201535.21191.nick@van-laarhoven.org> <4b925570b9c69698b6eb029454ed29fa@mteege.de> <20090505144938.GA87033@psconsult.nl> In-Reply-To: <20090505144938.GA87033@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905110940.31187.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 11 May 2009 12:49:35 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=BAYES_00, DATE_IN_PAST_03_06, RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx 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, 11 May 2009 16:49:37 -0000 On Tuesday 05 May 2009 10:49:38 am Paul Schenkeveld wrote: > On Mon, Apr 20, 2009 at 03:55:23PM +0200, Matthias Teege wrote: > > 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. > > Ok, a bit late (interrupt storm generated by device $WORK) but I just > tested with a clean 7.2-RELEASE source tree. I too can report this > regression in boot0 which now looks at the active flag in a MBR table > entry instead of its own default partition byte when not choosing the > partition by pressing 1 or 2 at the prompt. This is a regression. > > The boot0 source code appears to have had a complete overhaul between > 7.1 and 7.2. > > As a workaround, use the 7.1 boot0 source (or even use 7.1 completely > if you care about the anticipated eol of the release). > > I hope Luigi will have some time to look at the default drive delection > algorithm again zome time soon. I think you can simply re-enable the 'update' flag using boot0cfg in 7.2 to fix this? -- John Baldwin From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 07:53:03 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 8A9BB106566C for ; Tue, 12 May 2009 07:53:03 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id 190CB8FC1D for ; Tue, 12 May 2009 07:53:01 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id n4C7qs6A088437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 12 May 2009 09:52:59 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id n4C7qsZh088436 for freebsd-embedded@freebsd.org; Tue, 12 May 2009 09:52:54 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Date: Tue, 12 May 2009 09:52:54 +0200 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org Message-ID: <20090512075254.GA88230@psconsult.nl> Mail-Followup-To: freebsd-embedded@freebsd.org References: <200904201535.21191.nick@van-laarhoven.org> <4b925570b9c69698b6eb029454ed29fa@mteege.de> <20090505144938.GA87033@psconsult.nl> <200905110940.31187.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905110940.31187.jhb@freebsd.org> User-Agent: Mutt/1.5.17 (2007-11-01) 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, 12 May 2009 07:53:04 -0000 On Mon, May 11, 2009 at 09:40:31AM -0400, John Baldwin wrote: > On Tuesday 05 May 2009 10:49:38 am Paul Schenkeveld wrote: > > On Mon, Apr 20, 2009 at 03:55:23PM +0200, Matthias Teege wrote: > > > 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. > > > > Ok, a bit late (interrupt storm generated by device $WORK) but I just > > tested with a clean 7.2-RELEASE source tree. I too can report this > > regression in boot0 which now looks at the active flag in a MBR table > > entry instead of its own default partition byte when not choosing the > > partition by pressing 1 or 2 at the prompt. This is a regression. > > > > The boot0 source code appears to have had a complete overhaul between > > 7.1 and 7.2. > > > > As a workaround, use the 7.1 boot0 source (or even use 7.1 completely > > if you care about the anticipated eol of the release). > > > > I hope Luigi will have some time to look at the default drive delection > > algorithm again zome time soon. > > I think you can simply re-enable the 'update' flag using boot0cfg in 7.2 to > fix this? The update flag is on, besides it controls whether the first sector is written back or not after selecting another slice than the default using the keyboard. The problem above shows that the 'default' slice variable in sector 0 is not read anymore but the MBR records are searched for an active flag. Using the (M$DOS-compatible) active flag only slices 1-4 can be set as default, the boot0 default variable also allows for selection 5 (next disk) and probably also 6 (pxe boot) to be saved as default. -- Paul Schenkeveld From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 08:35:01 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 A3202106564A for ; Tue, 12 May 2009 08:35:01 +0000 (UTC) (envelope-from info@martenvijn.nl) Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by mx1.freebsd.org (Postfix) with ESMTP id 3FEF98FC1D for ; Tue, 12 May 2009 08:35:01 +0000 (UTC) (envelope-from info@martenvijn.nl) Received: from [192.168.178.47] (martenvijn.xs4all.nl [80.101.161.153]) by smtp-vbr13.xs4all.nl (8.13.8/8.13.8) with ESMTP id n4C8JfX9093451 for ; Tue, 12 May 2009 10:19:42 +0200 (CEST) (envelope-from info@martenvijn.nl) From: Marten Vijn To: freebsd-embedded@freebsd.org In-Reply-To: <1236874484.16141.4.camel@mvn-desktop> References: <93A3902C-A459-48A9-A36C-7036E0ED5C0D@develooper.com> <1236874484.16141.4.camel@mvn-desktop> Content-Type: text/plain; charset="UTF-8" Date: Tue, 12 May 2009 10:19:41 +0200 Message-Id: <1242116381.6449.83.camel@mvn-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Minimal NanoBSD image / make.conf? 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, 12 May 2009 08:35:02 -0000 On Thu, 2009-03-12 at 17:14 +0100, Marten Vijn wrote: > On Thu, 2009-03-12 at 08:28 -0700, Ask Bjørn Hansen wrote: > > Hi everyone, > > > > I used to build my NanoBSD images off 6.x. My original NanoBSD > > make.conf was based on one phk had for his ntpns clock (I think it was). > > > > I'm upgrading to 7.1 now and was wondering if anyone would like to > > share their make.conf for making a ~minimal install? > (I deploy on > > Soekris and PC Engines boards). > > Hi i asked this a while ago, > But no clear anwsers came, > > I willing to put some effort in this and document it in public place. > > This what use now: > http://bsd.wifisoft.org/svn/projects/nek/node/nanobsd/ > http://bsd.wifisoft.org/svn/projects/nek/node/nanobsd-8.0/node_ap_64M/ change NANO_TOOLS to your working dir. it had a 40Mb base and some packages. if some has a "cust_crunchgen" example for bin sbin usrbin and usr/sbin example, I would like to add it Marten > > > > > for this project: > > http://bsd.wifisoft.org/nek/ > > > > kind regards, > Marten > > -- http://martenvijn.nl Marten Vijn http://martenvijn.nl/trac/wiki/soas Sugar on a Stick http://bsd.wifisoft.org/nek/ The Network Event Kit http://har2009.org 13th-16th August http://opencommunitycamp.org 26th Jul - 2nd August From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 15:48:11 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 3B0DD1065673 for ; Tue, 12 May 2009 15:48:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0E2D38FC0A for ; Tue, 12 May 2009 15:48:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A245946B23; Tue, 12 May 2009 11:48:10 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 3F69C8A025; Tue, 12 May 2009 11:48:09 -0400 (EDT) From: John Baldwin To: freebsd-embedded@freebsd.org Date: Tue, 12 May 2009 10:08:18 -0400 User-Agent: KMail/1.9.7 References: <200904201535.21191.nick@van-laarhoven.org> <200905110940.31187.jhb@freebsd.org> <20090512075254.GA88230@psconsult.nl> In-Reply-To: <20090512075254.GA88230@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905121008.19196.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 12 May 2009 11:48:09 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx 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, 12 May 2009 15:48:11 -0000 On Tuesday 12 May 2009 3:52:54 am Paul Schenkeveld wrote: > On Mon, May 11, 2009 at 09:40:31AM -0400, John Baldwin wrote: > > On Tuesday 05 May 2009 10:49:38 am Paul Schenkeveld wrote: > > > On Mon, Apr 20, 2009 at 03:55:23PM +0200, Matthias Teege wrote: > > > > 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. > > > > > > Ok, a bit late (interrupt storm generated by device $WORK) but I just > > > tested with a clean 7.2-RELEASE source tree. I too can report this > > > regression in boot0 which now looks at the active flag in a MBR table > > > entry instead of its own default partition byte when not choosing the > > > partition by pressing 1 or 2 at the prompt. This is a regression. > > > > > > The boot0 source code appears to have had a complete overhaul between > > > 7.1 and 7.2. > > > > > > As a workaround, use the 7.1 boot0 source (or even use 7.1 completely > > > if you care about the anticipated eol of the release). > > > > > > I hope Luigi will have some time to look at the default drive delection > > > algorithm again zome time soon. > > > > I think you can simply re-enable the 'update' flag using boot0cfg in 7.2 to > > fix this? > > The update flag is on, besides it controls whether the first sector is > written back or not after selecting another slice than the default using > the keyboard. The problem above shows that the 'default' slice variable > in sector 0 is not read anymore but the MBR records are searched for > an active flag. Using the (M$DOS-compatible) active flag only slices > 1-4 can be set as default, the boot0 default variable also allows for > selection 5 (next disk) and probably also 6 (pxe boot) to be saved as > default. Err, so one of the things you need to keep in mind, is that boot1 re-reads the MBR and uses the "active" flag to determine where to load boot2 from (and where boot2 loads /boot/loader from and /boot/loader loads the kernel and /etc/fstab from). boot1 prefers an active slice to a non-active slice, so if boot0 doesn't write back an updated MBR with the active slice changed, then even if you load the boot1 from slice 2, it will still boot slice 1 if the active flag is set on slice 1. Note that this is not in boot0, but in boot1. However, having 'update' enabled should fix this. -- John Baldwin From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 17:16:03 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 0B17D1065676 for ; Tue, 12 May 2009 17:16:03 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id 828BF8FC18 for ; Tue, 12 May 2009 17:16:02 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id n4CHFuDU005377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 12 May 2009 19:16:01 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id n4CHFu4g005376 for freebsd-embedded@freebsd.org; Tue, 12 May 2009 19:15:56 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Date: Tue, 12 May 2009 19:15:55 +0200 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org Message-ID: <20090512171555.GA4985@psconsult.nl> Mail-Followup-To: freebsd-embedded@freebsd.org References: <200904201535.21191.nick@van-laarhoven.org> <200905110940.31187.jhb@freebsd.org> <20090512075254.GA88230@psconsult.nl> <200905121008.19196.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905121008.19196.jhb@freebsd.org> User-Agent: Mutt/1.5.17 (2007-11-01) 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, 12 May 2009 17:16:03 -0000 On Tue, May 12, 2009 at 10:08:18AM -0400, John Baldwin wrote: > On Tuesday 12 May 2009 3:52:54 am Paul Schenkeveld wrote: > > On Mon, May 11, 2009 at 09:40:31AM -0400, John Baldwin wrote: > > > On Tuesday 05 May 2009 10:49:38 am Paul Schenkeveld wrote: > > > > On Mon, Apr 20, 2009 at 03:55:23PM +0200, Matthias Teege wrote: > > > > > 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. > > > > > > > > Ok, a bit late (interrupt storm generated by device $WORK) but I just > > > > tested with a clean 7.2-RELEASE source tree. I too can report this > > > > regression in boot0 which now looks at the active flag in a MBR table > > > > entry instead of its own default partition byte when not choosing the > > > > partition by pressing 1 or 2 at the prompt. This is a regression. > > > > > > > > The boot0 source code appears to have had a complete overhaul between > > > > 7.1 and 7.2. > > > > > > > > As a workaround, use the 7.1 boot0 source (or even use 7.1 completely > > > > if you care about the anticipated eol of the release). > > > > > > > > I hope Luigi will have some time to look at the default drive delection > > > > algorithm again zome time soon. > > > > > > I think you can simply re-enable the 'update' flag using boot0cfg in 7.2 > to > > > fix this? > > > > The update flag is on, besides it controls whether the first sector is > > written back or not after selecting another slice than the default using > > the keyboard. The problem above shows that the 'default' slice variable > > in sector 0 is not read anymore but the MBR records are searched for > > an active flag. Using the (M$DOS-compatible) active flag only slices > > 1-4 can be set as default, the boot0 default variable also allows for > > selection 5 (next disk) and probably also 6 (pxe boot) to be saved as > > default. > > Err, so one of the things you need to keep in mind, is that boot1 re-reads the > MBR and uses the "active" flag to determine where to load boot2 from (and > where boot2 loads /boot/loader from and /boot/loader loads the kernel > and /etc/fstab from). boot1 prefers an active slice to a non-active slice, > so if boot0 doesn't write back an updated MBR with the active slice changed, > then even if you load the boot1 from slice 2, it will still boot slice 1 if > the active flag is set on slice 1. Note that this is not in boot0, but in > boot1. However, having 'update' enabled should fix this. But on a FB7.1 (and 7.0, 6.[43210] and some 5.x and 4.x releases too) it used to work like this (just tried on a live 7.1p5 system): # boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 333: 14:48 48 240432 2 0x00 334: 1: 1 0xa5 667: 14:48 240528 240432 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 version=1.0 drive=0x80 mask=0x3 ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) # boot0cfg -v -s 2 ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 333: 14:48 48 240432 2 0x00 334: 1: 1 0xa5 667: 14:48 240528 240432 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 version=1.0 drive=0x80 mask=0x3 ticks=182 options=packet,update,nosetdrv default_selection=F2 (Slice 2) # reboot Note that default_selection has changed, but slice 1 is still marked active in the MBR. After rebooting, the kernel in /dev/ad0s2a is loaded (verified by uname -a, both slices have a kernel with a different timestamp) and: # boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 2 0x80 334: 1: 1 0xa5 667: 14:48 240528 240432 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 version=1.0 drive=0x80 mask=0x3 ticks=182 options=packet,update,nosetdrv default_selection=F2 (Slice 2) # The active marker has moved from slice 1 to slice 2, most likely this was done by boot0 but I cannot verify this easily. Trying the same on FB7.2 will show that default_selection has changed and slice 1 still marked active in the MBR after 'boot0cfg -v -s 2 ad0' just like on FB7.1 but during the reboot the kernel from slice 1 gets loaded and ad0s1a becomes the root partition. I just cannot but conclude that this is a regression from 7.1 and before. Unfortunately my x86 assembly knowledge is not enough to completely understaand boot0.S (I tried to compare the 7.1 and 7.2 source but had to give up) but boot0.S appears to have changed quite a lot in 7.2 so I'll keep pointing my finger at the boot0.S changes until proven wrong. > -- > John Baldwin Paul Schenkeveld From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 19:21:10 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 63F021065676 for ; Tue, 12 May 2009 19:21:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 361DA8FC1F for ; Tue, 12 May 2009 19:21:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E22B046B8E; Tue, 12 May 2009 15:21:09 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id CB2FE8A025; Tue, 12 May 2009 15:21:08 -0400 (EDT) From: John Baldwin To: freebsd-embedded@freebsd.org Date: Tue, 12 May 2009 14:45:26 -0400 User-Agent: KMail/1.9.7 References: <200904201535.21191.nick@van-laarhoven.org> <200905121008.19196.jhb@freebsd.org> <20090512171555.GA4985@psconsult.nl> In-Reply-To: <20090512171555.GA4985@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905121445.27090.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 12 May 2009 15:21:08 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx 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, 12 May 2009 19:21:10 -0000 On Tuesday 12 May 2009 1:15:55 pm Paul Schenkeveld wrote: > After rebooting, the kernel in /dev/ad0s2a is loaded (verified by > uname -a, both slices have a kernel with a different timestamp) and: > > # boot0cfg -v ad0 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 > 2 0x80 334: 1: 1 0xa5 667: 14:48 240528 240432 > 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 > 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 > > version=1.0 drive=0x80 mask=0x3 ticks=182 > options=packet,update,nosetdrv > default_selection=F2 (Slice 2) > # > > The active marker has moved from slice 1 to slice 2, most likely this > was done by boot0 but I cannot verify this easily. Yes, it is done by boot0. > Trying the same on FB7.2 will show that default_selection has changed > and slice 1 still marked active in the MBR after 'boot0cfg -v -s 2 ad0' > just like on FB7.1 but during the reboot the kernel from slice 1 gets > loaded and ad0s1a becomes the root partition. Ok, so can you verify if 'update' is enabled for boot0 in the 7.2 case? -- John Baldwin From owner-freebsd-embedded@FreeBSD.ORG Tue May 12 22:13:49 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 D8D03106566C for ; Tue, 12 May 2009 22:13:49 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1958FC14 for ; Tue, 12 May 2009 22:13:49 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id n4CMDgNS014897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 May 2009 00:13:48 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id n4CMDgEd014896 for freebsd-embedded@freebsd.org; Wed, 13 May 2009 00:13:42 +0200 (CEST) (envelope-from fb-embedded@psconsult.nl) Date: Wed, 13 May 2009 00:13:42 +0200 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org Message-ID: <20090512221342.GA9393@psconsult.nl> Mail-Followup-To: freebsd-embedded@freebsd.org References: <200904201535.21191.nick@van-laarhoven.org> <200905121008.19196.jhb@freebsd.org> <20090512171555.GA4985@psconsult.nl> <200905121445.27090.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905121445.27090.jhb@freebsd.org> User-Agent: Mutt/1.5.17 (2007-11-01) 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, 12 May 2009 22:13:50 -0000 On Tue, May 12, 2009 at 02:45:26PM -0400, John Baldwin wrote: > On Tuesday 12 May 2009 1:15:55 pm Paul Schenkeveld wrote: > > After rebooting, the kernel in /dev/ad0s2a is loaded (verified by > > uname -a, both slices have a kernel with a different timestamp) and: > > > > # boot0cfg -v ad0 > > # flag start chs type end chs offset size > > 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 > > 2 0x80 334: 1: 1 0xa5 667: 14:48 240528 240432 > > 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 > > 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 > > > > version=1.0 drive=0x80 mask=0x3 ticks=182 > > options=packet,update,nosetdrv > > default_selection=F2 (Slice 2) > > # > > > > The active marker has moved from slice 1 to slice 2, most likely this > > was done by boot0 but I cannot verify this easily. > > Yes, it is done by boot0. > > > Trying the same on FB7.2 will show that default_selection has changed > > and slice 1 still marked active in the MBR after 'boot0cfg -v -s 2 ad0' > > just like on FB7.1 but during the reboot the kernel from slice 1 gets > > loaded and ad0s1a becomes the root partition. > > Ok, so can you verify if 'update' is enabled for boot0 in the 7.2 case? Yes (although I'm sure this only influences boot selection thru keyboard input when booting, not switching thru boot0cfg). Another strange observation, after a fresh nanobsd build using 7.2R, this is the output of boot0cfg: # boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 2 0x00 334: 1: 1 0xa5 667: 14:48 240528 240432 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) options=packet,update,nosetdrv default_selection=F1 (Slice 1) Note that none of the slices is marked active. Switching using boot0cfg yields: # boot0cfg -v -s 2 ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 2 0x00 334: 1: 1 0xa5 667: 14:48 240528 240432 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 version=1.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23) options=packet,update,nosetdrv default_selection=F2 (Slice 2) # During reboot, boot0 suggests that slice 2 is default: 1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. 1 FreeBSD 2 FreeBSD 5 Drive 1 Boot: 2 It looks like the kernel on ad0s1a gets loaded however. To be sure I upgraded the kernel on ad0s2a with a newer one, still the same behaviour. To summarize 7.2 boot0 behaviour: - Pressing [F]1 or [F]2 at the boot0 prompt selects slice 1 or 2 and boots off that slice. If the update option is on, default_selection is set in sector0, the active flage is set on the requested slice and cleared from the other slice. - Boot0cfg -s N sets default_selection to N and does not affect the active flag in MBR record. - Boot0 does not look at default_selection at all, the slice marked active is booted, if no slice is marked active, slice 1 is booted. Pressing a key during boot0 is kind of hard if the box is thousends of kilometers away, boot0 not looking at default_selection seems wrong because it exists to allow more control than just the active flags can achive (like defaulting to boor from the second disk. -- Paul Schenkeveld From owner-freebsd-embedded@FreeBSD.ORG Wed May 13 14:27:31 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 2BE97106566B for ; Wed, 13 May 2009 14:27:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id F13768FC08 for ; Wed, 13 May 2009 14:27:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A5FEC46B0C; Wed, 13 May 2009 10:27:30 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 7B8C98A028; Wed, 13 May 2009 10:27:29 -0400 (EDT) From: John Baldwin To: freebsd-embedded@freebsd.org Date: Wed, 13 May 2009 10:03:16 -0400 User-Agent: KMail/1.9.7 References: <200904201535.21191.nick@van-laarhoven.org> <200905121445.27090.jhb@freebsd.org> <20090512221342.GA9393@psconsult.nl> In-Reply-To: <20090512221342.GA9393@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905131003.16938.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 13 May 2009 10:27:29 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx 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: Wed, 13 May 2009 14:27:31 -0000 On Tuesday 12 May 2009 6:13:42 pm Paul Schenkeveld wrote: > During reboot, boot0 suggests that slice 2 is default: > > 1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. > > 1 FreeBSD > 2 FreeBSD > 5 Drive 1 > > Boot: 2 > > It looks like the kernel on ad0s1a gets loaded however. To be sure I > upgraded the kernel on ad0s2a with a newer one, still the same behaviour. Can you do boot0cfg -v after you have rebooted in this case? I want to see if the active flag is set to slice 2. > To summarize 7.2 boot0 behaviour: > > - Pressing [F]1 or [F]2 at the boot0 prompt selects slice 1 or 2 and > boots off that slice. If the update option is on, default_selection > is set in sector0, the active flage is set on the requested slice > and cleared from the other slice. Ok, so pressing the key always works? > - Boot0cfg -s N sets default_selection to N and does not affect the > active flag in MBR record. Right, the way this works at least in <= 7.1 is that boot0 changes the active flag based on 'default_selection' and then writes the new MBR back out to disk. > - Boot0 does not look at default_selection at all, the slice marked > active is booted, if no slice is marked active, slice 1 is booted. Well, boot1 does not look at default_selection at all. I think boot0 is still honoring it, but what happens is that boot0 loads boot1 from slice 2, but that boot1 doesn't find the active flag set, so it uses the first FreeBSD slice (slice 1) to load boot2, the loader, and the kernel. -- John Baldwin