When I set up Grub with dual-boot, I already had the issue of booting to a terminal instead of the selection of OS, but I brushed it off, since I could just type “exit” (sometimes I’d have to type it again in another Grub terminal that appeared shortly after) and it would show me the OS selections.

However, ever since I updated my computer to a new version of popOS, typing “exit” just puts me in a black screen. I tried running a grub fixer app, and resetting my grub configurations, but the issue is still there.

For now, I have to type a bunch of commands in order to boot my computer, which isn’t that bad, but the problem is that I’m not the only one using it, so I was wondering if anyone went through something similar and/or has a fix for this issue.

  • retrogirl@lemmings.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    Yes it does by default. Systemd boot meets Freedesktop standards for a bootloader in use with systemd. GRUB does not. It’s an old, bloated, unsecure chainloader that System76 bypassed almost a decade ago. The only reason to use GRUB is familiarity, which is a piss poor reason. Systemd boot is lightweight and modern and much better than GRUB. Using Kernelstub gives you the control that GRUB has without the bloat.