There's no wireless interface show in the network icon and none in when I type 'nmcli device' running dmesg shows

[130854.349171] mt7921e 0000:05:00.0: probe with driver mt7921e failed with error -22

However, the only version of mt7921e.ko.zst that isn't in the directory that I compiled my current kernel in has the same version as my current kernel. modinfo mt7921e.ko.zst shows:

:       /usr/lib/modules/6.16.0-273-tkg-eevdf/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst
license:        Dual BSD/GPL
description:    MediaTek MT7921E (PCIe) wireless driver
author:         Lorenzo Bianconi 
author:         Sean Wang 
firmware:       mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7922_1.bin
firmware:       mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7961_1.bin
firmware:       mediatek/WIFI_MT7961_patch_mcu_1a_2_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7961_1a.bin
srcversion:     579FF3B9B2F0D659D1EE01B
alias:          pci:v000014C3d00007920sv*sd*bc*sc*i*
alias:          pci:v000014C3d00000616sv*sd*bc*sc*i*
alias:          pci:v000014C3d00000608sv*sd*bc*sc*i*
alias:          pci:v00000B48d00007922sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007922sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007961sv*sd*bc*sc*i*
depends:        mt76-connac-lib,mt7921-common,mt792x-lib,mt76,rfkill
intree:         Y
name:           mt7921e
retpoline:      Y
vermagic:       6.16.0-273-tkg-eevdf SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        14:13:73:2F:93:AF:32:42:B8:04:91:B9:07:E5:D0:10:1A:DB:80:7C
sig_hashalgo:   sha512
signature:      30:66:02:31:00:CF:15:39:BD:88:4B:0D:21:03:28:74:FE:89:49:78:
                8A:43:A3:13:B9:70:3E:00:44:6E:5B:38:1D:74:EE:2D:C3:D0:A7:45:
                74:F6:08:87:6A:5D:C1:A7:58:A0:DE:C8:1C:02:31:00:BA:EE:70:E8:
                BE:D1:50:93:6A:5C:6C:94:28:C1:CA:2A:70:8B:29:2D:8E:E1:EE:72:
                9C:65:A3:F7:07:C1:D7:17:C0:42:BB:3B:C7:57:6B:47:33:8A:EE:5E:
                4C:C8:37:84
parm:           disable_aspm:disable PCI ASPM support (bool)

uname -a shows

mage 6.16.0-273-tkg-eevdf #1 SMP PREEMPT_DYNAMIC TKG Sat, 02 Aug 2025 14:38:19 +0000 x86_64 GNU/Linux

I'm running Endeavour OS I tried running 'modprobe mt7921e --force-modversion' but it gives the same error. All of the firmware files are there in /lib/firmware/mediatek. I tried using mt7921s and mt7921u, the don't give an error but they don't show a wireless device either. lspci -nn shows

:00.0 Network controller : MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]

This issue also occurs if I boot from a livecd (which has a different kernel version).

I am currently attempting to install Debian on my laptop computer. During the network configuration stage, I am prompted to "enter a passphrase for WPA/WPA2 PSK authentication". Unfortunately, I am on my school's network which requires both a username and a password, with the [MS-CHAPv2](https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access#MS-CHAPv2) authentication protocol. What should I enter at the prompt? I have an Ubuntu computer which can connect to this network. Here are the contents of /etc/NetworkManager/system-connections/NetworkName: [ipv6] method=auto [connection] id=NetworkName uuid=3e728a68-a877-4681-bc0e-1e64b2ff6434 type=802-11-wireless [802-11-wireless-security] key-mgmt=wpa-eap auth-alg=open [802-11-wireless] ssid=NetworkName mode=infrastructure mac-address=84:A6:C8:A9:67:DA security=802-11-wireless-security [802-1x] eap=ttls; identity=username phase2-auth=mschapv2 password-flags=1 [ipv4] method=auto Curiously enough, the password I enter to connect to NetworkName doesn't appear anywhere. EDIT 2: Screenshot of network connection process (in a live-boot Ubuntu)

I'm using Fedora 31 on my Notebook. Everything works well, except for Fedora dropping the wifi connection after a while, making it necessary to reconnect to the network. Every few minutes after reconnecting the behaviour repeats itself. I have no idea what the reasons are for that. It often happens when I download files (putting "load" on the network) but sometimes also without any obvious reason. The problem first appeared under Fedora 30 and stayed after the upgrade to Fedora 31. Output from journalctl -b -u NetworkManager: -- Logs begin at Sun 2019-07-14 01:05:47 CEST, end at Sat 2019-11-16 23:42:15 CET. -- Nov 16 23:35:19 localhost.localdomain systemd: Starting Network Manager... Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8189] NetworkManager (version 1.20.6-1.fc31) is starting... (after a restart) Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8191] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) Nov 16 23:35:19 localhost.localdomain systemd: Started Network Manager. Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8260] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8355] manager[0x5559cd8e80f0]: monitoring kernel firmware directory '/lib/firmware'. Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3382] hostname: hostname: using hostnamed Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3385] hostname: hostname changed from (none) to "localhost.localdomain" Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3390] dns-mgr[0x5559cd8cd240]: init: dns=default,systemd-resolved rc-manager=symlink Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3401] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.3/0000:05:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: Wi-Fi hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: WWAN hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3479] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wifi.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3486] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-adsl.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3511] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-team.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3553] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-bluetooth.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3559] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wwan.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3561] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3563] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3565] manager: Networking is enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3567] dhcp-init: Using DHCP client 'internal' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-settings-plugin-ifcfg-rh.so") Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: keyfile (internal) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3838] device (lo): carrier: link connected Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3845] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3886] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3951] settings: (enp4s0): created default wired connection 'Kabelgebundene Verbindung 1' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3986] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4067] device (wlp5s0): driver supports Access Point (AP) mode Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4079] manager: (wlp5s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4127] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.7252] device (wlp5s0): set-hw-addr: set MAC address to 96:1B:95:D7:6D:B2 (scanning) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0023] modem-manager: ModemManager available Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0103] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] supplicant: wpa_supplicant running Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] device (wlp5s0): supplicant interface state: init -> starting Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0323] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0446] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0458] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0583] sup-iface[0x5559cd8fe130,wlp5s0]: supports 5 scan SSIDs Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0596] device (wlp5s0): supplicant interface state: starting -> ready Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0597] Wi-Fi P2P device controlled by interface wlp5s0 created Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0599] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0602] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0610] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0613] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0631] sup-iface: failed to cancel p2p connect: P2P cancel failed Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3859] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3906] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3924] device (virbr0): Activation: starting connection 'virbr0' (dc059138-81a5-4d0a-bb5e-725c891ae6bf) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3935] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3947] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3976] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (d3fd587b-3b1e-418f-9fa9-dc52709be3e1) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3980] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3991] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4045] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4060] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4066] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4073] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4083] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4108] device (virbr0): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4127] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0): bridge port virbr0-nic was attached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4214] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4270] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4274] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4291] device (virbr0-nic): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4363] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0): bridge port virbr0-nic was detached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0-nic): released from master device virbr0 Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7709] policy: auto-activating connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7722] device (wlp5s0): Activation: starting connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7731] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7741] manager: NetworkManager state is now CONNECTING Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7777] device (wlp5s0): set-hw-addr: reset MAC address to 58:00:E3:D0:B5:0F (preserve) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7887] device (wlp5s0): supplicant interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7889] device (p2p-dev-wlp5s0): supplicant management interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7892] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7897] device (wlp5s0): Activation: (wifi) access point 'Wifi-SSID' has security, but secrets are required. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7898] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7901] sup-iface[0x5559cd8fe130,wlp5s0]: wps: type pbc start... Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7939] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7946] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7950] device (wlp5s0): Activation: (wifi) connection 'Wifi-SSID' has security, and secrets exist. No new secrets needed. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'ssid' value 'Wifi-SSID' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'scan_ssid' value '1' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7953] Config: added 'bssid' value '54:67:51:B8:29:2A' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7954] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7955] Config: added 'psk' value '' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (wlp5s0): supplicant interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (p2p-dev-wlp5s0): supplicant management interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8098] device (wlp5s0): supplicant interface state: inactive -> scanning Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8099] device (p2p-dev-wlp5s0): supplicant management interface state: inactive -> scanning Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5410] device (wlp5s0): supplicant interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5412] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5617] device (wlp5s0): supplicant interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5618] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (wlp5s0): supplicant interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (wlp5s0): supplicant interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (p2p-dev-wlp5s0): supplicant management interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7563] device (wlp5s0): supplicant interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Wifi-SSID" Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (p2p-dev-wlp5s0): supplicant management interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7651] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7656] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds) Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8962] dhcp4 (wlp5s0): state changed unknown -> bound Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8970] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8993] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8995] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9002] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9017] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9018] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv4 routing and DNS Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9062] device (wlp5s0): Activation: successful, device activated. Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9069] manager: startup complete Nov 16 23:35:31 localhost.localdomain NetworkManager: [1573943731.0336] manager: NetworkManager state is now CONNECTED_GLOBAL Nov 16 23:35:32 localhost.localdomain NetworkManager: [1573943732.0747] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv6 routing and DNS Nov 16 23:35:34 localhost.localdomain NetworkManager: [1573943734.5034] agent-manager: req[0x5559cd9eb540, :1.201/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE The general journal shows the following before dropping the connection: Nov 16 23:40:40 localhost.localdomain systemd: Starting Tracker metadata database store and lookup manager... Nov 16 23:40:40 localhost.localdomain systemd: Started Tracker metadata database store and lookup manager. Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:40:47 localhost.localdomain systemd: Starting Network Manager Script Dispatcher Service... Nov 16 23:40:47 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:40:47 localhost.localdomain audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:40:57 localhost.localdomain systemd: NetworkManager-dispatcher.service: Succeeded. Nov 16 23:40:57 localhost.localdomain audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:41:11 localhost.localdomain tracker-store: OK Nov 16 23:41:11 localhost.localdomain systemd: tracker-store.service: Succeeded. I also get the following error during the creation phase of the connection: Nov 16 23:43:08 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:43:08 localhost.localdomain kernel: wlp5s0: deauthenticating from 54:67:51:b8:29:2a by local choice (Reason: 3=DEAUTH_LEAVING) Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=54:67:51:b8:29:2a reason=3 locally_generated=1 Nov 16 23:43:08 localhost.localdomain wpa_supplicant: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6104] sup-iface[0x5559cd8fe130,wlp5s0]: connection disconnected (reason -3) Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6110] device (wlp5s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): canceled DHCP transaction Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): state changed bound -> done Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE

~$ lspci -nn 00:00.0 Host bridge : Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 00:16.0 Communication controller : Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) 00:16.3 Serial controller : Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.3 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) 00:1c.4 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4) 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge : Intel Corporation QM67 Express Chipset Family LPC Controller [8086:1c4f] (rev 04) 00:1f.2 SATA controller : Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04) 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) 0d:00.0 System peripheral : Ricoh Co Ltd PCIe SDXC/MMC Host Controller [1180:e823] (rev 07) As [he was saying](https://unix.stackexchange.com/questions/645901/having-issue-with-debian-installation#comment1210259_645901) . I was following [the Wiki](https://wiki.debian.org/iwlwifi) . root@debian:/home/istiak# apt update && apt install firmware-iwlwifi Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package firmware-iwlwifi root@debian:/home/istiak# modprobe -r iwlwifi ; modprobe iwlwifi bash: modprobe: command not found bash: modprobe: command not found When I try to run iwconfig or ifconfig I get that command not found. How can I install wifi driver? I have installed(iwlwifi-6000g2a-ucode-18.168.6.1.tgz) from [here](https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html) . When I extracted I got it(iwlwifi-6000g2a-6.ucode). What I have to do with it? Output of /usr/sbin/modprobe --version : kmod version 26 +XZ -ZLIB +OPENSSL -EXPERIMENTAL iwconfig : root@debian:~# /sbin/iwconfig enp0s25 no wireless extensions. wwp0s29u1u4 no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off lo no wireless extensions. lspci -knn | grep -i net -A3 : istiak@debian:~$ lspci -knn | grep -i net -A3 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Lenovo 82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520) [17aa:21ce] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) -- 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1311] Kernel driver in use: iwlwifi Kernel modules: iwlwifi

I know that this question is posted a few times already, but I tried many of the solutions there and they didn't work. If I start my Laptop (restart or fresh boot after being turned off) the WiFi works most of the time and I can connect to it without a problem. *Not always though* If I'm connected and close the lid or press the power button so that the laptop goes into suspend mode, after I open it up again, I can't connect to the internet. The available networks are shown, but all of them only have a 10% strength and nothing happens when I try to connect to them. If I deactivate and activate WiFi again (either by the switch in network-manager or by the F-Key on the keyboard), it shows WiFi as "not connected". I tried to restart network-manager after the suspension, but that didn't fix the problem. I know that this is not a lot of debugging information, but I'm not knowledgeable enough of Linux to be able to give you a more relevant one. But I'm happy to provide it, if you tell me what exactly. EDIT: After thinking about the problem a little bit more I also remembered the following: If I let the Laptop suspend by going idle and waiting for the 5 minutes it requires, I sometimes have WiFi after booting up again. It also happened recently, that I was playing in offline mode (because I had no WiFi) and after quite some time I could connect to the Internet again (I think about an hour, but I'm not exactly sure). I have seen this phenomenon very rarely and it only happened on a few occasions.

When I install Debian, installer request network connection. But Debian can't found my Ethernet card (Intel(R) Dual Band Wireless-AC 8260). I use non-free installer and try put .ucode file in /firmware/ folder on USB (from here ), but it not work! I also try renamed iwlwifi-8000 in iwlwifi-8260, but it also not work. Big thanks for your response!

Issue Summary: Multiple worldwide ThinkPad models with WCN6855 hw2.1 fail to properly handle regulatory domain settings, defaulting to incorrect country codes and causing regulatory compliance issues in EU. Affected Hardware: - Primary: Lenovo ThinkPad P16s Gen 2, QCNFA765 (WCN6855 hw2.1) - Secondary: Lenovo ThinkPad T14s Gen 4, same WCN6855 hw2.1 chip - Location: Czech Republic (EU) - Common pattern: Both models have worldwide country codes (00/WW suffix) Firmware versions tested: - Custom kernel: WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41 (2024-04-17) - Debian Live: WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 (2022-04-18) Problem Description: Despite kernel regulatory domain settings, both laptops fail to apply correct regulatory rules: 1. Boot errors (consistent across all systems): ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting 2. Incorrect regulatory domains applied: - P16s defaults to Brazil (BR) despite CZ kernel parameter - T14s defaults to United States (US) - Both ignore proper EU regulatory requirements 3. Regulatory compliance issues in EU: - All 5GHz channels marked "No IR" (No Initiate Radiation) - 6GHz power levels incorrect (30dBm instead of EU limit 23dBm) - Wrong DFS requirements (DFS-UNSET/DFS-FCC instead of DFS-ETSI) Test Results: ThinkPad P16s (21K9S0DC00) with kernel parameter cfg80211.ieee80211_regdom=CZ: global: country CZ: DFS-ETSI [correct] phy#0 (self-managed): country BR: DFS-UNSET [incorrect] ThinkPad T14s (21F8CT01WW) - stock configuration: global: country 00: DFS-UNSET phy#0 (self-managed): country US: DFS-FCC [incorrect for EU] Debian Live CD test (P16s) - proves cross-distribution issue: global: country 00: DFS-UNSET phy#0 (self-managed): country 00: DFS-UNSET 6GHz: 20dBm with "no IR" on ALL channels [overly restrictive] What I tried: 1. Kernel parameter cfg80211.ieee80211_regdom=CZ - Sets global domain but chip remains on wrong country 2. Kernel source modification - Changed default regulatory domain in net/wireless/reg.c: -static char *ieee80211_regdom = "00"; +static char *ieee80211_regdom = "CZ"; 2. Result: Global domain correctly set to CZ, but phy#0 still remains BR - firmware ignores kernel setting 3. Runtime iw reg set CZ - No effect on self-managed phy#0 4. Different distributions - Debian Live CD shows identical boot errors 5. Multiple hardware - Issue affects different worldwide ThinkPad models consistently Analysis: - Both laptops have worldwide country codes in model numbers (00/WW suffix) - SMBIOS likely contains "00" (worldwide) which firmware doesn't handle properly - Firmware falls back to hardcoded regional defaults instead of respecting kernel settings - Issue appears related to SMBIOS country code handling patch for WCN6855 (commit referencing reading country code from SMBIOS) - Problem affects multiple Linux distributions and kernel versions - Kernel-level regulatory changes are completely ignored by self-managed firmware Next Plan: Patching /usr/lib/firmware/ath11k/WCN6855/hw2.1/regdb.bin to replace incorrect regulatory data resolves the issue, but this shouldn't be necessary. Expected behavior: at the very least, it should be possible to change regulatory domain configuration via standard Linux methods Impact: This affects regulatory compliance for EU users with worldwide ThinkPad models, potentially causing interference and legal issues due to incorrect power levels and frequency usage.

My Arch (3.6.5-1) is exhibiting a rather peculiar problem: when wifi is set up, all logs indicate that the setup was successful and that the interface is up and functional. However, when attempting to access a website (or execute ping) all requests time out (despite that connection is reported as working and signal at 63% strength). This tends to happen randomly after laptop is switched on - after some time the connection usually starts working and does not break until next shutdown/suspend. Relevant dmesg entries (full dmesg output can be found [here](http://pastebin.com/PH7jb8fy)) : [ 13.858528] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.024275] r8169 0000:02:00.0: eth0: link down [ 14.024339] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.895920] wlan0: authenticate with 00:24:6c:c8:e4:a1 [ 34.900827] wlan0: send auth to 00:24:6c:c8:e4:a1 (try 1/3) [ 34.902963] wlan0: authenticated [ 34.908362] wlan0: associate with 00:24:6c:c8:e4:a1 (try 1/3) [ 34.911153] wlan0: RX AssocResp from 00:24:6c:c8:e4:a1 (capab=0x1431 status=0 aid=9) [ 34.911217] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 34.911294] wlan0: associated ip -s link shows: wlan0: mtu 1500 qdisc mq state UP mode DORMANT qlen 1000 link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 14970982 50472 0 0 0 0 TX: bytes packets errors dropped carrier collsns 19116 233 0 0 0 0 ip minotor outputs some failure messages: [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [LINK]3: wlan0: mtu 1500 qdisc mq state DOWN link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: mtu 1500 qdisc mq state DORMANT link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: link/ether [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: mtu 1500 qdisc mq state UP link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP [NEIGH]ff02::1:ff1e:f421 dev wlan0 lladdr 33:33:ff:1e:f4:21 NOARP [NEIGH]ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.79.218 dev lo lladdr 00:00:00:00:00:00 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED All that should be loaded seem to be ([output of lsmod](http://pastebin.com/zJm1NiX9)) . Any idea on how to solve this or what the problem is?

**TL;DR** I have reduced the transmit power of a WiFi device and I would like to make this change permanent, so it does not revert after a reboot. **Details** I have joined two Raspberry Pi 4 devices to an existing WiFi network, and I have discovered that by default they transmit at 31 dBm, which is quite high. I was getting a lot of latency, in that it would work fine for 10 seconds and then pretty much stop for 5 seconds, then repeat. I discovered that if I lower the transmit power on both devices to only 10 dBm then the latency dramatically improves. I did this by running the command iw wlan0 set txpower limit 1000. I would like to make this setting persistent across reboots, however I can't see anything in systemd-networkd or wpa_supplicant that controls transmit power. Is there a way to set this (e.g. in systemd's .network or .link file for the WiFi connection)? Failing that, what would be the best way to do this? I am guessing a udev rule would be better than a systemd service as it would run only when the device is available however any advice would be appreciated.

I bought a wireless adapter Realtek 8812BU Wireless. It came with a small CD for the driver but since I don't have a CD-ROM I looked for the driver on the Internet. After a few searches, I managed to install the right one on my Windows 11 machine, it appears as WI-FI 3 on Windows. So everything works as expected so far. The problem is that I couldn't find a way to install a driver for my Kali Linux Virtual machine. The adapter is getting recognized by the VM but when I run ifconfig it doesn't appear so I asume I dont have a good driver. Sorry if my problem seems trivial, I'm new to networking and also to linux.

I recently bought a HP 15-da0206ng laptop and since my goal was to finally switch from Windows to Linux I installed the Linux distribution Pop!_OS 18.04 LTS which is built on Ubuntu 18.04 LTS. After I installed the OS, I encountered a problem: No WIFI Adapter was detected. The WIFI Adapter in the HP 15-da0206ng is a Realtek RTL8821CE 802.11b/g/n/ac, according to HP. I quickly found a solution for this: https://askubuntu.com/questions/1071299/how-to-install-wi-fi-driver-for-realtek-rtl8821ce-on-ubuntu-18-04 I disabled secure boot in BIOS, connected my Laptop via cable updated and upgraded and installed the driver and my WIFI Adapter was detected and worked. However, my download speed via wifi is very slow. The terminal and the browsers (Firefox and Chrome) download everything with a speed of around 85 kb/s. According to this site (it is a German site): http://www.speedmeter.de/ my download speed is at 0.6-0.7 mbit/s. My upload speed is at 5 mbit/s which I consider normal. I did the same speed check with my Samsung phone and it reaches a download speed of 102 mbit/s and an upload speed of 5 mbit/s. Something is clearly wrong with the download speed of my Notebook. After researching this problem I found this thread: https://askubuntu.com/questions/1148030/slow-wifi-connection-ubuntu-18-04/1148065?r=SearchResults#1148065 but switching antennas resulted in no difference. Selecting a specific antenna explicitly seems to be a working solution if your wifi signal is not strong, as it is explained here: https://askubuntu.com/questions/1058379/wifi-signal-is-weak-in-ubuntu-18-04-with-rtl8723be In my case I would say that the signal strength is not a problem. As you can see in the results of running

dev wifi list

IN-USE  SSID                            MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
 *       Burt-Reynolds                   Infra  1     405 Mbit/s  82      ▂▄▆█  WPA2

I also turned of power saving for the wifi adapter as described at the bottom of this readme: https://github.com/tomaspinho/rtl8821ce/blob/master/README.md but it did not make any difference as well. I upgraded the kernel from 4.18 to 4.19 but there was no change. I tried to install Ubuntu (instead of Pop!_OS) 18.04 but here I did not manage to install the rtl8821ce drivers at all. Currently I am running Pop!_OS 19.04 where I can install the drivers again but the download speed is still painful slow. Furthermore I went through this troubleshooting: https://support.system76.com/articles/wireless/ which means I tried to change the router configuration, I disabled IPv6, I enabled Antenna Aggregation, I tried to disable the N mode in /etc/modprobe.d/iwlwifi.conf and I disabled bluetooth coexistence. I am not quite sure what to try anymore and my next steps will be to buy a usb wifi adapter or, the worst case, install Windows again. It seems that most questions related to the rtl8821ce are about getting it not working at all. In my case it works but very slowly. I am not sure if I am missing something obvious and that is why I decided to post this problem here. Here is some additional hardware information:

Intel® Core™ i5-8250U
DDR4-2400 SDRAM, 16 GB      
256 GB PCIe® NVMe™ M.2 SSD
Intel® UHD Graphics 620

Thanks in advance.

I installed Debian 12 using the net installer, I used ethernet to do that (which is probably why i didn't notice the problem), but now I cannot use wifi. Gnome-control-center shows *No Wi-Fi adapter found: Make your have a Wi-Fi adapter plugged in and turned on". kernel version: Kernel: 6.1.0-16-amd64 packages already installed: - firmware-linux 20230210-5 - firmware-linux-free 20200122-1 - firmware-iwlwifi 20230210-5 - intel-microcode 3.20231114.1~deb12u1 output for

is:

00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 02)
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 SATA controller: Intel Corporation Device 06d3
00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Device 06b6 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake LPC Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD
03:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Output for

| grep iwl

is:

iwlmvm                385024  0
mac80211             1175552  1 iwlmvm
iwlwifi               360448  1 iwlmvm
cfg80211             1142784  3 iwlmvm,iwlwifi,mac80211
rfkill                 36864  7 iwlmvm,asus_wmi,bluetooth,cfg80211

output from

dmesg | grep iwl

shows a bunch of stuff, i can show the complete output if you guys want, I will try to only include the relevant stuff:

[   21.070847] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[   21.080175] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-72.ucode
[   21.080185] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[   21.080191] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[   21.080425] iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 QuZ-a0-hr-b0-72.ucode op_mode iwlmvm
[   21.194199] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
[   22.224784] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x5675, CPU2 Status: 0x3
[   22.224822] iwlwifi 0000:00:14.3: WFPM_LMAC1_PD_NOTIFICATION: 0x0
[   22.225386] iwlwifi 0000:00:14.3: HPM_SECONDARY_DEVICE_STATE: 0x42
[   22.225951] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_ADDR: 0x0
[   22.226511] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_DATA: 0x0
[   22.227064] iwlwifi 0000:00:14.3: UMAC PC: 0xc0081558
[   22.227602] iwlwifi 0000:00:14.3: LMAC PC: 0x14f8c
[   22.228132] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
[   22.229241] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode
[   22.229778] iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
[   22.230294] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status0
   .
   .
   .
[   22.243549] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[   22.243879] iwlwifi 0000:00:14.3: 0x00000000 | flow_handler
[   22.244250] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[   22.244567] iwlwifi 0000:00:14.3: Transport status: 0x00000042, valid: 7
[   22.244934] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[   22.245323] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[   22.245687] iwlwifi 0000:00:14.3: 0x80455E9C | umac branchlink2
   . 
   . 
   . 
[   22.249205] iwlwifi 0000:00:14.3: 0x00000004 | isr status reg
[   22.249551] iwlwifi 0000:00:14.3: IML/ROM dump:
[   22.249879] iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
[   22.250226] iwlwifi 0000:00:14.3: 0x00005675 | IML/ROM data1
[   22.250540] iwlwifi 0000:00:14.3: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[   22.250827] iwlwifi 0000:00:14.3: Fseq Registers:
[   22.251114] iwlwifi 0000:00:14.3: 0x20000021 | FSEQ_ERROR_CODE
[   22.251404] iwlwifi 0000:00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION
   . 
   . 
   . 
[   22.254116] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   22.254446] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   22.254727] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
[   22.254993] iwlwifi 0000:00:14.3: Collecting data: trigger 16 fired.
[   23.492898] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
[   23.504797] iwlwifi 0000:00:14.3: retry init count 0
[   23.509449] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
[   24.529089] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x562a, CPU2 Status: 0x3
[   24.530217] iwlwifi 0000:00:14.3: WFPM_LMAC1_PD_NOTIFICATION: 0x0
[   24.531217] iwlwifi 0000:00:14.3: HPM_SECONDARY_DEVICE_STATE: 0x42
[   24.532224] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_ADDR: 0x0
[   24.533250] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_DATA: 0x0
[   24.534147] iwlwifi 0000:00:14.3: UMAC PC: 0xc008151e
[   24.534480] iwlwifi 0000:00:14.3: LMAC PC: 0x14f8c
[   24.534777] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
[   24.535891] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode
[   24.536150] iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
[   24.536411] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status0
   . 
   . 
   .
[   24.544753] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[   24.545086] iwlwifi 0000:00:14.3: 0x00000000 | flow_handler
[   24.545421] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[   24.545707] iwlwifi 0000:00:14.3: Transport status: 0x00000042, valid: 7
[   24.546008] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[   24.546251] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[   24.546492] iwlwifi 0000:00:14.3: 0x80455E9C | umac branchlink2
   . 
   .
   .
[   24.553263] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   24.553523] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   24.553776] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
[   24.554026] iwlwifi 0000:00:14.3: Collecting data: trigger 16 fired.
[   25.766399] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
[   25.779620] iwlwifi 0000:00:14.3: retry init count 1
[   25.786114] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
[   27.025073] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x60e8, CPU2 Status: 0x3
[   27.025938] iwlwifi 0000:00:14.3: WFPM_LMAC1_PD_NOTIFICATION: 0x0
[   27.026775] iwlwifi 0000:00:14.3: HPM_SECONDARY_DEVICE_STATE: 0x42
[   27.027621] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_ADDR: 0x0
[   27.028474] iwlwifi 0000:00:14.3: WFPM_MAC_OTP_CFG7_DATA: 0x0
[   27.029342] iwlwifi 0000:00:14.3: UMAC PC: 0xc00839a2
[   27.030204] iwlwifi 0000:00:14.3: LMAC PC: 0x14f8c
[   27.030484] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
[   27.031599] iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 QuZ-a0-hr-b0-72.ucode
[   27.031829] iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
[   27.032061] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status0
   .
   .
   .
[   27.039690] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[   27.039906] iwlwifi 0000:00:14.3: 0x00000000 | flow_handler
[   27.040168] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[   27.040383] iwlwifi 0000:00:14.3: Transport status: 0x00000042, valid: 7
[   27.040601] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[   27.040883] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
   .
   .
   .
[   27.047332] iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
[   27.047555] iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
[   27.047776] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   27.047997] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   27.048235] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
[   27.048447] iwlwifi 0000:00:14.3: Collecting data: trigger 16 fired.
[   28.257165] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
[   28.270905] iwlwifi 0000:00:14.3: retry init count 2

output from

-kkn | grep Net -A3

00:14.3 Network controller : Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
	DeviceName: Onboard - Ethernet
	Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0074]
	Kernel driver in use: iwlwifi

I have tried connecting with nmcli and iwctl with nmcli

dev wifi connect  password

But that returns: Error: No Wi-Fi device found iwctl Device list shows an empty table. output from

iwconfig

lo        no wireless extensions.

enp4s0    no wireless extensions.

I have restarted the following services NetworkManager networking iwd wpa_supplicant After reinstalling

-wifi

this is the output from

a

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp4s0:  mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 3c:7c:3f:5b:6c:1c brd ff:ff:ff:ff:ff:ff
5: wlan0:  mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 76:51:7c:eb:56:0f brd ff:ff:ff:ff:ff:ff permaddr 78:2b:46:92:4d:0c

contents of

/etc/network/interfaces

is:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

contents of

/etc/NetworkManger/NetworkManager.conf

;

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

contents of

/etc/apt/sources.list

# deb cdrom:[Debian GNU/Linux 12.4.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20231210-17:57]/ bookworm main non-free-firmware

deb http://deb.debian.org/debian/  bookworm main non-free-firmware
deb-src http://deb.debian.org/debian/  bookworm main non-free-firmware

deb http://security.debian.org/debian-security  bookworm-security main non-free-firmware
deb-src http://security.debian.org/debian-security  bookworm-security main non-free-firmware

deb http://deb.debian.org/debian/  bookworm-updates main non-free-firmware
deb-src http://deb.debian.org/debian/  bookworm-updates main non-free-firmware

Yes I have rebooted multiple times. I flashed a live iso with fedora where wifi worked perfectly (wireless). This is my last attempt at finding a solution before I re-install everything again. It bothers me that I haven't been able to solve it. Any help is appreciated, thanks in advance ***Possible solution*** I reinstalled the system, but kept running into the same problem, i repeated it multiple times with varying installation methods (live-image, net-install, and CD-image), all using a wired connection. The common factor between them was that I was always installing gnome. On my last try I installed the system without gnome. I connected to the network (without a desktop environment) via cli. Everything seemed to work fine. I proceeded to install sway, this worked fine, I was able to ssh into my remote machine and get my config files. When using sway, i like to use gnome-control-settings to manage wifi (this worked fine with Debian 11). When I launched the control center from within sway I noticed it did not show any networks available, it did not recognize wifi nor ethernet. However, wifi was working completely fine. After browsing a few files, I noticed a difference in

/etc/network/interfaces

, it now shows

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug wlo1
iface wlo1 inet dhcp
	wpa-ssid 
	wpa-psk

It contains extra interface information. After referencing this link , I changed

/etc/NetworkManager/NetworkManager.conf

to show

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

[device]
wifi.backend=wpa_supplicant

[logging]
level=INFO

After installing and starting the iwd service, I opened gnome-control-settings, wifi networks populated, but when i clicked on mine the cogwheel displayed next to its name but it would not connect (i was not prompted for a password). I selected it, went to the security tab, and noticed that the password field was empty, I filled it out, clicked apply, then the wifi started working (this was from withing sway). I thought this was weird so I logged on with the gnome desktop environment, when I clicked on a different network (my phone hot spot) it now prompted me for a password and the connection was fine. My guess is that gnome-keyring was not activated for my sway session. In short my advice is to ***Make sure only one network management program is running at a time*** and also ***Ensure that the correct keyring is running for your environment.*** I know that debugging network issues on debian is a nightmare, so i hope this helps someone.

I am building an embedded device that runs Linux (Armbian) and receives a steady stream of UDP data. It has both Ethernet and WiFi connectivity. Ethernet works fine, however when using WiFi, the data stream will occasionally appear to suddenly pause for up to a second, no data is received during this period. The packets are not lost, however, they seem to just be queued in the network driver stack somewhere. And after the pause is up, the entire backlog is dumped on the application. This would be fine if I had a reasonable buffer to work with, but my stream is very time-sensitive, I cannot afford jitter more than 50ms or so. So these pauses lead to big buffer underruns in my application. The delay is at the receiver, earlier than userspace, since tshark running there shows a gap in packets when it happens. But this gap is not present in wireshark on the client PC. It is hard to tell whether the spikes correlate with activity, since activity is very evenly distributed on the device, there is nothing else of note running on there than my application. It is not correlated with time, it seems random. Where can I begin to troubleshoot this?

I'm trying to get a standard user on my laptop installed with Linux Mint 17.3 on the wireless. I can get to the internet just fine logged in with an administrator but as soon as i log in with a standard user it asks to unlock a system setting then asks for the password for the wireless again despite my having saved it. Since anyone that uses this laptop besides me will be using the standard account, they won't have any passwords this makes it unusable for any purposes that require an internet connection. Relevant attempts to fix: 1.Adding the standard user to the netdev group - no change 2.Adding a new/second admin account - no change 3.Looked up a tutorial on the Linux Mint site titled "Connect to a wireless network as standard user without administrator authentication" - this page was completely blank Note: It is definitely not a hardware issue.

I've been trying to get my wireless working for two weeks now. I have 1814:3290 wireless card. I am on Linux Mint 14 64-bit. I have tried all the suggestion on here: https://askubuntu.com/questions/240553/how-do-i-install-ra3290-bin-wireless-driver-into-lib-firmware http://ubuntuforums.org/showthread.php?t=2104129 https://askubuntu.com/questions/240553/how-do-i-install-ra3290-bin-wireless-driver-into-lib-firmware I updated my kernel to 3.8.5-030805-generic. The first thing I tried was compiling the drivers (using original kernel 3.5.0-17-generic). When I compiled and installed, my wireless worked, but, I kept getting kernel panics every time I logged in. So I modprobe -r rt3290sta. After that I tried updating the kernel to the one I have now and copying the bin file. The kernel saw the wireless card but it was not active or anything. I checked rfkill and nothing was blocked. So then I tried compiling the drivers again after make clean first. Now when I try to compile the drivers I get this: /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:43:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rt2860_remove_one’ /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:44:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rt2860_probe’ /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:63:46: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__devinitdata’ /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:85:17: error: ‘rt2860_pci_tbl’ undeclared here (not in a function) /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:86:17: error: ‘rt2860_probe’ undeclared here (not in a function) /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:88:5: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration] /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:88:29: error: ‘rt2860_remove_one’ undeclared here (not in a function) /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:292:24: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rt2860_probe’ /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:463:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rt2860_remove_one’ /home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.c:71:1: error: ‘__mod_pci_device_table’ aliased to undefined symbol ‘rt2860_pci_tbl’ cc1: some warnings being treated as errors make: *** [/home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux/../../os/linux/pci_main_dev.o] Error 1 make: *** [_module_/home/dis/Downloads/DPO_RT3290_LinuxSTA_V2600_20120508/os/linux] Error 2 make: Leaving directory `/usr/src/linux-headers-3.8.5-030805-generic' make: *** [LINUX] Error 2 Everything is up to date also. I'm not sure where to go from here. Maybe I should downgrade my kernel to 3.6 or 3.7? Edit: So I downgrade my kernel to 3.7.2 and recompiled the drivers. The kernel sees my wireless card but doesn't really seem to work and everything freezes. Going to try kernel 3.6. Edit2: After more testing I found out that 3.7.2 and 3.6.11 both give me kernel panics after installing the wireless driver. Edi3: I installed 3.7.11 and compiled and installed the wireless drivers. Wireless worked for 3 seconds and then had a kernel panic.

I wanted to set up promiscuous Wi-Fi monitoring into Wireshark. Tried to do it like I used to with iwconfig, but this system sets me back to managed as soon as I bring the interface back up. I see online posts saying iw can add a monitor interface alongside the managed connection, so you can keep your internet alive while monitoring. Would be great, but: [loren@Gazp9 ~]$ iw dev wlp3s0 interface add mon0 type monitor command failed: Operation not permitted (-1) [loren@Gazp9 ~]$ iw phy wlp3s0 interface add mon0 type monitor command failed: No such file or directory (-2) [loren@Gazp9 ~]$ iw phy Wiphy phy0 [loren@Gazp9 ~]$ iw phy phy0 interface add mon0 type monitor command failed: Operation not permitted (-1) (That's Antergos 4.19.8-arch1-1-ARCH, if it matters.) So I dug deeper, including https://unix.stackexchange.com/questions/401464/deciphering-the-output-of-iw-list-valid-interface-combinations here. But I'm still not sure if this means there is no hope of adding the monitor interface. Here are excerpts from my "iw phy" command response: phy0 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor * P2P-client * P2P-GO * P2P-device Supported commands: * new_interface (nothing about add interface) software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ managed } sudo iw dev wlan1 station get and > sudo iw dev wlan0 set power_save on show the use of sudo? None of the "add" commands show it: > iw dev wlan0 interface add fish0 type monitor flags none But this is intellectual curiosity. I'm happy to have a working monitor and get on with the real project.

I have an old MacMini from 2009 running Debian 12 (stable). Its built-in WiFi adapter seems to be quite slow since I get around 5 Mbit/s compared to 50 Mbit/s with a newer laptop (in the same location). I therefor bought a USB WiFi adapter which presents itself as [21658.544330] usb 1-7: new high-speed USB device number 18 using ehci-pci [21658.706136] usb 1-7: New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00 [21658.706148] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [21658.706152] usb 1-7: Product: 802.11ac NIC [21658.706155] usb 1-7: Manufacturer: Realtek [21658.706158] usb 1-7: SerialNumber: 123456 According to an answer on Ask Ubuntu the driver for this adapter is included in the Linux kernel from version 6.3, however, Debian 12 currently runs version 6.1 so I followed the instructions in the answer to install the driver from GitHub: https://askubuntu.com/a/1463799 After rebooting the computer the ip link command shows that the new WiFi interface is in a dormant state. I tried to bring it up but nothing changes. How do I enable the USB WiFi adapter and disable the build-in WiFi adapter? $ sudo ip link set wlx00e04c5cc5e9 up $ ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp0s10: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether d4:9a:20:f8:dc:a8 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether 90:84:0d:f3:85:7e brd ff:ff:ff:ff:ff:ff 4: wlx00e04c5cc5e9: mtu 1500 qdisc mq state DORMANT mode DORMANT group default qlen 1000 link/ether 7e:09:b0:4f:84:ee brd ff:ff:ff:ff:ff:ff permaddr 00:e0:4c:5c:c5:e9

##Background I'm using Ubuntu 18.04 server (on a laptop, for development) and am trying to get my wifi configured to work with an WPA-EAP network. - To enable Wifi I followed the guide [Wifi on Ubuntu 18 server](https://gist.github.com/austinjp/9b968c75c3e54004be7cd7a134881d85) - I looked at the [Netplan Examples](https://netplan.io/examples) (none with WPA-EAP ) - I've read the [Netplan Full Documentation](https://github.com/CanonicalLtd/netplan/blob/master/doc/netplan.md) . I've got netplan to work with an an open network, even with a password protected network, but haven't been able to get it to work with WPA-EAP where both an identity and password are required. ##Attempted Configuration I've tried this in my /etc/netplan/config.yaml file: network: wifis: wlp1s0: dhcp4: yes access-points: "My-Enterprise-Network": auth: key-management: eap identity: johndoe1 password: pass1234 But when I run netplan apply I get: Error in network definition /etc/netplan/config.yaml: unknown key auth ##From the Documentation From the [online netplan documentation](https://github.com/CanonicalLtd/netplan/blob/master/doc/netplan.md) : The `auth` block supports the following properties: `key-management` (scalar) : The supported key management modes are `none` (no key management); `psk (WPA with pre-shared key, common for home wifi); eap` (WPA with EAP, common for enterprise wifi); and `802.1x` (used primarily for wired Ethernet connections). `password` (scalar) : The password string for EAP, or the pre-shared key for WPA-PSK. The following properties can be used if `key-management is eap` or `802.1x`: `method` (scalar) : The EAP method to use. The supported EAP methods are `tls` (TLS), `peap (Protected EAP), and ttls` (Tunneled TLS). `identity` (scalar) : The identity to use for EAP. ## From man netplan access-points (mapping) This provides pre-configured connections to NetworkManager. Note that users can of course select other access points/SSIDs. The keys of the mapping are the SSIDs, and the values are mappings with the following supported properties: password (scalar) Enable WPA2 authentication and set the passphrase for it. If not given, the network is assumed to be open. **Other authentication modes are not currently supported.** Note the last line: Other authentication modes are not currently supported. ###Questions 1. What's the right way to use netplan with WPA-EAP? 1. Does Ubuntu 18.04 ship with an outdated version of netplan? ( netplan --version is not supported ) Hence perhaps why the online documentation has options that the man version does not? 1. If so, can I upgrade netplan to a more cutting edge release? 1. Or does netplan need to be used with something like a wpa_supplicant.conf to specify additional parameters?

I'm running a fully up-to-date Fedora on a Macbook Pro. To get WiFi working in the first place, I installed akmods-wl as recommended. The WiFi works, but the connection keeps dropping. I've noticed this is especially true when there are several devices on my WiFi (when I'm the only person in the house it's usually OK although it still drops on occasion, when roommates come in with their laptops + their phones, the drop rate increases). When connection drops it's usually down for 30 seconds-1 minute before reconnecting. In worst cases this happens every couple of minutes. I have another laptop running Fedora and the WiFi is fine on there, even when there are many devices in the network. My wireless card is Broadcom BCM4331: $ lspci | grep Broadcom 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) 01:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10) 02:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) iwconfig on my wireless interface: $ iwconfig wlp2s0 wlp2s0 IEEE 802.11abg ESSID:"WINDRUSH" Mode:Managed Frequency:2.412 GHz Access Point: 44:E9:DD:0E:7F:00 Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off dmesg shows lots of these two errors: ... [11387.414926] ERROR @wl_cfg80211_get_tx_power : error (-1) [11507.449435] ERROR @wl_dev_intvar_get : error (-1) [11507.449440] ERROR @wl_cfg80211_get_tx_power : error (-1) [11627.486001] ERROR @wl_dev_intvar_get : error (-1) [11627.486008] ERROR @wl_cfg80211_get_tx_power : error (-1) [11631.113431] ERROR @wl_dev_intvar_get : error (-1) ... Couldn't find any solutions for Fedora regarding this issue. Found some from Arch Wiki and Ubuntu but they didn't work and were also dealing with different versions of the Broadcom wireless card. *(Even if no one has any clear tips for me, can someone explain what those two errors in dmesg mean?)*

I have a computer running Debian 12 (stable) that I want to connect wirelessly to the internet. The computer has a builtin WiFi adapter which uses the firmware brcmfmac4330 and is available in the package firmware-brcm80211. After having installed the firmware the interface wlan0 shows up but its state is DOWN. However, even after trying to bring it up it's still down. Also, the interface is not blocked. How can I troubleshoot this problem? $ sudo ip link set wlan0 up $ ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: end0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether d0:63:b4:00:97:0e brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc fq_codel state DOWN mode DORMANT group default qlen 1000 link/ether 4c:aa:16:fe:ca:f7 brd ff:ff:ff:ff:ff:ff $ sudo rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked $ uname -a Linux server 6.1.0-37-armmp #1 SMP Debian 6.1.140-1 (2025-05-22) armv7l GNU/Linux