From: "J.A. Magallón" <jamagallon@ono.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Wrong path for ucode in udev
Date: Wed, 18 Nov 2009 01:22:58 +0100 [thread overview]
Message-ID: <20091118012258.765b7b74@werewolf.home> (raw)
Hi...
I'm trying to see if my CPU needs an ucode update or not.
I want to see if I get positive feedback from the kernel, but I see a couple
problems:
- I hacked the firmware.sh script with a couple debug lines:
logger "$DIR/$FIRMWARE"
logger /sys$DEVPATH
And i get this:
Nov 17 17:01:53 bran logger: /lib/firmware/intel-ucode/0f-02-09
Nov 17 17:01:53 bran logger: /sys/devices/platform/microcode/firmware/microcode
In that second path, firmware.sh looks for /data, /loading, etc.
The problem is that path _doesn't exist_.
Is firmware.sh out of date ? Or the kernel is missing something ?
- The kernel does not give any info about successful load, even when microcode_ctl
writes to /dev/cpu/microcode (as the split files still do not exist...)
Any ideas ?
kernel is 2.6.31.6, udev is 147.
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2010.0 (Cooker) for x86_64
Linux 2.6.29.3-desktop-1mnb (gcc 4.3.2 (GCC) #1 Wed May
reply other threads:[~2009-11-18 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091118012258.765b7b74@werewolf.home \
--to=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®