[sane-devel] Problems with Microtek Scanmaker-III, Solaris 8, sgen driver, xsane

[Henning Meier-Geinitz]

Hi,

On Mon, Apr 08, 2002 at 12:00:12PM +1000, Craig Dewick wrote:
> Well I have compiled and installed xsane-frontends and xsane-backends,
> along with xsane-0.84. I did have a small problem with sane-backends and
> specifying linker paths (only occured when linking against the JPEG shared
> library), but otherwise it went smoothly.

Can you tell us more about this problem so we can fix it? Or was it a
local installation problem?

> I searched the sane list archives to see some messages about configuring
> sane to work properly with scanners under solaris using the 'sgen' driver,
> however I still cannot get xsane to talk to the scanner (a Microtek
> Scanmaker-III) correctly.

There is a README.solaris in th sane-backends tar.gz file. I have
never used SCSI on a Solaris system or a Microtek scanner but I will
try to answer anyway:

> The scanner is set to SCSI ID # 6 and connected to the SCSI port of a
> SunSwift PCI card. The 'sgen' device driver has no problems finding it at
> at boot time and setting up a link for it in /dev/scsi/scanner.
> 
> Contrary to the document posted to the mailing list, the device handle
> that the driver has created is 'c6t6d0', *not* 'c6t6d6'. I don't know if

As far as I know c=controller, t=target (SCSI id) and d=LUN so
"c6t6d0" looks only a bit suspicious because it's your 6th SCSI
controller. But if it's a big machine...

> that's a problem - my system has the latest Solaris 8 maintenance update
> installed which included a patch to the 'sgen' driver package.
> 
> In any case, when I start xsane by entering:
> 
> xsane microtek:/dev/scsi/scanner/c6t6d0

Did you enter /dev/scsi/scanner/c6t6d0 into microtek.conf? I don't
know if this is necessary, however.

> the application starts, displays the GPL acceptance window, then gives an
> error box saying 'Failed to open device microtek:/dev/scsi/scanner/c6t6d0
> Invalid argument'. What might be causing this?

Try setting the environment variable SANE_DEBUG_MICROTEK to 255 for
more details (on stderr).

> I've su'd to root and run 'sane-find-scanner /dev/scsi/scanner/c6t6d0'
> which works fine:
> 
> 
> 116 root at lios #----> sane-find-scanner /dev/scsi/scanner/c6t6d0
[...]

> sane-find-scanner: found SCSI scanner "MICROTEK ScanMakerIII 2.70" at device /dev/scsi/scanner/c6t6d0
> sane-find-scanner: found USB scanner (UNKNOWN vendor and product) at device /dev/scsi/scanner/c6t6d0

> But I don't know how it figures the scanner has anything to do with USB as
> my Ultra-30 has no USB hardware. 8-)

That's ok. If you specify the filename on the command line, both the
tests for SCSI and USB will be positive because sane-find-scanner
can't really detect the pesence of an USB scanner. 

> Anyway, that's beside the point. 'sane-find-scanner' detects the presence
> of the scanner and correctly reports what it is, so what could be causing
> 'xsane' to be unable to access it?

Look at the debug output, maybe you get a hint.

Bye,
  Henning