Hi,
I have Mandrake 9.0 on a laptop. When I resume after a suspend on disk,
system clock is 8 times slower. It's very annoying and I must reboot.
Any idea ?
Thanks.
--
Philippe BOURDEU d'AGUERRE
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
DataChannel wrote:
What does it mean when probable hardware bug: clock timer configuration
lost - probably a VIA686a motherboard. scrolls up in my logs at random
intervals between once every 10 seconds to once every 45 minutes on a
motherboard (GA-5AX) that doesn't have a VIA chipset on a
. The erroneous clock throws off the probe software
producing the spike.
-JMS
[EMAIL PROTECTED]
|-Original Message-
|From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
|Of Bill Thompson
|Sent: Sunday, September 02, 2001 5:03 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [expert] Clock
What does it mean when probable hardware bug: clock timer configuration
lost - probably a VIA686a motherboard. scrolls up in my logs at random
intervals between once every 10 seconds to once every 45 minutes on a
motherboard (GA-5AX) that doesn't have a VIA chipset on a fresh
installation
Maybe your bios battery is flat!
Don wrote:
I am trying to figure out why does not Mandrake 7.2, and/or KDE2.0 see the
system clock? Whenever I reboot this system the time gets reset to 00:00:00
and starts counting from there. I usually reset the clock in KDE, but must
reset the clock
No That was not the problem, I just reflash the BIOS to BP6RU125.bin BIOS,
and the problem is still here. I think it has something to do with the
/etc/rc.d/rc.sysinit fle in Mandrake 7.2, because that is the file that sets
the time at boot up.
But thanks,
Don
On Tuesday 05 December
I am trying to figure out why does not Mandrake 7.2, and/or KDE2.0 see the
system clock? Whenever I reboot this system the time gets reset to 00:00:00
and starts counting from there. I usually reset the clock in KDE, but must
reset the clock each time I reboot. This is a dual boot machine,
Not a problem with mandrake. My bp6 with 550 Celerons just smokes along
with the clock dead on the national observatory time. Check your bios
rev and update it if necessary. I had to update mine to RU from NJ to
get it stable with the smp kernel in 7.2 but I've never had a clock
problem. You may
I checked the source for 6.1 (include/asm-i386/param.h) and noticed that the
interrupt is set for 100HZ.
how much of a performace increase could be expected if this were increased (and
the appropriate utilties were patched so they wouldn't break)? this would
primarily affect the scheduler,
