Guys the Epson has been working ok, but refuses to wake up when required. Inserting the usb plug and starting xsane works ok. But after some time has passed it refuses to wake.
The log below is very prominent on the net, but I have not yet solved this. The first two lines seem to indicate a problem when I start xsane.
Then I disconnect and reconnect the usb plug and you can see the scanner is initialized. The bottom two lines indicate another problem which I am not attempting to address here.
I cannot find any reference to usbfs in lsmod or using locate command. When I google I can see some people attempt a workaround using udev to isolate the problem.
Any ideas on how I might resolve this ?
linux-rz2v kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while ‘scanimage’ sets config #1
linux-rz2v kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while ‘scanimage’ sets config
linux-rz2v kernel: usb 9-3.3: USB disconnect, device number 16
linux-rz2v kernel: usb 9-4: new high-speed USB device number 17 using xhci_hcd
linux-rz2v kernel: usb 9-4: New USB device found, idVendor=04b8, idProduct=014a
linux-rz2v kernel: usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
linux-rz2v kernel: usb 9-4: Product: EPSON Perfection V37/V370
linux-rz2v kernel: usb 9-4: Manufacturer: EPSON
linux-rz2v kernel: usb 9-4: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
linux-rz2v kernel: usb 9-4: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
uys the Epson has been working ok, but refuses to wake up when required. Inserting the usb plug and starting xsane works ok. But after some time has passed it refuses to wake.
So, the scanner is working is initially , but some power management ‘feature’ makes the USB port (or scanner) go to sleep?
I cannot find any reference to usbfs in lsmod or using locate command.
The USB files system is a virtual filesystem, dynamically generated and managed by the kernel. (IIRC, the usbcore module is responsible, but usually compiled as part of the kernel with openSUSE.)
I see the the sleep mode is a built-in power-saving feature
Default Delay Times for Power Management for EPSON Products
This product will enter sleep mode after a period of nonuse. The time interval has been set at the factory tothe product meets Energy Star Standards of energy effiency, and cannot be modified by the consumer.
I tried switching the unit off overnight, using the Scanner on/off switch. This did not amount to anything. When I turned it on this morning I came up against the same problem. Also tried using skanlite from the command line. This returned a log very similar to the earlier one.
kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while ‘KSaneIface::Fin’ sets config #1
kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while ‘skanlite’ sets config #1
Yes but how to deal with it. Googling about this shows some people actually recompiling the kernel with usbfs turned off. I do not really want to go down this path.
Yes but how to deal with it. Googling about this shows some people actually recompiling the kernel with usbfs turned off. I do not really want to go down this path.
>
> Guys the Epson has been working ok, but refuses to wake up when
> required. Inserting the usb plug and starting xsane works ok. But after
> some time has passed it refuses to wake.
> The log below is very prominent on the net, but I have not yet solved
> this. The first two lines seem to indicate a problem when I start xsane.
>
> Then I disconnect and reconnect the usb plug and you can see the scanner
> is initialized. The bottom two lines indicate another problem which I am
> not attempting to address here.
> I cannot find any reference to usbfs in lsmod or using locate command.
> When I google I can see some people attempt a workaround using udev to
> isolate the problem.
> Any ideas on how I might resolve this ?
>
> linux-rz2v kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while
> ‘scanimage’ sets config #1
> linux-rz2v kernel: usb 9-3.3: usbfs: interface 0 claimed by usbfs while
> ‘scanimage’ sets config
> linux-rz2v kernel: usb 9-3.3: USB disconnect, device number 16
> linux-rz2v kernel: usb 9-4: new high-speed USB device number 17 using
> xhci_hcd
> linux-rz2v kernel: usb 9-4: New USB device found, idVendor=04b8,
> idProduct=014a
> linux-rz2v kernel: usb 9-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> linux-rz2v kernel: usb 9-4: Product: EPSON Perfection V37/V370
> linux-rz2v kernel: usb 9-4: Manufacturer: EPSON
> linux-rz2v kernel: usb 9-4: ep 0x81 - rounding interval to 128
> microframes, ep desc says 255 microframes
> linux-rz2v kernel: usb 9-4: ep 0x2 - rounding interval to 128
> microframes, ep desc says 255 microframes
>
>
I find installing the Epson drivers and the iscan programs the Epson V370
works fine on two of my OpenSuse 12.2 computers. I then use Image Scan to
do the scanning.
Following some details that were googled from elsewhere I created a file
50-epson.rules
Inside this I have the following line.
SUBSYSTEM==“usb”, ATTRS{idVendor}==“04b8”, ATTRS{idProduct}==“014a”, MODE:=“666”, GROUP=“users”
Starting xsane now causes the Epson V370 to wake up ok and no logs appear at all. Trying to use a usb 3.0 port does not work. Usb 2.0 and its ehci-pci driver are required.
That’s interesting. FWIW, the sane-backends package provides /etc/udev/rules.d/55-libsane.rules which has rules for many scanner models (including some Epson Perfection models) that take the form like the following
Yes this may work as well. I commented out my 50-epson.rules and edited the 55-libsane.rules as per above. This seems to work ok, but more testing is needed.
In short we edit the V300 Photo rules by substituting ATTR{idProduct}==“014a” for ATTR{idProduct}==“0131”. This should allow the Epson Perfection V370 to work with xsane as planned.