"Jonathan Billings" wrote:
I suspect I know why this happened.
Do you have the "sdubby" or "systemd-boot-unsigned" package installed (which brings in sdubby)?
The sdubby package installs an /etc/kernel/install.conf that tells the kernel-install script that runs in the kernel-core %post to install kernels and initrds in /boot/efi/$MACHINE_ID/. (Where $MACHINE_ID is from the contents of /etc/machine-id).
This is something that systemd-boot uses, and I'm not sure why it happens, but some dependency seems to pull that package in for some people.
Backing it out simply means you need to uninstall the sdubby package and re-run the kernel-install command, or more simply, reinstall the kernel-core package. Once that's done, it will do the normal GRUB2 boot method of putting filesinto /boot/ and blscfg entries in /boot/loader/entries/.
That worked! Thanks!
Now I'll try to go back through my logs and try to see when sdubby got installed and why.