Jetpack 4.2 wifi hotspot problems

Since I updated to 4.2 I have seen wifi hotspot issues. Especially with 5GHz, but with 2.4GHz a well. Even if the signal strength is sufficient - any connection just timeouts or shows deauth. And then at one point (can be minutes or hours after boot) it will not respond at all. It could be related to https://devtalk.nvidia.com/default/topic/1039317/jetson-tx2/tx2-as-wireless-ap-drops-connections-randomly/ or https://devtalk.nvidia.com/default/topic/1038939/wireless-hotspot-random-failure-right-after-boot/?offset=7.

Dmesg log where it happens: https://pastebin.com/cSrXdJn8 (cannot post here because it is too long).

The issue starts at 72 second. At about that time it was no longer possible to connect. It did show up as hotspot on other devices but on connect it just timeouts. At 329 we connected monitor to get more info.

Also tried changing /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf to disable power saving - it didn’t work.

Another log just a network manager restart later where it happened again: https://pastebin.com/8b8jZrnF - first part is the same as first log (first disconnect at 72), then another at about 2834. When monitor is plugged in (hdmi: plugged) then it just happened. So it can happen multiple times in one boot.

Any ideas? Because this is seriously hurting us.

Client connecting to the AP shows this:

[172392.966430] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 1/3)
[172393.042464] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 2/3)
[172393.136939] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 3/3)
[172393.215974] wlp3s0: authentication with 00:04:4b:c5:e3:2e timed out
[172396.898286] wlp3s0: authenticate with 00:04:4b:c5:e3:2e
[172396.904855] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 1/3)
[172396.970418] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 2/3)
[172397.019812] wlp3s0: send auth to 00:04:4b:c5:e3:2e (try 3/3)
[172397.085774] wlp3s0: authentication with 00:04:4b:c5:e3:2e timed out

The only thing that fixes this is network manager restart. I have this on all tx2’s with Jetpack 4.2. I use default BSP.

I updated OP with new logs.

Hi Dalus,

Did you ever end up finding a solution for this, as I am experiencing something similar?

Any update yet?

Hi,

I am having the same issue. I have about 6 TX2 devices running JetPack 4.2 L4T 32.1 and I am trying to connect to a private network with static IP’s and they will just not connect. I’ve tried all variations of settings and know for a fact the subnet and gateway are correct. I’ve worked with our IT on this issue and it is still not working and is holding us back from critical development.

Please assist as its an issue with the JetPack driver from Nvidia it seems like for WIFI.