Arch Linux User Repository

You should remove 'uefi=yes' from dracut.conf. This option make dracut generate UKIs on its own and it conflicts with dracut-ukify which uses ukify for that.

jcruz, you're not the only one I too was having this issue https://bbs.archlinux.org/viewtopic.php?id=292326 and have not been able to successfully build a UKI with dracut-ukify.

I made habit of making sure to do it with dracut directly after a kernel update to avoid it. Would be nice if this could be fixed, or we could know what we're doing wrong.

Hi,

I'm testing this on a VM and installed a fresh arch. My setup includes LUKS & LVM and 3 kernels: linux, linux-zen & linux-lts. I have a custom /etc/dracut.conf.d/custom.conf with the following:

compress="gzip"
install_items+=" /etc/crypttab "
hostonly="yes"
uefi="yes"

From arch-chroot, when I run dracut --regenerate-all -f it generates the efi files and it works just fine after reboot. I'm using systemd-boot.

In the etc/dracut-ukify.conf I changed the default kernel to be linux-zen and uncommented the ukify_variants. I also removed the hostonly flag from the custom.conf above.

If I then run dracut-ukify -a to regenerate the efi and reboot I get an error about a magic number and can't decompress a file and it won't boot. I have to boot from the installation ISO and regenerate with pure dracut.

I know dracut works, so I'm not sure why this script does something that breaks it.

@android_aur sure, added in 9-3, thanks for suggestion!

Awesome package! Thanks.

Would it be possible to add Target = usr/lib/firmware/* as an install [Trigger]? So that my UKI gets rebuild on linux-firmware package updates? The script I was previously using had this in it's install.hook.

@Prototik THX!

I ment a note along the lines of that dracut-ukify will use flags from /etc/dracut.conf.d/* and that ukify_variants=() is just for flag overrides in different variants.

Since at least to me it was not clear if I had to manually copy the contents of /etc/dracut.conf.d/* into

ukify_variants=(
  [default]="mycopyiedflags"
)

or not.

@aur_person23

Also a small note that dracut-ukify does not(?) take existing kernel parameters from /etc/kernel/cmdline?

It's kinda systemd' kernel-install specific, but I don't see a reason why we can not use it too, so dracut-ukify 9-1 now using it if nothing provided via dracut-ukify.conf. Moreover, it will search for /etc/kernel/cmdline, /usr/lib/kernel/cmdline and /proc/cmdline, and use first one found.

Would it be possible to add a short note/comment in dracut-ukify.conf to help other users?

What kind of note do you offer?

@Prototik Thank you for your help!

Would it be possible to add a short note/comment in dracut-ukify.conf to help other users?

Also a small note that dracut-ukify does not(?) take existing kernel parameters from /etc/kernel/cmdline?

I could only get dracut-ukify working after manually copying my kernel parameters to ukify_global_args+=(--cmdline "root=/dev/sda1 quiet")

(I just assumed that would look at /etc/kernel/cmdline because the project I was previous using - kernel-install-for-dracut [AUR] - did)

@aur_person23 sure, all available config files of dracut used in the initrd generation process for any variants, see man 5 dracut.conf for search paths.

But if you need to pass some flags only for some variants, you need to used ukify_variants as you stated.

Quick question:

Does dracut-ukify automatically take existing flags from e.g.: /etc/dracut.conf.d/myflags.conf?

Or are you supposed to move those flags into dracut-ukify.conf like so:

ukify_variants=(
  [default]="--omit_dracutmodules+=" network nfs cifs " --add_drivers+=" i915 ""

?