From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2AA7B138247 for ; Sat, 9 Nov 2013 03:26:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03560E09BF; Sat, 9 Nov 2013 03:26:07 +0000 (UTC) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by pigeon.gentoo.org (Postfix) with ESMTP id ECC50E09AA for ; Sat, 9 Nov 2013 03:26:05 +0000 (UTC) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta09.westchester.pa.mail.comcast.net with comcast id nFN61m0021HzFnQ59FS5uN; Sat, 09 Nov 2013 03:26:05 +0000 Received: from ajax ([24.11.47.14]) by omta14.westchester.pa.mail.comcast.net with comcast id nFS51m00H0JMh7c3aFS5qo; Sat, 09 Nov 2013 03:26:05 +0000 Date: Fri, 8 Nov 2013 22:25:53 -0500 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: [gentoo-amd64] USB Scanner Problems with Newer Kernels/Libusb Message-Id: <20131108222553.33af27243ad5aa2411c3f0ff@comcast.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.22; x86_64-unknown-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383967565; bh=QO/jYy3tf042c/dd7ICwTLFxx77cvh4T9qiY/E2IhJk=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=c7sAm22/cYx1lw0N+PgRUbSN9lMHhRoxO1B1Crcb2Uw/7c/719XKXv6nUk8Bkzdqu 7qh7rhm6t0Kp3CMxdfZSiEcR18wW7WAr6psfw9nIt5k3vl9ZPOmHX+xWBjt2ejvSnI DFn3sXH8R1HCMjYs/ZeFDuhaKJuDLjKr6dT1gEsodiJ8ie2gHrux7lanhkjTMAtGb9 bDc7FXwQqQtAqMBBiwx97gZ4kvYELlnnSpVxK1Z2jCmK68PIqCSBSo2y/iJkSRII5a w6G/wI2FarLFvnxCvt3E4W3Wd/sgn9x7PSUYl5GdSglr56Vwr7dyIuzyvHs3A5D3/2 jlHIXlmTwx/rA== X-Archives-Salt: cc3abf6f-7abe-4dde-8134-8416edf1258e X-Archives-Hash: 2a8ba3fd3af63a1bc759add78365539e I do not make scans very often, but when I do my scanners work very well with Linux and Sane -- or at least they used to. Checking the file dates on my last scans I discover that I last used my scanner during January of 2012. This was about the time of the release of kernel 3.5. The significance of this is that with kernel 3.5 the usbfs file system was eliminated. Previously, libusb was used to read/write to the scanner from user space. Libusb is still used by Sane but since usbfs has been eliminated it no longer detects my scanner. When I plug in the scanner the kernel log shows this message: Kernel: usb 2-1.4: new full-speed USB device number 4 using ehci-pci The kernel can detect the device, but the user-space libusb, and hence Sane, cannot access the scanner. In fact, sane-find-scanner, which should detect the scanner, fails with this output: # Could not initialize libusb-1.0, error -99 # Skipping libusb devices >From what I've manged to find through searches I believe that udev is used to create devices "on the fly" when a scanner is detected. However, I've never used udev before and never had problems with libusb detecting the scanner. But since usbfs is gone I am now unable to scan due to a failure to detect the scanner. The utility usb-devices, which uses libusb, can produce data on the scanner, but lsusb, which also uses libusb but depends on usbfs, fails. Does anyone know to resolve such a problem? How can I get my scanner to be utilized by libusb and sane? Frank Peters