Re: getting started with wlan
For the bits Paul didn't cover: On Wednesday 24 March 2010, Kai-Martin wrote: > On 03/22/2010 01:40:06 PM, Al Johnson wrote: > > Connectivity, or direct through dbus with mdbus2, dbus-send or similar. > > How would I do this? ( I miss man pages on my freerunner ;-) mdbus2 -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled More generally check http://docs.freesmartphone.org for how the API is supposed to work. You can also use mdbus2 to show you what dbus interfaces are available at a given level by omitting arguments. So to see what Usage provides you could use: mdbus2 -s org.freesmartphone.ousaged /org/freesmartphone/Usage btw the -s switch is for the session bus. the -h switch can be helpful too ;-) > > See above. I saw 'linksys' in your scan results. Mokonnect never sees my > > wrt54g, > > Same here. > I wonder, why mokonnect can't see my wlan while iwlist reliably does. I guess it (or connman, which I think it's using) is filtering the results by some set of criteria. I've not checked the source. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
Kai-Martin writes: >> In SHR WiFi is powered on and off through FSO's Resource handling.This is >> usually set to 'auto' so it will be powered up if an app requests the WiFi >> resource, and shut down when nothing is requesting it. > > Does "wmiconfig -i eth0 --power maxperf" interfere with this setting? When the device is turned off you obviously can't change its parameters. >> and I have to use 'wmiconfig -i eth0 --power maxperf' to get a >> reliable connection when setting up with wpa_supplicant. > > Great tip! > With maxperf wlan connection is finally solid :-) > I reckon, this also means increased power consumption. Is there an option to > get back to normal, too? Or more broadly: Where can I look up the features I > can adjust with wmiconfig? (Did I mention, I miss access to man > pages?) --power=rec There's no decent man page unfortunately, just info returned by wmiconfig itself. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On 03/22/2010 01:40:06 PM, Al Johnson wrote: > In SHR WiFi is powered on and off through FSO's Resource handling.This is > usually set to 'auto' so it will be powered up if an app requests the WiFi > resource, and shut down when nothing is requesting it. Does "wmiconfig -i eth0 --power maxperf" interfere with this setting? > Connectivity, or direct through dbus with mdbus2, dbus-send or similar. How would I do this? ( I miss man pages on my freerunner ;-) > See above. I saw 'linksys' in your scan results. Mokonnect never sees my > wrt54g, Same here. I wonder, why mokonnect can't see my wlan while iwlist reliably does. > and I have to use 'wmiconfig -i eth0 --power maxperf' to get a > reliable connection when setting up with wpa_supplicant. Great tip! With maxperf wlan connection is finally solid :-) I reckon, this also means increased power consumption. Is there an option to get back to normal, too? Or more broadly: Where can I look up the features I can adjust with wmiconfig? (Did I mention, I miss access to man pages?) ---<)kaimartin(>--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
Kai-Martin writes: >> Exactly. Just add an appropriate section to wpa_supplicant.conf, it >> works for all networks. > > Assembling bits and pieces from many sites, I got wifi to work -- manually > with commands through ssh and still with wake-up issues. Add this one to your knowledge base too :) it has some clarifications and also a solution to your dhcp issue (btw, you do not need to use the "bind" command manually, FSO does that for you automatically, and you do not need to scan manually, wpa_supplicant does that): http://www.mail-archive.com/community@lists.openmoko.org/msg58146.html -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On Sunday 21 March 2010, Kai-Martin wrote: > On 03/21/2010 03:00:52 AM, William Kenworthy wrote: > > Just a point ... why modules? > > Because the manual suggested to load the modules in the same section > as the image of the kernel and of the image of the root file system. > > > you only need the module step if you are changing from the > > matching kernel so need to change them. > > I'll add an explaining comment to the wiki manual. > > > Sorry cant help with wifi - I find that mokoconnect and similar gui's > > are too flaky - manual is more reliable. > > Ok, why not. > I am only half fluent with the necessesary commands. On my > laptop I used to call wpa_supplicant with some fancy config file. > The wlan device to talk to seems to be eth0, right? > > Most of the time when I check with ifconfig, there is no decice eth0. > Presumably this is, because the wlan chip is xswitched off. > How do I manually switch the wlan chip on and off? > How do I make sure, die wlan device is not shut off again by some > power saving application? In SHR WiFi is powered on and off through FSO's Resource handling.This is usually set to 'auto' so it will be powered up if an app requests the WiFi resource, and shut down when nothing is requesting it. You can force it to 'enabled' or 'disabled' if needed. You can do this with the Settings app under Connectivity, or direct through dbus with mdbus2, dbus-send or similar. > I just found the wiki page on wlan connectivity: > http://wiki.openmoko.org/wiki/Wifi > However, the commands there assume a working eth0 device. > So I have to deal with that first. See above. I saw 'linksys' in your scan results. Mokonnect never sees my wrt54g, and I have to use 'wmiconfig -i eth0 --power maxperf' to get a reliable connection when setting up with wpa_supplicant. > ---<(kaimartin)>--- > > PS: The search utility in the wiki seems to be broken. The term > "Wifi" could not be not be found, even though there is a page > called like that. The internal search engine is bordering on useless, which is why search is set up to use google by default instead. If you use NoScript, RequestPolicy or similar to block the google search then it falls back to the useless internal engine. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On Sun, Mar 21, 2010 at 4:21 AM, Kai-Martin wrote: > I just found the wiki page on wlan connectivity: > http://wiki.openmoko.org/wiki/Wifi > However, the commands there assume a working eth0 device. > So I have to deal with that first. Here are a few scripts that I use. I've put them in my home directory, where they are easy to start: $ cat ./up fsoraw -f -r WiFi -- wpa_supplicant -ieth0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf & $ cat ./a udhcpc $ cat ./u #! /bin/sh fsoraw -f -r CPU,Display -- opkg update swapon /dev/mmcblk0p4 fsoraw -f -r CPU,Display -- opkg upgrade swapoff /dev/mmcblk0p4 $ cat ./down killall wpa_supplicant Note that my 'u' script turns swap on and off. You may not have a swap file or partition, so you may want to leave this out (although swapon will complain if it doesn't find a swap file or partition). These scripts kinda 'work', although e SIGABRT's for me, too, when I turn off the WiFi, or if I let the FR suspend while WiFi is on. I'll open tickets for those problems. Hope this helps! Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On 03/21/2010 06:57:34 AM, Paul Fertser wrote: > Exactly. Just add an appropriate section to wpa_supplicant.conf, it > works for all networks. Assembling bits and pieces from many sites, I got wifi to work -- manually with commands through ssh and still with wake-up issues. This is what I did: 1) Dump the testing install of shr and flash the latest unstable and rootfs instead. I figured, I had not much to loose. Whith enlightment constantly crashing and wlan not working out of the box, I thought I'd give the bleeding edge stuiff a try. In addidtion many aspects of the testing GUI do not match the description in the online manual. So I reflashed with the latest unstable uImage plus latest kernel. Et voila: A much smoother interface with illum rather than enlightment and no crashes of the desktop. Mokonnect still couldn't find any network, though. So I hadn't gained anything on that issue. 2) Modify the sample wpa_supplicant.conf given in http://wiki.openmoko.org/wiki/Wifi I just gave my local ssid and added my secret wpa key. 3) Connect to the freerunner with ssh via usb from the dektop. The first two commands are needed to set up the interface on my desktop (Debian/squeze): sudo ip address add 192.168.0.200/24 dev eth2 sudo ip link set dev eth2 up ssh r...@192.168.0.202 4) On freerunner, create an empty /etc/wpa_supplicant/wpa_supplicant.conf $ touch /etc/wpa_supplicant/ edit the file with vi: $ vi /etc/wpa_supplicant/wpa_supplicant.conf press i to insert and copy-paste the proper contents from the desktop. This sure can be done in a more elegant way with sftp. But what the heck. 5) Bind the eth0 interface, so it is visible to other processes: $ echo s3c2440-sdi > /sys/bus/platform/drivers/s3c2440-sdi/bind 6) Check whether eth0 really appeared: $ ifconfig 7) Scan for wifi nets $ iwlist eth0 scan 8) Bring the eth0 interface up: $ ifconfig eth0 up 9) Start wpa_supplicant with fsoraw. This registers the use of the chip with the power saving framework. A stand-alone call of wpa_supplicant would suffer from power-down of the wifi chip. $ fsoraw -r WiFi -- wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf & The ampersand (&) at the end of the line puts the execution in the background of the ssh terminal . It let me use the terminal for further commands. On the ssh terminal there is four times a warning followed by some more ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:12:17:cc:f9:a2 (SSID='linksys' freq=2462 MHz) Associated with 00:12:17:cc:f9:a2 WPA: Key negotiation completed with 00:12:17:cc:f9:a2 [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:12:17:cc:f9:a2 completed (auth) [id=1 id_str=] This is good news --> wlan is up and running! 10) Issue a command to get proper IP numbers from the wlan server: $ udhcpc udhcpc (v1.15.3) started Sending discover... Sending select for 192.168.10.113... Sending select for 192.168.10.113... Lease of 192.168.10.113 obtained, lease time 86400 adding dns 81.14.243.9 adding dns 81.14.244.9 11) To test for internet connectivity with a ping to a reliable server: $ ping heise.de PING heise.de (193.99.144.80): 56 data bytes 64 bytes from 193.99.144.80: seq=0 ttl=248 time=54.180 ms 64 bytes from 193.99.144.80: seq=1 ttl=248 time=56.079 ms 64 bytes from 193.99.144.80: seq=2 ttl=248 time=186.172 ms ... Now I was able to browse the web with midori :-) However, I still have issues with loss of connection on suspend and/or idle. The connection does not come up properly on wake-up. It looks like wpa key negotiation is automatically restarted, but udhcpc is not. Consequently,there is wlan on wake-up, but no working web until I call udhcpc manually. How would I fix this? I guess, there is a way to add to the fso framework. Any quick hint? Of course, this eleven point check list is just a proof of principle and not ready for regular use. My goal is to wrap all this into a script and start it with a button on the illum desktop. This must have been done by others before. Any pointers to tricks and pitfalls? > to search the wiki without JS shit, ^^^ You mean, it works for browsers, other than epiphany? Checking with iceweasel --> works! ---<)kaimartin(>--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/list
Re: getting started with wlan
On 03/21/2010 06:57:34 AM, Paul Fertser wrote: > Exactly. Just add an appropriate section to wpa_supplicant.conf, it > works for all networks. Assembling bits and pieces from many sites, I got wifi to work -- manually with commands through ssh and still with wake-up issues. This is what I did: 1) Dump the testing install of shr and flash the latest unstable and rootfs instead. I figured, I had not much to loose. Whith enlightment constantly crashing and wlan not working out of the box, I thought I'd give the bleeding edge stuiff a try. In addidtion many aspects of the testing GUI do not match the description in the online manual. So I reflashed with the latest unstable uImage plus latest kernel. Et voila: A much smoother interface with illum rather than enlightment and no crashes of the desktop. Mokonnect still couldn't find any network, though. So I hadn't gained anything on that issue. 2) Modify the sample wpa_supplicant.conf given in http://wiki.openmoko.org/wiki/Wifi I just gave my local ssid and added my secret wpa key. 3) Connect to the freerunner with ssh via usb from the dektop. The first two commands are needed to set up the interface on my desktop (Debian/squeze): sudo ip address add 192.168.0.200/24 dev eth2 sudo ip link set dev eth2 up ssh r...@192.168.0.202 4) On freerunner, create an empty /etc/wpa_supplicant/wpa_supplicant.conf $ touch /etc/wpa_supplicant/ edit the file with vi: $ vi /etc/wpa_supplicant/wpa_supplicant.conf press i to insert and copy-paste the proper contents from the desktop. This sure can be done in a more elegant way with sftp. But what the heck. 5) Bind the eth0 interface, so it is visible to other processes: $ echo s3c2440-sdi > /sys/bus/platform/drivers/s3c2440-sdi/bind 6) Check whether eth0 really appeared: $ ifconfig 7) Scan for wifi nets $ iwlist eth0 scan 8) Bring the eth0 interface up: $ ifconfig eth0 up 9) Start wpa_supplicant with fsoraw. This registers the use of the chip with the power saving framework. A stand-alone call of wpa_supplicant would suffer from power-down of the wifi chip. $ fsoraw -r WiFi -- wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf & The ampersand (&) at the end of the line puts the execution in the background of the ssh terminal . It let me use the terminal for further commands. On the ssh terminal there is four times a warning followed by some more ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:12:17:cc:f9:a2 (SSID='linksys' freq=2462 MHz) Associated with 00:12:17:cc:f9:a2 WPA: Key negotiation completed with 00:12:17:cc:f9:a2 [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:12:17:cc:f9:a2 completed (auth) [id=1 id_str=] This is good news --> wlan is up and running! 10) Issue a command to get proper IP numbers from the wlan server: $ udhcpc udhcpc (v1.15.3) started Sending discover... Sending select for 192.168.10.113... Sending select for 192.168.10.113... Lease of 192.168.10.113 obtained, lease time 86400 adding dns 81.14.243.9 adding dns 81.14.244.9 11) To test for internet connectivity with a ping to a reliable server: $ ping heise.de PING heise.de (193.99.144.80): 56 data bytes 64 bytes from 193.99.144.80: seq=0 ttl=248 time=54.180 ms 64 bytes from 193.99.144.80: seq=1 ttl=248 time=56.079 ms 64 bytes from 193.99.144.80: seq=2 ttl=248 time=186.172 ms ... Now I was able to browse the web with midori :-) However, I still have issues with loss of connection on suspend and/or idle. The connection does not come up properly on wake-up. It looks like wpa key negotiation is automatically restarted, but udhcpc is not. Consequently,there is wlan on wake-up, but no working web until I call udhcpc manually. How would I fix this? I guess, there is a way to add to the fso framework. Any quick hint? Of course, this eleven point check list is just a proof of principle and not ready for regular use. My goal is to wrap all this into a script and start it with a button on the illum desktop. This must have been done by others before. Any pointers to tricks and pitfalls? > to search the wiki without JS shit, ^^^ You mean, it works for browsers, other than epiphany? Checking with iceweasel --> works! ---<)kaimartin(>--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/list
Re: getting started with wlan
What works best for me is the following:
edit /etc/network/interfaces
iface eth0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
down wpa_action eth0 down
iface homeNet inet dhcp
/etc/wpa_supplicant/wpa_supplicant.conf looks like this:
ctrl_interface=/var/run/wpa_supplicant
update_config=1
network={
ssid="..."
scan_ssid=1
id_str="homeNet"
psk="..."
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
}
Once I turn on wifi in SHR-Settings-Connectivity it automatically
connects. Works very well.
On Sun, Mar 21, 2010 at 04:21, Kai-Martin wrote:
> On 03/21/2010 03:00:52 AM, William Kenworthy wrote:
>
>> Just a point ... why modules?
>
> Because the manual suggested to load the modules in the same section
> as the image of the kernel and of the image of the root file system.
>
>
>> you only need the module step if you are changing from the
>> matching kernel so need to change them.
>
> I'll add an explaining comment to the wiki manual.
>
>
>> Sorry cant help with wifi - I find that mokoconnect and similar gui's
>> are too flaky - manual is more reliable.
>
> Ok, why not.
> I am only half fluent with the necessesary commands. On my
> laptop I used to call wpa_supplicant with some fancy config file.
> The wlan device to talk to seems to be eth0, right?
>
> Most of the time when I check with ifconfig, there is no decice eth0.
> Presumably this is, because the wlan chip is xswitched off.
> How do I manually switch the wlan chip on and off?
> How do I make sure, die wlan device is not shut off again by some
> power saving application?
>
> I just found the wiki page on wlan connectivity:
> http://wiki.openmoko.org/wiki/Wifi
> However, the commands there assume a working eth0 device.
> So I have to deal with that first.
>
> ---<(kaimartin)>---
>
> PS: The search utility in the wiki seems to be broken. The term
> "Wifi" could not be not be found, even though there is a page
> called like that.
>
> --
> Kai-Martin Knaak
> Email: k...@familieknaak.de
> Öffentlicher PGP-Schlüssel:
> http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
Kai-Martin writes: > Ok, why not. > I am only half fluent with the necessesary commands. On my > laptop I used to call wpa_supplicant with some fancy config file. > The wlan device to talk to seems to be eth0, right? Yes but you can change that to more logical "wlan" with udev. > Most of the time when I check with ifconfig, there is no decice eth0. > Presumably this is, because the wlan chip is xswitched off. > How do I manually switch the wlan chip on and off? Depends on what manually means :-) In debian I do om wifi power 1 With FSO you are probably supposed to request the WiFi resource. > PS: The search utility in the wiki seems to be broken. The term > "Wifi" could not be not be found, even though there is a page > called like that. It needs javascript. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On 21 March 2010 03:21, Kai-Martin wrote: > The wlan device to talk to seems to be eth0, right? Correct. > Most of the time when I check with ifconfig, there is no decice eth0. > Presumably this is, because the wlan chip is xswitched off. Yes. > How do I manually switch the wlan chip on and off? In the SHR UI, I'm not sure - but I would guess that there is a switch somewhere in the Settings app. At the D-Bus API level, it's a RequestResource call for the WiFi device: mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource WiFi > How do I make sure, die wlan device is not shut off again by some > power saving application? Sorry, don't know that one. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
Kai-Martin writes: >> Sorry cant help with wifi - I find that mokoconnect and similar gui's >> are too flaky - manual is more reliable. > > Ok, why not. > I am only half fluent with the necessesary commands. On my > laptop I used to call wpa_supplicant with some fancy config file. > The wlan device to talk to seems to be eth0, right? Exactly. Just add an appropriate section to wpa_supplicant.conf, it works for all networks. To understand power management, read FSO_Resources wiki page, to search the wiki without JS shit, just google ``site:wiki.openmoko.org wifi''. Most probably you'll need an additional delay before wpa_supplicant, just like with BT. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On 03/21/2010 03:00:52 AM, William Kenworthy wrote: > Just a point ... why modules? Because the manual suggested to load the modules in the same section as the image of the kernel and of the image of the root file system. > you only need the module step if you are changing from the > matching kernel so need to change them. I'll add an explaining comment to the wiki manual. > Sorry cant help with wifi - I find that mokoconnect and similar gui's > are too flaky - manual is more reliable. Ok, why not. I am only half fluent with the necessesary commands. On my laptop I used to call wpa_supplicant with some fancy config file. The wlan device to talk to seems to be eth0, right? Most of the time when I check with ifconfig, there is no decice eth0. Presumably this is, because the wlan chip is xswitched off. How do I manually switch the wlan chip on and off? How do I make sure, die wlan device is not shut off again by some power saving application? I just found the wiki page on wlan connectivity: http://wiki.openmoko.org/wiki/Wifi However, the commands there assume a working eth0 device. So I have to deal with that first. ---<(kaimartin)>--- PS: The search utility in the wiki seems to be broken. The term "Wifi" could not be not be found, even though there is a page called like that. -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: getting started with wlan
On Sun, 2010-03-21 at 01:28 +0100, Kai-Martin wrote: > Hi. > > Last week, I bought this used freerunner, version GTA02-A5. I decided to > dump the existing install and do a fresh flash of shr. So I followed the > directions in http://wiki.openmoko.org/wiki/SHR_User_Manual : > > Download images from http://build.shr-project.org/shr-testing/images/om-gta02 > full-om-gta02.jffs2 > uImage-om-gta02-latest.bin > modules-2.6.29-oe11+gi...355c2067c4e88-r8-om-gta02.tgz > Install of rootfs and kernel image with dfu-util was successful. > > For the kernel moduls, the manual just says: "Put that file on the FreeRunner > and run gzi -dc modules ..." > The only way could come up to put the file on the freerunner, was with sftp > via usb_ether, after the image and the kernel had been flashed and booted. > Is this the way the modules are supposed to be installed? Just a point ... why modules? - the jffs file already has the modules installed - you only need the module step if you are changing from the matching kernel so need to change them. Saves a couple of steps and the heartache of trying to install the modules. Suggestion, if you really want the modules - put them on the sd card using the old system before flashing :) Sorry cant help with wifi - I find that mokoconnect and similar gui's are too flaky - manual is more reliable. BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
getting started with wlan
Hi. Last week, I bought this used freerunner, version GTA02-A5. I decided to dump the existing install and do a fresh flash of shr. So I followed the directions in http://wiki.openmoko.org/wiki/SHR_User_Manual : Download images from http://build.shr-project.org/shr-testing/images/om-gta02 full-om-gta02.jffs2 uImage-om-gta02-latest.bin modules-2.6.29-oe11+gi...355c2067c4e88-r8-om-gta02.tgz Install of rootfs and kernel image with dfu-util was successful. For the kernel moduls, the manual just says: "Put that file on the FreeRunner and run gzi -dc modules ..." The only way could come up to put the file on the freerunner, was with sftp via usb_ether, after the image and the kernel had been flashed and booted. Is this the way the modules are supposed to be installed? Anyway, the flash seems to have worked out fine. On boot I get a shr boot screen and an enlightment driven "desktop". The touch screen is resonpsive. Dial-out works, I can call my other phone. There is nbo display of current net strength, though. Ether over USB works. I can ssh from my desktop to the freerunner and did the transfer of the kernel modules. Mokomaze works, so the orientation sensor is operative, too. The only major hardware component I could not get running, is wlan. Scannning in mokonnect does not reveal any net. If I tell mkonnect to connect, anyway, it runs into timeout. However, iwlist on the ssh command line yields the expected local wlan net: /- $ iwlist eth0 scan eth0 Scan completed : Cell 01 - Address: 00:12:17:CC:F9:A2 ESSID:"linksys" Mode:Master Frequency:2.462 GHz (Channel 11) Quality=10/94 Signal level=-85 dBm Noise level=-95 dBm Encryption key:on Extra:bcn_int=100 Extra:wpa_ie=dd180050f2010150f2020150f2020150f202 \- What might be the problem on here? Do I have to configure mokonnect in some way? This may or may not be related: On exit of mokonnect I get a popup Enlightment error This is very bad. Enlightment SigABRT'd. This not meant to happen and is most liekly a bug (...) (F1) recover (F2) exit Any advice how I would go ahead to get wlan working? ---<)kaimartin(>--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
