From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Rankin <rankincj@yahoo.com>
Cc: tigran@veritas.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Loading Pentium III microcode under Linux - catch 22!
Date: 07 Aug 2003 15:53:13 +0100 [thread overview]
Message-ID: <1060267992.3168.70.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030807143831.73389.qmail@web40603.mail.yahoo.com>
On Iau, 2003-08-07 at 15:38, Chris Rankin wrote:
> July 2000, and my current BIOS just doesn't have any
> microcode for them. Without the update, I used to come
> back at the end of the day, switch on the KVM and be
> unable to use the keyboard and mouse.
Sounds believable
> Anyway, I wasn't aware that Intel had released a
> changelist for their microcode updates. Goodness knows
> what bugs they're fixing.
Generally speaking its the ones that end "Can be worked around by
the BIOS" in the big list of errata. Some of those are however
other things like setting timing registers or turning off features
via semi-secret mtrr registers
> memory), and CPU malfunction is the leading candidate
> explanation. I have already replaced the 300W PSU with
> a 400W one and tested the memory.
Ok
> Yes, that's the "catch-22" bit. I was originally
> thinking about either a bootstrapping floppy disk, or
> maybe hacking some code into the boot-up sequence
> itself.
>
> > it can load it very early after that from initrd.
>
> OK, I'll look into that.
Looking at it you can do it in initrd fine, or you can do it
as the first thing you do once the real root fs is mounted
from init's scripts (/etc/rc.sysinit normally)
next prev parent reply other threads:[~2003-08-07 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 12:28 Chris Rankin
2003-08-07 13:04 ` Måns Rullgård
2003-08-07 13:58 ` Alan Cox
2003-08-07 14:38 ` Chris Rankin
2003-08-07 14:53 ` Alan Cox [this message]
2003-08-07 15:21 ` Tomas Szepe
2003-08-07 15:41 ` Chris Rankin
2003-08-07 23:12 ` Eyal Lebedinsky
2003-08-07 15:57 ` Tigran Aivazian
2003-08-07 15:55 ` Alan Cox
2003-08-08 8:24 ` Chris Rankin
2003-08-07 17:40 Nakajima, Jun
2004-01-13 19:00 ` Alan Cox
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=1060267992.3168.70.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.com \
--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®