Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Nov 2000 10:49:42 -0600
From:      "McKinley, Rob" <RMcKinley@mercantec.com>
To:        "'mjacob@feral.com'" <mjacob@feral.com>
Cc:        "'freebsd-alpha@freebsd.org'" <freebsd-alpha@FreeBSD.ORG>
Subject:   RE: AS200, PC164 Success.
Message-ID:  <C0276A99F75AD41188950008C7B989FF088B4B@nt01.merc.local>

next in thread | raw e-mail | index | archive | help
Arrggh.  After seeing someone else have no problem with RC1 and an AS200, I
scoured the machine and physically removed the CDROM from the case to
checked the jumpers again.  Indeed, the terminator was on (and the CDROM is
in the middle of the chain), so all of my problems were because of a screwed
up SCSI bus.  Did a re-install booting off the CDROM and all went well,
banged on it a while and seems to be stable.  Sorry for the false alarm.

Rob (hanging head in shame)

> -----Original Message-----
> From: McKinley, Rob [mailto:RMcKinley@mercantec.com]
> Sent: Thursday, November 16, 2000 12:13 PM
> To: 'mjacob@feral.com'; McKinley, Rob
> Cc: 'freebsd-alpha@freebsd.org'
> Subject: RE: AS200, PC164 Success.
> 
> 
> Yeah, without a serial connection I couldn't get the boot 
> messages to show
> when it's broken (unless anyone knows of a way to get dmesg 
> output from the
> emergency shell available from sysinstall).  I didn't have 
> time to get it
> last night either, so I'll try again tonight.
> 
> Rob
> 
> > -----Original Message-----
> > From: Matthew Jacob [mailto:mjacob@feral.com]
> > Sent: Thursday, November 16, 2000 11:20 AM
> > To: McKinley, Rob
> > Cc: 'freebsd-alpha@freebsd.org'
> > Subject: RE: AS200, PC164 Success.
> > 
> > 
> > 
> > 
> > > 
> > > Dmesg output below is from the resulting installed system.  
> > I need to pick
> > > up a working serial cable this evening to boot it from a 
> > console to get the
> > > boot messages when booting off the CDROM/floppies.   The 
> > CDROM is a Plextor
> > > 12x SCSI. I double checked termination on the scsi chain 
> > and all seems well
> > > there.  I did note that after a buildworld, when I shut it 
> > down a show dev
> > > at the SRM prompt only showed the hard drive, no CDROM, 
> > even though I had
> > > the CDROM mounted during the buildworld.  My guess at this 
> > point is that
> > > during the beginning of sysinstall (and possibly during 
> > normal running), the
> > > CDROM device is getting dropped as a valid device (similar 
> > to the thread
> > > about the AS1200 getting read errors on the hard drive 
> > early on in boot
> > > sequence?).
> > > The SRM is the updated version from the Tru64 5.0 kit, so I 
> > could try moving
> > > it back a rev or two.
> > 
> > The dmesg you sent shows no errors. I'm still trying to 
> > figure out where
> > precisely the CDROM seems to go away. Sigh.
> > 
> > > 
> > > As an aside, if I leave the Tru64 5 disk on the chain I get 
> > the dreaded
> > > "going nowhere without my init" panic. 
> > 
> > Yes, this still seems to be here. Something is reading the 
> > wrong disks's root
> > filesystem.
> > 
> > 
> > -matt
> > 
> > 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C0276A99F75AD41188950008C7B989FF088B4B>