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 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. > > this helped! You are right, no hpet clocksource available on my system. I followed your advice and selected acpi_pm.
dhcppc2:/home/georg # cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc acpi_pm jiffies dhcppc2:/home/georg # cat /sys/devices/system/clocksource/clocksource0/current_clocksource acpi_pm Ok, now I'll wait and see how the behaviour of the clock is now :-) >> 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 > > No,never! I am just no "give me 2 seconds" man, more a ruminant with small pieces of unknown stuff, spitting out the result 2 months later. Once again, thank you very much for your help!!! Georg ------------------------------------------------------------------------- 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
