How about, lets see what systemd says:
sudo systemctl start wpa_supplicant
systemctl status wpa_supplicant
and then:
journalctl | grep wpa
Regards,
root@beaglebone:~# sudo systemctl start wpa_supplicant
root@beaglebone:~# systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled)
Active: active (running) since Sun 2015-04-26 20:47:58 CEST; 11s ago
Main PID: 2747 (wpa_supplicant)
CGroup: /system.slice/wpa_supplicant.service
└─2747 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
Apr 26 20:47:58 beaglebone wpa_supplicant[2747]: Successfully initialized wpa_s…t
Hint: Some lines were ellipsized, use -l to show in full.
root@beaglebone:~# journalctl | grep wpa
Apr 26 20:47:58 beaglebone sudo[2744]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start wpa_supplicant
Apr 26 20:47:58 beaglebone wpa_supplicant[2747]: Successfully initialized wpa_supplicant
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: Successfully initialized wpa_supplicant
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: Could not set interface wlan0 flags (UP): No such file or directory
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: nl80211: Could not set interface ‘wlan0’ UP
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: Could not set interface wlan0 flags (UP): No such file or directory
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: WEXT: Could not set interface ‘wlan0’ UP
Apr 26 20:48:58 beaglebone wpa_supplicant[2760]: wlan0: Failed to initialize driver interface
It is a Driver problem then? :S
Thanks and Regards!
I solved the issue and just in case someone has it also this is what I did:
debian@beaglebone:~$ lsusb
Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
debian@beaglebone:~$ sudo dmesg -c > /dev/null
debian@beaglebone:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
debian@beaglebone:~$ sudo dmesg -c
[ 593.724806] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file ‘rt2870.bin’
[ 593.724912] ieee80211 phy0: rt2x00lib_request_firmware: Error - Failed to request Firmware
→ A firmware problem??? shhhhit yes! :S
just install new drivers and problem solved!
sudo apt-get install firmware-ralink
And then configure it as usual:
sudo wpa_passphrase my_ssid my_password
sudo nano /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wpa-ssid “my_ssid”
wpa-psk “my_generated_pswd”
sudo ifup wlan0
Thanks for your support Robert.
By the way, I did this on your hot new one release 
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-26/console/BBB-eMMC-flasher-debian-8.0-console-armhf-2015-04-26-2gb.img.xz
In other hand, in here there is a supersized file, probaly something was wrong with it:
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-26/console/
Best regards!
I solved the issue and just in case someone has it also this is what I did:
debian@beaglebone:~$ lsusb
Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070
Wireless Adapter
debian@beaglebone:~$ sudo dmesg -c > /dev/null
debian@beaglebone:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
debian@beaglebone:~$ sudo dmesg -c
[ 593.724806] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading
firmware file 'rt2870.bin'
[ 593.724912] ieee80211 phy0: rt2x00lib_request_firmware: Error - Failed to
request Firmware--> A firmware problem??? shhhhit yes! :S
just install new drivers and problem solved!
sudo apt-get install firmware-ralink
Oh sorry about that, yeah the console lacks firmware...
And then configure it as usual:
sudo wpa_passphrase my_ssid my_password
sudo nano /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wpa-ssid “my_ssid”
wpa-psk “my_generated_pswd”
sudo ifup wlan0
Thanks for your support Robert.
By the way, I did this on your hot new one release
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-26/console/BBB-eMMC-flasher-debian-8.0-console-armhf-2015-04-26-2gb.img.xzIn other hand, in here there is a supersized file, probaly something was
wrong with it:
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-26/console/
Found it, i used the big target config for the beaglebone console image..
So, it pulled in 60mb's of drivers/etc that are included with the big
desktop image..
Regards,
Now everything make sense I will take this into consideration for other devices then. It is OK the minimalism for the console release. Thanks for your work! regards.
Hello Robert and Everyone.
I’m a newbie with beaglebones black running debian…
I’m having a problem with connman and the interfaces file.
The problem arises with a beaglebone black rev c and the image BBB-eMMC-flasher-debian-8.3-iot-armhf-2016-03-13-4gb.img, but also happened with BBB-eMMC-flasher-debian-8.3-lxqt-4gb-armhf-2016-03-13-4gb.img.
The same beaglebone worked with a debian wheezy image installed…
Here is the problem: I cannot access the network through eth0.
I’ve found the instructions in this thread and removed connman, but the problem remains.
I have the following configuration on the beaglebone:
**** /etc/network/interfaces file:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet static
address 192.168.20.79
netmask 255.255.255.0
network 192.168.20.0
broadcast 192.168.20.255
gateway 192.168.20.1
dns-name-servers 192.168.20.200
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1
**** /etc/resolv.conf:
nameserver 192.168.20.200
nameserver 8.8.8.8
nameserver 4.4.4.4
**** ifconfig command returns:
eth0 Link encap:Ethernet HWaddr 54:4a:16:f0:f1:f0
inet addr:192.168.20.79 Bcast:192.168.20.255 Mask:255.255.255.0
inet6 addr: fe80::564a:16ff:fef0:f1f0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2652 errors:0 dropped:1 overruns:0 frame:0
TX packets:2218 errors:16 dropped:63 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:272369 (265.9 KiB) TX bytes:15461 (15.0 KiB)
Interrupt:175
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:388 errors:0 dropped:0 overruns:0 frame:0
TX packets:388 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36764 (35.9 KiB) TX bytes:36764 (35.9 KiB)
usb0 Link encap:Ethernet HWaddr 54:4a:16:f0:f1:f1
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::564a:16ff:fef0:f1f1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:886 errors:0 dropped:5 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:129397 (126.3 KiB) TX bytes:9712 (9.4 KiB)
***** iptables -L command returns:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
**** route -n command returns:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.20.1 0.0.0.0 UG 0 0 0 eth0
192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0
192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
REMARK: The first route I added manually - when the beaglebone boots, it was not configured, just the last two.
I cannot ping the beaglebone from another computer.
I cannot ping another computer from the beaglebone.
What am I missing?
Thanks in advance…
Regards,
Daniel.