[sane-devel] Epson Perfection 1650 vs RedHat 7.2: not seen?

[JJ Behrens]

Karl,

Thanks for your response.

> The scanner should show up in 'cat /proc/bus/usb/devices' even 
> when no scanner driver is loaded. 

Hmm, you can't do that in FreeBSD 4.4 :)

> I suspect that something is
> wrong with your cable. You write that you tried both ports, 
> can you also try a different cable? 

Actually, the scanner works successfully under Winblows 2000.

> Before you can run any Sane frontend, you need to see the 
> scanner in the devices list. 

tcp# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found USB scanner (UNKNOWN vendor and product) at
device /dev/uscanner0

# `UNKNOWN vendor and product' means that there seems to be a scanner
# at this device file but the vendor and product ids couldn't be
# identified. Currently identification only works with Linux versions
# >= 2.4.8.

tcp# 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).

> Depending on how recent your kernel is, you may not have to
> provide the vendor and product ids as paramaters to modprobe.
> Once the scanner shows up, try to load the scanner module
> without any parameters. If the entry in devices lists the
> scanner driver, you are all set, if it does not list the
> driver, then add the IDs.

Hmm, please correct me if I'm wrong, but I think this is different in
FreeBSD. FreeBSD uses a .h file that lists all of the device ID's that
should be treated as scanners. My earlier email explains that I had to
modify this list to support my scanner, but my changes mirrored those of
the Epson Perfection 1640 and were based on an email regarding running the
Epson Perfection 1640. When I plug the scanner in, I get the following in
/var/log/messages:

Jan 24 19:06:13 tcp /kernel: uscanner0: EPSON EPSON Scanner, rev
1.00/1.08, addr 2

Furthermore, the call to open works when I did a kernel trace. I think
that it's the next call to ioctl that is messing things up.

Karl, thanks for helping me recheck all of these various things.

-jj