[sane-devel] Linux-update: scanner no more recognized
Stef
stef.dev at free.fr
Fri Jul 27 19:18:38 UTC 2012
On 27/07/2012 21:11, M.B. Schiekel wrote:
> Am 27.07.2012 20:56, schrieb Stef:
>> now USB trouble in sight. I'm quite surprised there is no message
>> for sanei_usb_open() which is called from the UMAX_open_device() that
>> failed in your first message. What are the traces with:
>>
>> export SANE_DEBUG_UMAX1220U=128
>> export SANE_DEBUG_SANEI_USB=128
>> scanimage -L
>
> Hallo Stef,
>
> thank you for your help again. Here's the output. There's no
> sanei_usb_open() .
>
> Kind regards,
> bernhard
>
> -------------------------------------------------------------------
>
> export SANE_DEBUG_UMAX1220U=128
> export SANE_DEBUG_SANEI_USB=128
> scanimage -L
>
> [sanei_debug] Setting debug level of umax1220u to 128.
> [umax1220u] sane_init: version_code != 0, authorize != 0
> [umax1220u] sane_init: SANE umax1220u backend version 1.0.2 from
> sane-backends 1.0.22
> [sanei_debug] Setting debug level of sanei_usb to 128.
> [sanei_usb] sanei_usb_init: marking existing devices
> [sanei_usb] sanei_usb_init: Looking for kernel scanner devices
> [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory
> [sanei_usb] sanei_usb_init: Looking for libusb devices
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0002, interface 0 doesn't
> look like a scanner (9/9)
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0002: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001, interface 0 doesn't
> look like a scanner (9/9)
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x093a/0x2510, interface 0 doesn't
> look like a scanner (0/3)
> [sanei_usb] sanei_usb_init: device 0x093a/0x2510: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001, interface 0 doesn't
> look like a scanner (9/9)
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001, interface 0 doesn't
> look like a scanner (9/9)
> [sanei_usb] sanei_usb_init: device 0x1d6b/0x0001: no suitable interfaces
> [sanei_usb] sanei_usb_init: found 0 devices
> [umax1220u] reading configure file umax1220u.conf
> [umax1220u] attach_matching_devices(usb 0x1606 0x0010)
> [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010
> [umax1220u] attach_matching_devices(usb 0x1606 0x0030)
> [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030
> [umax1220u] attach_matching_devices(usb 0x1606 0x0130)
> [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0130
> [umax1220u] finished reading configure file
> [umax1220u] sane_get_devices(local_only = 0)
>
> 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).
> [umax1220u] sane_exit
>
>
Well, I am puzzled. why don't you get the traces you got the first
time:
[umax1220u] attach_scanner: libusb:003:002
[umax1220u] attach_scanner: opening libusb:003:002
[umax1220u] UMAX_open_device: `libusb:003:002'
[umax1220u] UMAX_open_device: couldn't open device `libusb:003:002':
Invalid argument
[umax1220u] ERROR: attach_scanner: opening libusb:003:002 failed
Any interesting messages with 'dmesg' ? Does 'lsusb' still list the scanner ?
Regards,
Stef
More information about the sane-devel
mailing list