Red Hat Bugzilla – Bug 542215
firmware.sh is out of step with microcode-ctl
Last modified: 2010-06-25 07:49:05 EDT
Description of problem:
modprobe microcode results in error messages:
Nov 28 16:32:14 mail kernel: microcode: CPU0 sig=0x106a5, pf=0x2, revision=0x11
Nov 28 16:32:14 mail kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
(repeat for each cpu).
microcode_ctl -f <file> may or may not be loading the correct file - there is no easy way to see.
A few obvious issues:
1) microcode-ctl intel firmware is stored generically in /lib/firmware/microcode.dat. firmware.sh is looking for intel-ucode/06-1a-05 in various places including /lib/firmware.
2) Assuming you've got the correct microcode stored in /lib/intel-ucode/06-1a-05, the script then tries to set the 'loading" indicator at /sys/devices/platform/microcode/firmware/microcode/loading. That doesn't exist. Looking at the kernel driver, it doesn't look like it's even used anymore.
When I comment out the "loading" lines and override the FIRMWARE variable with /lib/firmware/microcode.dat and then modprobe microcode, I get log messages that suggest success:
Nov 28 16:52:47 mail kernel: microcode: CPU0 sig=0x106a5, pf=0x2, revision=0x11
Nov 28 16:52:47 mail kernel: platform microcode: firmware: requesting intel-ucode/06-1a-05
repeated for each cpu
Version-Release number of selected component (if applicable):
Was also true for fc12 versions - dk about 11.
1) the kernel requests the file, so it should be present in the file system with that name. Maybe a softlink should be provided by the package which provides micocode.dat.
2) I will fix the script to test for the existence of the "loading" file first.
Created attachment 381748 [details]
Please add a symlink to the firmware file in /lib/firmware and test this firmware.sh script, if it fixes your problems.
Fixed - however now that the firmware is found, the loading is unacceptably slow.
There are at least two other bugs open for that, so I'd say let's close this one.
Fedora Bugzappers volunteer triage team
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here: