From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 20 11:06:50 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 19F2F1065676 for ; Mon, 20 Apr 2009 11:06:50 +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 075F08FC16 for ; Mon, 20 Apr 2009 11:06:50 +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 n3KB6nsP032974 for ; Mon, 20 Apr 2009 11:06:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n3KB6nJF032970 for freebsd-embedded@FreeBSD.org; Mon, 20 Apr 2009 11:06:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Apr 2009 11:06:49 GMT Message-Id: <200904201106.n3KB6nJF032970@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, 20 Apr 2009 11:06:50 -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 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" From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 20 13:55:27 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 9BD4D10656CD for ; Mon, 20 Apr 2009 13:55:27 +0000 (UTC) (envelope-from matthias-bsde@mteege.de) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.freebsd.org (Postfix) with ESMTP id 5A1D28FC0C for ; Mon, 20 Apr 2009 13:55:27 +0000 (UTC) (envelope-from matthias-bsde@mteege.de) Received: from mail-in-09-z2.arcor-online.net (mail-in-09-z2.arcor-online.net [151.189.8.21]) by mx.arcor.de (Postfix) with ESMTP id EB8A1332700; Mon, 20 Apr 2009 15:55:25 +0200 (CEST) Received: from mail-in-10.arcor-online.net (mail-in-10.arcor-online.net [151.189.21.50]) by mail-in-09-z2.arcor-online.net (Postfix) with ESMTP id D7E6E28EE08; Mon, 20 Apr 2009 15:55:25 +0200 (CEST) Received: from crn.mteege.de (six.mteege.de [88.79.143.204]) by mail-in-10.arcor-online.net (Postfix) with ESMTP id 8D38228F063; Mon, 20 Apr 2009 15:55:24 +0200 (CEST) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-10.arcor-online.net 8D38228F063 Received: from cab.de ([192.168.153.14]) by crn; Mon Apr 20 13:55:24 GMT 2009 Message-ID: <4b925570b9c69698b6eb029454ed29fa@mteege.de> To: nick@van-laarhoven.org, freebsd-embedded@freebsd.org Date: Mon, 20 Apr 2009 15:55:23 +0200 From: Matthias Teege In-Reply-To: <200904201535.21191.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: Subject: Re: nanobsd boot slice selection does not work X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-embedded@freebsd.org 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:55:28 -0000 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 From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 20 14:44:42 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 1FB1D1065677 for ; Mon, 20 Apr 2009 14:44:42 +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 D59708FC1B for ; Mon, 20 Apr 2009 14:44:41 +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 21A9E3F45C; Mon, 20 Apr 2009 16:44:37 +0200 (CEST) From: Nick Hibma To: freebsd-embedded@freebsd.org Date: Mon, 20 Apr 2009 16:44:35 +0200 User-Agent: KMail/1.9.10 References: <4b925570b9c69698b6eb029454ed29fa@mteege.de> In-Reply-To: <4b925570b9c69698b6eb029454ed29fa@mteege.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904201644.35430.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 14:44:42 -0000 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 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 From owner-freebsd-embedded@FreeBSD.ORG Thu Apr 23 22:01: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 20E6A106564A for ; Thu, 23 Apr 2009 22:01:38 +0000 (UTC) (envelope-from rickvanderzwet@gmail.com) Received: from mail-fx0-f162.google.com (mail-fx0-f162.google.com [209.85.220.162]) by mx1.freebsd.org (Postfix) with ESMTP id 786458FC17 for ; Thu, 23 Apr 2009 22:01:37 +0000 (UTC) (envelope-from rickvanderzwet@gmail.com) Received: by fxm6 with SMTP id 6so448984fxm.43 for ; Thu, 23 Apr 2009 15:01:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=hHGOEoqNI3Spo0UCyiWHF7QZF594AGQOYLCfzxcIctw=; b=pHVQTGA36ixBXVzfO3P76tjbR9ZGI8nTFY3YiOvIXiJ21+zr840pxzh2nK7MkPucVn zSd9cajnMACYvXTOrRnkwfbYPh01RLNsvborOtnKFpPN5/5JBBaSITM3D0r4Fkv3lDPX 3cXU3HstLAs1CI9UJXf5jHkQptM6KQVJt5wB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=jBrpIdm1WhIixckB5U98FnaWuf17iobyMRc21Ole2ecH/smAY7pu9rHIyGzFC3eiov qTMYwaz4nTCe7kkwbofGx7EHRkNOBhm8NJ3jaDUaZHLqAr3UoNdDheh6iZVIJAWWZaPM 3Bc+REMjQNj239xVq2rfARV2bLSV+T6aB12LU= MIME-Version: 1.0 Sender: rickvanderzwet@gmail.com Received: by 10.223.108.74 with SMTP id e10mr482171fap.35.1240522720687; Thu, 23 Apr 2009 14:38:40 -0700 (PDT) Date: Thu, 23 Apr 2009 23:38:40 +0200 X-Google-Sender-Auth: c313f4fc20d1f675 Message-ID: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> From: Rick van der Zwet To: freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: nanobsd image boot issues 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: Thu, 23 Apr 2009 22:01:38 -0000 Boot delay and fail issues on various hardware using nanobsd generated RELENG_7_1 images on a sandisk 2gb CF (SDCFH2-002G). For example while trying to run a image on a soekris net4521 (bios 1.33) it seems to take ages (up to a minute) to start booting. Same image supplied to a PC (intel Pentium 1 & award bios) using a CF->IDE converter does not seems to boot at all, neither does a net4801 (bios 1.33). Just seems trying to find a boot loader. The net4801 even bails out after a while. Output of fdisk of image list as follows: Disk: /dev/disk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: A5 0 1 1 - 491 15 63 [ 63 - 495873] FreeBSD 2: A5 492 1 1 - 983 15 63 [ 495999 - 495873] FreeBSD 3: A5 984 0 1 - 992 15 63 [ 991872 - 9072] FreeBSD 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused A reference pfSense image put on the same CF card is boot perfectly fine under the net4521 & PC (untested net4801): Disk: /dev/rdisk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused *4: A5 0 0 1 - 1023 254 63 [ 0 - 50000] FreeBSD Which makes me wonder about the sector start, why does nanobsd not start at sector 0, but uses sector 63 as a start instead. Could that be the explanation or is something else going on? /Rick -- http://rickvanderzwet.nl From owner-freebsd-embedded@FreeBSD.ORG Thu Apr 23 22:26:28 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 C9C4E106564A for ; Thu, 23 Apr 2009 22:26:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 56D278FC12 for ; Thu, 23 Apr 2009 22:26:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n3NMNSjh045525; Thu, 23 Apr 2009 16:23:28 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 23 Apr 2009 16:24:27 -0600 (MDT) Message-Id: <20090423.162427.-1543901316.imp@bsdimp.com> To: info@rickvanderzwet.nl From: "M. Warner Losh" In-Reply-To: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> References: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@freebsd.org Subject: Re: nanobsd image boot issues 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: Thu, 23 Apr 2009 22:26:29 -0000 In message: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> Rick van der Zwet writes: : Boot delay and fail issues on various hardware using nanobsd generated : RELENG_7_1 images on a sandisk 2gb CF (SDCFH2-002G). For example while : trying to run a image on a soekris net4521 (bios 1.33) it seems to : take ages (up to a minute) to start booting. Same image supplied to a : PC (intel Pentium 1 & award bios) using a CF->IDE converter does not : seems to boot at all, neither does a net4801 (bios 1.33). Just seems : trying to find a boot loader. The net4801 even bails out after a : while. Output of fdisk of image list as follows: : : Disk: /dev/disk3 geometry: 992/64/63 [4001760 sectors] : Signature: 0xAA55 : Starting Ending : #: id cyl hd sec - cyl hd sec [ start - size] : ------------------------------------------------------------------------ : *1: A5 0 1 1 - 491 15 63 [ 63 - 495873] FreeBSD : 2: A5 492 1 1 - 983 15 63 [ 495999 - 495873] FreeBSD : 3: A5 984 0 1 - 992 15 63 [ 991872 - 9072] FreeBSD : 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : This looks right... : A reference pfSense image put on the same CF card is boot perfectly : fine under the net4521 & PC (untested net4801): : : Disk: /dev/rdisk3 geometry: 992/64/63 [4001760 sectors] : Signature: 0xAA55 : Starting Ending : #: id cyl hd sec - cyl hd sec [ start - size] : ------------------------------------------------------------------------ : 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused : *4: A5 0 0 1 - 1023 254 63 [ 0 - 50000] FreeBSD This looks like the 'faked' DD geometry. : Which makes me wonder about the sector start, why does nanobsd not : start at sector 0, but uses sector 63 as a start instead. Could that : be the explanation or is something else going on? Because the first cylinder is reserved for the boot blocks. Have you enabled packet mode for boot in boot0 with boot0cfg? Warner