Re: Mustek600IICD / lost lines

Klaus Weglehner (klaus@amsys.nbg.sub.org)
Sat, 18 Oct 1997 09:34:20 +0200 (MET DST)

Hello David!
------------

> This appears to be a feature of newer firmware revisions. If SANE
> recognizes your scanner, you should be OK, though.

The Firmware is 2.03. Perhaps I should send you the complete output
of the SCSI initialization too:

<4>Started kswapd v 1.4.2.2
<6>FDC 0 is an 8272A
<4>aha152x: processing commandline: ok
<4>aha152x: BIOS test: passed, detected 1 controller(s)
<4>aha152x0: vital data: PORTBASE=0x340, IRQ=12, SCSI ID=7, reconnect=disabled, parity=disabled,
synchronous=disabled, delay=100, extended translation=disabled
<4>aha152x: trying software interrupt, ok.
<4>scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $
<4>scsi : 1 host.
<4> Vendor: SCANNER Model: Rev: 2.03
<4> Type: Scanner ANSI SCSI revision: 01 CCS
<4>Detected scsi generic sga at scsi0, channel 0, id 0, lun 0
<4>scsi : detected total.
<6>SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).

Is it ok?

>
> Klaus> I tried to scan a
> Klaus> LineArt picture and everything seems to work well. But when I
> Klaus> tried to scan Color or even Grayscale pictures the scanner
> Klaus> mechanic moves to its physical end and makes the well known
> Klaus> sound which is described in the PROBLEMS file. I can limit
> Klaus> the scaning area to a non-dangerous value, but the image
> Klaus> seems to be compressed in y-direction and the scaning range
> Klaus> was always more than I have specified on the
> Klaus> comandline.
>
> That's strange. It appears as if the line-distance command does not
> get issued. If you run sane-0.66, make sure that "option
> linedistance-fix" is turned on (if you use the default mustek.conf,
> you should be fine, but verify to be sure: it's in
> /usr/local/etc/sane.d/mustek.conf).

Yes, it's turned on. The file looks like this:
(Btw: why comes the default file with several spaces in front of the option
commands so that the driver does not recognize it?)

|# See sane-mustek(5) for documentation.
|
|option strip-height 1
|
|/dev/scanner
|option linedistance-fix
|option lineart-fix # lineart may be faster with this option off.

> If you have the linedistance-fix on and it still doesn't work, can you
> invoke scanimage with environment variable SANE_DEBUG_MUSTEK set to
> 255 and send me the output you get?

Yep, comes at the end of the mail.

> Klaus> A tip how to get the Adaptec 1505 with the supplied
> Klaus> Windows-Twain-Driver working would be very useful too.
> Hmmh, sane-scsi(5) lists the Adaptec AHA-1505 to be working fine. I'm
> not familiar with that adapter, but if it has some sort of BIOS
> configuration, you may have to disable synchronous transfers, tagged
> queueing, and target disconnects (as documented in sane-mustek(5)).
> If you get it working, please let me know what you had to do so I can
> add it to the man page.
It has no bios. But I made the configuration shown in the SCSI
startup at the begining of this mail via lilo append line and I
think it's ok. The only thing I'm in doubt is the tagged queueing.
There is no kernel comandline option to turn it off and on. I
tried to set a DEFINE in aha152x.h to zero which says something about
the number of queueable commands. But I don't know whether this define
really means TAGGED queuing or queuing at all. (I don't know if there
is a difference) However, the behaviour has not changed since.

Ok, here comes the debug output:
The comand was:
scanimage -l90 -x20 -y30 --resolution 600 >test.pnm 2>debug.txt

[sanei_init_debug]: Setting debug level of mustek to 255.
[mustek] sane_init: strip-height set to 1 inches
[mustek] attach: opening /dev/scanner
[mustek] attach: sending INQUIRY
[mustek] wait_ready: sending TEST_UNIT_READY
[mustek] attach: firmware revision 2.03
[mustek] attach: found Mustek scanner model MFC-06000CZ (flatbed scanner), 1-pass
[mustek] sane_init: enabling linedistance-fix for /dev/scanner
[mustek] sane_init: enabling lineart-fix for /dev/scanner
[mustek] wait_ready: sending TEST_UNIT_READY
[mustek] line_distance: got factor=65535, (r/g/b)=(0/4/8)
[mustek] line_distance: fixed up to factor=65535, (r/g/b)=(0/4/8)
^^^^^
Is this ok?

[mustek] get_image_status: bytes_per_line=470, lines=710
[mustek] lines_per_buffer=277, bytes_per_line=470
[mustek] reader_process: line=554 (num_lines=710), num_reqs=2
[mustek] reader_process.send_data: data=0x80fb000, lpb=277, bpl=470, extra=0x813b000
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] reader_process: line=710 (num_lines=710), num_reqs=2
[mustek] reader_process.send_data: data=0x811ac8e, lpb=277, bpl=470, extra=0x813b000
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] reader_process: line=710 (num_lines=710), num_reqs=1
[mustek] reader_process.send_data: data=0x80fb000, lpb=156, bpl=470, extra=0x813b000
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] read 4096 bytes
[mustek] reader_process: line=710 (num_lines=710), num_reqs=0
[mustek] read 4096 bytes
[mustek] read 1924 bytes
[mustek] read 0 bytes
[mustek] do_stop: terminating reader process
[mustek] do_stop: reader process terminated with status 0x0
[mustek] do_stop: closing scanner

A note about the windows driver of the Controller:
They deliver a Lite-Version of the driver with the card. But
for scanning with the TWAIN driver which comes with the
scanner it seems that the full version is necessary.
I found this behaviour of Adaptec very bad because they
make advertisement by talking about the "wonderful" scanning
speed of the device but opening the package you
discover that you have to *buy* the Driver first.
Very strange.
But I would prefer to scan with linux either :-).

Many thanks!!
Klaus


--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com