On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote: > 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)
If I do that, it does find the loader, but the kernel panics, because it thinks root should be on da2s1a. > > 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? This are the boot loaders from last night, just after make world got through. > > -- > Robert Nordier -- 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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
