From: basploeger <basploeger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Support intel-ucode when using mkinitcpio
Date: Tue, 09 Jan 2024 23:53:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48145@inbox.vuxu.org> (raw)
[-- 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
next reply other threads:[~2024-01-09 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 22:53 basploeger [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48145@inbox.vuxu.org \
--to=basploeger@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).