[sane-devel] Lost with udev and sane

[John Coppens]

Hello people.

A couple of days ago, I needed my Snapscan scanner again, after a long
while of disuse and found that it isn't recognized anymore. A while ago I
had to install a newer version of udev for another reason, so this could
be the reason, or, worse, a couple of days ago, a utility transformer
blew up nearby, and I just finished repairing UPS, phone, fax and other
equipment.

So, I tried the following:

1) scanimage -L (no detection at all)
2) sane-find-scanner -q at first didn't detect anything either, till I
   modified the rule file slightly (see below). Now it says:
root at on6jc /etc/udev/rules.d$ sane-find-scanner -q
found USB scanner (UNKNOWN vendor and product) at device /dev/usb/scanner

3) I noticed that no scanner device was generated at all, but lots of
dynamic devices which weren't recognized by 1) or 2). I added

, SYMLINK="usb/scanner" to the rule for my scanner (Snapscan 1212U_2)

and found that the link appeared correctly, confirming that the rule file
was really being used.

4) /dev/usb$ udevinfo -a -p $(udevinfo -q path -n /dev/usb/scanner) gives:

  looking at parent device '/devices/pci0000:00/0000:00:0b.0/usb1/1-5':
    KERNELS=="1-5"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{product}=="SNAPSCAN"
    ATTRS{manufacturer}=="AGFA "
    ATTRS{quirks}=="0x1"
    ATTRS{maxchild}=="0"
    ATTRS{version}==" 1.00"
    ATTRS{devnum}=="8"
    ATTRS{busnum}=="1"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="ff"
    ATTRS{bDeviceSubClass}=="ff"
    ATTRS{bDeviceClass}=="ff"
    ATTRS{bcdDevice}=="0100"
    ATTRS{idProduct}=="2061"
    ATTRS{idVendor}=="06bd"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{bmAttributes}=="40"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{configuration}==""
    ATTRS{dev}=="189:7"

5) Checked that the firmware was available, and the firmware command set
in snapscan.conf

6) with DEBUG level set to 255, I get:

[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.53
[snapscan] add_usb_device(/dev/usb/scanner bus=usb)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(/dev/usb/scanner)
[snapscan] snapscani_check_device()
[snapscan] mini_inquiry
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 (36))
[snapscan] atomic_usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 (36))
[snapscan] usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 (36))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x12 0x00 0x00 0x00 0x24 0x00
[snapscan] usb_write Only 0 bytes written
[snapscan] Written 0 bytes
[snapscan] mini_inquiry: snapscan_cmd command failed: Error during device
I/O [snapscan] snapscani_check_device: mini_inquiry failed with Error
during device I/O. [snapscan] snapscani_usb_close(0)
[snapscan] 1st read 0 write 0
[snapscan] sane_snapscan_get_devices (0xbfe533a8, 0)
device `v4l:/dev/video0' is a Noname LifeView/Typhoon FlyVIDEO2000
virtual device [snapscan] sane_snapscan_exit


Which seems all correct (and gives me hope the scanner is still alive)

Can anyone suggest what else to try?

Thanks,
John