Hi! I've been using Siduction for the past few months, and it's been very nice as my first ever distrohop (I was using Mint before).
I've had a problem where Kernels 6.15.7-1-siduction-amd64 and 6.15.6-1-siduction-amd64 both fail to load to sddm. They both reach chkrootkit on the loading terminal screen before getting stuck there. I can use Ctrl+Alt+F2 to reach a terminal view and login through that, but visuals never appear.
6.15.5-1 does work just fine, though. From reading the other topics around here, it may have something to do with NVidia's drivers? I wouldn't know what to do with that information, though.
Basically, I wanted to ask for an explanation / a way to fix it, since going through the [DE] thread with DeepL could only get me so far (yeehaw american English and all that). I'm not too deep into general Linux knowledge, but I know my way around the terminal.
(If this is the wrong spot to put this thread, my apologies. First post and all.)
Appreciate it!
-tD
Show $ inxi -G
See:
https://forum.siduction.org/index.php?topic=9721.msg77248#msg77248
It begins DE and moves to EN ...
Ah, yeah. Suppose that would be a necessary step.
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070] driver: nvidia v: 550.163.01
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
loaded: nvidia gpu: nvidia resolution: 1: N/A 2: 1920x1080~144Hz
API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.163.01
renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2
API: Vulkan v: 1.4.315 drivers: nvidia,llvmpipe surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
I had scrolled through that post before, like mentioned. Checked again, still confused. I know it's a problem with the Linux Nvidia Drivers, and I know they need to be patched, I guess? Either that or updated.
Either way, thanks for your help.
Do you have the sidution fixes repo enabled?
Look at
apt policy nvidia driver whether or not you have the unfixed Debian version or the fixed siduction version of the driver.
Quotenvidia-driver:
Installiert: (keine)
Installationskandidat: 550.163.01-1siduction1
Versionstabelle:
555.42.02-1 1
1 http://dellopti:3142/deb.debian.org/debian experimental/non-free amd64 Pack$
550.163.01-1siduction1 500
500 http://dellopti:3142/packages.siduction.org/fixes unstable/non-free amd64 P$
550.163.01-1 500
500 http://dellopti:3142/deb.debian.org/debian unstable/non-free amd64 Packages
500 http://dellopti:3142/deb.debian.org/debian testing/non-free amd64 Packages
535.247.01-1~deb12u1 500
500 http://dellopti:3142/deb.debian.org/debian stable/non-free amd64 Packages
500 http://deb.debian.org/debian stable/non-free amd64 Packages
I assume they *look* the same in inxi!
Sorry for the delay, I got sick at the worst possible time.
:~$ apt policy nvidia driver
Notice: Unable to locate package nvidia
Notice: Unable to locate package driver
:~$ apt policy nvidia-driver
nvidia-driver:
Installed: 550.163.01-1siduction1
Candidate: 550.163.01-2
Version table:
550.163.01-2 500
500 https://deb.debian.org/debian unstable/non-free amd64 Packages
*** 550.163.01-1siduction1 500
500 https://ftp.belnet.be/mirror/siduction/fixes unstable/non-free amd64 Packages
100 /var/lib/dpkg/status
Update: it has gotten worse and I can no longer get to the boot screen at all. I still have the terminal, sure, but without graphics, it basically makes my PC for the tasks I use it for completely useless.
The nvidia persistence service fails to start, and I've tried a few things, notably reinstalling the nvidia-driver package and trying different kernels... Essentially, basic troubleshooting steps. I'm at a complete loss on what to do anymore.
did you apt update && apt dist-upgrade ?
In /etc/default/grub you need a line similar to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.show_status=1 nvidia_drm.modeset=1"
Hi again! Okay, so firstly, yes I did do a full upgrade sweep to try and get it fixed, with no dice.
I didn't see the grub thing until much later, but it turns out that it's unnecessary (sorry).
So after a bunch of troubleshooting with apt, looking stuff up on my phone about how drivers work, I managed to stumble across the solution of "Install the headers, you goof!". I think what happened was with an apt autoremove, it removed some of the headers for versions I wasn't using at the time. Get a kernel update with an upgrade, remove those same kernel's headers with an autoremove, go up one, the headers are gone, so no drivers. try to update and autoremove again from the terminal (ctrl + alt + f2), therefore removing the other kernel's headers.
Basic TL;DR: I did
sudo apt install linux-headers-6.15.7-1-siduction-amd64
then rebooted, and everything is good again.
Real weird, but now I know for the future.
Sorry for the trouble ! :)
Don't install linux-headers-$version-siduction-amd64, install linux-headers-siduction-amd64
Thanks for the advice! I did that, it installed the newer ones no problem.