From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode update AMD
Date: Tue, 18 Jan 2011 09:38:40 -0600 [thread overview]
Message-ID: <AANLkTimPyrBHCq5TVQtRYB7NBCO55p5yiwp0AfBpKbde@mail.gmail.com> (raw)
In-Reply-To: <1295324985.21821.37.camel@rattus>
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy <billk@iinet.net.au> wrote:
> The bios microcode update is likely an enable setting rather than the
> bios actually updating the cpu. You need to do some reading/asking of
> the manufacturers (not here) if it bothers you.
Thanks for the links, I didn't realize they made the microcode data
available separately.
From Intel's download site for the microcode data:
"The microcode data file contains the latest microcode definitions for
all Intel processors. Intel releases microcode updates to correct
processor behavior as documented in the respective processor
specification updates. While the regular approach to getting this
microcode update is via a BIOS upgrade, Intel realizes that this can
be an administrative hassle. The Linux Operating System and VMware ESX
products have a mechanism to update the microcode after booting. For
example, this file will be used by the operating system mechanism if
the file is placed in the /etc/firmware directory of the Linux
system."
next prev parent reply other threads:[~2011-01-18 16:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:21 [gentoo-user] Microcode update AMD meino.cramer
2011-01-17 18:10 ` BRM
2011-01-17 18:34 ` meino.cramer
2011-01-17 19:14 ` Volker Armin Hemmann
2011-01-17 18:48 ` Mark Knecht
2011-01-17 19:12 ` Volker Armin Hemmann
2011-01-20 0:53 ` [gentoo-user] " walt
2011-01-20 1:08 ` walt
2011-01-17 19:08 ` [gentoo-user] " Volker Armin Hemmann
2011-01-17 19:19 ` meino.cramer
2011-01-17 19:46 ` Volker Armin Hemmann
2011-01-17 19:57 ` meino.cramer
2011-01-17 20:12 ` Mark Knecht
2011-01-17 20:52 ` Volker Armin Hemmann
2011-01-18 4:29 ` William Kenworthy
2011-01-18 15:38 ` Paul Hartman [this message]
2011-01-18 16:16 ` Mark Knecht
2011-01-18 17:34 ` Mark Knecht
2011-01-18 17:48 ` Volker Armin Hemmann
2011-02-05 14:28 ` Enrico Weigelt
2011-02-05 15:26 ` meino.cramer
2011-02-05 17:07 ` Volker Armin Hemmann
2011-02-06 11:36 ` Volker Armin Hemmann
2011-01-18 17:55 ` Paul Hartman
2011-01-18 18:21 ` Mark Knecht
2011-01-18 20:42 ` Paul Hartman
2011-01-18 20:56 ` Mick
2011-01-18 21:13 ` Paul Hartman
2011-01-18 23:08 ` Mick
2011-01-18 23:56 ` Mark Knecht
2011-01-17 20:13 ` Jason Weisberger
2011-01-17 20:49 ` Volker Armin Hemmann
2011-01-17 21:59 ` Jason Weisberger
2011-01-17 23:27 ` Volker Armin Hemmann
2011-01-18 15:39 ` [gentoo-user] " Nuno J. Silva
2011-02-05 13:34 ` [gentoo-user] " Enrico Weigelt
2011-02-05 16:15 ` Florian Philipp
2011-01-18 16:27 ` Volker Armin Hemmann
2011-01-19 17:10 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimPyrBHCq5TVQtRYB7NBCO55p5yiwp0AfBpKbde@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox