Epson scanners iscan and sane/xsane howto FC3

[bgidney]

:) --- 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

:) I have tested both the flabed and TPU using iscan and xsane from Gimp. I encountered no problems with my scanner (3170). TPU scan times are longer and warmup times, for TPU and flatbed, are longer then I previously encountered but this is more inline with functionality under Windows XP. :)

[zipper]

I'm trying to configure my scanner (Epson 1260 Photo) using your instructions and have run into a problem. All is well up to step 7. When I enter this command, line P says, "P: Vendor=0000 ProdID=0000 Rev= 2.06." instead of P: Vendor=04b8 ProdID=0116 Rev =1.00 as you say in the instructions. Any suggestions?

[zipper]

Ignore my previous post. I repeated the instructions and this time I found my scanner in the list and am continuing on. Sorry.

[pkands]

Excellent! Works great.

[bgidney]

zipper - I am glad it worked out for you. Is there anythig in the instructions that could be reworded to make it clearer?

pkands - In your opinion are the instructions easy to follow?

I will attempt to keep this howto up to date and will refine the instructions based on input from all to make it as easy to follow and clear as is possible.

Thank you all!

[zipper]

Thanks bgidney for your help, but I'm still having problems. I followed all 22 steps as listed in your original post. The instructions are clear and easy to follow. I restarted my computer and logged back in. I unplugged the scanner and USB cables and plugged them back in. The scanner is on. In terminal I entered "iscan," and got an error message from iscan which says, "Could not send command to scanner. Check the scanner's status."

Any idea what I'm doing wrong?

[bossfrog]

One possiblity is that you did not complete Bruce Gidney's instruction #15 (commenting out /dev/usb/scanner0 in /etc/sane.d/epkowa.conf and adding a line: usb, or usb followed by the vendor and product ID numbers).

[bossfrog]

Thank you, bgidney, for your instructions.

I found that I did not need to use instructions #16-22 in order to have a fully functional iscan. I installed the latest iscan (iscan-1.12.0-4.i386.rpm). I only plug in my scanner after I have already logged on to my PC as a user; this seems to take care of any permission problems. I am using FC3 and have an Epson Perfection 1660 Photo scanner.

[bgidney]

zipper - bossfrog is right, if you do not complete step 15 (or do not put in your scanner's id instead of mine in the example) you will get that precise message.

bossfrog - thanks for the information on iscan-1.12.0-4, it seems (from your experience) that they have solved the issues with the libraries making steps 16 - 22 unessecary. I updated to iscan-1.12.0-4 and noted that all I needed to do was re-edit /etc/sane.d/epkowa.conf .

Has anyone else had the same experience as bossfrog?

[Finalzone]

I found out Epson is widely supported on Linux distros than let's say Canon. I am considering to change all-in-one printer.

[dwdrumrboy]

bgidney, thank you for the step-by-step, unfortunately I am still having problems as well. I am running FC3, with the 2.6.9-1.681_FC3smp kernel.

A note, instead of completing the steps as super do "sudo", I executed them as root. Any problems with completing the steps as root?

I installed the iscan-1.12.0-4.i386.rpm and received no errors.

When I lauch iscan from bash, iscan loads, but the scanner does not initialize and the bulb doesn't light up. I receive the error message "Could not send command to the scanner. Check the scanner's status".

Gimp 2.0 just hangs at the "Initalizing Plugins". I created a symbloic link as my regular user: ln -s /usr/bin/iscan ~/.gimp-2.0/plug-ins/.

Being fairly new at Linux, I read in varoius forums about running "modprobe" and looked at the man pages, but wasn't sure if I needed to do this or even how to correctly do this. Do I need to look at the devices, if so - how? Since I got g4u to work properly, I guess I shouldn't worry too much.

In the hardware browser, I see the Epson scanner listed under "System Devices", but the driver is "unknown".

The main item, as compared to XP (which the scanner works fine), is that the scanner itself is not initalizing, hence the error messgaes. Any assistance would be greatly appreciated.

Thanks - dwdrumrboy

CPU: Dual Xeon 2.8 GHz
Motherboard: SuperMicro X5DAL-TG2
Memory: 1 GB ECC DDR-266 (PC2100)
Storage: Maxtor 120 GB SATA, WD 80 GB SATA, WD 80 IDE, 36 GB IBM U320 SCSI
Optical: Yamaha CRW-F1, Sony RW DRU-700A, Pioneer DVD-305S
Video: Nvidia GeForce FX 5200 (Generic driver)
Sound: Creative SB Live! Platinum
OS: Fedora Core 3 (2.6.9-1.681_FC3smp) and Windows XP Professional SP2

[zipper]

Hi bgidney. I'm still having trouble with getting my Epson Perfection 1260 Photo scanner to work using the above instructions. I've followed everything to the letter, except the sudo commands. I'm not familiar with sudo so please be patient. Here's what happens. I complete steps 1 & 2 above. In the terminal window I am not logged in as su. I enter "sudo vi ...." and I am asked for a password. Neither my regular login password or my root password works. Is there something else I need to set up first?

I logged in as su, and then entered all of the steps exactly as listed, except for step 16 & 17, because I am already logged in as root. Should these steps work even if I enter all steps as su?

Thanks for answering my questions.

[bgidney]

All - It appears that iscan-1.12.0-4 has broken my configuration. iscan will open but does not activate scanner. I am working on this and will post as soon as I resolve it.

[zovirl]

Zipper, I found an easier way to get my 1260 scanner to work:
http://www.fedoraforum.org/forum/showthread.php?t=28218

Hopefully it will still work for you after installing all that other stuff :)

[trigpoint]

I have followed the above instructions and have iscan-1.12.0-4 installed on fedora core 3.

I can now get into iscan, when I press preview, the "waiting for scanner to warm up" message appears the scanner moves, then it hangs leaving the warming up message.

Any ideas.

Thanks

[pkands]

bgidney,
1.12 broke me and I can't figure it out.
And yes, I thought your instructions were clear.
pkands

[bgidney]

pkands
I just downloaded and installed iscan-1.13.0-3.i386.rpm and it works! I tried many things and was in the process of building a custom rpm. I even reloaded my system twice in the testing. Because of the reloads I do not know if 1.13 will straighten out the 1.12 install. Try it and post your results.
Bruce

[pkands]

Yes it now works although it seems as though it has to think about it for a while--pauses for several seconds before scanning. I had to remove the ID from epkowa.conf--only have "usb" now. Is that the same for you?
John

[bgidney]

Actually I have everything as in the original post. I do notice a longer than before pause when I start iscan but xsane is actually faster and no longer gives me 2 choices for the scanner, before it would give me a standard epson and the epkowa entry.

I am going to do a full test with TPU, color, grayscale, etc. This is what I did when I first strated the howto. I will be doing this in the morning, my usual time for my endeavors.

Bruce

[trigpoint]

It works.

I have gone for a clean install of FC3, as I don't know how much mess I made of the config.

Before trying the scanner I allowed the system to be fully updated and installed kernel-2.6.9-1.715_FC3.

xsane worked as root with no tweaking. iscan-1.13.0-3 required the scanner line in epkowa.conf to be changed to usb.

:confused: Now to sort out permissions so I can run as a user :confused: This used to be easy, don't I just love :eek: udev :eek:

[bgidney]

trigpoint,
If you follow the guide on the first page it will walk you through all the steps to set user permissions and steps 19 on take care of sane/xsane.

[pointym5]

I've got FC2 (2.6.10-1.9_FC2 kernel) and iscan 1.13, all sane stuff up-to-date, and my 2450 does not want to work at all. I get symptoms reported elsewhere in this thread: very long delays in iscan and xsane when trying to do anything, followed eventually by one or another error dialogs. The programs know the scanner's a 2450, but nothing is ever able to get its light on.

I noticed a post from last year in the epkowa forms from one of the developers, who reported discovering that the 2450 (and possibly other models) don't behave as the driver expects, leading to timeouts and complete non-functionality.

[drunkahol]

This all worked well for me under FC3, but I'm now having problems with FC4.

Don't know if it's the FC4 upgrade that's the issue, or the fact that I went to x86_64 instead of i386 this time.

Scanner: Epson Perfection 2480
Downloaded: iscan-1.15.0-2.i386.rpm

I tried the tarball previous to this to compile a 64-bit iscan, but the build failed beyond my capabilities to fix.

I completed all the steps (1 through to 25) and logged out and back in.

When I open a terminal window now, however, I get the following:

ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
[duncan@desktop ~]$


The only area of confusion I had in the steps were steps 14 & 15. I found a line that exactly matched my scanner, Vendor & ProdID, so I left it alone.

Can anyone shed any light on my problem?

Cheers

Duncan

Edit:

The iscan application works fully when run from the command line.
GIMP starts iscan during the plugin load phase, but this seems to hang until you close down that instance of iscan.
Xsane from command line reports "No devices available".
GIMP reports the same when you attempt to acquire an image via xsane device dialog.

[geerten]

FC 4, Epson Perfection 1260 Photo with TPU.

Works great for photos with iscan, but got "Could not send commands to scanner" when trying to scan negatives. However TPU is working because Kooka with plustek back-end works (poor quality though :( ).

Solution: comment plustek from /etc/sane/dll/conf :)

Reason: The plustek driver sits in the way??

[captv564]

Have a 3170 that won't work on FC5. Do these instructions work on FC5 also?

[Blisk]

I have tryed this but scanner doesn't work.
I tryed everything but doesn't work I tryed to install even sane-plustek, but there are really poor manual how to do and I didn't make it.
I installed sane with rpm and with compilinga and it is the same I have installed FC7 and hotplug, scanner is Genius HR6X which is supported by sane-plustek.
Can someone help me?


When I run
sane-find-scanner -v
found USB scanner (vendor=0x0458, product=0x2019, chip=GL646) at libusb:002:006

after that I run
export SANE_DEBUG_DLL=12
export SANE_DEBUG_SANEI_USB=255
export SANE_DEBUG_PLUSTEK=12
after that I run
scanimage -L

and get this
[sanei_debug] Setting debug level of dll to 12.
[dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.0.18
[dll] sane_init: reading dll.conf
[dll] add_backend: adding backend `plustek'
[dll] sane_get_devices
[dll] load: searching backend `plustek' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-plustek.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-plustek.so.1'
[dll] init: initializing backend `plustek'
[sanei_debug] Setting debug level of plustek to 12.
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: Looking for kernel scanner devices
[sanei_usb] sanei_usb_init: Looking for libusb devices
usb_set_debug: Setting debugging level to 255 (on)
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 003
usb_os_find_devices: Found 006 on 002
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: found libusb device (0x0458/0x2019) interface 0 at libusb:002:006
[sanei_usb] sanei_usb_init: device 0x046d/0xc30f, interface 0 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x046d/0xc30f, interface 1 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x046d/0xc30f: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x046d/0xc040, interface 0 doesn't look like a scanner (0/3)
[sanei_usb] sanei_usb_init: device 0x046d/0xc040: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x03f0/0x6004, interface 0 doesn't look like a scanner (0/7)
[sanei_usb] sanei_usb_init: device 0x03f0/0x6004: no suitable interfaces
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: found 1 devices
[plustek] Plustek backend V0.51-12, part of sane-backends 1.0.18
[plustek] Retrieving all supported and conntected devices

[sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2220
[sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x6620
[plustek] Available and supported devices:
[plustek] NONE.
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] ># or<
[plustek] ># device libusb:bbb:ddd<
[plustek] ># where bbb is the busnumber and ddd the device number<
[plustek] ># make sure that your user has access to /proc/bus/usb/bbb/ddd<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] ># [usb]<
[plustek] ># device /dev/scanner<
[plustek] >#<
[plustek] ># or simply<
[plustek] ># [usb]<
[plustek] >#<
[plustek] ># or if you want a specific device but you have no idea about the<
[plustek] ># device node or you use libusb, simply set vendor- and product-ID<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device auto<
[plustek] >#<
[plustek] ># NOTE: autodetection is safe, as it uses the info it got<
[plustek] ># from the USB subsystem. If you're not using the<
[plustek] ># autodetection, you MUST have attached that device<
[plustek] ># at your USB-port, that you have specified...<
[plustek] >#<
[plustek] ><
[plustek] >[usb] 0x0458 0x2019<
[plustek] next device is a USB device (0x0458-0x2019)
[plustek] ... next device
[plustek] >device /dev/scanner<
[plustek] Decoding device name >/dev/scanner<
[plustek] ><
[plustek] >#<

[plustek] attach (/dev/scanner, 0xbfe64bb8, (nil))
[plustek] Device configuration:
[plustek] device name : >/dev/scanner<
[plustek] USB-ID : >0x0458-0x2019<
[plustek] model ovr. : 0
[plustek] warmup : -1s
[plustek] lampOff : 300
[plustek] lampOffOnEnd : yes
[plustek] cacheCalData : no
[plustek] altCalibrate : no
[plustek] skipCalibr. : no
[plustek] skipFine : no
[plustek] skipFineWhite: no
[plustek] invertNegs. : no
[plustek] dis.Speedup : no
[plustek] pos_x : 0
[plustek] pos_y : 0
[plustek] pos_shading_y: -1
[plustek] neg_x : 0
[plustek] neg_y : 0
[plustek] neg_shading_y: -1
[plustek] tpa_x : 0
[plustek] tpa_y : 0
[plustek] tpa_shading_y: -1
[plustek] red gain : -1
[plustek] green gain : -1
[plustek] blue gain : -1
[plustek] red offset : -1
[plustek] green offset : -1
[plustek] blue offset : -1
[plustek] red lampoff : -1
[plustek] green lampoff: -1
[plustek] blue lampoff : -1
[plustek] red Gamma : 1.00
[plustek] green Gamma : 1.00
[plustek] blue Gamma : 1.00
[plustek] gray Gamma : 1.00
[plustek] ---------------------
[plustek] usbDev_open(/dev/scanner,0x0458-0x2019) - (nil)
[sanei_usb] sanei_usb_open: trying to open device `/dev/scanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/scanner' in list
[plustek] sanei_usb_open failed: No such file or directory (2)
[plustek] open failed: -1
[dll] init: backend `plustek' is version 1.0.0
[plustek] sane_get_devices (0xbfe66cf8, 0)
[dll] sane_get_devices: found 0 devices

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).
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `plustek's exit function
[plustek] sane_exit
[dll] sane_exit: finished

[Finalzone]

Check out sane-plustek page (http://www.sane-project.org/man/sane-plustek.5.html)/