sane-backends' versions Reply-To:
I'm using an Epson CX-3200 all-in-one/MFP (usb printer+scanner+photocopier), when "usblp" kernel module is loaded the scanner part is not detected (not even by root, but anyway it isn't a matter of permissions) by xsane and scanimage, and obviously it doesn't work. I tried sane-backends-1.0.16 and sane today snapshot (September 22nd), libusb-0.1.8 and 0.1.10a, with Gentoo and Slackware, both with kernel 2.6.13 (vanilla). "epson" is uncommented in dll.conf and right device id has been written in epson.conf. sane-find-scanner gives me this message: "[..] found USB scanner (vendor=0x04b8 [EPSON], product=0x0802 [USB MFP]) at libusb:001:010 [??]" scanimage -L : "No scanners were identified.[..]" lsusb : "[..] Bus 001 Device 010: ID 04b8:0802 Seiko Epson Corp. Stylus CX3200 [..]" xsane gives me about this message (it's in Italian language): No available device. in /var/log/messages and /var/log/syslog I've such messages: " Sep 22 23:00:17 xxxx usb 1-1: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 ep 22 23:19:09 xxxx usb 1-1: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1 Sep 22 23:26:13 xxxx usb 1-1: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 " SANE_EPSON_DEBUG=255 scanimage : " [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.0.16-cvs [epson] sane_init, ># epson.conf< [epson] sane_init, >#< [epson] sane_init, ># here are some examples for how to configure the EPSON backend< [epson] sane_init, >#< [epson] sane_init, ># SCSI scanner:< [epson] sane_init, >#scsi EPSON< [epson] sane_init, ># for the GT-6500, comment out the previous line and uncomment the following line:< [epson] sane_init, >#scsi< [epson] sane_init, >#< [epson] sane_init, ># Parallel port scanner:< [epson] sane_init, >#pio 0x278< [epson] sane_init, >#pio 0x378< [epson] sane_init, >#pio 0x3BC< [epson] sane_init, >#< [epson] sane_init, ># USB scanner:< [epson] sane_init, ># There are two different methods of configuring a USB scanner: libusb and the kernel module< [epson] sane_init, ># For any system with libusb support (which is pretty much any recent Linux distribution) the< [epson] sane_init, ># following line is sufficient. This however assumes that the connected scanner (or to be more< [epson] sane_init, ># accurate, it's device ID) is known to the backend.< [epson] sane_init, >#usb< [epson] sane_init, ># For libusb support for unknown scanners use the following command< [epson] sane_init, ># usb <product ID> <device ID>< [epson] sane_init, ># e.g.:< [epson] sane_init, ># usb 0x4b8 0x110< [epson] sane_init, ># And for the scanner module, use the following configuration:< [epson] sane_init, >#usb /dev/usbscanner0< [epson] sane_init, >#usb /dev/usb/scanner0< [epson] sane_init, >usb 0x4b8 0x802< [epson] attach_one_usb(libusb:001:010) [epson] SANE Epson Backend v0.2.45 - 2000-01-09 [epson] attach(libusb:001:010, 3) [epson] attach: opening libusb:001:010 [epson] sane_get_devices() scanimage: no SANE devices found " If I remove "usblp" module (with rmmod), the scanner got recognized and working, but it is only a workaround: scanimage -L : "device `epson:libusb:001:010' is a Epson CC-570L flatbed scanner" and xsane starts smoothly I suppose there is a problem with printer part that monopolizes all. BTW I've found a SUSE user's post on http://forums.suselinuxsupport.de/index.php?s=ea9dc99f955913e529b5 d2c7e1eb61a8&showtopic=19054&pid=109816&st=0&#entry109816 (one URL), regarding a similar problem with another MFP. He says: <<Seems that usb_set_configuration in sanei_usb.c was causing the failure since usblp had already set it. Commenting out the function and recompiling SANE allowed the interface to be claimed without problem. Xsane and Kooka are now happy.>> Thank you. -- GNU/Linux - Slackware current - 2.6.13 GNU/Linux - Gentoo testing - 2.6.13-vanilla LRU #210970 LRM #98222 (Slackware-RU #12583) diffida dell'hardware inaffidabile: www.no1984.org
