You are not logged in.
Hello all
I have an old system I'm trying to resurrect. It's an NVIDIA nf4 chipset, the old dfi LANPARTY boards
The date changes by itself completely randomly every few seconds - back to 2005, up to 2020, and back to 2010.
I used the date command to set a new time, and looped that in bash every second. even within the time it takes between these commands, the time changes.
This wreck networking on this system, at a minimum. I can't tell what other, pernicious effects it could be having.
I changed the button cell (CR2032 type) but it didn't help.
Anything else I can try, or is this motherboard stuffed & fit only for garbage?
Last edited by Sanjeev K Sharma (2020-06-27 19:41:29)
Offline
What clock source options are available?
cat /sys/devices/system/clocksource/*/available_clocksource
Offline
acpi_pm
What clock source options are available?
cat /sys/devices/system/clocksource/*/available_clocksource
Offline
acpm_pm should be the broken rtc. I was hoping for an alternative such as hpet or tsc.
Please try booting with the kernel paramater clocksource=jiffies
Edit:
Then set the clock once and see if it maintains the time.
Last edited by loqs (2020-06-27 18:54:13)
Offline
great, thanks
OK, with the jiffies it's maintaining the time. got networking working (but still no dhcp, it must be static for some reason).
Now I'll find a way to set it so I need not set the time manually at every boot
what I'm still noticing is that ping will do 10 or 30 lines, then I get a report
ping: warning - time of day goes back (-239852986293us) taking countermeasures
acpm_pm should be the broken rtc. I was hoping for an alternative such as hpet or tsc.
Please try booting with the kernel paramater clocksource=jiffies
Edit:
Then set the clock once and see if it maintains the time.
Last edited by Sanjeev K Sharma (2020-06-27 19:24:21)
Offline
See https://wiki.archlinux.org/index.php/Sy … ronization to automate setting the correct time.
Offline