How do you get Wi-Fi SDIO on the BNN?
john
jptmoore at gmail.com
Thu Aug 5 18:39:06 EDT 2010
Hi...
On 5 August 2010 23:18, Mike McCauley <mikem at open.com.au> wrote:
> Hello all,
>
> Lars is quite right. The process is for the current version of the official
> BNN firmware with the SDW-823 SDIO Wi-Fi card is:
>
> 1. Copy ks7010sd.rom and ks79xx.cfg from
> http://downloads.qi-hardware.com/software/ks7010-firmware-20100217.tar.bz2
> to /lib/firmware on BNN. result is
>
> root at BenNanoNote:/lib/firmware# ls -l
> -rw-r--r-- 1 root root 79136 Jan 1 09:28 ks7010sd.rom
> -rw-r--r-- 1 root root 1940 Jan 1 09:27 ks79xx.cfg
>
> 1a. Optionally to remove the noisy error messages from the console
> append this line to /etc/config/system
> option 'conloglevel' '4'
>
> 2. Create and edit /etc/wpa_supplicant/wpa_supplicant.conf to be something
> like this for an AP configured for WPA personal:
>
> ctrl_interface=/var/run/wpa_supplicant
> network={
> ssid="YourApSSID"
> scan_ssid=1
> key_mgmt=WPA-PSK
> psk="your_wpa_passphrase"
> }
>
> 3. Reboot the BNN with the SDW-823 already inserted.
>
> 4. Check if the ks7010 is working fine
>
> # iwconfig
> lo no wireless extensions.
> usb0 no wireless extensions.
> eth0 IEEE 802.11b/g ESSID:"default"
> Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
> Bit Rate:11 Mb/s
> RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> 5. Run wpa_supplicant:
> with debug for testing:
> # wpa_supplicant -Dwext -ieth0 -d -c /etc/wpa_supplicant/wpa_supplicant.conf
> or as a daemon when everything is working:
> # wpa_supplicant -Dwext -ieth0 -B -c /etc/wpa_supplicant/wpa_supplicant.conf
>
> 6. Check if we are associated and connected
> # iwconfig
> lo no wireless extensions.
>
> usb0 no wireless extensions.
>
> eth0 IEEE 802.11b/g ESSID:"zyxel-b-3000a"
> Mode:Managed Frequency:2.422 GHz Access Point: 00:A0:C5:7E:42:31
> Bit Rate:11 Mb/s
> RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=100/100 Signal level=-55 dBm Noise level=0 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:12:E6:50:02:17
> inet addr:203.63.154.153 Bcast:203.63.154.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:547 errors:6 dropped:0 overruns:0 frame:0
> TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:52912 (51.6 KiB) TX bytes:5483 (5.3 KiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> ....
>
>
> 7. start DHCP client:
> # udhcpc eth0
> dhcpc (v1.15.3) started
> Sending discover...
> Sending select for 203.63.154.153...
> Lease of 203.63.154.153 obtained, lease time 14400
> udhcpc: ifconfig eth0 203.63.154.153 netmask 255.255.255.0 broadcast +
> udhcpc: setting default routers: 203.63.154.248
> udhcpc: setting dns servers: 203.63.154.29 203.63.154.248
> udhcpc: setting dns domain: open.com.au
>
> 8. Test:
> # ping www.google.com
> PING www.google.com (66.102.11.104): 56 data bytes
> 64 bytes from 66.102.11.104: seq=0 ttl=55 time=149.146 ms
>
> 64 bytes from 66.102.11.104: seq=1 ttl=55 time=137.762 ms
> 64 bytes from 66.102.11.104: seq=2 ttl=55 time=137.902 ms
>
> My tests show that you can remove and reinsert the SDW-823 card and it will
> continue to work, provided wpa_supplicant keeps running, and provided you run
> # udhcpc eth0
> again after reinserting
>
> Tests here also show that it will usually work if you insert the SDW-823 card
> _after_ booting, and before running wpa_supplicant. And that thereafter you
> can remove and reinsert the card and it will reassociate and reconnect to the
> AP fine. However, if you have had any connection failures to the AP, its
> possible for the SDW card (or driver?) to get confused and subsequent
> connection attempts will always fail. Its possible that unloading and
> reloading the driver would fix this without having to reboot but I havent
> tried.
>
>
> Thanks Lars!
> Thanks Everyone!
>
>
>
>
> On Friday 06 August 2010 07:00:49 am Lars Bahner wrote:
>> 2010/8/5 Mike McCauley <mikem at open.com.au>
>>
>> > Hi,
>> > I have been looking at the howto at
>> > http://en.qi-hardware.com/wiki/Wi-Fi_in_Nanonote
>> >
>> > Its a very poor howto, since it doenst actually tell you how to do most
>> > things.
>>
>> It is, but that is because it advises use of the SDW-823, which doesn't
>> work very well anymore :( The driver and/or firmware is not maintained and,
>> as far as I can tell, won't be.
>>
>> You do however not really need to do any of the points in the Howto. The
>> driver is ready to go already. All you need to do is download the firmware
>> and stick the firmware bins in /lib/firmware
>>
>> You need to set
>> option 'conloglevel' '4'
>>
>> in /etc/config/system as the kernel error messages in the driver will
>> saturate your console otherwise.
>>
>> The card needs to be inserted when you power on your nanonote.
>>
>> The rest is wpa_supplicabt configuration as described.
>>
>> Please note that wireless networking will work, you might even find it OK,
>> but it really is in a terrible state.
>>
>> Kind regards,
>> Lars Bahner
>
>
>
> --
> Mike McCauley mikem at open.com.au
> Open System Consultants Pty. Ltd
> 9 Bulbul Place Currumbin Waters QLD 4223 Australia http://www.open.com.au
> Phone +61 7 5598-7474 Fax +61 7 5598-7070
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
> DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
>
> _______________________________________________
> discussion mailing list
> discussion at lists.qi-hardware.com
> http://en.qi-hardware.com/mailman/listinfo/discussion
>
Works for me also.
One of my APs triggers a kernel panic though. Still handy for testing
a few things!
John.
More information about the discussion
mailing list