The sg driver prints out a line like:
Detected scsi generic sg? at scsi? channel ? id ? lun ?
where "?" will be the appropriate letter or number.
This line is output by sg for every SCSI device that
is _not_ a disk, nor a tape, nor a cdrom. So you should
see it for your scanner.
If sg is built into the kernel, you should see it in
your boot up sequence, and if it is a module then you
will see it when you do a 'insmod sg'.
If you are not seeing this line then something is wrong
(eg sg is not in kernel).
> I created a group called scanner with the ID of 43. I
> added root and another user in the group. I chmod
> /dev/sge to 660 and chgrp /dev/sge to scanner as
> instructed by san-scsi help file. I made a soft link
> of /dev/scanner pointing to /dev/sge. I edited
> /usr/local/etc/sane.d/umax.conf and it looks like this
> (excluded comments in the file):
>
> scsi UMAX * scanner
> /dev/scanner
> /dev/sge
>
> I edited /usr/local/etc/sane.d/dll.conf and it looks
> like this (excluded comments in the file):
>
> pnm
> umax
>
> Now when I used xscanimage or xsane, they only list
> out pnm:0 and pnm:1 as the devices to choose from.
>
> When I use scanimage, which I am not sure about the
> command syntac, with -d umax:/dev/sge and gave an
> error message like device failed to open:Invalid
> Argument. When I used findscanner -v, it tried to open
> the device from all /dev/sg* but all failed.
Also the version of sg in 2.2.6 (sg version 2.1.31) has
problems with the aic7xxx driver. Visit
http://www.torque.net/sg
and pick up sg version 2.1.32 or 2.1.34. Alternatively
upgrade your kernel to 2.2.8 or 2.2.9 .
You don't seem to be getting this far since the scanner
would still be detected.
Hope this helps.
Doug Gilbert
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com