From: GertJan Spoelman <kl@gjs.cc>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Microcode update driver
Date: Sat, 27 Apr 2002 22:04:06 +0200 [thread overview]
Message-ID: <200204272204.06592.kl@gjs.cc> (raw)
In-Reply-To: <Pine.LNX.4.44.0204272141010.2833-100000@mustard.heime.net>
On Saturday 27 April 2002 21:42, Roy Sigurd Karlsbakk wrote:
> On Sat, 27 Apr 2002, Matthew M wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Saturday 27 April 2002 7:57 pm, Roy Sigurd Karlsbakk wrote:
> > > Sorry if this is a FAQ, but where's the microcode.dat supposed to be
> > > placed? I can't find any information about that in the doc.
> >
> > /usr/share/misc/microcode.dat
>
> hm... but... Isn't the microcode update being done during kernel boot?
> I rarely have a system set up with /usr on the same fs as /
On my system it lives in /etc, but you can place it anywhere you want, see the
part below which I copied from the microcode README
***************************************************************************
>>> updating every system boot
***************************************************************************
A simple script has been included for systems to apply the microcode
update on boot. The script is a good illustration on how to use the
utility but it may be useful to run through some basic usage.
Without using the provided startup script, to update your microcode and
free the internal buffer on every system boot you'll need to add a line
like the following to /etc/rc.d/rc.local (where prefix indicates the
location of the binary)
prefix/microcode_ctl -iu
or to specify another microcode file
prefix/microcode_ctl -if /etc/microcode.dat
Simple as that. Problems? Contact either myself at simon@veritas.com or
Tigran at tigran@veritas.com
next prev parent reply other threads:[~2002-04-27 20:04 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
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 [this message]
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=200204272204.06592.kl@gjs.cc \
--to=kl@gjs.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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