Date: Mon, 4 Jan 2010 09:38:21 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Andrew Reilly <areilly@bigpond.net.au> Cc: freebsd-usb@freebsd.org Subject: Re: Getting a scanner to work with new usb stack? Message-ID: <alpine.BSF.2.00.1001040925160.4840@wonkity.com> In-Reply-To: <20100104030903.GA15746@duncan.reilly.home> References: <20100104030903.GA15746@duncan.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Jan 2010, Andrew Reilly wrote:
> For many years I've been happily (if only occasionally)
> using an AGFA Snapscan e20 flat-bed USB scanner, using
> xsane. This scanner (apparently) requires a "firmware
> upload", which I had managed to arrange with this
> line in /usr/local/etc/sane.d/snapscan.conf:
> firmware /usr/local/share/sane/snapscan/snape20.bin
>
> I don't know whether or not that is (or is related to) the
> problem, but it isn't working any more, and I've run out of
> ideas to try, so thought I'd ask here.
>
> sane-find-scanner finds:
> found USB scanner (vendor=0x06bd [AGFA ], product=0x2091 [SNAPSCAN]) at libusb:/dev/usb:/dev/ugen0.3
> # Your USB scanner was (probably) detected. It may or may not be supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> But no amount of scanimage -d spellings or SANE_DEFAULT_DEVICE
> tweaking seems to make scanimage or xsane happy.
> ("snapscan:/dev/uscanner0" used to be what I used.)
>
> For what it's worth, I'm running -current as of Saturday, and my
> dmesg.boot says:
> ugen0.3: <AGFA> at usbus0
snapscan.conf should have
usb /dev/ugen0.3
(snapscan:libusb:/dev/usb:/dev/ugen0.3 from the command line, I think.)
Need new 0660 permissions to ugen0.3 (or ugen*, or usb/*) in
devfs.rules, too.
-Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001040925160.4840>