Not quite a repeat of my former message under subject 9.3 arrives in UK, scanner setup still broken but about the same problem. I posted lots of info there, which I won't repeat unless someone thinks it might help - I can't use 9.3 on my main workstation until I can get my Epson Perfection 2450 Photo scanner working with it. It worked with 9.2, after a fight, and historically support (on the identical hardware) was perfect under earlier versions. So there's no physical reason why it wouldn't work. Johannes Meixner has kindly tried to help, but no dice. His feeling is there's a problem with the USB setup somewhere. He also suggested I'd been unfair in saying the scanner setup was broken in 9.3 when it was going well elsewhere, and perhaps that's fair enough. The mainboard is an Intel 845, and has performed flawlessly with the same scanner in the past. Johannes wondered if it might, however, have an imperfect USB 2.0 implementation. I know it's worked fine with a USB 2.0 CF card reader, and that the USB 2.0 setup under 9.3 does correctly report the scanner as a high-speed device, and sees it correctly as an Epson scanner, down to the model number. But it doesn't work ... With the USB 2.0 disabled in the mainboard BIOS (which is the latest) the scanner is again correctly identified, this time as a USB 1.1 device, but it doesn't ... errr ... work. Anyone got any oddness to report in 9.3 USB, or with particular boards? Anyone now any usb tricks to try? Anyone got a happy set up with this scanner or similar model? Cheers Fergus -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Fergus Wilde wrote:
Not quite a repeat of my former message under subject
9.3 arrives in UK, scanner setup still broken
I can't use 9.3 on my main workstation until I can get my Epson Perfection 2450 Photo scanner working with it.
I remember perusing your other thread, but do not have the time to go back through and check what you have tried. I did a quick search for you (which I am sure you have also done). The only information that I pulled up that may help (and again, because I did not go back to read what you have tried, you may have done this or something similar) is for the Fedora distribution, but may help you out. Here is the info, and the link will be at the bottom: :) --- UPDATE --- :) I am using a 3170 in Fedora Core 3 and have iscan and sane/xsane fully functional. I am running the install kernel. This has worked for all 2.6.8 and 2.6.9 kernels I have tested in FC2, FC3 Tests, and FC3 final. This should work with all epkowa supported scanners: Perfection 610, Perfection 640U, Perfection 1200S, Perfection 1200U, Perfection 1200U PHOTO, Perfection 1240U, Perfection 1250, Perfection 1250 PHOTO, Perfection 1260, Perfection 1260 PHOTO, Perfection 1640SU, Perfection 1640SU PHOTO, Perfection 1650, Perfection 1650 PHOTO, Perfection 1660 PHOTO, Perfection2400 PHOTO, Perfection 2450 PHOTO, Perfection 3170 PHOTO, Perfection 3200 PHOTO, Perfection 4180 PHOTO, Perfection 4870 PHOTO, Perfection 4990 PHOTO, Expression 1600, Expression 1680, Expression 1640XL, Expression 10000XL, GT-10000, GT-10000+, GT-15000, GT-30000 NOTE: 610 and 640U have reported issues with lines in scan and it is suggested to fall back to 1.11.0 which is posted in the news item on the epkowa site. :) NEW VERSION SOLVED MY PROBLEMS :) 1. Download iscan-1.13.0-3.i386.rpm from www.epkowa.co.jp 2. Open a terminal window and cd to the download directory. 3. sudo vi /etc/yum.conf 4. If enable gpgcheck=1 change it to enable gpgcheck=0 5. :wq 6. sudo yum localinstall iscan-1.11.0-0.i386.rpm 7. Power on scanner. 8. sudo cat /proc/bus/usb/devices and look for your scanner. In the output find this line: P: Vendor=04b8 ProdID=0116 Rev= 1.00 You will need the ProdID for the next step. 9. Power off scanner. 10. sudo vi /etc/hotplug/usb/libsane.usermap 11. /Epson 12. Scroll to the line that most closley matches your model, I used the Perfection 3200. 13. Highlight the entire line (Epson to the last 0 preceeding the next Epson block). 14. Type i, press the Enter key, press the middle mouse button (or left and right together if you have no middle button) 15. Edit the line Changing the Title (I changed mine to: Epson Corp.|Perfection 3170) and change the ProdID to the one you found in Step 7 (0x0003 0x04b8 0x[ProdID]). 16. Press the ESC key and type :wq to save the changes and quit. 17. sudo vi /etc/sane.d/epkowa.conf 18. Change the last entries to look like this, using YOUR ProdID: #usb /dev/usb/scanner0 usb 0x04b8 0x0116 :) DO NOT MAKE THE SYM LINK FOR GIMP PLUGIN, USE THE FOLLOWING INSTEAD :) There is an issue with the library iscan uses versus sane and the simplest method of handling it is via an enviroment variable. In order to make this automatic and work in bash and csh I created 2 profile files in /etc/profile.d . I called the files iscanlib.sh (for bash) and iscanlib.csh (for csh). NOTE: THIS MUST BE DONE AS root and NOT THROUGH sudo! 19. su - 20. Type in root password 21. # echo "export LD_PRELOAD=/usr/lib/libstdc++.so.6">/etc/profile.d/iscanlib.sh 22. # chmod 755 /etc/profile.d/iscanlib.sh 23. # echo "setenv LD_PRELOAD /usr/lib/libstdc++.so.6">/etc/profile.d/iscanlib.csh 24. # chmod 755 /etc/profile.d/iscanlib.csh 25. # exit Note that the above points to the base link for libstdc++ version 6 major which points to the current version 6 file. This means that you only have to edit this when libstdc++ changes from the version 6 major. In order to use the scanner immediately you must either log off and back on or issue one of the following commands depending on your shell (bash is default): BASH: export LD_PRELOAD=/usr/lib/libstdc++.so.6 CSH: setenv LD_PRELOAD=/usr/lib/libstdc++.so.6 Now you simply have to cycle the power. NOTE: If you have the scanner turned on and connected prior to logging on you will need to cycle the power in order to have the correct device permissions to allow you to use the scanner. That should take care of everything. Bruce Gidney http://www.fedoraforum.org/forum/archive/index.php/t-26744.html I hope that this helps, and apologize if you have posted that you tried this. - James W.
On Tue April 26 2005 11:17 am, James Wright wrote:
:):) NEW VERSION SOLVED MY PROBLEMS :):)
1. Download iscan-1.13.0-3.i386.rpm from www.epkowa.co.jp 2. Open a terminal window and cd to the download directory.
I just went to that site, selected MY scanner, Epson Perfection 4180 Photo, and it came back with iscan-1.14.0-3.i386.rpm . I've never gotten my scanner to work with Linux, but I LOVE the scanner, and it is the ONLY reason i still run XP, is to run Adobe and process scans. -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
Hello, On Apr 26 11:37 Paul Cartwright wrote (shortened):
On Tue April 26 2005 11:17 am, James Wright wrote:
1. Download iscan-1.13.0-3.i386.rpm from www.epkowa.co.jp
I just went to that site, selected MY scanner, Epson Perfection 4180 Photo, and it came back with iscan-1.14.0-3.i386.rpm .
In Suse Linux 9.3 we have the package iscan-1.13.1.1 included which was the most up-to-date version which was available from Epson Kowa when we made Suse Linux 9.3. The epkowa.desc (description for the epkowa backend) shows that the "Perfection 4180 PHOTO" has "good" support status with the limitation that it "only scans up to 2400dpi". The epson.desc (description for the epson backend) shows that the "Perfection 4180" is "unsupported". Therefore it should work o.k. under Suse Linux 9.3 as is provided - the USB system can reliably communicate with the device - you use the epkowa backend - you use the iscan frontend See http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html and http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wednesday 27 April 2005 11:03, Johannes Meixner wrote:
Hello,
On Apr 26 11:37 Paul Cartwright wrote (shortened):
On Tue April 26 2005 11:17 am, James Wright wrote:
1. Download iscan-1.13.0-3.i386.rpm from www.epkowa.co.jp
I just went to that site, selected MY scanner, Epson Perfection 4180 Photo, and it came back with iscan-1.14.0-3.i386.rpm .
In Suse Linux 9.3 we have the package iscan-1.13.1.1 included which was the most up-to-date version which was available from Epson Kowa when we made Suse Linux 9.3.
As the OP, just to note that I have tried the updated iscan, and it doesn't make any difference at my end. Thanks all Cheers Fergus
The epkowa.desc (description for the epkowa backend) shows that the "Perfection 4180 PHOTO" has "good" support status with the limitation that it "only scans up to 2400dpi".
The epson.desc (description for the epson backend) shows that the "Perfection 4180" is "unsupported".
Therefore it should work o.k. under Suse Linux 9.3 as is provided - the USB system can reliably communicate with the device - you use the epkowa backend - you use the iscan frontend
See http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html and http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Hello, On Apr 27 11:09 Fergus Wilde wrote (shortened):
On Wednesday 27 April 2005 11:03, Johannes Meixner wrote:
In Suse Linux 9.3 we have the package iscan-1.13.1.1 included
... I have tried the updated iscan ...
I know that you even tried a new installation of 9.3 but I also worte:
... it should work o.k. under Suse Linux 9.3 as is provided - the USB system can reliably communicate with the device
As far as I see this is the problem in your case but I don't know how to slove it. But perhaps the newest Image Scan version from Epson Kowa which has changed to Epson Avasys and moved to http://www.avasys.jp/english/linux_e/index.html may work but from my point of view is it really unlikely that "Error during device I/O" is caused by the backend in particular because the problems in your case appeared since the major kernel version upgrade 2.4 -> 2.6 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wednesday 27 April 2005 11:32, Johannes Meixner wrote:
Hello,
On Apr 27 11:09 Fergus Wilde wrote (shortened):
On Wednesday 27 April 2005 11:03, Johannes Meixner wrote:
In Suse Linux 9.3 we have the package iscan-1.13.1.1 included
... I have tried the updated iscan ...
I know that you even tried a new installation of 9.3
but I also worte:
... it should work o.k. under Suse Linux 9.3 as is provided - the USB system can reliably communicate with the device
As far as I see this is the problem in your case but I don't know how to slove it.
But perhaps the newest Image Scan version from Epson Kowa which has changed to Epson Avasys and moved to http://www.avasys.jp/english/linux_e/index.html may work but from my point of view is it really unlikely that "Error during device I/O" is caused by the backend in particular because the problems in your case appeared since the major kernel version upgrade 2.4 -> 2.6
Yes, thanks, and point taken, Johannes - it's seeing at what point the scanner & USB systems disagree that is my problem, and I don't know where to start looking. As I said, lsusb and scanimage -L can find it, and the various scanner programs can see it and identify the model, etc. But the actual scanning fails ... something that has changed from 9.1 > 9.2 > 9.3 has stopped working, so I suppose the trick would be to identify that change and get it back to the happy working of 9.1, or at least the semi-happy working of 9.2. I've got the machine booted in 9.2 now, and have just been scanning without probs. Cheers Fergus
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Hello, On Apr 27 11:40 Fergus Wilde wrote (shortened):
... lsusb and scanimage -L can find it, and the various scanner programs can see it and identify the model, etc. But the actual scanning fails ... ... ... I've got the machine booted in 9.2 now, and have just been scanning without probs.
This is new. I thought it worked for you up to 9.0 and since 9.1 it had failed. Did I ever mention to use SANE debugging? See man sane-usb man sane-<backend> (i.e. man sane-epkowa in your case) For example when you use the epkowa backend for a USB scanner, do 1. without debugging scanimage -d epkowa -T && echo OK || echo FAILED 2. with debugging only regarding USB stuff export SANE_DEBUG_SANEI_USB=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB 3. with debugging only regarding epkowa backend stuff export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_EPKOWA 4. with debugging for both export SANE_DEBUG_SANEI_USB=128 export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB unset SANE_DEBUG_EPKOWA This does of course not solve the problem but it may show more details about the reason. But I guess all you get is some USB errors where I don't know how to solve them because I am no USB expert. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wednesday 27 April 2005 12:55, Johannes Meixner wrote:
Hello,
On Apr 27 11:40 Fergus Wilde wrote (shortened):
... lsusb and scanimage -L can find it, and the various scanner programs can see it and identify the model, etc. But the actual scanning fails ...
...
... I've got the machine booted in 9.2 now, and have just been scanning without probs.
This is new. I thought it worked for you up to 9.0 and since 9.1 it had failed.
Did I ever mention to use SANE debugging? See man sane-usb man sane-<backend> (i.e. man sane-epkowa in your case)
For example when you use the epkowa backend for a USB scanner, do
1. without debugging scanimage -d epkowa -T && echo OK || echo FAILED
2. with debugging only regarding USB stuff export SANE_DEBUG_SANEI_USB=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB
3. with debugging only regarding epkowa backend stuff export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_EPKOWA
4. with debugging for both export SANE_DEBUG_SANEI_USB=128 export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB unset SANE_DEBUG_EPKOWA
This does of course not solve the problem but it may show more details about the reason.
But I guess all you get is some USB errors where I don't know how to solve them because I am no USB expert.
Well, someone might be able to help - thanks for all your help, Johannes, will post anew when I have had the chance to try your advice. Best Fergus
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Hello, On Apr 27 14:14 Fergus Wilde wrote (shortened):
Well, someone might be able to help
Right now I got the information that USB problems are often caused by ACPI stuff (of course I am no ACPI expert at all), see http://portal.suse.com/sdb/en/2002/10/81_acpi.html and the related documents for this. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wednesday 27 April 2005 12:55, Johannes Meixner wrote:
Hello,
On Apr 27 11:40 Fergus Wilde wrote (shortened):
... lsusb and scanimage -L can find it, and the various scanner programs can see it and identify the model, etc. But the actual scanning fails ...
...
... I've got the machine booted in 9.2 now, and have just been scanning without probs.
This is new. I thought it worked for you up to 9.0 and since 9.1 it had failed.
Did I ever mention to use SANE debugging?
If so I didn't get the right idea - I have tried now and the resulting output is below. It clearly shows some messed up USB behaviour, and I would be very grateful if anyone could give me a clue how to fix it. Johannes has separately suggested turning off ACPI - doesn't make any difference. The failures are the same whether done as user or as root. Thanks for any input, sorry the output is tediously long Best Fergus
2. with debugging only regarding USB stuff export SANE_DEBUG_SANEI_USB=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB
3. with debugging only regarding epkowa backend stuff export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_EPKOWA
4. with debugging for both export SANE_DEBUG_SANEI_USB=128 export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa -T && echo OK || echo FAILED unset SANE_DEBUG_SANEI_USB unset SANE_DEBUG_EPKOWA
This does of course not solve the problem but it may show more details about the reason.
But I guess all you get is some USB errors where I don't know how to solve them because I am no USB expert.
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Bus 004 Device 003: ID 04b8:0112 Seiko Epson Corp. Perfection 2450 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 EHCI Host Controller (4) Manufacturer: Linux 2.6.11.4-20a-default ehci_hcd Serial #: 0000:00:1d.7 Manufacturer: EPSON Apr 27 09:54:02 pc11 kernel: usb 4-2: new high speed USB device using ehci_hcd and address 3 pc11:/home/fergus # 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=0x0112 [EPSON Scanner]) at libusb:001:002 # 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. pc11:/home/fergus # scanimage -L device `epkowa:libusb:001:002' is a Epson Perfection 2450 flatbed scanner pc11:/home/fergus # lsusb 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 pc11:/home/fergus # man epkowa No manual entry for epkowa fergus@pc11:~> scanimage -L 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). fergus@pc11:~> scanimage -L device `epkowa:libusb:001:002' is a Epson Perfection 2450 flatbed scanner fergus@pc11:~> scanimage -d epkowa -T && echo OK || echo FAILED scanimage: open of device epkowa failed: Invalid argument FAILED fergus@pc11:~> export SANE_DEBUG_SANEI_USB=128 fergus@pc11:~> scanimage -d epkowa -T && echo OK || echo FAILED [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: couldn't open /dev/usbscanner: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner1: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner2: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner3: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner4: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner5: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner6: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner7: No such device usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 001 on 004 usb_find_devices_on_bus: Couldn't open /dev/dsp1 usb_find_devices_on_bus: Couldn't open /dev/dsp2 usb_find_devices_on_bus: Couldn't open /dev/dsp3 usb_find_devices_on_bus: Couldn't open /dev/video usb_find_devices_on_bus: Couldn't open /dev/modem usb_find_devices_on_bus: Couldn't open /dev/cdrom1 usb_find_devices_on_bus: Couldn't open /dev/cdrom2 usb_find_devices_on_bus: Couldn't open /dev/cdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdram usb_find_devices_on_bus: Couldn't open /dev/dvdram2 usb_find_devices_on_bus: Couldn't open /dev/dvd1 usb_find_devices_on_bus: Couldn't open /dev/dvd2 usb_find_devices_on_bus: Couldn't open /dev/sr0 usb_find_devices_on_bus: Couldn't open /dev/sr1 usb_find_devices_on_bus: Couldn't open /dev/sr2 usb_find_devices_on_bus: Couldn't open /dev/sr3 usb_find_devices_on_bus: Couldn't open /dev/scanner usb_find_devices_on_bus: Couldn't open /dev/pilot usb_find_devices_on_bus: Couldn't open usb:any usb_find_devices_on_bus: Couldn't open /dev/usbscanner usb_os_find_devices: Found 001 on 003 usb_find_devices_on_bus: Couldn't open /dev/dsp1 usb_find_devices_on_bus: Couldn't open /dev/dsp2 usb_find_devices_on_bus: Couldn't open /dev/dsp3 usb_find_devices_on_bus: Couldn't open /dev/video usb_find_devices_on_bus: Couldn't open /dev/modem usb_find_devices_on_bus: Couldn't open /dev/cdrom1 usb_find_devices_on_bus: Couldn't open /dev/cdrom2 usb_find_devices_on_bus: Couldn't open /dev/cdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdram usb_find_devices_on_bus: Couldn't open /dev/dvdram2 usb_find_devices_on_bus: Couldn't open /dev/dvd1 usb_find_devices_on_bus: Couldn't open /dev/dvd2 usb_find_devices_on_bus: Couldn't open /dev/sr0 usb_find_devices_on_bus: Couldn't open /dev/sr1 usb_find_devices_on_bus: Couldn't open /dev/sr2 usb_find_devices_on_bus: Couldn't open /dev/sr3 usb_find_devices_on_bus: Couldn't open /dev/scanner usb_find_devices_on_bus: Couldn't open /dev/pilot usb_find_devices_on_bus: Couldn't open usb:any usb_find_devices_on_bus: Couldn't open /dev/usbscanner usb_os_find_devices: Found 001 on 002 usb_find_devices_on_bus: Couldn't open /dev/dsp1 usb_find_devices_on_bus: Couldn't open /dev/dsp2 usb_find_devices_on_bus: Couldn't open /dev/dsp3 usb_find_devices_on_bus: Couldn't open /dev/video usb_find_devices_on_bus: Couldn't open /dev/modem usb_find_devices_on_bus: Couldn't open /dev/cdrom1 usb_find_devices_on_bus: Couldn't open /dev/cdrom2 usb_find_devices_on_bus: Couldn't open /dev/cdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdram usb_find_devices_on_bus: Couldn't open /dev/dvdram2 usb_find_devices_on_bus: Couldn't open /dev/dvd1 usb_find_devices_on_bus: Couldn't open /dev/dvd2 usb_find_devices_on_bus: Couldn't open /dev/sr0 usb_find_devices_on_bus: Couldn't open /dev/sr1 usb_find_devices_on_bus: Couldn't open /dev/sr2 usb_find_devices_on_bus: Couldn't open /dev/sr3 usb_find_devices_on_bus: Couldn't open /dev/scanner usb_find_devices_on_bus: Couldn't open /dev/pilot usb_find_devices_on_bus: Couldn't open usb:any usb_find_devices_on_bus: Couldn't open /dev/usbscanner usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 usb_find_devices_on_bus: Couldn't open /dev/dsp1 usb_find_devices_on_bus: Couldn't open /dev/dsp2 usb_find_devices_on_bus: Couldn't open /dev/dsp3 usb_find_devices_on_bus: Couldn't open /dev/video usb_find_devices_on_bus: Couldn't open /dev/modem usb_find_devices_on_bus: Couldn't open /dev/cdrom1 usb_find_devices_on_bus: Couldn't open /dev/cdrom2 usb_find_devices_on_bus: Couldn't open /dev/cdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdrecorder2 usb_find_devices_on_bus: Couldn't open /dev/dvdram usb_find_devices_on_bus: Couldn't open /dev/dvdram2 usb_find_devices_on_bus: Couldn't open /dev/dvd1 usb_find_devices_on_bus: Couldn't open /dev/dvd2 usb_find_devices_on_bus: Couldn't open /dev/sr0 usb_find_devices_on_bus: Couldn't open /dev/sr1 usb_find_devices_on_bus: Couldn't open /dev/sr2 usb_find_devices_on_bus: Couldn't open /dev/sr3 usb_find_devices_on_bus: Couldn't open /dev/scanner usb_find_devices_on_bus: Couldn't open /dev/pilot usb_find_devices_on_bus: Couldn't open usb:any usb_find_devices_on_bus: Couldn't open /dev/usbscanner [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x0112) interface 0 at libusb:001:002 [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found 1 devices [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0101, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0103, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0104, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0106, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0107, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0109, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010a, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010b, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010c, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010e, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010f, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0110, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0112, attach=0x402680c4 [sanei_usb] sanei_usb_open: trying to open device `libusb:001:002' [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 1) [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2) [sanei_usb] sanei_usb_open: opened usb device `libusb:001:002' (*dn=0) [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, productID: 0x0112 [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] 0000: 1B 40 .@.............. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] 0000: 06 ................ [sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] 0000: 1B 49 .I.............. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 4 bytes [sanei_usb] 0000: 02 12 6A 00 ..j............. [sanei_usb] sanei_usb_read_bulk: wanted 4 bytes, got 4 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 106 bytes [sanei_usb] 0000: 42 38 52 32 00 52 3C 00 52 48 00 52 4B 00 52 50 B8R2.R<.RH.RK.RP [sanei_usb] 0010: 00 52 5A 00 52 64 00 52 78 00 52 85 00 52 90 00 .RZ.Rd.Rx.R..R.. [sanei_usb] 0020: 52 96 00 52 A0 00 52 AF 00 52 B4 00 52 C8 00 52 R..R..R..R..R..R [sanei_usb] 0030: D8 00 52 F0 00 52 0A 01 52 2C 01 52 40 01 52 5E ..R..R..R,.R@.R^ [sanei_usb] 0040: 01 52 68 01 52 90 01 52 E0 01 52 58 02 52 D0 02 .Rh.R..R..RX.R.. [sanei_usb] 0050: 52 20 03 52 84 03 52 B0 04 52 40 06 52 08 07 52 R .R..R..R@.R..R [sanei_usb] 0060: 60 09 52 80 0C 41 40 6A 40 92 `.R..A@j@....... [sanei_usb] sanei_usb_read_bulk: wanted 106 bytes, got 106 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] 0000: 1B 44 .D.............. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] 0000: 06 ................ [sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 1 bytes [sanei_usb] 0000: 10 ................ [sanei_usb] sanei_usb_write_bulk: wanted 1 bytes, wrote 1 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] 0000: 06 ................ [sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] 0000: 1B 66 .f.............. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 4 bytes [sanei_usb] 0000: 02 12 2A 00 ..*............. [sanei_usb] sanei_usb_read_bulk: wanted 4 bytes, got 4 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 42 bytes [sanei_usb] 0000: 05 00 00 00 00 00 80 00 32 C0 71 00 00 00 00 00 ........2.q..... [sanei_usb] 0010: 00 00 00 00 00 00 00 00 00 00 47 54 2D 39 37 30 ..........GT-970 [sanei_usb] 0020: 30 20 20 20 20 20 20 20 20 20 0 ...... [sanei_usb] sanei_usb_read_bulk: wanted 42 bytes, got 42 bytes [sanei_usb] sanei_usb_close: closing device 0 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0116, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0118, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011b, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011c, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011d, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011e, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0121, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0126, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0128, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0129, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x012a, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0801, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0802, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0805, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0806, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0807, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x080d, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x080e, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x080f, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0810, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0811, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0814, attach=0x402680c4 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0000, attach=0x402680c4 [sanei_usb] sanei_usb_open: trying to open device `libusb:001:002' [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 1) [sanei_usb] sanei_usb_open: we already have a bulk-in endpoint (address: 129), ignoring the new one [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2) [sanei_usb] sanei_usb_open: we already have a bulk-out endpoint (address: 2), ignoring the new one [sanei_usb] sanei_usb_open: opened usb device `libusb:001:002' (*dn=0) [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] 0000: 1B 40 .@.............. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes USB error: error reading from bulk endpoint 0x81: Connection timed out [sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out [sanei_usb] sanei_usb_close: closing device 0 scanimage: sane_start: Error during device I/O FAILED -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Fergus Wilde wrote:
fergus@pc11:~> export SANE_DEBUG_SANEI_USB=128 fergus@pc11:~> scanimage -d epkowa -T && echo OK || echo FAILED [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: couldn't open /dev/usbscanner: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner1: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner2: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner3: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner4: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner5: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner6: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner7: No such device
Do you have the above devices in your /dev tree? Perhaps udev is not creating the devices. I'm still running 9.2, but if that is the case, perhaps you could make a udev rule to create the device. Not sure exactly how it works in 9.3 though. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Thursday 28 April 2005 12:36, Joe Morris (NTM) wrote:
Fergus Wilde wrote:
fergus@pc11:~> export SANE_DEBUG_SANEI_USB=128 fergus@pc11:~> scanimage -d epkowa -T && echo OK || echo FAILED [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: couldn't open /dev/usbscanner: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner1: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner2: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner3: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner4: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner5: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner6: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner7: No such device
Do you have the above devices in your /dev tree? Perhaps udev is not creating the devices. I'm still running 9.2, but if that is the case, perhaps you could make a udev rule to create the device. Not sure exactly how it works in 9.3 though.
Hi Joe, thanks for getting back - I've got this: crw------- 1 fergus root 180, 48 2004-10-02 09:38 /dev/usbscanner Do you know if that looks right? I don't understand USB at all - cheers, Fergus
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Fergus Wilde wrote:
Hi Joe, thanks for getting back - I've got this: crw------- 1 fergus root 180, 48 2004-10-02 09:38 /dev/usbscanner
Do you know if that looks right? I don't understand USB at all - cheers,
Yea, it looks right for resmgr accessed device, and it is there. After reading Johannes' message, I guess I am wrong, it does not access it via the device but via libusb, and it looked like it is found but cannot communicate. I would guess maybe the backend, epkowa, has problems communicating via libusb instead of a device, but that is purely a speculative guess based on my limited experience. Maybe check out http://www.avasys.jp/cgi-bin/lx/bbs/en/scanner-bbs/hyperbbs.cgi?mode=view;Co... and since it was mentioned, it wouldn't hurt to check the source to make sure it was compiled with the --with-libusb option (though I would be fairly sure SuSE would have, but worth double checking). HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Hello, On Apr 28 09:09 Joe Morris (NTM) wrote (shortened):
maybe the backend, epkowa, has problems communicating via libusb
But it works well for me (using a new installed 9.3 and an Epson Perfection 1240U). And up to now Fergus' report is the only ony I know about with this kind of problem - for other known problems see http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html I don't think epkowa has a problem with libusb. I think it is not backend-related at all. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Thu April 28 2005 10:19 am, Johannes Meixner wrote:
But it works well for me (using a new installed 9.3 and an Epson Perfection 1240U).
WOW ! I am now able to scan using my Epson Perfection 4180 Photo scanner!! This is great, now I am REAL happy I bought that model. and glad I upgraded to SUSE 9.3 ! -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
Hello, On Apr 28 13:14 Paul Cartwright wrote (shortened):
I am now able to scan using my Epson Perfection 4180 Photo
With this model (and some others) there should be the problem that it doesn't work with "scanimage" (resulting some confusion when setting it up with YaST), but I have made a new "iscan" package for 9.3 - see http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html Unfortunately ;-) I don't have one of these scanners which don't work with "scanimage" so that I cannot test it on my own. Therefore I would be happy to get feedback whether the new "iscan" package has more or hopefully less problems. In particular please test whether scanimage -L finds it and whether scanimage -d epkowa -T && echo OK || echo FAILED is successful. If you have time then remove the old "iscan" package before you install the new one so that you have to set it up anew. Then do the setup with YaST and test whether it works well, in particular whether YaST shows it as active scanner and whether YaST can test it. Many Thanks and Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hello, only some more notes but no solution... On Apr 28 11:34 Fergus Wilde wrote (shortened):
pc11:/home/fergus # lsusb ... Bus 001 Device 002: ID 04b8:0112 Seiko Epson Corp. Perfection 2450
remember this because it shows what and where it really is
fergus@pc11:~> export SANE_DEBUG_SANEI_USB=128 fergus@pc11:~> scanimage -d epkowa -T && echo OK || echo FAILED [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: couldn't open /dev/usbscanner: No such device [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
it tries to detect the scanner at all possible USB connections i.e. ignore the many failed arttempts for USB connection types where in fact the scanner is not connected to
[sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x0112) interface 0 at libusb:001:002
it found it (see above what we remembered)
[sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0112, attach=0x402680c4
it detected that it is one of the known scanners of the backend
[sanei_usb] sanei_usb_open: opened usb device `libusb:001:002' (*dn=0)
it was able to access the scanner now some read/write operations happen . . . until it fails:
USB error: error reading from bulk endpoint 0x81: Connection timed out [sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out [sanei_usb] sanei_usb_close: closing device 0 scanimage: sane_start: Error during device I/O FAILED
I don't know why the "Connection timed out". When I do with my "Perfection 1240U" export SANE_DEBUG_SANEI_USB=128 scanimage -d epkowa -T && echo OK || echo FAILED I get a very much longer log with read/write operations so that it seems in your case the communication breaks down at some (perhaps random) time during the read/write operations but I don't know why this happens. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wed April 27 2005 6:03 am, Johannes Meixner wrote:
The epson.desc (description for the epson backend) shows that the "Perfection 4180" is "unsupported".
Therefore it should work o.k. under Suse Linux 9.3 as is provided - the USB system can reliably communicate with the device - you use the epkowa backend - you use the iscan frontend
this is exciting news !! I have 9.3 setup on a separate partition, but I haven't moved my 9.2 over to it yet... I'm trying to wait for a good time to break the news to my wife:) she doesn't like change. -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
Hello, On Apr 26 11:17 James Wright wrote (shortened):
... vi /etc/hotplug/usb/libsane.usermap
For scanners this is no longer needed since Suse Linux 9.2. We had it up to 9.1 to grant access for normal users via resmgr, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html Plain scanner device access via libusb via /proc/bus/usb/ or via /sys/bus/usb/devices/ does not need hotplug/usb/*.usermap. This would be needed if the device would need a special kernel module to be loaded for device access which is not necessary for USB scanners. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Tuesday April 26 2005 4:13 am, Fergus Wilde wrote:
Not quite a repeat of my former message under subject
Anyone got any oddness to report in 9.3 USB, or with particular boards? Anyone now any usb tricks to try? Anyone got a happy set up with this scanner or similar model? Cheers Fergus
Hello Fergus. I have a 2400 Photo working on 9.3 using the epkowa package (Yast shows it as the same one the 2450 needs. I set it up using Yast. I have to unplug it and plug it back in to get it to work each time I want to use it. Rich. Rich -- Rich Matson Reno, Nv. USA
participants (6)
-
C. Richard Matson -
Fergus Wilde -
James Wright -
Joe Morris (NTM) -
Johannes Meixner -
Paul Cartwright