Open duhow opened 4 months ago
Same issue, sudo systemctl restart sddm
also helped me login.
Hardware: ASRock B250M-HDV Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz NVIDIA GeForce RTX 3070/PCIe/SSE2
Here output of rpm-ostree status
. Pinned image index 1 (2024-02-14) used to work, but from a couple of days ago stopped and index 2 (2024-02-05) is the only one that works without workarounds.
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
Digest: sha256:b2e9d91aee99cb448274955238093f129e7871aa6506c25e20ca6b735ac31c2f
Version: 39.20240116.0 (2024-02-25T07:26:47Z)
Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
Digest: sha256:cb9e8310f7180042c48a42ddb3519a337c49fccb4b74b54d81644c905ce12683
Version: 39.20240116.0 (2024-02-14T09:33:57Z)
Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'
Pinned: yes
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
Digest: sha256:3fc5f0ab5d9349c9edbf6b03a6e33a5701174233a10d85d5c6bbe49cab404766
Version: 39.20240116.0 (2024-02-05T09:03:16Z)
Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'
Pinned: yes
For what it's worth
This issue caught my attention also, as another unfortunate nVidia consumer...
But i don't (luckily) experience the described problem on my machine.
I checked https://www.nvidia.com/Download/driverResults.aspx/214100/en-us/ and looks like the 545.29.02
driver supports these as an excerpt from the total:
GeForce RTX 30 Series (Notebooks):
GeForce RTX 3080 Ti Laptop GPU, GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Ti Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU
GeForce RTX 30 Series:
GeForce RTX 3090 Ti, GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti, GeForce RTX 3060, GeForce RTX 3050
GeForce 900 Series:
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950
545.29.06
), anyhow:
@duhow
Can you try to see if the problem persists wtihout using shunshine
:thinking:
@janoxakes can you try to enroll the new MOK-Key using the ujust
command on the newer images?
They used a different akmods-MOK-key
back then IIRC.
Maybe both of you need to enroll this (new) MOK-Key, in case you are booting with SecureBoot on... :woman_shrugging:
While I do have sunshine
, I haven't used it, and I don't recall it starts during boot process...
Surprisingly, without any other changes than bumping to latest version, ~now it seems to be working?~
📝 EDIT: Nah, after rebooting the issue happened again.
[ 15.428435] show_signal_msg: 7 callbacks suppressed
[ 15.428437] sddm-greeter[4359]: segfault at 178 ip 00007f6842e15a80 sp 00007ffd30774220 error 4 in libnvidia-eglcore.so.545.29.06[7f6842427000+bc3000] likely on CPU 3 (core 3, socket 0)
[ 15.428449] Code: fe e8 d4 d5 0b 00 eb 8a 66 90 48 8b 78 10 4c 89 fe ff d2 e9 7a ff ff ff 66 90 55 48 89 fd 53 48 83 ec 08 48 8b 87 e0 03 00 00 <48> 39 b8 78 01 00 00 0f 84 eb 00 00 00 48 8b bd e8 03 00 00 48 85
[ 16.441422] evdi: [I] (card3) Closed by Task 4983 ((sd-close)) of process 4983 ((sd-close))
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
Digest: sha256:e7bf4f3cc4ae67e49f81cf1d6a4f57a90656757cde71c02be4e267eff689b418
Version: 39.20240116.0 (2024-02-24T02:02:28Z)
LocalPackages: sunshine-0.21.0-1.x86_64
Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
Digest: sha256:0c779386100258771e5947e913348d072935e2683f8301ca5c256d4b8f44bbb0
Version: 39.20240116.0 (2024-02-20T17:03:54Z)
LocalPackages: sunshine-0.21.0-1.x86_64
Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'
@TriMoon, I have secure boot disabled because I had similar (related?) issues mid january. I followed the steps for enrolling the keys in secure boot anyway back then, and they appear as already registered. AFAIK, if it was due to secure boot, restarting sddm wouldn't solve anything, right?
@fedora:~$ just enroll-secure-boot-key
echo 'Enter password "ublue-os" if prompted after your user password.'
Enter password "ublue-os" if prompted after your user password.
sudo mokutil --timeout -1
[sudo] password for jano:
sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der
SKIP: /etc/pki/akmods/certs/akmods-ublue.der is already enrolled
echo 'When you reboot your computer, follow the instructions to start MOK util'
When you reboot your computer, follow the instructions to start MOK util
echo 'by pressing a key, then enroll the secure boot key and enter "ublue-os" as the password'
by pressing a key, then enroll the secure boot key and enter "ublue-os" as the password
AFAIK, if it was due to secure boot, restarting sddm wouldn't solve anything, right?
Iv'e met so many illogical bugs in my live, that i stopped looking for logical reasons when it comes to bugs in programs :rofl: But anyhow, it was just a something you guys might want to try.
Didn't solve the problem it seems, so i have no idea what to suggest further... (This uBlue/ostree stuff is also new to me, so..) :woman_shrugging:
@duhow it suddenly started working fine for me today. I hadn't used the system for over a week so it might be one of the updates during this time.
Did it work for you?
I've run in to this as well with though it's moved on from sddm crashing to pretty much all of the KDE apps segfaulting inside the nvidia driver. Doing a kill
on the kdewayland
process than systemctl restart sddm
seems to work to bring it back.
Apr 12 18:41:57 fedora kernel: kded5[4896]: segfault at 178 ip 00007fae3a4fc140 sp 00007ffc1d4ea5c0 error 4 in libnvidia-glcore.so.550.67[7fae39800000+1d27000] likely on CPU 3 (core 3, socket 0)
Describe the bug
Power on the PC, boot splash screen, then terminal. No login, just the blinking cursor
_
. Sometimes white garbage pixels show.sddm-greeter
crashed according todmesg
.If I run into another TTY, login, then
sudo systemctl restart sddm
, everything works again fine.What did you expect to happen?
Boot into the login screen.
Output of
rpm-ostree status
Hardware
ASUSTeK Z170-A Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz NVIDIA Corporation GM204 [GeForce GTX 970]
Extra information or context