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

leifb

Hey guys,

I installed updates yesterday and now my system won't start properly. I am installing updates quite frequently, so it was probably caused by something in the update from yesterday (https://discuss.getsol.us/d/5036-solus-03-07-2020-sync-report).

The following lines are in my lightdm logs:

Process 1215 exited with return value 1
[...]
Seat seat0: Stopping; greeter display server failed to start

Process 1215 is the x server.

The Xorg.0.log tells me, that something is wrong with my nvidia drivers:

(EE) NIVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
    system's kernel log for additional error messages and
    consult the NVIDIA README for details.
[the same thing three more times]
(EE) No devices detected.

I don't know where to look for those logs. Does somebody know?

In the sync report somebody else had problems with nvidia. When I run eopkg li | grep 'nvidia- I get the following:

nvidia-390-glx-driver-modaliases
nvidia-glx-driver-32bit
nvidia-glx-driver-common
nvidia-glx-driver-current
nvidia-glx-driver-modaliases

I have an nvidia gtx 970, in case that helps.

I don't know where to go from here, so I would appreciate some help. Thanks for reading!

PS.: Is there a way to upload my logs from the terminal?

Girtablulu

leifb haste-it can be used for this

Quade

Hi, I also seem to be having this same issue with a GTX 1070 since yesterday's sync.

leifb

Girtablulu Great thanks!

Heres the Xorg.0.log and the lighdm.log

Girtablulu

leifb are you fully updated? after the first sync we pushed a sec one reg nvidia drivers and dmseg log we be handy as well

leifb

Girtablulu I saw your post in the other thread. I tried eopkg up this morning and just now. Got No packages to upgrade both times.

I also ran sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall and it reinstalled the package shadow. I'm not sure, whether this is related or not.

leifb

Here is the output when i run dmseg

Girtablulu

leifb what kernel version are you using? because there is a mismatch between kernel and nvidia driver

€: nvidia version as well

leifb

uname -r: 5.6.4-152

Nvidia driver version from Xorg.0.log: NVIDIA dlloader X Driver 440.100

Girtablulu

leifb that's the kernel from april, you need 5.6.18 can you run inside of your tty sudo eopkg it --reinstall linux-current ?

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