I turn on the V300, and then issue a
echo "scsi add-single-device 0 0 6 0" > /proc/scsi/scsi
command with root. The green light at the front of the scanner turns off, and
then the computer starts becoming unresponsive. If I don't turn off the
scanner, eventually the kernel freezes. Turning off the scanner allows the
scsi driver to return to normal. Leaving the scanner on during boot seems to
work fine. Maybe I should test this thing under win95 (ugh) just to make sure
it works. This is a Tekram 390F (UltraWide). I am using a SCSI-3 cable (68pin
on one end, 50pin Centronics to the scanner, with an inline passive
terminator). Could the terminator be the problem? I don't need an active
terminator, do I?
Sep 22 07:49:56 oto kernel: scsi singledevice 0 0 6 0
Sep 22 07:49:59 oto kernel: scsi : aborting command due to timeout : pid
225687, scsi0, channel 0, id 0, lun 0 0x08 1c 85 61 02 00
Sep 22 07:49:59 oto kernel: ncr53c8xx_abort: pid=225687 serial_number=226017
serial_number_at_timeout=226017
Sep 22 07:49:59 oto kernel: ncr53c875-0: abort ccb=c3e03020 (cancel)
Sep 22 07:50:01 oto kernel: SCSI host 0 abort (pid 225687) timed out -
resetting
Sep 22 07:50:01 oto kernel: SCSI bus is being reset for host 0 channel 0.
Sep 22 07:50:01 oto kernel: ncr53c8xx_reset: pid=225687 reset_flags=2
serial_number=226017 serial_number_at_timeout=226017
Sep 22 07:50:01 oto kernel: ncr53c875-0: restart (scsi reset).
Sep 22 07:50:01 oto kernel: ncr53c875-0: Downloading SCSI SCRIPTS.
Sep 22 07:50:07 oto kernel: ncr53c875-0:6: ERROR (0:4) (8-0-0) (0/5) @ (script
5c:86030000).
Sep 22 07:50:07 oto kernel: ncr53c875-0: script cmd = 1e000000
Sep 22 07:50:07 oto kernel: ncr53c875-0: regdump: da 00 80 05 47 00 06 07 71 08
00 00 80 00 08 02.
Sep 22 07:50:07 oto kernel: ncr53c875-0: have to clear fifos.
Sep 22 07:50:07 oto kernel: ncr53c875-0: unexpected disconnect
Sep 22 07:50:07 oto kernel: ncr53c875-0-<6,0>: COMMAND FAILED (8a 0) @c0005020.
Sep 22 07:50:07 oto kernel: ncr53c875-0: SCSI parity error detected: SCR1=64
DBC=1e000000 SSTAT1=e
Sep 22 07:50:07 oto kernel: ncr53c875-0: restart (scsi reset).
Sep 22 07:50:07 oto kernel: ncr53c875-0: Downloading SCSI SCRIPTS.
Sep 22 07:50:10 oto kernel: ncr53c875-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
offset 8)
Sep 22 07:50:10 oto kernel: ncr53c875-0-<1,*>: FAST-5 SCSI 5.0 MB/s (200 ns,
offset 7)
On 22-Sep-98 Bernd Schroeder wrote:
> I have uploaded this to
>
> ftp://ftp.muc.de/people/bernds/mtek2/microtek2-pre0.5.220998.tar.gz .
>
> According to the scanner attributes the difference between the V300
> and the ScanMaker 330 is that the V300 has a 256 bytes gamma table, whereas
> the the 330 has 1024 bytes gamma table. This means that the V300 works
> internally with 8 bit per colour and the 330 with 10 bit.
>
> The backend should handle both sizes, so I would have expected, that
> it works with the above version, but it returned an IO-error.
> If this happens for you, too, please send me a trace with the environment
> variable SANE_DEBUG_MICROTEK2 set to 30.
>
> Just be sure, that find-scanner finds the scanner before calling scanimage
> or xscanimage.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com