[solved] NetworkManager cannot find wlan0

Myrddin · 2024-08-02 09:45:49

I used to use NetworkManager, but after I tried to start up proton VPN it completely stopped working (I have since deleted protonvpn and all its config files hoping that would fix it but to no avail). Scanning for networks results in no output.

When I run nmcli d the output is as follows:

DEVICE  TYPE      STATE                   CONNECTION 
lo      loopback  connected (externally)  lo

And the output of nmcli c is:

NAME              UUID                                  TYPE      DEVICE 
lo                c6314cd5-782a-48b5-a639-8e3d562ee672  loopback  lo     
Redmi Note 10 5G  76c2bbc0-7c25-4133-9f6b-5fcae1194271  wifi      --     
VM0645029         fe4976ca-1464-4417-a16b-fa08af5660b0  wifi      --

The device, which I'm fairly sure used to be wlan0 is no longer showing up at all when using NetworkManager, but is there when I use iwd. I do not have iwd and NetworkManager running at the same time.

Any help would be greatly appreciated. Thanks

Last edited by Myrddin (2024-08-03 15:41:01)

d_fajardo · 2024-08-02 12:45:06

Redmi Note 10 5G 76c2bbc0-7c25-4133-9f6b-5fcae1194271 wifi --
VM0645029 fe4976ca-1464-4417-a16b-fa08af5660b0 wifi --

It's possible your wlan0 got renamed to either of this. See if you can find a lead here:
https://wiki.archlinux.org/title/Networ … interfaces

seth · 2024-08-02 15:13:46

Just havin iwd installed would however prevent that.

ip a
lspci -k
rfkill

Edit to check rfkill

Last edited by seth (2024-08-02 15:14:09)

Myrddin · 2024-08-02 17:37:25

seth wrote:

Just havin iwd installed would however prevent that.
ip a
lspci -k
rfkill
Edit to check rfkill

ip a (with iwd)

1: lo: <LOOPBACK,UP,LOWER_UP> 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
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f8:54:f6:c6:1e:ce brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.178/24 metric 600 brd 192.168.0.255 scope global dynamic wlan0
       valid_lft 86398sec preferred_lft 86398sec
    inet6 fe80::fa54:f6ff:fec6:1ece/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

ip a (with NetworkManager)

1: lo: <LOOPBACK,UP,LOWER_UP> 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

lspci -k

00:00.0 Host bridge: Intel Corporation Raptor Lake-P/U 2p+8e cores Host Bridge/DRAM Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: igen6_edac
	Kernel modules: igen6_edac
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [UHD Graphics] (rev 04)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: i915
	Kernel modules: i915, xe
00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: proc_thermal_pci
	Kernel modules: processor_thermal_device_pci
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel_vsec
	Kernel modules: intel_vsec
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Alder Lake-P SATA AHCI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: ahci
00:1c.0 PCI bridge: Intel Corporation Device 51bc (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Alder Lake PCI Express x1 Root Port #10 (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: pcieport
00:1e.0 Communication controller: Intel Corporation Alder Lake PCH UART #0 (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:1e.3 Serial bus controller: Intel Corporation Alder Lake SPI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: sof-audio-pci-intel-tgl
	Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 8bba
	Kernel driver in use: intel-spi
	Kernel modules: spi_intel_pci
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less) (rev 02)
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less)
	Kernel driver in use: nvme
	Kernel modules: nvme
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller
	DeviceName: WLAN
	Subsystem: Hewlett-Packard Company Device 88e3
	Kernel driver in use: rtw89_8852be
	Kernel modules: rtw89_8852be

rfkill

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

Output for lspci -k and rfkill same with both iwd and NetworkManager

seth · 2024-08-02 19:59:29

4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

What are the other NICs, please don't filter the output, post all of it.

Wrt "with iwd/with NetworkManager" - does tha mean "enabled" or "installed"?
In doubt please post your complete system journal for a boot using NM, eg. for the previous one

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

Myrddin · 2024-08-03 15:39:29

Hmm. In order to provide the log for a boot using NM I disabled iwd and enabled NM and rebooted my laptop, and suddenly everything is working. I spent the last 3 months using iwd and now NM decides it wants to work again. Thanks for all the help!

seth · 2024-08-03 15:43:02

1. How was the NM related output in #1 obtained?
2. Is there a parallel windows installation?
3. Make sure to ever only use one network managing service (actually "per NIC") at a time, you can configure iwd as NM backend but never run NM and iwd services in parallel.

Myrddin · 2024-08-03 15:44:36

1.

nmcli d
nmcli c

2. no
3. yep only had one of iwd or NetworkManager running at a time, no clue what had happened

seth · 2024-08-03 16:13:17

I meant because of "suddenly everything is working. I spent the last 3 months using iwd"

Arch Linux

#1 2024-08-02 09:45:49

[solved] NetworkManager cannot find wlan0

#2 2024-08-02 12:45:06

Re: [solved] NetworkManager cannot find wlan0

#3 2024-08-02 15:13:46

Re: [solved] NetworkManager cannot find wlan0

#4 2024-08-02 17:37:25

Re: [solved] NetworkManager cannot find wlan0

#5 2024-08-02 19:59:29

Re: [solved] NetworkManager cannot find wlan0

#6 2024-08-03 15:39:29

Re: [solved] NetworkManager cannot find wlan0

#7 2024-08-03 15:43:02

Re: [solved] NetworkManager cannot find wlan0

#8 2024-08-03 15:44:36

Re: [solved] NetworkManager cannot find wlan0

#9 2024-08-03 16:13:17

Re: [solved] NetworkManager cannot find wlan0

Board footer