> I've searched for some kind of explanation for this in the man pages,
> to no avail. Can anyone suggest why scanimage thinks my scanner is
> [root@home /root]# scanimage -V
> scanimage (sane-backends) 1.0.4
> [root@home /root]# scanimage -d coolscan:/dev/scanner
> scanimage: open of device coolscan:/dev/scanner failed: Device busy
> [root@home /root]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: Nikon Model: LS-2000 Rev: 1.31
> Type: Scanner ANSI SCSI revision: 02
> [root@home /root]# ./sane-backends-1.0.4/tools/find-scanner
> # Note that find-scanner will find any scanner that is connected
> # to a SCSI bus. 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, USB or other non-SCSI port.
> find-scanner: found scanner "Nikon LS-2000 1.31" at device /dev/scanner
> find-scanner: found scanner "Nikon LS-2000 1.31" at device /dev/sg0
> find-scanner: found scanner "Nikon LS-2000 1.31" at device /dev/sga
> [root@home /root]#
> And here is the output of strace. I have no idea why it is looking
> for the v4linux devices.
> [root@home /root]# strace scanimage -d coolscan:/dev/scanner
> open("coolscan:/dev/scanner", O_RDWR) = -1 ENOENT (No such file or directory)
Strange, this open() took the "-d" argument too literally.
It should be trying to open("/dev/scanner", ...).
> write(2, "scanimage: open of device coolsc"..., 68scanimage:
> open of device coolscan:/dev/scanner failed: Device busy
This "Device busy" is confusing since ENOENT means
exactly what strace says: "no such file or directory".
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com
This archive was generated by hypermail 2b29 : Thu Jan 18 2001 - 19:42:42 PST