Lost scanner (13.1)

kingbeowulf · 09-14-2010, 01:14 PM

In previous Slackware libsane releases, my scanner was not supported. In 13.1 the support is there:

root@gandalf:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:3304 Hewlett-Packard DeskJet 990c
Bus 002 Device 004: ID 04a7:0229 Visioneer OneTouch 7100
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@gandalf:~# sane-find-scanner
...
found USB scanner (vendor=0x04a7 [Visioneer], product=0x0229 [USB Scanner], chip=GL646) at libusb:002:004
...
root@gandalf:~# scanimage -L
device `genesys:libusb:002:004' is a Visioneer OneTouch 7100 flatbed scanner

On a new Slackware64 install, the scanner worked with Skanlite and xsane. I was so excited that a posted a snippet to the HCL on linuxquestions.org

Now, after a few /patches updates, the scanner stopped working. Scanlite and xsane find the scanner but can't scan. The scanner still scans in WinXP. Ive been all over the udev rules and elsewhere but don't see where the change occurred.

I tried with a "fresh" Slackware32 with the same results, but unfortunately I had already installed the /patches updates on that system.

The only 2 log messages are:
SYSLOG:
Sep 14 10:47:52 gandalf skanlite: io/hpmud/musb.c 2007: invalid usb_open: Permission denied

MESSAGES:
Sep 14 10:45:52 gandalf kernel: usb 2-3: new full speed USB device using ohci_hcd and address 4
Sep 14 10:45:52 gandalf kernel: usb 2-3: New USB device found, idVendor=04a7, idProduct=0229
Sep 14 10:45:52 gandalf kernel: usb 2-3: New USB device strings: Mfr=1, Product=3, SerialNumber=0
Sep 14 10:45:52 gandalf kernel: usb 2-3: Product: USB Scanner
Sep 14 10:45:52 gandalf kernel: usb 2-3: Manufacturer: Visioneer

Why am I suddenly getting "permission denied" both as root, and as the normal user (yes added to 'scanner' group)? What changed from the full DVD installation (using 2.6.33.4-generic and initrd) after added the the patches? I've been googling for months trying different "permission fixes" and fiddling with udev rules with no luck. So there is something I don't understand going on here.

Richard Cranium · 09-14-2010, 03:30 PM

If you run xsane on the command line, you should get a lot more errors. Or look in ~/.xsession-errors.

kingbeowulf · 09-14-2010, 07:18 PM

Quote:

Originally Posted by Richard Cranium

If you run xsane on the command line, you should get a lot more errors. Or look in ~/.xsession-errors.

nope, xsession-errors doesn't exist, no errors on the command line. Only the syslog error and a xsane pop up "Failed to start scanner: Error during device I/O"

Richard Cranium · 09-14-2010, 07:40 PM

Odd. When I do it as a non-root user that belongs to the plugdev and scanner groups, I get stuff like...

Code:

$ xsane
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/001/003: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/001/004: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/002: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/003: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/004: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/005: Permission denied.
libusb requires write access to USB device nodes.

...followed by some Gtk warnings and the xsane application. (/dev/bus/usb/001/002 appears to be my scanner. That character device belongs to the 'scanner' group.)

kingbeowulf · 09-16-2010, 09:00 PM

RC, thats just xsane running through all USB nodes, afaik. I get the same xsane message for each "root hub" but USB printer and USB scanner (and any other plugged in device) don't kick that error. (BTW, the scanner is not multifunction - I have separate USB devices for printer and flatbed scanner.) The USB printer has never given me any issues. Even got HPLIP status in Xfce so I can get ink levels. I was about to give up on the scanner and get a new one when it started working in a clean 13.1 install when slack 1st came out. I really don't have time to roll back all the updates since then - but i may try another clean install on another HD....

Richard Cranium · 09-16-2010, 11:41 PM

Aha. I should have read your first post more carefully.

Given your scanimage result, what does "ls -l /dev/bus/usb/002/004" give you?

On my machine, it gives....

Code:

# scanimage -L
device `hp5590:libusb:001:002' is a HP 5590 Workgroup scanner
# ls -al /dev/bus/usb/001/002 
crw-rw-r-- 1 root scanner 189, 1 2010-09-16 23:42 /dev/bus/usb/001/002

kingbeowulf · 09-18-2010, 12:05 AM

Same here,

Code:

# scanimage -L
device `genesys:libusb:002:003' is a Visioneer OneTouch 7100 flatbed scanner
# ls -l /dev/bus/usb/002/003
crw-rw-r-- 1 root scanner 189, 130 2010-09-16 23:29 /dev/bus/usb/002/003

allend · 09-18-2010, 01:27 AM

Check the backend library. On my Slackware64 install 'ls -l /usr/lib64/sane/libsane-genesys*' gives:

Code:

-rwxr-xr-x 1 root root    890 2010-04-30 14:22 /usr/lib64/sane/libsane-genesys.la*
lrwxrwxrwx 1 root root     25 2010-05-02 01:56 /usr/lib64/sane/libsane-genesys.so -> libsane-genesys.so.1.0.21*
lrwxrwxrwx 1 root root     25 2010-05-02 01:56 /usr/lib64/sane/libsane-genesys.so.1 -> libsane-genesys.so.1.0.21*
-rwxr-xr-x 1 root root 245888 2010-04-30 14:22 /usr/lib64/sane/libsane-genesys.so.1.0.21*

Also 'man sane-genesys' may provide a clue.

Richard Cranium · 09-18-2010, 03:07 AM

Quote:

Originally Posted by beowulf999

Same here,

Code:

# scanimage -L
device `genesys:libusb:002:003' is a Visioneer OneTouch 7100 flatbed scanner
# ls -l /dev/bus/usb/002/003
crw-rw-r-- 1 root scanner 189, 130 2010-09-16 23:29 /dev/bus/usb/002/003

Your user is in the scanner group, isn't it? Maybe you got the broken shadow update.