xsane problems with F20 and Epson 3490 photo
Hello All,
I have been using this scanner with xsane (via gimp) for quite a long time, generally with few problems. The most notable being occasionally the xsane preview window would open blank or corrupted but a good workaround was to delete ~/.sane dir, start again and all was OK. It has been quite a while since I had need to use the scanner so not sure when my current problems commenced. I am currently running an up to date F20 x86_64 system, which includes Xsane 0.999. Starting the scanning process, via gimp -> create Xsane Device dialog is quite erratic...sometimes works, sometimes not. When it fails I get a message "no devices found", or words to that effect. When it works, the Xsane windows open and I get a preview scan OK, but when I then choose "scan" I get an error message "Error failed to start scanner: Error during device I/O". In case it helps those in the know to understand what might be going on here, I report the following sequence of events and their outcome. (1) scanner on (2) boot F20, scanner initialises (ie scan head motor sounds like it resets its position) (3) run Simplescan (v3.1.3), scans page OK. (4) run gscan2pdf (v6.2.3), "no devices found". (5) run gimp -> create Xsane device dialog, "no devices available". (6) delete ~/.sane, repeat (5), same result. (7) restart F20, scanner initialises. (8)gimp -> create Xsane device dialog, long wait then Xsane windows open, acquires preview, then "scan" gives " Error failed to start scanner:Error during device I/O". I have checked my /etc/sane.d/snapscan.conf, which points to the driver /usr/share/sane/snapscan/esfw52.bin, and it is as-was when the whole business was working with little or no trouble. Following advice I saw elsewhere re similar problem, have created a "scanner" group, added myself to that group and then given group permission to /dev/bus/usb/003/003 (my scanner is device 003 on bus 003), but to no avail as it has not made any difference...but I may have done this last bit incorrectly, not sure. Anyone have any advice or need more info to fix this? Cheers, Terry |
Hi:
See if maybe Epson has a Linux driver for your printer/scanner- http://www.epson.com/cgi-bin/Store/s...rm=OSF_O_LINUX http://www.epson.com/cgi-bin/Store/s...portIndex.jsp? Maybe you need a sane backend drivers for your Epson. http://www.sane-project.org/sane-backends.html Aside from that the only other things I can think of is check the cable (usb) if that's how your printer/scanner connects to your pc and ensure that the connections are good. If your printer connects via WiFi it could be a cups issue- http://www.freebsd.org/doc/en/articl...-printers.html Everytime I have a power outage or a bad thunderstorm with lightning I have to go online, delete the printer and than use the terminal to add it again in order for the printer or scanner to work. http://localhost:631/ Hope that helps. |
Quote:
Quote:
Quote:
Quote:
Quote:
Cheers, Terry |
Your Welcome; I gave it my best go-
|
I would like to resurrect this thread...still having problems and not found a solution.
What I find strange, or odd, is that the combination of Epson 3490 photo scanner (USB), the Epson binary driver (esfw52.bin) installed in /usr/share/sane/snapscan/ with the appropriate detail added to /etc/sane.d/snapscan.conf has been working flawlessly with Fedora linux for as long as I can remember (many years), and now I have these problems. I suspect that something has changed in Xsane or Fedora, but if this is the case surely others would have similar problems? Does anyone have any helpful advice on the problem I have outlined in this thread? |
This is really driving me around the bend!
I think I have found (almost) every story about how to configure sane for this scanner, and check/rechecked the config files, but it still doesn't work. After a system reboot, I can run "scanimage -L" and it finds the scanner OK, and I can run "sane-find-scanner" and that too reports the correct stuff. If I then start gimp and use "file->create xsane dialog" the xsane windows all open OK. I can then select "preview" and the scanner does a preview scan, but when I then select "scan" there is a long delay and " Error failed to start scanner:Error during device I/O". Any attempts to do a preview scan or run "scanimage -L" or "sane-find-scanner" after that all result in a failure...but I can repeat the process OK after a reboot. This suggests to me that maybe something goes haywire with the USB communications after Xsane does a preview...but this is a bit of a guess. I don't think it is a hardware problem. I have installed "Vuescan" (a review copy) and this will do a number a scans OK immediately after a reboot, but won't scan after Xsane has done a preview scan and failed to do then do a scan. Given the history, it also suggests that something that affects this in either Xsane or Fedora has changed, but I have no idea where to look. Is there anyone reading this who knows about this stuff who can help? |
I don't know how to solve this printer issue that you have going on.
In fact I find it quite puzzeling till I saw this: Quote:
Input/output error could mean that the communication between the printer and the cable may not be working at some point. I had an error last week: problems occur between the communication of the disk and the host I found out that the cable to my HDD wasn't seated all the way down. It's acting up again leading me to believe the cable might be bad. It it 5 years old. I asked one of our Moderators to join your thread. |
Thanks for joining this thread.
The USB cable looks like it might be a special for this scanner, not sure. I haven't seen another like it before, it has cylindrical devices, about 25mm long, 12mm dia near each end. I happened to have an unused USB cable from an Epson printer, and fitted that. After a reboot, "scanimage -L" reports correctly, as does "sane-find-scanner". Start gimp and "File -> Create -> Xsane: device dialog" pops up a dialog box saying "scanning for devices" and sometime later says" "no devices found". Repeating this gives the same result. At this point "scanimage -L" fails, but "sane-find-scanner" reports correctly. I try Vuescan, which takes an age to start, and when asked to scan it exits...poof! Refit the old cable, same results as with the new cable. This is all very confusing to me. Hopefully I haven't ended up with some crook config files as a result of all my previous troubleshooting. I'll have a look at documenting the "correct" setup and what I have to delete and re-install to start completely from fresh. If any of the results of this trial with new USB cable give someone in the know any clues, I look forward to hearing about them. Cheers, Terry |
I got called in to see if I could help diagnose things, so let's see:
Quote:
Code:
lsusb 2) Post any configs you have changed (manually or via a User Interface) like /etc/sane.d/epson.conf etc, etc. Also add any steps you took, between noticing the error for the very first time and now, to "correct"' things. Permisssions, ownership, anything. |
3 Attachment(s)
Quote:
The results of the tests (at 0. above) are in attached file "sane_root_tests.txt". Quote:
Re-ran tests (at 0. above, results in attached file "sane_root_tests2.txt". Nothing USB/sane related in /var/log/messages, /var/log/audit/audit.log does not exist. Quote:
I have the epson firmware file "esfw52.bin" in /usr/share/sane/snapscan/ and I have changed permissions on this file (chmod 777). Apologies if I have missed any of your requested info, or obtained it incorrectly. Hope this helps, and thanks for your help. Cheers, Terry |
I'm having the same problem with my Epson perfection 4490 Photo. It used to work just fine, but has problems similar to those described above on any kernel newer than 3.10. I don't know if something changed in the kernel or the sane environment, but what used to work no longer does.
My 4490 still works with the VueScan front end (http://www.hamrick.com/). The Epson/Epkowa iscan files and proprietary driver still have to be installed even though they don't function. VueScan is commercial software, but you can run it in trial mode for no cost to determine if VueScan is a viable solution |
Code:
[root@localhost terry]# lsusb Code:
checking /dev/scanner... Code:
[root@localhost terry]# scanimage -L Code:
[root@localhost terry]# scanimage -vvv -T Code:
[root@localhost terry]# scanimage -vvv --format tiff > /tmp/scan2.tiff |
epsonconf file:
Code:
# SCSI scanner: Also I noticed that all of the arguments in the 'epsonconf file' all of the arguments are commented out. Is is possibly unSpawn that (usb /dev/usbscanner0 or usb /dev/usb/scanner0) should be un-commented? |
Quote:
What it does have is /dev/bus/usb/001/, .../002/, .../003/, .../004/ and each of those dirs have files 001, 002 etc, with no sign of a "scanner0". I have no idea what this means. usb isn't commented out in my epson.conf. Cheers, Terry |
Quote:
Configuration files assist process and devices that we want to work. (aside from drivers assisting the hardware) I wonder if it is as simple as adding an argument to the file you already have? (Again let's see what unSpawn suggest's) I called on him because he has more experience and I trust him. It could also be that sane needs to be updated. Maybe updating will help. Just run: su -c 'yum update xsane' and see if it helps. Another thing that I found out while I was looking up all the details of sane is that The binary driver needs a libsane.dll from Sane version 1.0.16 or later. A fancy name for the backend driver I think. Is this the place where you downloaded your binary driver here? http://rpm.pbone.net/index.php3?stat...sane&srodzaj=3 |
All times are GMT -5. The time now is 10:13 PM. |