You are not logged in.
Pages: 1
I have strictly followed the instructions in the Arch Linux NVIDIA wiki page. I installed the following packages: nvidia-open lib32-nvidia-utils nvidia-utils. I didn't install the nvidia proprietary driver as the wiki suggests that Turing and newer (which of course includes RTX 5060) should install nvidia-open.
The information below should explain the hardware I am using. Also, nvidia-smi can show the right information.
❯ lspci -k -d ::03xx
04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)
DeviceName: Onboard VGA
Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family
Kernel driver in use: ast
Kernel modules: ast
31:00.0 VGA compatible controller: NVIDIA Corporation GB206 [GeForce RTX 5060] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 41c1
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
❯ sudo pacman -Q nvidia
error: package 'nvidia' was not found
❯ sudo pacman -Q nvidia-open
nvidia-open 575.64.05-1
❯ sudo pacman -Q lib32-nvidia-utils
lib32-nvidia-utils 575.64.05-1
❯ sudo pacman -Q nvidia-utils
nvidia-utils 575.64.05-1I am currently using Wayland and Gnome, which is default to Arch Linux. After installing the drivers, I am able to toggle HDR and 160Hz in gnome settings. But the problem here is that even though the HDR toggle in the gnome settings GUI is on, the display still doesn't actually display HDR content.
In order to verify whether the HDR is correctly enabled or not, I used the following commands:
❯ nvidia-settings -q CurrentHDRStatenvidia-settings -q CurrentHDRState
ERROR: Error parsing query 'CurrentHDRStatenvidia-settings' (Unrecognized attribute name).
❯ nvidia-settings -q CurrentHDRState
ERROR: Error parsing query 'CurrentHDRState' (Unrecognized attribute name).
❯ xrandr --verbose | grep -i bpc
❯ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
❯ uname -r
6.15.7-arch1-1
❯ nvidia-settings -q all | grep -i hdr
ERROR: Error while querying valid values for attribute 'OperatingSystem' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying valid values for attribute 'PCIEMaxLinkSpeed' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying valid values for attribute 'PCIECurrentLinkSpeed' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying valid values for attribute 'GPUCurrentPerfLevel' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying valid values for attribute 'GPUAdaptiveClockState' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCStatus' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCConfiguration' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying valid values for attribute 'ECCDefaultConfiguration' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCSingleBitErrors' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCDoubleBitErrors' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCAggregateSingleBitErrors' on astraTZ:0[gpu:0] (Operation not supported).
ERROR: Error while querying attribute 'ECCAggregateDoubleBitErrors' on astraTZ:0[gpu:0] (Operation not supported).In addition to the command line output, I can tell if HDR is on just by my naked eye because I am using a miniLED display which can support up to 1600nits for HDR content. When I connect the display to my MacBook and enable HDR. The desktop will become very very bright, which differs greatly enough for naked eye to tell. I tried this monitor on another machine with Debian installed and HDR on, the effect is the same as on the MacBook. But on my ArchLinux machine, I don't think the HDR is "actually" turned on.
Also, HDR options is not available on Chrome, Firefox, Brave, Zen when watching YouTube videos that supports HDR. When using mpv to play HDR content, HDR is also not enabled (I have used the correct command line parameters. press i when playing video can show you the necessary information, including whether HDR is enabled).
So, what should I do?
Offline
Or maybe can anyone tell me if it is safe to just use the .run file provided by Nvidia to install the proprietary driver for RTX 50 series GPU on Arch Linux? It is not recommended in the Arch wiki anyway.
------
update: Don't do it
Last edited by SerSmile628 (2025-07-30 19:46:23)
Offline
That will not make any difference whatsoever on this, unless you're using an actual different driver, in which case properly adjusting the existing PKGBUILDs or using one from the AUR are the better options anyway. Not sure how far HDR in GNOME, is but have you e.g. tested KDE Plasma or so? Also for completeness sake, can you get rid of the onboard chip in the UEFI to ensure it doesn't interfere and add nvidia-drm.modeset=1 to the kernel parameters (the cmdline not the modprobe conf that already is the default anyway) to make sure simpledrm doesn't interfere
Last edited by V1del (2025-07-26 14:00:01)
Offline
After consulting NVIDIA technical support, I have confirmed that:
1. The proprietary driver is not compatible with Blackwell as of July 31, 2025.
2. Obviously enough, nvidia-open cannot support HDR on Gnome+Wayland. Didn't try out KDE Plasma because I am too lazy. But 3060 and the proprietary driver works fine for HDR on Gnome+Wayland.
So the solution for me and everyone who is suffering from all kinds of issue when using Blackwell GPU on Linux is to wait for the proprietary driver support.
Offline
Except proprietary driver support isn't coming, the open driver will be the only one from NVIDIA moving forward. https://developer.nvidia.com/blog/nvidi … l-modules/
Offline
5060 is not supported by nvidia-dkms?
Its time to switch to AMD.
Last edited by ankabo (2025-07-31 08:56:26)
Offline
It's not, but it's supported by nvidia-open-dkms which is the open source variant of nvidia's kernel module (... that still uses the proprietary user space libs for GL/CUDA/Vulkan, but the kernel module is open source) and the one they are actively going to maintain in the future.
Last edited by V1del (2025-07-31 12:29:01)
Offline
Pages: 1