[sane-devel] sane fails to recognize my nikon coolscan IV

Fri Dec 16 06:04:35 UTC 2011

On Wed, Dec 14, 2011 at 08:01:39PM -0800, Travis Parker wrote:
> Date: Wed, 14 Dec 2011 20:01:39 -0800
> From: Travis Parker <travis.parker at gmail.com>
> To: sane-devel at lists.alioth.debian.org
> Subject: sane fails to recognize my nikon coolscan IV
> 
> I can't seem to get my nikon coolscan IV film scanner (should be fully
> supported by sane-coolscan3) to be be recognized. sane-find-scanner sees
> and identifies it, but scanimage -L doesn't, nor does xsane or anything
> similar.
>                          
> I've looked around the archlinux forums, the archives for this list, and
> can't find anything that seems to fit my issue.
>                          
> Any help would be much appreciated!
>                          
> --travis
> 
> 
> [teepark at spaceghost ~]$ uname -a
> Linux spaceghost 3.1.5-1-ARCH #1 SMP PREEMPT Sat Dec 10 14:43:09 CET 2011 x86_64 Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz GenuineIntel GNU/Linux
> [teepark at spaceghost ~]$ scanimage --version
> scanimage (sane-backends) 1.0.22; backend version 1.0.22
> [teepark at spaceghost ~]$ lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd
> Bus 002 Device 011: ID 04b0:4000 Nikon Corp. Coolscan LS 40 ED
> [teepark at spaceghost ~]$ cat /etc/sane.d/coolscan3.conf
> usb 04b0 4000
> [teepark at spaceghost ~]$ sane-find-scanner
> 
>   # sane-find-scanner will now attempt to detect your scanner. If the
>   # result is different from what you expected, first make sure your
>   # scanner is powered up and properly connected to your computer.
> 
>   # No SCSI scanners found. If you expected something different, make sure that
>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>   # Also you need support for SCSI Generic (sg) in your operating system.
>   # If using Linux, try "modprobe sg".
> 
> 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/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/003: 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/002/001: Permission denied.
> libusb requires write access to USB device nodes.
> found USB scanner (vendor=0x04b0, product=0x4000) at libusb:002:011
>   # Your USB scanner was (probably) detected. It may or may not be supported by
>   # SANE. Try scanimage -L and read the backend's manpage.
> 
>   # Not checking for parallel port scanners.
> 
>   # Most Scanners connected to the parallel port or other proprietary ports
>   # can't be detected by this program.
> 
>   # You may want to run this program as root to find all devices. Once you
>   # found the scanner devices, be sure to adjust access permissions as
>   # necessary.
> [teepark at spaceghost ~]$ SANE_DEBUG_COOLSCAN3=1 scanimage -L
> [sanei_debug] Setting debug level of coolscan3 to 1.
> [coolscan3] coolscan3 backend, version 1.0.0 initializing.
> 
> No scanners were identified. If you were expecting something different,
> 
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).

I narrowed it down to being in a libusb_set_configuration, and
specifically in libusb/os/linux_usbfs.c:op_set_configuration an error
from the ioctl(), but couldn't find any reason that it might come back
with EPIPE (errno 32), that's never mentioned in the manpages.

I ran the scanimage with more debugging output (below). It also came out
exactly this way when I configured sane with --enable-libusb_1_0, so
that rules out the compatibility layer at least. Is there anything else
I can provide to help diagnose the issue?

--travis

[teepark at spaceghost ~]$ SANE_DEBUG_COOLSCAN3=255 SANE_DEBUG_SANEI_USB=255 scanimage -L
[sanei_debug] Setting debug level of coolscan3 to 255.
[coolscan3] coolscan3 backend, version 1.0.0 initializing.
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: marking existing devices
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory
[sanei_usb] sanei_usb_init: Looking for libusb devices
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0002, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0002: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x8087/0x0024, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x8087/0x0024: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x04f2/0xb217, interface 0 doesn't look like a scanner (239/14)
[sanei_usb] sanei_usb_init: device 0x04f2/0xb217, interface 1 doesn't look like a scanner (239/14)
[sanei_usb] sanei_usb_init: device 0x04f2/0xb217: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0002, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x1d6b/0x0002: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x8087/0x0024, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x8087/0x0024: no suitable interfaces
[sanei_usb] sanei_usb_init: found libusb device (0x04b0/0x4000) interface 0  at libusb:002:009
[sanei_usb] store_device: add dn 0 with libusb:002:009
[sanei_usb] sanei_usb_init: found 1 devices
[sanei_usb] sanei_usb_init: device 00 is libusb:002:009
[coolscan3] sane_coolscan3_get_devices
[coolscan3] sane_get_devices(): Reading config file.
[coolscan3] cs3_open, device = auto, interface = 0
[sanei_usb] sanei_usb_find_devices: vendor=0x04b0, product=0x4000
[coolscan3] cs3_open, device = libusb:002:009, interface = 2
[coolscan3] cs3_open, trying to open libusb:002:009, assuming USB interface
[sanei_usb] sanei_usb_open: trying to open device `libusb:002:009'
libusb:error [op_set_configuration] failed, error -1 errno 32
[sanei_usb] sanei_usb_open: libusb complained: Numerical result out of range
[coolscan3]  ...failed: Invalid argument.
[sanei_usb] sanei_usb_find_devices: vendor=0x04b0, product=0x4001
[sanei_usb] sanei_usb_find_devices: vendor=0x04b0, product=0x4002
[coolscan3] sane_coolscan3_get_devices: 0 device(s) detected.

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[coolscan3] sane_coolscan3_exit