Keysight Technologies U3810A, Getting Started Manual

Page: 98 / 134

Keysight U3810 Series Getting Started Guide 98
Wi-Fi Disabled
An improper sequence may disable Wi-Fi in such a way that it looks permanently disabled.
debian@beaglebone:~/temp/LabCode$ connmanctl
Error /net/connman/technology/wifi: No carrier
connmanctl>exit
debian@beaglebone:~$ rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
1
If the Wi-Fi was blocked by the
rfkill
command without a reboot,
rfkill unblock wifi
will
restore it. However, if there was a reboot or power down, after unblocking an additional reboot
will be required.
2 If the wireless is turned off in the /boot/uEnv.txt, then it will not show up as a technology
available in the connmanctl control system.
debian@beaglebone:~/temp$ connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided
by any connmanctl> scan wifi
Error /net/connman/technology/wifi: Method "Scan" with signature "" on
interface "net.connman.Technology" doesn't exist
connmanctl> technologies
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = False
Tethering = False
connmanctl>
3 Use cat to examine /boot/uEnv.txt and make sure the disable wireless has a “ # ” in front of the
line. This is the normal configuration for the disable section of the uEnv.txt file. If necessary, use
the
nano editor
[1]
to make the change.
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
WARNING
It is important to always execute the command rfkill unblock wlan after completing
the procedure in which you used the command rfkill block wlan . This must always
be done before your BeagleBone CPU is shutdown or rebooted.
The same is true for bluetooth
.