[8145] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: DC-390: Debian broke it!

daemon@ATHENA.MIT.EDU (Eddie Maddox)
Tue Feb 22 04:38:56 2000

Date:   Tue, 22 Feb 2000 03:15:31 -0500 (EST)
From: Eddie Maddox <eddie@mngovsci.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Debian Boot <debian-boot@lists.debian.org>,
	Linux SCSI List <linux-scsi@vger.rutgers.edu>,
	"Andrew M.A. Cater" <amacater@galactic.demon.co.uk>,
	56634@bugs.debian.org
In-Reply-To: <20000221012450.V25715@mobil.tue.nl>
Message-ID: <Pine.LNX.3.96.1000222025701.25966A-100000@ns1.greenbush.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 21 Feb 2000, Kurt Garloff wrote:

> > 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]

> The message cited above is from my driver (tmscsim/DC390/AM53C974 driver),
> not the AM53C974. Sorry for the name confusion!

> > 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.

> > 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

Boot fails (see above):
Debian boot floppies 2.2.7:  AM53C974 v2.0d 1998/12/25
(From the console screen during boot attempts.)

Boots and runs fine:
Mandrake 6.1: AM53/79C974 PCscsi driver rev. 0.5; host I/O address...
(From /var/log/message* and /proc/scsi/am53c974/0.)

------------------
Eddie Maddox
eddie@mngovsci.com



-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post