[8132] in linux-scsi channel archive
Re: DC-390: Debian broke it!
daemon@ATHENA.MIT.EDU (Kurt Garloff)
Sun Feb 20 19:33:31 2000
Date: Mon, 21 Feb 2000 01:24:51 +0100
From: Kurt Garloff <garloff@suse.de>
To: Eddie Maddox <eddie@mngovsci.com>
Cc: Linux SCSI List <linux-scsi@vger.rutgers.edu>,
"Andrew M.A. Cater" <amacater@galactic.demon.co.uk>,
56634@bugs.debian.org
Message-ID: <20000221012450.V25715@mobil.tue.nl>
Mail-Followup-To: Eddie Maddox <eddie@mngovsci.com>,
Linux SCSI List <linux-scsi@vger.rutgers.edu>,
"Andrew M.A. Cater" <amacater@galactic.demon.co.uk>,
56634@bugs.debian.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="8MA55IEjTDEadc2f"
In-Reply-To: <Pine.LNX.3.96.1000218124034.14371A-100000@ns1.greenbush.com>
--8MA55IEjTDEadc2f
Content-Type: text/plain; charset=us-ascii
On Fri, Feb 18, 2000 at 01:06:50PM -0500, Eddie Maddox wrote:
> I'm testing the Debian boot floppy 2.2.x images for their next release.
> They do not boot for me. Floppy images 2.2.7 have kernel 2.2.14.
>
> I filed Debian bug# 56634.
>
> I have a Tekram DC-390. Error message:
> DC390: RESTORE POINTER message received... reject
> scsi: aborting command due to timeout: pid 24, ... (status 4)
> [and 1/2 a screen full of other stuff, then booting halts]
>
> It appears to use the AM53C974 driver.
The message cited above is from my driver (tmscsim/DC390/AM53C974 driver),
not the AM53C974. Sorry for the name confusion!
> When I boot with old 2.1.9 (2.0.36 kernel) floppies all works well. Newer
> 2.1.12 and this 2.2.x testing series are the problem.
>
> I noticed from Kurt Garloff's DC-390 site that the version of the AM53C974
> driver changed from 1.x to 2.x after kernel 2.0.36. Does that help explain
> why Debian '390 support is broke after the 2.1.9 boot floppies with the
> 2.0.36 kernel?
Do I correctly understand, that the _new_ 2.0d driver included into kernel
2.0.36+ and 2.2.x broke the boot process?
In that case, a bug report should have gone to me!!!
> However, I now run Mandrake 6.1 for production use. That has kernel
> 2.2.13pre. No problems!
So what. Tell us what version of the driver is included there and what
version failed for you. There is no way developers can track the versions
of their drivers put into all the distros. I just happen to know it for the
one I use and develop.
> Please note: I am _not_ a developer. I do _not_ code C in my sleep.
> So please be careful before saying things like, "Just recompile your
> kernel!" :(
OK, so you want to have somebody else to do it for you ...
> Debian, and all distros, need _working_ code. Expecting a user to fix what
> is broke is worse than bad. And I am a user, not an experimenter.
If you believe, that open source leads to perfect products, you are out of
reality, sorry!
The feedback process is much better and the fixing possibilities are much
better. But only if the ones meeting the trouble are willing to help.
> This does go against Free Software/Open Source ideas somewhat, but those
> without coding skills need "out of the box" functionality. And I don't
> code.
Well, go and buy something and try to sue somebody and see whether this
works. Alternatively, try to send a bug report to a commercial vendor and
see whether you get more than an automated response. If you get a human one,
guess whether it's one from the developer concerned with this peice of
software.
> I will try to help you all diagnose this bug, however. Tell me what you
> need from me, and how to do it. I do have some related experience.
The version of the working drivers and the ones of the non-working ones.
Are displayed on driver initialization (i.e. kernel boot time or module load
time) and can also be displayed by cat /proc/scsi/tmscsim/?
A hint to the debian people: I don't know what version you used. If it is
2.0d, I might ask you to try the latest one (2.0d28) from my web page
http://www.garloff.de/kurt/linux/dc390/ ?
The RESTORE POINTER message there is handled.
It should be sent to Linus for kernel inclusion anyway, but I'm sometimes
trying to be too perfect ...
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
--8MA55IEjTDEadc2f
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4sIXSxmLh6hyYd04RAeb2AJ9xhCTtSP6stLg8xUUCpzzcua0q3ACgpLYI
U3Lh820rAlT0PvgSITq9TnQ=
=LpMn
-----END PGP SIGNATURE-----
--8MA55IEjTDEadc2f--
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
