If you already have a setup and configured network it should be sufficient to run wpa_supplicant
wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -B
is responsible for managing the wireless connection.
Since I haven't setup my Kobo Touch yet, I am going to briefly describe how I did setup the wireless manually.
1. Load the module for the wifi
# insmod /drivers/freescale/wifi/ar6000.ko
2. Verify that the module is loaded
3. Start wpa_supplicant
(as mentioned above)
# wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -B
4. Configure the network via wpa_cli
in interactive mode ( A help at the wpa_cli prompt '>' will show you all available commands)
4a. Retrieve and show all available networks
4b. add a new network. The resulting digit (0 in my case) indicates the new network number for the following commands
4c. set SSID for network
> set_network 0 ssid "Your-Network"
4d. set password phrase
> set_network 0 psk "YourPassphrase"
4e. save the new configuration
4f. quit wpa_cli
5. Set an IP address to wlan0 adapter either static or by dhcp
5a. static IP (example)
# ifconfig wlan0 192.168.1.1
6. For hostname to ip resolving the file /etc/resolv.conf
is needed. If the file does not exist create the file with a line pointing to your nameserver in it, e.g.
7. Add a route to kernel routing table to reach external networks
# route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.1 dev wlan0
After these steps I was able to download from internet with wget
To have the wireless available after booting the Kobo Touch I created a script that is called during start up:
/bin/busybox insmod /drivers/freescale/wifi/ar6000.ko > /mnt/onboard/test.log
/bin/busybox lsmod > /mnt/onboard/test.log
/bin/wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -B > /mnt/onboard/test.log
/sbin/ifconfig wlan0 192.168.1.12 > /mnt/onboard/test.log
/sbin/route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.1 dev wlan0
/sbin/route > /mnt/onboard/test.log
The redirection in the test.log file is just for information purpose. You can omit if everything is working properly.
One issue I discovered is that nickel
interferes with my batch script. The output in the log file was as expected, but
when I listed loaded modules and running threads neither the wireless module was loaded nor wpa_supplicant
log file an error during wireless module loading was indicated.
Therefore, I decided to comment out nickel
file, since I do not need it anyway.
I hope my description helps you to get your wireless running after boot,