You are not logged in.
I have been using a fujitsu scan snap 300m with arch linux for over three years. It has always worked fine.
With the upgrade to linux 3.6.2, scanimage can no longer find the scanner. When calling scanimage, I get the following error:
[20:14]% scanimage --device epjitsu > out.pnm
scanimage: open of device epjitsu failed: Invalid argument
Was there a regression with the new kernel and usb peripherals or udev permissions?
Here are the details:
All other usb devices (including usb stick automounting) are working correctly.
The scanner is attached:
[20:14]% lsusb
Bus 001 Device 006: ID 04c5:117f Fujitsu, Ltd
Bus 001 Device 005: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 003 Device 002: ID 05b8:3155 Agiler, Inc.
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I have the firmware installed:
[20:13]% ls /usr/share/sane/epjitsu
300M_0B00.nal
/etc/sane.d/epjitsu.conf is correct:
# Fujitsu S300M
firmware /usr/share/sane/epjitsu/300M_0B00.nal
usb 0x04c5 0x117f
Permissions are correct in //lib/udev/rules.d/53-sane.rules
# Fujitsu ScanSnap S300M
ATTRS{idVendor}=="04c5", ATTRS{idProduct}=="117f", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"
Sane-find-scanner sees the scanner:
[20:15]% sane-find-scanner
[...]
found USB scanner (vendor=0x04c5 [FUJITSU], product=0x117f [ScanSnap S300M]) at libusb:001:006
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
[...]
I am a member of the group scanner:
[20:15]% groups
lp wheel network video audio storage scanner power users matt abs sbox
And here is what scanimage -L prints out:
[20:25]% scanimage -L
device `v4l:/dev/video0' is a Noname CNF7129 virtual device
Note running scanimage as root has the same result, so this does not seem to be a permissions issue.
What else am I missing?
Last edited by madalu (2012-10-19 13:01:18)
Offline
For further reference, here's what udevadmin reports:
[7:57]% udevadm monitor --env
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1246.177213] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3 (usb)
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/009
DEVNUM=009
DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-3
DEVTYPE=usb_device
MAJOR=189
MINOR=8
PRODUCT=4c5/117f/100
SEQNUM=1608
SUBSYSTEM=usb
TYPE=255/255/255
KERNEL[1246.178674] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v04C5p117Fd0100dcFFdscFFdpFFicFFiscFFipFFin00
PRODUCT=4c5/117f/100
SEQNUM=1609
SUBSYSTEM=usb
TYPE=255/255/255
UDEV [1246.199517] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3 (usb)
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/009
DEVNUM=009
DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-3
DEVTYPE=usb_device
ID_BUS=usb
ID_FOR_SEAT=usb-pci-0000_00_1d_7-usb-0_3
ID_MODEL=ScanSnap_S300M
ID_MODEL_ENC=ScanSnap\x20S300M
ID_MODEL_ID=117f
ID_PATH=pci-0000:00:1d.7-usb-0:3
ID_PATH_TAG=pci-0000_00_1d_7-usb-0_3
ID_REVISION=0100
ID_SERIAL=FUJITSU_ScanSnap_S300M
ID_USB_INTERFACES=:ffffff:
ID_VENDOR=FUJITSU
ID_VENDOR_ENC=FUJITSU
ID_VENDOR_ID=04c5
MAJOR=189
MINOR=8
PRODUCT=4c5/117f/100
SEQNUM=1608
SUBSYSTEM=usb
TAGS=:seat:uaccess:
TYPE=255/255/255
USEC_INITIALIZED=46177250
libsane_matched=yes
UDEV [1246.211550] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v04C5p117Fd0100dcFFdscFFdpFFicFFiscFFipFFin00
PRODUCT=4c5/117f/100
SEQNUM=1609
SUBSYSTEM=usb
TYPE=255/255/255
USEC_INITIALIZED=179187
So it looks like everything is being recognized. But neither "scanimage -L" nor "sudo scanimage -L" recognizes the device.
Last edited by madalu (2012-10-19 15:58:09)
Offline
FWIW, the same problem has occurred with the scan snap S1300 on my arch linux box at work.
I can confirm, moreover, that I have no problem with linux-lts. So this is definitely a kernel issue. I suppose I'll scour the bug reports there.
Last edited by madalu (2012-10-19 15:53:57)
Offline
I've got exactly the same problem with ScanSnap S300 and Linux 3.6.2.
Offline