Bruce Dubbs wrote: > Bryan Kadzban wrote: > >>>> What does "/sbin/udevadm info -q path -n /dev/rtc" say? Where does >>>> the /sys/$(/sbin/udevadm info -q path -n /dev/rtc)/subsystem >>>> symlink point to? >>> udevadm returns '/devices/platform/rtc_cmos/rtc/rtc0' >> OK; here I get: >> >> /devices/pnp0/00:02/rtc/rtc0 > > On a 64-bit system, I get: > > /devices/pnp0/00:05/rtc/rtc0
Yeah, the bit-count doesn't actually affect this, but it looks like you
probably have the same RTC-class setup I have.
>> What about the standard:
>>
>> /sbin/udevadm --attribute-walk -n /dev/rtc
>
> I get:
>
> /sbin/udevadm: unrecognized option '--attribute-walk' :)
Uh, oops. Yeah, adding "info" would help. :-)
> But for /sbin/udevadm info --attribute-walk -n /dev/rtc, I get
>
>> looking at device '/devices/pnp0/00:02/rtc/rtc0':
>> KERNEL=="rtc0"
>> SUBSYSTEM=="rtc"
>> DRIVER==""
>> ATTR{name}=="rtc_cmos"
>> ATTR{date}=="2009-09-16"
>> ATTR{time}=="03:32:10"
> "03:56:50"
>> ATTR{since_epoch}=="1253071930"
> "1253073410"
Those two differences are just due to you running it at a different time
than I did.
>> ATTR{max_user_freq}=="1024"
> "64" !!!
That's because I have my own udev rule that sets this to 1024 when the
device shows up. 64 is the default; I set it to 1024 because whatever
mplayer version I have will warn if it can't set up a higher-frequency
timer (as a non-root user).
>> ...but I'm using the rtc_cmos (rtc-class) driver, not the older setup
>> that creates its own misc device.
>
> # CONFIG_SYSFS_DEPRECATED_V2 is not set
> CONFIG_HPET_EMULATE_RTC=y
>
> CONFIG_RTC_LIB=y
> CONFIG_RTC_CLASS=y
Yep, those two. (Along with CONFIG_RTC_DRV_CMOS below. I have it set
as a module, with the modalias autoloading it, but yeah, either way.)
> The udev rule is
>
> SUBSYSTEM=="rtc", MODE="0644", ACTION=="add", RUN+="/etc/rc.d/init.d/setclock
> start"
>
> and setclock does not have a path to hwclock, but that shouldn't be an issue
> because it just sets the time,
Right, but wasn't that the original issue? That the time wasn't being
set?
...
Hang on, no it wasn't. Hmm, helps if I read a bit more closely. :-(
> If the udev rule fires, you should have:
>
> $ ls -l /dev/rtc*
> lrwxrwxrwx 1 root root 4 Sep 12 00:43 /dev/rtc -> rtc0
> crw-r--r-- 1 root root 254, 0 Sep 12 00:43 /dev/rtc0
With the RTC class, yes.
With the RTC misc driver, not sure. That may not use the same SUBSYSTEM
-- I haven't seen any data yet from a setup like that...
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
