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 4CB03138247 for ; Sun, 10 Nov 2013 04:26:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8EC34E0A9D; Sun, 10 Nov 2013 04:26:33 +0000 (UTC) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by pigeon.gentoo.org (Postfix) with ESMTP id C708CE0A94 for ; Sun, 10 Nov 2013 04:26:32 +0000 (UTC) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA11.westchester.pa.mail.comcast.net with comcast id ngQt1m0020vyq2s5BgSYxe; Sun, 10 Nov 2013 04:26:32 +0000 Received: from ajax ([24.11.47.14]) by omta05.westchester.pa.mail.comcast.net with comcast id ngSY1m0040JMh7c3RgSY1i; Sun, 10 Nov 2013 04:26:32 +0000 Date: Sat, 9 Nov 2013 23:26:17 -0500 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb [Solved] Message-Id: <20131109232617.972ccb80d57935742bd71d13@comcast.net> In-Reply-To: <20131110015302.GA6695@crud> References: <20131108222553.33af27243ad5aa2411c3f0ff@comcast.net> <20131109203050.a1754f19defbcfd9a514a48d@comcast.net> <20131110015302.GA6695@crud> 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=1384057592; bh=P1nV8OtrAKs9xT5l1O9ujhZFoKkXE3e619egj+3OmKU=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=Wih56Hf4VZzJkQ4hkEjDmyDwCaXIgba92rjzydP0UdgZAL/WKAd3mu8qayFVNLQua HiJL3FBhnhfHa6RDeYCbQgt5yFrDxSL7Zh7k9QQa8XYOUWHRNuMhffcsXVueJ71OsF 2zu40VlDyU106++YUF9Z6U3AsBvC0TUSxARfoFHKlCeUk8pQHrkwSFx0B+J2458080 ZkwJXPPB6NG4bIthpGtO+9w7We8y68kw6it8aV9Ae1xhZ2ayLF76wkRlOlsLET09sk qdbCES6z4ny74O32v62BDL39alTSLFDaTvwmXhiwyk2Ocd2iC50kw0ALBaQn77cfzr SQDQ98uDEvezw== X-Archives-Salt: 8afe1557-1e0c-4acf-9410-3f9e8b59818e X-Archives-Hash: 3df58796c8a16cd0038937f7b8f07e5b On Sat, 9 Nov 2013 19:53:02 -0600 Barry Schwartz wrote: > > I figured as much. Please let us know if you come up with a good > technique that can be adapted to a MAKEDEV script or such. It is nice > to know how to dump e?udev, just in case; and I also use a scanner. > There are some difficulties with my previous response, but now I have found the final answer. Here are the steps. Udev (or equivalent) is *not* necessary. 1) Plug in the scanner. Check kernel log. Mine shows this message: kernal: usb 2-1.4 ... 2) Based on kernel message, check matching entry in the /sys tree. /sys/bus/usb/devices/2-1.4/uevent Mine shows this: MAJOR=189 MINOR=130 DEVNAME=bus/usb/002/003 DEVTYPE=usb_device DRIVER=usb PRODUCT=4b8/110/110 TYPE=255/255/255 BUSNUM=002 DEVNUM=003 3) Based on this information, create the device node: mknod --mode=0666 /dev/bus/usb/002/003 c 189 130 Now it works well. This is certainly the correct device node. I can scan with SANE without problems. Also, this can be scripted using bash to read the /sys file. But there may be a much better way to get the kernel output other than using the kernel log. I need to research this step. Frank Peters