I recently upgraded from Kubuntu 6.10 to 7.04. I have an Acer 640u scanner attached to my computer which worked with Sane under Kubuntu 6.10. when I installed 7.04, sane would not detect the scanner, either as root nor as a user. I have copied the firmware to my /usr/share/sane/snapscan folder and modified the /etc/sane.d/snapscan.conf file, using the same firmware which worked under 6.10.

As I was looking for the culpret, I noticed that there is no scanner in the /dev directory in any form (usbscanner, scanner0, usb/scanner, etc). sane-find-scanner correctly identifies my scanner and shows it at libusb 001:006. In the /etc/udev/rules.d/60-sane rules (something like that, I'm at work right now) it has a listing for my snapscan scanner, but it does not appear to be creating a device.

Should I edit the rule in udev? I dont' even remember if udev created at device in my old version or not.

TIA

Goog

Is /proc/bus/usb mounted? As far as I remember, libusb does not use /dev.

Yes, /proc/bus/usb is mounted.

I created just a script that runs
xsane <driver>:$(sane-find-scanner | grep <model> | sed -e 's/.* at //')
If you specify USB address explicitly xsane starts.

is the <driver> argument the .bin file or the backend?

I appreciate the help I'm getting, but still unclear about why it no longer works in Kubuntu 7.04. Was there a change in libusb?

Goog

<driver> is backend name, like gt68xx for me. Maybe they ruined something in xsane..

I tried this by finding the scanner first with sane-find-scanner, then running the command:

xsane snapscan:libusb:002:008

The command returned with "Failed to open device 'snapscan:libusb:002:008' Invalid Argument.

Goog

Hm.. Try 'strace -f -o xsane.strace xsane snapscan:libusb:002:008' and post xsane.strace . Also try unloading ehci_hcd and ohci_hcd and loading uhci_hcd before plugging scanner.

The output is:

umovestr: Input/output error
umovestr: Input/output error
umovestr: Input/output error

Sane comes back with "Failed to open device 'snapscan:libusb:002:008': Invalid Argument.

It's got to be a libusb thing. Sane-find-scanner is finding the device, it recognizes it as snapscan, even if I dont' specify it, but it seems like sane doesn't like libusb as much as it does udev. The snapscan.conf has a line that you can edit to specify a device in the /dev directory.

Goog

I checked dmesg after running xsane and found this:


[ 202.552000] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann rqt 128 rq 6 len 2 ret -62

And if you run as root, what appears in dmesg and xsane.strace?

no dmesg output at all.

the xsane.strace file is INSANELY long (pardon the pun). Is there a particular line you are looking for in the output?

Goog

Well, at least it would be interesting to know what 'open()' was executed just before writing 'Failed to open' to output.