Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).
“nmcli device wifi list” command is supposed to show the list of wifi modules like uap0 and mlan0.
but in this current version of torizoncore os it isnt returning any output.
how to approach this issue and set up Wifi Access Point mode?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, it seems that the issue you’re facing is related to setting up Wi-Fi Access Point mode on a TorizonCore system with the Verdin iMX8M Plus. The error message indicates a problem with the network interface configuration, specifically that the expected Wi-Fi interfaces (like uap0 and mlan0) are not being recognized.
Here are some steps you can take to troubleshoot and potentially resolve the issue:
Verify Wi-Fi Module Compatibility: Ensure that the Wi-Fi module you are using is compatible with the Verdin iMX8M Plus and is supported by TorizonCore. You can refer to the “3rd Party Modules Tested with Toradex COMs” section in the Wi-Fi Connectivity article for a list of tested modules.
Check Interface Names: The interface names (uap0, mlan0) might differ based on the kernel driver and userspace configuration. Use the ip link or nmcli device command to list all network interfaces and verify their names.
Kernel and Driver Configuration: Ensure that the necessary kernel modules and drivers for your Wi-Fi module are loaded. You might need to check the kernel configuration to ensure that the required drivers are enabled.
NetworkManager Configuration: The error message suggests a mismatch in the interface name. Check the NetworkManager configuration to ensure that the correct interface names are being used in the connection profiles.
Logs and Diagnostics: Check system logs (journalctl -xe) for any additional error messages or warnings that might provide more context on the issue.
TorizonCore Version: Since you are using a nightly version of TorizonCore, consider testing with a stable release to see if the issue persists. Nightly builds might have unresolved issues or changes that could affect functionality.
If these steps do not resolve the issue, you may need to reach out to Toradex technical support for further assistance, as they can provide more specific guidance based on your hardware and software configuration.
Please, also check if these links can help you solve your problem:
Just to clarify, in this article of ours that you are referencing, are you following “Method 1” or “Method 2” for configuring wi-fi access point mode?
Could you try with “Method 2: Hostapd”, instead. I believe there are some issues with the access point interface and how it interacts with NetworkManager. Last time I tried this I used the Hostapd method and it worked from what I can recall. Though this was on a newer Torizon 6.X version. I just noticed you are using a nightly 5.7.7 version.
May I ask why you are still on the old 5.X series?
I’ve tried both the method 1 and 2, torizoncore preempt RT 5.7.7 & 5.7.6 seems to have some issue with WiFi interface.
Now I have installed TorizonCore 6.8.0, in this version wifi interfaces were accessible and I’ve enabled both static-ip and wifi access point mode. But in our custom development board the device tree is not deploying properly. only ethernet0 is enabled.
we require two ethernet port for our application that is to be configured as EtherCAT.
Reason for using 5.X series, is to maintain uniformity across all our SoMs and certain packages works only with particular kernel version of torizoncore. Though i installed 6.8.0 now, i’m yet to check the compatibility with our other packages.
Please suggest how to approach the device tree issue in 6.8.0 or wifi in 5.7.X
Also it would be appreciated if you provide the details of the torizoncore that is compatible with the verdin imx8m plus 1.1 b
Please suggest how to approach the device tree issue in 6.8.0 or wifi in 5.7.X
Well the device tree issue is probably because of the kernel version difference between 6.X and 5.X. If you just copied the device tree you used in 5.X and tried to use that for 6.X there are probably some incompatibilities in your device tree that would need to be changed and updated to account for the newer kernel.
As for the WiFi issue, I’m not sure specifically what WiFi issue you are referring to. That said it should be noted that the 5.X series is more or less end-of-life (EoL) at this point. If there really is an issue, then we don’t plan to be updating or fixing anything in that series anymore.
Also it would be appreciated if you provide the details of the torizoncore that is compatible with the verdin imx8m plus 1.1 b
I’m not sure what you mean by this. The Verdin i.MX8M Plus should be supported by all current releases of Torizon OS/TorizonCore as of now.
By the term, wifi issue I’m referring to the wifi interfaces like mlan0 or uap0 not being available in 5.7.x series. Now that I have updated to the core is 6.8.0, wifi interfaces are available. And I’m able to configure wifi Access point mode for verdin.
Still I’m not able to configure the Ethernet ports in the customized carrier board. But the device tree was successfully deployed on the verdin development board.
As I said before. You probably designed your device tree for the older kernel used in the 5.X series. If you want similar results in 6.X you need to rebase your changes and adjust your device tree so that it is in-line with 6.X. If you compare the 5.X and 6.X device trees quite a number of things changed. Therefore you must adapt to the changes.
