From: jhf@rivenstone.net (Joseph Fannin)
To: tigran@veritas.com
Cc: linux-kernel@vger.kernel.org
Subject: microcode driver fails on PIII-Celeron
Date: Mon, 5 May 2003 15:43:29 -0400 [thread overview]
Message-ID: <20030505194329.GA2094@rivenstone.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
The microcode driver in the kernel fails for me on my laptop with
a PIII-era Celeron 900. I've tested both 2.4 and 2.5 kernels over
course of a year or so; all abort with the same error when trying to
load the microcode:
microcode: CPU0 no microcode found! (sig=68a, pflags=32)
My amateur reading of the code leads me to think the processor
might be misidentified somehow (or something, my head doesn't like bit
operations).
/proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Celeron (Coppermine)
stepping : 10
cpu MHz : 897.366
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1773.56
FWIW, this is a Debian unstable system, using the microcode
utilities as packaged for Debian. The laptop is a Dell Inspiron 2500,
based on the i815 chipset.
Is this a bug, or is this really not supposed to work?
--
Joseph Fannin
jhf@rivenstone.net
"That's all I have to say about that." -- Forrest Gump.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-05-05 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 19:43 Joseph Fannin [this message]
2003-05-05 20:51 ` Tigran Aivazian
2003-05-05 20:53 ` Tigran Aivazian
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=20030505194329.GA2094@rivenstone.net \
--to=jhf@rivenstone.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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
all inboxes | Powered by JetHome®