[6664] in linux-scsi channel archive
Re: scsi problems (continued)...
daemon@ATHENA.MIT.EDU (Kurt Garloff)
Sat Jun 12 03:26:19 1999
Date: Sat, 12 Jun 1999 09:00:04 +0200
From: Kurt Garloff <garloff@suse.de>
To: DMW <shamrock@mtco.com>
Cc: linux-scsi@vger.rutgers.edu, Gerard Roudier <groudier@club-internet.fr>
Mail-Followup-To: DMW <shamrock@mtco.com>, linux-scsi@vger.rutgers.edu,
Gerard Roudier <groudier@club-internet.fr>
In-Reply-To: <3761B8F7.9721903D@mtco.com>; from DMW on Sat, Jun 12, 1999 at 01:33:43AM +0000
--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Sat, Jun 12, 1999 at 01:33:43AM +0000, DMW wrote:
> Hi everyone --
>=20
> I had posted a problem a week ago or so about a new Tekram DC 310 scsi
> controller (uses the sym53c810 chip) that I'm trying to get working.=20
> Well, I think I've gotten a little further, but I'm still unsuccessful
> at getting everything working.
>=20
> The situation is, I have a Pentium-based Redhat 6 system, with a fresh
> 2.3.5 kernel. I just re-built the kernel with support (not modular) for
> the sym53c8xx and ncr53c8xx. The only scsi device I have is a Umax
> scanner...it has ID 1. The controller is ID 0. Sound simple enough?
You only need one of them. And for 53c810a, you should prefer ncr53c8xx, I
think.
> Jun 11 20:18:19 localhost kernel: sym53c8xx: 53c810a detected with Symbio=
s NVRAM
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: rev=3D0x23, base=3D0xdf80=
0000, io_port=3D0xd000, irq=3D4
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: Symbios format NVRAM, ID =
0, Fast-10, Parity Checking
Gerard, does the DC310 use Symbios format NVRam?
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: initial SCNTL3/DMODE/DCNT=
L/CTEST3/4/5 =3D (hex) 03/ce/a0/01/00/00
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: final SCNTL3/DMODE/DCNTL/=
CTEST3/4/5 =3D (hex) 03/ce/a0/00/08/00
> ...
> Jun 11 20:18:19 localhost kernel: scsi0 : sym53c8xx - version 1.3c=20
> Jun 11 20:18:19 localhost kernel: scsi : 1 host. J
> ...
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: command processing resumed
> Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6 6@=
002ffe45 resid=3D5.
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
> Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: COMMAND FAILED (8a =
ff) @c3fe7000.
> Jun 11 20:18:19 localhost kernel: sym53c810a-0-<1,0>: phase change 2-6 6@=
002ffe45 resid=3D5.
> Jun 11 20:18:19 localhost kernel: sym53c810a-0: unexpected disconnect
> ...
> Jun 11 20:18:19 localhost kernel: scsi : detected total. =
=20
>=20
>=20
> I don't know if these messages are good, bad, or just ugly. I do know
> that when I do a "cat /proc/scsi/scsi" I get a "Attached devices:
> none". I guess that means it can't see the scanner. I do have the
> scanner powered up before booting. =20
They are not just ugly, because you don't see the scanner. So you either
have a hardware or a driver problem.=20
But I'd like to have Gerard to comment on it.
> Like I said, the only scsi devices are the scanner, which I know is
> terminated, and the host adapter. So what could the problem be?
Did you try the ncr53c8xx driver?
(Don't tell me that it's in the kernel. I know that from the above messages.
Just, how it is supposed to work, if the sym53c8xx driver is initialized
first and takes the resources?)
Regards,
--=20
Kurt Garloff <garloff@suse.de> SuSE GmbH, N=FCrnberg, FRG
Linux kernel development; SCSI driver: DC390 (tmscsim/AM53C974)
--45Z9DzgjV8m4Oswq
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3in
iQCVAwUBN2IFdBaQN/7O/JIVAQEDBwP+O/EHDxnbJi2KRbuoDiC1+yPzNO4wrpth
P8tRJwVry+CcaARTQubJBdx9w/8gYx+IxtvekIB0RYzxeRtg7aQaoNUGTyhGZ/zh
XrPwAwf5t6oqKgjev/wiFI+5ZeuHGyiolLmK2DIxu6ltQ43ZxOmDnlXDsPWK/0/A
DlB9SP2AKtc=
=mK4d
-----END PGP SIGNATURE-----
--45Z9DzgjV8m4Oswq--
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
