Is video hardware decoding on firefox possible now with this new driver? What about enabling Wayland now, it is viable on NVIDIA with this new driver? Thanks for the awesome job.
1 Like
See:
https://www.phoronix.com/scan.php?page=news_item&px=XWayland-21.1.2-RC
See Chapter 38. OpenGL and Vulkan on Xwayland in the README:
cat /usr/share/doc/nvidia/README | less -p "38A. OVERVIEW"
There are quite a few issues and we don’t have all the new packages yet:
I’ll check it out. Thanks.
All went fine except nvidia-opencl : I got this message when compiling one of darktable opencl modules :
ptxas fatal : Unresolved extern function ‘__nv_fast_log2f’
Look here: How to deal with ptxas : fatal error : Unresolved extern function 'cudaGetParameterBuffer' - CUDA Programming and Performance - NVIDIA Developer Forums. Maybe post about your issue in their forum.
1 Like
Got an error related to Kwallet, but after reboot, everything seems fine so far.
Kernel 5.12 and 5.13 still don’t properly support resume from sleep with AMD Ryzen 4000 laptops, sadly.
It’s unbelievable that they don’t manage to fix that on kernels after 5.10 (which was affected until ~5.10.30 but works now).
I’m getting more connection drops and wifi instability on my intel wireless AC card with this update that seems to be unrelated to the beacon timing issue that’s been around for 2 years (here’s the bugzilla thread for that one if you’re interested)
(chipset is Intel Wireless AC 9260)
I noticed it was different because the dmesg logs had a new error I hadn’t seen before. This only appears to happen on Linux 5.13, I keep the latest LTS installed as a backup and haven’t gotten these errors running 5.11 so far.
Here’s the dmesg output:
sudo dmesg | grep -i iwl
[ 3.200238] iwlwifi 0000:06:00.0: enabling device (0000 -> 0002)
[ 3.227216] iwlwifi 0000:06:00.0: WRT: Overriding region id 0
[ 3.227220] iwlwifi 0000:06:00.0: WRT: Overriding region id 1
[ 3.227222] iwlwifi 0000:06:00.0: WRT: Overriding region id 2
[ 3.227224] iwlwifi 0000:06:00.0: WRT: Overriding region id 3
[ 3.227225] iwlwifi 0000:06:00.0: WRT: Overriding region id 4
[ 3.227227] iwlwifi 0000:06:00.0: WRT: Overriding region id 6
[ 3.227228] iwlwifi 0000:06:00.0: WRT: Overriding region id 8
[ 3.227229] iwlwifi 0000:06:00.0: WRT: Overriding region id 9
[ 3.227231] iwlwifi 0000:06:00.0: WRT: Overriding region id 10
[ 3.227232] iwlwifi 0000:06:00.0: WRT: Overriding region id 11
[ 3.227233] iwlwifi 0000:06:00.0: WRT: Overriding region id 15
[ 3.227235] iwlwifi 0000:06:00.0: WRT: Overriding region id 16
[ 3.227236] iwlwifi 0000:06:00.0: WRT: Overriding region id 18
[ 3.227237] iwlwifi 0000:06:00.0: WRT: Overriding region id 19
[ 3.227239] iwlwifi 0000:06:00.0: WRT: Overriding region id 20
[ 3.227240] iwlwifi 0000:06:00.0: WRT: Overriding region id 21
[ 3.227241] iwlwifi 0000:06:00.0: WRT: Overriding region id 28
[ 3.227626] iwlwifi 0000:06:00.0: loaded firmware version 46.6b541b68.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[ 3.509977] iwlwifi 0000:06:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[ 3.557640] iwlwifi 0000:06:00.0: base HW address: 0c:dd:24:82:fa:55
[ 3.624777] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 3.629316] iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0
[ 111.763009] iwlwifi 0000:06:00.0: reached 10 old SN frames from ac:ec:80:31:90:65 on queue 2, stopping BA session on TID 0
[ 141.600010] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600010] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600012] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600014] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600014] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600016] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600016] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600016] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600018] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600018] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600020] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600021] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600023] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600024] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600028] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.600032] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601534] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601537] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601537] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601538] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601539] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601540] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601541] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601541] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601542] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601542] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601542] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601543] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601544] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601544] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601546] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.601547] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603051] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603052] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603054] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603053] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603055] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603056] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603057] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603057] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603058] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603060] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603060] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603060] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603061] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603064] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603066] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.603068] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604535] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604535] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604537] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604537] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604538] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604538] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604539] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604539] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604540] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604541] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604542] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604542] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604543] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604545] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604547] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 141.604549] iwlwifi 0000:06:00.0: expected hw-decrypted unicast frame for station
[ 148.262101] iwlwifi 0000:06:00.0: Unhandled alg: 0xc0400707Update process was smooth as usual, but after the first reboot KWallet keeps nagging me for some password, and as a result Plasma won’t automatically connect to any of my saved WiFi networks. Rebooted again and KWallet got silenced the next time I logged in to Plasma. Basically, I got a similar experience to @Dino-Fossil’s post, except that I don’t use a Ryzen 4000 laptop and don’t get the other unrelated issue:
Also, if you use KDE and have been annoyed by the glitchy fade effects since Plasma 5.22.0, then this update is for you. I can confirm the fade effects got fixed on my install once I re-enabled the Dialog Parent and Dim Screen for Administrator Mode effects in System Settings.
Now here I am waiting for a similar bug, this time with Yakuake, to be fixed…
I noticed this message right before logging in:
thermal thermal_zone9: failed to read out thermal zone (-61)
The dmesg log shows other issues, potentially older:
[ 6.423257] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[ 6.423271] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
FYI resume from sleep on Renoir/Cezanne laptops is supposed to be fixed in 5.14. Take a look at this issue: Ryzen 4700U failing to enter suspend/modern-standby correctly (#1230) · Issues · drm / amd · GitLab
@philm I found this:
“With the absolutely huge NVIDIA 470 driver release now out the door, NVIDIA has just put up a fresh release of their open source NVAPI interface.
For those who haven’t seen us report on it previously here’s what it is: “NVAPI is NVIDIA Corporation’s core software development kit that allows access to NVIDIA GPUs and drivers on all Windows platforms. NVAPI provides support for categories of operations that range beyond the scope of those found in familiar graphics APIs such as DirectX and OpenGL.”
What’s the use for Linux? NVIDIA say the version of nvapi.h that’s now under the MIT license helps to enable “open source re-implementations of NVAPI for Windows emulation environments”. The updated release adds in lots more Functions, Enums and Structures for developers to use. For us normal users, it doesn’t mean too much but for developers (on projects like Wine, Proton, DXVK, VKD3D-Proton and so on) it can help get more features hooked up for running Windows games on Linux with compatibility layers.”
Nah, there’s no difference when using wayland for me. It still doesn’t render the top 1/3rd of my right screen and you still can’t chose which screen is your primary screen.
That’s nice to see, but I’m not holding my breath yet.
While there might be good reasons for it, they still broke resume/suspend for a not-so-small subset of Linux users before actually having a working solution in place and are taking ages to fix it again…
The whole thread linked by @matt17br reads a bit depressing, honestly.
Yeah, they are working on getting stupid modern standby to work, but in the process broke “normal” standby for AMD Renoir and Cezanne. With a lot of luck, it might work in 5.14, but it could well be 5.16.
Great job, guys!
In the meantime, you can try to either build your own patched kernel, abandon use of standby or keep on using 5.10, I guess.
Another nvidia beta driver update. Awesome!
Well, I tried it with kde wayland session and it went pretty much OK. Firefox with GPU acceleration crashed once, but it’s working good after that. MPV player doesn’t render and an old opengl game stops working. But the desktop is fast and vulkan games are buttery smooth. A good start, I guess. But I’m going to stick with X11 for the time being. 
I suppose I should have linked to the specific sub-thread that tracks the patches needed to fix S3-sleep on recent AMDGPUs, and in particular these replies by an AMD staff member
I would say the discussion under the linked issue is actually pretty reassuring @Dino-Fossil! Perhaps you might have just missed the most relevant bits in that thread.
1 Like
@DaviKar Are you talking about KDE? Wayland is not supposed to support the context of a ‘primary screen’. I was surprised about that too.
But it is possible to set a primary display in Gnome Wayland session.
How did you manage to access the wayland session in kde? I tried installing the wayland-session but it doesn’t even load.