wlan0 not being recognized

[rintaro001]

wlan0 not being recognized. "ip -a" returns only lo, wan0 and lan0.

[tacomilkshake]

Same issue here, but I resolved with:

sudo apt install iwd
sudo systemctl enable iwd --now
sudo iwctl device list
sudo iwctl station wlp1s0 show

Oddly, I often have intermittency with this command showing the card, and sometimes not!

sudo lspci | grep 'Wireless'

[libresurf]

Same issue here.

@tacomilkshake, have you got the optional M.2 Key E 2230 Wireless and Bluetooth Combo Module ? or do you use a USB wifi dongle ?

With the optional M.2 Wifi/Bluetooth module, your trick doesn't work for me.

It seems that the Wifi module is not powered on, so the command lspci doesn't see it.
I think that the solution would be in the device tree (rk3568-nanopi5.dts) but I didn't manage to activate it :

m2_wlan_radio: m2-wlan-radio {
	compatible = "rfkill-gpio";
	type = "wlan";
	shutdown-gpios = <&gpio2 RK_PD2 GPIO_ACTIVE_HIGH>;
};

[inindev]

@tacomilkshake, have you got the optional M.2 Key E 2230 Wireless and Bluetooth Combo Module ? or do you use a USB wifi dongle ?

This is a good point, the R5C has a M.2 Key E 2230 slot, the R5S does not. To be sure everyone is talking about the same issue, can we confirm the R5 model and the interface?

[libresurf]

Hello @inindev,

I've got the R5C with the optional Wifi/Bluetooth combo module (AzureWave AW-CB375NF) on the M.2 Key E 2230 slot.
Do you have one?

[inindev]

I have an R5C but have never put a wifi card in the Key E. I can do that tomorrow.

[libresurf]

I have an R5C but have never put a wifi card in the Key E. I can do that tomorrow.

Thanks.

[tacomilkshake]

Confirming I do indeed also have a R5C with the M.2 Key E 2230 Wireless and Bluetooth Combo Module.

It's odd it seems about 50/50 on boot whether I can get the device to show up using sudo lspci | grep 'Wireless'.

When it does, I can use iwd/iwctl to configure and connect to WLAN.

I tried adding a variety of drivers: firmware-realtek, non-free misc, etc. Unfortunately, none improved the reliably of the device appearing (and being usable). Though, I believe this kernel should include the driver...

[inindev]

any chance a pci device rescan helps this?

echo "1" > /sys/bus/pci/devices/DDDD\:BB\:DD.F/remove
sleep 1
echo "1" > /sys/bus/pci/rescan

[libresurf]

echo "1" > /sys/bus/pci/rescan

Whaou !
This made the card visible to lscpi !!! :-D

root@nanopi:~# lspci
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0000:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0002:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)

how can we make this permanent?

[inindev]

This made the card visible to lscpi !!! :-D

Good news there is a solid work-around until a permanent solution is found.

how can we make this permanent?

The easiest solution would be to make /etc/rc.local (and mark it executable) with this command in there.

[libresurf]

OK, but the wifi is not yet operational.
The command iw list shows nothing.

[tacomilkshake]

Try using iwd once it appears in the lspci list; that’s what worked for me. I’m guessing iwd is doing the extra configuration needed to enable the device. I couldn’t get base networking to recognize it, nor using NetworkManager.

…

On Sat, Dec 30, 2023, at 11:24, libresurf wrote: OK, but the wifi is not yet operational. The command *iw list* shows nothing. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN5RBS4YO4T6VBD4NPC5QDYMBS57AVCNFSM6AAAAAA63OIQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGU4DQMRTGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[inindev]

Try using iwd once it appears in the lspci list; that’s what worked for me. I’m guessing iwd is doing the extra configuration needed to enable the device. I couldn’t get base networking to recognize it, nor using NetworkManager.

Also, does dmesg tell you anything like it is missing firmware? Is your e-key a realtek device?

I minimize the firmware in the image to keep it small as it can easily be installed later. Ensure non-free is enabled in /etc/apt/sources.list

apt install firmware-realtek

I generally use wpasupplicant:

apt install wireless-regdb wpasupplicant

[libresurf]

lspci shows no driver in use for the wifi card :

root@nanopi:~# lspci -k
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
        Kernel driver in use: pcieport
0000:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
        Subsystem: AzureWave RTL8822CE 802.11ac PCIe Wireless Network Adapter
        Kernel modules: rtw88_8822ce
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
        Kernel driver in use: pcieport
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
        Kernel driver in use: r8169
        Kernel modules: r8169, r8125
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
        Kernel driver in use: pcieport
0002:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
        Kernel driver in use: r8169
        Kernel modules: r8169, r8125

[inindev]

This should take care of it then:

apt install firmware-realtek