Sorry if this sounds a bit silly!
I just converted (again) to systemd-boot (BTRFS, BTRFS-Assistant, Snapper… installed - Had a few system snapshots and /home as well)
I followed instructions I did before and now I can boot to LTS thanks to @dalto and his instructions.
Now, when I start BTRFS-Assistant I can only see my /home snapshots, no profile for system or even eariler system snapshots!
Is this OK?
How can I get back system snapshots and snapshot as I did before under BTRFS (if possible under systemd-boot)?
Just in case so I can live boot, install BTRFS-Assistant, restore a previous snapshot, then reboot. (This is the right way to recover?)
Your kind assistance as usual highly appreciated.
Thank you.
Glad I stumbled upon this tutorial because I could not get GRUB to go past the 452 pointer error no matter what. With my determination to not have to rebuild my PC, I went on the systemd-boot path and I’m grateful for this.
OK @dalto, thanks a lot.
I thought it is somehow related to systemd-boot as nothing has changed other than changing the bootloader.
Will make a separate thread.
I use envycontrol, ( GitHub ) which is similar to optimus-manager but far simpler by design and I encountered zero issues so far in my week or two so far of using systemd-boot
I see. So it is better for Legacy booting as you mentioned.
So can I say for UEFI it is for sure Grub, then systemd-boot (I would not mention rEFInd as I personally found it a bit hard for me to get it up and running. It’s me not rEFInd to be honest and fair)
Asus Tuf A15 2021 version here. AMD Ryzen 7 5800H-Nvidia GA106M (RTX-3060) and also using envycontrol.
Before the grub issues happened I used grub also without issues with the Nvidia card and with envycontrol, after changing to systemd-boot something must have changed as now when i change to nvidia the laptop boots to a black screen only.
Using a tty seems to light up the backlight and then i can do envycontrol -s hybrid, a reboot after this command boots back into the xfce desktop.
kernel cmd line has been adjusted with the same options as with grub before, been pulling out my hairs to find why this is happening but no luck yet. Hopefully someone could shed a light on this,
yes i reinstalled EOS and then converted to systemd-boot because when i did the procedure on my working system the laptop didn’t boot anymore and couldn’t be accessed.
Black screen with white blinking cursor after reboot
Note : This only applies if you’re using Xorg. If this issue with Wayland, open a new issue.
This is mostly caused when switching to nvidia mode due to a file generated by Xorg or a command which you might have ran to generate this(such as nvidia-xconfig). This isn’t caused by the file itself but due to the contents of the file pointing to wrong screen ids, which causes xorg to start incorrecly. This is fixed by removing the file /etc/X11/xorg.conf.
If the above solution doesn’t fix the problem, you can try to find its root by :
Editing the grub entry by pressing ‘e’ on the kernel entry.
Removing ‘quiet splash’ and replacing it with ‘text’.
Reboot. There should be debug messages visible on the screen, from there you should be able to solve the problem by either doing it yourself or opening a new issue with the output attached.
If that doesn’t work or you don’t even have that file on your system, I would consider filing a bug report with the envycontrol dev(s), they are active. If that were my system, I only use the nvidia option, so if I was unable to get that to work successfully, I’d just go back to grub personally. systemd-boot is nice and all, but if it gets in the way of my nvidia use I’d think it might just be more trouble than it’s worth. nvidia already makes me pull my hair out enough, I don’t need any other packages adding to that
@MrToddarama honestly using grub is probably the best option still for most users. Any search or wiki reading you’ll do will have grub as the de facto option. systemd-boot may be simpler code, but from a user experience, grub is “easier” to configure since it’s been around so much longer and I’ve already got experience with it. I like trying and testing shiny new things, so that was partially why I made the switch, but if you have no real preference, grub is still a great choice.
I tried also optimus and got the same result as with envycontrol, but ok i’ll try of course this also. Still doesn’t explain why the same settings worked with grub and not with systemd-boot.
Because more than the bootloader changed. Any other changes you made in prior install are now gone. Also, anything that changed on the ISO between your original install and the new install would also be different.
I’m messing around with rEFInd now, it’s actually pretty easy to get working…but working WELL is another story, I’m not a fan of it’s defaults, particularly the way it folds all the Arch/Endeavour kernels into one boot entry initially, took me a while to figure out my Zen kernel was hiding under the F2 menu.
