Date: Fri, 30 May 1997 10:44:34 +0000 From: "Riley J. McIntire" <chaos@mail.tgci.com> To: Nadav Eiron <nadav@barcode.co.il> Cc: questions@FreeBSD.ORG Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't bo Message-ID: <199705301817.LAA20907@train.tgci.com>
next in thread | raw e-mail | index | archive | help
> Date: Thu, 29 May 1997 09:04:09 +0300 > From: Nadav Eiron <nadav@barcode.co.il> > To: chaos@tgci.com > Cc: questions@FreeBSD.ORG > Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't bo > Riley J. McIntire wrote: > > > [snip] > > > > > > Try giving: > > > 1:sd(0,a)/kernel > > > > > That worked! I did try it in a previous incarnation, but the config > > was differnent. > > > > Now, why doesn't the boot loader work? Not a big deal, but a theory > > would be nice. > > Here it goes (I may be mistaken, as I'm not the one who've written the > code, but still...): > The 1: at front hints to the boot code that the disk you're about to > boot is known by the BIOS as the second disk (BIOS code 0x81). > Otherwise, FreeBSD cannot guess what drive to ask the BIOS to boot from, > and its best shot is to use the number you have on the device name, so > when you give it sd0 it assumes it's your first disk (#0), but in your > case, that's wd0. This is simply because the boot code has no sure way > of knowing the mapping between FreeBSD device names and BIOS disk > numbers. > This might explain this new behavior: I reinstalled using the upgrade option. Again, the IDE bus was disabled in cmos while installing. After the upgrade I reenabled the ide bus. Now the boot prompt F1/F2/F5 (dos/fbsd/2nddisk) works--I press F5, get the second disk, choose F2 (sd(0,a)--2.2.2-R), it goes through the paces, and then get a "Panic--cannot mount root on sd(0,a)" (may not be the exact message...) Anyway, if I specify 1:sd(0,a)/kernel, it boots. Strange. Cheers, Riley
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705301817.LAA20907>