RFE: systemd-boot should say "Default boot entry is not working" or similar
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
Submission type
- Request for enhancement (RFE)
systemd version the issue has been seen with
systemd 231 and earlier
Used distribution
Arch Linux (currently in use)
Fedora (has conf files, not installed)
Gentoo (removed conf files)
In case of bug report: Expected behaviour you didn't see
More verbose error screen, especially when timeout is very low, saying something along the lines "Default boot entry not working"
In case of bug report: Unexpected behaviour you saw
systemd-boot was throwing an error about a file not being in EFI dir (\EFI\shellx64_v2.efi in my case) when it was, in fact, in that location.
In case of bug report: Steps to reproduce the problem
Can probably reproduce by having an invalid efi file at the same location (most likely same effect)
- On EFI capable computer (one that CANNOT run shellx64_v2),
- Add uefi-shell-v2-x86_64.conf.txt inside /loader/entries folder (without .txt extension)
- Add uefi v2 shell in proper location
- Reboot
Side note: I don't know why it was always trying to boot the shell first (during troubleshooting, I removed the file and a different error came up, related to an OS I had removed, which is how I resolved the issue). It is possible that it defaulted to the shell after I removed a different conf file awhile back.
Additional information:
$ ls /boot/efi
c69ea34dbc144cd0b964c740ee7bf87c keys mach_kernel shellx64_v2.efi
EFI loader shellx64.efi System$ ls /boot/efi/EFI
arch Boot Microsoft refind shellx64_v1.efi shellx64_v2.efi systemd tools$ ls /boot/efi/loader/entries
arch.conf fedora.conf
arch-fallback.conf keytool.conf
arch-grub.conf uefi-shell-v1-x86_64.conf
c69ea34dbc144cd0b964c740ee7bf87c-4.7.6-1-ARCH.conf uefi-shell-v2-x86_64.conf
c69ea34dbc144cd0b964c740ee7bf87c-4.7.6-ARCH.conf
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the systemd-boot behavior around /loader/entries and EFI paths, using the supplied uefi-shell-v2-x86_64.conf reproduction setup on an EFI-capable system. Trace the error shown when the selected entry cannot boot and determine how the default-entry failure should be reported; done means the screen clearly identifies that the default boot entry is not working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100