Kernel 2.4.x breaks microtek SCSI 35t+ scanner!

Kernel 2.4.x breaks microtek SCSI 35t+ scanner!

Post by Richard M. Denne » Fri, 04 May 2001 13:14:52



I have been posting to this newsgroup about problems with my 2 year old
SCSI 35t slide scanner. I hadn't used it for a while and found that it
failed to scan and gave SCSI bus errors in /var/log/messages when
accessed via GIMP and xscanimage. On the same machine, it works under
WinNT, so it is mechanically OK.  I realized that the last time I had
used it was probably before installation of RH 7.0 and subsequent
upgrading of a 2.2.17 kernel to 2.2.1. I now have found that it is the
kernel upgrade that was the culprit, but I don't have a solution to make
the scanner work in a 2.2.x kernel.

My other SCSI devices workewith the newer kernels (including a microtek
E6 scanner, Yamaha 4x4x16 cdrom writer, and 100 meg zip drive).

I have just recompiled a 2.2.19 kernel and a 2.2.0 kernel and tried both
of them with the scanner. The scanner (and other devices) work fine with
the 2.2.19 kernel, but the 35t+ shows the following symptoms with the
2.2.0 kernel. (Also a 2.2.1 and 2.2.4 kernels that I have also tried.):

When accessed under GIMP  1.1 (xscanimage 0.61) from RedHat 7 package,
(Xtrns > Acquire Image, preview window ), the slide is lowered into
place, but as the scan begins,  the error "device is busy" occurs. In
/var/log/messages file, I get a variety of messages from the SCSI bus.
Typical is:

May  2 23:01:08 rdenney kernel: scsi : aborting command due to timeout :
pid 0, scsi0, channel 0, id 3, lun 0 Read Reverse 00 00 00 06 00
May  2 23:01:09 rdenney kernel: SCSI host 0 abort (pid 0) timed out -
resetting
May  2 23:01:09 rdenney kernel: SCSI bus is being reset for host 0
channel 0.
May  2 23:01:18 rdenney kernel: (scsi0:0:3:0) Data overrun detected in
Data-In phase, tag 0;
May  2 23:01:18 rdenney kernel:   Have seen Data Phase. Length=6,
NumSGs=1.
May  2 23:01:18 rdenney kernel:      sg[0] - Addr 0x177d0000 : Length 6

The slide remains in the lowered position until the scanner is powered
off and on, which reboots the scanner and restores it to a ready state.

If anyone has any idea why this particular scanner would malfunction
with kernels 2.4.x, but not with 2.2.19, would be appreciated.  I
NEED kernel 2.4.X to access a new 60 meg harddrive I have attached to a
ATA100 IDE card (using the Promise 20267 chip support compiled into the
2.4.x kernel). The 2.2.19 kernel has no support for this card and the
drive is not recognized.

Oh well, I can alwas boot into either kernel using lilo!

Rick Denney