-
Notifications
You must be signed in to change notification settings - Fork 396
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
dracut 059 produces broken unified kernel images with systemd 254 #2431
Comments
Same issue. Bisected to systemd/systemd@dfca558. |
Thanks for your feedback. If it's already fixed on the master branch, there is no need to keep this issue open. |
@aafeijoo-suse Do you plan to release dracut 060 before systemd 254 hits the repos (an thus breaking dracut uki setups)? |
The main purpose of the issue tracker is to reflect current upstream issues, when it's fixed, it's closed. It has nothing to do with the release process. |
Alternatively, you can pin the issue. Because this is fairly important information + to avoid duplicates when 254 will land. |
I've just got my system borked. Wasted 2 hours before I stumbled into this issue and rolled back systemd to 253. Updating arch right now means borked system for anybody using systemd + dracut + UKI |
Unless you use |
@Mithras I got into the same problem. Make sure you're not on dracut 059-2. Because the problem is gone when I upgraded dracut to 059-3. |
Oh, 059-3? Guess they pulled in another commit that hasn't made it to a release. |
@kode54 I released the new pkg after seeing the first complains today. I hope we'll see a release soon. |
Can confirm that 59-3 works with systemd 254. Thank you! |
systemd 254 changed the efistub, the hardcoded offsets are wrong with the new efistub. See: dracutdevs/dracut#2431 systemd/systemd@0fa2cac#commitcomment-76747223
systemd 254 changed the efistub, the hardcoded offsets are wrong with the new efistub. See: dracutdevs/dracut#2431 systemd/systemd@0fa2cac#commitcomment-76747223
systemd 254 changed the efistub, the hardcoded offsets are wrong with the new efistub. See: dracutdevs/dracut#2431 systemd/systemd@0fa2cac#commitcomment-76747223
@aafeijoo-suse Any chance a new version of dracut could be released with the fix for this issue included? |
Fixed version was released a few hours after the bug hit arch repos |
No, not everybody uses Arch. There is no new official dracut release. |
Sorry, that doesn't depend on me. |
I would encourage downstream Linux distributions to consider making downstream releases from git commits. If you'd like to see a version bump and release notes in a git commit, please take a look at #2509. Github allows to download a tarball from any commit {sha} with the following link Currently only Github project admins can tag git commits in this project. The current project admins are documented in the wiki - https://github.com/dracutdevs/dracut/wiki/Dracut-development |
Describe the bug
I am testing systemd v254-rc2 now and dracut generates broken unified kernel images (
--uefi
) with it.Distribution used
Arch Linux, testing repo
Dracut version
059
Init system
systemd
To Reproduce
No extra configuration. Prints such messages during build:
Dracut itself does not recognize it as an error and produces an image successfully:
But systemd-boot fails to load the image:
Expected behavior
Produced images should work.
Additional context
I suspect systemd/systemd@dfca558 is the cause. But not sure.
The text was updated successfully, but these errors were encountered: