3.9.8 brought a tiny improvement! scanimage -L now succesfully reports the scanner, but then hangs. I still can not scan with xsane however (no scanner device found) $ scanimage -L device `plustek:libusb:001:004' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner (hang, but eventually returns prompt after couple of minutes) Best regards Martin On Fri, May 24, 2013 at 2:49 PM, Martin van Es <mrvanes@xxxxxxxxx> wrote: > Is noone interested in taking this up with me? > > Martin > > On Mon, May 13, 2013 at 1:20 PM, Martin van Es <mrvanes@xxxxxxxxx> wrote: >> Hi, >> >> I have exactly the same problem as described by Harald Judt in this mail: >> http://www.spinics.net/lists/linux-usb/msg58841.html >> >> The thread ends here, in mid conversation with Sarah Sharp: >> http://www.spinics.net/lists/linux-usb/msg69636.html >> >> ... so I'd like to take it up from there. >> >> The scanner is a Canoscan N670U (LiDE 20). >> >> sane-fine-scanner finds the scanner: >> found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan]) >> at libusb:003:003 >> >> but scanimage -L fails (no output) >> >> The attached (3.9.2) kernel log is from boot, to supply all usb >> initialisation messages. >> Around 46.650933 I did the sane-find-scanner. >> Starting 60.438552 you see output of scanimage -L and 707.400622 again >> so it's isolated from possible noise. >> >> The scanner is fully functional on my old laptop with USB2 ports. >> >> Hope this helps resolving the bug. >> >> Best regards, >> Martin van Es >> -- >> If 'but' was any useful, it would be a logic operator -- If 'but' was any useful, it would be a logic operator -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
