Help<br><br><div class="gmail_quote">On Fri, Feb 13, 2009 at 5:00 AM, <span dir="ltr"><<a href="mailto:devel-request@lists.openmoko.org">devel-request@lists.openmoko.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Send devel mailing list submissions to<br>
<a href="mailto:devel@lists.openmoko.org">devel@lists.openmoko.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.openmoko.org/mailman/listinfo/devel" target="_blank">https://lists.openmoko.org/mailman/listinfo/devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:devel-request@lists.openmoko.org">devel-request@lists.openmoko.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:devel-owner@lists.openmoko.org">devel-owner@lists.openmoko.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. AR6k vs. Tomato: next round (#1250) (Werner Almesberger)<br>
2. Re: Problem in Building Openmoko on Qemu (Angus Ainslie)<br>
3. Re: WLAN: known issues and how to help - Catch 22 (Philip Rhoades)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 13 Feb 2009 00:06:27 -0200<br>
From: Werner Almesberger <<a href="mailto:werner@openmoko.org">werner@openmoko.org</a>><br>
Subject: AR6k vs. Tomato: next round (#1250)<br>
To: <a href="mailto:devel@lists.openmoko.org">devel@lists.openmoko.org</a>, Michael 'Mickey' Lauer<br>
<<a href="mailto:mickey@openmoko.org">mickey@openmoko.org</a>><br>
Message-ID: <<a href="mailto:20090213020627.GS4526@almesberger.net">20090213020627.GS4526@almesberger.net</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Since I now have a small army of WRT54G(L) APs, I put Tomato 1.22 on<br>
one of them, in an attempt to reproduce Mickey's famous bug #1250:<br>
<a href="https://docs.openmoko.org/trac/ticket/1250" target="_blank">https://docs.openmoko.org/trac/ticket/1250</a><br>
<br>
The test consisted of setting the AP to open, b/g mixed, the preamble<br>
according to the table below, cycling (unbind/bind) the AR6k, calling<br>
wmiconfig (or not) according to the table, and then trying to<br>
associate.<br>
<br>
This is what happens:<br>
<br>
Tomato AR6k AP adv~ Neo AP responds<br>
[1] [2] ertizes requests<br>
<br>
Long default long long success<br>
<br>
Long 0 long long success<br>
<br>
Long 1 long long doesn't respond at first,<br>
then success<br>
<br>
Short default short short success<br>
<br>
Short 0 short short success<br>
<br>
Short 1 short takes a while to get going ...<br>
long association denied<br>
(repeats)<br>
<br>
[1] Setting Advanced/Wireless/Preamble<br>
[2] no wmiconfig or wmiconfig -i eth0 --setlongpreamble 0/1<br>
<br>
I went back to my books and found that I had mis-interpreted the<br>
short preamble option in the Probe Response: it doesn't mean that<br>
the station is allowed to choose to use short preambles but that<br>
it is required to do so.<br>
<br>
Here's why: <a href="http://www.tomsguide.com/us/802,review-120-5.html" target="_blank">http://www.tomsguide.com/us/802,review-120-5.html</a><br>
<br>
I therefore send apologies in the general direction of Tomato for<br>
having considered it a lemon, and to Mickey for having doubted his<br>
network. The AP is doing everything right.<br>
<br>
The AR6k driver is certainly a bit stupid to try to associate with<br>
a network requiring support for short preambles while insisting<br>
on using a long preamble. However, if told by the user to insist<br>
on long preambles and with the AP only allowing short preambles,<br>
there isn't really any common ground.<br>
<br>
What's puzzling me here is that the default setting was apparently<br>
overridden in Mickey's AR6k, even in the first runs, well before<br>
anyone mentioned --setlongpreamble. I tried setting the ESSID to<br>
"vanille" but that didn't yield any magic effects.<br>
<br>
The packets captured in<br>
<a href="https://docs.openmoko.org/trac/attachment/ticket/1250/bug1250-wifiproblem.dump" target="_blank">https://docs.openmoko.org/trac/attachment/ticket/1250/bug1250-wifiproblem.dump</a><br>
are consistent with the Short/1 scenario, so this explains what is<br>
happening but not why.<br>
<br>
Mickey, what is the precise setup sequence for the WLAN interface<br>
that leads to this ? I.e., is there more than just an<br>
iwconfig eth0 essid vanille ? Also, does an explicit<br>
wmiconfig -i eth0 --setlongpreamble 0<br>
help ?<br>
<br>
The capture data from my experiments is under<br>
<a href="http://svn.openmoko.org/developers/werner/wlan/tomato/" target="_blank">http://svn.openmoko.org/developers/werner/wlan/tomato/</a><br>
<br>
Another observation is that communication seems more fragile if the<br>
network requires support for short preambles than when it doesn't.<br>
<br>
So if experiencing network instability, it may be worth trying to set<br>
wmiconfig -i eth0 --setlongpreamble 1<br>
and see if the AP accepts this. If it does, this may improve network<br>
stability, but at the price of lowering available data bandwidth.<br>
<br>
- Werner<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 12 Feb 2009 21:14:50 -0700<br>
From: Angus Ainslie <<a href="mailto:nytowl@openmoko.org">nytowl@openmoko.org</a>><br>
Subject: Re: Problem in Building Openmoko on Qemu<br>
To: <a href="mailto:devel@lists.openmoko.org">devel@lists.openmoko.org</a><br>
Message-ID: <1234498490.6572.53.camel@think-laptop><br>
Content-Type: text/plain<br>
<br>
On Thu, 2009-02-12 at 15:17 -0800, Truedat101 wrote:<br>
> Not sure what the status is on these openmoko scripts like env and<br>
> download.sh, but these previous posts are related:<br>
> <a href="http://lists.openmoko.org/nabble.html#nabble-td2185294" target="_blank">http://lists.openmoko.org/nabble.html#nabble-td2185294</a><br>
> <a href="http://lists.openmoko.org/nabble.html#nabble-td1633573|a1633573" target="_blank">http://lists.openmoko.org/nabble.html#nabble-td1633573|a1633573</a><br>
><br>
> The download_dir appears to not exist and/or no longer be correct for<br>
> OM2008.12. I am going to do the manual builds and work through this<br>
> issue.<br>
><br>
<br>
If you are looking for Om2008.12 it is here now<br>
<br>
<a href="http://downloads.openmoko.org/distro/releases/Om2008.12/" target="_blank">http://downloads.openmoko.org/distro/releases/Om2008.12/</a><br>
<br>
Newer unstable kernels are here<br>
<br>
<a href="http://downloads.openmoko.org/distro/unstable/" target="_blank">http://downloads.openmoko.org/distro/unstable/</a><br>
<br>
Angus<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 13 Feb 2009 17:57:57 +1100<br>
From: Philip Rhoades <<a href="mailto:phil@pricom.com.au">phil@pricom.com.au</a>><br>
Subject: Re: WLAN: known issues and how to help - Catch 22<br>
To: <a href="mailto:devel@lists.openmoko.org">devel@lists.openmoko.org</a><br>
Message-ID: <<a href="mailto:499519F5.2020404@pricom.com.au">499519F5.2020404@pricom.com.au</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Werner,<br>
<br>
To reiterate - I am using:<br>
<br>
wlan-trial-20090206.uImage<br>
openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.jffs2<br>
<br>
while trying to use u-boot (NOR) with:<br>
<br>
setenv bootargs_base \${bootargs_base} log_buf_len=2M<br>
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand<br>
read.e 0x32000000 kernel 0x300000\; bootm 0x32000000<br>
saveenv<br>
<br>
for network testing - the battery ran down. So I have to allow a<br>
"normal" boot and use the charger rather than the USB PC connection to<br>
try and charge the battery but the battery isn't charging and I can't<br>
get the network connection to work so I can get software to try and<br>
force a fast charge. So I can't do any more network testing until I can<br>
work out how to charge the battery . .<br>
<br>
Any ideas?<br>
<br>
Thanks,<br>
<br>
Phil.<br>
--<br>
Philip Rhoades<br>
<br>
GPO Box 3411<br>
Sydney NSW 2001<br>
Australia<br>
E-mail: <a href="mailto:phil@pricom.com.au">phil@pricom.com.au</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@lists.openmoko.org">devel@lists.openmoko.org</a><br>
<a href="https://lists.openmoko.org/mailman/listinfo/devel" target="_blank">https://lists.openmoko.org/mailman/listinfo/devel</a><br>
<br>
<br>
End of devel Digest, Vol 8, Issue 34<br>
************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Sashi<br>