Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
Subject: application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
Subject: X Windows problem (xauth)
Subject: Upgrading openoffice 1 1 rpm
Subject: FTP: connection refused
Subject: FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
Subject: broadcom network interface
make mrproper
Couldn 't open PID file /var/run/named/named pid Permission denied
sendmail configuration on redhat
kernel 2 6 and /dev/sound/mixer not found
Subject: Promise 378 controller
Subject: Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
Subject: Lotus Notes under Wine
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
/etc/security/limits conf question
Intel E/1000 driver
rpm database corrupt
Command stream end of file while reading
qla2300 modules
 
Subject: Problem with internal clock.

Subject: Problem with internal clock.

2003-06-19       - By MUSTIATA Bogdan

 Back
 Problem with internal clock.

 Mainly, clock is coordinated by BIOS in old operating systems, so an
overclock/change of FSB (on old system also) could affect the clock.
Mainly, the internal clock use the same FSB in order to know the track of
time. I knew a friend of mine who had a computer 486dx overclocked from
100 to 120 MHz and his clock was acting weird, running very-very fast.
Also, a simply hardware problem (clock not working physically), or BIOS
software problem (it's a program after all) could make your clock go mad.

 In what I am aware of, I know that Linux has it's own BIOS, so I don't
think your clock is damaged in this direction. The only thing I can think
is an overclock / software problem on your linux kernel side.

 What you can do, is to try to find out if your computer is overclocked
(mainly new computers know how to handle change of FSB, I belive Linux is
not so bad at this, but who knows) and also try recompile a kernel (not
recommended). I don't belive the second option is a valid one.

 Bogdan Mustiata