Date: Sun, 17 Jan 1999 14:52:14 -0800 From: Mike Smith <mike@smith.net.au> To: ulf@Alameda.net Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Message-ID: <199901172252.OAA09325@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 17 Jan 1999 14:23:59 PST." <19990117142359.J28911@TelcoSucks.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > 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. Which device is the bootstrap (not the bootloader) defaulting to? If it's 'wd(0,a)', then yes, it does seem that System Commander is at fault, since it should be passing in the BIOS unit number. If it's 'wd(2,a)', then it's doing the Right Thing. -- \\ 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901172252.OAA09325>