public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
Date: Thu, 03 Jul 2008 02:35:47 -0400	[thread overview]
Message-ID: <32146.1215066947@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 03 Jul 2008 07:17:16 BST." <Pine.LNX.4.61.0807030716030.10434@ginsburg.homenet>

[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]

On Thu, 03 Jul 2008 07:17:16 BST, Tigran Aivazian said:
> Hi Valdis,
> 
> On Wed, 2 Jul 2008 Valdis.Kletnieks@vt.edu wrote:
> 
> > I built the -rc8-mmotd kernel, and built it with 'CONFIG_FIRMWARE_IN_KERNEL
=n'.
> > Lo and behold, the microcode.ko was now doing a request_firmware for
> > 'intel-ucode/06-0f-06' (which makes sense, the Core2 Duo in this laptop is
> > family 6, model 15, stepping 6).  However, what I had in /lib/firmware was
> > the Intel-distributed 'microcode.dat' with updates for all the CPUs (which
> > used to work in times past).
> >
> > What's the magic incantation to take the microcode.dat and create something
> > that the firmware driver is willing to use, or is this all borked up and
> > I need to do a major rethink or fix my config?
> 
> that's because it expects the Intel-supplied microcode data and you are 
> using the old style microcode.dat data.

I fed it the stuff I downloaded today from this URL:

http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2643&OSFullName=Linux*&lang=eng&strOSs=39&submit=Go!

which gets me a microcode-20080401.dat that does the same thing.  Is there
some *other* Intel-supplied microcode data I should be getting instead?

(If I should be looking elsewhere, can somebody fix http://www.urbanmyth.org/microcode/
to point somewhere other than http://downloadcenter.intel.com/default.aspx so
people go to the right place?)
> 
> Kind regards
> Tigran
> 
> >
> > Another minor annoyance - the tg3 driver, when builtin to the kernel, would
n't
> > load the microcode in this config. It complained it couldn't get 'tigon/tg3
_tos.bin',
> > but that's almost certainly an issue with Fedora's 'nash' firmware support 
and/or
> > my understanding of it - I got *that* part working by dropping the file int
o
> > /lib/firmware/tigon and building the driver as a module. Fortunately, I don
't
> > need the tg3 driver to boot far enough to get a full udev running.
> >
> >
> 


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-07-03  7:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  1:32 Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware Valdis.Kletnieks
2008-07-03  1:43 ` Andrew Morton
2008-07-03  6:17 ` Tigran Aivazian
2008-07-03  6:35   ` Valdis.Kletnieks [this message]
2008-07-03  6:44     ` Tigran Aivazian
2008-07-03  9:23       ` David Woodhouse
2008-07-03 10:17         ` Valdis.Kletnieks
2008-07-03 10:30           ` David Woodhouse
2008-07-03 11:34             ` Valdis.Kletnieks
2008-07-03 12:21               ` David Woodhouse
2008-07-03 12:41                 ` Kay Sievers
2008-07-03 12:45                   ` David Woodhouse
2008-07-03 13:03                     ` Kay Sievers
2008-07-03 13:26                       ` David Woodhouse
2008-07-03 13:54                       ` Valdis.Kletnieks
2008-07-03 15:23                         ` David Woodhouse
2008-07-03 13:48                 ` Valdis.Kletnieks
2008-07-03 10:22         ` Kay Sievers
2008-07-03 10:42           ` David Woodhouse
2008-07-03 11:32             ` Kay Sievers
2008-07-03  9:24       ` Giacomo A. Catenazzi
2008-07-03 13:56         ` Arjan van de Ven
2008-07-03 15:54           ` David Woodhouse
2008-07-03 16:22             ` Giacomo A. Catenazzi

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=32146.1215066947@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@aivazian.fsnet.co.uk \
    /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