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 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 I'd try acpi_pm first and then jiffies. Any way, jiffies should be 
the last, since it's only a simple CPU-cycle counter. But it may still work 
well if you use ntpd for network time synchronization.

> May be my OpenSUSE is lacking something? Ok, at least it was worth
> trying and I learned something new.

Don't give up too early :)

Regards,
Stefan

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to