I understand from other threads that this is not the best nic for the BBB,
and I'll waste no time replacing it. However, I would like to ask for help
understanding the syslog entries that result
I have Debian Jessie installed on a BBB Rev C,
root@beaglebone:~# uname -a
Linux beaglebone 3.14.26-ti-r39 #1 SMP PREEMPT Mon Dec 8 01:52:29 UTC 2014
armv7l GNU/Linux
This is a fresh install with the firmware-realtek package installed and the
connman package removed. Also IPv6 networking is disabled.
At the moment this BBB is powered and the Realtek RTL8188CUS is attached to
a USB hub:
root@beaglebone:~# lsusb
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS
802.11n WLAN Adapter
Bus 001 Device 003: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And it is not working. I've put the device at 192.168.1.11 and have
another at 192.168.1.106:
root@beaglebone:~# ping 192.168.1.106
PING 192.168.1.106 (192.168.1.106) 56(84) bytes of data.
>From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
>From 192.168.1.10 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.10 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.1.106 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
I include that ping data because one might otherwise think the card is up:
root@beaglebone:~# ifconfig
. . .
wlan0 Link encap:Ethernet HWaddr 00:f1:40:25:06:a7
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7359 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2116131 (2.0 MiB) TX bytes:5245 (5.1 KiB)
and
root@beaglebone:~# iwconfig
wlan0 IEEE 802.11bgn ESSID:"home"
Mode:Managed Frequency:2.437 GHz Access Point:
C8:B3:73:0F:F4:CC
Bit Rate=18 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-38 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:68 Missed beacon:0
Actually, the card did not come up at boot, as explained by these syslog
lines:
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: Successfully initialized
wpa_supp
plicant
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: Could not read interface
wlan0 ff
lags: No such device
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: nl80211: Driver does not
supportt
authentication/association or connect commands
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: Could not read interface
wlan0 ff
lags: No such device
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: Could not read interface
wlan0 ff
lags: No such device
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: WEXT: Could not set
interface 'ww
lan0' UP
Dec 13 05:51:28 beaglebone wpa_supplicant[272]: wlan0: Failed to initialize
drivv
er interface
And ifup also appears to fail:
root@beaglebone:~# ifup wlan0
RTNETLINK answers: File exists
Failed to bring up wlan0.
But the syslog entries don't seem to reflect that:
Dec 13 05:55:24 beaglebone wpa_supplicant[2155]: Successfully initialized
wpa_suu
pplicant
Dec 13 05:55:24 beaglebone kernel: [ 252.758943] rtl8192cu: MAC auto ON
okay!
Dec 13 05:55:24 beaglebone rsyslogd-2007: action 'action 17' suspended,
next rett
ry is Sat Dec 13 05:55:54 2014 [try http://www.rsyslog.com/e/2007 ]
Dec 13 05:55:24 beaglebone kernel: [ 252.807746] rtl8192cu: Tx queue
select: 0xx
05
Dec 13 05:55:25 beaglebone kernel: [ 253.385326] IPv6:
ADDRCONF(NETDEV_UP): wlaa
n0: link is not ready
Dec 13 05:55:25 beaglebone avahi-daemon[382]: Joining mDNS multicast group
on inn
terface wlan0.IPv4 with address 192.168.1.11.
Dec 13 05:55:25 beaglebone avahi-daemon[382]: New relevant interface
wlan0.IPv4
for mDNS.
Dec 13 05:55:25 beaglebone avahi-daemon[382]: Registering new address
record forr
192.168.1.11 on wlan0.IPv4.
Dec 13 05:55:26 beaglebone wpa_supplicant[2161]: wlan0: SME: Trying to
authenticc
ate with c8:b3:73:0f:f4:cc (SSID='home' freq=2437 MHz)
Dec 13 05:55:26 beaglebone kernel: [ 254.625557] wlan0: authenticate with
c8:b33
:73:0f:f4:cc
Dec 13 05:55:26 beaglebone kernel: [ 254.693055] wlan0: send auth to
c8:b3:73:00
f:f4:cc (try 1/3)
Dec 13 05:55:26 beaglebone wpa_supplicant[2161]: wlan0: Trying to associate
withh
c8:b3:73:0f:f4:cc (SSID='home' freq=2437 MHz)
Dec 13 05:55:26 beaglebone kernel: [ 254.697889] wlan0: authenticated
Dec 13 05:55:26 beaglebone kernel: [ 254.705475] rtl8192cu 1-1.3:1.0
wlan0: diss
abling HT/VHT due to WEP/TKIP use
Dec 13 05:55:26 beaglebone kernel: [ 254.705518] rtl8192cu 1-1.3:1.0
wlan0: diss
abling HT as WMM/QoS is not supported by the AP
Dec 13 05:55:26 beaglebone kernel: [ 254.705540] rtl8192cu 1-1.3:1.0
wlan0: diss
abling VHT as WMM/QoS is not supported by the AP
Dec 13 05:55:26 beaglebone kernel: [ 254.716288] wlan0: associate with
c8:b3:733
:0f:f4:cc (try 1/3)
Dec 13 05:55:26 beaglebone kernel: [ 254.719992] wlan0: RX AssocResp from
c8:b33
:73:0f:f4:cc (capab=0x411 status=0 aid=3)
Dec 13 05:55:26 beaglebone kernel: [ 254.728123] wlan0: associated
Dec 13 05:55:26 beaglebone wpa_supplicant[2161]: wlan0: Associated with
c8:b3:733
:0f:f4:cc
Dec 13 05:55:26 beaglebone kernel: [ 254.739080] IPv6:
ADDRCONF(NETDEV_CHANGE)::
wlan0: link becomes ready
Dec 13 05:55:26 beaglebone wpa_supplicant[2161]: wlan0: WPA: Key
negotiation comm
pleted with c8:b3:73:0f:f4:cc [PTK=TKIP GTK=TKIP]
Dec 13 05:55:26 beaglebone wpa_supplicant[2161]: wlan0:
CTRL-EVENT-CONNECTED - CC
onnection to c8:b3:73:0f:f4:cc completed [id=0 id_str=]
Hmmm. I would guess the driver for the card just doesn't work properly and
it's time to move on. Does anyone see it differently? Thanks.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
