Messages in this thread | | | Subject | Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware... | From | Valdis.Kletnieks@vt ... | Date | Thu, 03 Jul 2008 02:35:47 -0400 |
| |
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. > > > > >
[unhandled content-type:application/pgp-signature] | |