public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] microcode applied?
Date: Mon, 8 Jan 2018 16:41:17 +1100	[thread overview]
Message-ID: <CAC=wYCFvcb-Qcv0V7FdMYRueVp3R+=jMOOe8UVS9z8nw70pQLA@mail.gmail.com> (raw)
In-Reply-To: <CACjvM=dnZiLnp541C5yb4DDkFOU=3EKWBNeowV7G9gJyn0AAPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

On Mon, Jan 8, 2018 at 3:55 PM, Max Zettlmeißl <max@zettlmeissl.de> wrote:

> > The contents of cpuinfo is the same as the messages in dmesg. What does
> that
> > imply?
>
> Your BIOS or EFI might already install the same version or a later
> version than what the microcode package provides. Although the second
> case is highly unlikely.
> The update might also just not get applied properly.
>
> You should check whether the actual microcode version is the version
> which you expect.
>
> How are you trying to apply the microcode?
> The best way to update your processor's microcode is via early
> microcode loading.
> You can either use an initrd or build the microcode into your kernel
> image. I prefer the latter.
>
>
Yes the microcode is in the the kernel. Equivalent config works fine on
another machine.

The problem could be;
The firmware from /lib/firmware is that same as that on the system, so its
not required
The firmware loaded successfully, but didnt write a success log
The firmware failed to load (and didnt write a failure log, but we dont
expect it to)

Since I dont know where look up firmware version numbers i'm in the dark.

[-- Attachment #2: Type: text/html, Size: 1826 bytes --]

  reply	other threads:[~2018-01-08  5:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  3:24 [gentoo-user] microcode applied? Adam Carter
2018-01-08  4:01 ` Max Zettlmeißl
2018-01-08  4:23   ` Adam Carter
2018-01-08  4:55     ` Max Zettlmeißl
2018-01-08  5:41       ` Adam Carter [this message]
2018-01-08  9:05         ` Max Zettlmeißl
2018-01-08 11:53           ` Mick
2018-01-09 14:21             ` [gentoo-user] " Holger Hoffstätte
2018-01-09 14:31               ` Holger Hoffstätte
2018-01-08 10:14       ` [gentoo-user] " Peter Humphrey
2018-01-08 10:29         ` Max Zettlmeißl
2018-01-09  0:15           ` Peter Humphrey
2018-01-09  7:31             ` Mick
2018-01-09  9:33               ` Peter Humphrey
2018-01-09  8:43             ` Neil Bothwick
2018-01-09  8:56             ` Adam Carter
2018-01-09  9:58               ` Adam Carter
2018-01-09  9:02             ` Jorge Almeida
2018-01-08 21:22         ` Adam Carter
2018-01-08  4:42   ` mad.scientist.at.large
2018-01-08 13:52     ` Rich Freeman
2018-01-09  9:26       ` Wols Lists
2018-01-09 13:35         ` Rich Freeman
2018-01-08 17:55 ` Corbin Bird

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='CAC=wYCFvcb-Qcv0V7FdMYRueVp3R+=jMOOe8UVS9z8nw70pQLA@mail.gmail.com' \
    --to=adamcarter3@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