I got hwclock to work by using the "--directisa" parameter.
Must be related to the mainboard/BIOS of the various Dell systems. I talked to a support guy and he confirmed that different PowerEdge systems have totally different BIOSes and mainboards. Although he has not heard of my problem before...
Now the last question: When I shut down the system it tries to sync the system time into the hardware clock and it gets the exact same error. How do I tell this process to use the "--directisa" parameter? Is there a config file or do I have to modify the respective file in etc/init.d directly?
markarnold
1 Rookie
•
3 Posts
0
April 25th, 2005 19:00
A quick update:
I got hwclock to work by using the "--directisa" parameter.
Must be related to the mainboard/BIOS of the various Dell systems. I talked to a support guy and he confirmed that different PowerEdge systems have totally different BIOSes and mainboards. Although he has not heard of my problem before...
Now the last question: When I shut down the system it tries to sync the system time into the hardware clock and it gets the exact same error. How do I tell this process to use the "--directisa" parameter? Is there a config file or do I have to modify the respective file in etc/init.d directly?
Thanks,
MARK
TriplePC-Mike
6 Posts
0
April 26th, 2005 20:00
Simply modify it there.
If you update your packages, this change may be overwritten.
markarnold
1 Rookie
•
3 Posts
0
April 27th, 2005 15:00
Actually, I found that the right thing to do is adding a line
CLOCKFLAGS='--directisa'
into the file "/etc/sysconfig/clock". This file (and the variable) is read by both the "halt" and the "rc.sysinit" scripts.
MARK
Ricky42
19 Posts
0
May 10th, 2005 04:00
Thanks! That was what I was looking for for my Fedora FC4 Test2 and a Poweredge 800 (with CERC 6-CH RAID) ...
Clock is now working fine!
Message Edited by Ricky42 on 05-10-2005 03:22 AM