On Fri, 2005-07-15 at 17:05 -0400, Bill Nottingham wrote: > Ignacio Vazquez-Abrams (ivazquez@xxxxxxxxxxxx) said: > > Apparently udev can't see them. > > > > "The first thing you need to do is find a directory somewhere in /sys > > that corresponds to your hardware, and includes a file named "dev", as > > udevinfo can only work on directories of this type. These directories > > are all found under either /sys/block or /sys/class - there is no point > > looking anywhere else!" > > > > User-mode drivers don't give the device a block or class designator, and > > so udev won't handle them. > > Sure it will. > > At the end of udev.rules: > > ACTION=="add", SUBSYSTEM=="usb", MODALIAS=="*", \ > RUN+="/sbin/modprobe $modalias" > > This gets run for all usb devices to *try* and load a driver. It's running > before the kernel could know whether or not a driver is kenrel or > userspace. Aha! That got it. > Perhaps the udev docs need some help. Indeed. The range of actions possible would also be useful. -- Ignacio Vazquez-Abrams <ivazquez@xxxxxxxxxxxx> http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
