Nvidia Driver install

Working on xfce, I have got a problem with nvidia RTX5050 that had been working fine until now. After the last update, the graphics are slower and clearly limited with a drop of fps when gaming and finally, freezing.

Acording to nvidia driver base the new driver is 595 but only 580 is available until now and I assume this would be working. I cannot activate v580 as it is conflicting with the open nvidia

manjaro-settings-manager

gives

config 'video-nvidia-580xx' conflicts with config(s): video-nvidia

I did also make other intents with mhwd and forcing install of the new driver but all this enter in conflict with the nvidia installation and does not conclude.
Finally, I am a bit confused by the output of

nvidia-smi

that gives

NVIDIA-SMI 610.43.02              KMD Version: 610.43.02     CUDA UMD Version: 13.3

According to my former investigations, KMD version corresponds to a Driver version, 610, well above 595.

I did finally also apply kernel 6.18 from 6.12 but this did not solve anything.

First, I don’t have nvidia gpus. However, the package nvidia-open-dkms is probably installed and this is the latest driver. Do you want to downgrade the driver? I would rather recommend to try to upgrade the kernel to 7.1 or even 7.2rc. You can keep the 6.18 as fallback. Manjaro’s setting manager makes it easy to install several kernels.

Thank you, I am not willing to downgrade the driver but my system upgrade did mess up the nvidia set-up.
I will try to install nvidia-open-dkms that is missing indeed but I do not know why?
I prefer to stay with 6.18 wich is the LTS version.
I will try and report.
Thank you

This does not work and I did uninstall.
Back again to the driver that is not working completely

Mod edit: Consecutive posts merged.

Please post the output of inxi -zv8.

2 Likes

Your GPU should work with both 610 and 580, but 610 is a new feature branch so may have more issues. Not sure why 595 is no longer in the repo, I didn’t notice until now (unless I forgot about it).

There could be other reasons for that.

It’s generally helpful if you show the command and resulting output so we can see what’s going on.

Anyway this should do it.

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia-580xx

If you get a conflict with libxnvctrl, remove it and run the command again, like below.

sudo pacman -Rdd libxnvctrl
sudo mhwd -i pci video-nvidia-580xx

It should pull in libxnvctrl-580xx automatically. If not then re-install it manually.

sudo pacman -S libxnvctrl-580xx 

Because you’ll have linux618-nvidia-open instead.

Thank you for your help.

Applying your proposals gives:

sudo mhwd -r pci linux-nvidia   > Error: config 'linux-nvidia' is not installed!
sudo mhwd -i pci linux-nvidia-580xx   > Error: config 'linux-nvidia-580xx' does not exist!

I did try to install them with sudo pacman -S linux-nvidia linux-nvidia-580xx error: target not found: linux-nvidia linux-nvidia-580xx

I dif identify another interesting package related to the driver 580 that is probably more adapted for the time beeing and tryed to install

sudo pacman -Syu linux-nvidia-580xx-meta

:: nvidia-580xx-utils-580.159.04-1 and nvidia-utils-610.43.02-2 are in conflict (nvidia-libgl). Remove nvidia-utils? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency 'nvidia-utils=610.43.02' required by lib32-nvidia-utils
:: removing nvidia-utils breaks dependency 'nvidia-utils=610.43.02' required by linux618-nvidia-open

My personnal impression is that the recent upgrade of Manjaro did install the driver 610 which is not fully working for me and the whole “system” of driver/utils is blocking the downgrading.
All my explorations yesterday did give a similar result, conflict and dependencies that would be broken.
Nota: I did keep the kernel 6.18 LTS as the default to avoid an additiionnal difficulty for the time being

Sorry they were typos, should’ve been video-nvidia and video-nvidia-580xx, I’ve fixed my original post.

The actual packages would be linux618-nvidia-open and linux618-nvidia-580xx-open, but there are other packages which mhwd will take care of, so use mhwd.

No problem with the typo, I could have seen it also!
But I get about the same conclusion, conflict with nvidia-utils and driver 610

Applying your proposals gives:

sudo mhwd -r pci video-nvidia   > error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency 'nvidia-utils' required by gpu-control
:: removing nvidia-settings breaks dependency 'nvidia-settings' required by gpu-control
sudo mhwd -i pci video-nvidia-580xx   > Error: config 'video-nvidia-580xx' conflicts with config(s): video-nvidia

The first Error indicates that gpu-control is the problem and I remember I installed it a week ago. I will try to remove it first.

The second Error suggests that the solution might be with the configs??? Any idea?

I am trying to reinstal the linux618-nvidia-open and linux618-nvidia-580xx-open as I thing this is also necessary but there is a permanent conflict with the former driver nvidia-utils-610.43.02-2. Should I try all this directly from ther terminal in a terminal session and not a grpahic session?

I can find this package only in the AUR. This isn’t part of neither the Manjaro nor the Arch distribution.

I’m wondering what your goal is. You didn’t say what driver is installed and you didn’t post the output of inxi -zv8. My guess is linux618-nvidia is installed. Or maybe linux618-nvidia-open as another guess. But the folks who try to help aren’t here to waste their time guessing :man_with_white_cane: :man_shrugging:

Probably best to remove gpu-control and re-install it afterwards.

sudo pacman -R gpu-control

It indicates the first command didn’t complete, as such video-nvidia is still used, so it still conflicts.

Hello, I know I did not post the output of inxi -zv8 because it is very large and do not know how to share it efficiently or select the adequate information. On the other hand, I was clearly struggling between the driver 580 and 610 and changing the kernel at the same time in order to sort it out.
Eliminating gpu-control did clarify a bit and I am on the good way but not yet sure of the result.

inxi -zv8 | grep nvidia

gives

  Device-1: NVIDIA GB207 [GeForce RTX 5050] vendor: ASUSTeK driver: nvidia
    v: 580.159.04 alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+
    driver: X: loaded: nvidia gpu: nv_platform,nvidia,nvidia-nvswitch
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 580.159.04
    gpu: nvidia-settings,nvidia-smi x11: xprop
  System Temperatures: cpu: 33.9 C mobo: 31.0 C gpu: nvidia temp: 54 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%

The current situation if kernel 6.18 and

The installation seems to be more “clean” now but something is not working as I cannot even launch a GPU-demanding software now.

You share it just like you did but without any truncation or “selecting the adequate information”. So again please post inxi -zv8.

Now given the GeForce RTX 5050 is about a year old, wrt Linux this is like new. One should expect a delay for the best driver support on Linux even in case of AMD and Intel (and these companies provide open source drivers for their GPUs since over a decade at least and although Nvidia may be willing now to support Linux better than in the past at least for their new cards they can’t catch up a decade of experience in a year or so.)

Assuming the rest of your system is also rather fresh and fits well together i’m wondering why you chose to use Manjaro but sort of refuse to try the latest kernels together with the latest drivers. Notice with Manjaro’s settings manager you can easily install several kernels in parallel and the drivers for the different kernel versions don’t conflict with each other. Of course you can always run only one kernel but you can choose which one to boot from the grub menu. (It has been always like this.)

So for what reason you don’t install 7.1 and 7.2rc together with the latest video-nvidia? (Normally there isn’t much reason to run an old kernel with the latest gpu driver - there might be exceptions. IMO, there is even less reason to run 580 on your gtx 5050.) You can also try whether the open source driver versions run better than the proprietary ones - i mostly read the proprietary ones would be still better. There isn’t anything that could go wrong. In the worst case a kernel/gpu driver combo would boot into a black screen or so, and then from the boot menu you simply pick the 6.18 kernel. (Nobody said you should uninstall it.)

Moreover, the 3rd component to keep an eye on is the graphics stack, that is, mesa, opengl and perhaps vulkan (if nvidia gpus should run this).

3 Likes

Thank you for your patience

Here is the inxi output

System:
  Kernel: 6.18.36-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=34f6fa13-77fd-4feb-b71d-8c3b76d7b15d rw quiet splash apparmor=1
    security=apparmor resume=UUID=5129dbde-86ac-421f-aefd-7cc11041bf7a
    udev.log_priority=3
  Desktop: Xfce v: 4.20.2 tk: Gtk v: 3.24.52 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: B550M DS3H v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: B550M DS3H v: x.x serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: FD date: 03/22/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.48 GiB used: 2.62 GiB (16.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
    part-no: F4-3600C18-8GVK serial: N/A
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
    part-no: F4-3600C18-8GVK serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 5500 bits: 64 type: MT MCP arch: Zen 3 gen: 3
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm)
    family: 0x19 (25) model-id: 0x50 (80) stepping: 0 microcode: 0xA500012
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 798 high: 799 min/max: N/A cores: 1: 798 2: 798 3: 797
    4: 798 5: 798 6: 798 7: 799 8: 798 9: 798 10: 798 11: 799 12: 798
    bogomips: 19164
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm_lock syscall tce topoext tsc tsc_scale umip user_shstk
    v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq
    wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GB207 [GeForce RTX 5050] vendor: ASUSTeK driver: nvidia
    v: 580.159.04 alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 5 speed: 32 GT/s lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:2d83
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.23 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: nvidia gpu: nv_platform,nvidia,nvidia-nvswitch
    display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: HDMI-A-1 model: C24A1H serial: <filter> built: 2025
    res: 1920x1080 dpi: 94 gamma: 1.2 chroma: red: x: 0.675 y: 0.318 green:
    x: 0.290 y: 0.612 blue: x: 0.141 y: 0.055 white: x: 0.314 y: 0.329
    size: 522x294mm (20.55x11.57") diag: 600mm (23.6") ratio: 16:9
    modes: 1920x1080, 1680x1050, 1600x900, 1280x1024, 1280x960, 1152x864,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 580.159.04
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5050/PCIe/SSE2
    memory: 7.77 GiB
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xprop
Audio:
  Device-1: NVIDIA GB207 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: gen: 5 speed: 32 GT/s
    lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22ec class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.18.36-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 931.53 GiB used: 309.44 GiB (33.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD2500AAKX-753CA1 size: 232.89 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 1H19
    scheme: GPT
  Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-216AB rev: MD00
    dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 75 GiB size: 73.27 GiB (97.70%) used: 50.69 GiB (69.2%)
    fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 34f6fa13-77fd-4feb-b71d-8c3b76d7b15d
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 324 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: D417-F473
  ID-3: /data/pc/fly raw-size: 300 GiB size: 294.23 GiB (98.08%)
    used: 170.14 GiB (57.8%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: Fly
    uuid: 54d1ba1f-ce7b-41c8-93a0-889b4fb340e1
  ID-4: /data/pc/sda6 raw-size: 153.38 GiB size: 150.8 GiB (98.31%)
    used: 88.61 GiB (58.8%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: N/A
    uuid: 7fefcd70-9e7b-4575-96a1-5c18bc43d23c
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: 5129dbde-86ac-421f-aefd-7cc11041bf7a
Unmounted:
  ID-1: /dev/sdb2 maj-min: 8:18 size: 165.76 GiB fs: ntfs label: Fly500_MS
    uuid: 7876C5DB7B36FBC8
  ID-2: /dev/sdc1 maj-min: 8:33 size: 42.4 GiB fs: ext4 label: N/A
    uuid: 01fa6873-73d2-47c6-9c60-93d590d0628f
  ID-3: /dev/sdc2 maj-min: 8:34 size: 32.88 GiB fs: ntfs label: N/A
    uuid: 2E4D83A41CBEBB5E
  ID-4: /dev/sdc3 maj-min: 8:35 size: 26 GiB fs: ext4 label: Manjaro
    uuid: fbca60ca-a334-44f0-bc99-2e8238236e8c
  ID-5: /dev/sdc4 maj-min: 8:36 size: 131.6 GiB fs: ext4 label: N/A
    uuid: 7fefcd70-9e7b-4575-96a1-5c18bc43d23c
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Logitech Nano Receiver type: mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52f class-ID: 0300
  Device-2: 1-5:3 info: CHERRY Keyboard type: keyboard,HID
    driver: cherry,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 046a:0023 class-ID: 0300
  Device-3: 1-10:4 info: Integrated Express RGB LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:5702 class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:6 info: Saitek PLC Pro Flight Rudder Pedals type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 06a3:0763 class-ID: 0300
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 5-1:2 info: Realtek Mass Storage Device
    type: smart card,mass storage driver: usb-storage,usbfs interfaces: 2
    rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 0bda:0169 class-ID: 0806 serial: <filter>
  Hub-6: 5-2:3 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 214b:7250 class-ID: 0900
  Hub-7: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 32.9 C mobo: 29.0 C gpu: nvidia temp: 41 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 1438 pm: pacman pkgs: 1430 libs: 395 tools: pamac,yay pm: flatpak
    pkgs: 8
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    2: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    3: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    4: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    5: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    8: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 350
  1: cpu: 28.7% command: exe pid: 3626 mem: 356.4 MiB (2.2%)
  2: cpu: 25.0% command: librewolf pid: 1908 mem: 465.8 MiB (2.9%)
  3: cpu: 19.2% command: librewolf pid: 3514 mem: 464.0 MiB (2.9%)
  4: cpu: 17.0% command: librewolf pid: 3683 mem: 286.1 MiB (1.8%)
  5: cpu: 11.4% command: keepassxc pid: 1911 mem: 135.2 MiB (0.8%)
  Memory top: 5 of 350
  1: mem: 465.8 MiB (2.9%) command: librewolf pid: 1908 cpu: 25.0%
  2: mem: 464.0 MiB (2.9%) command: librewolf pid: 3514 cpu: 19.2%
  3: mem: 356.4 MiB (2.2%) command: exe pid: 3626 cpu: 28.7%
  4: mem: 286.1 MiB (1.8%) command: librewolf pid: 3683 cpu: 17.0%
  5: mem: 225.6 MiB (1.4%) command: nextcloud pid: 1913 cpu: 6.3%
Info:
  Processes: 350 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.1 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 260 default: graphical tool: systemctl
  Compilers: clang: 22.1.6 gcc: 16.1.1 Shell: Zsh v: 5.9.1
    running-in: xfce4-terminal inxi: 3.3.40

I am not against the idea to install a new kernel and do it regularly but I had a lot of unsolved problems and wanted to “clean” my install first. I do not quite know how to manage various drivers but maybe I can also choose between different drivers (580 and 610) as I do with kernels, using manjaro-settings-manager

I understand the argument with newer material (a computer I did build some weeks ago) and it is a good point also for me to keep in mind.

I already have been able to extract a reasonable power from this GPU with some adjustment of nvidia-settings until last week and something went wrong after the update. gpu-control is one possibly, maybe others?

I don’t know what “clean” is meant to mean. But if it hasn’t solved your problems and even made them worse then your issue seems to be elsewhere.

I’d probably change back to 610 and try then and find your issue. You might want to check what your temps are like, especially when you’re having issues.

When did you install gpu-control?

I can’t find any information on it, so why did you install it?

Please notice the information from inxi is important for trying to help but also for other folks with a similar problem. They can now compare their system with yours and decide if the solution we may find for you can also apply for them.

nvidia-settings is part of the Manjaro distribution so it’s fine to use. gpu-control is in the AUR and you had to check what it is to begin with. I had a glance at the single cpp file and it looks like a simple gui wrapper to run nvidia-settings which one could do from the command line. So you don’t need this. The question is though whether there is anything else from the AUR that you have installed. Especially if it is something lower level like a driver or something that would be part of the base system but comes from the AUR?

My normal procedure would be to start with 6.18 and the open linux618-nvidia-open (610). If this isn’t satisfying install in addition kernel 7.1 and linux71-nvdia-open. Moreover I would also install and try out kernel 7.2 and linux72-nvidia-open. (Internet search shows for these new cards one has to use the open kernel modules.)

Btw, could you install vulkan-tools and post the output of vulkaninfo --summary to check if it is configured to use Nvidia’s proprietary Vulkan driver? (This could have a measurable impact on gaming performance.)

2 Likes

Thank you.

Changing to 610: sorry I feel a bit stupid but I do not know how to reinstall the driver 610.

sudo pacman -S linux618-nvidia-open
resolving dependencies...
looking for conflicting packages...
:: nvidia-utils-610.43.02-2 and nvidia-580xx-utils-580.159.04-1 are in conflict (nvidia-libgl). Remove nvidia-580xx-utils? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-580xx-utils breaks dependency 'nvidia-580xx-utils=580.159.04' required by linux612-nvidia-580xx-open
:: removing nvidia-580xx-utils breaks dependency 'nvidia-580xx-utils=580.159.04' required by linux618-nvidia-580xx-open
:: removing nvidia-580xx-utils breaks dependency 'nvidia-580xx-utils=580.159.04' required by linux71-nvidia-580xx-open
:: removing nvidia-580xx-utils breaks dependency 'nvidia-utils=580.159.04' required by nvidia-580xx-settings

Vulkan: I do not know anything about Vulkan yet but here is the current status .

> vulkaninfo --summary

==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.350


Instance Extensions: count = 27
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_layer_settings                  : extension revision 2
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_maintenance1            : extension revision 1
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 4
--------------------------
VK_LAYER_MESA_anti_lag      Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select Linux device selection layer                                 1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer                                         1.4.312  version 1
VK_LAYER_NV_present         NVIDIA GR2608 layer                                          1.4.312  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.312
	driverVersion      = 580.159.4.0
	vendorID           = 0x10de
	deviceID           = 0x2d83
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce RTX 5050
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 580.159.04
	conformanceVersion = 1.4.1.3
	deviceUUID         = 273b79a8-2643-1579-c967-7e25a41c68d0
	driverUUID         = c7d8a05e-be16-5883-a818-6d61bf0812b6

Looks like one can’t have different nvidia driver versions for different kernels because the driver package depends on the nvidia-utils package which isn’t per kernel. So to install the new driver version you have to install it for each of your kernels at once. Install nvidia-settings, too. Perhaps it will be easier to use the pamac gui for this? I would remove 6.12 since you have 6.18.

This is the right entry, all good.

I was able to install the driver as follows by trial and error (I may have searched the wrong way into pamac but did not clearly decide what to apply).

nvidia-driver-assistant

indicated that I should install linux72-nvidia-open that does not exist.

sudo pacman -S linux71-nvidia-open

And I did eliminate the kernel 7.2 that is apparently not ready yet.

Solved for the driver and kernel, at least I have a complete installation running with kernel 7.1 and driver 610.

I will test a bit, it is still slow and showing a low fps as compared to last week’s situation.
I do not know if there is something with vulkan as discussed above?

vulkaninfo --summary 
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.350


Instance Extensions: count = 27
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_layer_settings                  : extension revision 2
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_maintenance1            : extension revision 1
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 4
--------------------------
VK_LAYER_MESA_anti_lag      Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select Linux device selection layer                                 1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer                                         1.4.341  version 1
VK_LAYER_NV_present         NVIDIA Presentation Layer                                    1.4.341  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.341
	driverVersion      = 610.43.2.0
	vendorID           = 0x10de
	deviceID           = 0x2d83
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce RTX 5050
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 610.43.02
	conformanceVersion = 1.4.3.3
	deviceUUID         = 273b79a8-2643-1579-c967-7e25a41c68d0
	driverUUID         = 2fcde862-7b88-5df8-8c98-ae7c26fb8f33

Makes sense - the driver is in the testing and unstable branch. You may consider to switch branches, see https://wiki.manjaro.org/index.php/Switching_Branches

This is all good. I think it’s likely one needs the latest kernel.

1 Like

I feel that there is something wrong still.
I have a contradicting information with driver 580 which is l apparently also active.

  • nvidia-smi confirms the use of driver 610/open
  • pamac does not help much, I do not understand what can be installed and/or is missing as there are few proposals with the reference “610”, while I would supress others with reference “580”
  • manjaro-setting-manager still shows that I cannot remove as the suppression of libxnvctrl-580xx breaks necessary dependencies of libxnvctrl for xfce4-sensors-plugin