[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: aic7xxx kernel: Did you solve your problem?



Hi

I've got an 2940UW to and I've got a similar problem with it. I've tried
almost everything since the past December and the problem still goes on. My
system hangs at the detection phase of the HD attached to the card (it's the
only device attached to the card). I get a timed out error.

If you get a solution, how did you solve your problem?

I'll thank any information that could solve my problem?

Antonio A. Rivas     aeypil@teleline.es
STARTEG Project - Oviedo (Spain)  aesypil@hotmail.com

-
Even God discuss on the details with the devil.
-

-----Mensaje original-----
De: Richard Hall <hall@ns.utk.edu>
Para: Debian User List <debian-user@lists.debian.org>
Fecha: lunes, 11 de enero de 1999 07:58 a.m.
Asunto: aic7xxx kernel


>I installed Debian using a pre-compiled set of disks made especially for
>the Adaptec 2940 SCSI card, and now I am trying to make a custom kernel.
>I know what I'm doing, but I can't figure out which options to choose
>during 'make config' to get a working kernel.  I've tried several
>permutations.  Here's what happens:
>
>When I boot with the precompiled kernel and its starting to deal with the
>SCSI bus, it says:
>
>(scsi0) Downloading sequencer code . . . 419 instructions read
>
>then it boots fine
>
>When I boot with my custom floppy:
>
>(scsi0) Downloading sequencer code . . . 406 instructions read
>
>then it reports a parity error and falls into an infinite failure loop
>
>Can anyone tell me which parameters to choose during 'make config' to fix
>this?  There are three questions that come up when I choose the AIC7xxx
>driver.  I've answered yes and no to overriding driver defaults, yes and
>no to verbose error reporting, and tried 5 and 15 second waits after
>resetting SCSI bus.  What am I missing?
>
>TIA,
>
>Richard Hall
>Network Services
>University of Tennessee
>
>
>--
>Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org <
/dev/null
>


Reply to: