| View previous topic :: View next topic |
| Author |
Message |
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
 Posted: Thu Feb 19, 2004 2:45 pm Post subject: epson scanner and libusb |
 |
|
I have an 'Epson Perfection 2450 Photo' scanner. I have not been able to get it to work with libusb. Kernel 2.6.3-rc2-mm1 no longer has a USB scanner option so it off to libusb. The scanner did work with the kernel module when it was available.
I have checked the forums etc for the answer to this problem with no solution. I have also tried the configuration from:
http://www.freecolormanagement.com/sane/libusb.html
to no avail. There is no device created in /dev.
sane-find-scanner finds the scanner:
root@go2:/dev# sane-find-scanner
...
found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:001:013
...
/etc/hotplug/usb.usermap entry:
epson_scanner 0x0003 0x04b8 0x0112 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
/usr/hotplug/usb/epson_scanner contents:
#!/bin/bash
if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
chown root "${DEVICE}"
chgrp scanner "${DEVICE}"
chmod 660 "${DEVICE}"
fi
The scanner does not appear in /sys. At least I can't find it.
It does appear in /proc/bus/usb/:
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 13 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0112 Rev= 1.01
S: Manufacturer=EPSON
S: Product=EPSON Scanner
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I have seen this problem a lot in the forums etc but no answer.
Does anyone have a clue?
Thanks,
Gene Imes[/quote] |
|
| Back to top |
|
 |
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Thu Feb 19, 2004 7:34 pm Post subject: |
|
|
| have exactly the same problem with kernels 2.6.3 and 2.6.3-mm1 but the earlier kernels such as 2.6.2-rc2-mm1 were OK and my scanner showed up in /dev and /sys. |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Fri Feb 20, 2004 12:43 pm Post subject: |
|
|
| fredor wrote: | | have exactly the same problem with kernels 2.6.3 and 2.6.3-mm1 but the earlier kernels such as 2.6.2-rc2-mm1 were OK and my scanner showed up in /dev and /sys. |
Who do I tell about this? Andrew Morton? I sure would like to get this fixed.
Thanks,
Gene Imes |
|
| Back to top |
|
|
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Fri Feb 20, 2004 6:48 pm Post subject: |
|
|
imesg wrote
| Quote: | Who do I tell about this? Andrew Morton? I sure would like to get this fixed.
|
I guess he's your man but I'm relatively new to this. Alternatively you could post a kernel bug.
Best of Luck |
|
| Back to top |
|
|
geophagus
n00b
Joined: 16 Dec 2002
Posts: 36
Location: Tönisvorst/Germany
|
| Posted: Fri Feb 20, 2004 9:02 pm Post subject: |
|
|
I got the same problem with my Canon Scanner and I solved it like this
1) create /etc/hotplug/usb/scanner.usermap
| Code: | | scanner 0x0003 0x04a9 0x220d 0x0100 0x0000 0xff 0x00 0x00 0xff 0x00 0xff 0x00000000 |
(most of the non-zero values can probably changed to zero)
2) make a copy of /etc/hotplug/usb/usbcam and name it /etc/hotplug/usb/scanner
3) you might want to modify the "chown" and "chmod" commands in the newly created /etc/hotplug/usb/scanner. In my case the essential part looks like this:
| Code: | if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
# New code, using lock files instead of copying /dev/console permissions
# This also works with non-gdm logins (e.g. on a virtual terminal)
# Idea and code from Nalin Dahyabhai <nalin@redhat.com>
if [ -f /var/run/console.lock ]
then
CONSOLEOWNER=`cat /var/run/console.lock`
elif [ -f /var/lock/console.lock ]
then
CONSOLEOWNER=`cat /var/lock/console.lock`
else
CONSOLEOWNER=
fi
if [ -n "$CONSOLEOWNER" ]
then
chmod 0000 "${DEVICE}"
chown "$CONSOLEOWNER":video "${DEVICE}"
chmod 0660 "${DEVICE}"
fi
fi
|
The ebuild version I use are:
gentoo-dev-sources-2.6.3-r1
libusb-0.1.7-r1
xsane-0.91
BTW: don't forget to comment out "brother" in /etc/sane.d/dll.conf |
|
| Back to top |
|
|
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Sat Feb 21, 2004 2:31 pm Post subject: |
|
|
Thanks Geophagus for your input.
I have more or less the same hotplug files as you except for the CONSOLEOWNER items.
With kernel 2.6.3-mm1, the scanner shows in /proc/bus/usb/devices and with lsusb but no device nodes are made and it does not show during the boot sequence. Previously there was a line:-
drivers/usb/core/usb.c: registered new driver usbscanner.
There is a new kernel version out, but at the moment for me, this hangs at the parport_pc module. |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Sat Feb 21, 2004 2:48 pm Post subject: |
|
|
| geophagus wrote: | I got the same problem with my Canon Scanner and I solved it like this
|
Thanks, geophagus, no workee for me. I am still trying.
Gene Imes |
|
| Back to top |
|
|
Elm0
Apprentice
Joined: 24 Nov 2002
Posts: 281
Location: UK
|
| Posted: Sat Feb 21, 2004 3:10 pm Post subject: |
|
|
Woah, back up guys  I had similar problems, but after a lot of fiddling I understand how this whole new way of accessing scanners works
libusb is a way of accessing usb devices from within userspace using the /proc/usb filesystem. You DO NOT need a /dev/ device for your scanner to work now. FYI, my scanner is an Epson Perfection 1260 which uses the Plustek backend.
First thing you need is the latest ~x86 version of sane-backends compiled with the USB use flag. You also (obviously) need the latest version of libusb. Get rid of the scanner module in your kernel, obviously keep all your other USB stuff Remove all the hotplug modifications you've made, you really don't need them!
For my plustek backend the settings in /etc/sane.d/plustek are
This is standard so you probably won't need to modify anything. I don't know the syntax for epson.conf, but its definetly on these forums somewhere, so have a search. I'm thinking maybe just 'usb' on a line will work.
Restart your PC with the new kernel, and run sane-find-scanner, and you'll get output as the original poster did.
| Code: |
found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:001:013
|
Now here is the not so obvious part: permissions on the /proc/usb filesystem.
In my /etc/conf.d/local.start file I have:
| Code: |
chmod 660 /proc/bus/usb/003/002
chgrp users /proc/bus/usb/003/002
|
I always have my scanner plugged in at the same place (you need to adjust the numbers to point to your scanner device), but I reckon you could just do the following and forget about it:
| Code: |
chmod 660 /proc/bus/usb/ -R
chgrp users /proc/bus/usb/ -R
|
This will allow people in the users group to access the scanner.
All your userspace scanner apps like xsane should work flawlessly now |
|
| Back to top |
|
|
Niko_K
Guru
Joined: 19 Sep 2002
Posts: 484
Location: Rietz/Tirol
|
| Posted: Sat Feb 21, 2004 6:01 pm Post subject: Hmm |
|
|
Hi,
i did the same as Elm0, but I really think that this is a very dirty solution!
It only works, when the scanner is connected at boot time.
If i disconnect the scanner while using gentoo i have to reboot!!!
Is there a better way to solve this problem (without hotplug)?
Niko
_________________
Meine Homepage |
|
| Back to top |
|
|
Elm0
Apprentice
Joined: 24 Nov 2002
Posts: 281
Location: UK
|
| Posted: Sat Feb 21, 2004 6:13 pm Post subject: |
|
|
I don't have my scanner to hand atm, however...
What happens when you plug in after boot time? Do the /proc/bus/usb entries lose their permissions and revert to root,root ownership?
If that is the problem, I'm thinking maybe a hotplug script which would take the position of the device on the usb bus and then correctly chmod the /proc/bus/usb entry would solve the problem.
Niko_k - whats the problem with hotplug? I've found it (in conjunction with udev) to be a very powerful combination. |
|
| Back to top |
|
|
geophagus
n00b
Joined: 16 Dec 2002
Posts: 36
Location: Tönisvorst/Germany
|
| Posted: Sat Feb 21, 2004 7:25 pm Post subject: |
|
|
@imesg: | Quote: | There is no device created in /dev.
The scanner does not appear in /sys. At least I can't find it.
|
Same for /dev on my system. But some devices and device information are created below /sys/bus/usb. They information can easily be displayed using | Code: | | # systool -v -b usb |
(systool is part of sysfsutils)
The output from my /proc/bus/usb/devices looks similar to yours
What output does "scanimage -L" give on your system? On my system the output is | Code: | | device `plustek:libusb:002:003' is a Canon N670U/N676U/LiDE20 USB flatbed scanner |
Before I made the changes to /etc/hotplug/usb only root could run this command.
Some additional information concerning my system (they might not be of importance): I'm running hotplug-20040105 and udev-016-r1 (udev is a replacement for devfsd. In the past I used it to create a device /dev/usbscanner0. But his no longer works with kernel 2.6.3 because it needs the scanner.ko which is no longer available with 2.6.3) |
|
| Back to top |
|
|
marc
Apprentice
Joined: 13 Jan 2003
Posts: 290
|
| Posted: Sun Feb 22, 2004 2:34 am Post subject: |
|
|
ElmO wrote:
| Quote: | In my /etc/conf.d/local.start file I have:
Code:
chmod 660 /proc/bus/usb/003/002
chgrp users /proc/bus/usb/003/002
I always have my scanner plugged in at the same place (you need to adjust the numbers to point to your scanner device), but I reckon you could just do the following and forget about it:
Code:
chmod 660 /proc/bus/usb/ -R
chgrp users /proc/bus/usb/ -R |
note: 660 does not hand because exec-right are necessary
770 and it works fine for me. |
|
| Back to top |
|
|
Niko_K
Guru
Joined: 19 Sep 2002
Posts: 484
Location: Rietz/Tirol
|
| Posted: Sun Feb 22, 2004 8:49 am Post subject: Hotplug |
|
|
I am emerging hotplug right now, ...
The "problem" ist, that there is another boot-sktipt, which takes quite some time...
Niko
EDIT: Don't forget to set the right Permissions for /etc/hotplug/usb/epson_scanner. At the moment I use 660 - and it works
_________________
Meine Homepage
Last edited by Niko_K on Sun Feb 22, 2004 12:49 pm; edited 1 time in total |
|
| Back to top |
|
|
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Sun Feb 22, 2004 12:31 pm Post subject: |
|
|
I tried Elm0's solution but it didn't work for me.
I take it you are using a 2.6.3 type kernel. Kernels prior to 2.6.2-rc3 worked fine with the /dev/scanner0 showing up but with this and subsquent kernels, I have been unable to get them working.
My scanner is Epson Perfection 1640SU
Using udev018 with no /lib/udev-states/devices file
libusb version 0.1.7-r1 |
|
| Back to top |
|
|
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Sun Feb 22, 2004 11:45 pm Post subject: |
|
|
I re-emerge sane-backends with USE=usb and scanimage -L now gives
device 'epson:libusb:003:003' is Epson Perfection1640 flatbed scanner
many thanks to geophagus and Elm0
No /dev node but Xsane works OK |
|
| Back to top |
|
|
Bob Paddock
n00b
Joined: 25 Aug 2002
Posts: 49
|
| Posted: Tue Feb 24, 2004 2:07 am Post subject: |
|
|
| fredor wrote: | I re-emerge sane-backends with USE=usb and scanimage -L now gives
|
I have been following along trying to get my Epson Perfection 1240USB working, using
UDEV-018/2.6.3-gentoo-r1.
sane-find-scanner says:
| Code: | found USB scanner (vendor=0x04b8 [EPSON], product=0x010b [Perfection1240]) at libusb:002:003
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage. |
Alas scanimage -L says "No scanners were identified".
This was scanner was working fine with scanner module under 2.4.x, so I'm sure it is all hooked up correctly.
What should I try next? |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Tue Feb 24, 2004 2:15 pm Post subject: |
|
|
| Elm0 wrote: | Woah, back up guys
...
This is standard so you probably won't need to modify anything. I don't know the syntax for epson.conf, but its definetly on these forums somewhere, so have a search. I'm thinking maybe just 'usb' on a line will work.
...
|
I had tried this before and 'scanimage -L' appeared to be hung but it was not. I was impatient and killed it. However now that I tried the 'usb' line in /etc/sane.d/epson.conf again and waited for 'scanimage -L' to complete I get:
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson GT-9700 flatbed scanner
However this takes about two minutes to complete. And this:
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson GT-9700 flatbed scanner
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson Unknown model flatbed scanner
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson GT-9700 flatbed scanner
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson Unknown model flatbed scanner
root@go2:/etc# scanimage -L
device `epson:libusb:001:002' is a Epson GT-9700 flatbed scanner
As you can see the commands complete but alternating commands cannot find the model number. These commands also take about two minutes to complete.
The same thing happens in gimp and OpenOffice also, about two minutes to get the xsane dialog.
All of this started about two or three days ago when I did an 'emerge -update world'. I also started having printer problems at what seems to me the same time, you never know sometimes when exactly something goes wrong because you are not using these thing constantly.
After writing all this and trying again I get 'no devices available'. However an 'lsusb' returns this:
Bus 008 Device 002: ID 0409:0058 NEC Corp. USB2.0 Hub Controller
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 003: ID 051d:0002 American Power Conversion Back-UPS Pro 500
Bus 007 Device 002: ID 099a:610c
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 002: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 04b8:0112 Seiko Epson Corp. Perfection 2450
Bus 001 Device 001: ID 0000:0000
Anyone know why the long delay?
Thanks again,
Gene Imes |
|
| Back to top |
|
|
Elm0
Apprentice
Joined: 24 Nov 2002
Posts: 281
Location: UK
|
| Posted: Tue Feb 24, 2004 2:30 pm Post subject: |
|
|
This sounds like a bug to me, very odd behavior. Its difficult to say where the problem lies but as your having problems with your printer it might be in the kernel or in libusb rather than sane.
Pretty much reached by problem solving skills on this one, sorry |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Tue Feb 24, 2004 4:03 pm Post subject: |
|
|
| imesg wrote: |
The same thing happens in gimp and OpenOffice also, about two minutes to get the xsane dialog.
All of this started about two or three days ago when I did an 'emerge -update world'. I also started having printer problems at what seems to me the same time, you never know sometimes when exactly something goes wrong because you are not using these thing constantly.
After writing all this and trying again I get 'no devices available'. However an 'lsusb' returns this:
|
Bus 008 Device 003: ID 0409:0058 NEC Corp. USB2.0 Hub Controller
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 003: ID 051d:0002 American Power Conversion Back-UPS Pro 500
Bus 007 Device 002: ID 099a:610c
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 002: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0924:fff3 Xerox
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 04b8:0112 Seiko Epson Corp. Perfection 2450
Bus 001 Device 001: ID 0000:0000
Ok, when reverting back to kernel 2.6.3-rc2-mm1 the printer resumes normal function but the scanner continues to misbehave.
Thanks,
Gene |
|
| Back to top |
|
|
fredor
Tux's lil' helper
Joined: 13 Oct 2003
Posts: 84
Location: UK
|
| Posted: Tue Feb 24, 2004 7:07 pm Post subject: |
|
|
I was getting some interference with other usb devices so I commented out everything in /etc/sane.d/dll.conf except 'epson'. This stopped the interference.
There's no /dev node for the scanner but everything works perfectly now. |
|
| Back to top |
|
|
Bob Paddock
n00b
Joined: 25 Aug 2002
Posts: 49
|
| Posted: Wed Feb 25, 2004 2:04 am Post subject: |
|
|
| fredor wrote: | I was getting some interference with other usb devices so I commented out everything in /etc/sane.d/dll.conf except 'epson'. This stopped the interference.
There's no /dev node for the scanner but everything works perfectly now. |
That fixed it, thank you.
This is also a good place to look for Epson scanners with libusb/udev:
http://www.khk.net/sane/libusb.html |
|
| Back to top |
|
|
kurtb
n00b
Joined: 05 Nov 2003
Posts: 23
|
| Posted: Wed Feb 25, 2004 3:24 am Post subject: |
|
|
Ok, the issue here seems to be that the scanner kernel module has been removed as per these lines from teh 2.6.3 kernel changelog.
| Code: |
<trini@kernel.crashing.org>
[PATCH] USB: mark the scanner driver BROKEN
Greg, I think this now makes 2 distinct bugs in the scanner kernel
driver. Maybe it should be protected with a BROKEN:
<bunk@fs.tum.de>
[PATCH] USB: remove USB_SCANNER from the build
USB_SCANNER is obsolete, and it's now marked as BROKEN.
I there a good reason to keep it in the kernel?
<greg@kroah.com>
[PATCH] USB: remove scanner driver files.
|
I have an epson perfection 2400 and here is what I did to get things working with libusb which is what you will have to use.
1. run sane-find-scanner
| Code: |
sane-find-scanner
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04b8 [EPSON], product=0x011b [EPSON Scanner]) at libusb:001:003
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports can't be
# detected by this program.
|
2. Hopefully your scanner is deteced as mine was.
3. Edit your /etc/saned/epson.conf file and add a line like the following using your output from find-sane-scanner.
4. Next, we need to set permissions for the devices. This info taken from $man sane-usb.
| Code: |
The permissions for the device files used by libusb must be adjusted
for user access. Otherwise only root can use SANE devices. For Linux,
the devices are located in /proc/bus/usb/. There are directories named
e.g. "001" (the bus name) containing files "001", "002" etc. (the
device files). The right device files can be found out by running scan-
image -L as root. Setting permissions with "chmod" is not permanent,
however. They will be resetted after reboot or replugging the scanner.
It's also possible to mount the usbfs with the option "devmode=0666",
e.g. by using the following line in /etc/fstab:
none /proc/bus/usb usbfs defaults,devmode=0666 0 0
|
So I then just did a chmod 660 /proc/bus/usb/001/* and then chgrp users /proc/bus/usb/001/* since my device was 001/003.
This will probably not work if you disconnect and then reconnect the device so I need to figure out a way to do this with hotplug seemlessly. I'll post back when I have figured that out, but this is a workaround for now. Hope this helps somebody! |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Thu Feb 26, 2004 12:20 am Post subject: |
|
|
| kurtb wrote: | Ok, the issue here seems to be that the scanner kernel module has been removed as per these lines from teh 2.6.3 kernel changelog.
...
I have an epson perfection 2400 and here is what I did to get things working with libusb which is what you will have to use.
...
So I then just did a chmod 660 /proc/bus/usb/001/* and then chgrp users /proc/bus/usb/001/* since my device was 001/003.
This will probably not work if you disconnect and then reconnect the device so I need to figure out a way to do this with hotplug seemlessly. I'll post back when I have figured that out, but this is a workaround for now. Hope this helps somebody! |
geophagus has the thing mostly right in about the fifth post in this thread. His method takes care of ownership and permissions. However you need to add the group scanner and change the group in the /etc/hotplug/usb/scanner to 'scanner'.
Check out:
http://khk.net/sane/libusb.html
Look at this:
root@go2:/proc/bus/usb/001# ls -l *
-rw-r--r-- 1 root root 43 Feb 25 17:18 001
-rw-rw---- 1 gene scanner 50 Feb 25 17:24 002
This is from the setup the way geophagus did it and from the link above. In epson.conf just put 'usb' I don't think you need the libusb:001:003 part.
I say this works for me but there is one problem. Whenever the scannner is called it takes about one minute or so for the scanner to be found. I am not completely happy with it but it works.
Goodluck,
Gene |
|
| Back to top |
|
|
kurtb
n00b
Joined: 05 Nov 2003
Posts: 23
|
| Posted: Thu Feb 26, 2004 3:37 am Post subject: |
|
|
| Quote: | geophagus has the thing mostly right in about the fifth post in this thread. His method takes care of ownership and permissions. However you need to add the group scanner and change the group in the /etc/hotplug/usb/scanner to 'scanner'.
|
I found the link you mentioned shortly after making my post and yes that is definitely the better way to handle things. The method I posted was a quick kludge that worked and was by no means a final solution as I mentioned.
However, I have set things up as mentioned in the link and I'm seeing some very peculiar weirdness. Sometimes when I run xsane or scanimage it works just fine. But most of the time it sits there quite a while and either says no devices found or it eventually works. While xsane is sitting there I see the following in my log files.:
| Code: |
usb 1-2: bulk timeout on ep1in
usbfs: USBDEVFS_BULK failed dev 3 ep 0x81 len 1 ret -110
usb 1-2: bulk timeout on ep2out
usbfs: USBDEVFS_BULK failed dev 3 ep 0x2 len 2 ret -110
usb 1-2: bulk timeout on ep1in
usbfs: USBDEVFS_BULK failed dev 3 ep 0x81 len 1 ret -110
|
Anyone else experiencing this? Might this be a kernel bug? |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Thu Feb 26, 2004 3:51 am Post subject: |
|
|
| kurtb wrote: |
...
However, I have set things up as mentioned in the link and I'm seeing some very peculiar weirdness. Sometimes when I run xsane or scanimage it works just fine. But most of the time it sits there quite a while and either says no devices found or it eventually works. While xsane is sitting there I see the following in my log files.:
| Code: |
usb 1-2: bulk timeout on ep1in
usbfs: USBDEVFS_BULK failed dev 3 ep 0x81 len 1 ret -110
usb 1-2: bulk timeout on ep2out
usbfs: USBDEVFS_BULK failed dev 3 ep 0x2 len 2 ret -110
usb 1-2: bulk timeout on ep1in
usbfs: USBDEVFS_BULK failed dev 3 ep 0x81 len 1 ret -110
|
Anyone else experiencing this? Might this be a kernel bug? |
Yes, I have this problem however, maybe not as bad as you describe. I do not know the problem. I suspect the kernel. I had to revert to a previous kernel to get my printer to work. All usb of course.
Gene |
|
| Back to top |
|
|
|
Kernel & Hardware
