Some Nvidia cards don’t work with the current 465.31 drivers when used with Display Port and/or 4k Monitors. More about the issue at the Nvidia Developer Forum. We recommend to switch to Nouveau driver as needed. If you however need the Nvidia driver, you can get the PKGBUILDs of the 460.73.01 version and build your driver locally with makepkg or use the pre-compiled packages: nvida-utils, dkms and lib32 + precompiled .
Older Issues
OS prober does not run and add other operating systems
Please click the ► at the beginning of this line to view this solution
To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub
We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DOhere for your particular card.
If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:
sudo mhwd -a pci nonfree 0300
If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
For AMD GPU users having a black screen with kernel 5.10
Please click the ► at the beginning of this line to view more info
Due to a bug in the AMD drivers, please try the following first:
For GRUB:
Open a terminal or a TTY
Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
Add amdgpu.dc=0
Save
Execute sudo update-grub and reboot
For systemd-boot:
Open a terminal or a TTY
Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
Add amdgpu.dc=0 to the end of the line options
Save & reboot
For rEFInd:
Open a terminal or a TTY
Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
Find the line: "Boot using default options" "root=
Add amdgpu.dc=0
Save & reboot
Possible 2 Min delay on shutdown with Gnome
Please click the ► at the beginning of this line to view more info
If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:
You get [PKGNAME] warning: directory permissions differ on [Directory name]
followed by:
Filesystem: NNN package MMM
Please click the ► at the beginning of this line to view this solution
The solution:
sudo chmod MMM DirectoryName
Where obviously MMM is the second number you see (the correct one)
The explanation:
Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.
Systemd error message: .slice: Failed to migrate controller cgroups
If you have a similar error message like this:
systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied
… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.
Python 3.9 Requires Rebuilds
Instructions for quickly and easily rebuilding affected AUR packages:
# Install yay
sudo pacman -S --needed --noconfirm yay
# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")
The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem
PAM and PAMBASE got updated, which might prevent you from login
Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.
Typical issue:
For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”
System takes a long time to boot
If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here Update: If you can see the line dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here: systemctl disable cups.service systemctl enable cups.socket
I think I’ve some font problems
With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.
Gnome-shell-extension-pop-shell is currently incompatible with wayland
… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
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.
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: 0xc0400707
Update 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.
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
“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.
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 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.
