From owner-freebsd-usb@FreeBSD.ORG Mon Jan 4 16:38:26 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A0CA106566B for ; Mon, 4 Jan 2010 16:38:26 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B76458FC14 for ; Mon, 4 Jan 2010 16:38:25 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o04GcLGQ005144; Mon, 4 Jan 2010 09:38:21 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o04GcLjS005141; Mon, 4 Jan 2010 09:38:21 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 4 Jan 2010 09:38:21 -0700 (MST) From: Warren Block To: Andrew Reilly In-Reply-To: <20100104030903.GA15746@duncan.reilly.home> Message-ID: References: <20100104030903.GA15746@duncan.reilly.home> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Mon, 04 Jan 2010 09:38:21 -0700 (MST) Cc: freebsd-usb@freebsd.org Subject: Re: Getting a scanner to work with new usb stack? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2010 16:38:26 -0000 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: 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