[7340] in linux-scsi channel archive
ACARD host adapter and scanner
daemon@ATHENA.MIT.EDU (Jordi)
Sat Oct 9 00:49:39 1999
Date: Sat, 9 Oct 1999 00:55:52 +0200
From: Jordi <jordi-sd@softhome.net>
To: linux-scsi@vger.rutgers.edu
Message-ID: <19991009005552.A1213@softhome.net>
Mail-Followup-To: linux-scsi@vger.rutgers.edu
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu"
--sdtB3X0nJg68CQEu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
I had to resend this message due to sendmail errors. I apologize if you
recieved it twice.
----- Forwarded message from Jordi <jordi-sd@softhome.net> -----
Hello,
I'm having problems trying to boot a 2.2 kernel with my scanner on.
The SCSI card is ACARD and the kernel does recognize the SCSI device on
boot. If I boot with the scanner powered off, no problem, the kernel=20
recognizes the device and continues on, but if the scanner is on=20
at boot time, I get this error message (copied by hand) and the kernel
does not end booting.
aec67x_detect:
ACARD AEC-6666671X PCI Ultra/W SCSI-3 Host Adapter:0 IO: 6300, IRQ: 11
ID: 2 Color FlatbedScanner_90062
ID: 7 Host Adapter
scsi0 : ACARD AEC-6710/6712 PCI Ultra/W SCSI-3 Adapter Driver V1.0
scsi: 1 host
scsi: aborting command due to timeout: pid 2, scsi 0, channel 0, id 2, lun
0, Request Sense 00 00 00 10 00 workingu=3D1=20
last_cmd=3D2 quhdu=3D2 quendu=3D2 r 0=3D6 r 1=3D2c r2=3Dcf r3=3D3 r4=3D0 r5=
=3D0 r6=3D0 r7=3D10
r8=3D0 r9=3D0 ra=3D0 rb=3D0 rc=3D0 rd=3D0 re=3D0 rf=3D0=20
r10=3D36 r11=3D20 r12=3D0 r13=3D0 r14=3D4 r15=3D2 r16=3D80 r1c=3Da1 r1f=3D3=
7 ls_snd=3D0 r20=3D9
r22=3D1
SCSI: aborting command due to timeout: pid 2, scsi 0, channel 0, id 2, lun
0, Request Sense 00 00 00 10 00 workingu=3D1=20
last_cmd=3D2 quhdu=3D2 quendu=3D2 r 0=3D6 r 1=3D2c r2=3Dcf r3=3D3 r4=3D0 r5=
=3D0 r6=3D0 r7=3D10
r8=3D0 r9=3D0 ra=3D0 rb=3D0 rc=3D0 rd=3D0 re=3D0 rf=3D0=20
r10=3D36 r11=3D20 r12=3D0 r13=3D0 r14=3D4 r15=3D2 r16=3D80 r1c=3Da1 r1f=3D3=
7 ls_snd=3D0 r20=3D9
r22=3D1
SCSI host 0 abort (pid 2) timed out - reseting
SCSI bus is being reset for host 0 channel 0
SCSI host 0 channel 0 reset (pid 2) timed out - trying harder
SCSI bus is being reset for host 0 channel 0
I have left the computer 30 minutes in this state but nothing else
happened.
I have asked in the scsi newsgroups some time ago, and I got this response:
---
Your situation is different than mine, however,
the errors are the same. This being said I'll tell
you what I did and let you figure out if its of
help.
I'm running Redhat 6.0 using an adaptec 2940UW
SCSI host adaptor. I've been trying to get a old
SCSI hard drive to work but I was getting the same
messages as you during boot up.
I thought all my problems dealt with SCSI
termination. I was wrong.
I ended up going into the SCSI BIOS by pressing
ctrl-A at the boot up prompt.
After hours of troubleshooting I began resorted to
going into the BIOS scsi configuration and
changing individual flag settings and then
rebooting. It it didn't work I set the flag back
and changed another one. Scientific, I know.
I went into SCSI configuration and set the "Wide
negotiation" flag for the scsi ID corresponding to
my hard drive from "yes" to "no". This turned out
to be the only setting I needed to get my drive to
work.
-dan
---
Well, this card does not have bios support. ACARD told me the only way to
modify parameters was through the windows driver. I have tried what dan told
me, as well as other combinations, but it didn't work, so I'm clueless now.
Does anyone have experience with this card or problem?
Thank you in advance,
Jordi
----- End forwarded message -----
--sdtB3X0nJg68CQEu
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3/nZ4JYSUupF6Il4RAmp0AKCIibtWgIwuzjkoDLRK0DMNeEBjxACgsfiD
r5IBm0txr+rRrMgMu0QGG5w=
=xYET
-----END PGP SIGNATURE-----
--sdtB3X0nJg68CQEu--
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
