[sane-devel] 1.0.7 can't find Microtek X6EL

abel deuring adeuring at gmx.net
Sat Mar 9 13:52:15 GMT 2002


"K. Holcomb" wrote:
> 
> >> On Fri, Mar 08, 2002 at 05:17:42PM -0500, K. Holcomb wrote:
> >> > I am running RedHat 7.2, which came originally with sane 1.0.5.  My Microtek
> >> > X6EL was not detected by sane-find-scanner even though it shows up in
> >> > /proc/scsi/scsi.  In light of the FAQ answer concerning sane 1.0.5 and scanners
> >> > that do not report a vendor string (which it does not do),
> >>
> >> This problem is only with scanimage (and other frontends), not with
> >> sane-find-scanner. The frontends will work if you add /dev/scanner (or
> >> wherever your scanner is located) to the backend config file instead
> >> of only a "scsi vendor product" line.
> 
>     Actually, sane-find-scanner hangs indefinitely.
> 
> >>
> >> > cat /proc/scsi/scsi gives
> >> > Attached devices:
> >> > Host: scsi0 Channel: 00 Id: 06 Lun: 00
> >> >   Vendor:          Model: scanner 636EL    Rev: 1.20
> >> >   Type:   Scanner                          ANSI SCSI revision: 02
> >> > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> >> >   Vendor: IOMEGA   Model: ZIPCD1024INT-A   Rev:  1.1
> >> >   Type:   CD-ROM                           ANSI SCSI revision: 02
> >> >
> >> > The IOMEGA is a CD burner and it is actually using the ide-scsi interface.
> >> > Those of us with ATAPI CD burners have no choice but to use this module.
> >>
> >> I remember that some people had problems with ide-scsi in combination
> >> with SANE, maybe you can try to disable it while testing.
> 
>    OK, I unloaded the ide-scsi module and tried the exact debug line you
>    specified (I had used something from the microtek2-backend man page
>    before).  The result was
> 
> sane-find-scanner: searching for SCSI scanners:
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_find_devices: vendor=(null) model=(null) type=Scanner
>         bus=0 chan=0 id=6 lun=0  num=0
> [sanei_scsi] lx_chk_id: 0,0  0,0  6,6  0,0
> [sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg0
> [sanei_scsi] get_max_buffer_size for /dev/sg0: 131072
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=131072 bytes
> 
>   at which point sane-find-scanner hung.

Strange. The next step in sanei_scsi_open after the DBG statement for
sanei_scsi_max_request_size is to open the device file and to issue a
few ioctls. Since you are using kernel kernel version 2.4.17, the next
thing you should see is something like

"[sanei_scsi] sanei_scsi_open: SG driver version: xxxxx"

Do you get any related error messages in /var/log/messages? Which low
level SCSI driver do you use?

Abel



More information about the sane-devel mailing list