From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Rankin <rankincj@yahoo.com>,
tigran@veritas.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Loading Pentium III microcode under Linux - catch 22!
Date: Thu, 7 Aug 2003 17:21:11 +0200 [thread overview]
Message-ID: <20030807152111.GF7094@louise.pinerecords.com> (raw)
In-Reply-To: <1060267992.3168.70.camel@dhcp22.swansea.linux.org.uk>
> [alan@lxorguk.ukuu.org.uk]
>
> 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
Sure does. There are machines (like the HP tc2100) which
always freeze entirely as soon as a PS/2 keyboard is attached.
> > > 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)
and /etc/rc.d/rc.S on BSDish systems I believe.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-08-07 15:26 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
2003-08-07 15:21 ` Tomas Szepe [this message]
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=20030807152111.GF7094@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=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®