Crash after deep sleep, black screen on start

David26

pomon
I boot on 7.0.3-336), log in
and I have: folowing packages broken: linux-current reinstall the brocken packages yest/no

so what I do?
thanks

pomon

Yes/uninstall nvidia/reboot

David26

pomon
I do that, after restart on current kernel (7.0.3-336), I have again "failed to start lightdm.service".

pomon

I'm out of ideas. Since you can get to TTY, let's check what's wrong with lightdm:

systemctl status lightdm.service

Also check for errors in the log:

sudo journalctl -u lightdm.service -n 20 --no-pager

David26

pomon
I boot on current kernel (7.0.3-336),
and results are:

pomon

Run:

sudo usysconf run -f
sudo systemctl restart lightdm.service

If that doesn't help, show the output of:

ls -R /etc/X11
ls /etc/modprobe.d/
cat /proc/cmdline

Finally, just do this:

sudo eopkg up -y
sudo eopkg it nvidia-open-current nvidia-glx-driver-current nvidia-glx-driver-32bit
sudo reboot

David26

pomon
I boot on current kernel (7.0.3-336),
after sudo usysconf run -f sudo systemctl restart lightdm.serviceI have again "failed to start lightdm.service".

results for the 2nd list of commands:

results for final commands:

after booting on current kernel (7.0.3-336) : still "failed to start lightdm.service".

pomon

OK. You need to choose one, so try:

sudo eopkg install nvidia-open-current nvidia-glx-driver-32bit
sudo reboot

David26

pomon
I do that,
and reboot, still choosing current kernel (7.0.3-336)
but it's now black screen.

pomon

When you see the boot menu, select the kernel, press e to edit, remove nvidia-drm.modeset=1 from the command line, then press Enter to boot.
If the black screen persists, press Ctrl+Alt+F3 to access TTY and run: eopkg li | grep nvidia

David26

pomon
ok I do that, but when I go to boot after edit, I have black screen
and no access to TTY ("Ctrl+Alt+F3" or F2 do nothing).
(I have to got to sleep, be back tomorow)

Harvey

You have a GT 1030 so the nvidia-open* driver will not work for you.

The 580 driver is the latest driver that will support your card which is currently what our nvidia-glx-driver* packages are at.

So remove nvidia-470-glx-driver nvidia-470-glx-driver-common and install these again
sudo eopkg it nvidia-glx-driver-current nvidia-glx-driver-32bit

If you want to boot into the LTS kernel you will also need to install this too:
nvidia-glx-driver

Now you need to do the following:
echo "modprobe.blacklist=nouveau" | sudo tee /etc/kernel/cmdline.d/40-blacklist.conf

sudo clr-boot-manager update

Reboot and you should be able to login to a graphical session.

This will break again in future when Solus moves the nvidia-glx-driver* to a newer driver branch. At which point you will need to manually switch to a legacy driver branch for 580 which we currently do not have added.

David26

Harvey
ok thanks, I'm going to try that in the chroot/target from the live Solus.
Result, with conflicts:

root@solus / # sudo eopkg it nvidia-glx-driver-current nvidia-glx-driver-32bit
D-Bus call failed: [Errno 2] Aucun fichier ou dossier de ce nom
Les paquets suivants sont déjà installés et ne seront pas installés à nouveau :
nvidia-glx-driver-32bit
Taille totale du/des paquets(s) : 171.32 MB
Téléchargement 1 / 1
Paquet nvidia-glx-driver-current trouvé dans le dépôt Solus
nvidia-glx-driver-current-580.142-599-1-x86_64.eopkg [en cache]
Finished downloading packages.
Désactivation des interruptions clavier pour les opérations sur les fichiers.
Installation 1 / 1
nvidia-glx-driver-current-580.142-599-1-x86_64.eopkg [en cache]
Installation de nvidia-glx-driver-current, version 580.142, millésime 599
 [✓] Syncing filesystems                                                success
Programme terminé.
Conflit de fichiers :
/usr/lib64/kernel/initrd-com.solus-project.current.7.0.3-336.nvidia pour le paquet nvidia-open-current
/usr/lib64/modules/7.0.3-336.current/extra/drivers/video/nvidia-drm.ko.zst pour le paquet nvidia-open-current
/usr/lib64/modules/7.0.3-336.current/extra/drivers/video/nvidia-modeset.ko.zst pour le paquet nvidia-open-current
/usr/lib64/modules/7.0.3-336.current/extra/drivers/video/nvidia-peermem.ko.zst pour le paquet nvidia-open-current
/usr/lib64/modules/7.0.3-336.current/extra/drivers/video/nvidia-uvm.ko.zst pour le paquet nvidia-open-current
/usr/lib64/modules/7.0.3-336.current/extra/drivers/video/nvidia.ko.zst pour le paquet nvidia-open-current

Do I continue ? with
echo "modprobe.blacklist=nouveau" | sudo tee /etc/kernel/cmdline.d/40-blacklist.conf
sudo clr-boot-manager update

I run "echo "modprobe.blacklist=nouveau" | sudo tee /etc/kernel/cmdline.d/40-blacklist.conf"
but answer is:

tee: /etc/kernel/cmdline.d/40-blacklist.conf: Aucun fichier ou dossier de ce nom
modprobe.blacklist=nouveau

Harvey

As I said, nvidia-open* will not work with your card so if you have installed it, you will now need to remove it.

Since there has been a lot of installing of the wrong drivers run eopkg li | grep nvidia- and remove everything it shows so we can start fresh.

Then run:
sudo eopkg it nvidia-glx-driver-current nvidia-glx-driver-32bit

sudo mkdir -p /etc/kernel/cmdline.d/

echo "modprobe.blacklist=nouveau" | sudo tee /etc/kernel/cmdline.d/40-blacklist.conf

sudo clr-boot-manager update

Reboot.

To be clear you shouldn't need to be in a chroot that just makes it more complex. You can do this from the TTY like you were before 99.99% of times even if you boot to a blank screen you can switch to a TTY by pressing ctrl+alt+F5 or most other function numbers.

David26

Harvey
Ok I start on LTS kernel (6.18.26-286) (because with current 7.0.3-336 I have black screen and impossible to go to TTY)
I run all the commands
I reboot on on LTS kernel (6.18.26-286) (witch was on 1st choice)
I have "failed to start to vboxdrv.service"
And after, just TTY with login prompt.

Harvey

David26

If you boot into that kernel you need to install nvidia-glx-driver too. Make sure you have done that and reboot.

If that does not resolve the issue then its not then the blank screen is not caused by the issue I thought and I have no idea whats gone wrong on your system.

David26

Harvey
Ok I do that.
I reboot, I had a very short message "failed ..." (but I don't see what)
And then the normal prompt, so I get back to my desk!! :-)
Thanks a lot all of you! It was hard job, but I learn about booting using TTY...

Now what I do please?
Do I run all the updates? No risks?
I see 11 updates, with 2 about nvidia:
org.freedesktop.Platform.GL.nvidia-580-126-18
org.freedesktop.Platform.GL32.nvidia-580-126-18
toward version 1.4
?

I have to stay on this LTS Kernel? The updates will replace this LTS by current?

Harvey

David26
org.freedesktop.Platform.GL.nvidia-580-126-18
org.freedesktop.Platform.GL32.nvidia-580-126-18

Those seem like flatpaks and yes you should update. This weeks sync will happen soon so there will be a lot more updates soon. After sync I would update fully, reboot and try the 7.0.5 kernel.

EDIT: Sync has happened

David26

Harvey
Thanks. I do the 11 updates.
And now I see 55 new updates.
With some about Nvidia graphic drivers.
I will do these 55 after a reboot.
Thanks again and good day.
We can say its solve now I think! :-)

« Previous Page