Fergus Wilde wrote:

On Tuesday 10 August 2004 11:39, Fergus Wilde wrote:

...

---------- Forwarded Message ----------

Subject: Re: [SLE] Epson scanner and sane in 9.1 Date: Monday 09 August 2004 20:56 From: Kastus To: suse-linux-e@suse.com

On Mon, Aug 09, 2004 at 10:14:58AM +0100, Fergus Wilde wrote:

...

SuSE 9.1, all updates, rebooted, tried hotplug restart and re-plugging scanner in all the possible combinations. Scanner worked perfectly in 9.0. Now with xsane, error message always appears:

Failed to start scanner. Error during device I/O

The system log for the relevant portion of activity:

[etc etc]

...

...

Aug 9 09:17:48 pc11 kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x81 len 1 ret -110

Fergus, as you see from the messages, the problem is resmgr related (5xx error codes).

Please see the thread http://lists.suse.com/archive/suse-linux-e/2004-Feb/2859.html in list archives.

For the impatient, the solution is to create a file /etc/hotplug/usb/desktopdev.usermap with the following lines:

# usb module match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info desktopdev 0x0003 0x04b8 0x011c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000

That forces /etc/hotplug/usb.agent to invoke /etc/hotplug/usb/desktopdev and add a usb device to resmgr.

The first line is actually a comment explaining the format of the next line.

idVendor 0x04b8 is Epson, idProduct 0x011c is for Perfection Photo 3200. The second item might be different in your case.

Regards, -Kastus

Thanks Kastus, good advice - the thing now partly works, though not as well as it did under 8.2 and 9.0 - each time it loads it scans for a device, which takes a while, and it doesn't work with Gimp like it did. If you open xsane via the Gimp acquire menu, xsane starts quickly but then fails as before with messages complaining about an I/O error.

It wouldn't work at all until I had added in two zeroes following the x characters in /etc/sane.d/epson.conf; that is to say, I added two zeroes and then it grudgingly worked ...

Before (as per suse installation):

grep -v \# /etc/sane.d/epson.conf usb /dev/usbscanner usb 0x4b8 0x112

After, with tow more zeroes: grep -v \# /etc/sane.d/epson.conf usb /dev/usbscanner usb 0x04b8 0x0112

I found useful information at http://www.freecolormanagement.com/sane/usb_scanner.html, which includes a handy list of those bizarre codes for the scanners.

But the logs are still bitching as much as before, or so it seems to my untutored eye (below).

Thanks very much again for your help. But what a massive backwards step in SuSE's installation routines if you have to meddle like this to get a part-working version of something they had working perfectly before.

Aug 10 14:17:38 pc11 xsane: resmgr: server response code 502 Aug 10 14:17:38 pc11 last message repeated 17 times Aug 10 14:17:38 pc11 kernel: ehci_hcd 0000:00:1d.7: qh deda8280 (#17) state 1 Aug 10 14:18:15 pc11 kernel: usb 1-5: bulk timeout on ep1in Aug 10 14:18:15 pc11 kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 1 ret -110 Aug 10 14:19:21 pc11 xsane: resmgr: server response code 502 Aug 10 14:19:21 pc11 last message repeated 17 times Aug 10 14:19:51 pc11 kernel: usb 1-5: bulk timeout on ep1in Aug 10 14:19:51 pc11 kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 1 ret -110 Aug 10 14:19:51 pc11 kernel: ehci_hcd 0000:00:1d.7: qh deda8300 (#17) state 1

I had problems with my 610 and xsane/xscanimage, whatever I did I couldn't get it found. The 2.6 kernel removed USB scanners, leaving that task to the libusb and sane developers to support it in user space. Eventually I googled and found vuescan for Linux on http://www.hamrick.com/, immediate success with no need to configure anything. I just tried to see if I could link vuescan to xsane and xscanimage in the gimp plugins directory, but that gave me a dead process which is still around. I next changed it all to vuescan and in gimprc changed all instances of xsane and xscanimage to vuescan also, gimp started and so did vuescan, then vuescan went solid grey, possibly it'll be straightened out later when I boot up the new kernel -- hoping, as starting vuescan standalone also ends in a Dead process. Other than with gimp which this post prompted me to try, vuescan has always been solid. It wouldn't be a bad idea if gimp allowed you to configure whatever scan software you fancied. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====