From: Borislav Petkov <bp@alien8.de>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD C1E issue? 2.6.38.4
Date: Sat, 7 May 2011 18:21:30 +0200 [thread overview]
Message-ID: <20110507162130.GA13307@liondog.tnic> (raw)
In-Reply-To: <4DC54CE5.6050307@xs4all.nl>
Hi,
On Sat, May 07, 2011 at 03:45:09PM +0200, Udo van den Heuvel wrote:
> Hello,
>
> Saw these in my messages after enabling C1E on my new Jetway Mini-ITX board:
>
> # microcode_ctl -u
> microcode_ctl: writing microcode (length: 430080)
> microcode_ctl: error writing to '/dev/cpu/microcode' errno=22 (Invalid
> argument)
> microcode_ctl: there may be messages from the driver in your system log.
>
> microcode: AMD microcode update via /dev/cpu/microcode not supported
> microcode: AMD microcode update via /dev/cpu/microcode not supported
no, the message is correct - the AMD ucode driver doesn't support
ucode loading method through the /dev node, only through the firmware
loader. I.e., you should simply put the microcode image into
/lib/firmware/amd-ucode/ and compile the kernel microcode driver as a
module - then it'll load automatically.
> This is on kernel.org 2.6.38.4 on AMD Athlon II X2 235e on JNC84E-LF
> board, Fedora 14 for most of the rest of the stuff.
>
> Anybody can tell why the update cannot work?
> The previous board (JNC81) did not show these but also did not have C1E
> in BIOS as far as I recall.
This doesn't have anything to do with C1E.
HTH.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2011-05-07 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:45 Udo van den Heuvel
2011-05-07 16:21 ` Borislav Petkov [this message]
2011-05-07 16:30 ` Udo van den Heuvel
2011-05-08 19:00 ` Borislav Petkov
2011-05-09 9:05 ` Heinz Diehl
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=20110507162130.GA13307@liondog.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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
all inboxes | Powered by JetHome®