fsavigny
n00b
Joined: 08 Sep 2012
Posts: 24
|
 Posted: Sat Sep 08, 2012 6:18 pm Post subject: Scanner found by sane-find-scanner, but not scanimage -L |
 |
|
I have bought quite an old Avision AV500U Scanner (which the dealer claims is an AV600U).
According to http://www.sane-project.org/sane-mfgs.html#Z-AVISION, the AV600U is supported.
According to http://sane-project.meier-geinitz.de/lists/sane-mfgs-cvs.html#AVISION, it is untested.
Neither of the two pages even lists the AV500U, whether as unsupported or supported.
I am now somewhat disoriented about how to find out whether this scanner works with sane or not.
On the one hand:
| Code: | > sane-find-scanner
...
found USB scanner (vendor=0x0638, product=0x0a1e) at libusb:005:003
...
|
But:
| Code: | > scanimage -L
No scanners were identified. ...
|
What is surprising, however, is that the proprietary VueScan program, which lists the both the AV500U and the AV600U as supported (see http://www.hamrick.com/vuescan/vuescan.htm#avision) does not find a scanner either, which makes me doubt the idea that the fact could simply be due to the AV500U's not being supported. (Because then, VueScan should find it, shouldn't it?)
What probably reflects the fact that sane-find-scanner detects the scanner is that when it is switched on, a new entry in the /sys/ hierarchy is created:
| Code: | | /sys/bus/usb/devices/6-1 -> ../../../devices/pci0000:00/0000:00:1d.1/usb6/6-1 |
This 6-1 directory contains a bunch of information:
| Code: |
> tree /sys/devices/pci0000:00/0000:00:1d.1/usb6/
[this is a part of the output]
|-- 6-1
| |-- authorized
| |-- avoid_reset_quirk
| |-- bConfigurationValue
| |-- bDeviceClass
| |-- bDeviceProtocol
| |-- bDeviceSubClass
| |-- bMaxPacketSize0
| |-- bMaxPower
| |-- bNumConfigurations
| |-- bNumInterfaces
| |-- bcdDevice
| |-- bmAttributes
| |-- busnum
| |-- configuration
| |-- descriptors
| |-- dev
| |-- devnum
| |-- devpath
| |-- driver -> ../../../../../bus/usb/drivers/usb
| |-- ep_00
| | |-- bEndpointAddress
| | |-- bInterval
| | |-- bLength
| | |-- bmAttributes
| | |-- direction
| | |-- interval
| | |-- power
| | |-- type
| | |-- uevent
| | `-- wMaxPacketSize
| |-- idProduct
| |-- idVendor
| |-- maxchild
| |-- power
| | `-- persist
| |-- product
| |-- quirks
| |-- remove
| |-- speed
| |-- subsystem -> ../../../../../bus/usb
| |-- uevent
| |-- urbnum
|
When the scanner is switched off, the whole directory disappears. The information in "idProduct" and "idVendor" is exactly the same as the one that sane-find-scanner reports.
What does NOT happen, however, is that udev creates a device file. I have tried to prod it to doing this, by copying /lib/udev/rules.d/41-libsane.rules to /etc/udev/rules.d/41-libsane.rules, deleting most of the file contents, creating an entry using the Vendor and Product Ids I had found, and leaving only (most comments left out):
| Code: |
ACTION!="add", GOTO="libsane_rules_end"
ENV{DEVTYPE}=="usb_device", GOTO="libsane_create_usb_dev"
# SUBSYSTEMS=="scsi", GOTO="libsane_scsi_rules_begin"
SUBSYSTEM=="usb_device", GOTO="libsane_usb_rules_begin"
SUBSYSTEM!="usb_device", GOTO="libsane_usb_rules_end"
# Kernel >= 2.6.22 jumps here
LABEL="libsane_create_usb_dev"
# For Linux >= 2.6.22 without CONFIG_USB_DEVICE_CLASS=y
# this is indeed "not set" in my kernel config
# If the following rule does not exist on your system yet, uncomment it
# (I did that:)
ENV{DEVTYPE}=="usb_device", MODE="0664", OWNER="root", GROUP="root"
# Kernel < 2.6.22 jumps here
LABEL="libsane_usb_rules_begin"
# Avision AV500U
ATTRS{idVendor}=="0638", ATTRS{idProduct}=="0a1e", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
LABEL="libsane_usb_rules_end"
LABEL="libsane_rules_end"
|
This has not done the trick, however.
Can anybody suggest to me how to proceed? My suspiscion is that the problem has to do with the missing device file, but is that correct, and how can I get udev to create one? (I have created a udev rule before, but that was without understanding anything about it. Things haven't improved in that respect.  )
Thanks so much for any help!
Florian |
|
Kernel & Hardware
