Intel WiFi card randomly dropped to 100B/s download speeds.

Nova · 2025-11-14 05:56:15

I've been trying to fix this issue for a couple of days now. Basically, earlier this week my internet speeds randomly dropped and have been hovering at around 80-120B/s ever since. After working with ChatGPT for an hour (Yes I know ChatGPT can give wrong information and AI bad and whatever, but its responses are nearly instant and in this case it did manage to find a somewhat working solution), I was able to figure out that by adding

options iwlwifi 11n_disable=1
options iwlwifi power_save=0

to /etc/modprobe.d/iwlwifi.conf, I was able to restore some amount of functionality, at the cost of significantly lower speeds than before this issue began. (~2MB/s down from ~20 before)
I've been running Arch for about a year without anything like this happening, and I don't think I changed anything significant around the time this started. Is there any chance I would be able to truly fix the issue and go back to the original functionality?

Information that might be useful (I've added a > before the commands I typed in for clarity, and for personal reasons, I've censored the name of my network.):

>uname -a
>pacman -Qi linux | grep Version
>pacman -Qi linux-firmware | grep Version
Linux archlinux 6.17.7-arch1-2 #1 SMP PREEMPT_DYNAMIC Wed, 12 Nov 2025 14:41:18 +0000 x86_64 GNU/Linux
Version         : 6.17.7.arch1-2
Version         : 20251021-1

This one is really long, you might need to scroll to see all of it:

>lspci -nnk | grep -iA3 net
>iwconfig
>iw dev wlan0 link
>sudo iw phy | grep -i ht
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8]
	DeviceName: Onboard - Ethernet
	Subsystem: ASRock Incorporation Device [1849:15b8]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
--
02:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
	Subsystem: Intel Corporation Device [8086:2110]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
lo        no wireless extensions.

eno1      no wireless extensions.

wlan0     IEEE 802.11  ESSID:"MyWifiName"  
          Mode:Managed  Frequency:5.22 GHz  Access Point: 12:A7:93:22:99:8F   
          Bit Rate=54 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=55/70  Signal level=-55 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:520   Missed beacon:0

Connected to 12:a7:93:22:99:8f (on wlan0)
	SSID: MyWifiName
	freq: 5220.0
	RX: 14172104 bytes (22739 packets)
	TX: 5439273 bytes (14519 packets)
	signal: -55 dBm
	rx bitrate: 54.0 MBit/s
	tx bitrate: 54.0 MBit/s
	bss flags: short-slot-time
	dtim period: 1
	beacon int: 100
		Bitrates (non-HT):
		Bitrates (non-HT):
	HT Capability overrides:
	Device supports HT-IBSS.
		* [ VHT_IBSS ]: VHT-IBSS

>cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1
options iwlwifi power_save=0

>fastfetch #(logo removed)
OS: Arch Linux x86_64
Kernel: Linux 6.17.7-arch1-2
Uptime: 37 mins
Packages: 1567 (pacman), 42 (flatpak)
Shell: bash 5.3.3
Display (LF27T35): 1920x1080 in 27", 75 Hz [External] *
Display (DELF115): 1920x1080 in 27", 60 Hz [External]
DE: KDE Plasma 6.5.2
WM: KWin (Wayland)
WM Theme: CatppuccinMocha-Modern
Theme: Breeze (CatppuccinMochaMauve) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: Papirus-Dark [Qt], Papirus-Dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: Catppuccin-Mocha-Mauve (24px)
Terminal: kitty 0.44.0
Terminal Font: JetBrainsMonoNF-Regular (11pt)
CPU: Intel(R) Core(TM) i7-9700F (8) @ 4.70 GHz
GPU: NVIDIA GeForce GTX 1660 SUPER [Discrete]
Memory: 5.24 GiB / 31.27 GiB (17%)
Swap: 0 B / 4.00 GiB (0%)
Disk (/): 175.90 GiB / 232.69 GiB (76%) - ext4
Disk (/mnt/NewVolume): 676.20 GiB / 931.50 GiB (73%) - fuseblk
Local IP (wlan0): 10.0.0.244/24
Locale: en_US.UTF-8

Other things I've tried:
- Downgrading firmware from 3168-29 to 3168-22
- Turning power saving off in about 20 different places (BIOS, grub config, nmcli)
- Turning off Bluetooth coexistence in iwlwifi.conf (Firmware or kernel ignores that setting.)
- All the standard troubleshooting stuff (Restarting my pc & router, checking for loose cables, making sure packages are up to date, etc.)

If there's any other information that could help solve this, please tell me.

-thc · 2025-11-14 06:38:36

Since this behavior change happened quite recently I would first check "linux-lts" as a kernel (driver issue) and if that does nothing downgrade "linux-firmware-intel" (firmware issue).

Nova · 2025-11-15 01:14:19

Installed linux-lts, rebooted, and confirmed it was installed with:

>uname -r
6.12.58-1-lts

However, I still have the same issues: Bad speeds with 11n_disable=1, and non-functional without it. How would I downgrade the intel firmware?

jonno2002 · 2025-11-15 01:39:46

try

options iwlmvm power_scheme=1

and get rid of the other 2 options, i was doing updates on my machines today and had to enable this on one to sort some network issues

Nova · 2025-11-15 02:44:07

jonno2002 wrote:

options iwlmvm power_scheme=1

That doesn't seem to work for my issue sadly.

Nova · 2025-11-15 04:21:32

-thc wrote:

if that does nothing downgrade "linux-firmware-intel" (firmware issue).

I tried doing this by downloading it from the package archive with

sudo pacman -U https://archive.archlinux.org/packages/l/linux-firmware-intel/linux-firmware-intel-20251021-1-any.pkg.tar.zst

But that still didn't fix it. I downloaded the version from October 21st, which I am almost certain was before this issue started, and the issue still happens.

Some extra information I forgot to include earlier, the dmesg logs sorted for iwlwifi:

sudo dmesg | rg iwlwifi
[    3.970317] iwlwifi 0000:02:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
[    3.970325] iwlwifi 0000:02:00.0: PCI dev 24fb/2110, rev=0x220, rfid=0xd55555d5
[    3.970327] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless-AC 3168
[    4.003407] iwlwifi 0000:02:00.0: loaded firmware version 22.0005fa3c.0 3168-29.ucode op_mode iwlmvm
[    4.134158] iwlwifi 0000:02:00.0: base HW address: d8:3b:bf:2a:3d:9d, OTP minor version: 0x0
[   29.311559] iwlwifi 0000:02:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [58, 222] HW [58, 222] FH TRB=0x0c010a049
[   29.312723] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   29.312865] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[   29.312870] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[   29.312902] iwlwifi 0000:02:00.0: Loaded firmware version: 22.0005fa3c.0 3168-29.ucode
[   29.312908] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   29.312915] iwlwifi 0000:02:00.0: 0x00800A30 | trm_hw_status0
[   29.312920] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[   29.312925] iwlwifi 0000:02:00.0: 0x00043838 | branchlink2
[   29.312930] iwlwifi 0000:02:00.0: 0x0004A584 | interruptlink1
[   29.312934] iwlwifi 0000:02:00.0: 0x0000588E | interruptlink2
[   29.312938] iwlwifi 0000:02:00.0: 0x00000000 | data1
[   29.312943] iwlwifi 0000:02:00.0: 0x00000080 | data2
[   29.312947] iwlwifi 0000:02:00.0: 0x07030000 | data3
[   29.312951] iwlwifi 0000:02:00.0: 0x300135FF | beacon time
[   29.312956] iwlwifi 0000:02:00.0: 0x35365DE6 | tsf low
[   29.312960] iwlwifi 0000:02:00.0: 0x00000017 | tsf hi
[   29.312964] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[   29.312969] iwlwifi 0000:02:00.0: 0x01681EB9 | time gp2
[   29.312973] iwlwifi 0000:02:00.0: 0x00000000 | uCode revision type
[   29.312977] iwlwifi 0000:02:00.0: 0x00000016 | uCode version major
[   29.312981] iwlwifi 0000:02:00.0: 0x0005FA3C | uCode version minor
[   29.312986] iwlwifi 0000:02:00.0: 0x00000220 | hw version
[   29.312990] iwlwifi 0000:02:00.0: 0x00C89200 | board version
[   29.312994] iwlwifi 0000:02:00.0: 0x0A3A001C | hcmd
[   29.312998] iwlwifi 0000:02:00.0: 0xA4022002 | isr0
[   29.313002] iwlwifi 0000:02:00.0: 0x00800000 | isr1
[   29.313006] iwlwifi 0000:02:00.0: 0x0000000A | isr2
[   29.313011] iwlwifi 0000:02:00.0: 0x0041F8C9 | isr3
[   29.313015] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[   29.313018] iwlwifi 0000:02:00.0: 0x00004110 | last cmd Id
[   29.313023] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[   29.313027] iwlwifi 0000:02:00.0: 0x000000D4 | l2p_control
[   29.313032] iwlwifi 0000:02:00.0: 0x00010030 | l2p_duration
[   29.313036] iwlwifi 0000:02:00.0: 0x00000007 | l2p_mhvalid
[   29.313040] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[   29.313044] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[   29.313048] iwlwifi 0000:02:00.0: 0x25091923 | timestamp
[   29.313052] iwlwifi 0000:02:00.0: 0x00340818 | flow_handler
[   29.313063] iwlwifi 0000:02:00.0: Fseq Registers:
[   29.313071] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ERROR_CODE
[   29.313080] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[   29.313088] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[   29.313096] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_OTP_VERSION
[   29.313104] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[   29.313112] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[   29.313120] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVI_ID
[   29.313128] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVR_ID
[   29.313136] iwlwifi 0000:02:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[   29.313144] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[   29.313152] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   29.313160] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   29.313169] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
[   29.313177] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION
[   29.313185] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_BT_FSEQ_VERSION
[   29.313193] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CLASS_TP_VERSION
[   29.313252] iwlwifi 0000:02:00.0: Collecting data: trigger 2 fired.
[   29.313271] iwlwifi 0000:02:00.0: Device error - SW reset
[   29.449132] iwlwifi 0000:02:00.0: restart completed
[   40.574569] iwlwifi 0000:02:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [32, 1] HW [32, 1] FH TRB=0x0c010a02f
[   40.575643] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   40.575782] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[   40.575788] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[   40.575795] iwlwifi 0000:02:00.0: Loaded firmware version: 22.0005fa3c.0 3168-29.ucode
[   40.575801] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   40.575808] iwlwifi 0000:02:00.0: 0x00800A30 | trm_hw_status0
[   40.575813] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[   40.575817] iwlwifi 0000:02:00.0: 0x00043838 | branchlink2
[   40.575822] iwlwifi 0000:02:00.0: 0x0004A584 | interruptlink1
[   40.575826] iwlwifi 0000:02:00.0: 0x0000B250 | interruptlink2
[   40.575830] iwlwifi 0000:02:00.0: 0x00000000 | data1
[   40.575834] iwlwifi 0000:02:00.0: 0x00000080 | data2
[   40.575838] iwlwifi 0000:02:00.0: 0x07030000 | data3
[   40.575843] iwlwifi 0000:02:00.0: 0x14813A9F | beacon time
[   40.575847] iwlwifi 0000:02:00.0: 0x35E23949 | tsf low
[   40.575852] iwlwifi 0000:02:00.0: 0x00000017 | tsf hi
[   40.575856] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[   40.575860] iwlwifi 0000:02:00.0: 0x00AA2A39 | time gp2
[   40.575864] iwlwifi 0000:02:00.0: 0x00000000 | uCode revision type
[   40.575869] iwlwifi 0000:02:00.0: 0x00000016 | uCode version major
[   40.575873] iwlwifi 0000:02:00.0: 0x0005FA3C | uCode version minor
[   40.575877] iwlwifi 0000:02:00.0: 0x00000220 | hw version
[   40.575881] iwlwifi 0000:02:00.0: 0x00C89200 | board version
[   40.575886] iwlwifi 0000:02:00.0: 0x0A20001C | hcmd
[   40.575890] iwlwifi 0000:02:00.0: 0xA4022002 | isr0
[   40.575894] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[   40.575898] iwlwifi 0000:02:00.0: 0x0000000A | isr2
[   40.575902] iwlwifi 0000:02:00.0: 0x0040E8C9 | isr3
[   40.575906] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[   40.575910] iwlwifi 0000:02:00.0: 0x00004110 | last cmd Id
[   40.575914] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[   40.575918] iwlwifi 0000:02:00.0: 0x000000D0 | l2p_control
[   40.575922] iwlwifi 0000:02:00.0: 0x00010030 | l2p_duration
[   40.575927] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[   40.575931] iwlwifi 0000:02:00.0: 0x00000080 | l2p_addr_match
[   40.575935] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[   40.575939] iwlwifi 0000:02:00.0: 0x25091923 | timestamp
[   40.575943] iwlwifi 0000:02:00.0: 0x0034F808 | flow_handler
[   40.575954] iwlwifi 0000:02:00.0: Fseq Registers:
[   40.575962] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ERROR_CODE
[   40.575970] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[   40.575979] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[   40.575987] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_OTP_VERSION
[   40.575995] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[   40.576003] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[   40.576011] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVI_ID
[   40.576019] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVR_ID
[   40.576027] iwlwifi 0000:02:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[   40.576039] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[   40.576047] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   40.576056] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   40.576064] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
[   40.576072] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION
[   40.576080] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_BT_FSEQ_VERSION
[   40.576088] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CLASS_TP_VERSION
[   40.576160] iwlwifi 0000:02:00.0: Collecting data: trigger 2 fired.
[   40.576178] iwlwifi 0000:02:00.0: Device error - SW reset
[   40.718768] iwlwifi 0000:02:00.0: restart completed
[  113.279499] iwlwifi 0000:02:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [63, 28] HW [63, 28] FH TRB=0x0c010a04e
[  113.280574] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[  113.280692] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[  113.280693] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[  113.280694] iwlwifi 0000:02:00.0: Loaded firmware version: 22.0005fa3c.0 3168-29.ucode
[  113.280696] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[  113.280697] iwlwifi 0000:02:00.0: 0x00800A30 | trm_hw_status0
[  113.280698] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[  113.280699] iwlwifi 0000:02:00.0: 0x00043838 | branchlink2
[  113.280699] iwlwifi 0000:02:00.0: 0x0004A584 | interruptlink1
[  113.280700] iwlwifi 0000:02:00.0: 0x000220FC | interruptlink2
[  113.280701] iwlwifi 0000:02:00.0: 0x00000000 | data1
[  113.280702] iwlwifi 0000:02:00.0: 0x00000080 | data2
[  113.280702] iwlwifi 0000:02:00.0: 0x07030000 | data3
[  113.280703] iwlwifi 0000:02:00.0: 0x1C81397F | beacon time
[  113.280704] iwlwifi 0000:02:00.0: 0x3A379A69 | tsf low
[  113.280705] iwlwifi 0000:02:00.0: 0x00000017 | tsf hi
[  113.280706] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[  113.280706] iwlwifi 0000:02:00.0: 0x04539073 | time gp2
[  113.280707] iwlwifi 0000:02:00.0: 0x00000000 | uCode revision type
[  113.280708] iwlwifi 0000:02:00.0: 0x00000016 | uCode version major
[  113.280709] iwlwifi 0000:02:00.0: 0x0005FA3C | uCode version minor
[  113.280709] iwlwifi 0000:02:00.0: 0x00000220 | hw version
[  113.280710] iwlwifi 0000:02:00.0: 0x00C89200 | board version
[  113.280711] iwlwifi 0000:02:00.0: 0x0A3F001C | hcmd
[  113.280712] iwlwifi 0000:02:00.0: 0xA4022002 | isr0
[  113.280713] iwlwifi 0000:02:00.0: 0x01800000 | isr1
[  113.280713] iwlwifi 0000:02:00.0: 0x0000000A | isr2
[  113.280714] iwlwifi 0000:02:00.0: 0x004028C9 | isr3
[  113.280715] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[  113.280715] iwlwifi 0000:02:00.0: 0x00004110 | last cmd Id
[  113.280716] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[  113.280717] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
[  113.280718] iwlwifi 0000:02:00.0: 0x00010030 | l2p_duration
[  113.280719] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[  113.280719] iwlwifi 0000:02:00.0: 0x000000CE | l2p_addr_match
[  113.280720] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[  113.280721] iwlwifi 0000:02:00.0: 0x25091923 | timestamp
[  113.280722] iwlwifi 0000:02:00.0: 0x00342838 | flow_handler
[  113.280728] iwlwifi 0000:02:00.0: Fseq Registers:
[  113.280732] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ERROR_CODE
[  113.280737] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[  113.280741] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[  113.280745] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_OTP_VERSION
[  113.280750] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[  113.280754] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[  113.280758] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVI_ID
[  113.280762] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVR_ID
[  113.280767] iwlwifi 0000:02:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[  113.280771] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[  113.280775] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[  113.280780] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[  113.280784] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
[  113.280788] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION
[  113.280792] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_BT_FSEQ_VERSION
[  113.280797] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CLASS_TP_VERSION
[  113.280804] iwlwifi 0000:02:00.0: Collecting data: trigger 2 fired.
[  113.280806] iwlwifi 0000:02:00.0: Device error - SW reset
[  113.402118] iwlwifi 0000:02:00.0: restart completed
[  124.031545] iwlwifi 0000:02:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [114, 83] HW [114, 83] FH TRB=0x0c010a081
[  124.032613] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[  124.032731] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[  124.032732] iwlwifi 0000:02:00.0: Transport status: 0x0000004A, valid: 6
[  124.032734] iwlwifi 0000:02:00.0: Loaded firmware version: 22.0005fa3c.0 3168-29.ucode
[  124.032735] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[  124.032736] iwlwifi 0000:02:00.0: 0x000002F3 | trm_hw_status0
[  124.032737] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[  124.032738] iwlwifi 0000:02:00.0: 0x00043838 | branchlink2
[  124.032739] iwlwifi 0000:02:00.0: 0x0004A584 | interruptlink1
[  124.032740] iwlwifi 0000:02:00.0: 0x00006186 | interruptlink2
[  124.032740] iwlwifi 0000:02:00.0: 0x00000000 | data1
[  124.032741] iwlwifi 0000:02:00.0: 0x00000080 | data2
[  124.032742] iwlwifi 0000:02:00.0: 0x07030000 | data3
[  124.032743] iwlwifi 0000:02:00.0: 0x09C139B1 | beacon time
[  124.032743] iwlwifi 0000:02:00.0: 0x3ADBAA34 | tsf low
[  124.032744] iwlwifi 0000:02:00.0: 0x00000017 | tsf hi
[  124.032745] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[  124.032746] iwlwifi 0000:02:00.0: 0x00A25C5E | time gp2
[  124.032747] iwlwifi 0000:02:00.0: 0x00000000 | uCode revision type
[  124.032747] iwlwifi 0000:02:00.0: 0x00000016 | uCode version major
[  124.032748] iwlwifi 0000:02:00.0: 0x0005FA3C | uCode version minor
[  124.032749] iwlwifi 0000:02:00.0: 0x00000220 | hw version
[  124.032750] iwlwifi 0000:02:00.0: 0x00C89200 | board version
[  124.032751] iwlwifi 0000:02:00.0: 0x0000001C | hcmd
[  124.032751] iwlwifi 0000:02:00.0: 0x02EA2002 | isr0
[  124.032752] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[  124.032753] iwlwifi 0000:02:00.0: 0x0000000A | isr2
[  124.032753] iwlwifi 0000:02:00.0: 0x0041D480 | isr3
[  124.032754] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[  124.032755] iwlwifi 0000:02:00.0: 0x10000112 | last cmd Id
[  124.032756] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[  124.032757] iwlwifi 0000:02:00.0: 0x00000000 | l2p_control
[  124.032757] iwlwifi 0000:02:00.0: 0x00001C20 | l2p_duration
[  124.032758] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[  124.032759] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[  124.032760] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[  124.032760] iwlwifi 0000:02:00.0: 0x25091923 | timestamp
[  124.032761] iwlwifi 0000:02:00.0: 0x0034C8D8 | flow_handler
[  124.032767] iwlwifi 0000:02:00.0: Fseq Registers:
[  124.032772] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ERROR_CODE
[  124.032776] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[  124.032780] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[  124.032785] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_OTP_VERSION
[  124.032789] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[  124.032793] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[  124.032797] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVI_ID
[  124.032802] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVR_ID
[  124.032806] iwlwifi 0000:02:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[  124.032810] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[  124.032815] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[  124.032819] iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[  124.032823] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
[  124.032827] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION
[  124.032832] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_BT_FSEQ_VERSION
[  124.032836] iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CLASS_TP_VERSION
[  124.032873] iwlwifi 0000:02:00.0: Collecting data: trigger 2 fired.
[  124.032876] iwlwifi 0000:02:00.0: Device error - SW reset
[  124.172956] iwlwifi 0000:02:00.0: restart completed

Last edited by Nova (2025-11-15 04:22:34)

Nova · 2025-11-15 04:37:48

Nova wrote:

I downloaded the version from October 21st, which I am almost certain was before this issue started, and the issue still happens.

I ended up downgrade even farther to the October 11th version, which still didn't fix the issue. I can say with absolute certainty that this became an issue more recently than October 11th, so downgrading the intel firmware doesn't fix whatever this issue is.

-thc · 2025-11-15 07:02:22

Since it doesn't look like a driver/frimware issue - I would suggest a complete rollback of all changes to the recent kernel/firmware.
Try to boot w/o the module options and post a complete journal of that boot.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Nova · 2025-11-15 19:32:48

-thc wrote:

Since it doesn't look like a driver/frimware issue - I would suggest a complete rollback of all changes to the recent kernel/firmware.
Try to boot w/o the module options and post a complete journal of that boot.
sudo journalctl -b | curl -F 'file=@-' 0x0.st

That command specifically doesn't seem to work when the module options are disabled. It just returns : "curl: (6) Could not resolve host: 0x0.st"

I did save the output of 'sudo journalctl -b' to a txt file, however, which I uploaded to Pastebin here.

Last edited by Nova (2025-11-15 19:33:14)

seth · 2025-11-15 21:11:37

Nov 15 11:11:57 archlinux iwd[557]: udev interface=wlan0 ifindex=4
Nov 15 11:11:57 archlinux NetworkManager[553]: <info>  [1763233917.9066] device (wlan0): new IWD device state is disconnected

Disable the iwd.service - if you want to use it as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend to let NM control iwd.

Nova · 2025-11-16 03:05:08

seth wrote:

Nov 15 11:11:57 archlinux iwd[557]: udev interface=wlan0 ifindex=4
Nov 15 11:11:57 archlinux NetworkManager[553]: <info>  [1763233917.9066] device (wlan0): new IWD device state is disconnected
Disable the iwd.service - if you want to use it as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend to let NM control iwd.

That isn't related to this issue, and doesn't fix it.

thenextdon13 · 2025-11-16 05:45:42

Hello-
I very recently (after pacman -Suy yesterday) started having trouble with my intel card as well, although the symptoms may be slightly different. My card seems to silently drop traffic whenever powersave mode is on. I don't get anything in dmesg or the system journal. When i disable powersave (via iwconfig $INTERFACE power off) the troubles all go away. I see you tried disabling power save about '20 different places', and it didn't help- but i'm not sure how iwconfig interfaces with the network card vs the programs you mention. Do you know for sure if your card is in or out of powersave mode? Its not clear from your snippets if you ever get it out of powersave mode.

Here are the details of my situation:

[dylan@thinkarch ~]$ uname -a && lspci | grep -i wireless && iwconfig wlp4s0 | grep Management
Linux thinkarch 6.17.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 14 Nov 2025 06:54:20 +0000 x86_64 GNU/Linux
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
          Power Management:on
[dylan@thinkarch ~]$ ethtool -i wlp4s0 
driver: iwlwifi
version: 6.17.8-arch1-1
firmware-version: 36.c8e8e144.0 8000C-36.ucode
expansion-rom-version: 
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
[dylan@thinkarch ~]$

ssh'ing into the wireless router/ap that i am connected to is very bad- latency of typing feedback changes and frequently locks up.

Ping times occasionally get high, and i get an occational 'DUP!'

64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=22 ttl=64 time=4.27 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=23 ttl=64 time=114 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=24 ttl=64 time=3.64 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=25 ttl=64 time=3.72 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=26 ttl=64 time=4.25 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=27 ttl=64 time=5.69 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=28 ttl=64 time=5.68 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=29 ttl=64 time=4.14 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=30 ttl=64 time=3.74 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=31 ttl=64 time=4.08 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=32 ttl=64 time=3.12 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=33 ttl=64 time=108 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=34 ttl=64 time=5.76 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=35 ttl=64 time=3.23 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=36 ttl=64 time=3.20 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=37 ttl=64 time=5.83 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=38 ttl=64 time=6.15 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=39 ttl=64 time=5.79 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=40 ttl=64 time=3.61 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=41 ttl=64 time=3.64 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=42 ttl=64 time=3.12 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=43 ttl=64 time=108 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=44 ttl=64 time=5.04 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=45 ttl=64 time=4.10 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=46 ttl=64 time=4.15 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=47 ttl=64 time=3.63 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=48 ttl=64 time=3.88 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=49 ttl=64 time=4.95 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=50 ttl=64 time=5.34 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=51 ttl=64 time=112 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=52 ttl=64 time=3.20 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=53 ttl=64 time=107 ms
64 bytes from router01.sandy (fd6e:2bca:e310::1): icmp_seq=54 ttl=64 time=3.50 ms

MTR sees packet loss intermittently here and there, but no small amount (6% in this case)

 1. router01.sandy                                                                                                                                                       6.0%   233    3.0   5.7   1.4 112.4  15.8

The wireless interface does log excessive retries and invalid misc- i'm not sure how normal this is:

wlp4s0    IEEE 802.11  ESSID:"Wifi N"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 20:05:B6:FF:BB:76   
          Bit Rate=130 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=52/70  Signal level=-58 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:221   Missed beacon:0

[dylan@thinkarch ~]$

The network interface doesn't show any errors/dropped/missed/etc

[dylan@thinkarch ~]$ ip stats show dev wlp4s0 
3: wlp4s0: group offload subgroup hw_stats_info
    l3_stats off used off
3: wlp4s0: group xstats_slave subgroup bond suite 802.3ad
3: wlp4s0: group xstats_slave subgroup bridge suite vlan
3: wlp4s0: group xstats_slave subgroup bridge suite mcast
3: wlp4s0: group xstats_slave subgroup bridge suite stp
3: wlp4s0: group xstats subgroup bond suite 802.3ad
3: wlp4s0: group xstats subgroup bridge suite vlan
3: wlp4s0: group xstats subgroup bridge suite mcast
3: wlp4s0: group xstats subgroup bridge suite stp
3: wlp4s0: group afstats subgroup mpls
3: wlp4s0: group offload subgroup l3_stats off used off
3: wlp4s0: group offload subgroup cpu_hit

3: wlp4s0: group link
    RX:  bytes packets errors dropped  missed   mcast           
     558409301  501642      0       0       0       0 
    TX:  bytes packets errors dropped carrier collsns           
      30328152  204899      0       0       0       0 
[dylan@thinkarch ~]$

Unsure if this will help you any, but i certainly would like to have working power management on my box again and can post more info as needed to this or another thread

seth · 2025-11-16 08:00:04

Do you get FW crashes similar to the OP and notably

Queue * is active on fifo * and stuck for 10000 ms.

@Nova, please post an updated journal
Do you get the same jams with wpa_supplicant?

thenextdon13 · 2025-11-16 16:40:00

I do not. dmesg looks pretty clean on mine (see below). I'm happy to start a new thread if that would be best?

[dylan@thinkarch ~]$ sudo dmesg | grep iwlwifi
[sudo] password for dylan: 
[    5.853187] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[    5.870643] iwlwifi 0000:04:00.0: Detected crf-id 0xbadcafe, cnv-id 0x3000000 wfpm id 0x80000000
[    5.870788] iwlwifi 0000:04:00.0: PCI dev 24f3/0130, rev=0x201, rfid=0xd55555d5
[    5.870793] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless-AC 8260
[    5.892725] iwlwifi 0000:04:00.0: loaded firmware version 36.c8e8e144.0 8000C-36.ucode op_mode iwlmvm
[    6.166660] iwlwifi 0000:04:00.0: base HW address: 44:85:00:b9:0c:c1, OTP minor version: 0x4
[    6.269913] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0

seth · 2025-11-16 17:20:05

I'm happy to start a new thread if that would be best?

Probably.

When i disable powersave (via iwconfig $INTERFACE power off) the troubles all go away.

Do you still "iwlwifi.power_save=Y" any level of "iwlwifi.power_level=1-5" and "iwlmvm.power_scheme > 1"?
Does the userspace config actually save you any battery at all?

thenextdon13 · 2025-11-16 18:22:53

Copy. I'll open a new topic after we're done with the questions here.

I don't specifically remember changing any power configuration- i think it was all out of the box (but its been a while since i set this box up)
And i have no idea if i save any battery at all- i'm happy to do some testing if there are suggested methods. I just know it was really convenient when everything worked 'out of the box' so to speak.

Here are what the parameters and iwconfig indicate after a fresh boot and on battery (and the problem is presently occuring)

[dylan@thinkarch module]$ head iwlwifi/parameters/power_save iwlwifi/parameters/power_level iwlmvm/parameters/power_scheme && sudo iwconfig wlp4s0 | grep Management
==> iwlwifi/parameters/power_save <==
N

==> iwlwifi/parameters/power_level <==
0

==> iwlmvm/parameters/power_scheme <==
2
          Power Management:on
[dylan@thinkarch module]$

And here are what the parameters and iwconfig indicate after issuing 'iwconfig $INTERFACE power off', and the problem has gone away-

[dylan@thinkarch module]$ head iwlwifi/parameters/power_save iwlwifi/parameters/power_level iwlmvm/parameters/power_scheme && sudo iwconfig wlp4s0 | grep Management
==> iwlwifi/parameters/power_save <==
N

==> iwlwifi/parameters/power_level <==
0

==> iwlmvm/parameters/power_scheme <==
2
          Power Management:off
[dylan@thinkarch module]$

Apparently iwconfig doesn't enable power management in the iwlwifi parameters that you expect?

Last edited by thenextdon13 (2025-11-16 18:23:17)

Nova · 2025-11-16 18:36:02

seth wrote:

Do you get FW crashes similar to the OP and notably
Queue * is active on fifo * and stuck for 10000 ms.
@Nova, please post an updated journal
Do you get the same jams with wpa_supplicant?

I have already posted my journal in a previous post, but I'll link it again here: https://pastebin.com/97SkXPZE

Last edited by Nova (2025-11-16 18:55:53)

seth · 2025-11-16 19:01:41

The question was for thenextdon13 or do you mean you get the same w/ wpa_supplicant instead of iwd?

I meant the journal after disabling iwd, but was wrong itfp, iwd /is/ NM controlled - fooled myself because there's no trace of NM scanning around.
Wild guess: what if you move the DNS away from comcast and to 1.1.1.1 or 8.8.8.8?

@thenextdon13, see whether you can enable power saving in the driver w/o losing stability
powertop will get you an idea o the battery discharge rate, but that's a rather unsharp metric.

thenextdon13 · 2025-11-16 19:41:07

With iwconfig power off, and the driver parameters as follows, I no longer have the problems. I tried to find a definition of power_scheme and power_level but have not at this point.

I did try power_level=5 as well as power_level=1 and the shown power_level=0. All seemed to work just fine.

[dylan@thinkarch module]$ head iwlwifi/parameters/power_save iwlwifi/parameters/power_level iwlmvm/parameters/power_scheme && sudo iwconfig wlp4s0 | grep Management
==> iwlwifi/parameters/power_save <==
Y

==> iwlwifi/parameters/power_level <==
0

==> iwlmvm/parameters/power_scheme <==
2
          Power Management:off
[dylan@thinkarch module]$

At this point, it seems like ?userspace network tools? power issue vs driver, and i'll move off of this thread to avoid confusion (unless @seth you feel otherwise)

Thank you -- and i'm sorry @Nova didn't mean to hijack your thread.

seth · 2025-11-16 21:51:43

parm:           power_level:default power save level (range from 1 - 5, default: 1) (int)

"power_level=0" is probably "none" (as it goes along power_save=N) and according to https://elixir.bootlin.com/linux/v6.17. … ower.c#L39 higher values seem to cause more aggressive saving (thermal throttling)

Nova · 2025-11-16 23:49:22

If you are going to keep discussing another issue, can I ask you to please create a new post to discuss it, because it's making it difficult to keep track of what is in reference to my issue and what isn't.

thenextdon13 · 2025-11-17 05:20:51

@Nova - i'm sorry.
As we are running the same driver and ran into issues around the same time, I thought these issues may be related.
It was not clear to me that this is likely an unrelated issue until the most recent set of updates. It was not my intention at all to hijack your issue/thread so much as make sure they were not related and not start duplicate issue threads. I don't know enough to understand until the most recent updates that our problems are (at least superficially) unrelated.
Now that it is clear our problems are likely not related, i'll create another thread, as i mentioned in #19.
Wish you luck on resolving your issue.

-thc · 2025-11-17 06:45:54

@Nova: Your journal contains some hints.

Since your WiFi adapter is an onboard adapter on your ASRock B365M IB-R consider updating your BIOS to version 1.01 - just to make sure that it's not a nasty firmware bug.

The log clearly states serious problems:

Nov 15 11:12:25 archlinux kernel: iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.

The iwlwifi microcode runs into a fatal problem and those

Nov 15 11:12:25 archlinux kernel: wlan0: HW problem - can not stop rx aggregation for 12:a7:93:22:99:8f tid 0

Nov 15 11:17:15 archlinux iwd[557]: invalid HE capabilities for ac:db:48:82:98:8a

show that something is definitely not working.

I would suggest testing this hardware via live boot medium (e.g. Mint, Ubuntu, Debian) - if the problems persist it's probably the hardware.

If not - I would try to skip iwd and give wpa_supplicant a try.

seth · 2025-11-17 10:58:03

Problems start with

Nov 15 11:12:25 archlinux kernel: iwlwifi 0000:02:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [65, 213] HW [65, 213] FH TRB=0x0c010a050
Nov 15 11:12:25 archlinux kernel: iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.

The device resets twice

Nov 15 11:12:25 archlinux kernel: iwlwifi 0000:02:00.0: restart completed
Nov 15 11:12:36 archlinux kernel: iwlwifi 0000:02:00.0: restart completed

but then shuts up.

ac:db:48 is from Commscope but the connection is to the LAA 12:a7:93:22:99:8f ?

Ftr. this is 10s before the jam causing the reset

Nov 15 11:12:14 archlinux otd-daemon[1218]: [Detect:Info]        No tablets were detected.
Nov 15 11:12:14 archlinux vesktop[1208]: APPIMAGE env is not defined, current application is not an AppImage
Nov 15 11:12:14 archlinux vesktop[1208]: Vesktop v1.6.1
Nov 15 11:12:14 archlinux vesktop[1208]: Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
Nov 15 11:12:14 archlinux systemd[1]: Starting Time & Date Service...
Nov 15 11:12:14 archlinux systemd[1]: Started Time & Date Service.
Nov 15 11:12:15 archlinux kbuildsycoca6[1495]: The action "new-window" in the desktop file "/usr/share/applications/rustdesk.desktop" has no Exec key and not D-Bus activatable
Nov 15 11:12:15 archlinux systemd[728]: Started app-org.chromium.Chromium-1208.scope.
Nov 15 11:12:15 archlinux kded6[957]: Registering ":1.62/StatusNotifierItem" to system tray
Nov 15 11:12:15 archlinux vesktop[1208]: [arRPC > ipc] listening at /run/user/1000/discord-ipc-0
Nov 15 11:12:15 archlinux vesktop[1208]: [arRPC > websocket] listening on 6463
Nov 15 11:12:15 archlinux vesktop[1208]: [arRPC > process] started
Nov 15 11:12:15 archlinux vesktop[1208]: [1208:1115/111215.881729:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
Nov 15 11:12:15 archlinux vesktop[1208]: [1208:1115/111215.881738:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
Nov 15 11:12:16 archlinux rtkit-daemon[781]: Supervising 6 threads of 3 processes of 1 users.
Nov 15 11:12:16 archlinux rtkit-daemon[781]: Supervising 6 threads of 3 processes of 1 users.
Nov 15 11:12:16 archlinux flatpak[1382]: INFO:Hidamari:Hidamari v3.6

but I suspect it's just "we use the NIC at all".

Iff it's not the kernel not the firmware and iff "iwlwifi.11n_disable=1" indeed is a reliable switch and not just a fluke I'd first and foremost test this against a different AP (eg. your phone hotspot)
Did anything change in the environment (new radio device, neighbors, …) or did you switch the wifi channel?
Does (likely, in doubt) increasing the rx buffer "iwlwifi.amsdu_size=3" help anything?

Arch Linux

#1 2025-11-14 05:56:15

Intel WiFi card randomly dropped to 100B/s download speeds.

#2 2025-11-14 06:38:36

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#3 2025-11-15 01:14:19

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#4 2025-11-15 01:39:46

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#5 2025-11-15 02:44:07

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#6 2025-11-15 04:21:32

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#7 2025-11-15 04:37:48

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#8 2025-11-15 07:02:22

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#9 2025-11-15 19:32:48

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#10 2025-11-15 21:11:37

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#11 2025-11-16 03:05:08

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#12 2025-11-16 05:45:42

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#13 2025-11-16 08:00:04

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#14 2025-11-16 16:40:00

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#15 2025-11-16 17:20:05

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#16 2025-11-16 18:22:53

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#17 2025-11-16 18:36:02

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#18 2025-11-16 19:01:41

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#19 2025-11-16 19:41:07

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#20 2025-11-16 21:51:43

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#21 2025-11-16 23:49:22

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#22 2025-11-17 05:20:51

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#23 2025-11-17 06:45:54

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

#24 2025-11-17 10:58:03

Re: Intel WiFi card randomly dropped to 100B/s download speeds.

Board footer