From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 03B98138334 for ; Tue, 17 Jul 2018 14:19:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE57BE09F7; Tue, 17 Jul 2018 14:19:27 +0000 (UTC) Received: from jeeves.wrkhors.com (23-25-19-49-static.hfc.comcastbusiness.net [23.25.19.49]) by pigeon.gentoo.org (Postfix) with ESMTP id 1C4C3E09F1 for ; Tue, 17 Jul 2018 14:19:26 +0000 (UTC) Received: from wrkhors.com (localhost [127.0.0.1]) by jeeves.wrkhors.com (Postfix) with ESMTP id E27E310ECC5; Tue, 17 Jul 2018 09:33:14 -0500 (CDT) Date: Tue, 17 Jul 2018 09:18:48 -0500 From: Steven Lembark To: gentoo-user@lists.gentoo.org Cc: lembark@wrkhors.com Subject: Re: [gentoo-user] scanner problem Message-ID: <20180717091848.20329745@wrkhors.com> In-Reply-To: <20180717063853.GA1944@ca.inter.net> References: <20180717063853.GA1944@ca.inter.net> Organization: Workhorse Computing Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 7b2abe83-d8c0-4c92-a209-91e97e95ca02 X-Archives-Hash: 27b0c0df10d430bfcaff10bc75388c23 > Since then, I've updated my kernel & some other pkgs. You build your own kernel or rely on modules to handle it all? Any idea what modules you've rebuilt since the last use of the scanner? As a sanity check you might want to take a look at VueScan. Hamerick does a nice to of just making things work. Might give some better error messages -- it's also a nice package, worth a few bucks to have something that Just Works and also helps support someone who actually releases software for Linux. Depending on which syslogger you use, create /var/log/debug with debug-level output (no idea how to do this with systemd), zero the log, and tail -f it while you plug in the scanner, try to use it. I normally keep /var/log/messages w/ *.info, auth.none and have logrotate switch it out frequently (daily) at 1MiB. You only need it once to make it worth the disk space :-) Try: ( strace sane /var/tmp/sane.strace.out 2>&1; and see what it's trying to open when it fails to get the file. It might not be the device itself that is botching the process but a secondary file that got stepped on. Try: find /etc -name '._cfg*'; any of them affect scanning, dbus, usb (anything else that might be used by sane)? -- Steven Lembark 1505 National Ave Workhorse Computing Rockford, IL 61103 lembark@wrkhors.com +1 888 359 3508