Systemd-boot missing in boot menu

Thank you, I successfully updated my UEFI.

2 Likes

off topic: does anyone know why Debian as opposed to other Linux always manages to stay bootable in BIOS? Thanks.

would be interesting if they have something implemented that does this indeed.
But what i do always is to create a new efi partition aside from the windows one if i create dualboots.

Issues can be different things also… as i see the case that the boot entry in the ā€œBiosā€ is removed this is an entry written into the motherboards nvram not on the boot partition.

In this case you can simply recreate the entry from booting and chrooting on a live ISO bootctl install --efi-boot-option-description="YourFancyName"
The second case is that a windows update is recreating the efi partition and with this removing kernel images and boot files completely… recreating will work too, you can use this as a guide: [Tutorial] Convert to systemd-boot

Basically you need to reinstall bootloader (systemd-boot) and recreate the kernel images plus generating the needed systemd-boot entries

1 Like

I see. If two efi boot partitions exist, one needs to tell each OS which one to use (how?) and must not forget. I seem to remember why some years ago, I did away with it. Debian as a 3rd OS on all may has since then enabled me to reinstall refind and get into EnOS. The good thing is, that I do not need to remember any commands.

I’ve just installed a new SSD to my Computer.

However, I’m unable to install EOS on it, because it fails with the partitions: https://termbin.com/7cyr

Different error I get sometimes: https://termbin.com/48a4

Does anyone has an Idea why it fails with partitioning or installing the packages?

And again… Installed EOS, ran EOS-Update, rebooted and screen stays black.

Log shows ā€œerror while waiting for gpu progressā€

So my question is when you installed and booted into endeavouros did it load properly before running an update?

What do you mean by properly?

Also I saw on reddit some people have the exact same issue with newest NVIDIA driver and multiple monitors.

I’m asking if after installing and booting into EOS it loaded to the desktop before you updated. The reason I’m asking is because when you do an install it’s always right up to date.

So I’m not understanding you saying Installed EOS, ran EOS-Update rebooted and screen is black. It would have already been up to date when installed so when you install it and boot into it is the screen black after logging in or before? You shouldn’t be needing to run EOS Update after installing it.

1 Like

You might need to run an update if you did an offline install.

You are right there. I wasn’t even considering that. Didn’t even cross my mind. :grin:

Yeah, if I’m offered the choice of an online install, I always take it. Then I have a good Internet connection and not everybody does.

I did an offline installation because pacman always failed during the online installation.

EOS was working probably.

You would have to look at the pacman log in /var/log/pacman.log and scroll to the bottom and then scroll up to where you did the updates after the install to see what was updated. I’m sure it’s quite a lot and would be somewhat difficult to determine which update is the issue. It would be a lot of guessing.

Like I said, there was a bug with the NVIDIA drivers.

NVIDIA driver version 570.133.07-1 is available since today and fixed the black screen issue.

After installing a second drive to my computer, I’m now running EOS and Windows 11 on two sperate drives with separate EFI partitions.

I’ve also checked previous linked guides for some tips and avoiding issues.

That being said, I’ll mark this thread as resolved for now.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.