Scanning with Epson

[David Fletcher]

Just tried plugging my scanner into the fc5t3 machine. Can't get it to do a 
thing.

The scanner is an Epson Perfection 2450 Photo, connected to USB.

There is no scanner entry in the graphics menu, and when I run command xsane 
nothing happens.

I also installed iscan, which says "Could not send command to scanner. Check 
the scanner's status"

The scanner appears in /dev/ as scanner-usbdev1.x

Any ideas for me to try?

Dave Fletcher

[glenn]

David Fletcher wrote:
> Just tried plugging my scanner into the fc5t3 machine. Can't get it to do a 
> thing.
>
> The scanner is an Epson Perfection 2450 Photo, connected to USB.
>
> There is no scanner entry in the graphics menu, and when I run command xsane 
> nothing happens.
>
> I also installed iscan, which says "Could not send command to scanner. Check 
> the scanner's status"
>
> The scanner appears in /dev/ as scanner-usbdev1.x
>
> Any ideas for me to try?

I also have an Epson 2450 scanner and running it on FC5T3.  I use the 
driver that I was using under FC4 (esfw41.bin is from a windoze distro).

In my case I happen to load esfw4esfw41.bin in file in my 
/root/downloads directory, so I made an edit to 
/etc/sane.d/snapscan.conf to provide a link to the driver
   firmware /root/downloads/esfw41.bin

Hope this gets you going.

[Gerry Tool]

On Sun, 2006-02-26 at 16:07 +0000, David Fletcher wrote:
> Just tried plugging my scanner into the fc5t3 machine. Can't get it to do a 
> thing.
>
> The scanner is an Epson Perfection 2450 Photo, connected to USB.
>
> There is no scanner entry in the graphics menu, and when I run command xsane 
> nothing happens.
>
> I also installed iscan, which says "Could not send command to scanner. Check 
> the scanner's status"
>
> The scanner appears in /dev/ as scanner-usbdev1.x
>
> Any ideas for me to try?

You can try as root:
[root@fc5t3 ~]# sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make
sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0119 [EPSON
Scanner]) at libusb:007: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.

If it gives you the usb device numbers for your system as above, then

[root@fc5t3 ~]# ls -l /proc/bus/usb/007/002
-rw-rw-rw- 1 root root 50 Feb 25 09:04 /proc/bus/usb/007/002

where you replace the /007/002 with the numbers sane-find-scanner
provided.

If the permissions are not as above, then

[root@fc5t3 ~]# chmod a+w /proc/bus/usb/007/002

for your particular device numbers.

If you are lucky, the scanner will now work.  If it doesn't, please file
a bug report.  You can see my bug report for my Epson Perfecition 4490
Photo scanner at bugzilla #182210.  My problem may be because this is a
newly supported scanner, but if you find the same thing happening, the
bug will get fixed faster if you add your input or file an additional
report.

Thanks.  Good Luck.

Gerry

[David Fletcher]

On Sunday 26 Feb 2006 17:49, Gerry Tool wrote:
> If you are lucky, the scanner will now work.  If it doesn't, please file
> a bug report.  You can see my bug report for my Epson Perfecition 4490
> Photo scanner at bugzilla #182210.  My problem may be because this is a
> newly supported scanner, but if you find the same thing happening, the
> bug will get fixed faster if you add your input or file an additional
> report.
>
> Thanks.  Good Luck.
>
> Gerry

There is a bug report 149027 which sounds like the same problem I've got. I've 
added my 2d worth to it.

Due to previous problems with this scanner on FC3, I am suspicious of the 
current libusb. That was before I joined Fedora Documentation and Bugzilla so 
I didn't get around to reporting it properly, but I don't really want to get 
into fighting with FC5 to implement the same work-around.

Dave