From: "François Cami" <stilgar2k@wanadoo.fr>
To: Dave Jones <davej@suse.de>
Cc: Matthew M <matthew.macleod@btinternet.com>, linux-kernel@vger.kernel.org
Subject: Re: Microcode update driver
Date: Sat, 27 Apr 2002 14:05:21 +0200 [thread overview]
Message-ID: <3CCA9401.7040308@wanadoo.fr> (raw)
In-Reply-To: <m171QRZ-000Ga6C@Wasteland> <20020427134241.H14743@suse.de>
Dave Jones wrote:
> On Sat, Apr 27, 2002 at 12:32:42PM +0100, Matthew M wrote:
> > -----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)
>
> Probably the microcode.dat file has no updated microcode for this
> stepping of CPU. Make sure you have the latest one from
> http://www.urbanmyth.org/microcode/
>
> But it's still possible that there is no update (yet).
>
considering that the microcode update is one year old, I don't believe
there is an update for that CPU...
François
next prev parent reply other threads:[~2002-04-27 11:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 11:32 Microcode update driver Matthew M
2002-04-27 11:42 ` Dave Jones
2002-04-27 12:05 ` François Cami [this message]
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=3CCA9401.7040308@wanadoo.fr \
--to=stilgar2k@wanadoo.fr \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.macleod@btinternet.com \
/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