SANE issue - some parts find scanner, others don't

[Dave (from the UK)]

I'm using the sane to try to use an EPSON Perfection 1200 SCSI scanner
on a Sun workstation running Solaris 10 update 1. I'm using the sgen
driver, rather than scg, sg or similar.

I've used earlier version of sane with this scanner on Solaris 9, so I
know the basic setup should work, but I'm a bit stuck here.

The program 'sane-find-scanner' finds my scanner, and is clearly reading
it, since it works out it is an EPSON Perfection 1200. But 'scanimage'
can not find the scanner. See below.

Setup:
******

Hardware
---------

Scanner: Epson Perfection 1200 (SCSI)
Computer: Sun Ultra 80

Software
--------
Solaris 10 update 1.
sane backends 1.0.17
sgen driver


# ./sane-find-scanner -v

This is sane-find-scanner from sane-backends 1.0.17

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scg0a... failed to open (Invalid argument)
checking /dev/scg0b... failed to open (Invalid argument)
<lots of similar lines removed>
checking /dev/sg/6... failed to open (Invalid argument)
cannot stat `/dev/scsi/scanner/' (No such file or directory)
checking /dev/scsi/processor/c1t2d0... open ok
found SCSI processor "EPSON Perfection1200 1.03" at
/dev/scsi/processor/c1t2d0
# Your SCSI scanner was detected. It may or may not be supported by
SANE. Try
# scanimage -L and read the backend's manpage.

(I get a bit fed up joining mailing lists, but perhaps I'll need to).

sparrow /usr/local/bin # scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


# ./scanimage -d epson:/dev/scsi/processor/c1t2d0 -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
he documentation
which came with this software (README, FAQ, manpages).

# ./scanimage -d epson:/dev/scanner -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


# ./scanimage -d epson:/dev/scsi/processor/c1t2d0 -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


# ls -l /dev/scanner
lrwxrwxrwx 1 root root 26 Feb 4 03:32 /dev/scanner ->
/dev/scsi/processor/c1t2d0
sparrow /usr/local/bin # ls -l /dev/scsi/processor/c1t2d0
lrwxrwxrwx 1 root root 56 Feb 4 02:11
/dev/scsi/processor/c1t2d0 ->
.../../../devices/pci@1f,4000/scsi@3,1/sgen@2,0rocessor
sparrow /usr/local/bin #


/usr/local/etc/sane.d has the epson line there (not commented out).

Any ideas ????

--
Dave K

http://www.southminster-branch-line.org.uk/

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually. The month is
always written in 3 letters (e.g. Jan, not January etc

 

[Glenn]

I'm using the sane to try to use an EPSON Perfection 1200 SCSI scanner
on a Sun workstation running Solaris 10 update 1. I'm using the sgen
driver, rather than scg, sg or similar.

Scanner: Epson Perfection 1200 (SCSI)
Computer: Sun Ultra 80

Software
--------
Solaris 10 update 1.
sane backends 1.0.17
sgen driver

/usr/local/etc/sane.d has the epson line there (not commented out).

Any ideas ????

I installed an HP 6300c SCSI scanner on S10 FCS, to operate using
the /opt/sfw/bin/scanimage supplied via the Companion CD. I foolishly
modified certain system files directly, without leaving .orig files
around to directly compare against, but still there are some clues.

(1) The /kernel/drv/sgen.conf file was left containing the following
lines, which are clearly specific to my system:

inquiry-config-list= "HP", "C7670A"; # HP 6300c scanner

# Recognize only this SCSI ID, and only on the fas2 SCSI bus.
name="sgen" parent="/sbus@1f,0/SUNW,fas@1,8800000" target=2 lun=0;

(2) /opt/sfw/etc/sane.d/hp.conf was modified to reflect the actual
device path of my SCSI-attached page scanner:

# The usual place for a SCSI-scanner on Linux
# /dev/scanner
# The actual place on my particular Solaris box.
/dev/scsi/processor/c2t2d0

This setup worked for me. I also defined:

alias lampoff scanimage -n --lamp-off

in my ~/.cshrc file because scanning leaves the light on forever after,
and I'd rather save the bulb for the 1% of the time I might actually
use the device.

 

[Dave (from the UK)]

I installed an HP 6300c SCSI scanner on S10 FCS, to operate using
the /opt/sfw/bin/scanimage supplied via the Companion CD. I foolishly
modified certain system files directly, without leaving .orig files
around to directly compare against, but still there are some clues.


(2) /opt/sfw/etc/sane.d/hp.conf was modified to reflect the actual
device path of my SCSI-attached page scanner:

# The usual place for a SCSI-scanner on Linux
# /dev/scanner
# The actual place on my particular Solaris box.
/dev/scsi/processor/c2t2d0

Thanks, that was helpful. I did look in the epson.conf man page, but see
no similar line. The file just says

scsi EPSON
usb

and even the comments don't allude to adding a link to the scanner. But
I thought I'd do so anyway, so added the line
/dev/scsi/processor/c1t2d0
and removed the USB line, so it now looks like:

scsi EPSON
/dev/scsi/processor/c1t2d0

It is now OK.

Thanks. All I need now is find out how to get the gimp plugin working.
I've done that before, but will need to read some docs to refresh my
memory.

--
Dave K

http://www.southminster-branch-line.org.uk/

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually. The month is
always written in 3 letters (e.g. Jan, not January etc)

 

[Joerg Schilling]

I'm using the sane to try to use an EPSON Perfection 1200 SCSI scanner
on a Sun workstation running Solaris 10 update 1. I'm using the sgen
driver, rather than scg, sg or similar. ....
The program 'sane-find-scanner' finds my scanner, and is clearly reading
it, since it works out it is an EPSON Perfection 1200. But 'scanimage'
can not find the scanner. See below. .....
# ./sane-find-scanner -v

This is sane-find-scanner from sane-backends 1.0.17

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scg0a... failed to open (Invalid argument)
checking /dev/scg0b... failed to open (Invalid argument)

SANE should be better called INSANE. It is one of the worst pieces of software
I've ever seen :-( They try e.g. to work around Linux SCSI kernel implementation
bugs in high level parts of the code what of course causes problems on other OS.

No system will ever have /dev/scg0a or similar

Some years ago, the Sane people did contact me and asked me how to use the
scg driver. I send them a detailed description and directed them to libscg
(a highly portable SCSI transport lib that works on 24 different platforms)
and cdrecord which is based on libscg.

It seems that the SANE people did completely ignore my hints and that they never
did try out SANE on Solaris otherwise they would know that the scg driver only
has one device node per SCSI bus (scg0, scg1, ....).

As a result, I have never been able to use SANE on Solaris.

It seems that the claims of the SANE people about what is suported are
unsubstiantial.

Any attempt to get the SANE bugs fixed have been of no avail so far.

 

[Dave (from the UK)]

SANE should be better called INSANE. It is one of the worst pieces of software
I've ever seen :-( They try e.g. to work around Linux SCSI kernel implementation
bugs in high level parts of the code what of course causes problems on other OS.

<snip>

I have it working. I scanned this tonight - about quartz locking a
pendulum clock. Converted to pdf inside of xsane.

http://www.g8wrb.org/useful-stuff/time/pendulum+quartz.pdf

Actually, sane and xsane were not too hard to get working - all I needed
to do was add one line to /usr/local/etc/epson.conf to tell it where the
scanner was. This is not documented in the epson configuration file, but
it is documented in the hp configuration file, so I thought I'd try it.

I have in /kernel/drv/sgen.conf

device-type-config-list="processor";
inquiry-config-list= "EPSON", "Perfection1200";
name="sgen" class="scsi" target=2 lun=0;

and in epson.conf

scsi EPSON
/dev/scsi/processor/c1t2d0

As a result, I have never been able to use SANE on Solaris.

I think I had it working on Solaris 8, but definately Solaris 9 and 10.

Clearly others have too. Have you read README.solaris? Have you tried
the *three* drivers they suggest - your own, Suns and sg the driver by
Kevin Sheehan?

I'm using Sun's sgen driver, which is part of Solaris 10.

It seems that the claims of the SANE people about what is suported are
unsubstiantial.

Well, they say my EPSON Perfection 1200 scanner is supported and it
works. It also worked with my old Umax, although that was not on their
supported list. I don't blame them there, as the scanner was
unrelieable. It would often not be seen at the open-boot prompt and so
frequently required the scanner and Sun switched on/off server times
before it could be seen. Once seen, it was OK.

Any attempt to get the SANE bugs fixed have been of no avail so far.

I don't know what your issue is, so it is hard to say much. But if it is
simply it does not work with your own driver, and they know it does with
a driver that is part of Solaris 10, you can hardly blame them not
worrying too much about it.
--
Dave K

http://www.southminster-branch-line.org.uk/

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually. The month is
always written in 3 letters (e.g. Jan, not January etc)