Jetson Orin Nano - No WiFi

[pquack]

So I can’t seem to get the wifi to work.

This is a jetson orin nano on the developer kit.

lspci -v shows this:

0001: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
	Flags: fast devsel, IRQ 255
	I/O ports at 1000 [disabled] [size=256]
	Memory at 20a8000000 (64-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-c8-22-01
	Capabilities: [158] Latency Tolerance Reporting
	Capabilities: [160] L1 PM Substates
	Kernel modules: rtl88x2ce

lshw -class network shows this:

  *-network UNCLAIMED       
       description: Network controller
       product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0001:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
       resources: ioport:1000(size=256) memory:20a8000000-20a800ffff

wlan0 is not in ifconfig

sudo modprobe rtl88x2ce returns peter@ubuntu:~$ sudo modprobe rtl88x2ce modprobe: FATAL: Module rtl88x2ce not found in directory /lib/modules/5.15.136-tegra.

Any ideas what the problem could be?

Ethernet works fine.

[DaneLLL]

Hi,
We don’t observe the issue on Orin Nano developer kit with Jetpack 6.0GA. Do you install the system through SDKManager? If you use the default system image, it should be working just fine.

[WayneWWW]

If lspci already showed the wifi card detected and rtl88x2ce in use, then you don’t need to modprobe rtl88x2ce again…

ifconfig -a to see if wlan0 is there…

[pquack]

peter@ubuntu:~$ ifconfig -a
can0: flags=128<NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 202  

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:6cff:fe77:2e1b  prefixlen 64  scopeid 0x20<link>
        ether 02:42:6c:77:2e:1b  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12686  bytes 2273543 (2.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.127  netmask 255.255.240.0  broadcast 192.168.15.255
        inet6 fd99:618c:94d:a34b:beed:3175:8e4:c22f  prefixlen 64  scopeid 0x0<global>
        inet6 fd99:618c:94d:a34b:a9f5:ba65:3766:4432  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::37b8:3868:a69b:a998  prefixlen 64  scopeid 0x20<link>
        ether 48:b0:2d:eb:c8:fc  txqueuelen 1000  (Ethernet)
        RX packets 1472093  bytes 674216456 (674.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 494769  bytes 72972656 (72.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 238  base 0x5000  

l4tbr0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 3e:c7:e7:79:f3:87  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 37994  bytes 5142455 (5.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 37994  bytes 5142455 (5.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether be:c5:e5:70:ad:e1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether be:c5:e5:70:ad:e3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethb561ebe: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::d05b:9dff:fea2:15f2  prefixlen 64  scopeid 0x20<link>
        ether d2:5b:9d:a2:15:f2  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12959  bytes 2300832 (2.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I don’t have a wlan0 anymore.

[WayneWWW]

then please share the full dmesg

[DaneLLL]

Hi,
Since we set up developer kit and don’t hit the issue, you may consider re-flash the system and see whether it works or not.

[pquack]

Ok. I re-flashed it and mostly working now.

A weird thing (and I don’t know how to diagnose it … possibly my router) but wpa_supplicant crashes every now and then. You can kill it and reset the wireless and it will work again. The crash generally happens during a heavy download. It will just stop working, and need a reset.

But that’s a somewhat minor annoyance.