-------- Original Message -------- Subject: Re: Fwd: trouble using wifi on Linaro Ubuntu for Pandaboard Date: Sun, 18 Nov 2012 22:13:57 -0800 (PST) From: Alex Stefanescu stefanescu@rice.edu Reply-To: Alex Stefanescu stefanescu@rice.edu To: Andy Green andy.green@linaro.org

Thank you for the reply.

It worked!

-- Alex Stef

------------------------------------------------------------------------ *From:* Andy Green andy.green@linaro.org *To:* Fathi Boudra fathi.boudra@linaro.org *Cc:* Alex Stefanescu stefanescu@rice.edu; linaro-dev linaro-dev@lists.linaro.org *Sent:* Sunday, November 18, 2012 9:21 PM *Subject:* Re: Fwd: trouble using wifi on Linaro Ubuntu for Pandaboard

On 11/18/12 16:24, the mail apparently from Fathi Boudra included:

Wrong mailing list, forwarding lo linaro-dev

---------- Forwarded message ---------- From: Alex Stefanescu <stefanescu@rice.edu mailto:stefanescu@rice.edu> Date: 18 November 2012 02:09 Subject: trouble using wifi on Linaro Ubuntu for Pandaboard

Hello,

I'm having trouble connecting to wifi on the Linaro Ubuntu releases for the Pandaboard. I've tried with both 12.10 and 12.09 releases, which are listed to have passed the wifi test.

...

I'm using Pandaboard with OMAP4430 and wl1271 wlan chipset.

I've also tried running wpa_supplicant manually to connect to both the same open network, or another one secured with WPA2 (I used the wpa_supplicant.conf from an Android phone so I'm pretty sure it was correct) and I have the same issue. There is also a wpa_supplicant always running in the background, does it matter?

Yes you can't have two wpa_supplicants fighting over the state of the same wireless interface.

The "by hand" method for the WPA2 network -->

# service network-manager stop # wpa_passphrase "Rice Visitor" > /etc/wpa_supplicant/wpa_supplicant.conf

(type the AP passphrase and enter)

# wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf &

(should associate after a second or two)

# dhclient wlan0

At that point you should have an IP on wlan0, default route and DNS configured and workable.

For unencrypted AP "by hand", you don't use wpa_supplicant.

# service network-manager stop # killall wpa_supplicant # iwlist wlan0 scan

(find your AP, use its info below)

# ifconfig wlan0 up # iwconfig wlan0 essid "Unencypted AP Name" # iwconfig wlan0 chan 11 # iwconfig wlan0 ap 00:1F:12:34:56:78

(check if associated)

# iwconfig

wlan0 IEEE 802.11abgn ESSID:"Unencrypted AP Name" Mode:Managed Frequency:2.462 GHz Access Point: 00:1F:12:34:56:78 Bit Rate=72.2 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=40/70 Signal level=-70 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:2 Missed beacon:0

# dhclient wlan0

Again your connection should have DNS, route and be workable.

If you're missing some of these commands make sure you have dhcp3-client and wireless-tools packages.

-Andy

-- Andy Green | TI Landing Team Leader Linaro.org │ Open source software for ARM SoCs | Follow Linaro http://facebook.com/pages/Linaro/155974581091106 - http://twitter.com/#%21/linaroorg - http://linaro.org/linaro-blog