Hi all - I recently purchased an Athlon64 X2 machine, and wanted to get Linux on it asap. Well - long story short - I found my dream distro in Mandriva 2006. I have been able to tweak away most of the minor glitches (mouse, monitor etc) but there is a strange bug that i can't even find the culprit for.
Every once in a while, when in X, the timing on the system seems to just go south. Cursors blink at amazing rates, the clock accelerates to about 10 mins per min. If i shut down all user programs, and shut down X - then restart X, everything comes back fine.
Anyone got any ideas. I did see similar clock behavior from running a non smp kernel.
Thanks for any and all theories on this
If it is an HP system they released a BIOS update for this (http://h10025.www1.hp.com/ewfrf/wc/s...tem=ob-36843-1)
Another fix is to pass noapic and no_timer_check to the kernel at boot.
If neither of those work some people have noticed clock issues related to frequency scaling.
Thanks for the quick reply! It is an HP system - I will try the BIOS update first.
Let me know if it works (I have an AMD64 that I have been waiting to convert to linux until I can get a driver that will work for my eth0 in 64 bit)
Still trying ...
The hp update is for a laptop - I have a dual processor desktop.
Tried the other like:
hung on start up looks like during hw detection-
append="splash=silent noapic no_timer_check"
tried just noapic ... hung
tried just no_timer_check ... hung
I havn't done anything with networking yet - still trying to get one machine in satisfactory shape first ;-)
i'm actually looking to shut off eth check at startup - do you know the file?
oops - i lied <blush>
I just realized in all the rebooting - i never tried just no_timer_check - that seems to be booting normally ... YES!
Now to see if it fixes the problem - I'll report back here in a day or so.
Thanks, it worked ...
The no_timer_check seems to have done the job for me.
Next is my usb - serial modem connection ... then ...
an endless list of fun stuff to do!
Well - That wasn't it...
The crazy clock thing returned despite the no_timer_check.
The symptoms are:
I notice the clock updating minut every second.
as root set clock through use of
then startx again - clock stoill crazy - so i shut doiwn X.
date --set="date stuff"
keyboard is now locked! I have to hard boot. :-(