rtc and chrony on Ultra 1 and Ultra 5
Hi,
I am kernel running 2.4.27 on my Ultra 1 and Ultra 5.
If I comment in ("remove the hash in front of")
| rtcfile /var/lib/chrony/chrony.rtc
in /etc/chrony/chrony.conf chrony trashes syslog on start:
,----
| Apr 19 11:57:05 radioactive chronyd[767]: chronyd version V1_20 starting
| Apr 19 11:57:05 radioactive chronyd[767]: Initial txc.tick=10001 txc.freq=-147469 (-2.25019836) txc.offset=0 => hz=100 shift_hz=7
| Apr 19 11:57:05 radioactive chronyd[767]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
| Apr 19 11:57:05 radioactive chronyd[767]: Linux kernel major=2 minor=4 patch=27
| Apr 19 11:57:05 radioactive chronyd[767]: calculated_freq_scale=0.99902439 freq_scale=0.99902439
| Apr 19 11:57:05 radioactive chronyd[767]: Could not start measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not stop measurement : Invalid argument
| Apr 19 11:57:05 radioactive chronyd[767]: Could not read flags /dev/rtc : Invalid argument
|
| [...]
|
`----
The lines right above that entry in the chrony configuration file say:
,----
| # Specify the file where real-time clock data is stored. To use this you
| # must have enhanced real-time clock support compiled into your kernel.
| # Comment out the next line if you do not. Note: I have seen problems with
| # the rtc on some motherboards. Please file a bug if this bites you.
|
| # rtcfile /var/lib/chrony/chrony.rtc
`----
I am not sure If I have to file a bug report for chrony or ...
,----
| radioactive:/home/niehaus# dmesg | grep -i rtc
| rtc_init: no PC rtc found
`----
.. if there is a (sun specific?) configuration problem. Any hints out
there?
Thanks for reading and thinking about this!
Sebastian
Reply to: