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