From: Greg KH <greg@kroah.com>
To: art@usfltd.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
Date: Wed, 16 May 2007 22:14:20 -0700 [thread overview]
Message-ID: <20070517051420.GA10934@kroah.com> (raw)
In-Reply-To: <20070516145822.d1bz7paab4o8gg8c@67.106.77.50>
On Wed, May 16, 2007 at 02:58:22PM -0500, art@usfltd.com wrote:
> greg
>
> CONFIG_SYSFS_DEPRECATED=Y
>
> check that we have
> rwxrwxrwx 1 root root 15 May 16 13:43 scanner-usbdev2.12 ->
> bus/usb/002/012
>
> in /dev directory after usb-scanner connection for kernel-2.6.20
> we don't have this for kernel-2.6.22
Who creates that? udev? What udev rule does that?
Can you run 'udevtest' to see what is supposed to be matching here?
Odds are you have a broken rule somehow.
>
> ----------------------------2.6.20 usb-scanner connect
>
> # /usr/sbin/udevmonitor
>
> UEVENT[1179340996.886805]
> add@/devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2
> UEVENT[1179340996.886864] add@/class/usb_endpoint/usbdev2.12_ep00
> UEVENT[1179340996.887438]
> add@/devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0
> UEVENT[1179340996.887467] add@/class/usb_endpoint/usbdev2.12_ep81
> UEVENT[1179340996.887484] add@/class/usb_endpoint/usbdev2.12_ep02
> UEVENT[1179340996.887499] add@/class/usb_endpoint/usbdev2.12_ep83
> UEVENT[1179340996.887514] add@/class/usb_device/usbdev2.12
> UDEV [1179340996.921506]
> add@/devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2
> UDEV [1179340996.936005] add@/class/usb_endpoint/usbdev2.12_ep00
> UDEV [1179340996.960144] add@/class/usb_endpoint/usbdev2.12_ep81
> UDEV [1179340996.963672] add@/class/usb_endpoint/usbdev2.12_ep02
> UDEV [1179340996.967439] add@/class/usb_endpoint/usbdev2.12_ep83
> UDEV [1179340997.240934]
> add@/devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0
> UDEV [1179340997.473142] add@/class/usb_device/usbdev2.12
This last device is correct, and what your udev rule should be using to
create your symlink.
You didn't answer my, "what distro are you using" question. Also, what
package created the udev rule that creates the above symlink?
thanks,
greg k-h
next prev parent reply other threads:[~2007-05-17 5:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 19:58 usb-scanner-cameras kernel-2.6.22 and udev-095 problem art
2007-05-17 5:14 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 3:11 art
2007-06-07 3:37 ` Greg KH
2007-06-07 2:26 art
2007-06-06 0:20 art
2007-06-06 5:34 ` Greg KH
2007-05-18 0:00 art
2007-05-24 17:53 ` Greg KH
[not found] ` <6bffcb0e0706050518l53628a55k7b91ce38e272289d@mail.gmail.com>
2007-06-05 21:46 ` Greg KH
2007-05-17 17:05 art
2007-05-17 18:14 ` Greg KH
2007-05-15 17:42 art
2007-05-15 18:02 ` Linus Torvalds
2007-05-15 22:51 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070517051420.GA10934@kroah.com \
--to=greg@kroah.com \
--cc=art@usfltd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox