[quote]"microcode device doesn't exist?"[/quote] Try grepping for 'microcode' in /var/log/messages, try dmesg | grep microcode, either or both may give you the exact text. chkconfig --list | grep microcode may also give you a hit, if yes, the problem is easy to cure: turn off the service (man chkconfig).
If these don't give hits, then it's time to build a kernel for your hardware and desires, switching 'microcode' stuff off.
Brian Brunner brian.t.brunner@gai-tronics.com (610)796-5838
dave@tokyocomedy.com 09/12/05 09:31AM >>>
If I boot with "rhgb quiet" off, my computer boots in 1 minute and 30 seconds.
If I boot with "rhgb quiet" on, my computer boots in 3m11s. That's a long time to wait.
Significantly, when booting with "rhgb quiet", right at the moment X takes over, there is a 1m36s pause where the screen is blank except for the hourglass cursor turning around and around.
Of course, if my main priority was to simply boot quickly, I would simply remove the "rhgb quiet" option from the boot process. And I'm not opposed to doing that.
However, this pause only started happening recently, so I wonder why it exists at all.
When booting with "rhgb quiet" off, I tried to look for any errors or indications of a problem, but it seemed to boot mostly without pause or error. There was one message which was like an error warning, which said something about a "microcode device doesn't exist?". But text was moving across the screen quickly and I couldn't write down exactly what it said.
Before I give in and remove the "rhgb quiet" option permanently, is there any way I might be able to diagnose and fix this delay problem? I'd rather be telling the computer how to boot, instead of it telling me.
Dave _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept for the presence of computer viruses.
www.hubbell.com - Hubbell Incorporated
Brian T. Brunner wrote:
[quote]"microcode device doesn't exist?"[/quote] Try grepping for 'microcode' in /var/log/messages, try dmesg | grep microcode, either or both may give you the exact text. chkconfig --list | grep microcode may also give you a hit, if yes, the problem is easy to cure: turn off the service (man chkconfig).
My Athlon XP 2600+ system gives me this every boot with no apparent problems. I've seen this with other non-Intel CPUs too. I suspect this is NOT what is causing your boot delay.
Just my $.02!
On Sep 12, 2005, at 10:11 AM, Jay Leafey wrote:
Brian T. Brunner wrote:
[quote]"microcode device doesn't exist?"[/quote] Try grepping for 'microcode' in /var/log/messages, try dmesg | grep microcode, either or both may give you the exact text. chkconfig --list | grep microcode may also give you a hit, if yes, the problem is easy to cure: turn off the service (man chkconfig).
My Athlon XP 2600+ system gives me this every boot with no apparent problems. I've seen this with other non-Intel CPUs too. I suspect this is NOT what is causing your boot delay.
Just my $.02!
Jay Leafey - Memphis, TN jay.leafey@mindless.com _______________________________________________
The message comes from (on one of my systems) /etc/init.d/microcode_ctl
which is part of the kernel-utils package.
I started getting this message when I upgraded to CentOS 4. My installed kernel-utils is version 2.4-13.1.66. Is this meant for version 2.4 kernels and if so, is there a version for 2.6 kernels? I don't see anything listed with "yum list available"
Tony Schreiner Boston College
-
Brian T. Brunner -
Jay Leafey -
Tony Schreiner