From owner-freebsd-current Sun Jan 17 14:24:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09596 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:24:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09546 for ; Sun, 17 Jan 1999 14:24:00 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id OAA03216; Sun, 17 Jan 1999 14:23:59 -0800 (PST) (envelope-from ulf) Message-ID: <19990117142359.J28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 14:23:59 -0800 From: Ulf Zimmermann To: Mike Smith , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Reply-To: ulf@Alameda.net References: <19990117134951.H28911@TelcoSucks.org> <199901172157.NAA09016@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901172157.NAA09016@dingo.cdrom.com>; from Mike Smith on Sun, Jan 17, 1999 at 01:57:20PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 01:57:20PM -0800, Mike Smith wrote: > > On Sun, Jan 17, 1999 at 01:36:12PM -0800, Mike Smith wrote: > > > > > 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) > > > > > > > > If I do that, it does find the loader, but the kernel panics, because > > > > it thinks root should be on da2s1a. > > > > > > You need 'set num_ide_disks=2' > > > > > > The variable's somewhat misnamed, and I'm still groping for an > > > algorithm that'll get it more or less right without screwing the pooch > > > should we ever improve the root mount detection in the kernel. > > > > Set that where? At the disk1s1a:> prompt ? Still can't find kernel. > > num_ide_disks will help the kernel work out where the root filesystem > is. If you can't find the kernel, try 'ls' to start with, and then > send the output 'lsdev' > > I'm also curious why you get a 'disk1s1a' prompt, when it should be > disk3 (presuming you have a floppy disk). Have you installed new > bootblocks on your boot disk? I have installed the new bootblocks with disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/da0s1. I use System Commander, that might have an influence too. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message