Hoes anyone managed to install easily a usb wifi on beaglebone with Ubuntu and use it in ad-hoc mode?
If yes let me know the model.
Thank you
Hi,
Yes i have.
I have had great success with the dlink dwa-127.
I use Ubuntu but with kernel and modules kindly provided by RobertCNielson since the current kernel does not yet support this module
Regards
I've used the DLink DWA 131 with 3.0.x kernels... I've used a narcissus build then switched to precompiled 3.0.17+ kernel + modules provided in http://www.angstrom-distribution.org/demo/beagleboard/
Then I used a 3.0.25+ system build with openembedded, wifi connection seems to be more stable than before (less disconnects)
The DLinkw DWA131 is also a very small device (less than 2 centimeters long), very cool for a small board !
Hi Chris,
I have the same WiFi module (DLink DWA 131) and not able to make it work.
Can you give me some hints?
See details below:
root@beaglebone:~# uname -a
Linux beaglebone 3.2.14 #1 Mon Apr 9 12:21:19 CEST 2012 armv7l GNU/Linux
##no module inserted
root@beaglebone:~# lsmod
Module Size Used by
sit 7593 0
tunnel4 2379 1 sit
ip_tables 7830 0
x_tables 14348 1 ip_tables
g_mass_storage 24018 0
rfcomm 24259 0
ircomm_tty 14073 0
ircomm 8407 1 ircomm_tty
irda 85557 2 ircomm_tty,ircomm
hidp 10152 0
bluetooth 109654 4 rfcomm,hidp
rfkill 14605 2 bluetooth
ipv6 210442 17 sit
root@beaglebone:~#
##module inserted
root@beaglebone:~# [ 37.102130] r8712u: Firmware request failed
root@beaglebone:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 07d1:3303 D-Link System
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@beaglebone:~# lsmod
Module Size Used by
r8712u 119298 0
ip_tables 7830 0
x_tables 14348 1 ip_tables
g_mass_storage 24018 0
rfcomm 24259 0
ircomm_tty 14073 0
ircomm 8407 1 ircomm_tty
irda 85557 2 ircomm_tty,ircomm
hidp 10152 0
bluetooth 109654 4 rfcomm,hidp
rfkill 14605 2 bluetooth
ipv6 210442 14
root@beaglebone:~#
Regards
Jan
Hi Janek, I’m using this adapter under a 3.0.25+ kernel (but it worked with a 3.0.17)
AFAIK the module have been included in the mainstream kernel from the 2.6.39
Under Ubuntu (kernel 3.2) the module was loaded but wlan0 did not started up, and I didn’t investigated because I was just evaluating Ubuntu.
So, under my (working) system I got
lsmod
Module Size Used by
bufferclass_ti 4688 0
omaplfb 11026 0
pvrsrvkm 142423 2 bufferclass_ti,omaplfb
twl4030_madc_hwmon 1611 0
twl4030_madc 5564 1 twl4030_madc_hwmon
rtc_twl 3921 0
r8712u 143647 0
rfcomm 29383 0
hidp 11946 0
ipv6 239459 12
Same module than you, but the module need a firmware (in /lib/firmware) to fonction.
I remember that the module was looking for this firmware in the wrong directory, (/lib/firmware/rtlwifi instead of /lib/firmware/realtek/rtlwifi) so I had to move the firmware files
These files are available here Then I only use wpa_supplicant and classic Angstrom network configuration (no networkmanager or so) le 24/04/2012 01:00, Janek nous a dit:
Thanks Chris for showing the direction
Jan
U dxkxxxxzx xeSl
Thanks,
~Denny
Hi Chris,
One step ahead.
Following your advice I have low level drivers working
root@beaglebone:~# iwconfig
lo no wireless extensions.
wlan0 unassociated Nickname:“rtl_wifi”
Mode:Auto Access Point: Not-Associated Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth0 no wireless extensions
root@beaglebone:~# ifdown wlan0
root@beaglebone:~# ifup wlan0
udhcpc (v1.19.4) started
Sending discover…
Sending discover…
Sending discover…
No lease, failing
root@beaglebone:~# iwlist scanning
…
Cell 01 - Address: 00:24:6C:E1:6C:62
ESSID:“SOMETHING”
Protocol:IEEE 802.11bgn
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:wpa_ie=dd1a0050f20101000050f20202000050f2020050f204010
00050f201
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : 802.1x
Extra:rsn_ie=30180100000fac020200000fac02000fac040100000fac0
10000
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : 802.1x
Signal level=69/100
…
Any hints where to go from here?
Despite trying different things following searches on the subject have no luck in achieving network connectivity.
Jan
Hi Jan, I dunno for Ubuntu but under Angstrom I had to configure
-
/etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wireless_mode managed
wireless_essid any
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf -
/etc/wpa_supplicant.conf
ap_scan=1
eapol_version=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=“mybox”
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk=“mykey”
pairwise=TKIP
group=TKIP
}
After ifup wlan0 you should at least have something with iwconfig, like
wlan0 IEEE 802.11bg ESSID:“mybox” Nickname:“rtl_wifi”
Mode:Managed Frequency:2.437 GHz Access Point: 00:1F:9F:F8:1B:25
Bit Rate:54 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:------- Security mode:open
Power Management:off
Link Quality=99/100 Signal level=60/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
If you don’t get something in the ESSID it might be cause by a bad configuration OR because of the low wireless quality.
In my case, my access point is one floor below and somethimes the beagleboard can’t connect, I have to move it a little bit in some other place of my desktop.
This might be due to the very small antenna of the DLINK adapter, or by a too low signal coming from the access point.
Of course, wpa_supplicant.conf network{} section will greatly vary depending the wireless access point you want to connect
Have a look to the wpa_supplicant web site they have a lot of examples covering a lot of situations.
Then, when every is fine after ifup wlan0 you get
[ 340.894714] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sending discover…
Sending select for 192.168.1.95…
Lease of 192.168.1.95 obtained, lease time 86400
adding dns 192.168.1.254
Hi Chris,
Finally I had some luck, it works.
Thanks you and everyone who contributed for help, appreciate it.
Jan