Hi Henning, I've got a mustek bearpawn 2448 cs plus scanner attached to the usb port. But it does not work.
I'm running a debian/testing system with - 2.6.7-smp linux kernel - sane 1.0.15-2 - libusb-0.1-4 The scanner is recognized by the first sane-find-scanner and the first scanimage -L. But scanimage > /tmp/foo fails and from there on scanimage -L too. Here's some output: the first scanimage -L device `gt68xx:libusb:002:013' is a Mustek Bearpaw 2448 CS Plus flatbed scanner scanimage > /tmp/foo with SANE_GT68XX=255 <snipped some> [gt68xx] sane_init: config file line 110: trying to attach `usb 0x055f 0x021a' [gt68xx] attach: start: devp != NULL, may_wait = 0 [gt68xx] attach: trying to open device `libusb:002:014' [gt68xx] gt68xx_device_new: enter [gt68xx] gt68xx_device_new:: leave: ok [gt68xx] gt68xx_device_open: enter: dev=0x8052608 [gt68xx] gt68xx_device_open: leave: ok [gt68xx] attach: device `libusb:002:014' successfully opened [gt68xx] attach: found Mustek flatbed scanner BearPaw 2448 TA Plus at libusb:002:014 [gt68xx] gt68xx_device_close: enter: dev=0x8052608 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] attach: exit [gt68xx] sane_init: config file line 111: ignoring empty line [gt68xx] sane_init: config file line 112: ignoring comment line [gt68xx] sane_init: device mustek-bearpaw-2448-ta-plus: model name set to Bearpaw 2448 CS Plus <snipped some> [gt68xx] gt68xx_device_memory_write: dev=0x8052608, addr=0x1f80, size=0x40, data=0xbfffab30 [gt68xx] gt68xx_device_memory_read: dev=0x8052608, addr=0x1f80, size=0x40, data=0xbfffaaf0 [gt68xx] gt68xx_device_generic_req: command=0x69 [gt68xx] >> 69 01 c0 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 69 1a 02 5f 05 16 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] gt68xx_device_generic_req: command=0x2e [gt68xx] >> 2e 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 2e 1a 02 5f 05 16 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] get_id: vendor id=0x021A, product id=0x055F, DID=0x00010016, FID=0x0000 [gt68xx] gt68xx_device_generic_req: command=0x41 [gt68xx] >> 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 [gt68xx] gt68xx_device_generic_req: reading response failed: Invalid argument [gt68xx] somewhere: gt68xx_device_stop_scan (dev): Invalid argument scanimage: open of device gt68xx:libusb:002:014 failed: Invalid argument [dll] sane_exit: exiting [dll] sane_exit: calling backend `gt68xx's exit function [gt68xx] sane_exit: start [gt68xx] gt68xx_device_free: enter: dev=0x8052608 [gt68xx] gt68xx_device_close: enter: dev=0x8052608 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] gt68xx_device_free: freeing dev [gt68xx] gt68xx_device_free: leave: ok [gt68xx] sane_exit: exit [dll] sane_exit: finished dmesg says: usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 len 8 ret -110 usb 2-2: control timeout on ep0out What's going on here? Micha. -- -- Michael Daum -- Natural Language Systems -- Department of Informatics ---University of Hamburg -- http://nats-www.informatik.uni-hamburg.de/~micha
