How to downgrade nvidia drivers?

[rambo919]

A few months ago I needed non-ancient drivers to make new games work (not work better just plain actually load) so 525 was out of the question.

I used https://www.linuxcapable.com/install-nv ... on-debian/ to install 545 via ddm. Now however due to nvidia being stupid on their end and sending a hotfix only to certain places..... flatpaks are broken. So I though ok no problem.... just downgrade back to 525 or even non-hotfix 545. Computer says no.

525 remnants are still installed for some reason, ddm never removed them. ddm tries to install 390 but does not remove either 525 or 545. I tried a purge of nvidia with the nvidia repos disabled but then when I try to reinstall.... unmet dependencies and had to timeshift back to before I attempted to downgrade. This is a laughable situation.... I can maybe timeshift back all the way to november with no guarantee it will will work but for some reason it refuses to not also shift back parts of my /home which I cannot disable so backup first, ok, option. Imagine if on windows to merely downgrade a driver you have to potentially reinstall the OS?

What happened to the missing dependencies? Can I downgrade without timeshift or OS reinstall? Is my best option just to wait for nvidia to wake up and upgrade to the next driver version so flatpaks can work again? Is there a non-cuda repo somewhere I can try?

Code: Select all

System:
  Kernel: 6.6.9-amd64 [6.6.9-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6.9-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
    Distro: MX-23.1_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: Q370M D3H GSM PLUS serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: F15 date: 11/11/2021
CPU:
  Info: model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 800 high: 802 min/max: 800/4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 802 8: 800 9: 800 10: 800
    11: 800 12: 799 bogomips: 76799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte driver: nvidia v: 545.23.08
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1c82
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1080 s-dpi: 94 s-size: 1384x292mm (54.49x11.50")
    s-diag: 1414mm (55.69")
  Monitor-1: DVI-D-0 pos: top-center res: 1920x1080 hz: 60 dpi: 102
    size: 477x268mm (18.78x10.55") diag: 547mm (21.54") modes: N/A
  Monitor-2: HDMI-0 pos: primary,top-right res: 1920x1080 hz: 60 dpi: 93
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
  Monitor-3: HDMI-2 pos: bottom-l res: 1024x768 hz: 60 dpi: 102 size: 256x192mm (10.08x7.56")
    diag: 320mm (12.6") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 545.23.08 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  API: ALSA v: k6.6.9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: JACK v: 1.9.21 status: off with: a2jmidid status: off tools: jack_control
  Server-2: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Gigabyte driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bb class-ID: 0200
  IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Drives:
  Local Storage: total: 9.55 TiB used: 4.7 TiB (49.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3B4QFXO7 temp: 33.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000LPCX-24VHAT0 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-9YN164 size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC4B scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD Blue SA510 2.5 1000GB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 6100 scheme: MBR
  ID-5: /dev/sdd maj-min: 8:48 vendor: Toshiba model: HDWE140 size: 3.64 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: FP2A
    scheme: GPT
  ID-6: /dev/sde maj-min: 8:64 vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC25 scheme: MBR
Partition:
  ID-1: / raw-size: 97.66 GiB size: 95.56 GiB (97.86%) used: 51.79 GiB (54.2%) fs: ext4
    dev: /dev/sdc1 maj-min: 8:33
  ID-2: /home raw-size: 720.86 GiB size: 708.98 GiB (98.35%) used: 160.29 GiB (22.6%) fs: ext4
    dev: /dev/sdc2 maj-min: 8:34
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 12 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc3
    maj-min: 8:35
Sensors:
  System Temperatures: cpu: 36.0 C pch: 47.0 C mobo: 32.0 C gpu: nvidia temp: 45 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 4955 pm: dpkg pkgs: 4888 libs: 2527 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 67
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/atom.list
    1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
  Active apt repos in: /etc/apt/sources.list.d/deb-multimedia.list
    1: deb [signed-by=/usr/share/keyrings/deb-multimedia.gpg] https://www.deb-multimedia.org bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/element-io.list
    1: deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main
  Active apt repos in: /etc/apt/sources.list.d/freedownloadmanager.list
    1: deb [arch=amd64] https://debrepo.freedownloadmanager.org/ bionic main
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian-ppas-2.list
    1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu focal main
    2: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu focal main
    3: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu focal main
    4: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian-ppas.list
    1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu bionic main
    2: deb http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic main
    3: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu bionic main
    4: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu bionic main
    5: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu bionic main
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net/ bullseye main
  No active apt repos in: /etc/apt/sources.list.d/lutris.list
  Active apt repos in: /etc/apt/sources.list.d/makedeb.list
    1: deb [signed-by=/usr/share/keyrings/makedeb-archive-keyring.gpg arch=all] https://proget.makedeb.org makedeb main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://ftp.saix.net/pub/linux/distributions/mxlinux/mx/repo/ bookworm non-free main
    2: deb https://ftp.saix.net/pub/linux/distributions/mxlinux/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nvidia-drivers.list
    1: deb [signed-by=/usr/share/keyrings/nvidia-drivers.gpg] https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/ /
  Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
    1: deb https://download.onlyoffice.com/repo/debian/ squeeze main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list
    1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode/ stable main
  Active apt repos in: /etc/apt/sources.list.d/webmin.list
    1: deb [signed-by=/usr/share/keyrings/debian-webmin-developers.gpg] https://download.webmin.com/download/newkey/repository/ stable contrib
  Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
  Processes: 389 Uptime: 1h 8m wakeups: 1 Memory: 31.25 GiB used: 6.73 GiB (21.5%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

[TuxNuX]

nvidia driver with flakpack but are you serious?
Stop this kind of nonsense!
I don't understand what you want, why do you want to downgrade the drivers, it's stupid, your card is recent, you need drivers 525.xxx or more.
If it works well but one of the games does not work, the problem does not come from the video drivers but from your game
I want to help you but honestly I don't understand your problem :(

with ddm-mx you can force the installation of a version, but personally unless you really know what you are doing it is to be avoided
for more info in console type

Code: Select all

sudo ddm-mx -help

[wdscharff]

I can't solve your problem, but I can see some issues that could have led to the problem
(maybe, your problem is only the game)

You did NOT use the MXPI for the installation, which can always lead to problems. I have always installed nvidia drivers via MXPI, rarely had problems (which were always solved here promptly) and my biggest problem was that the drivers did not help me much (in my daily work). Especially with drivers, you should first try out external sources intensively on a test system, even if it is the manufacturer. By test system I don't mean a USB stick or a virtual machine, but (the only real thing) a real installation on the system on which it is to be used. I have a free 50GB partition on one of the connected SSDs for such "games"

I also see a lot of PPAs, i.e. Ubuntu sources, in the repos. This is suicide in action!

PPA are Ubuntu world (so not even debian), can work, but often break your system after the first update.
Keyword to google: FrankenDebian.

Anyone who has at least taken a cursory look at the documentation, help files and the wiki for MX knows that it is better not to do this.

that smells like a new installation

[Eadwine Rose]

nvidia driver with flakpack but are you serious?
Stop this kind of nonsense!
I don't understand what you want, why do you want to downgrade the drivers, it's stupid, your card is recent, you need drivers 525.xxx or more.
If it works well but one of the games does not work, the problem does not come from the video drivers but from your game
I want to help you but honestly I don't understand your problem :(

@TuxNuX

Calling things nonsense and stupid is not a helpful way to address peoples' questions. Please refrain from doing this in the future.

[rambo919]

nvidia driver with flakpack but are you serious?
Stop this kind of nonsense!
I don't understand what you want, why do you want to downgrade the drivers, it's stupid, your card is recent, you need drivers 525.xxx or more.
If it works well but one of the games does not work, the problem does not come from the video drivers but from your game
I want to help you but honestly I don't understand your problem :(

with ddm-mx you can force the installation of a version, but personally unless you really know what you are doing it is to be avoided
for more info in console type

Code: Select all

sudo ddm-mx -help

Any OpenGL accelerated flatpak requires an equivalent flatpak graphics driver runtime to run.... because of the driver version mismatch it cannot find one so it just does not start up. The obvious solution is to downgrade the graphics driver back down to a version before this mismatch occurred. This is something that should not happen but in this case it did because nvidia was lazy and pushed a fire and forget hotfix that basically broke half of flatpak for anyone with that driver version.

[rambo919]

I can't solve your problem, but I can see some issues that could have led to the problem
(maybe, your problem is only the game)

You did NOT use the MXPI for the installation, which can always lead to problems. I have always installed nvidia drivers via MXPI, rarely had problems (which were always solved here promptly) and my biggest problem was that the drivers did not help me much (in my daily work). Especially with drivers, you should first try out external sources intensively on a test system, even if it is the manufacturer. By test system I don't mean a USB stick or a virtual machine, but (the only real thing) a real installation on the system on which it is to be used. I have a free 50GB partition on one of the connected SSDs for such "games"

I also see a lot of PPAs, i.e. Ubuntu sources, in the repos. This is suicide in action!

PPA are Ubuntu world (so not even debian), can work, but often break your system after the first update.
Keyword to google: FrankenDebian.

Anyone who has at least taken a cursory look at the documentation, help files and the wiki for MX knows that it is better not to do this.

that smells like a new installation

The thing is the driver actually runs flawlessly and per se I have no problem with it.... but it has a fight with flatpak which I only noticed way after, probably the hotfix came out later when I was not paying attention. This was from the official nvidia repo btw not a ppa, this is completely their mess.

Numerous people over the last period of time have tried to get newer drivers into MXPI but it always gets rebuffed because no one feels like working on it... otherwise I would have taken that route.... you even have the ridiculous situation where there is nothing in the test repo at all even though 535 is officially considered stable (but it's a buggy mess IMO that got replaced instead of fixed) and 545 runs better than both 525 and 535. The irony is unless someone wakes up and smells the rotting corpse the next driver version in MXPI will be the inferior 535 and that will only happen in a year or so's time.

For reference, it's not all that an obscure problem https://forums.developer.nvidia.com/t/5 ... age/273181

[Snod Blatter]

I also installed the drivers from the CUDA repo so this was interesting to me. I've never had this problem but then I don't run flatpaks soo....

Anyway, it seems that just a few hours ago the CUDA 545.23.08 drivers were added to Flatpak, so hopefully it'll work now? If not you can also try the command

Code: Select all

flatpak update

to get the new driver.

Fingers crossed!

[TuxNuX]

I can't solve your problem, but I can see some issues that could have led to the problem
(maybe, your problem is only the game)

You did NOT use the MXPI for the installation, which can always lead to problems. I have always installed nvidia drivers via MXPI, rarely had problems (which were always solved here promptly) and my biggest problem was that the drivers did not help me much (in my daily work). Especially with drivers, you should first try out external sources intensively on a test system, even if it is the manufacturer. By test system I don't mean a USB stick or a virtual machine, but (the only real thing) a real installation on the system on which it is to be used. I have a free 50GB partition on one of the connected SSDs for such "games"

I also see a lot of PPAs, i.e. Ubuntu sources, in the repos. This is suicide in action!

PPA are Ubuntu world (so not even debian), can work, but often break your system after the first update.
Keyword to google: FrankenDebian.

Anyone who has at least taken a cursory look at the documentation, help files and the wiki for MX knows that it is better not to do this.

that smells like a new installation

if you installed with a flatpak you must uninstall with a flatplack
if you installed with a ".run" you must uninstall with the ".run"
And from what I can understand you had to install more times with different installers and that's why you end up with several versions of drivers and a bunch of problems
the debian mx drivers work really very well and unless you have an insurmountable problem you should avoid installing them from other sources
I think you'll have to delete everything manually.
I've already done anything wrong (I'm stupid too hahaha) and found myself with several versions of the same program, it's really hard to repair especially if it concerns drivers or other things important to the system
maybe you will have to reinstall your distribution :(
But is your game a Linux or Windows game?

[TuxNuX]

everyone does what they want but personally I do not recommend flatpaks especially for drivers and important things concerning the system
If you really have no choice, it is better to use the ".run" drivers from the Nvidia website

[rambo919]

everyone does what they want but personally I do not recommend flatpaks especially for drivers and important things concerning the system
If you really have no choice, it is better to use the ".run" drivers from the Nvidia website

Uhm, you seem confused.

Flatpak does the driver mirroring itself, you cannot install a driver from a flatpak, it looks at what you are running and installs the corresponding flatpak runtime. This is where the version mismatch breaks flatpak and only flatpak. Anything from gzdoom to peazip or calibre is broken because of this.

As for the game that caused me to have to update the graphics drivers, it was Starfield.... which still runs better on windows anyway annoyingly. The big games that started coming out in the last months of 2023 pretty much all require 545 version... and it's going to continue this year. They use functions not implemented yet in the older drivers.