Solus won't boot to greeter / login screen after installing updates

leifb

That's strange. Installing the new kernel works without any errors. But when rebooting uname -r still gives me 5.6.4-152. In grub i can only choose between Solus-current-5.5.11.151 and Solus-current-5.6.4-152.

Girtablulu

leifb ERM okay OK maybe @DataDrake knows something more, if you really installing 5.6.18 but it doesn't get mentioned inside grub I dont know what's going on

leifb

And when running sudo eopkg it --reinstall linux-current it says it's installing 5.6.18.

leifb

Girtablulu Okay, still thanks for helping me so far!

Harvey

Are you dual booting? My assumption is your using Windows default EFI partition which is tiny and it has run out of space. I thought this would produce an error but maybe not.

Please post the output of lsblk

leifb

Harvey That sounds very likely.

Here is the output of lsblk

leifb

Might be relevant:

A while ago (maybe two to three months) I had problems with dual booting to windows. After some time I settled on just not using windows anymore and 'merged' my windows and linux partitions. During that time I also did some stuff to my grub / boot partitions. I don't know exactly anymore, what I did, as booting Solus worked just fine. There might be something wrong here. Maybe there is another 'grub' somethere, that gets updated.

leifb

In my motherboards boot menu the entry that boots to grub is called UEFI OS (SATA6G_1: Samsung SSD 850 EVO 500GB)

Harvey

leifb
Yeah so its a UEFI install which means its not grub, it is using systemd boot.

I guess the merging you've done also explains the weird sda2,5,6 (missing numbers). My theory now falls to Solus trying to install the kernel to a dev ID that no longer exists. sda1.

At which point IF I am correct. I would backup and reinstall because I'm not sure how to fix that. Maybe someone else can help but yeah at this point, looks like a nightmare to me 😛

Sorry.

leifb

Harvey I had the feeling that it would come back to me when I moved the partitions back then. Maybe I will have to take some time for a reinstall this weekend. Anyway, thanks for your input!

Girtablulu I have no idea what the consequences could be, but as my install is messed up anyway it might be worth a shot.

GueGuerreiro

Seems similar to my issue here: https://discuss.getsol.us/d/4942-can-t-boot-into-latest-kernel

Girtablulu

you could try renaming SDA2 to SDA1, but i never tried this

Quade

Hey all, I ended up rolling back to a previous update and my Solus is back to a working state. That's one alternative, if you don't have the time to do backups and reinstall at this time.

https://getsol.us/articles/package-management/history-and-rollback/en/

I might as well leave my system like that for now, until I find some time to play around and try upgrading again.

Cheers! 🙂

tadcan

Have the same issue as well with a 750ti. Ran sudo eopkg up and checked for broken packages. Also tried rollback to previous up date which didn't work either. Running sudo eopkg remove nvidia-glx-driver-common worked to bring back to a working login screen. This PC also duel-boots with windows and uses uefi.

Then I checked uname -r and it was back on the lts kernel. So I reinstalled the nvidia drivers, pressed esc on boot and picked the last kernel which worked, which makes it the same solution to last breakage. Updated the clear boot manager, but the change didn't stick after reboot.

« Previous Page