Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!stanford.edu!agate!ucbvax!dog.ee.lbl.gov!nosc!manta!samuels@nosc.mil
From: samuels@nosc.mil
Newsgroups: comp.os.mach
Subject: Mach 2.5 Installation problem
Message-ID: <2049@manta.NOSC.MIL>
Date: 17 Jun 91 17:03:40 GMT
Sender: nobody@manta.NOSC.MIL
Organization: Naval Ocean Systems Center
Lines: 39

I'm installing Mach 2.5 from tape to a Sun 3/160 with a Xylogics 451
controller and a Fujitsu M2333 disk, removing Mach 2.0 to do the
install.

After loading all tapes, when I try to boot Mach 2.5 for the first time,
I get the following:

>b xy(0,1,0)vmunix -as 
Boot: xy(0,1,0)boot				
Boot: xy(0,1,0)vmunix -as
/* booting messages... */
root device: xy1*		// I enter xy1*
use one of sd%d sd%d	// here's my problem - kernel only knows
						// about scsi disks, not xy controllers

Within the booting messages mentioned above, there is no 
line showing the xy controller, either.  I've got to conclude
the kernel I have was built without 'knowledge' of xy devices;
looking at the MASTER.sun conf file, there are only sd devices,
no xy devices.

NOTES: the Xylogics disk is disk 1 (there's also a disk 0) so the
(0,1,0) parameter is correct.  Also, if I use only the -s parameter
(not -as), I don't even get the query 'root device'; it just
trys to boot from the (non-existing) scsi disk.  I tried booting the
'mach' kernel as well; same resutl.  I add this only
to let you know what I've tried.

Is there some known fix for this, or am I
overlooking some obvious solution?  Do I need to consider a rebuild
of the kernel with a different conf file?

Many thanks for any help with this.

Larry Samuels
samuels@nosc.mil

Naval Ocean Systems Center
619-553-4134