* [ISSUE] Support intel-ucode when using mkinitcpio
@ 2024-01-09 22:53 basploeger
2024-01-10 9:31 ` dkwo
` (11 more replies)
0 siblings, 12 replies; 13+ messages in thread
From: basploeger @ 2024-01-09 22:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
New issue by basploeger on void-packages repository
https://github.com/void-linux/void-packages/issues/48145
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.10_1 x86_64 GenuineIntel uptodate rrrmFFFFFF
### Package(s) Affected
intel-ucode-20231114_1, mkinitcpio-37_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No. But [this information](https://wiki.archlinux.org/title/microcode#Initrd_images) from Arch Linux is useful for reference.
Arch's intel-ucode package generates the necessary `/boot/intel-ucode.img` [here](https://gitlab.archlinux.org/archlinux/packaging/packages/intel-ucode/-/blob/main/PKGBUILD?ref_type=heads#L22).
### Expected behaviour
Intel microcode gets loaded in early boot before loading the initramfs produced by mkinitcpio.
### Actual behaviour
Intel microcode does not get loaded as testified by the following console error messages before initramfs gets loaded:
```
TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)
RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
```
These error messages disappear when loading an initramfs produced by dracut, as the intel-ucode package supports dracut already.
### Steps to reproduce
1. Install intel-ucode.
2. [Switch](https://docs.voidlinux.org/config/kernel.html#changing-the-default-initramfs-generator) from dracut to mkinitcpio
3. Reboot
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
@ 2024-01-10 9:31 ` dkwo
2024-01-10 12:08 ` basploeger
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dkwo @ 2024-01-10 9:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1884486750
Comment:
The arch page you link says
> However, Arch Linux defaults to using mkinitcpio to generate its initial ramdisk (initramfs), which does not support this.
but i agree it'd be nice to have a mechanism for other initrams to load microcode (e.g. booster, tinyramfs).
in the intel case, it could be stripped first (otherwise it's huge) and placed somewhere.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
2024-01-10 9:31 ` dkwo
@ 2024-01-10 12:08 ` basploeger
2024-01-10 14:24 ` classabbyamp
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: basploeger @ 2024-01-10 12:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
New comment by basploeger on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1884729338
Comment:
Right, mkinitcpio does not support loading microcode natively, unlike dracut. So we have to load microcode from the boot loader as explained further down on that page: generate /boot/intel-ucode.img and instruct the boot loader to load that image before loading the initramfs. For example, `grub-mkconfig` should auto-detect that image file and add it to the grub config.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
2024-01-10 9:31 ` dkwo
2024-01-10 12:08 ` basploeger
@ 2024-01-10 14:24 ` classabbyamp
2024-01-10 14:25 ` classabbyamp
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-01-10 14:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 220 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1884947646
Comment:
iirc you can also `cat` the two images into one combined ucode + initrd
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (2 preceding siblings ...)
2024-01-10 14:24 ` classabbyamp
@ 2024-01-10 14:25 ` classabbyamp
2024-01-10 16:25 ` dkwo
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-01-10 14:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1884947646
Comment:
iirc you can also `cat` the two images into one combined ucode + initrd image
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (3 preceding siblings ...)
2024-01-10 14:25 ` classabbyamp
@ 2024-01-10 16:25 ` dkwo
2024-01-10 16:38 ` classabbyamp
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dkwo @ 2024-01-10 16:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1885180971
Comment:
right, most bootloaders should support that, e.g. for efistub by append an initrd= option as `initrd=\ucode.img initrd=\initramfs-linux.img`
this tool https://github.com/anatol/ucode-image-gen seems capable of generating host specific images.
then one could edit our efibootmgr hook i guess?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (4 preceding siblings ...)
2024-01-10 16:25 ` dkwo
@ 2024-01-10 16:38 ` classabbyamp
2024-01-10 17:52 ` dkwo
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-01-10 16:38 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1885204741
Comment:
if you're using ukis and efibootmgr, microcode is already supported by mkinitcpio
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (5 preceding siblings ...)
2024-01-10 16:38 ` classabbyamp
@ 2024-01-10 17:52 ` dkwo
2024-01-10 18:00 ` dkwo
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dkwo @ 2024-01-10 17:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 234 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1885341701
Comment:
on a side note, should our intel-ucode pkg do the same as arch or alpine do with iucode_tool?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (6 preceding siblings ...)
2024-01-10 17:52 ` dkwo
@ 2024-01-10 18:00 ` dkwo
2024-01-16 17:06 ` classabbyamp
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dkwo @ 2024-01-10 18:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1885353142
Comment:
maybe something like https://github.com/jirutka/efi-mkuki could be used, if one wants smth initram-agnostic.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (7 preceding siblings ...)
2024-01-10 18:00 ` dkwo
@ 2024-01-16 17:06 ` classabbyamp
2024-02-05 21:05 ` classabbyamp
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-01-16 17:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1894158557
Comment:
a solution is in progress in concert with upstream: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/merge_requests/291
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (8 preceding siblings ...)
2024-01-16 17:06 ` classabbyamp
@ 2024-02-05 21:05 ` classabbyamp
2024-03-16 16:47 ` classabbyamp
2024-03-16 16:47 ` [ISSUE] [CLOSED] " classabbyamp
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-02-05 21:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-1928092604
Comment:
microcode support has now been added on mkinitcpio's master branch and will be released with version 38 probably sometime this month.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (9 preceding siblings ...)
2024-02-05 21:05 ` classabbyamp
@ 2024-03-16 16:47 ` classabbyamp
2024-03-16 16:47 ` [ISSUE] [CLOSED] " classabbyamp
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-03-16 16:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48145#issuecomment-2002043065
Comment:
as of mkinitcpio 38, the microcode hook has been released. install the relevant microcode package (`intel-ucode` or `linux-firmware-amd`) and add `microcode` to the `HOOKS` array in `/etc/mkinitcpio.conf`. if the hook is placed after `autodetect`, only microcode for the your host cpu will be added.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [ISSUE] [CLOSED] Support intel-ucode when using mkinitcpio
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
` (10 preceding siblings ...)
2024-03-16 16:47 ` classabbyamp
@ 2024-03-16 16:47 ` classabbyamp
11 siblings, 0 replies; 13+ messages in thread
From: classabbyamp @ 2024-03-16 16:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
Closed issue by basploeger on void-packages repository
https://github.com/void-linux/void-packages/issues/48145
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.10_1 x86_64 GenuineIntel uptodate rrrmFFFFFF
### Package(s) Affected
intel-ucode-20231114_1, mkinitcpio-37_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No. But [this information](https://wiki.archlinux.org/title/microcode#Initrd_images) from Arch Linux is useful for reference.
Arch's intel-ucode package generates the necessary `/boot/intel-ucode.img` [here](https://gitlab.archlinux.org/archlinux/packaging/packages/intel-ucode/-/blob/main/PKGBUILD?ref_type=heads#L22).
### Expected behaviour
Intel microcode gets loaded in early boot before loading the initramfs produced by mkinitcpio.
### Actual behaviour
Intel microcode does not get loaded as testified by the following console error messages before initramfs gets loaded:
```
TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)
RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
```
These error messages disappear when loading an initramfs produced by dracut, as the intel-ucode package supports dracut already.
### Steps to reproduce
1. Install intel-ucode.
2. [Switch](https://docs.voidlinux.org/config/kernel.html#changing-the-default-initramfs-generator) from dracut to mkinitcpio
3. Reboot
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2024-03-16 16:47 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-09 22:53 [ISSUE] Support intel-ucode when using mkinitcpio basploeger
2024-01-10 9:31 ` dkwo
2024-01-10 12:08 ` basploeger
2024-01-10 14:24 ` classabbyamp
2024-01-10 14:25 ` classabbyamp
2024-01-10 16:25 ` dkwo
2024-01-10 16:38 ` classabbyamp
2024-01-10 17:52 ` dkwo
2024-01-10 18:00 ` dkwo
2024-01-16 17:06 ` classabbyamp
2024-02-05 21:05 ` classabbyamp
2024-03-16 16:47 ` classabbyamp
2024-03-16 16:47 ` [ISSUE] [CLOSED] " classabbyamp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).