Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37020 - mkinitcpio does not automatically include the firmware files for "intel-ucode" in the initrd image
Attached to Project:
Arch Linux
Opened by James (thx1138) - Saturday, 21 September 2013, 18:44 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 21 September 2013, 22:57 GMT
Opened by James (thx1138) - Saturday, 21 September 2013, 18:44 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 21 September 2013, 22:57 GMT
|
DetailsDescription:
Name : mkinitcpio Version : 0.15.0-1 Configuring, for instance, 'MODULES="radeon microcode"' in /etc/mkinitcpio.conf, a "mkinitcpio -p linux" will automatically include the firmware files from /usr/lib/firmware/radeon/, but fail to include any files from /usr/lib/firmware/intel-ucode/. Presumably, with these firmware files missing, the intel-ucode module is useless in the early-boot microcode-install. Furthermore, adding something like 'FILES="/usr/lib/firmware/intel-ucode/"' or 'FILES="/usr/lib/firmware/intel-ucode/*"' in /etc/mkinitcpio.conf fails to add the desired set of firmware files, which instead, must be enumerated explicitly in a 'FILES="..."' entry. I'm assuming that some automation is missing here... There seems to be a problem with intel-ucode interacting with udev, where the microcode module will hang for 60s per core on boot, but it is not clear that this is caused directly by the missing firmware files. Thanks James |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 21 September 2013, 22:57 GMT
Reason for closing: Won't fix
Additional comments about closing: Early userspace isn't your plaything. There's no need to load microcode firmware so early, and there's no correlation between the microcode module and firmware to make this straightforward to automate.
Saturday, 21 September 2013, 22:57 GMT
Reason for closing: Won't fix
Additional comments about closing: Early userspace isn't your plaything. There's no need to load microcode firmware so early, and there's no correlation between the microcode module and firmware to make this straightforward to automate.
Comment by Dave Reisner (falconindy) -
Saturday, 21 September 2013, 22:55 GMT
I will not support this. Do not try to load microcode from early userspace.