From: drew@juliet.cs.colorado.edu (Drew Eckhardt) Subject: Re: Segate ST02 problems Date: Mon, 1 Mar 1993 06:24:30 GMT
In article <1mp0rkINNg87@life.ai.mit.edu> jimc@hal.gnu.ai.mit.edu (James Carpenter) writes:
>In article <C32wDL.HC6@news.cso.uiuc.edu> jeske@ux4.cso.uiuc.edu (Dave Jeske) writes:
>>The SLS .99pl5 boot disk detects the scsi host and the SEGATE ST296N
>>drive just fine. It continues a few more lines through the boot, and then
>>hangs with two "SCSI host 3 timed out - aborting command" messages. Is
>>there a fix for this. I seem to remember someone posting some st02
>>problems a short while ago, and I cannot find it.
>>
>
>I have a problem just like this. I use a ST-01 with a Quantum ELS85. Linux
>sees it. MS-DOG loves the thing. And I can use it under Linux for a little
>while but then:
>
>>SCSI host 3 timed out - aborting command
>>SCSI host 3 timed out - aborting command
>>
>
>Except for me its host 0. Message is always twice. It appears that yours
>hangs much sooner than mine (it always times out during boot?). Mine varies.
>But will always, sooner or later, timeout.
>
>><the computer hangs here>
>>
>
>Have you tried switching to another VC. My computer appears to hang but I
>can still use other VCs. I can't kill the process that caused the timeout. I
>also can't use a command that deals with the SCSI. For example, because I
>can mount it, sync will hang, and I have to go to a third VC. Mount/unmount
>will work for any drives except the SCSI.
>
>I am truly sorry. But it appears that, now, you are stuck in my world :-)
>And there doesn't appear to be a way out :-(
From the FAQ :
QUESTION: I get SCSI timeouts.
ANSWER: Make sure your board has interrupts enabled correctly.
QUESTION: The seagate driver doesn't work.
ANSWER: There are several possibilities
1) Is the board jumpered for IRQ5 ?
The factory settings are
for MSLOSS, and have interrupts disabled. Interrupts are controlled
by the W3 (ST01) or JP3 (ST02) jumper, which should have pins FG
shorted. See your manual.
2) Cached machines will not have problems IF the Seagate's address
space (typically C8000 - CAFFFF) is not marked "non cacheable."
This applies to the i486 internal cache as well as i386/i486
external caches.
This can be set in the XCMOS of most machines. If you can't disable
cache for the Seagate's area (16K in size, starting at the base
address), then you must disable the cache entirely, otherwise
it won't work.
-- Boycott USL/Novell for their absurd anti-BSDI lawsuit. | Drew Eckhardt Condemn Colorado for Amendment Two. | drew@cs.Colorado.EDU Use Linux, the fast, flexible, and free 386 unix |