71

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by dibl on 2024/04/02, 00:05:01 »

Digging, digging, digging ...

I watched closely while attempting to install --reinstall nvidia-driver. It appears to me that the dkms process to build the nvidia module is not actually working (I have dkms and nvidia-kernel-dkms installed). Here is the output of the installation command:

Code: [Select]

Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
  libabsl20220623t64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 520 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://cdn.liquorix.net/siduction/fixes unstable/non-free amd64 nvidia-driver amd64 550.67-0siduction2 [520 kB]
Fetched 520 kB in 1s (637 kB/s)
(Reading database ... 282371 files and directories currently installed.)
Preparing to unpack .../nvidia-driver_550.67-0siduction2_amd64.deb ...
Unpacking nvidia-driver (550.67-0siduction2) over (550.67-0siduction2) ...
Setting up nvidia-driver (550.67-0siduction2) ...
root@dibl-MOW:~#
That's all of it -- no dkms module build output.

Following that exercise, here is the output of

Code: [Select]

modprobe nvidia

Code: [Select]

modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.7.6-1-siduction-amd64
Question: Is the 550.67 driver ONLY for kernel 6.8 and later?  I'm still on 6.7.

72

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by dibl on 2024/04/01, 22:53:45 »

Thank you, @ro_sid. Tomorrow will bring new energy to attack this issue.   

73

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by ro_sid on 2024/04/01, 22:41:33 »

But how to remove nouveau?

With my Ubuntu 18.04 LTS [I never upgraded beyond that because of "forced snap"], I always used

Code: [Select]

module-load=nvidia blacklist=nouveauin the grub kernel-load line ("linux").
With Debian 11

Code: [Select]

nouveau.modeset=0With Debian 12

Code: [Select]

nomodesetThen I could "rmmod (=modprobe -r) nouveau".
May be, one of those or a combination can help you, too .

The xserver-xorg-video-nouveau package is already removed.

You may even (re-)install that, it is just "xorg". The problematic part is the nouveau kernel driver, automatically included in the kernel package.

74

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by dibl on 2024/04/01, 21:58:48 »

The real problem is, as long, as nouveau module is loaded, no nvidia blob can be used.

Exactly correct!  And we all know what happens to the terminal display when I

Code: [Select]

modprobe -r nouveau.   

Thanks @geier0815 -- my /etc/X11/xorg.conf.d does not contain the 20-nvidia.conf file, but as far as I know, this is no longer needed. My other nvidia desktop does not have it, and it is running the nvidia driver correctly.

I have been setting "Wayland" in my  sddm login for over a year with no issues on that.

Maybe I can figure out a way to use the chroot helper on the siduction ISO to unload nouveau and load nvidia.

Or maybe I go to a VESA driver first, then nvidia.  But how to remove nouveau?  The xserver-xorg-video-nouveau package is already removed.

75

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by towo on 2024/04/01, 21:30:14 »

The real problem is, as long, as nouveau module is loaded, no nvidia blob can be used.

76

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by ro_sid on 2024/04/01, 20:53:31 »

My system is a hybrid system ("optimus") only, thus I can not really tell, how it should read, but ...

Code: [Select]

kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255... why is there no "/run/user/1000/kdeinit5__0" file? It is unlikely, that this is "nvidia"-dependent.
Also

Code: [Select]

startkde: Starting up...
startkde: Shutting down...
startkde: Done.seems to say, that you did not start it by/from a display manager (sddm)?
[A display manager should have the same problem starting with the nvidia-driver.]
Also for me this reads "plasma...", not "...kde".

The KDE people - to my knowledge - now prefer wayland over xorg. Is a mismatch possible? System assumes xorg, but default is wayland?

Finally, you could - in terminal mode - test, if the nvidia driver module/s is/are loaded (lsmod) at all.

77

Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver

« Last post by Geier0815 on 2024/04/01, 20:09:09 »

And what looks your /etc/X11/xorg.conf.d/20-nvidia.conf ( or similar) like?
I don't know if it is still needed this days, but I've got this config with

Code: [Select]

Section "Device"
Identifier "Device 0"
Driver "nvidia"
EndSection

78

Upgrade Warnings / Re: Attention! Malicious Software in testing and sid

« Last post by edlin on 2024/04/01, 18:10:51 »

Ich frage mich aber, ob es Sinn macht, das System neu zu installieren?

Welchen Sinn sollte eine Neuinstallation machen? Wenn du aus den offiziellen Isos von Siduction installierst, bist du auf dem Stand von September 2023. Machst du danach ein full-upgrade, bist du auf dem gleichen Stand wie vorher. Wenn du mehr Wert auf Stabilität und Sicherheit legst, musst du dir schon Debian/Stable oder eine gleichwertige Distri installieren.

Viel wichtiger ist wohl ein aktuelles Backup der Daten und einiger Konfigurationsdateien. Ein neues Siduction ist im Fall der Fälle schnell aufgesetzt.

edlin

79

Upgrade Warnings / Re: Attention! Malicious Software in testing and sid

« Last post by mrfloppy74 on 2024/04/01, 17:51:00 »

"Ich persönlich schiebe auch keine Paranoia und habe auch aktualisiert."

Ich frage mich aber, ob es Sinn macht, das System neu zu installieren?

Ssh war zwar aktiv aber durch den Router / Firewall von außen nicht erreichbar.

In den Logfiles sehe ich ebenfalls keine Zugriffsversuche von außen.

Nach dem Fund habe ich ssh erstmal deaktiviert.

80

Upgrade Warnings / Re: Attention! Malicious Software in testing and sid

« Last post by dibl on 2024/04/01, 16:11:47 »

Wenn man sich für Debian/Sid entscheidet, dann sollte man wissen, dass man halt auch der Erste in der Schlange am Schafott ist. Den Preis habe ich mehrere Jahrzehnte lang in Kauf genommen und die Vorzüge von Sid und OSS genossen. Und ich werde das auch weiterhin!

edlin

+1