forked from lalithsuresh/odin
-
Notifications
You must be signed in to change notification settings - Fork 17
Solving potential problems with the auxiliary interface
Jose Saldana edited this page May 8, 2018
·
1 revision
One problem may appear in some deployments, when using an auxiliary interface:
Sometimes, when trying to reboot the Archer devices, the auxiliary USB wireless interface is not created properly. As a consequence, when the start script on the applications is run, the following output is obtained:
Setting variables
Setting interfaces
ifconfig: SIOCGIFFLAGS: No such device
command failed: No such file or directory (-2)
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCSIFMTU: No such device
ifconfig: SIOCGIFFLAGS: No such device
Restarting OpenvSwitch
Now you can launch the Wi-5 odin controller and press Enter
This issue appears after one reboot and is repeated after subsequent reboots.
In order to solve this problem, you have to disable and enable the USB port on which the auxiliary device is placed.
To do this we execute the commands below:
echo 0 > /sys/class/gpio/gpio21/value
echo 1 > /sys/class/gpio/gpio21/value
After these commands are run, we rebooted the Archer AP again and the problem will be fixed. If the problem persists, repeat this process again until the USB interface is detected.