public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 14:42:05 -0600	[thread overview]
Message-ID: <AANLkTimxc62wtS6YG0iWcdVDZOEt020d5x_+Pn9f_1sa@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik=6dqsQ6dgNDfGv49xrdt-Uw7iaNftc8fcyyPU@mail.gmail.com>

On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
>> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht <markknecht@gmail.com> wrote:
>>> OK, I got it to load by hand:
>>>
>>> 1) emerge microcode-ctl
>>>
>>> which also emerges microcode-data. Unfortunately microcode-data looks
>>> to be out of date.
>>
>> The ebuild for newer versions (including the latest 20101123) is in
>> portage as ~amd64 and ~x86.
>>
>>
>
> Thanks Paul.
>
> Also, it does seem to work, for Intel anyway, as a module or built
> into the kernel. I chose to build it in as I'm tired of how long lsmod
> is looking these days.

If you use the /etc/init.d/microcode_ctl runscript and have
MICROCODE_UNLOAD="yes" set in /etc/conf.d/microcode_ctl (which is the
default), it will unload the module automatically after it runs, so
you shouldn't see it in lsmod anyway, and saves a few kb of memory.
But, quite honestly, 8kb of memory is probably inconsequential on a
system where microcode_ctl is being used in the first place... :)



  reply	other threads:[~2011-01-18 21:05 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
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 [this message]
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=AANLkTimxc62wtS6YG0iWcdVDZOEt020d5x_+Pn9f_1sa@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