i'm running on vmware system and HP proliant DL360 G5 servers
on wmware, on boot i have the following message:
----------------------------- Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK] -----------------------------
and on a HP proliant DL360 G5 server , on boot i have too the following message:
----------------------------- Applying Intel Microcode update: don't know to make device "cpu/microcode" etc/rc3.d/S00microcode_ctl: microcode device /dev/cpu/microcode doesn't exist? [OK] -----------------------------
Why this message, warning ?
Denis MACHARD mailto:d@enst-bretagne.fr
On Wed, 29 Nov 2006, Denis Machard wrote:
Date: Wed, 29 Nov 2006 11:42:20 +0100 From: Denis Machard dmachard@fr.netcentrex.net Reply-To: CentOS mailing list centos@centos.org To: 'CentOS mailing list' centos@centos.org Subject: [CentOS] microcode_ctl
i'm running on vmware system and HP proliant DL360 G5 servers
on wmware, on boot i have the following message:
Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK]
and on a HP proliant DL360 G5 server , on boot i have too the following message:
Applying Intel Microcode update: don't know to make device "cpu/microcode" etc/rc3.d/S00microcode_ctl: microcode device /dev/cpu/microcode doesn't exist? [OK]
Do you have i686 kernel running (rather than i586) ? I had such message on Fedora Core 6 which installed i586 kernel on my PIII CPU.
Wojtek
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wednesday 29 November 2006 11:42, Denis Machard wrote:
i'm running on vmware system and HP proliant DL360 G5 servers
on wmware, on boot i have the following message:
Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK]
microcode_ctl is seldom needed, just turn it off and rely on your bios to properly update your CPUs.
/Peter
microcode_ctl is seldom needed, just turn it off and rely on your bios to properly update your CPUs.
and make sure your BIOS is updated and knows about your specific CPU ... AFAIK, this is mostly a Intel thing. If you look up the 'sspec' of your CPU in the specification updates on http://developer.intel.com, I believe it will describe what specific fixes were applied. some are trivial, some serious.