From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 16:45:31 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0C63106566B for ; Tue, 1 Dec 2009 16:45:31 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 5DAA78FC1C for ; Tue, 1 Dec 2009 16:45:30 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Tue, 1 Dec 2009 11:45:31 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B154905.8020400@greatbaysoftware.com> Date: Tue, 01 Dec 2009 11:49:09 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4B0ABD27.2080501@greatbaysoftware.com> In-Reply-To: <4B0ABD27.2080501@greatbaysoftware.com> X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: No "boot0" menu on Soekris, net5501 vs net4521 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 16:45:31 -0000 Charles Owens wrote: > Hello, > > We're working with two different Soekris models (net5501 and net4521), > working withFreeBSD 7.1 (nanobsd). We've found that the two models > exhibit different boot behavior. Summary: the 4521 works fine, and > the 5501 doesn't seem right. Here's what we see when we boot either: > > net4521 (BIOS ver 1.33) -- > > * "boot0" menu appears (letting you pick either of two FreeBSD slices) > * OS loads properly from chosen or default slice > > > net5501 (BIOS ver 1.33c) -- > > * "boot0" menu does _not_ appear. > * system boots directly to slice 1 or 2, as chosen via BIOS option > BootPartition > > > Have others seen this behavior? For our application, we really need > the 5501 to boot just like the 4521. Is this a bug (in BIOS, I'm > guessing), or am I doing something wrong? It seems like there should > be a way to clear the BootPartition setting, or set it to "MBR" or > somesuch. > Issue resolved. The syntax for resetting the BootPartition parameter in BIOS was non-obvious (to me). This can be accomplished with: set BootPartition=Disabled ... my thanks to maintainer of wiki: http://wiki.soekris.info/What_do_all_those_BIOS_settings_do%3F ... Charles Owens Great Bay Software