Date: Wed, 22 Feb 2006 17:29:08 -0500 From: Joe Altman <fj@panix.com> To: freebsd-stable@freebsd.org Cc: stable@freebsd.org Subject: Re: freebsd-stable Digest, Vol 147, Issue 4 Message-ID: <20060222222908.GA14423@panix.com> In-Reply-To: <20060222070811.D045D16A43A@hub.freebsd.org> References: <20060222070811.D045D16A43A@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 22, 2006 at 07:08:11AM +0000, freebsd-stable-request@freebsd.org wrote:
>
> 21. uscanner-problems (Holger Kipp)
>
> ------------------------------
>
> Message: 21
> Date: Wed, 22 Feb 2006 00:01:59 +0100
> From: Holger Kipp <hk@alogis.com>
> Subject: uscanner-problems
> To: stable@freebsd.org
> Message-ID: <20060221230159.GA56946@intserv.int1.b.intern>
> Content-Type: text/plain; charset=us-ascii
>
> Hello List,
>
> I encounter some strange problems with accessing my
> Epson Perfection 1260 Scanner (Plustek):
>
> sane-find-scanner from non-root-user that belongs to
> group usb finds the scanner every time (so far):
>
> # No SCSI scanners found.
> found USB scanner (vendor=0x04b8, product=0x011d) at /dev/uscanner0
>
> sane-find-scanner from root does so sometimes. I got
> the following different things:
>
> a) # No SCSI scanners found.
> # No USB scanners found.
>
> b) # No SCSI scanners found.
> found USB scanner (vendor=0x04b8, product=0x011d) at /dev/uscanner0
>
> c) hangs, according to ctrl-t in state [cbwait]
>
>
> scanimage -L from non-root-user finds the scanner only
> the first time, then again after reattaching the scanner.
>
> Anyone else seeing this behaviour? This worked ok with
> gimp, xscanimage etc. on 6.0-STABLE. Unfortunately I
> don't use the scanner that often, but it did work ok
> on 25.01.2006 (timestamp of last image I scanned).
>
> Regards,
> Holger Kipp
Ah, the plustek backend. My HP 2200C began, suddenly, to exhibit this
type of behavior some weeks back. I asked on -questions and received
no reply, so I assumed it was best to file a bug report with the
backend maintainers. That went over like a lead balloon; not that it
was their fault, it just went badly. I finally gave up and purchased a
new scanner.
The last thing I heard about my bug report from the backend
maintainers was "It works for me."
I was torn between attributing it to some weird issue with FBSD's USB
bits, and a bug in the sane backend code; but I lack the clue to know
which. Prior to the backend update, outlined below, the HP 2200C
worked adequately.
2005-12-18: SANE-Backends-1.0.17 has been released. Changes since
1.0.16:
* New backends: hp4200 (HP ScanJet 4200), lexmark (Lexmark X1100
series), mustek_usb2 (Mustek BearPaw 2448 TA Pro)
* Updated backends: artec_eplus48u, avision, canon, epson,
fujitsu, genesys, gt68xx, microtek2, mustek_pp, plustek,
plustek_pp, sm3600, snapscan, umax_pp.
>From <http://www.sane-project.org>.
I'd give you the bug number, but they closed and tossed it.
Good luck, and I hope it works out....
Joe Altman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060222222908.GA14423>