From owner-freebsd-questions  Thu Dec  5 11:31:21 1996
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id LAA26926
          for questions-outgoing; Thu, 5 Dec 1996 11:31:21 -0800 (PST)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA26918
          for <questions@freebsd.org>; Thu, 5 Dec 1996 11:31:16 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.3/8.6.12) with SMTP id LAA08382; Thu, 5 Dec 1996 11:31:07 -0800 (PST)
Date: Thu, 5 Dec 1996 11:31:07 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Dan Yergeau <yergeau@gloworm.Stanford.EDU>
cc: questions@freebsd.org
Subject: Re: hardwiring second-level boot to load 1:sd(0,a)/kernel by default
In-Reply-To: <199612051743.JAA17473@antonios.Stanford.EDU>
Message-ID: <Pine.BSI.3.94.961205112951.8339F-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 5 Dec 1996, Dan Yergeau wrote:

> Is there any way to hardwire the second-level boot loader to default
> loading the kernel from a specific device?

Not really, at least now.

The situation you're detailing is fairly common.  The best way to fix it
is to teach your kernel it's proper place.  Modify the kernel line in your
kernel config to point to sd0, rebuild, and reinstall.  That should
hopefully fix it up.  

Having both IDE and SCSI does confuse the boot loader, but there's not
much we can do about it at present.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major