meino.cra...@gmx.de wrote: > > As I wrote the kernel is configured > > > CONFIG_RTC_HCTOSYS=y > CONFIG_RTC_HCTOSYS_DEVICE="rtc0" > > so there is no module, the functionality is compiled into the kernel. > > And as I wrote I am using the ntp_client to set the system time via > ntp/ntp_client later in the boot process to get the correct system > time. >
When I built my new rig, I had to use chrony to set my clock for a good long while. For some reason, ntp just plain failed. After ntp had several updates and bug fixes, I tried it again and it now works fine. Could be that maybe something is buggy and affects your system, similar to the way it did on mine, and you need to either back up a few versions, run unstable if you are not already or as I did, try chrony for a while until ntp gets fixed. I never did figure out why ntp failed on me. I do know my clock was awful without something keeping it on track. If you choose to use chrony, I'd be glad to share my config and help you set it up. I think I still got the commands to finds the closest time server and stuff. It about runs with default settings tho. Dale :-) :-) P. S. Here is the info: chrony.conf ! Use the exclamation mark to comment lines and not the # key. server 64.6.144.6 server 67.159.5.90 server 67.59.168.233 server 204.62.14.98 driftfile /etc/chrony.drift logdir /var/log/chrony log measurements statistics tracking rtc You may not want the last line. It logs a LOT. I used it for testing. Note: Use ! to comment instead of #. Weird. Command to find closest servers: # A good way to get servers for your machine is: # netselect -s 3 pool.ntp.org # netselect -s 3 0.gentoo.pool.ntp.org Just pick the ones with the least delay. Now I'm gone. -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
