charliem_1216 wrote:
>
> OK, that's a different problem. I guess either you have static
device
> nodes, or startup scripts are creating the device node /dev/rtc
> (major 10, minor 135), when actually you don't really have the
older
> style rtc device. You _do_ get the new rtc0, as indicated by your
> logs when you insert the module, but you _don't_ have the character
> device for it in /dev.
>
> [BTW, You can find a detailed explanation of the older PC-centric
> (rtc) and the newer (rtc0, rtc1, ...) devices in your kernel tree:
> Documentation/rtc.txt.]
>
> So, try these: * cat /proc/driver/rtc (check capabilities of new
rtc
> driver) * cd /dev * mknod rtc0 c 254 0 * ln -nsf rtc0 rtc * hwclock
>
> If this works, the longer term solution is (1) to update your udev
or
> static device nodes to be sure /dev/rtc0 shows up, and (2) upgrade
> to a hwclock that knows to try /dev/rtc0 if /dev/rtc is not
> available.
>
> Regards, .......... Charlie
Hi Charlie;
Here's the first:
m("ts7200","root");:init.d#">:init.d# cat /proc/driver/rtc
rtc_time : 15:53:51
rtc_date : 2008-01-23
24hr : yes
mode : bcd
battery : ok
After making the link and trying hwclock again, I get the same error
message:
:dev# hwclock
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
I also tried making the device node with 10 135 which is what my Gentoo
desktop is set up with, but it made no difference.
So it appears from dmesg that the device is being registered as rtc0
(what does that mean, incidentally?), and the kernel at least is able
to read it correctly and displays the date and time in
/proc/driver/rtc. But somehow this isn't being associated with a
/dev/rtc or /dev/rtc0 the way hwclock thinks it should?
Regards,
--Jeff
__._,_.___
![]()
__,_._,___
|
|