Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!servitude!rogerk
From: rogerk@mips.COM (Roger B.A. Klorese)
Newsgroups: comp.sys.mips
Subject: Re: Trouble with Exabyte on RC3240 under RISCos 4.50
Keywords: 3240, 4.50, Exabyte
Message-ID: <41472@mips.mips.COM>
Date: 13 Sep 90 06:48:09 GMT
References: <1990Sep12.151525.16755@sobeco.com>
Sender: news@mips.COM
Reply-To: rogerk@mips.COM (Roger B.A. Klorese)
Organization: MIPS Computer Systems, Inc.
Lines: 39

In article <1990Sep12.151525.16755@sobeco.com> stacy@sobeco.com (Stacy L. Millions) writes:
>
>On a MIPS RC3240 running RISCos 4.50 I have installed
>an exabyte drive as unit # 5. The switches are set
>according to the 4.50 release notes.
>
>If I boot with:
>
>boot -f dkis()unix showconfig
>
>I can access the exabyte.
>
>If I don't boot with showconfig, the command:
>
>mt -f /dev/rmt/h0 status
>
>returns:
>
>/dev/rmt/h0: No such device.
>
>as does dd, tar, and any thing else that tries
>to open the device.
>
>I assume this is a problem with the initialization
>of the SCSI devices at boot time, but I have not
>taken the time to go look at the device driver since
>booting showconfig is a fairly simple work around.
>Anyone have a better solution (like a working kernel :-).

Did your 4.50 release include a document headed "READ ME FIRST"?  The fix for
this problem is documented therein.

Contact the CRC for either (a) a script you can run in the startup sequence
to clear the drive status, or (b) a driver source patch, whichever you prefer.
-- 
ROGER B.A. KLORESE                                  MIPS Computer Systems, Inc.
MS 6-05    930 DeGuigne Dr.   Sunnyvale, CA  94086              +1 408 524-7421
rogerk@mips.COM         {ames,decwrl,pyramid}!mips!rogerk         "I'm the NLA"
"Lead me not into temptation; I can find the way myself."      --Rita Mae Brown