Stefan Seifert schrieb:
On Sunday 27 April 2008 23:53:01 Georg Vollnhals wrote:
default 0
timeout 8
clock=hpet
This is wrong. The kernel parameters are following the file name in
the kernel line. This is the section I boot on my server:
###Don't change this comment - YaST2
On Monday, 28. April 2008, Georg Vollnhals wrote:
But checking the result is disappointing. I did it after 3 boot cycles
(2 reboot and one cold boot):
dhcppc2:/home/georg # cat
/sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Maybe your system simply doesn't have a hpet
Hi Stefan,
Stefan Seifert schrieb:
Maybe your system simply doesn't have a hpet clocksource. For example my
system at home only has:
acpi_pm jiffies tsc
You can get the available clocksources by issuing:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
In my case
Georg Vollnhals wrote:
Hi Stefan,
Stefan Seifert schrieb:
Maybe your system simply doesn't have a hpet clocksource. For example my
system at home only has:
acpi_pm jiffies tsc
You can get the available clocksources by issuing:
cat
Jon Stockill schrieb:
Assuming the machine has an internet connection - if you install ntp and
set it to sync from pool.ntp.org you'll never need to worry about such
problems again - it'll sync from an internet clock source within a few
minutes of starting up, and then stay in sync.
Jon
Stefan Seifert schrieb:
On Saturday 26 April 2008 21:08:15 Georg Vollnhals wrote:
Sorry for that - my new O/S OpenSUSE 10.3 has some difficulties with my
hardware-clock - at least using Wine changes the time and day and I have
to correct that manually. And a time-jump would be nicer
On Sunday 27 April 2008 23:53:01 Georg Vollnhals wrote:
default 0
timeout 8
clock=hpet
This is wrong. The kernel parameters are following the file name in
the kernel line. This is the section I boot on my server:
###Don't change this comment - YaST2 identifier: Original name: linux###
title
7 matches
Mail list logo
