Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 335 subscribers
  • Views 635 views
  • Users 0 members are here
Related

Connect to webserver error

luciaom_02

Hello, I’m using a ultra96-V2 board and I’m trying to set up the wifi connection, following the guide and I’m running into some problems.
I’m reading chapter 8, “Connect to Webserver”, but I can’t set up the network called Ultra96-V2_<MAC_ADDRESS>. When I run ./wifi.sh, I get an error with the configuration of the LAN:

root@ultra96v2-2020-1:~# ./wifi.sh
Stopping Connection Manager
ifdown: interface wlan0 not configured
Successfully initialized wpa_supplicant
[ 85.017404] power up request for already powered up source Wifi
[ 85.023330] Device already up. request source is Wifi
[ 85.028409] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
[ 85.034600] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
Could not set interface wlan0 flags (UP): Invalid argument
nl80211: Could not set interface 'wlan0' UP
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface

When I run this file step by step, I get an error when I run ifdown and I get the following output:

ifdown: interface wlan0 not configured

I have tried using ip link set wlan0 down instead and that seems to work and doesn’t report any error. 

Then if I keep running the wifi.sh script, one command at a time, it raises an error when reaching ifup.
When I run either ifup wlan0 or ip link set wlan0 up, I get the following error:

[ 883.500230] power up request for already powered up source Wifi
[ 883.506161] Device already up. Request source is Wifi
[ 883.511239] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
[ 883.517421] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
RTNETLINK answers: Invalid argument


Perhaps, is the ploblem in the wifi/bluethoot module? Is there any step that I‘m skipping? Could there be a file incompatibility problem?

Has anyone had the same problem?

  • 0

    It seems like you are encountering issues with the WiFi setup on your Ultra96-V2 board. The error messages suggest that there might be a problem with the WiFi module or the configuration.

    Let's try to troubleshoot the issue step-by-step:

    Double-check if the WiFi/Bluetooth module is properly connected to the Ultra96-V2 board. Ensure that all connections are secure and there are no loose connections.

    The error messages include "power up request for already powered up source Wifi." This could indicate that the WiFi module is already powered up. However, the script is trying to power it up again, leading to an error. Ensure that there are no conflicts in the power control for the WiFi module.

    The error "Failed to get mac address" could indicate a problem with the driver for the WiFi module. Ensure that the appropriate driver is loaded for the WiFi module. You may need to check the kernel configuration and make sure the required driver is enabled.

    The script reports issues related to the MAC address. Verify that the MAC address is correctly assigned to the WiFi interface (wlan0). If the MAC address is not assigned, the interface may not work correctly. Check if the MAC address is properly configured in the network interface settings.

    The error "Could not set interface wlan0 flags (UP): Invalid argument" suggests a problem with setting up the network interface. Double-check the network interface configuration files to ensure they are correctly set up.


    Ensure that you are running the wifi.sh script with appropriate permissions and as a superuser (root) to avoid any permission-related issues.


    Make sure you are using the correct software versions and configurations. Check for any incompatibility between the Ultra96-V2 board, WiFi module, and the software you are using. Verify if there are any specific instructions or patches required for your specific setup.


    Ensure that all required dependencies, libraries, and packages are installed for the WiFi setup.

  • 0 in reply to bidrohini

    Thank you for your help.
    Unfortunately, we have followed all the steps you advised and are still running into exactly the same issue.
    We are going to try to get it changed for a new one.