[SOLVED] kernel-generic-smp-3.10.30_smp-i686 there's no RTC device

RoyBatty100 · 03-28-2014, 05:04 AM

Hi guys
I wanted use ntp on Slackware 14.1 kernel-generic-smp-3.10.30_smp-i686,
What I noticed after reboot it took ages to save hwclock and the time was incorrect.
I tried command hwclock --show and nothing, tryed /dev/rtc and rtc0 still nothing.
I have checked zgrep HCTOSYS /proc/config.gz not set.
After kernel recompilation finally I got CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0" and now everything works fine.
Hwclock shows time

and ntp works well. Question, is there an easier
way to make RTC work that way?
Thanks

allend · 03-28-2014, 09:52 AM

The short answer is no.
It appears your system does not have a persistent_clock or else it is not being recognised.

From http://lkml.iu.edu/hypermail/linux/k...4.3/00350.html
John Stultz

Quote:

Its only systems where there isn't a persistent_clock is where the RTC layer
and the HCTOSYS is helpful.

Again, if you're having a problem where an x86 system isn't getting its time
initialized correctly, please let me know the details of the system.

then Kay Sievers

Quote:

Until the above commits we always needed:
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
to get the system time correctly initialized at bootup on x86.

and John Stultz again

Quote:

On non-x86 (mostly embedded) platforms that do not have persistent_clock support, yes, the above is needed.

But I'm unaware of the above actually being necessary on x86, as its always had persistent_clock support.

RoyBatty100 · 03-28-2014, 11:06 PM

Quote:

Originally Posted by allend

The short answer is no.
It appears your system does not have a persistent_clock or else it is not being recognised.

From http://lkml.iu.edu/hypermail/linux/k...4.3/00350.html
John Stultz

then Kay Sievers

and John Stultz again

Thank you for quick reply. That did the job.