Did you add your device to /etc/usbmgr/usbmgr.conf (I think that is the file, there is a device configuation in there somewhere). If you don't, the usbmgr software will cause you no end of headache trying to get this to work. I had this problem with my 1240U and after adding the proper line to the configuration file for usbmgr and restarting usbmgr, everything worked fine (I also unplug the usb cable and replugged it in after doing this to make usbmgr see the device again). You will need to rmmod scanner to make that work. If this doesn't give you enough, I could try looking when I boot my system up again later this evening and send a little more information. I got most of this from the special SuSE FAQ on the www.freecolormanagement.com site. On Wed, 5 Sep 2001, Farrell, Thomas wrote:
Hi!,
I have reached my wits end attempting to get my USB scanner working. I would greatly appreciate assistance.
I have a Soyo 5EHM, with the lastest BIOS revision, which has an ETEQ chipset (remarked VIA MVP3, revision CE). The lspci section lists it as follows: 00:07.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 02). I have used the recommended BIOS settings from the USBman website w/o success. I have verified everythings properly connected to the board and started the system from a cold boot with everything turned on.
The scanner itself is an Epson Perfection 636U.
I am running SuSE 7.2 with kernel 2.4.4-4GB (stock) with the followinng packages installed: sane-1.0.4-79, xsane-0.74-32, and usb-0.6-7. It's an old install that's been upgraded several times but so far no joy on any USB devices.
Some general info:
alice:~/logs # ls -l /dev/usbscanner lrwxrwxrwx 1 root root 16 Sep 4 19:27 /dev/usbscanner -> /dev/usbscanner0 alice:~/logs # ls -l /dev/usbscanner0 crw-rw-rw- 1 root root 180, 48 Sep 4 19:27 /dev/usbscanner0
alice:~/logs # more /etc/sane.d/epson.conf # here are examples for how to configure the EPSON backend #scsi EPSON # option color_correction 1 2 3 4 5 6 7 8 9 # #pio 0x278 #pio 0x378 #pio 0x3BC #scsi EPSON #/dev/scanner usb /dev/usbscanner0
/etc/sane.d/dll.conf has all driver but 'epson' entries commented out as recommended by the backend maintainer. I tried the epson backend shipped with SuSE 7.2 and the latest from the maintainer.
alice:~/logs # cat /proc/bus/usb/drivers usbdevfs hub ibmcam 48- 63: usbscanner
I have tried loading the scanner module with vendor ID & product ID as well as without them. I get the same results.
alice:~/logs # cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=d400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
xscanimage epson:/dev/usbscanner0 results in:
strace producing: open("/dev/usbscanner0", O_RDWR|O_EXCL) = -1 ENODEV (No such device)
AND
/var/log/messages producing: Sep 5 09:07:25 alice kernel: scanner.c: open_scanner(0): Unable to access minor data
I can produce the same errors by changing all references to /dev/usbscanner0 to /dev/usbscanner and the errors produced change accordingly.
Any suggestions?
Thanks in advance, Thom ------------------------------------------------------------------- Common sense is what tells you the earth is flat. -------------------------------------------------------------------