[Stable Update] 2023-02-20 - Kernels, GNOME, NetworkManager, KDE Frameworks, Firefox

After last update in stable branch I started having issues with windows not getting properly focused. I clicked on the title bar, any other spot of the window, nothing really worked but swapping windows with Alt+Tab. In worst scenarios I had to close the window and open it again.
I hope this gets fixed soon. Im using Manjaro Gnome.

3 Likes

Hallo miteinander, hello everybody

pamac upgrade -a
Vorbereitung...
Synchronisiere Paketdatenbanken...
https://aur.manjaro.org/packages-meta-ext-v1.json.gz: Nicht akzeptables TLS-Zertifikat
Fehler beim Synchronisieren der AUR-Datenbank

Zertifikat Serverseitig abgelaufen?
Certificate expired on Server?
I tried:
pamac update --force-refresh

No success. Any clues?

Greetings
CC

Always try to search a minimum before “reporting issues”. You’ll find MANY threads about that.

2 Likes

I know, but if a Serverside Certificate runs out, then nobody should post it here? OK. Next time i remember.
I thought someone from the Manjaro-Team could find it useful to know there is a certificate to renew.

  • Sorry if i was wrong.

In the meantime everything is ok with the certificate again. So who cares anymore.

You didn’t click, and read the threads in the search I linked, did you? The issue is not that a certificate expired. Click, and read if you want to know more, too much off topic already in this thread. It has been multiple month now so you’ll find A LOT of threads about it.

1 Like

3 posts were merged into an existing topic: GNOME still reports 43.3 and not 43.4

This solved my infinite login loop on xfce4. Thanks aki42 !
Can I ask how you identified that libxfce4ui-devel was the issue ? Always something to learn…

In Element Desktop 1.8, all was working well, whereas Element Desktop 1.10 and 1.11 both forget my login information.

In addition, Element crashes when I begin typing a message in the new message field. This causes the login information to be forgotten, requiring a new login.

These bugs make Element Desktop 1.10+ unusable for me. Is this a known bug/regression?

There’s a bug report similar to what you are describing, but it is marked as “due date” and “due in version” undecided for now. FS#77258 : [element-desktop] crashes with error

After update keyboard layout switching in GNOME leads to input focus being lost. Downgrading mutter package to 43.2-2 helps.

I just pushed 43.3-2 with the fix.

Just a heads up - the most recent LTS kernel 6.1.12-1 screws up the driver for some Logitech mice hence scrolling experience becomes horrid. More info:

Changing audio volume using e.g. shortcut keys on the keyboard works for built-in speakers, but not for my Bluetooth speaker (Harman-Kardon Onyx Studio 7) anymore. The slider OSD shows up as usual, but the volume doesn’t change on the device. Any tips?

Edit: I’m going to try this today (with pipewire):

Do you use Easy Effects? In case you do: you should never select Easy Effects as the default output device. I stumbled upon somewhat similar issue just recently.

More info:

1 Like

If anybody else notices that while playing some FLAC files, there are momentary pauses during the playback with VLC 3.0.18, that’s a know bug that was fixed and the fix should be in VLC 3.0.19…
More info here: “FLAC skipping on section” bug report

After this update I’m having freezes with kernel 6.1 on a HP ProBook 445G8 (Ryzen 5 5600U). Kernel 5.19 works fine so far.

With an Acer SwiftX-SFX14 I’m having BT issues. When on battery or after suspend the BT controller stops working. In a previous update I had a similar issue wirh 6.1 kernel, but adding an exception using TLPUI solved it at the time. Now the issue is present with kernel 6.1 or 5.19 and adding the exception for the BT controller in TLPUI does nothing. The only way to bring the BT controller back is a reboot.

System:
  Host: SwiftX-SF14 Kernel: 5.15.94-1-MANJARO arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.26.5 Distro: Manjaro Linux
Machine:
  Type: Laptop System: Acer product: Swift SFX14-41G v: V1.04
    serial: <superuser required>
  Mobo: CZ model: Orion_CA v: V1.04 serial: <superuser required>
    UEFI: Insyde v: 1.04 date: 08/06/2021
Battery:
  ID-1: BAT1 charge: 50.5 Wh (100.0%) condition: 50.5/58.8 Wh (85.9%)
CPU:
  Info: 8-core AMD Ryzen 7 5800U with Radeon Graphics [MT MCP] speed (MHz):
    avg: 1711 min/max: 1600/1900
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel
  Device-2: Quanta HD User Facing type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.7 driver: X: loaded: amdgpu
    unloaded: modesetting dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.42 5.15.94-1-MANJARO)
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
Drives:
  Local Storage: total: 953.87 GiB used: 74.67 GiB (7.8%)
Info:
  Processes: 349 Uptime: 10m Memory: 14.99 GiB used: 2.49 GiB (16.6%)
  Shell: Zsh inxi: 3.3.25

Here’s the dmesg output with the error:

[    3.657340] Bluetooth: hci0: Waiting for firmware download to complete
[    3.658331] Bluetooth: hci0: Firmware loaded in 1395452 usecs
[    3.658415] Bluetooth: hci0: Waiting for device to boot
[    3.673613] Bluetooth: hci0: Device booted in 14869 usecs
[    3.673887] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[    3.679483] Bluetooth: hci0: Applying Intel DDC parameters completed
[    3.688738] Bluetooth: hci0: Firmware revision 0.3 build 15 week 45 2022
[    3.857098] NET: Registered PF_ALG protocol family
[    6.793192] wlp2s0: authenticate with c4:41:1e:4a:bf:cf
[    6.800240] wlp2s0: send auth to c4:41:1e:4a:bf:cf (try 1/3)
[    6.828295] wlp2s0: authenticated
[    6.832120] wlp2s0: associate with c4:41:1e:4a:bf:cf (try 1/3)
[    6.838290] wlp2s0: RX AssocResp from c4:41:1e:4a:bf:cf (capab=0x411 status=0 aid=21)
[    6.866240] wlp2s0: associated
[    6.996784] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   17.972434] acpi AMDI0010:03: Already enumerated
[   32.569512] systemd-journald[367]: Time jumped backwards, rotating.
[   73.214942] input: M720 Triathlon Keyboard as /devices/virtual/misc/uhid/0005:046D:B015.0002/input/input17
[   73.215131] input: M720 Triathlon Mouse as /devices/virtual/misc/uhid/0005:046D:B015.0002/input/input18
[   73.215341] hid-generic 0005:046D:B015.0002: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [M720 Triathlon] on 48:68:4a:cb:ac:ef
[   76.406948] input: M720 Triathlon Keyboard as /devices/virtual/misc/uhid/0005:046D:B015.0003/input/input20
[   76.407075] input: M720 Triathlon Mouse as /devices/virtual/misc/uhid/0005:046D:B015.0003/input/input21
[   76.407163] hid-generic 0005:046D:B015.0003: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [M720 Triathlon] on 48:68:4a:cb:ac:ef
[   80.272409] Bluetooth: RFCOMM TTY layer initialized
[   80.272418] Bluetooth: RFCOMM socket layer initialized
[   80.272423] Bluetooth: RFCOMM ver 1.11
[  661.948870] usb 1-3: reset high-speed USB device number 2 using xhci_hcd
[  662.250829] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[  678.115166] Bluetooth: hci0: command 0x0406 tx timeout
[  685.155176] Bluetooth: hci0: command 0x0c03 tx timeout

The BT controller is the following:

Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth

A post was split to a new topic: Strange error while updating

The certificates are valid. We even switched to the official LetsEncrypt CDN77 provides. The actual issue is OCSP signing with sha1sums, which is not recommended anymore:

Simon B, [27.02.23 15:33]
it is funny, wget throws the same error where as curl works fine

Simon B, [27.02.23 15:58]
❯ openssl s_client -connect aur.manjaro.org:443 2>&1 < /dev/null | sed -n '/-----BEGIN/,/-----END/p' > acm.pem
❯ openssl s_client -connect aur.manjaro.org:443 -showcerts </dev/null 2>/dev/null > chain.pembundle
❯ openssl x509 -noout -ocsp_uri -in acm.pem
http://r3.o.lencr.org
❯ openssl ocsp -issuer chain.pembundle -cert acm.pem -text -url $(openssl x509 -noout -ocsp_uri -in acm.pem)
OCSP Request Data:
    Version: 1 (0x0)
    Requestor List:
        Certificate ID:
          Hash Algorithm: sha1
          Issuer Name Hash: 48DAC9A0FB2BD32D4FF0DE68D2F567B735F9B3C4
          Issuer Key Hash: C257C8A3E9D3C48E991D792814211B21F214FA78
          Serial Number: 04D5F8629C5F36E95639A4888DE7EEF5ACEC
    Request Extensions:
        OCSP Nonce: 
            04106AA116A174204D99F734376D1C4BF611
Responder Error: unauthorized (6)
❯

Simon B, [27.02.23 16:00]
problem seems to be that they use SHA1 instead of SHA-256

Simon B, [27.02.23 16:09]
@philmmjr so it seems CDN77 needs to change the settings on their ocsp server

Simon B, [27.02.23 16:09]
| 2022-06-01 | 7.1.3.2.1 | CAs MUST NOT sign OCSP responses using the SHA-1 hash algorithm. |

Simon B, [27.02.23 16:10]
https://cabforum.org/2022/01/26/ballot-sc53-sunset-for-sha-1-ocsp-signing/

We reported that issue to CDN77 and wait for a fix. Also not always the issue will happen on your end. You can try it again at a later timeslot. Most likely it will download the AUR database at some point.

1 Like

I found another problem with this update. When connecting to 5GHz APs the WiFi I noticed a lot of dropped packets and delays, at first I tought it was my Internet service but the same happens with other 5GHz APs. I looked at the kernels messages and found this:

[75361.101632] iwlwifi 0000:02:00.0: Queue 5 is stuck 247 216
[75361.102086] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x0.
[75361.102394] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[75361.102396] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[75361.102398] iwlwifi 0000:02:00.0: Loaded firmware version: 66.f1c864e0.0 cc-a0-66.ucode
[75361.102400] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[75361.102403] iwlwifi 0000:02:00.0: 0x0000A2F0 | trm_hw_status0
[75361.102404] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[75361.102406] iwlwifi 0000:02:00.0: 0x004FAA46 | branchlink2
[75361.102407] iwlwifi 0000:02:00.0: 0x004F13DE | interruptlink1
[75361.102408] iwlwifi 0000:02:00.0: 0x004F13DE | interruptlink2
[75361.102409] iwlwifi 0000:02:00.0: 0x004E8BC0 | data1
[75361.102410] iwlwifi 0000:02:00.0: 0x01000000 | data2
[75361.102411] iwlwifi 0000:02:00.0: 0x00000000 | data3
[75361.102412] iwlwifi 0000:02:00.0: 0x15403DA4 | beacon time
[75361.102414] iwlwifi 0000:02:00.0: 0x804A125C | tsf low
[75361.102415] iwlwifi 0000:02:00.0: 0x00000062 | tsf hi
[75361.102416] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[75361.102417] iwlwifi 0000:02:00.0: 0x99C9E0A4 | time gp2
[75361.102418] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
[75361.102419] iwlwifi 0000:02:00.0: 0x00000042 | uCode version major
[75361.102420] iwlwifi 0000:02:00.0: 0xF1C864E0 | uCode version minor
[75361.102422] iwlwifi 0000:02:00.0: 0x00000340 | hw version
[75361.102423] iwlwifi 0000:02:00.0: 0x00C89000 | board version
[75361.102424] iwlwifi 0000:02:00.0: 0x80BCFD04 | hcmd
[75361.102425] iwlwifi 0000:02:00.0: 0x20028000 | isr0
[75361.102426] iwlwifi 0000:02:00.0: 0x00400000 | isr1
[75361.102427] iwlwifi 0000:02:00.0: 0x08F00002 | isr2
[75361.102428] iwlwifi 0000:02:00.0: 0x00C3428C | isr3
[75361.102429] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[75361.102430] iwlwifi 0000:02:00.0: 0x0089019C | last cmd Id
[75361.102431] iwlwifi 0000:02:00.0: 0x004E8BC0 | wait_event
[75361.102432] iwlwifi 0000:02:00.0: 0x000000D4 | l2p_control
[75361.102433] iwlwifi 0000:02:00.0: 0x00000000 | l2p_duration
[75361.102435] iwlwifi 0000:02:00.0: 0x00000007 | l2p_mhvalid
[75361.102436] iwlwifi 0000:02:00.0: 0x00000081 | l2p_addr_match
[75361.102437] iwlwifi 0000:02:00.0: 0x00000009 | lmpm_pmg_sel
[75361.102438] iwlwifi 0000:02:00.0: 0x00000000 | timestamp
[75361.102439] iwlwifi 0000:02:00.0: 0x0000C80C | flow_handler
[75361.102585] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[75361.102586] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 7
[75361.102588] iwlwifi 0000:02:00.0: 0x20000066 | NMI_INTERRUPT_HOST
[75361.102590] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[75361.102591] iwlwifi 0000:02:00.0: 0x80455A96 | umac branchlink2
[75361.102592] iwlwifi 0000:02:00.0: 0x80473F9A | umac interruptlink1
[75361.102593] iwlwifi 0000:02:00.0: 0x80473F9A | umac interruptlink2
[75361.102594] iwlwifi 0000:02:00.0: 0x01000000 | umac data1
[75361.102595] iwlwifi 0000:02:00.0: 0x80473F9A | umac data2
[75361.102596] iwlwifi 0000:02:00.0: 0x00000000 | umac data3
[75361.102597] iwlwifi 0000:02:00.0: 0x00000042 | umac major
[75361.102598] iwlwifi 0000:02:00.0: 0xF1C864E0 | umac minor
[75361.102599] iwlwifi 0000:02:00.0: 0x99C9E0A2 | frame pointer
[75361.102601] iwlwifi 0000:02:00.0: 0xC0886260 | stack pointer
[75361.102602] iwlwifi 0000:02:00.0: 0x0089019C | last host cmd
[75361.102603] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[75361.102729] iwlwifi 0000:02:00.0: IML/ROM dump:
[75361.102730] iwlwifi 0000:02:00.0: 0x00000003 | IML/ROM error/state
[75361.102853] iwlwifi 0000:02:00.0: 0x00005CBD | IML/ROM data1
[75361.102921] iwlwifi 0000:02:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[75361.102986] iwlwifi 0000:02:00.0: Fseq Registers:
[75361.103047] iwlwifi 0000:02:00.0: 0x60000000 | FSEQ_ERROR_CODE
[75361.103109] iwlwifi 0000:02:00.0: 0x80290021 | FSEQ_TOP_INIT_VERSION
[75361.103172] iwlwifi 0000:02:00.0: 0x00050008 | FSEQ_CNVIO_INIT_VERSION
[75361.103229] iwlwifi 0000:02:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[75361.103286] iwlwifi 0000:02:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[75361.103349] iwlwifi 0000:02:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[75361.103405] iwlwifi 0000:02:00.0: 0x00100530 | FSEQ_CNVI_ID
[75361.103462] iwlwifi 0000:02:00.0: 0x00000532 | FSEQ_CNVR_ID
[75361.103521] iwlwifi 0000:02:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[75361.103583] iwlwifi 0000:02:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[75361.103642] iwlwifi 0000:02:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[75361.103708] iwlwifi 0000:02:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[75361.103996] iwlwifi 0000:02:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[75361.104001] ieee80211 phy0: Hardware restart was requested
[75384.141482] iwlwifi 0000:02:00.0: Queue 2 is stuck 107 95
[75384.141802] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x0.
[75384.142054] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[75384.142056] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[75384.142059] iwlwifi 0000:02:00.0: Loaded firmware version: 66.f1c864e0.0 cc-a0-66.ucode
[75384.142062] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[75384.142066] iwlwifi 0000:02:00.0: 0x008032F0 | trm_hw_status0
[75384.142068] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[75384.142070] iwlwifi 0000:02:00.0: 0x004FAA46 | branchlink2
[75384.142071] iwlwifi 0000:02:00.0: 0x00009E12 | interruptlink1
[75384.142073] iwlwifi 0000:02:00.0: 0x00009E12 | interruptlink2
[75384.142074] iwlwifi 0000:02:00.0: 0x00007D34 | data1
[75384.142076] iwlwifi 0000:02:00.0: 0x01000000 | data2
[75384.142078] iwlwifi 0000:02:00.0: 0x00000000 | data3
[75384.142079] iwlwifi 0000:02:00.0: 0x35C03E62 | beacon time
[75384.142081] iwlwifi 0000:02:00.0: 0x81A9A1A0 | tsf low
[75384.142083] iwlwifi 0000:02:00.0: 0x00000062 | tsf hi
[75384.142084] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[75384.142086] iwlwifi 0000:02:00.0: 0x01532109 | time gp2
[75384.142087] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
[75384.142089] iwlwifi 0000:02:00.0: 0x00000042 | uCode version major
[75384.142091] iwlwifi 0000:02:00.0: 0xF1C864E0 | uCode version minor
[75384.142092] iwlwifi 0000:02:00.0: 0x00000340 | hw version
[75384.142094] iwlwifi 0000:02:00.0: 0x00C89000 | board version
[75384.142096] iwlwifi 0000:02:00.0: 0x026B001C | hcmd
[75384.142097] iwlwifi 0000:02:00.0: 0x80020000 | isr0
[75384.142099] iwlwifi 0000:02:00.0: 0x00400000 | isr1
[75384.142100] iwlwifi 0000:02:00.0: 0x08F00002 | isr2
[75384.142102] iwlwifi 0000:02:00.0: 0x00C3408D | isr3
[75384.142103] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[75384.142105] iwlwifi 0000:02:00.0: 0x00D2019C | last cmd Id
[75384.142106] iwlwifi 0000:02:00.0: 0x00007D34 | wait_event
[75384.142108] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
[75384.142109] iwlwifi 0000:02:00.0: 0x00000020 | l2p_duration
[75384.142111] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[75384.142112] iwlwifi 0000:02:00.0: 0x000000CE | l2p_addr_match
[75384.142114] iwlwifi 0000:02:00.0: 0x00000009 | lmpm_pmg_sel
[75384.142116] iwlwifi 0000:02:00.0: 0x00000000 | timestamp
[75384.142117] iwlwifi 0000:02:00.0: 0x0000A8E8 | flow_handler
[75384.142262] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[75384.142263] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 7
[75384.142265] iwlwifi 0000:02:00.0: 0x20000066 | NMI_INTERRUPT_HOST
[75384.142267] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[75384.142269] iwlwifi 0000:02:00.0: 0x80455A96 | umac branchlink2
[75384.142271] iwlwifi 0000:02:00.0: 0x80473F9A | umac interruptlink1
[75384.142272] iwlwifi 0000:02:00.0: 0x80473F9A | umac interruptlink2
[75384.142274] iwlwifi 0000:02:00.0: 0x01000000 | umac data1
[75384.142275] iwlwifi 0000:02:00.0: 0x80473F9A | umac data2
[75384.142277] iwlwifi 0000:02:00.0: 0x00000000 | umac data3
[75384.142278] iwlwifi 0000:02:00.0: 0x00000042 | umac major
[75384.142280] iwlwifi 0000:02:00.0: 0xF1C864E0 | umac minor
[75384.142281] iwlwifi 0000:02:00.0: 0x01532106 | frame pointer
[75384.142283] iwlwifi 0000:02:00.0: 0xC0886260 | stack pointer
[75384.142285] iwlwifi 0000:02:00.0: 0x00D2019C | last host cmd
[75384.142286] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[75384.142409] iwlwifi 0000:02:00.0: IML/ROM dump:
[75384.142411] iwlwifi 0000:02:00.0: 0x00000003 | IML/ROM error/state
[75384.142538] iwlwifi 0000:02:00.0: 0x00005CC7 | IML/ROM data1
[75384.142607] iwlwifi 0000:02:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[75384.142728] iwlwifi 0000:02:00.0: Fseq Registers:
[75384.142785] iwlwifi 0000:02:00.0: 0x60000000 | FSEQ_ERROR_CODE
[75384.142850] iwlwifi 0000:02:00.0: 0x80290021 | FSEQ_TOP_INIT_VERSION
[75384.142909] iwlwifi 0000:02:00.0: 0x00050008 | FSEQ_CNVIO_INIT_VERSION
[75384.142970] iwlwifi 0000:02:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[75384.143032] iwlwifi 0000:02:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[75384.143094] iwlwifi 0000:02:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[75384.143157] iwlwifi 0000:02:00.0: 0x00100530 | FSEQ_CNVI_ID
[75384.143220] iwlwifi 0000:02:00.0: 0x00000532 | FSEQ_CNVR_ID
[75384.143283] iwlwifi 0000:02:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[75384.143348] iwlwifi 0000:02:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[75384.143414] iwlwifi 0000:02:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[75384.143479] iwlwifi 0000:02:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[75384.143786] iwlwifi 0000:02:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[75384.143791] ieee80211 phy0: Hardware restart was requested

Connecting to the 2.4GHz band does not give me these errors. This happens with 5.19 and 6.1 kernels. I did not have this problem prior to this update. I also noticed it happens when on battery.

As per my previous post I also have problems with the Bluetooth adapter, both WiFi and BT are on the same Intel AX200 card.

02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth

We decided to backport Kernels and Firmware to the stable branch as well.

8 Likes