Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Feb 1997 11:35:08 -0800 (PST)
From:      Doug White <dwhite@gdi.uoregon.edu>
To:        Marty Leisner <leisner@sdsp.mc.xerox.com>
Cc:        questions@freebsd.org
Subject:   Re: installing snapshot 10/14 
Message-ID:  <Pine.BSI.3.94.970206113201.829S-100000@localhost>
In-Reply-To: <9702052249.AA01411@gnu.sdsp.mc.xerox.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Feb 1997, Marty Leisner wrote:

> >   Rebuild your kernel and change the 'kernel' line to point to the proper
> >   device.
> >   
> >   You should be able to boot with the boot floppy by typing wd(2,a)/kernel
> >   at any boot: prompt.
> 
> Well, I tried this...
> 	1) booting from the boot disk with wd(2,a)/kernel gets into
> 	an infinite loop error (can't find device)
> 	Errox: ...0x82
> 	2) I built my 8/14 kernel with:
> config          kernel  root on wd2
> 
> Then I put it on a dos disk and did:
> 	fbsdboot -r -D .\kernel
> and the kernel booted, and then paniced "can't mount root"

can you boot with with booteasy, the boot manager?  fbsdboot is trying to
pass wd0 as the root disk which will confuse the kernel even more.

> Is there a way to configure a kernel so it doesn't automatically
> reboot after this panic (I don't have the time to copy the
> stuff it printed out).

You should be able to abort it by pressing a key, although I know exactly
what the problem is.

> I'm confused at wd1 and wd2...when booting up, the kernel messages
> says:
> 	wd0 (one type of disk)
> 	wd2 (another type of disk)
> 
> but at the kernel boot line I have to do:
> 	wd(1,a)/kernel

Can you move your hard disks onto the same controller?  that would make
things infinitely easier.

> I may stick the release on disk1...its a relatively clean system running
> a combination of OS2s/win95/linux with space and partitions...but shouldn't
> I be able to boot cleanly off another ide disk?

Yes, but the boot code gets confused in your instance.  We've had this
problem for a while and I'm not sure what causes it.  

Someone suggested changing the entry for wd2 to wd1 in the kernel config.
You might try that.

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.970206113201.829S-100000>