From: Matthew M <matthew.macleod@btinternet.com>
To: linux-kernel@vger.kernel.org
Subject: Microcode update driver
Date: Sat, 27 Apr 2002 12:32:42 +0100 [thread overview]
Message-ID: <m171QRZ-000Ga6C@Wasteland> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
When I try to update the microcode on my PIV (1.7GHz, Jetway mobo), the
update fails and i see --
microcode: CPU0 no microcode found! (sig=f0a, pflags=4)
in the kernel log. I couldn't find any reference to this on google, and it's
not urgent or anything; I just thought it might be helpful.
Thanks for any help
*MatthewM*
- --
Have you ever noticed that the people who are always trying to tell you
`there's a time for work and a time for play' never find the time for play?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8yoxcoVQMDIAmueURAvSwAJ0f1BlZkLxL7NGyEDDXkIw2MGeSSwCeInIE
5WbS/IckoMPHgTuUbttCfFU=
=5PZ4
-----END PGP SIGNATURE-----
next reply other threads:[~2002-04-27 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 11:32 Matthew M [this message]
2002-04-27 11:42 ` Microcode update driver Dave Jones
2002-04-27 12:05 ` François Cami
2002-04-27 18:57 ` Roy Sigurd Karlsbakk
2002-04-27 20:14 ` Matthew M
2002-04-27 19:19 ` arjan
2002-04-27 19:42 ` Roy Sigurd Karlsbakk
2002-04-27 20:04 ` GertJan Spoelman
2002-04-27 20:03 ` Tigran Aivazian
2002-04-27 20:08 ` Matthew M
2002-04-27 20:05 ` Tigran Aivazian
[not found] <Pine.LNX.4.44.0204272150130.2833-100000@mustard.heime.net>
2002-04-27 20:01 ` Matthew M
2002-04-27 20:15 ` Tigran Aivazian
2002-04-27 20:34 ` Roy Sigurd Karlsbakk
2002-04-27 20:43 ` Tigran Aivazian
[not found] <fa.fn3ukrv.1ghovg0@ifi.uio.no>
[not found] ` <fa.hho4jnv.11lkl19@ifi.uio.no>
2002-04-29 8:59 ` Giacomo Catenazzi
2002-04-29 10:39 ` Arjan van de Ven
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=m171QRZ-000Ga6C@Wasteland \
--to=matthew.macleod@btinternet.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