Linux boot settings fail to appear during PC startup.
Linux boot settings fail to appear during PC startup.
Pop_OS relies on systemd-boot and integrates its boot setup with the custom upgrade procedure. Modifying this setup could affect your OS installation during future upgrades, which is risky. This approach also contradicts two key points: first, you can run GRUB with EFI partitions wherever you prefer—this is supported by systems that use GRUB and have ESP mounted on /boot/efi. Second, the standard practice for Debian is to mount the ESP to /boot/efi, as outlined in relevant documentation. Changing the mount point to /boot can cause issues because the bootloader may depend on files in /boot that are essential for startup. Be cautious; altering these defaults might lead to unexpected behavior or an unbootable system for others.
Sure, I just verified this on a standard Ubuntu 21.10 setup with an EFI SSD. The bootloader is GRUB and the ESP is located at /boot/efi. This applies to Ubuntu as well. Once your system starts up, I can guide you through checking if it uses GRUB or systemd-boot.
Linux is designed to be both attractive and challenging at the same time. The changes you made work well enough for me to start up without issues, but the complexity remains. It’s a balance between usability and depth that many users find appealing yet confusing.
I noticed no text following the posted image. It seems the file Ubuntu used for a boot splash was hidden, which likely caused the display of the message and the generic picture. That clears things up! I’ll take a few minutes to review and prepare notes for you.