[sane-devel] scaner on HP LaserJet M1005 MFP

[m. allan noah]

2010/4/7 viktor vraniak <tyctor at post.cz>:
> ok first mail with attached log seems not be delivered
> so here is different part:
>
> first 89lines are same:
> [sanei_debug] Setting debug level of hpljm1005 to 255.
> [sanei_debug] Setting debug level of sanei_usb to 255.
> [sanei_usb] sanei_usb_init: marking existing devices
> [sanei_usb] sanei_usb_init: Looking for kernel scanner devices
> [sanei_usb] sanei_usb_init: Looking for libusb devices
> usb_set_debug: Setting debugging level to 255 (on)
> usb_os_find_busses: Found 001
> usb_os_find_busses: Found 004
> usb_os_find_busses: Found 002
> usb_os_find_busses: Found 003
> usb_os_find_busses: Found 005
> usb_os_find_devices: Found scanner0 on 001
> error obtaining child information: Inappropriate ioctl for device
> usb_os_find_devices: couldn't get connect info
> usb_os_find_devices: Found scanner0 on 004
> error obtaining child information: Operation not permitted
> usb_os_find_devices: couldn't get connect info
> usb_os_find_devices: Found scanner0 on 002
> error obtaining child information: Operation not permitted
> usb_os_find_devices: couldn't get connect info
> usb_os_find_devices: Found scanner0 on 003
> error obtaining child information: Operation not permitted
> usb_os_find_devices: couldn't get connect info
> usb_os_find_devices: Found scanner0 on 005
> error obtaining child information: Operation not permitted
> [sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x3b17) interface 0  at libusb:001:scanner0
> [sanei_usb] store_device: add dn 0 with libusb:001:scanner0
> [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: device 0x0686/0x3009, interface 0 doesn't look like a scanner (0/7)
> [sanei_usb] sanei_usb_init: device 0x0686/0x3009: 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 1 devices
> [sanei_usb] sanei_usb_init: device 00 is libusb:001:scanner0
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x3b17
> [hpljm1005] New device found: libusb:001:scanner0
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x5617
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x5717
> [hpljm1005] Found device libusb:001:scanner0
> [sanei_usb] sanei_usb_open: trying to open device `libusb:001:scanner0'
> USB error: could not set config 1: Device or resource busy
> [sanei_usb] sanei_usb_open: libusb complained: could not set config 1: Device or resource busy
> [sanei_usb] Maybe the kernel scanner driver or usblp claims the interface? Ignoring this error...
> [sanei_usb] sanei_usb_open: configuration nr: 0
> [sanei_usb] sanei_usb_open:     interface nr: 0
> [sanei_usb] sanei_usb_open:   alt_setting nr: 0
> [sanei_usb] sanei_usb_open: endpoint nr: 0
> [sanei_usb] sanei_usb_open: direction: 0
> [sanei_usb] sanei_usb_open: address: 1 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 0x01)
> [sanei_usb] sanei_usb_open: endpoint nr: 1
> [sanei_usb] sanei_usb_open: direction: 128
> [sanei_usb] sanei_usb_open: address: 1 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 0x01)
> [sanei_usb] sanei_usb_open: endpoint nr: 2
> [sanei_usb] sanei_usb_open: direction: 128
> [sanei_usb] sanei_usb_open: address: 3 transfertype: 3
> [sanei_usb] sanei_usb_open: found interrupt-in endpoint (address 0x03)
> [sanei_usb] sanei_usb_open: configuration nr: 0
> [sanei_usb] sanei_usb_open:     interface nr: 1
> [sanei_usb] sanei_usb_open:   alt_setting nr: 0
> [sanei_usb] sanei_usb_open: endpoint nr: 0
> [sanei_usb] sanei_usb_open: direction: 0
> [sanei_usb] sanei_usb_open: address: 2 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 0x02)
> [sanei_usb] sanei_usb_open: we already have a bulk-out endpoint (address: 0x01), ignoring the new one
> [sanei_usb] sanei_usb_open: endpoint nr: 1
> [sanei_usb] sanei_usb_open: direction: 128
> [sanei_usb] sanei_usb_open: address: 2 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 0x02)
> [sanei_usb] sanei_usb_open: we already have a bulk-in endpoint (address: 0x81), ignoring the new one
> [sanei_usb] sanei_usb_open: opened usb device `libusb:001:scanner0' (*dn=0)
> scanimage: rounded value of br-x from 220 to 220
> scanimage: rounded value of br-y from 330 to 330
> [hpljm1005] Sending packet 21, next data size 0, device libusb:001:scanner0
> [sanei_usb] sanei_usb_write_bulk: trying to write 32 bytes
> [sanei_usb] 000 41 53 50 01 00 00 00 15 00 00 00 00 00 00 00 00 ASP.............
> [sanei_usb] 010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [sanei_usb] sanei_usb_write_bulk: wanted 32 bytes, wrote 32 bytes
> [hpljm1005] Sending packet 0, next data size 0, device libusb:001:scanner0
> [sanei_usb] sanei_usb_write_bulk: trying to write 32 bytes
> [sanei_usb] 000 41 53 50 01 00 00 00 00 00 00 00 00 00 00 00 00 ASP.............
> [sanei_usb] 010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [sanei_usb] sanei_usb_write_bulk: wanted 32 bytes, wrote 32 bytes
> [hpljm1005] Waiting scanner answer on device libusb:001:scanner0
> [sanei_usb] sanei_usb_read_bulk: trying to read 32 bytes
>
>
> after lines are different:
> if scanimage hangs, theese lines occurs in log:
>
> [sanei_usb] sanei_usb_read_bulk: read failed: No such device
> USB error: could not clear/halt ep 129: No such device
> [sanei_usb] sanei_usb_read_bulk: trying to read 32 bytes
> USB error: error submitting URB: No such device
>
>
> if scanimage is OK, theese lines occurs in log:
>
> [sanei_usb] 000 41 53 50 01 00 00 00 00 00 00 00 00 00 00 00 00 ASP.............
> [sanei_usb] 010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [sanei_usb] sanei_usb_read_bulk: wanted 32 bytes, got 32 bytes
> [hpljm1005] Sending packet 6, next data size 0, device libusb:001:scanner0
> [sanei_usb] sanei_usb_write_bulk: trying to write 32 bytes
> [sanei_usb] 000 41 53 50 01 00 00 00 06 00 00 00 00 00 00 00 00 ASP.............
> [sanei_usb] 010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [sanei_usb] sanei_usb_write_bulk: wanted 32 bytes, wrote 32 bytes
> [hpljm1005] Waiting scanner answer on device libusb:001:scanner0
> [sanei_usb] sanei_usb_read_bulk: trying to read 32 bytes
> ....
> and so on
>
> so i think, opened device is renewed and scanimage lost/not get descriptor for new device?

Yes- It appears that the device is reset (either by the kernel or by
itself), after this attempted write. The reset succeeds, and so the
device is found by the second call to scanimage.

does a long-running frontend like xsane exhibit this behaviour? What
about the -b argument to scanimage (should make multiple scans)

allan
-- 
"The truth is an offense, but not a sin"