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#79115 - [dracut] systemd 254rc2 breaks efi stub booting with dracut
Attached to Project:
Arch Linux
Opened by freswa (frederik) - Sunday, 16 July 2023, 09:35 GMT
Last edited by freswa (frederik) - Wednesday, 02 August 2023, 06:53 GMT
Opened by freswa (frederik) - Sunday, 16 July 2023, 09:35 GMT
Last edited by freswa (frederik) - Wednesday, 02 August 2023, 06:53 GMT
|
DetailsDescription:
254rc2 breaks efi stub generation. The generated efi binaries aren't bootable at all (don't get executed by efi). Additional info: * package version(s) 254rc2 * config and/or log files etc. On generation dracut gives these non fatal errors: objcopy: /var/tmp/dracut.ku25Sp/uefi/linux.efi:.osrel: section below image base objcopy: /var/tmp/dracut.ku25Sp/uefi/linux.efi:.cmdline: section below image base objcopy: /var/tmp/dracut.ku25Sp/uefi/linux.efi:.splash: section below image base objcopy: /var/tmp/dracut.ku25Sp/uefi/linux.efi:.linux: section below image base objcopy: /var/tmp/dracut.ku25Sp/uefi/linux.efi:.initrd: section below image base * link to upstream bug report, if any https://github.com/dracutdevs/dracut/issues/2431 Steps to reproduce: Take 254rc2 and generate an efi stub with dracut. Optionally: Try to boot it. |
This task depends upon
Closed by freswa (frederik)
Wednesday, 02 August 2023, 06:53 GMT
Reason for closing: Fixed
Additional comments about closing: dracut-059-3
Wednesday, 02 August 2023, 06:53 GMT
Reason for closing: Fixed
Additional comments about closing: dracut-059-3
Thanks a lot @loqs!