home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!odin!fido!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sgi
- Subject: Re: Problem attaching Exabyte
- Message-ID: <ooj57j4@zuni.esd.sgi.com>
- Date: 19 Aug 92 04:49:18 GMT
- References: <1992Aug16.155546.24668@iscnvx.lmsc.lockheed.com> <olu5hl4@zuni.esd.sgi.com> <1992Aug19.010323.6813@iscnvx.lmsc.lockheed.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 23
-
- In <1992Aug19.010323.6813@iscnvx.lmsc.lockheed.com> cunning@arthur.msd.lmsc.lockheed.com (Dave Cunningham) writes:
- | No, I didn't change the kernel or system disk. Since my last posting
- | I built a new kernel with lboot, and got the same behavior. Also, it
- | turns out that the problem is not just the third party exabyte. I get
- | the same behaviour when I attach an SGI cdrom drive with SGI
- | cable/terminator- everything looks normal but unix dies somewhere
- | between loading (I can see that happen if I load sash and boot unix
- | from there) and the "Irix 4.x..." announcement. I also loaded a working
- | kernel across the net and got the same behavior. With only the
- | (internal) system disk on the bus everything works fine.
-
- It sure sounds to me like a SCSI cabling or connector problem.
- Possibly the termpower fuse for the SCSI bus has been blown.
-
- Even so, I wouldn't expect that to keep the kernel from booting,
- although it might give errors during the boot. A backwards
- cable could do it though (those plastic connectors will fit
- on the connector backwards quite nicely), and that might in
- fact keep the kernel from booting on the 20 and 25.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-