Re: Using NET backend

Matto Marjanovic (maddog@mir.com)
Fri, 15 May 1998 14:42:23 -0400 (EDT)

Date: Thu, 14 May 1998 22:58:55 -0700
From: David Mosberger-Tang <David.Mosberger@acm.org>

>>>>> On Thu, 14 May 1998 09:00:16 -0700, Jeff Freedman <jsf@hevanet.com> said:

Jeff> I'm trying out the "net" backend of the .72 release with a
Jeff> Microtek E3, Adaptec 2940, and Redhat Linux 5.0. It starts to
Jeff> work (in the "Preview" dialog of xscanimage); but after what
Jeff> seems like one pass, xscanimage freezes up. From then on, the
Jeff> scanner is unusable until I reboot. If I try "scanimage -L",
Jeff> scanimage just hangs until I kill it.

Jeff> Scanimage works fine if I use the Microtek backend directly.

...
I'm not saying this is necessarily a bug in the Microtek backend, but
just because it works with scanimage doesn't prove that it's a bug in
the net backend or in saned either. Maybe you can try to use
SANE_DEBUG_NET=128 on the client side and/or "saned -d 128" on the
server side to try to track the problem down?

Heh, I've never actually tried 'saned' myself. I'll give it a shot over
the weekend, and see if I can find/fix any bugs.

As far as resetting things after a hang: I've noticed that typically, when
I do something that hangs the scanner, often the scanner has barfed on some
command and reset itself, leaving another scsi command hanging off the bus.
If I wait some unreasonably long time (~5-10 minutes), the aha152x driver
will time-out and scrap the hanging command, and then I'm free to go and
do it again. Maybe the driver for your 2940 will do the same.

-matt m.

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