Menu
▾
▴
#49 Error during device I/O with SS 1236S
I was using an older version of sane and this scanner
for some time with very good results. When I had to
reinstall my OS due to a broken harddrive I compiled
the newest version of sane and it didn't work anymore.
So I got newest version of the snapscan backend with
the same result:
When I try to simply detect the scanner it works as
expected:
octo@leeloo:~ $ sane-find-scanner
...
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN
1236 1.50" at device /dev/scanner
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN
1236 1.50" at device /dev/sg4
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN
1236 1.50" at device /dev/sge
octo@leeloo:~ $ scanimage -L
device `snapscan:/dev/sg4' is a AGFA SNAPSCAN 1236
flatbed scanner
But when I try to access it, it aborts with an error:
octo@leeloo:~ $ scanimage
scanimage: open of device snapscan:/dev/sg4 failed:
Error during device I/O
The very same error accurs when trying with xscanimage
and xsane.
dmesg tells me:
(scsi0:0:4:0) Data overrun detected in Data-In phase,
tag 10;
Have seen Data Phase. Length=0, NumSGs=0.
Raw SCSI Command: 0x1d 04 00 00 00 00
The "tag" changes apparently randomly, but the SCSI
command stays the same.
If you need to know anything else please let me know.
Regards,
Florian Forster
flo-at-verplant-dot-org
Logged In: YES
user_id=89371
Hi,
please try the latest backend version (from today, 14th
April 2002). It contains a fix for some flavours of the
1236s.
If this still doesn't fix your problem please send me
(oliverschwartz@users.sourceforge.net) a debug log. Run
"export SNANE_DEBUG_SNAPSCAN=255" in your shell, then
"scanimage -L 2>debug.log" and send me the debug.log file.
Regards,
Oliver
Logged In: NO
Same problem. Using an Agfa Snapscan 1236s and now 3
different types of scsi controller the fault remains. I was using
this sytem satisfactorily under SuSE 7.3 but the upgrade to
SuSE 8.0 has given rise to this problem. (I can not recall the
SANE/XSANE version numbers, sorry) One bit of information
that might help is that under the 7.3 configuration I had to
ensure the quality box was unchecked in XSANE else it
would not work. I have an adaptable system that if you require
diagnostic test I can quickly run for you.
my work email is:
terry.timmis@ds-s.com
Logged In: NO
I have **exactly** the same problem (same symptoms, same
error messages)
My 1236S worked fine
under RedHat 7.2, and is now broken with RH 7.3.
I tried to deinstall the SANE/XSANE packages shipped with
RH 7.3 and to reinstall the old packages shipped with 7.2.
I still have this error, so I suppose a bad interaction between
SANE and the SCSI support of the kernel.
Logged In: YES
user_id=89371
Hi,
I said it before, but maybe it helps to say it again: The bug is
reported to be fixed in the latest backend version.
More particular: SANE-1.0.7 does not work for the
SnapScan1236s. SANE-1.0.8 should work fine.
As far as I know SANE-1.0.7 is shipped with RedHat 7.3. You
should try to get an updated SANE package from RedHat.
Alternatively you can compile SANE yourself.
If you still have problems after the upgrade please supply me
with a debug log (run "export
SANE_DEBUG_SNAPSCAN=255" in a shell, followed
by "xscanimage 2>debug.log". Send debug.log to
oliverschwartz@users.sourceforge.net).
Regards,
Oliver