Welcome, Guest. Please login or register.
Did you miss your activation email?

Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Software - Support / Re: Nouveau ----> Nvidia, trouble changing driver
« Last post by ro_sid on 2024/04/01, 22:41:33 »
Quote
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 :).
Quote
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.

72
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.   :-X

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.
73
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.
74
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.
75
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
76
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

77
"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.
78
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
79
Upgrade Warnings / Re: Attention! Malicious Software in testing and sid
« Last post by edlin on 2024/04/01, 16:01:51 »
Ich persönlich schiebe auch keine Paranoia und habe auch aktualisiert. Ich gehe davon aus, dass zumindest im aktuellen Fall, der Weckschrei laut genug war und die Aktualisierungen entsprechend gründlich vorbereitet werden.
Ein (absolut) sicheres Betriebssystem gibt es nicht. Software wird von Menschen geschaffen und die machen auch mal Fehler oder bauen Fehler ein, egal aus welchen Interessen. Und KI „lernt“ aus diesen Fehlern ...

Bleibt am Ende des Tages nicht mehr viel übrig: Ein Atari 800 XL oder ein Sinclair ZX Spectrum? Oder doch lieber ein Z80 Eigenbau (siehe Sprut: https://www.sprut.de/misc/sp04_1.jpg) mit FORTH? Oder ein K1003 von robotron (den U808 hab ich selbst noch in Maschinencode für einen Messplatz programmiert und die Hardware erweitert)?

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
80
Software - Support / Nouveau ----> Nvidia, trouble changing driver
« Last post by dibl on 2024/04/01, 15:34:06 »
It's been a very long time since I had any kind of trouble managing with graphics drivers, but today it feels like something has changed. This post was moved from the "Upgrades > Kernel 6.8x" item because it's not really on that topic.

At the end, I'll post a few of the search results that I have found, none of which have worked to change from nouveau to nvidia driver.

First, let me say my two desktop screens are beautiful and working perfectly with the nouveau driver, so it's not a problem for me if I can't go back to nvidia. But curiosity compels me to ask around, to find out what I've missed.

Code: [Select]
$ inxi -SG
System:
  Host: dibl-MOW Kernel: 6.7.6-1-siduction-amd64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 5.27.10 Distro: siduction 22.1.2 Masters_of_War -
    kde - (202303151559)
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nouveau v: kernel
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau
    resolution: 1: 1920x1200~60Hz 2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: nouveau,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.0.4-1 renderer: NV136

don@dibl-MOW:~$ sudo apt policy xserver-xorg-video-nouveau
xserver-xorg-video-nouveau:
  Installed: (none)
  Candidate: 1:1.0.17-3
  Version table:
     1:1.0.17-3 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages

don@dibl-MOW:~$ sudo apt policy nvidia-driver
nvidia-driver:
  Installed: 550.67-0siduction2
  Candidate: 550.67-0siduction2
  Version table:
 *** 550.67-0siduction2 500
        500 https://liquorix.net/siduction/fixes unstable/non-free amd64 Packages
        100 /var/lib/dpkg/status
     535.161.08-1 500
        500 https://deb.debian.org/debian unstable/non-free amd64 Packages

don@dibl-MOW:~$ nvidia-settings

ERROR: NVIDIA driver is not loaded

(nvidia-settings:72640): GLib-GObject-CRITICAL **: 07:38:05.012: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (nvidia-settings:72640): CRITICAL **: 07:38:05.013: ctk_powermode_new: assertion '(ctrl_target != NULL) && (ctrl_target->h != NULL)' failed

don@dibl-MOW:~$ lsmod | grep nouveau
nouveau              2514944  42
drm_gpuvm              16384  1 nouveau
mxm_wmi                12288  1 nouveau
drm_exec               12288  1 nouveau
gpu_sched              32768  1 nouveau
i2c_algo_bit           12288  1 nouveau
drm_ttm_helper         12288  1 nouveau
ttm                    69632  2 drm_ttm_helper,nouveau
drm_display_helper    143360  1 nouveau
button                 16384  1 nouveau
video                  57344  2 asus_wmi,nouveau
wmi                    20480  5 video,asus_wmi,wmi_bmof,mxm_wmi,nouveau

So nouveau is loaded, nvidia-driver and all related packages including dkms, nvidia-kernel-dkms, firmware-misc-nonfree, and firmware-nvidia-gsp are installed.

I set /etc/default/grub:

Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="nouveau.blacklist=1 quiet systemd.show_status=1"and updated grub.

I added /etc/default/modprobe.d/blacklist-nouveau.conf:

Code: [Select]
blacklist nouveau
options nouveau modeset=0

~/.xsession-errors -- Successful boot, nouveau not blacklisted:

Code: [Select]
Xsession: X session started for don at Mon Apr  1 08:22:50 AM EDT 2024
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/tmp/xauth_mpNVdL
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE
localuser:don being added to access control list
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
qt.svg: /usr/share/wallpapers/mow.svg:286:33: Could not resolve property: #linearGradient2611
(This last line is related to my "live" wallpaper setup and is not a problem)

Booting with nouveau blacklisted:

Code: [Select]
Xsession: X session started for don at Mon Apr  1 07:18:41 AM EDT 2024
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/tmp/xauth_AABZNz
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE
localuser:don being added to access control list
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
qt.svg: /usr/share/wallpapers/mow.svg:286:33: Could not resolve property: #linearGradient2611
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
startkde: Starting up...
startkde: Shutting down...
startkde: Done.


I reviewed Debian wiki:
https://www.startpage.com/sp/search?query=debian+wiki+nvidia+graphics&cat=web&pl=opensearch&language=english
and
https://wiki.debian.org/NvidiaGraphicsDrivers/Troubleshooting

and Debian forums.

Now I'm scratching my head.  Is it old age?  ;-)

Pages: 1 ... 6 7 [8] 9 10