You are not logged in.
Pages: 1
I have an EPSON ES-400 scanner connected to my computer by USB, and using the utsushi driver from the AUR package imagescan. This used to work fine. Recently, however, it only works if the scanner is powered on before the computer boots. In this case, scanimage -L reports the scanner:
device `v4l:/dev/video0' is a Noname FaceTime HD Camera (Built-in): virtual device
device `utsushi:esci:usb:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0' is a EPSON ES-400
However, if the scanner is off when the computer boots, and I later turn on the scanner, scanimage -L does not see it, reporting only:
device `v4l:/dev/video0' is a Noname FaceTime HD Camera (Built-in): virtual device
sane-find-scanner does see the scanner; it reports
...
found USB scanner (vendor=0x04b8 [EPSON], product=0x0156 [ES-400]) at libusb:002:002
...
Any ideas as to how I can fix this so I don't need to reboot whenever I want to scan something? Thanks.
Offline
This may be related to some change in the kernel.
If I downgrade the linux and linux-headers packages to version 4.13.12-1, the problem does not occur. With version 4.14.3-1, the problem does occur.
After I saw that, I tried compiling the imagescan package against the latest 4.14.4-1 kernel, but that does not fix the problem, and even causes scanimage to segfault when I actually try to scan something. (scanimage -L does not segfault.)
Offline
There is a workaround for this. In the file /etc/udev/rules.d/utsushi-esci.rules, find the line beginning ACTION!="add", and change that part of the line to ACTION!="add|bind".
It seems that the 4.14 kernels are generating "bind" udev actions when the scanner is plugged in, in addition to the "add" actions from 4.13. Exactly why this caused problems is still not understood, though. More details at https://github.com/utsushi/utsushi/issues/41.
Offline
Pages: 1