It looks like there is a compatibility problem with the
810 series of Intel M-boards (I'm using RH 6.0 but I
expect this issue with earlier versions as well). This
is a Celeron board, my experience has been with two
CA810 boards, the BIOS version of one of them is Phoenix
8c1a100a.86a.0010.p03 (really) and I've come across the
Apparently, the on-board clock doesn't provide a tick for
the system clock to sync to, and rc.sysinit hangs setting
the system clock (/sbin/hwclock). Apparently ctrl-c will
bypass the hang, but I haven't tried tried that.
If the clock section of rc.sysinit is commented out, it
will boot, but expect problems (networking, filesystem,
etc) from not setting the clock. A better solution might
be to write a script to request current time at boot-up
then run a script to set it more accurately from the
rdate -s <url of a timeserver>
Some links on the board...
Do you have another example on this? Quoting the post:
Never mind, I'm banging my head on the keyboard right now. The
motherboard was faulty.
Actually the motherboard was faulty. The bios clock would not advance.
When Linux boots it waits for 1 tick of the clock before booting.
I troubleshot linux to death before even looking at the hardware.
Lesson well learned.
-- original author
Their have been two additional instances that I've been made aware of.