[sane-devel] Hmm, why does sane-find-scanner think I have a USB scanner?

[Henning Meier-Geinitz]

Hi,

On Sat, Feb 16, 2002 at 02:41:57PM -0800, paul beard wrote:
> it isn't USB:
> 
> uk0 at scsibus0 target 2 lun 0: <UMAX, Astra 1200S, V2.7> SCSI2 
> 6/scanner fixed
> 
> If I specify the device (/dev/scanner) I get this result.
> 
> [...-backends/work/sane-backends-1.0.7/tools]# sane-find-scanner 
> /dev/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 SCSI scanner "  " at device /dev/scanner
> sane-find-scanner: found USB scanner (UNKNOWN vendor and product) 
> at device /dev/scanner
> 
> # `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.
> 
> this also happens when I use the verbose flag, whether or not I 
> specify the device. if I do neither, I just get the unidentifiable 
> scsi scanner message.

If you explicitely specify a device name, both the tests for SCSI and
USB scanners are run. The USB scanner test is very simple, it justs
opens the device and tries to identify it. The identification doesn't
work on NetBSD. The open does (because the files exists and is a
device file) and so the false positive is printed. I have no idea how
to avoid this without adding options like "--scsi-only" and
"--usb-only".

It shouldn't harm in this case, however.

Bye,
  Henning