SCSI Microtek slide scanner 35t stops working right!

SCSI Microtek slide scanner 35t stops working right!

Post by Richard M. Denne » Sun, 29 Apr 2001 16:38:02



The problem:
    1. A microtek 35t slide scanner which I have used periodically over
the last two years with xscanimage (or plugin in gimp) suddenly fails to
work. When selected to acquire a preview or scan (scanimage), the
scanner initializes, lowers the slide into position and sounds like it
begins the scan, but then freezes. Scanimage gives a message box,
"Error: device busy." When this happens, the /var/log/messages file
acquires references (see below) to "kernel: scsi: aborting command due
to timeout : pid 0, scsi0, channel 0, id 3, lun 0 Read Reverse 00 00 00
06 00" and then "SCSI host 0 abort (pid 0) timed out -resetting"....

 Additional information:
    1. The other SCSI devices (cdrom writer, E6 scanner and zip drive)
seem to be working fine.
    2. The 35 t slide scanner itself seems to be OK, because it scans
properly on the same system booted up with Win NT. (I use Win NT boot
manager during startup of my Linux system. I usually use Win NT in a
Linux vmware session. None of the scanners or the cdwriter work under
Win NT in a vmware session, which is as it should be, according to
vmware documentation).

The system: I have a SCSI chain consisting of a Yamaha 4x4x16 cdrom
writer (ID-1), Microtek 35t slide scanner (ID-3), Microtek E6 flatbed
scanner (0 0 4 0) and zip drive (0 0 5 0) connected to a single Adaptec
2930 CU SCSI card; RedHat 7 updated with kernel 2.4.1. SCSI support is
compiled in the kernel (ai7xxxx ). All SCSI devices are identified
properly at system startup and at Linux startup and are registered in
the /proc/scsi/scsi file., as follows:

Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: YAMAHA   Model: CRW4416S         Rev: 1.0g
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
  Vendor: MICROTEK Model: ScanMaker 35t+   Rev: 1.40
  Type:   Scanner                          ANSI SCSI revision: 01 CCS
Host: scsi0 Channel: 00 Id: 04 Lun: 00
  Vendor: MICROTEK Model: ScanMaker E6     Rev: 1.42
  Type:   Scanner                          ANSI SCSI revision: 04
Host: scsi0 Channel: 00 Id: 05 Lun: 00
  Vendor: IOMEGA   Model: ZIP 100          Rev: K.05
  Type:   Direct-Access                    ANSI SCSI revision: 02

I know little about SCSI troubleshooting, but it is clear from the
/var/log/messages file that the SCSI chain is failing when the 35t
scanner is started, as shown below. Could the 08:34:03 entry "Data
overrun detected in Data-In phase, tag 2" line be the critical problem?
If so, how does one deal with this type of problem?
Output of /var/log messages file as scan is started on the 35t scanner:
(triggered by selecting "acquire  preview" in scanimage for /dev/sgb:

Apr 27 08:33:53 rdenney kernel: scsi : aborting command due to timeout :
pid 0, scsi0, channel 0, id 3, lun 0 Read Reverse 00 00 00 06 00
Apr 27 08:33:54 rdenney kernel: SCSI host 0 abort (pid 0) timed out -
resetting
Apr 27 08:33:54 rdenney kernel: SCSI bus is being reset for host 0
channel 0.
Apr 27 08:34:03 rdenney kernel: (scsi0:0:3:0) Data overrun detected in
Data-In phase, tag 2;
Apr 27 08:34:03 rdenney kernel:   Have seen Data Phase. Length=6,
NumSGs=1.
Apr 27 08:34:03 rdenney kernel:      sg[0] - Addr 0x1c258000 : Length 6
Apr 27 08:34:09 rdenney kernel: scsi : aborting command due to timeout :
pid 0, scsi0, channel 0, id 1, lun 0 Prevent/Allow Medium Removal 00 00
00 01 00
Apr 27 08:34:13 rdenney kernel: scsi : aborting command due to timeout :
pid 0, scsi0, channel 0, id 3, lun 0 Read Reverse 00 00 00 06 00
Apr 27 08:34:19 rdenney kernel: scsi : aborting command due to timeout :
pid 0, scsi0, channel 0, id 1, lun 0 Prevent/Allow Medium Removal 00 00
00 01 00

I have tried rebooting my older kernel (2.2.17) and I seem to see the
same problem as described above. I have recently added an Adaptec ATA100
card and a new ATA harddrive attached to that card. This drive is
recognized as /dev/hde, while older drives in the machine are attached
to the motherboard IDE connectors (/dev/hda, /dev/hdb, /dev/hdc and an
ATAPI cdrom drive).  I am going to try disconnecting this drive and
removing the card to see if this might be causing the trouble, but it is
not clear to me why it would or what I would do about it if it does!

Some smart SCSI person please help!

Rick Denney

 
 
 

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

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

2. q

3. Microtek Scanmaker 35t+

4. Need Linux/C/JAVA/PERL programmer for embedded network project

5. Microtek ScanMaker 35t+

6. Autocad 14

7. microtek scanmaker 35t

8. Redhat 4.1 on a Toshiba 4800CT

9. Microtek Scanmaker 35t+

10. Microtek ScanMaker 35t+

11. Microtek Scanmaker 35t+

12. Any interest in MicroTek Labs parallel port/SCSI scanners?