Replaced the cable with a brand new one.  Same set of kernel responses and
crash.  Any other ideas before I try 2.4?

Drew

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Warren Melnick
Sent: Friday, January 19, 2001 2:28 PM
To: '[EMAIL PROTECTED]'
Subject: RE: RE: Configuratin of a 486DX4 [was RE: Speed optimization
for 486DX]


Are you using 50-pin (old) SCSI or one of the newer, wider drives.  If the
latter is true, you might want to try changing the cable.  The higher
density cables are really easy to damage with a slight crimp and will
exhibit the exact symptoms you are speaking of.

----------------
Warren Melnick
Director of Research and Development
Astata Corporation




-----Original Message-----
From: Drew Hunt [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 4:13 PM
To: [EMAIL PROTECTED]
Subject: RE: RE: Configuratin of a 486DX4 [was RE: Speed optimization
for 486DX]


I wasn't, so I pulled the HD to check...  Yep, termination is set.  Checked
BIOS...  Termination also set on the SCSI adapter.  The two devices are
connected with a SCSI ribbon cable that can support two SCSI devices on the
adapter.  Do I have to terminate the extra connector as well?

I did a series of runs installing the aic7xxx module.  These are the error
messages I received:

Run 1:
(scsi0) <Adaptec AHA-284X SCSI host adapter> found at VLB slot 1
(scsi0) Narrow Channel, SCSI ID=7, 4/255 SCBs
(scsi0) Downloading sequencer code... 415 instructions downloaded
---freezes

Run 2: (disconnected drive)
(aic7xxx installs fine)

Run 3:
{same as Run 1 with additional line}
(scsi0:0:0:0) Syncronous at 10 Mbyte/sec, offset 15.
---freezes

Run 4: (same as Run 3)

I did the first run off a cold boot.  Then I disconnected the drive and
tried again.  Installing the module worked fine.  'lsmod' showed aic7xxx
installed, but unused.  Third run had the drive connected again.  This time
it came up with an extra line that identified the drive before dying.
Weird.  The last run was the same as the one before it.

Any ideas as to what's wrong?  Do I just need to upgrade to kernel 2.4 as
some have suggested?

Thanks,
Drew



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to