[Stable Update] 2022-02-27 - Kernels, Mesa 21.3.7, Plasma 5.24.2, Frameworks 5.91, Pipewire 0.3.47, Toolchain, Gstreamer 1.20, Nvidia 510.54

Intel AX200 Bluetooth is still broken after this update also. (WIFI part works (tested), but don’t care and not using it, as it’s desktop computer)

https://bugzilla.kernel.org/show_bug.cgi?id=215167

Summary
from inxi:
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 chip-ID: 8087:0029
           class-ID: e001
           Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: N/A

    ~  blueman-manager                                                                                ✔ 
blueman-manager 22.20.43 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 22.20.43 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
    ~  blueman-adapters                                                                               ✔ 
blueman-adapters 22.31.26 ERROR    Adapter:54 __init__  : No adapter(s) found
    ~  bluetoothctl list                                                                              ✔ 
    ~  bluetoothctl show                                                                              ✔ 
No default controller available
    ~  dmesg | grep -iE '(btusb|iwl|blue|ax200|wifi)'                                                                                                ✔ 
[    2.335287] Intel(R) Wireless WiFi driver for Linux
[    2.335330] iwlwifi 0000:27:00.0: enabling device (0000 -> 0002)
[    2.341470] iwlwifi 0000:27:00.0: api flags index 2 larger than supported by driver
[    2.341488] iwlwifi 0000:27:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    2.341731] iwlwifi 0000:27:00.0: loaded firmware version 67.8f59b80b.0 cc-a0-67.ucode op_mode iwlmvm
[    2.683247] iwlwifi 0000:27:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    2.806938] iwlwifi 0000:27:00.0: Detected RF HR B3, rfid=0x10a100
[    2.871940] iwlwifi 0000:27:00.0: base HW address: f8:e4:e3:00:d2:b4
[    2.889905] Bluetooth: Core ver 2.22
[    2.889918] NET: Registered PF_BLUETOOTH protocol family
[    2.889918] Bluetooth: HCI device and connection manager initialized
[    2.889954] Bluetooth: HCI socket layer initialized
[    2.889955] Bluetooth: L2CAP socket layer initialized
[    2.889957] Bluetooth: SCO socket layer initialized
[    3.041784] usbcore: registered new interface driver btusb
[    3.182855] iwlwifi 0000:27:00.0 muninn: renamed from wlan0
[    3.664130] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.664133] Bluetooth: BNEP filters: protocol multicast
[    3.664136] Bluetooth: BNEP socket layer initialized
[    5.048112] Bluetooth: hci0: command 0xfc05 tx timeout
[    5.048112] Bluetooth: hci0: Reading Intel version command failed (-110)

So basically bluetooth devices can’t connect. Because blueman-manager doesn’t find any controllers and doesn’t even start. And it seems I might not be the only one with ax200 problems with recent kernel/firmware/ucode updates – FS#73387 : [linux-firmware] Intel AX210 iwlwifi broken on kernel and firmware upgrade

Made an account to post this.

Plasma Wayland on NVIDIA has broken for me in this update. Just a black screen with blinking cursor. Installed gnome-shell just to test, and wayland works fine on that.

[ 168.525835] [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000600] Failed to allocate NVKMS memory for GEM object

Probably due to my dual NVIDIA GPU setup. I’ll update the post if single GPU fixes it.

Edit: Single GPU fixes it.

Thank you for the heads-up… found it in my update log:

Upgrading glibc (2.33-5 -> 2.35-2)...
/etc/locale.gen installed as /etc/locale.gen.pacnew.
Generating locales...
  en_US.UTF-8... done
  en_CA.UTF-8... done
Generation complete.
Upgrading gcc-libs (11.1.0-3 -> 11.2.0-3)...

Using meld I noticed the pacnew file was the same except for one additional line; resolved with:

$ cd /etc
$ sudo rm locale.gen
$ sudo mv locale.gen.pacnew local.gen
$ sudo mkinitcpio -P
1 Like

Since the last update I have a strange dark stripe on Brave-Browser on the left in my favorite newspaper website. I’m not sure if the error is related to Plasma or Brave. Can not say exactly, but those color probably matches the color of global theming.

Hi! Unable to update. This is the last lines of the update via pamac:
Controllo portachiavi…
Verifico l’integrità dei pacchetti…
Caricamento dei file dei pacchetti…
Controllo conflitti tra file…
Inizializzazione del trasferimento non riuscita.:
file in conflitto:

  • dunst: /usr/bin/dunstify already exists in filesystem (owned by dunstify)

I’ve previously had issues with my AX200 bluetooth (Anyone else experiencing Intel AX200 Bluetooth being disabled in kernel515?), and found after this update that it continues to work… No errors in journal, and my bluetooth devices are still listed in the bluetooth plasmoid. Some thoughts that may be helpful…

  • I am using kde plasma manjaro, and although blueman is listed in pamac, I do not have it installed. Not sure if it’s a requirement for your distro, but perhaps blueman is where the problem lies?
  • I am also still on kernel 5.15 (5.15.25) and have not tried 5.16 kernels yet.

You can either remove dunstify first, then upgrade and then reinstall dunstify or use --overwrite:

sudo pacman -Syyu --overwrite=/usr/bin/dunstify
8 Likes

The forum post says wine 7.2, but the update actually installed wine 7.3-1. Perhaps the description is wrong?

I’m not sure what’s responsible for it, but this update appears to have returned some of the great memory management I was typically experiencing. Over the previous 1-2 updates, I was noticing occasions where Firefox and Steam were using multiple gigs of RAM. Typical “abusers” that are now behaving well are:

  • Firefox… still under 600K after opening/using a few tabs, not 2-3G
  • plasmashell… 300K instead of 600K+
  • Steam… ~400K (if I also add up all the steamwebhelper's) instead of ~1G+

I’ll continue to watch memory usage as the days go by, but even after a fresh reboot my PC was using 3.78 GiB (of 32G) with all apps loaded, whereas previous to this update this was 1.5-2G higher! Awesome improvement :beer:

1 Like

The result of “sudo pamac update”:

Total installed size: -159.9 MB

Apply transaction ? [y/N] y
Checking keyring… [390/390]
Checking integrity… [390/390]
Loading packages files… [390/390]
Checking file conflicts… [390/390]
Error: Failed to commit transaction:
conflicting files:

  • kde-cli-tools: /usr/bin/kde-open already exists in filesystem (owned by kdebase-runtime)
  • kde-cli-tools: /usr/bin/keditfiletype already exists in filesystem (owned by kdebase-runtime)
  • kde-cli-tools: /usr/bin/kioclient already exists in filesystem (owned by kdebase-runtime)
  • kde-cli-tools: /usr/bin/kmimetypefinder already exists in filesystem (owned by kdebase-runtime)
  • kde-cli-tools: /usr/bin/kstart already exists in filesystem (owned by kdebase-runtime)
  • kde-cli-tools: /usr/bin/ksvgtopng already exists in filesystem (owned by kdebase-runtime)

I recall reading something about this in the testing threads… thinking I’d like to install this too (as a preventative measure, since i read it could also impact some steam games) I think I found a newer version in the Core repo, so why not install that instead? 4.4.26-1 vs 4.4.28-2

A post was split to a new topic: Conflict between jack and fluidsynth

While updating I did see several warnings. I am not sure what they mean, but they where:

WARNING: Possible missing firmware for module qla1280
WARNING: Possible missing firmware for module qla2xxx
WARNING: Possible missing firmware for module bfa
WARNING: Possible missing firmware for module qed

I am not sure if I need to do anything here. It does not seem to be affecting the upgrade.

@linux4all Those firmware warning are totally normal. You can ignore those unless you actually have those specific items of hardware in your system.

I’ve just updated and dolphin no longer works.

Launching Dolphin produces a blank window that visually mirrors what was behind it when it launched. Eventually Plasma tells me that it’s not responding and I can kill it. When I run dolphin from the terminal, I get no errors.

1 Like

Thank you ishaanbhimwal, I am glad you said that. What would I need to do if those packages affected my system? I was going to do a search on what those files do.
Thanks for your reply.

Since this update brings Plasma up to version 5.24, this bug started manifesting for me:

My cursor’s colors on Manjaro KDE are all messed up on my Radeon RX 6800.

i can’t see any updates.

Try to refresh database or pacman-mirror in pamac.

1 Like

You can read at beginning of this thread:

" New warnings when building the fallback initcpio - Possibly missing firmware for module: bfa, qed, qla1280, qla2xxx

That’s due to the recent changes to the linux-firmware package. Note these are warnings, not errors. You only need those firmwares if you have Mellanox Spectrum switches, Marvell devices, Qualcomm SoCs, Cavium LiquidIO server adapters, QLogic devices and Broadcom NetXtreme II 10Gb ethernet adapters. if you have that hardware you can install linux-firmware-qlogic to get rid of those warnings. If you do not have that hardware you can safely ignore those warnings.

pamac install linux-firmware-qlogic

:wink: :smiley:

2 Likes