[sane-devel] Problems with Canon CanoScan FB630U

[gerard klaver]

On Tue, 2004-08-31 at 18:55, Johannes Bauer wrote:
> Hello List,
> 
> I wanted to report the troubles I have with the Canon CanoScan FB630U 
> (USB scanner). The software I installed is the following:
> 
> libusb 0.1.7
> sane-backends 1.0.14
> xsane 0.91
> 
> The scanner is detected alright by sane-find-scanner:
> 
> found USB scanner (vendor=0x04a9, product=0x2204 [CanoScan FB630U]) at 
> libusb:003:006
> 
> When doing a "scanimage -L" everything seems fine, too:
> 
> device `canon630u:libusb:003:006' is a CANON Canoscan FB630U flatbed scanner
> 
> Then, however (as root even):
> 
> # scanimage
> scanimage: sane_start: Device busy
> 
> A couple of messages appear in the kernel log:
> 
> ppdev0: registered pardevice
> ppdev0: unregistered pardevice
> usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 12 len 1 
> ret -71
> [ This message repeats about 50 times ]
> hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
> hub 3-0:1.0: over-current change on port 1
> usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 12 len 1 
> ret -71
> usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 12 len 1 
> ret -71
> usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 12 len 1 
> ret -71
> usb 3-1: USB disconnect, address 6
> usb 3-1: new full speed USB device using address 7
> 
> I did not, however disconnect/reconnect the device! Every time I do a 
> "scanimage", the device gets "relisted" and therefore the device address 
> is incremented by one.
> 
> Does anybody have a clue what this could all be about? I'd be very grateful.
> 
> Greetings,
> Johannes

try to update libusb to a 0.1.8 version first
-- 
----------
m.vr.gr.
Gerard Klaver