No grub menu at start

I installed a fresh version of endeavors yesterday and have been trying to get to the grub menu but just can’t. instead, I see only these three options in the image. Any help?

These are lines from config;


That looks like a systemd-boot menu.

EnOS’ installer defaults to systemd-boot.

However, there is an option to choose Grub in the installer.

Since this is a fresh install, if you prefer Grub, you might want to reinstall and choose Grub in the installer.

1 Like

Thanks! Really appreciate the help <3

Well, I can do that but is there any way to fix this without reinstalling the whole system?

You could in principle convert it to Grub but it is a bit involved. You would need to use your live usb, chroot into the system and make some changes. I’m afraid I couldn’t help you out with that.

Much easier and faster to reinstall since it is still a new system. But that is your choice.

If you prefer to convert, please wait for other forum members with experience of such procedure to come along.

Uggh Guess I’ll just reinstall everything then. Thanks!

First of all, welcome to the wonderful world of EndeavourOS.

May I ask why do you need Grub in particular?
I would suggest you search the forum here and read about Grub and decide.

Nothing in particular actually. I’m just familiar with it and know that it has lots of themes and all :slight_smile:

What are the pros of using systemd-boot over grub?

systemd-boot is simpler and (presumably) less prone to breakage / reliant on manual intervention after updates.

EnOS switched to systemd-boot after Full transparency on the GRUB issue - Updated 2022-08-29 ; see also Latest grub bricked my system (grub_is_shim_lock_enabled not found)


Theres good post about systemd-boot vs grub here on forums which goes over pro’s and con’s;
Grub or Systemd-boot?

From my experience, systemd-boot Just works. It’s more robust and simpler.

Grub is more configurable, but also is more complex and can go borked easier over multiple things. And then there was that grub update thingie that broke booting for many and forced to fix it with chrooting.

1 Like

I think you’ve linked wrong post :laughing:

They probably meant to link to Dalto’s post, I imagine:


Whoopsie :smile: Fix’d.

So, nothing serious actually. Just cosmetic.

Well, I do not want to be pro or con anything, but I will tell you my experience. (you can verify and search the forum)

  • Grub “sometimes” need that if there is an update to Grub, that you install it again, though it is there already. The problem is if you did not review and watch carefully and miss it you might end with an unbootable system.
  • Though I have to admit, If you are using BTRFS file system, Snapper,… etc, having Grub allows you to boot to an earlier snapshot that is working. (I used to break my system with my own hands while playing with EndeavourOS, but no more)

In regards to systemd-boot:

  • it is much simpler in design, very stable and reliable, absolutely nothing to worry about.
  • it boots much faster.
  • you just update and don’t care.

If I am on Grub and was not focusing 150% on the updates, tired. sleepy, distracted… I might end with an unbootable system, so why take the risk of me not paying attention! Any human can do this.

Well, I personally trust the Endeavour Developers (On Linux since 2000, on EndeavourOS for a full year now.), so out of my trust in them if they chose systemd-boot to be the default then it is the best option! As simple as that.

Simply, with systemd-boot, simply your system works, boots, updates, no hassles

In addition to distrohopping till I settled on EndeavourOs, I did a lot of bootloader hopping several times between both on EndeavourOS till I found systemd-boot is the most convenient for me for having a boot loader that just works. I don’t really need to boot to earlier versions of system, though as far as I know even with systemd-boot there is some way(s) to make you boot to a previous snapshot.

Putting myself in your shoes and given you have no specific practical need for Grub, I would stick to systemd-boot.
I would like to quote:


But it is up to you. Linux is about freedom.

Maybe someone more expert than me can give us perhaps in a separate thread some clues on how to “decorate” systemd-boot, have a background… etc.

1 Like

Thanks for the detailed explanation! Really appreciate it.
I did not pay attention to the boot speed when I switched to grub so I can’t say much. But all I need is a menu to boot into the different installed systems and it’s a plus if systemd-boot is faster!!
It also seems like a better option too.
Maybe if I reinstall eos at some point, I’ll give it a try!

Thanks for nothing.
Everybody here tries to help everybody.

Honestly I do not know if systemd-boot can boot multiple OS and/or Windoze, I haven’t tried.
As I said I was on Linux since 2000 (dual booting with Windoze), but since end of 2003 I am on Linux only and one OS only (there was no systemd-boot at that time)

But as far as I read and learned here you have to have enough space for EACH OS on systemd-boot. Some other posts may help. (sorry I am not that techie)

I am sure you will enjoy EndeavourOS and enjoy the community here. The best ever experience I had since I started Linux till now.

1 Like

The speed being “much faster” is quite subjective.

As bootloader systemd-boot may be a bit faster. However the loading of the bootloader is a “tiny” part of the boot process. So at the end the boot speed gained is probably not perceptible.

For more on the boot process:

1 Like

I don’t use it, but from reading on it, it does support that; it should probably even autodetect windows.

1 Like

Wise man!
I have been now 20 years windoze free (other than at office, it is up to them anyway!), but now I have no “office” as I am retired happly!
So I am 110% windoze free!

Sorry for missing something I should have mentioned, I just remembered just a few minutes ago. (because I just installed the latest EndeavourOS on a very old machine, more than 10 years old, and did not have the luxury of having systemd-boot, only Grub, so this is how I remembered)

Some time ago, with the help of our friends and experts here I could create a “hook”, a little script that runs automatically if a certain condition occurs. That hook automatically installs Grub in case it needs to be installed, so you do not have to worry about Grub breaking. I tested it and lived with it for some time and it was OK, it removed the hassles I mentioned previously. you may check my thread and the hook at Grub Hook to grub-install and grub-mkconfig?

I hope this helps.

But still, I (as my own personal thinking) I did not like the idea of a software change that may lead to an ubootable system or require such attention from the user. I just thought how would I be sure that nothing similar will happen again in the future so that the hook might not work! I don’t mind a bug or whatever breaking with any app, but when it comes to data loss or unbootable system I am very very careful. Whatever software breaks I can simply reinstall it or even installan alternative easily, just really easy, but when it comes to these two, I can’t take it.

So, this is why I am sticking to systemd-boot.

Alas, “it” in my sentence referred to systemd-boot, not Windows.

(Sadly I have a dual boot to Win, for those rare times when a game does not run properly under Proton. )