Re: [SLE] usbdevfs needed for Microtek scanner install/setup???

On Fri, 27 Jan 2006 13:44:36 +0100 (CET) Johannes Meixner wrote:

Hello,

On Jan 27 07:24 ken wrote (shortened):

...

On Thu, 26 Jan 2006 16:29:48 +0100 (CET) Johannes Meixner wrote:

...

But you can test "scanimage -L" the same way: For example what results

export SANE_DEBUG_DLL=4 export SANE_DEBUG_EPSON=128 export SANE_DEBUG_SANEI_USB=128 scanimage -L && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB unset SANE_DEBUG_EPSON unset SANE_DEBUG_DLL

Thank you for that. Just to make cutting and pasting easier and the output cleaner, I put these command on one line:

# export SANE_DEBUG_DLL=4; export SANE_DEBUG_EPSON=128; \ export SANE_DEBUG_SANEI_USB=128; \ scanimage -L && echo OK || echo FAILED; unset SANE_DEBUG_SANEI_USB; \ unset SANE_DEBUG_EPSON; unset SANE_DEBUG_DLL

Sorry, I made a copy&paste error from my own test.

For you it is of course SANE_DEBUG_MICROTEK2 (see the man page for the microtek2 backend) and not SANE_DEBUG_EPSON which I used for my scanner.

Therefore do:

export SANE_DEBUG_DLL=4 export SANE_DEBUG_MICROTEK2=255 export SANE_DEBUG_SANEI_USB=128 scanimage -L && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB unset SANE_DEBUG_MICROTEK2 unset SANE_DEBUG_DLL

export SANE_DEBUG_MICROTEK2=255; \ export SANE_DEBUG_SANEI_USB=128; \ scanimage -L && echo OK || echo FAILED; \ unset SANE_DEBUG_SANEI_USB; \ unset SANE_DEBUG_MICROTEK2; \ unset SANE_DEBUG_DLL [sanei_debug] Setting debug level of dll to 4. [dll] sane_init: SANE dll backend version 1.0.11 from sane-backends 1.0.15 [dll] add_backend: adding backend `microtek2' [dll] sane_get_devices [dll] load: searching backend `microtek2' in `/usr/lib/fglrx/lib:/usr/lib/sane'[dll] load: trying to load `/usr/lib/fglrx/lib/libsane-microtek2.so.1' [dll] load: couldn't open `/usr/lib/fglrx/lib/libsane-microtek2.so.1' (No such file or directory) [dll] load: trying to load `/usr/lib/sane/libsane-microtek2.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-microtek2.so.1' [dll] init: initializing backend `microtek2' [sanei_debug] Setting debug level of microtek2 to 255. [microtek2] sane_init: Microtek2 (v0.96 build 200410042220) says hello... [microtek2] parse_config_file: fp=0x8052468 [microtek2] parse_config_file: read line: # See sane-microtek2(5) for a description of the options [microtek2] parse_config_file: read line: [microtek2] parse_config_file: read line: option dump 1 [microtek2] parse_config_file: found global option option dump 1 [microtek2] parse_config_file: read line: #option strip-height 14.0 [microtek2] parse_config_file: read line: option no-backtrack-option on [microtek2] parse_config_file: found global option option no-backtrack-option on [microtek2] parse_config_file: read line: option

# export SANE_DEBUG_DLL=4;\ lightlid-35 on [microtek2] parse_config_file: found global option option lightlid-35 on [microtek2] parse_config_file: read line: option toggle-lamp on [microtek2] parse_config_file: found global option option toggle-lamp on [microtek2] parse_config_file: read line: option lineart-autoadjust on [microtek2] parse_config_file: found global option option lineart-autoadjust on[microtek2] parse_config_file: read line: option backend-calibration on [microtek2] parse_config_file: found global option option backend-calibration on [microtek2] parse_config_file: read line: #option colorbalance-adjust on [microtek2] parse_config_file: read line: scsi * * Scanner [microtek2] parse_config_file: found device scsi * * Scanner [microtek2] add_device_list: device='/dev/scanner' [microtek2] add_device_list: md=0x8052600, malloc'd 5236 bytes [microtek2] free hdev at 0x8052468 [microtek2] attach: device='/dev/scanner' [microtek2] scsi_inquiry: mi=0x8052604, device='/dev/scanner' [microtek2] scsi_inquiry: 'Invalid argument' [microtek2] attach: 'Invalid argument' [dll] init: backend `microtek2' is version 1.0.0 [microtek2] sane_get_devices: local_only=0 [microtek2] sane_get_devices: sd_list=0x8052178, malloc'd 8 bytes [microtek2] attach: device='/dev/scanner' [microtek2] scsi_inquiry: mi=0x8052604, device='/dev/scanner' [microtek2] scsi_inquiry: 'Invalid argument' [microtek2] attach: 'Invalid argument' [microtek2] sane_get_devices: attach status 'Invalid argument' [dll] sane_get_devices: found 0 devices 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). [dll] sane_exit: exiting [dll] sane_exit: calling backend `microtek2's exit function [microtek2] sane_exit: [microtek2] free md_first_dev at 0x8052600 [microtek2] sane_get_devices: local_only=0 [microtek2] free sd_list at 0x8052178 [microtek2] sane_get_devices: sd_list_freed [microtek2] sane_exit: MICROTEK2 says goodbye. [dll] sane_exit: finished OK

I expect that the microtek2 backend is loaded and executed successfully but you will see only SCSI reledted tests from the backend but no USB stuff which would show you that this backend doesn't do anything regarding USB and therefore your scanner won't work via USB (but via SCSI). Of course you could inspect the sources to be 100% sure but I prefer first of all using user-level tools.

Seems it's wanting to talk to /dev/scanner, but /dev/scanner is saying no. And since it's a scsi_inquiry, it wouldn't help to ln -s /dev/usb/scanner0 /dev/scanner ... or would it? Or should/could I alter the entry in /etc/sane.d/microtek2.conf ?? i.e., scsi * * Scanner

Why can't you simply use the SCSI host adapter with which it had worked before?

I don't have a SCSI port on my laptop. :)

As far as I know some older SCSI host adapters are no longer supported but I am no SCSI expert so that I cannot help you with SCSI questions.

The machine with the (perfectly good) SCSI adapter blew a hard drive last week. I needed to scan a dozen documents and thought it would be simpler and easier to get the scanner working on the laptop than to rebuild the broken machine.

...

This tells me that scanimage was able to find a dynamic library file corresponding to the "backend" but was (still) not able to find a "device" (I think in this instance a device *file* like /dev/usb/scanner0, yes?).

Exactly. With "export SANE_DEBUG_MICROTEK2=255" you would additionally see the debug output of the microtek2 backend.

Yeah, that's cool. Up to a point, I much prefer too much debugging output over too little. Really helps narrow down the problem. Best again, ken -- "This world ain't big enough for the both of us," said the big noema to the little noema.