Red Hat Bugzilla – Bug 29558
Real Time Clock Driver v1.09
Last modified: 2007-04-18 12:31:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.17-14 i586)
I used your RHN Update agent to update my RH 7 machine. I am inside the a
firewall so I have to install socks on my machine. My machine now stops on
the Real Time Clock Driver v1.09. I just hit the enter key and it
continues. How can I fix it so I dont have to hit enter key? Thanks
Steps to Reproduce:
This bug is not timetool-related and belongs to the up2date or rhn_register
there is no way that up2date did this, you are having kernel problems.
what kernel are you running? (rpm -q kernel)
contents of /etc/lilo.conf? (cat /etc/lilo.conf)
This would be an IBM netfinity ?
No.. This is a normal pc.. P166
I just did a manual upgrade from kernel 2.2.16-22 to 2.2.17-14 and I now have
the same problem: system hangs when booting at Real Time Clock Driver v1.09.
Pressing any key continues the boot and system appears to run normally.
When booting to the saved kernel 2.2.16-14 the system does not hang.
Motherboard is SuperMicro P6SNE (Intell 440X chipset) with a 200MHz Pentium Pro
The upgrade I did over your RedHat Network I think got rid of the old kernel..
I go into boot and 2.2.16-14 doesn't show up anywhere.
No my machine is a IBM pentium 166
I see that this bug is categorized as a i586 problem.
Please note that I installed the i686 version of the kernel on my Pentium Pro
machine that has the problem. I have no idea at what point a processor steps
from a i586 to a i686, but the original RH 7.0 instal identified it as a i686
I did two other upgrades to 2.2.17-14 on i386 systems (a 486-DX2 and a 66MHz
Pentium I system). Neither exhibit this pause at the Real Time Clock Driver
So what do I do??
I too have the problem:
- RHL7 on a clone. P166 non-MMX CPU. Intel 430FX chipset, Intel motherboard.
- installed the 2.2.17-14 kernel from the updates (rpm -i, not -F)
- booting pauses after "Real Time Clock Driver v1.09" until I tap a key
(I happen to press Ctrl, or F12, but I'd bet any key would work)
- The important message might be the first after the pause:
"Toshiba System Managment Mode driver v1.7 22/6/2000"
- I can go back to the 2.2.16 kernel (I don't remember which one, but it was
built by Red Hat), and there is no pause.
I was just wondering if this was being worked on yet?? What should I do to correct the problem. I have no older kernel to go back to.
This seems very related to [bug 26993], "kernel 2.2.17-14 stalls at 'real time
clock' until keypress", which was reported on RH 6.2.
Turns out to be the toshiba driver ; fixed in 2.2.19