Systemd-boot missing in boot menu

After I noticed I have no signal and did the post, still didn’t work.

1 Like

Mainly just using the browser as described before. Nothing unusual or any installations.

Until September 2024.

Windows:
Just a Intel - Net driver update on February 21 and an update for Windows malicious software removal tool on February 14. All other updates were in January or earlier.

EndeavourOS:
If I don’t forget it, every day before shutting down.
Last update was the day before, February 27.
And today - as described in my previous post.

so you did and update shut it down then went into windows played games shut down then discovered there was an issue. Ok well maybe you can start by posting your pacman log for the last two updates and lets see what was updated that could have caused the initial issue.

Since you did and update before we were able to fix the issue we could have made it worse. I would first prepare a backup before moving on as you may need to reinstall. I suspect thought that the issue is

What helped me, when I first had dual boot Linux and Windows, was a second ESP.
The first ESP is for Windows … and the second (it could be at the end of the disk drive) for Linux.

The last year I switched to use rEFInd boot manager with option “start last boot entry”, so after a restart the last (same) OS comes up again.

And please don’t use hybrid or hibernation mode in both OS’!

Here’s my boot log, hardware information and pacman log.

You may find some useful info here:

Looks like a few people who do a dual boot have chimed in I would follow their advice on what steps best to take.

the boot log has nvidia errors at the end. I know @ricklinux uses nvidia maybe he can give some insight.

What do you mean by that and how do I do that?

what he means is having a separate boot partition for Windows. So you would have 2 boot partitions on the same drive. honestly I would recommend adding a new drive for a Linux system and leave the one for windows if you must dual boot.

Honestly when it comes to dual booting with Windows its not If you can its you really shouldn’t.

You can try to create a new /efi partition and then chroot into endeavour and install the boot loader to the new partition but you should back up all data before attempting to do this as this can and will remove data.

2 Likes

I know, it’s probably best to use an additional drive. But I’ve heard dual booting with windows can still make issues, even if they’re on different drives and I would like to avoid that issue in the future.

I still need Windows for specific cases, so its not an option to completely avoid Windows, even if I would like to do that.

And is it as simple to just move my current EOS installation to a new drive and reinstall systemd-boot or how would one do that?

True however with a separate drive the chances are slim to non existent. Depending on how you add a drive.

This certainly can be done however you may find it much easier to just do a new install. and then move your /home files over

If it were me I would get external drive. Install EndeavourOS install boot loader onto external drive (Choose Grub) and use the bios to boot to the new device (F? for boot menu at start) This would give Microsoft no access to the drive at all. (I would unplugg before logging into windows)

It’s not that much difficult.

First create an ESP on the new drive & copy the EndevourOS partition to it.
With most partition copy tools you’ll get a new (different) GUID for the eOS partition, so you have to chroot in from ISO (or use supergrubdisk) and change the /etc/fstab to the new GUID.

You have to mount the new ESP & install systemd-boot or grub on this ESP.
(Optional) Best practices: deconnect the Windows drive from motherbaord before installing bootloader to get sure you choose the right ESP.

(Optional) If that is done & running fine, you could think about using rEFInd for simple management of your boot loaders. It’s not a must for Linux, but likely good for using Windows (especially Updates).

@Niika

B550 AORUS ELITE AX V2/B550 BIOS FEc 09/20/2023

I noticed your Bios version is odd. I don’t see that version listed on the site and there are board revisions 1.0, 1.1, 1.2, 1.3, 1.4. and 1.5 so I’m not sure which Bios update is applicable for your Motherboard. It would seem though that there should be a newer version available.

Not sure this will help with your current issue but the updates are important for Ryzen Cpu. I use grub with nvidia and my card is only a GTX 1060 so it is not one of the newer Nvidia series RTX cards. This is on dual boot with Windows although i have EOS on a separate disc with it’s own /efi partition. I am running btrfs with snapshots and having no issues. I am using the latest nvidia drivers on current kernel and lts is also installed.

2 Likes

You mean updating the UEFI / Firmware?

NVIDIA drivers should be updated through eos-uodate, shouldn’t they?

I’m planning to get an additional drive to install EOS on it. Maybe I will install the bootloader on an external drive, as suggested by @thefrog, but is it really a good idea to use an external drive for that? Are there any downsides? And is there anything else I have to put in mind, or just install EOS on an additional drive and that’s it?

Yes

Personally I would use an new internal drive to install eos and also use a new /efi on eos on this drive.

1 Like

Thank you for your input!

I’m not sure about updating the UEFI to be honest, due to the risk that it can go wrong.
Why are UEFI updates important for the CPU? Never heard of that before.

Welcome to the forum @Niika :slight_smile:

Regarding systemd-boot, you can always try and “recreate” /efi partition as I did here: Dual Boot went south (no more eOS 😭), doesn’t seem to be the same cause, but the remedy might just work (like it did for someone else).
If you’re fine w/ rEFInd and it’s working, you could as well call it a day :stuck_out_tongue:

But I guess you should address your booting issue first, most probably Nvidia related looking at your logs:

kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm]

having a look here and there might help:

but, hey, idk ¯_ (ツ)_/¯

Cheers !

1 Like

Oh and yes, you should totally update your firmware! (which could mess up your dual boot too btw :rofl:)

BIOS or UEFI updates can often fix problems, add features, or both to the BIOS. BIOS update contains feature enhancements or changes that help keep the system software current and compatible with other computer modules (hardware, firmware, drivers, and software). BIOS update also provides security updates and increased stability

you most definitely should. And yes it’s just one more pain… (except for @ricklinux who’s always looking forward to a good old bios update to run!)

1 Like

Found this site to download the firmware.
How do I know if my motherboard is rev. 1.0, rev. 1.5, rev. 1.4, rev. 1.2/1.3 or rev. 1.1?

Maybe not the easiest, but definitely the safest, way is to physically check on your motherboard.

3 Likes