Hello Karl (and linux-usb), The following is a 'bug report' to advise of a possible issue that appears to have risen late in the 2.3 kernels and appears to continue in 2.4.0. I've an Epson Perfection 610 scanner (bought partially on the recommendation from your Epson Sane page - I agree that any company that actually encourages dissemination of their product information should be supported!) (that's not to imply any obligation on your part :-). I am running a 2.2.16 kernel, and have applied the 2.2 USB backport from SuSE (http://www.suse.cz/development/usb-backport/) - which is from what appears to be 2.4.0 (test2-pre2). I have a PIIX4 uhci USB controller, and have built usbcore, usb-uhci and scanner as modules. Everything seems to load correctly, the device is correctly identified. Unfortunately I'm experiencing what appears to be a known problem with at least some of the 2.3 kernels - usb_control/bulk_msg: timeout errors. This occurs with with sane's find-scanner program and even the simple bit of test code at the end of linux/src/Documentation/usb/scanner.txt (which basically opens the device and tries to write/read). The discussion at http://electricrain.com/lists/archive/linux-usb/2000/04/msg00573.html seems to match the symptoms I see. I have a slight twist in that eventually I get a 'NAK' msg: <all modules are loaded, I plug in the scanner> Jun 23 22:11:49 gromit kernel: usb.c: USB device number 2 default language ID 0x409 Jun 23 22:11:49 gromit kernel: Manufacturer: EPSON Jun 23 22:11:49 gromit kernel: Product: Perfection610 Jun 23 22:11:49 gromit kernel: usb.c: usbscanner driver claimed interface c2e57260 <fire up sane-1.0.2/tools/find-scanner -v /dev/usbscanner> Jun 23 22:12:05 gromit kernel: usb_control/bulk_msg: timeout Jun 23 22:12:45 gromit last message repeated 2 times Jun 23 22:13:45 gromit last message repeated 3 times Jun 23 22:14:45 gromit last message repeated 3 times Jun 23 22:15:45 gromit last message repeated 3 times Jun 23 22:15:45 gromit kernel: scanner.c: read_scanner(0): excessive NAK's received (I can turn debugging on if you like). I can't find a resolution to the problem discussed on linux-usb, I presume it is still an open issue? I'm very much a device driver novice, though have plenty of user-land coding experience. That is, I'm a bit out of my depth figuring out the scanner driver problem but would certainly be able to aid in any investigation... Regards, Ben Low --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
