From owner-freebsd-questions@FreeBSD.ORG Thu Jun 10 03:51:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B6B916A4D7 for ; Thu, 10 Jun 2004 03:51:25 +0000 (GMT) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3D3043D41 for ; Thu, 10 Jun 2004 03:51:24 +0000 (GMT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.12.11/8.12.11) with ESMTP id i5A3pO5v036147; Wed, 9 Jun 2004 21:51:24 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.12.11/8.12.11/Submit) with ESMTP id i5A3pNCH036144; Wed, 9 Jun 2004 21:51:24 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 9 Jun 2004 21:51:23 -0600 (MDT) From: Warren Block To: Rob In-Reply-To: <40C7D50F.9060702@users.sourceforge.net> Message-ID: <20040609214010.R36128@wonkity.com> References: <40C7C47D.7060902@users.sourceforge.net> <20040609202124.L35804@wonkity.com> <20040609204934.T35931@wonkity.com> <40C7D50F.9060702@users.sourceforge.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.3.8 (wonkity.com [127.0.0.1]); Wed, 09 Jun 2004 21:51:24 -0600 (MDT) cc: freebsd-questions@freebsd.org Subject: Re: Using scanner with FreeBSD. A nightmare! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2004 03:51:25 -0000 On Thu, 10 Jun 2004, Rob wrote: > This is exactly the point where I get confused. > > # cat /usr/local/etc/sane.d/hp.conf | grep -v "^#" > usb 0x03f0 0x0401 > /dev/uscanner0 > # sane-find-scanner -v > [...] > checking /dev/uscanner0... open ok, but vendor and product could NOT be > identified > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 > [...] Hmm. What does 'scanimage -L' say? The only other thing I can think of trying would be to check that 'usbdevs -v' shows matching USB vendor and product codes. HP may have revised them. > I get the impression that hp.conf is not read at all, because I created an > hp.conf with nonsense contents, but sane-find-scanner was not bothered. sane-find-scanner may not care, but the rest of SANE should. -Warren Block * Rapid City, South Dakota USA