charliem_1216 wrote:
>
> Hi Jeff --
>
> You are using modules, while I always compile RTCs into the
kernel. I
> see that there are other modules required: rtc-dev (which
triggers
> udev to create the rtc0 .. rtcN device nodes) and rtc-class at
least.
>
>
> Please see if you have these modules loaded or built in. When
> configuring your kernel, look for "/dev/rtcN (character devices)",
> which selects 'RTC_INTF_DEV'.
I just rebuilt the kernel with built in rtc support and retried it. I
noticed another option for setting the system clock from the RTC as a
part of booting and selected that as well. Guess what? That works.
Check out this /var/log/messages fragment:
Jan 23 19:47:42 localhost kernel: rtc-m48t86 rtc-m48t86: rtc core:
registered m48t86 as rtc0
Jan 23 19:47:42 localhost kernel: rtc-m48t86 rtc-m48t86: battery ok
Jan 23 19:47:42 localhost kernel: TCP cubic registered
Jan 23 19:47:42 localhost kernel: NET: Registered protocol family 1
Jan 23 19:47:42 localhost kernel: NET: Registered protocol family 17
Jan 23 19:47:42 localhost kernel: rtc-m48t86 rtc-m48t86: setting the
system clock to 2008-01-24 03:46:57 (1201146
417)
Not that I see any delta in the clock afterward. But hwclock is still
DOA. So, I have an interesting situation: the kernel can read the RTC
and set itself from it, but I have no way to set the RTC. should it
ever drift very far. I guess this will have to be good enough for now.
Thanks for everyone's help - I really appreciate it.
--Jeff
__._,_.___
![]()
__,_._,___
|
|