ga ho wrote: >> It might be that your kernel's SUBSYSTEM is wrong for this >> device. Do you have CONFIG_SYSFS_DEPRECATED turned on in the kernel >> .config file? Udev docs claim it may not work with that setting (though I >> don't know if that will cause this type of failure or not). > > CONFIG_SYSFS_DEPRECATED is not set in my .config
OK, good. >> What does "/sbin/udevadm info -q path -n /dev/rtc" >> say? > > /devices/virtual/misc/rtc Ah! A misc-device! :-) >> Where does the /sys/$(/sbin/udevadm info -q path -n /dev/rtc)/subsystem >> symlink point to? > > lrwxrwxrwx 1 root root 0 2009-09-15 20:45 > /sys/devices/virtual/misc/rtc/subsystem -> ../../../../class/misc OK, so I *suspect* the SUBSYSTEM here will be either "misc", or something else entirely. Have to get the output from the "udevadm info --attribute-walk" though. And that's really critical at this point; see my last reply to Bruce for why... > I have noticed that I have 3 udevd demons running whereas on my other > Linux systems I only have one. So I'm going to try and track down why. Because newer versions of udevd pre-fork some child processes to handle uevents -- there was a bunch of discussion a few udev versions ago about which was faster, this or making it threaded. This seemed to be.
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
