AX210 on Orin Nano (Jetpack 6.2.1, Kernel 5.15): iwlwifi loads but 802.11k/v/r (Fast Roaming) capabilities are missing

Hi Nvidia and Fellow developer,

I’m working on a project with a Jetson Orin Nano that requires seamless Wi-Fi roaming for a mobile application. I’ve set up a mesh network with three routers, and now I’m trying to ensure the Jetson device properly supports 802.11k/v/r (Fast Roaming).

My Setup:
Device: Jetson Orin Nano Developer Kit
Jetpack Version: Jetpack 6.2.1
Kernel Version: 5.15.148
Wi-Fi Card: Intel AX210 M.2 card

The Core Problem:

The default Jetpack 6.2.1 kernel does not include the iwlwifi driver for Intel cards. I have successfully cross-compiled the iwlwifi module from the official NVIDIA kernel sources and loaded it onto my Jetson. The Wi-Fi card is detected and works for basic connectivity.

However, my goal is to enable 802.11k/v/r for seamless roaming. When I check the device’s capabilities, these features are missing.

# These commands return no output
$ iw list | grep -i "Neighbor Report"
$ iw list | grep -i "BSS Transition"
$ iw list | grep -i "Fast BSS Transition"

Investigation and Troubleshooting Steps:

I’ve spent a considerable amount of time diagnosing this, and here’s what I’ve found. The key issue seems to be a mismatch between the iwlwifi driver and the firmware it tries to load.

The dmesg log shows a critical warning:

$ sudo dmesg | grep iwlwifi
...
[   11.934833] iwlwifi 0001:01:00.0: api flags index 2 larger than supported by driver
[   11.935239] iwlwifi 0001:01:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm
...

This “api flags… larger than supported” message strongly suggests that the iwlwifi driver from the Kernel 5.15 source is too old for the modern firmwares (v66) available in the linux-firmware package.

I then systematically tried forcing the driver to load older firmware versions (v63, v62, v59) by using symbolic links.

Firmware v63 & v62: The “api flags” warning persisted.

Firmware v59: The driver failed to initialize completely, resulting in a kernel panic within the module and no Wi-Fi interface. The log showed Failed to start RT ucode: -110.

This leads me to believe that the iwlwifi driver within the L4T 36.4.4 kernel source is fundamentally too old to correctly handle any available AX210 firmware for advanced features.

My Questions for the Community:

Has anyone successfully enabled 802.11k/v/r on an Intel AX210 card with Jetpack 6.2.1? If so, what combination of kernel source, driver configuration (.config), and firmware version did you use?

Is there a recommended patch or a specific kernel source branch I should use to compile a more up-to-date iwlwifi driver that is compatible with the Jetson’s 5.15 kernel?

Are there any specific kernel configuration options (CONFIG_…) related to iwlwifi or mac80211 that must be enabled during compilation to expose the 802.11k/v/r capabilities? I used the default tegra_defconfig and enabled the iwlwifi modules.

I’m at a point where I’ve confirmed basic driver compilation works, but I’m stuck on enabling these crucial roaming features. Any guidance, pointers, or shared experiences would be incredibly helpful.

Thank you in advance!

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

Additional driver may be required for the component. You may check
Jetson/L4T/r36.3.x patches - eLinux.org
Jetson/L4T/r36.4.x patches - eLinux.org

Hi kayccc,

Thank you for your response.

To answer your question: Yes, this is still an unresolved issue, and I would appreciate your support. I have not made any progress since my original post.

I have carefully checked the L4T r36.3 and r36.4 patch lists you shared. Unfortunately, I could not find any patches related to updating the iwlwifi driver or specifically addressing 802.11k/v/r support. My issue isn’t about a missing driver for the component—I successfully compiled the iwlwifi module from the provided kernel sources—but rather that the driver version itself appears to be outdated.

As detailed in my original post, the key evidence is the dmesg warning: api flags index 2 larger than supported by driver. This strongly suggests that the iwlwifi driver from the Kernel 5.15 source is fundamentally incompatible with the modern firmware required by the Intel AX210 to enable fast roaming features (802.11k/v/r).

To help me move forward, could the team please address my original questions? To reiterate, I’m trying to find out:

  1. Can you confirm if the iwlwifi driver in the L4T 36.4.4 (Kernel 5.15) source is known to be too old to support the firmware APIs needed for 802.11k/v/r on the AX210?
  2. Is there an official or recommended method to update/backport a newer iwlwifi driver to the Jetson’s 5.15 kernel?
  3. Has anyone internally at NVIDIA successfully enabled these features on this hardware? If so, what specific driver and firmware combination was used?

This functionality is critical for our mobile application. Any specific insights or guidance from the kernel development team would be extremely valuable.

Thank you for your continued support.

Hi,
Could you please consult with the vendor to get further information? We don’t have the module and are not able to provide further suggestion. This would need other users to share experience.

Hi DaneLLL,

Thank you for your reply.

I understand the suggestion to consult the vendor. However, I must respectfully clarify that this is not an issue with the Intel hardware, but rather an issue with the software support for it within NVIDIA’s L4T kernel.

To put it simply:

  • The Intel AX210 card and its 802.11k/v/r features work perfectly on standard Linux distributions (e.g., Ubuntu on a laptop) with a modern kernel. This confirms the hardware is not the problem.

  • The problem is that the iwlwifi driver provided in the L4T Kernel 5.15 source is too old to support the modern firmware that this card requires for advanced features. The dmesg error I provided (api flags... larger than supported by driver) is the definitive proof of this driver-firmware incompatibility.

In this scenario, NVIDIA is the vendor of the Board Support Package (BSP) and the customized kernel for the Jetson platform. The responsibility for ensuring that core kernel drivers can support common, modern peripherals lies with the L4T development team.

This is not just a minor issue for a single user. The Jetson platform is a leader in robotics and mobile autonomous systems. For any mobile robot, vehicle, or drone, seamless Wi-Fi roaming (802.11k/v/r) is a critical feature for maintaining stable command, control, and data links while moving through a facility. The lack of support for this fundamental feature in the official L4T kernel is a significant limitation for many real-world applications.

Therefore, my question is not for Intel, but for the NVIDIA kernel team:

Could you please escalate this issue to the L4T kernel development team? They are the ones with the expertise to confirm that the iwlwifi driver is outdated and to provide guidance on either patching it, backporting a newer version, or including an update in a future Jetpack release.

Thank you for your understanding and for helping to get this critical issue to the right team.

Hi,
We suggest contact with vendor of the module. See how to enable it on Kernel 5.15. It is standard upstream kernel version 5.15 in Jetpack 6 releases.

Is there any plan to upgrade the kernel version to 6.XX in Jetpack 7 or 8 releases in coming years by NVidia? so that such driver/firmware compatibility issues are resolved for the new hardware modules

1 Like

Hi DaneLLL,

Thank you. I believe @nagesh_accord 's comment gets to the heart of the matter.

The core issue is not about enabling a specific module on Kernel 5.15, but the limitations of Kernel 5.15 itself.

My question is now the same: Does NVIDIA have a roadmap to upgrade the kernel in a future Jetpack release? This would be the most effective solution for this and many other modern hardware compatibility issues.

1 Like

Hi,
We will have future Jetpack release with later kernel for Orin series in 2026. This is under planning and no concrete timeline yet.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.