From owner-freebsd-current@FreeBSD.ORG Wed Oct 2 12:32:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DEEFC5CA for ; Wed, 2 Oct 2013 12:32:02 +0000 (UTC) (envelope-from john@potato.growveg.org) Received: from potato.growveg.org (growveg-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:3d2::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A21C2662 for ; Wed, 2 Oct 2013 12:32:02 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VRLav-0000dF-UP for freebsd-current@freebsd.org; Wed, 02 Oct 2013 13:31:57 +0100 Date: Wed, 2 Oct 2013 13:31:57 +0100 From: John To: freebsd-current@freebsd.org Subject: Re: gphoto2 bus error Message-ID: <20131002123157.GC74638@potato.growveg.org> References: <20131001135021.GA56944@potato.growveg.org> <524BBC5A.6060108@bitfrost.no> <20131002120412.GB74638@potato.growveg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131002120412.GB74638@potato.growveg.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: john@potato.growveg.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 12:32:02 -0000 Hi, One for the archives. I'm not sure if your patch had anything to do with it but I finally got it working by commenting out everything in /usr/local/etc/sane.d/dll.conf and just uncommenting the one I wanted. It seems the scanner was being mis-identified Thanks for your help, -- John