Skip to contentSkip to conversation

Microcode update driver

DISCUSSION Matthew M 7 participants 11 messages Apr 27, 2002

lore
Share & tools
lore

Matthew M

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

When I try to update the microcode on my PIV (1.7GHz, Jetway mobo), the update fails and i see --

microcode: CPU0 no microcode found! (sig=f0a, pflags=4)

in the kernel log. I couldn't find any reference to this on google, and it's not urgent or anything; I just thought it might be helpful.

Thanks for any help

*MatthewM*
- --

Have you ever noticed that the people who are always trying to tell you `there's a time for work and a time for play' never find the time for play? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8yoxcoVQMDIAmueURAvSwAJ0f1BlZkLxL7NGyEDDXkIw2MGeSSwCeInIE 5WbS/IckoMPHgTuUbttCfFU=
=5PZ4
-----END PGP SIGNATURE-----

#1 lore raw
Quoted 9 lines · Matthew M

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

When I try to update the microcode on my PIV (1.7GHz, Jetway mobo), the update fails and i see --

microcode: CPU0 no microcode found! (sig=f0a, pflags=4)

Probably the microcode.dat file has no updated microcode for this stepping of CPU. Make sure you have the latest one from
http://www.urbanmyth.org/microcode/

But it's still possible that there is no update (yet).

Signature · 2 lines
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs
#2 lore raw
Quoted 3 lines

Probably the microcode.dat file has no updated microcode for this stepping of CPU. Make sure you have the latest one from
http://www.urbanmyth.org/microcode/

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

roy

Signature · 4 lines
Roy Sigurd Karlsbakk, Datavaktmester

Computers are like air conditioners.
They stop working when you open Windows.
author
#3 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Roy Sigurd Karlsbakk

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

/usr/share/misc/microcode.dat

*MatthewM*
- --

Failure is more frequently from want of energy than want of capital. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ywaloVQMDIAmueURAkfHAJ45eNlJ7NsOiEnRUQTjs0OFRlYp9gCcCeyI nCPiNidQN+LULkRcO9dQGo0=
=fs4b
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 8 lines · In article <m171Yag-000Ga6C@Wasteland> you wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Roy Sigurd Karlsbakk

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

/usr/share/misc/microcode.dat

hum doesn't the FHS specify that /usr/share shouldn't contain arch specific files ? microcode.dat I can't really call arch neutral....

#5 lore raw
In reply to Matthew M
Quoted 8 lines · Matthew M

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Roy Sigurd Karlsbakk

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

/usr/share/misc/microcode.dat

hm... but... Isn't the microcode update being done during kernel boot? I rarely have a system set up with /usr on the same fs as /

roy

Signature · 4 lines
Roy Sigurd Karlsbakk, Datavaktmester

Computers are like air conditioners.
They stop working when you open Windows.
#6 lore raw
Quoted 4 lines · Roy Sigurd Karlsbakk
Quoted 3 lines · Matthew M

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 8 lines
Quoted 5 lines · Roy Sigurd Karlsbakk
Quoted 2 lines

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

/usr/share/misc/microcode.dat

hm... but... Isn't the microcode update being done during kernel boot? I rarely have a system set up with /usr on the same fs as /

On my system it lives in /etc, but you can place it anywhere you want, see the part below which I copied from the microcode README

***************************************************************************

Quoted 1 line
Quoted 1 line
Quoted 1 line

updating every system boot

***************************************************************************

A simple script has been included for systems to apply the microcode update on boot. The script is a good illustration on how to use the utility but it may be useful to run through some basic usage.

Without using the provided startup script, to update your microcode and free the internal buffer on every system boot you'll need to add a line like the following to /etc/rc.d/rc.local (where prefix indicates the location of the binary)

prefix/microcode_ctl -iu

or to specify another microcode file

prefix/microcode_ctl -if /etc/microcode.dat

Simple as that. Problems? Contact either myself at [email protected] or Tigran at [email protected]

#7 lore raw
In reply to Matthew M
Quoted 9 lines · Matthew M

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Roy Sigurd Karlsbakk

Sorry if this is a FAQ, but where's the microcode.dat supposed to be placed? I can't find any information about that in the doc.

/usr/share/misc/microcode.dat

You could have asked the author of the driver (myself) or the author of microcode_ctl (Simon Trimmer) before giving your "authoritative" answer :)

The default location is /etc/microcode.dat but distributions are free to put it anywhere they like, e.g. Red Hat puts it in /etc/firmware/microcode.dat

Regards
Tigran

author
#8 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Tigran Aivazian

You could have asked the author of the driver (myself) or the author of microcode_ctl (Simon Trimmer) before giving your "authoritative" answer :)

No, that would have been too sensible :)

Quoted 3 lines

The default location is /etc/microcode.dat but distributions are free to put it anywhere they like, e.g. Red Hat puts it in /etc/firmware/microcode.dat

Yes; I have long since lost track of which parts of my system are debian and which are not. Roy: sorry for any confusion.

*MatthewM*
- --

"You can't get very far in this world without your dossier being there first."
- -- Arthur Miller
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ywVPoVQMDIAmueURAo2oAKCb1JYCRuac1A7boyYnvj88j5WlWgCgiKFO wHOpw6INae9bQgSf25pck4w=
=LZdS
-----END PGP SIGNATURE-----

#9 lore raw
In reply to Matthew M
Quoted 9 lines · Dave Jones
Quoted 8 lines · Matthew M

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

When I try to update the microcode on my PIV (1.7GHz, Jetway mobo), the update fails and i see --

Quoted 8 lines
Quoted 1 line

microcode: CPU0 no microcode found! (sig=f0a, pflags=4)

Probably the microcode.dat file has no updated microcode for this stepping of CPU. Make sure you have the latest one from
http://www.urbanmyth.org/microcode/

But it's still possible that there is no update (yet).

considering that the microcode update is one year old, I don't believe there is an update for that CPU...

François

#10 lore raw
In reply to Matthew M
Quoted 5 lines · Matthew M

microcode: CPU0 no microcode found! (sig=f0a, pflags=4)

in the kernel log. I couldn't find any reference to this on google, and it's not urgent or anything; I just thought it might be helpful.

This simply means your CPU0 is uptodate, there is no need to update anything. Don't worry about it.

Regards
Tigran