Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd-boot-manager: INITRD_ENTRIES not handled in script but very much needed #467

Closed
v1993 opened this issue Jan 1, 2025 · 3 comments · Fixed by #469
Closed

systemd-boot-manager: INITRD_ENTRIES not handled in script but very much needed #467

v1993 opened this issue Jan 1, 2025 · 3 comments · Fixed by #469
Assignees

Comments

@v1993
Copy link

v1993 commented Jan 1, 2025

This variable seems super useful for Booster users, as it does not support bundling microcode into initramfs images and devs explicitly suggest that the solution is to use your boot loader's functionality instead (in case of systemd-boot, add an initrd /cpuvendor-ucode.img entry before the main initrd entry); however, it's completely absent from the sdboot-manage script and thus does nothing. I had to manually tweak the script locally to insert the relevant line, but that's obviously a terrible idea in the long run.

I'm aware this does not affect the default installation, but since there's already support for non-mkinitcpio initramfs images with specific mention of Booster, it seems that properly supporting it is desirable - and being able to apply microcode updates is most definitely a part of that.

P.S.: https://github.com/CachyOS/systemd-boot-manager probably should be archived with a link here, as it seems that development moved to this repo.

@ventureoo ventureoo self-assigned this Jan 2, 2025
@ventureoo
Copy link
Member

Are there any other use cases for such option besides microcode?

@ventureoo
Copy link
Member

Is #469 working fine for you?

@v1993
Copy link
Author

v1993 commented Jan 2, 2025

Yep, just tested and it works great! As far as I'm aware, microcode updates are the only common use of this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants