You are not logged in.
Pages: 1
I am not sure if there is a simple answer to this but I thought it was fixed by added the systemd bypass file.
Today however the crash occurs and on reboot the error was userlogin, dbus, and others could not start. So I had to chroot in to reinstall the files and clear the errors.
I am back up and running but it is annoyingly common.
This is the journal http://0x0.st/Xm1J.txt
I now have a play drive installed, so I reboot to other OS, chroot in and fix, I know the commands off by heart now which in itself is worrying.
Thanks for any advice.
I was going to install Lutris for something to do, instead I spent the morning fixing this :-/
This is the journal after the crash, if that helps? http://0x0.st/Xm1w.txt
Last edited by SimonJ (2024-06-27 11:14:30)
Rlu: 222126
Offline
There are numerous threads on this already, there seems to be an interaction bug between the nvidia 550 series of drivers and systemd when systemd gets updated which can lead to corrupted kernel memory and thus a full on kernel panic. If your GPU is Turing+ you could try to go with nvidia-open which shouldn't be affected or going to the 535 line of drivers on the AUR: https://aur.archlinux.org/packages/nvidia-535xx-dkms (note for a DKMS kernel module to work you need to have linux-headers installed) see https://bbs.archlinux.org/viewtopic.php?id=293400 for more information when this first surfaced.
Offline
I have installed the nvidia-535xx-dkms package and will see how it goes.
Thank you, I was up to date on the fixes but I lost track, sorry.
Rlu: 222126
Offline
Pages: 1