Discussion:
Agfa DuoScan SCSI scanner with Mac OS X 10.4
(too old to reply)
Werner Randelshofer
2011-07-22 08:52:17 UTC
Permalink
Hi,

I am trying to use an Agfa DuoScan SCSI scanner with Mac OS X 10.4.

When I run sane-find-scanner, the scanner is listed, but scanimage -L reports an error.
I think scanimage does not work, because the device is listed with a number instead of with /dev/...

I tried
$ scanimage -d 01723e000000000e0b9ad186
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument

and

$ scanimage -d "<01723e000000000e0b9ad186>"
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument


Is there a different way how I am suposed to use the device number in the scanimage command?


Below are the outputs of sane-find-scanner and scanimage -L.

TIA,
Werner


$ sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

found SCSI scanner "AGFA DUOSCAN 2.30" at <01723e000000000e0b9ad186>
found SCSI scanner "AGFA DUOSCAN 2.30" at <01723c000000000e1b7f7937>
found SCSI scanner "AGFA DUOSCAN 2.30" at <01723a000000000e3190bf86>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017238000000000e31ec6d9c>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017236000000000e32468f79>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017234000000000e329f8164>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017232000000000e32f98119>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017230000000000e335270aa>
# Your SCSI scanner was detected. It may or may not be supported by SANE. Try
# scanimage -L and read the backend's manpage.

# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.


$ scanimage -L
[sanei_debug] Setting debug level of dll to 0.
[sanei_debug] Setting debug level of agfafocus to 128.
[agfafocus] attach: opening /dev/scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: device name /dev/scanner is not valid
[agfafocus] attach: open failed (Invalid argument)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
Werner Randelshofer
2011-07-22 10:30:01 UTC
Permalink
I have removed now all Adaptec Kernel extensions from /System/Library/Extensions except Adaptec 78XXSCSI.kext as described in the following article.

http://reviews.cnet.com/8301-13727_7-10334774-263.html


sane-find-scanner lists now only a single scanner device.

found SCSI scanner "AGFA DUOSCAN 2.30" at <0240a6000000002d134c34f4a>

I think this is an improvement. Yet, the scanner device has just this strange number, and
scanimage -L still states that no scanners were identified.

Any idea how to fix this?

-Werner
Post by Werner Randelshofer
Hi,
I am trying to use an Agfa DuoScan SCSI scanner with Mac OS X 10.4.
When I run sane-find-scanner, the scanner is listed, but scanimage -L reports an error.
I think scanimage does not work, because the device is listed with a number instead of with /dev/...
I tried
$ scanimage -d 01723e000000000e0b9ad186
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument
and
$ scanimage -d "<01723e000000000e0b9ad186>"
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument
Is there a different way how I am suposed to use the device number in the scanimage command?
Below are the outputs of sane-find-scanner and scanimage -L.
TIA,
Werner
m. allan noah
2011-07-22 10:51:03 UTC
Permalink
Try changing /etc/sane.d/dll.conf. Disable agfafocus and make sure
microtek is enabled.

allan

On Fri, Jul 22, 2011 at 4:52 AM, Werner Randelshofer
Post by Werner Randelshofer
Hi,
I am trying to use an Agfa DuoScan SCSI scanner with Mac OS X 10.4.
When I run sane-find-scanner, the scanner is listed, but scanimage -L reports an error.
I think scanimage does not work, because the device is listed with a number instead of with /dev/...
I tried
$ scanimage -d 01723e000000000e0b9ad186
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument
and
$ scanimage -d "<01723e000000000e0b9ad186>"
scanimage: open of device 01723e000000000e0b9ad186 failed: Invalid argument
Is there a different way how I am suposed to use the device number in the scanimage command?
Below are the outputs of sane-find-scanner and scanimage -L.
TIA,
Werner
$ sane-find-scanner
 # sane-find-scanner will now attempt to detect your scanner. If the
 # result is different from what you expected, first make sure your
 # scanner is powered up and properly connected to your computer.
found SCSI scanner "AGFA DUOSCAN 2.30" at <01723e000000000e0b9ad186>
found SCSI scanner "AGFA DUOSCAN 2.30" at <01723c000000000e1b7f7937>
found SCSI scanner "AGFA DUOSCAN 2.30" at <01723a000000000e3190bf86>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017238000000000e31ec6d9c>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017236000000000e32468f79>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017234000000000e329f8164>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017232000000000e32f98119>
found SCSI scanner "AGFA DUOSCAN 2.30" at <017230000000000e335270aa>
 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try
 # scanimage -L and read the backend's manpage.
 # No USB scanners found. If you expected something different, make sure that
 # you have loaded a kernel driver for your USB host controller and have setup
 # the USB system correctly. See man sane-usb for details.
 # Not checking for parallel port scanners.
 # Most Scanners connected to the parallel port or other proprietary ports
 # can't be detected by this program.
 # You may want to run this program as root to find all devices. Once you
 # found the scanner devices, be sure to adjust access permissions as
 # necessary.
$ scanimage -L
[sanei_debug] Setting debug level of dll to 0.
[sanei_debug] Setting debug level of agfafocus to 128.
[agfafocus] attach: opening /dev/scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: device name /dev/scanner is not valid
[agfafocus] attach: open failed (Invalid argument)
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
--
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
--
"The truth is an offense, but not a sin"
Werner Randelshofer
2011-07-22 11:40:14 UTC
Permalink
Hi Allan,

I have now disabled agfafocus and enabled microtek.
scanimage -L works now. This is great. Thank you!

Unfortunately, I still can not scan a page. I get the following error message.

scanimage: sane_start: Error during device I/O

I have attached the output of scanimage at the end of this e-mail.
I have switched the debugging on for sanei_scsi and microtek.

I guess there might be a problem with the commands that are sent to the device.
Suggestions highly appreciated.

Werner
Post by m. allan noah
Try changing /etc/sane.d/dll.conf. Disable agfafocus and make sure
microtek is enabled.
allan
$ scanimage > Desktop/test.pnm
[sanei_debug] Setting debug level of microtek to 128.
[microtek] sane_init: MICROTEK says hello! (v0.13.1)
[microtek] sane_init: config-> # Uncomment following line to disable "real calibration" routines...
[microtek] sane_init: config-> #norealcal
[microtek] sane_init: config-> # Uncomment following line to disable "clever precalibration" routines...
[microtek] sane_init: config-> #noprecal
[microtek] sane_init: config-> # Using "norealcal" will revert backend to pre-0.11.0 calibration code.
[microtek] sane_init: config-> scsi * * Scanner
[microtek] attach_scanner: <019bc800000000172dcdf573>
[microtek] attach_scanner: opening <019bc800000000172dcdf573>
[sanei_debug] Setting debug level of sanei_scsi to 255.
[microtek] attach_scanner: sending INQUIRY
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:96 isWrite:0
[sanei_scsi] isRead dst_size:96
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 96 bytes
[microtek] id_microtek...
[microtek]
[microtek]
[microtek]
[microtek] ========== Congratulations! ==========
[microtek] Your scanner appears to be supported
[microtek] by the microtek backend. However, it
[microtek] has never been tried before, and some
[microtek] parameters are bound to be wrong.
[microtek]
[microtek] Please send the scanner inquiry log in
[microtek] its entirety to mtek-***@mir.com and
[microtek] include a description of the scanner,
[microtek] including the base optical resolution.
[microtek]
[microtek] You'll find complete instructions for
[microtek] submitting an error/debug log in the
[microtek] 'sane-microtek' man-page.
[microtek]
[microtek]
[microtek]
[microtek] === SANE/Microtek backend v0.13.1 ===
[microtek] ========== Scanner Inquiry Block ========mm
[microtek] 06 00 01 01 5b 00 00 00 41 47 46 41 20 20 20 20
[microtek] 44 55 4f 53 43 41 4e 20 20 20 20 20 20 20 20 20
[microtek] 32 2e 33 30 53 43 53 49 20 46 57 20 56 33 2e 36
[microtek] 20 43 54 4c 35 33 38 30 03 4f 8c c5 06 ee 5d 43
[microtek] 01 03 47 00 00 83 00 01 0e 4a 07 05 00 00 00 00
[microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
[microtek] ========== Scanner Inquiry Report ==========
[microtek] ===== Scanner ID...
[microtek] Device Type Code: 0x06
[microtek] Model Code: 0x5d
[microtek] Vendor Name: 'AGFA ' Model Name: 'DUOSCAN '
[microtek] Vendor Specific String: 'SCSI FW V3.6 CTL5380'
[microtek] Firmware Rev: '2.30'
[microtek] SCSI F/W version: 0.0 Scanner F/W version: 0.1
[microtek] Response data format: 0x01
[microtek] ===== Imaging Capabilities...
[microtek] Modes: Lineart Halftone Gray Color (OnePass)
[microtek] Resolution Step Sizes: 1% 5% Expanded Resolution Support? yes
[microtek] Supported Bits Per Sample: 4 8 10 12
[microtek] Max. document size code: 0x06
[microtek] Max. document size: 8299 x 13499 pixels
[microtek] Frame units: pixels 1/8"'s
[microtek] # of built-in halftones: 12 Downloadable patterns? Yes
[microtek] Data Compression:
[microtek] Contrast Settings: 14 Exposure Settings: 74
[microtek] Adjustable Shadow/Highlight? yes Adjustable Midtone? yes
[microtek] Digital brightness/offset? yes
[microtek] Gamma Table Size: 4096 entries of 2 bytes (max. depth: 12)
[microtek] ===== Source Options...
[microtek] Feed type: flatbed ADF support? yes
[microtek] Document Feeder Support? yes Feeder Backtracking? yes
[microtek] Feeder Installed? no Feeder Ready? no
[microtek] Transparency Adapter Installed? yes
[microtek] Fast Color Prescan? no
[microtek] Selectable Transfer Format? no
[microtek] Color Transfer Sequence: line-by-line, non-sequential with headers
[microtek] Three pass scan support? no
[microtek] ModeSelect-1 and ModeSense-1 Support? yes
[microtek] Can Disable Linearization Table? no
[microtek] Can Disable Start-of-Scan Recalibration? no
[microtek] Internal expanded expansion? no
[microtek] ====== End of Scanner Inquiry Report =======
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: device name /dev/scanner is not valid
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:9 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:9
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 9 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:10 src_size:8192 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:8192
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 8192 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:11 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:11
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 11 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:10 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:10
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 10 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:6 isWrite:0
[sanei_scsi] isRead dst_size:6
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 6 bytes
[sanei_scsi] taskStatus = 0x00000002
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
scanimage: sane_start: Error during device I/O
m. allan noah
2011-07-22 12:21:24 UTC
Permalink
Well, according to the debug message, this model is untested. Perhaps
you can email the author as directed?

allan

On Fri, Jul 22, 2011 at 7:40 AM, Werner Randelshofer
Post by Werner Randelshofer
Hi Allan,
I have now disabled agfafocus and enabled microtek.
scanimage -L works now. This is great. Thank you!
Unfortunately, I still can not scan a page. I get the following error message.
scanimage: sane_start: Error during device I/O
I have attached the output of scanimage at the end of this e-mail.
I have switched the debugging on for sanei_scsi and microtek.
I guess there might be a problem with the commands that are sent to the device.
Suggestions highly appreciated.
Werner
Post by m. allan noah
Try changing /etc/sane.d/dll.conf. Disable agfafocus and make sure
microtek is enabled.
allan
$ scanimage > Desktop/test.pnm
[sanei_debug] Setting debug level of microtek to 128.
[microtek] sane_init:  MICROTEK says hello! (v0.13.1)
[microtek] sane_init:  config-> # Uncomment following line to disable "real calibration" routines...
[microtek] sane_init:  config-> #norealcal
[microtek] sane_init:  config-> # Uncomment following line to disable "clever precalibration" routines...
[microtek] sane_init:  config-> #noprecal
[microtek] sane_init:  config-> #   Using "norealcal" will revert backend to pre-0.11.0 calibration code.
[microtek] sane_init:  config-> scsi * * Scanner
[microtek] attach_scanner:  <019bc800000000172dcdf573>
[microtek] attach_scanner:  opening <019bc800000000172dcdf573>
[sanei_debug] Setting debug level of sanei_scsi to 255.
[microtek] attach_scanner:  sending INQUIRY
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:96 isWrite:0
[sanei_scsi] isRead dst_size:96
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 96 bytes
[microtek] id_microtek...
[microtek]
[microtek]
[microtek]
[microtek] ========== Congratulations! ==========
[microtek] Your scanner appears to be supported
[microtek] by the microtek backend.  However, it
[microtek] has never been tried before, and some
[microtek] parameters are bound to be wrong.
[microtek]
[microtek] Please send the scanner inquiry log in
[microtek] include a description of the scanner,
[microtek] including the base optical resolution.
[microtek]
[microtek] You'll find complete instructions for
[microtek] submitting an error/debug log in the
[microtek] 'sane-microtek' man-page.
[microtek]
[microtek]
[microtek]
[microtek]  === SANE/Microtek backend v0.13.1 ===
[microtek] ========== Scanner Inquiry Block ========mm
[microtek] 06 00 01 01 5b 00 00 00 41 47 46 41 20 20 20 20
[microtek] 44 55 4f 53 43 41 4e 20 20 20 20 20 20 20 20 20
[microtek] 32 2e 33 30 53 43 53 49 20 46 57 20 56 33 2e 36
[microtek] 20 43 54 4c 35 33 38 30 03 4f 8c c5 06 ee 5d 43
[microtek] 01 03 47 00 00 83 00 01 0e 4a 07 05 00 00 00 00
[microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
[microtek] ========== Scanner Inquiry Report ==========
[microtek] ===== Scanner ID...
[microtek] Device Type Code: 0x06
[microtek] Model Code: 0x5d
[microtek] Vendor Name: 'AGFA    '   Model Name: 'DUOSCAN         '
[microtek] Vendor Specific String: 'SCSI FW V3.6 CTL5380'
[microtek] Firmware Rev: '2.30'
[microtek] SCSI F/W version: 0.0     Scanner F/W version: 0.1
[microtek] Response data format: 0x01
[microtek] ===== Imaging Capabilities...
[microtek] Modes:  Lineart Halftone Gray Color (OnePass)
[microtek] Resolution Step Sizes: 1% 5%    Expanded Resolution Support? yes
[microtek] Supported Bits Per Sample: 4 8 10 12
[microtek] Max. document size code: 0x06
[microtek] Max. document size:  8299 x 13499 pixels
[microtek] Frame units:  pixels  1/8"'s
[microtek] # of built-in halftones: 12   Downloadable patterns? Yes
[microtek] Contrast Settings: 14   Exposure Settings: 74
[microtek] Adjustable Shadow/Highlight? yes   Adjustable Midtone? yes
[microtek] Digital brightness/offset? yes
[microtek] Gamma Table Size: 4096 entries of 2 bytes (max. depth: 12)
[microtek] ===== Source Options...
[microtek] Feed type:  flatbed    ADF support? yes
[microtek] Document Feeder Support? yes   Feeder Backtracking? yes
[microtek] Feeder Installed? no           Feeder Ready? no
[microtek] Transparency Adapter Installed? yes
[microtek] Fast Color Prescan? no
[microtek] Selectable Transfer Format? no
[microtek] Color Transfer Sequence: line-by-line, non-sequential with headers
[microtek] Three pass scan support? no
[microtek] ModeSelect-1 and ModeSense-1 Support? yes
[microtek] Can Disable Linearization Table? no
[microtek] Can Disable Start-of-Scan Recalibration? no
[microtek] Internal expanded expansion? no
[microtek] ====== End of Scanner Inquiry Report =======
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_open: device name /dev/scanner is not valid
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:9 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:9
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 9 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:10 src_size:8192 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:8192
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 8192 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:11 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:11
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 11 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:10 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:10
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 10 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:6 isWrite:0
[sanei_scsi] isRead dst_size:6
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 6 bytes
[sanei_scsi] taskStatus = 0x00000002
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Transferred 0 bytes
scanimage: sane_start: Error during device I/O
--
"The truth is an offense, but not a sin"
Werner Randelshofer
2011-07-22 12:48:59 UTC
Permalink
I have sent now the report to mtek-***@mir.com.

Thank you for your help!
-Werner
Post by m. allan noah
Well, according to the debug message, this model is untested. Perhaps
you can email the author as directed?
allan
Loading...