From owner-freebsd-current  Sun Jan 17 08:31:26 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA02073
          for freebsd-current-outgoing; Sun, 17 Jan 1999 08:31:26 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-25-dbn.dial-up.net [196.34.155.89])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02063
          for <current@FreeBSD.ORG>; Sun, 17 Jan 1999 08:31:20 -0800 (PST)
          (envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA26217; Sun, 17 Jan 1999 18:29:33 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199901171629.SAA26217@ceia.nordier.com>
Subject: Re: possible problem with new boot loader ?
In-Reply-To: <19990117061641.D28911@TelcoSucks.org> from Ulf Zimmermann at "Jan 17, 99 06:16:42 am"
To: ulf@Alameda.net
Date: Sun, 17 Jan 1999 18:29:30 +0200 (SAT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ulf Zimmermann wrote:

> Not sure if I am just to stupid or if this is a bug. My system has
> 2 IDE drives and then several SCSI drives. FreeBSD is on the first
> scsi drive, so da0. Root is da0s1a. Bios sees the drive as the 3.
> 
> When the new boot loader comes up with no /boot.config, it prints
> 2:da(2,a)/boot/loader, which isn't right, as it should be 2:da(0,a).
> If I now press a key and enter 2:da(0,a), it complains it can't find
> /boot/loader. Entering 2:da(0,a)/kernel works fine and that is
> what i have now in my boot.conf.
> 
> Could this be a bug or not?

There are two issues here:

    o  The bootblocks get the SCSI unit number wrong in cases where
       IDE drives are also attached.

       This is to be expected.  There is just insufficient space
       available to the bootblocks for "smarter" logic.

       The old bootblocks have a build setting BOOT_HD_BIAS to work
       around this problem.  The new bootblocks rely on /boot.config.
       You can have

	   2:da(0,a)

       in /boot.config (ie. without a kernel name) to override just
       the unit number.

    o  The /boot/loader program just isn't being found.

       Are you sure this actually exists?  What shows up if you
       enter

	   2:da(0,a)/boot/?

       (to get a directory listing of /boot) at the "boot:" prompt?

Incidentally, do these bootblocks contain the BTX patch I sent you,
or did you find some other way around that problem?

-- 
Robert Nordier

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message