[sane-devel] Automatic scanner recognition not working

Arcady Genkin antipode@thpoon.com
30 Sep 2001 15:34:14 -0400


Hi all:

How do I make my scanner recognizable by sane under Linux 2.4.10,
other than creating a /dev/scanner link?  I have a scsi scanner
connected as the first ID on the SCSI bus:
,----
| tea:/proc/scsi$ cat scsi 
| Attached devices: 
| Host: scsi0 Channel: 00 Id: 02 Lun: 00
|   Vendor:          Model: Scanner 636A4    Rev: 1.50
|   Type:   Scanner                          ANSI SCSI revision: 02
| Host: scsi0 Channel: 00 Id: 04 Lun: 00
|   Vendor: PIONEER  Model: DVD-ROM DVD-305  Rev: 1.00
|   Type:   CD-ROM                           ANSI SCSI revision: 02
| Host: scsi0 Channel: 00 Id: 05 Lun: 00
|   Vendor: SONY     Model: CD-ROM CDU-76S   Rev: 1.1c
|   Type:   CD-ROM                           ANSI SCSI revision: 02
| Host: scsi0 Channel: 00 Id: 06 Lun: 00
|   Vendor: MATSHITA Model: CD-R   CW-7502   Rev: 4.17
|   Type:   CD-ROM 
`----

Since most of the times I boot up with the scanner unpowered, and then
tell the kernel to add the scsi device, the scanner becomes /dev/sg3.
However, if I boot up with the scanner ON, it is assigned /dev/sg0.
As you can see, creating a /dev/scanner link is problematic.

In file /dev/sane.d/microtek2.conf (the config file for my backend) I
have a line "scsi * * Scanner", and the only line left in dll.conf is
"microtek2".  Supposedly, the scanner should be recognised
automatically, but for some reason that is not happening.  Command
"scanimage -L" says that no scanners were identified.

Any ideas on how to fix the problem?  I guess I can reassign the SCSI
device IDs so that the scanner is always the last one, but that's more
of a hack than solution, IMO.

Just for the sake of mentioning it, creating /dev/scanner link to the
correct /dev/sgN makes everything work.

Many thanks,
-- 
Arcady Genkin