Originally Posted by brahms
OK. First we have to find out if this is a SANE (scanner) problem or a USB problem.
Any sign of your scanner there? If not, it's a USB problem. Check by tailing the system messages log while you unplug and replug the scanner.
(enter root password)
tail -f /var/log/messages &
There should be some sign of activity.
If you do see your scanner here, go back to the root CLI and type
Does the script find your scanner as root? If so, try
If this works, then try the previous two steps as a non-root user. If they don't work here then it's likely a permissions problem. Let us know how you go.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 1606:1030 Umax [hex]
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 03f0:3a02 Hewlett-Packard
Bus 002 Device 002: ID 045e:0053 Microsoft Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Thus it does see the scanner
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".
found USB scanner (vendor=0x1606, product=0x1030) at libusb:003: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.
So I'm not sure what is going on...