Re: E6XL usable? & scg driver help [was: Re: Microtek V300, anyone?]

Joerg Schilling (joerg@schily.isdn.cs.tu-berlin.de)
Sun, 20 Sep 98 23:16:16 +0200

>From sjk@lux.com Sun Sep 20 21:18:45 1998

>Thanks to Martin Huber, I now have scanners working with SANE and the
>scg driver. Here's his help:

> Date: Fri, 18 Sep 1998 23:29:12 +0200 (MET DST)
> From: Martin Huber <hu@garfield.m.isar.de>
> Subject: Re: SANE SCSI inquiry failure on Solaris 2.5.1

> This looks as if you don't have defined SOLARIS_INTERFACE in sanei_scsi=
>=2Ec.

> Please check include/sane/config.h. The string

> #define HAVE_SYS_SCSI_TARGETS_SCGIO_H 1 =

>The reason HAVE_SYS_SCSI_TARGETS_SCGIO_H wasn't defined was that I'd
>run the `configure' script on a host that scg wasn't installed and
>this check failed:

> checking for sys/scsi/targets/scgio.h... no

>So if you're intending to use the scg driver be sure to install that
>package *before* configuring/compiling the SANE software. It might
>be good to make a note of that in one of the README files.

I got unclear error messages for some times and could not help the
people. These people thought that the problem might me in scg...
Another hint: I don't know if the man page is already changed, but I
got also problem reports that seem to related to the odd way sane
modifies the /dev/scg device name. People who get problems usually
try to find the device nodes and tend to believe that the installation
of the scg drvier failed because the faked driver entries are not there.

>The only trouble I've noticed are these messages which occur during
>scanning:

> Sep 19 17:54:36 shimmer saned[442]: access by sjk@halo.lux.com accepted=

> Sep 19 17:54:55 shimmer unix: handle_incomplete: 1 retry cnt: 27
> Sep 19 18:01:16 shimmer last message repeated 100 times
> Sep 19 18:02:54 shimmer unix: handle_incomplete: 1 retry cnt: 27
> Sep 19 18:05:39 shimmer last message repeated 64 times

>Those are coming from the scg driver; running `strings' on it reveals:

This is either a bug in the application or a bug in the SCSI implementation
of the scanner.

Either add a line:
set scg:scg_debug=3

to /dev/system and reboot or do as root (after the scg driver has been loaded):

adb -k
scg_debug/W3
$q

and then do the same thing as before and send me the console output
or the messages from /var/adm/messages

I then can tell you where the bug is located.

Jörg

EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com