Re: [2008.9] Wifi very unreliable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 10.10.2008 um 09:31 schrieb Matthias Apitz: > El día Thursday, October 09, 2008 a las 09:20:05PM +0100, Arigead > escribió: > >> Steve Mosher wrote: >>> We should allow for links to peoples pages. >>> >>> >> >> Hate to throw a spanner in the works but I think ideally the >> information >> should be on the wiki and maintained there. How up to date is the >> info >> on an external site, if it isn't maintained, or how do you know it is >> maintained? >> >> There is an external link on the GPRS wiki page to a German site for >> installing the GSM Multiplexor and a GUI. I've been trying to get >> those >> instructions to work for the last couple of days. I assume I'm >> getting >> something wrong but how can I be sure, given the speed things >> change in >> OpenMoko, the instructions still work. >> >> Of course I'm talking about the ideal world but I know that the >> wiki is >> maintained so I'm more trusting of info there and more likely to >> bring >> problems with the info to peoples attention. > > I fully agree with this opinion of Arigead and I will put my stuff > about > Wifi and GPRS/PPP which I have in my private pages and external linked > from the Wiki to these pages into the Wiki itself; > > in general (and without blaming nobody) I have to say about the Wiki > that a lot of stuff there is outdated and not well maintained; it is > sometimes also not very clear if the information/hints/changes are > for the newer > Om2008.[8|9] versions or for older Om2007.2 version; > > btw: the last days I have moved around a lot with my FR between home, > office and a hospital, ... but without any reboot: > > [EMAIL PROTECTED]:~# uptime > 09:31:05 up 2 days, 27 min, 1 user, load average: 0.12, 0.25, 0.29 > > and when I came today morning in my office, the FR Wifi came up just > fine; > which kernel are you using? > matthias > -- > Matthias Apitz > Manager Technical Support - OCLC GmbH > Gruenwalder Weg 28g - 82041 Oberhaching - Germany > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http:// > www.UnixArea.de/ > b http://gurucubano.blogspot.com/ > A computer is like an air conditioner, it stops working when you > open Windows > Una computadora es como aire acondicionado, deja de funcionar si > abres Windows > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > - -- - -BEGIN CONTACT BLOCK- eMail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++)>;UL;P++(+++)>; L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+>;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)>++;X(+);R*;tv->+;b++(+++);DI++; D++(+++)>;G(+)>++;e+>+++;h-()>++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFI7w09r81gVylJyzERAhjpAKDwyd+zJ1aC617WYHGleBuiR4U1mgCffBQv ByGa8iEWIPIW+iGyHROtjeA= =yy57 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Friday, October 10, 2008 a las 10:07:25AM +0200, Christian Adams escribió: > >btw: the last days I have moved around a lot with my FR between home, > >office and a hospital, ... but without any reboot: > > > >[EMAIL PROTECTED]:~# uptime > > 09:31:05 up 2 days, 27 min, 1 user, load average: 0.12, 0.25, 0.29 > > > >and when I came today morning in my office, the FR Wifi came up just > >fine; > > > > which kernel are you using? I've flashed some weeks ago kernel and rootfs from: Om2008.9-gta02-20080916.uImage.bin Om2008.9-gta02-20080916.rootfs.jffs2 and 'uname -a' tells me: [EMAIL PROTECTED]:~# uname -a Linux om-gta02 2.6.24 #1 PREEMPT Wed Sep 3 19:01:18 CST 2008 armv4tl unknown matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Fri, Oct 10, 2008 at 1:50 AM, Arigead <[EMAIL PROTECTED]> wrote: > > There is an external link on the GPRS wiki page to a German site for > installing the GSM Multiplexor and a GUI. I've been trying to get those > instructions to work for the last couple of days. I assume I'm getting > something wrong but how can I be sure, given the speed things change in > OpenMoko, the instructions still work. > > I was able to get them to work, and the Services GUI was quite handy. However, I switched over to Qtextended last weekend. Have you installed all dependencies? Where is it that you have a problem exactly? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Thursday, October 09, 2008 a las 09:20:05PM +0100, Arigead escribió: > Steve Mosher wrote: > > We should allow for links to peoples pages. > > > > > > Hate to throw a spanner in the works but I think ideally the information > should be on the wiki and maintained there. How up to date is the info > on an external site, if it isn't maintained, or how do you know it is > maintained? > > There is an external link on the GPRS wiki page to a German site for > installing the GSM Multiplexor and a GUI. I've been trying to get those > instructions to work for the last couple of days. I assume I'm getting > something wrong but how can I be sure, given the speed things change in > OpenMoko, the instructions still work. > > Of course I'm talking about the ideal world but I know that the wiki is > maintained so I'm more trusting of info there and more likely to bring > problems with the info to peoples attention. I fully agree with this opinion of Arigead and I will put my stuff about Wifi and GPRS/PPP which I have in my private pages and external linked from the Wiki to these pages into the Wiki itself; in general (and without blaming nobody) I have to say about the Wiki that a lot of stuff there is outdated and not well maintained; it is sometimes also not very clear if the information/hints/changes are for the newer Om2008.[8|9] versions or for older Om2007.2 version; btw: the last days I have moved around a lot with my FR between home, office and a hospital, ... but without any reboot: [EMAIL PROTECTED]:~# uptime 09:31:05 up 2 days, 27 min, 1 user, load average: 0.12, 0.25, 0.29 and when I came today morning in my office, the FR Wifi came up just fine; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Steve Mosher wrote: > We should allow for links to peoples pages. > > Hate to throw a spanner in the works but I think ideally the information should be on the wiki and maintained there. How up to date is the info on an external site, if it isn't maintained, or how do you know it is maintained? There is an external link on the GPRS wiki page to a German site for installing the GSM Multiplexor and a GUI. I've been trying to get those instructions to work for the last couple of days. I assume I'm getting something wrong but how can I be sure, given the speed things change in OpenMoko, the instructions still work. Of course I'm talking about the ideal world but I know that the wiki is maintained so I'm more trusting of info there and more likely to bring problems with the info to peoples attention. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Friday 10 October 2008 03:05:07 Michael Shiloh wrote: > All things wifi, including known issues and a link to Tom's article, are > here: > > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi Yep, but my point was that Tom's article covers way more than wifi and therefore could be indexed under multiple troubleshooting categories, along with other external sources. Currently you would have to access each applicable wiki area and add the link, then do the same when the link changes. Rather than than say 'this person did this here', why not say 'see the wifi section in troubleshooting' and have a small write up for each link? There's no problem with linking haphazardly, it just eliminates a single point of maintenance. This is just my view, no need to reply with any links, unless it to a troubleshooting index ;) ... I may even compile one up myself for personal use as I only use the wiki for troubleshooting and I tend to do more reading and searching than anything else. Something like this would be easy to create on the fly. Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Le jeudi 09 octobre 2008 à 09:10 -0700, Michael Shiloh a écrit : > Xavier Bestel wrote: > > I always use the manual iwconfig+udhcpc method. It works most of the > > time right after reboot, but often looses the network after a few > > minutes (sometimes it works for hals an hour). After that, redoing the > > iwconfig sometimes works, sometimes not and another reboot is in order. > > > Very interesting. Do you kill udhcpc in between invokations? I think > it's a daemon. Yes (in fact I tried both ways). > Of course the real issue is why in looses the connection. I presume you > have suspend disabled? Yes. > Have you tried a different channel? One of my neighbors is on a close > channel and things got better when I changed my AP to an unused channel. > iwlist is a great help here. I didn't try that, but every other wifi device had no problem so far. Changing the channel on the other end is a bit tricky. > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Disable_power_management > suggests that power management caused problems. You might try this too. I tried that long ago, thought I found the magic bullet at first, but nowadays it seems it doesn nothing. > Please let us know what works and what doesn't. Better yet add it to the > wiki. HTH, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Xavier Bestel wrote: > On Wed, 2008-10-08 at 16:19 -0700, Michael Shiloh wrote: >> Just did that. I reorganized the WLAN page and incoporated a number of >> community suggestions, including Tom's. >> >> In particular, this should work for most people: >> >> http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_iwconfig_manually >> >> Feedback and other working examples appreciated. > > Is feedback by mail ok ? It is my favorite method actually :-) > > I always use the manual iwconfig+udhcpc method. It works most of the > time right after reboot, but often looses the network after a few > minutes (sometimes it works for hals an hour). After that, redoing the > iwconfig sometimes works, sometimes not and another reboot is in order. Very interesting. Do you kill udhcpc in between invokations? I think it's a daemon. Of course the real issue is why in looses the connection. I presume you have suspend disabled? Have you tried a different channel? One of my neighbors is on a close channel and things got better when I changed my AP to an unused channel. iwlist is a great help here. http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Disable_power_management suggests that power management caused problems. You might try this too. Please let us know what works and what doesn't. Better yet add it to the wiki. Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Sarton O'Brien wrote: > On Thursday 09 October 2008 11:50:14 Steve Mosher wrote: >> well since this is wifi specific it needs to be referenced in the wifi >> section. If I had the wifi problem THAT would be the first place I >> looked. or in the known problem section. > > I can't say I'm extremely familiar with the wiki but I imagine there is a > troubleshooting section? With possibly a FAQ? I think a link to the selected > blogs page would be valuable in such a place along with a link on the wiki > index. All things wifi, including known issues and a link to Tom's article, are here: http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi > > As blogs tend be general, linking specifically within wifi might not be > appropriate but a link to the troubleshooting page within wifi that then > allows you to choose internal or external sources of information sounds > better > and keeps the non-official documentation contained and a little more > consolidated for all areas of troubleshooting. For actual wiki content this > isn't a problem but it would allow for an actual troubleshooting index of > wiki > approved content as well. > > I imagine linking directly, even if only to the selected blogs page, may > require more maintenance down the track as online information is pretty fluid > and relevance can change pretty quickly. If the site disappeared you'd have > to > modify more than one page to accommodate it. Having two primary links, faqs > and troubleshooting, seems less confusing and easier to maintain to me. > > Just a thought :) > > Sarton > > ___ > 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: [2008.9] Wifi very unreliable
On Wed, 2008-10-08 at 16:19 -0700, Michael Shiloh wrote: > Just did that. I reorganized the WLAN page and incoporated a number of > community suggestions, including Tom's. > > In particular, this should work for most people: > > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_iwconfig_manually > > Feedback and other working examples appreciated. Is feedback by mail ok ? I always use the manual iwconfig+udhcpc method. It works most of the time right after reboot, but often looses the network after a few minutes (sometimes it works for hals an hour). After that, redoing the iwconfig sometimes works, sometimes not and another reboot is in order. HTH, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Thursday 09 October 2008 11:50:14 Steve Mosher wrote: > well since this is wifi specific it needs to be referenced in the wifi > section. If I had the wifi problem THAT would be the first place I > looked. or in the known problem section. I can't say I'm extremely familiar with the wiki but I imagine there is a troubleshooting section? With possibly a FAQ? I think a link to the selected blogs page would be valuable in such a place along with a link on the wiki index. As blogs tend be general, linking specifically within wifi might not be appropriate but a link to the troubleshooting page within wifi that then allows you to choose internal or external sources of information sounds better and keeps the non-official documentation contained and a little more consolidated for all areas of troubleshooting. For actual wiki content this isn't a problem but it would allow for an actual troubleshooting index of wiki approved content as well. I imagine linking directly, even if only to the selected blogs page, may require more maintenance down the track as online information is pretty fluid and relevance can change pretty quickly. If the site disappeared you'd have to modify more than one page to accommodate it. Having two primary links, faqs and troubleshooting, seems less confusing and easier to maintain to me. Just a thought :) Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
well since this is wifi specific it needs to be referenced in the wifi section. If I had the wifi problem THAT would be the first place I looked. or in the known problem section. Michael Shiloh wrote: > Joel Newkirk wrote: >> On Wed, 08 Oct 2008 09:42:00 -0700, Michael Shiloh <[EMAIL PROTECTED]> >> wrote: >>> Tom Yates wrote: On Sun, 5 Oct 2008, Steve Mosher wrote: > Thanks, >Maybe you could work with micheal to put this on the wiki. i also wrote up my positive experiences with openmoko (see at http://www.teaparty.net/technotes/openmoko-2.html , if you like). is there some mileage in a wiki page where people can link to their writeups, each with perhaps a paragraph of "this is what i managed to >>> do, and it's documented here and here and here"? i know in an ideal world i'd've written all my stuff up on the wiki itself, but i just writing it all down was hard enough work; wikialising it was more than i could bear, and i may not be the only such person. >>> Great post. I'll extract some things for the wiki. You of course are >>> invited to do the same. >>> >>> I don't think we have a specific page linking to other people's pages. >>> Usually they are linked in various relevant sections (e.g. since you >>> give an excellent wifi writeup, yours might be a good page to link to >>> from our wifi section). Perhaps we need to rethink this (on the >>> documentation list). >> What about >> http://wiki.openmoko.org/wiki/FreeRunner:_Selected_Blogs_and_Articles? Is >> it intended strictly for blogs and 'news' articles? > > Excellent. Done. > > > ___ > 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: [2008.9] Wifi very unreliable
We should allow for links to peoples pages. Michael Shiloh wrote: > Tom Yates wrote: >> On Sun, 5 Oct 2008, Steve Mosher wrote: >> >>> Thanks, >>>Maybe you could work with micheal to put this on the wiki. >> i also wrote up my positive experiences with openmoko (see at >> http://www.teaparty.net/technotes/openmoko-2.html , if you like). is >> there some mileage in a wiki page where people can link to their >> writeups, each with perhaps a paragraph of "this is what i managed to do, >> and it's documented here and here and here"? >> >> i know in an ideal world i'd've written all my stuff up on the wiki >> itself, but i just writing it all down was hard enough work; wikialising >> it was more than i could bear, and i may not be the only such person. >> >> > > Great post. I'll extract some things for the wiki. You of course are > invited to do the same. > > I don't think we have a specific page linking to other people's pages. > Usually they are linked in various relevant sections (e.g. since you > give an excellent wifi writeup, yours might be a good page to link to > from our wifi section). Perhaps we need to rethink this (on the > documentation list). > > ___ > 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: [2008.9] Wifi very unreliable
Just did that. I reorganized the WLAN page and incoporated a number of community suggestions, including Tom's. In particular, this should work for most people: http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_iwconfig_manually Feedback and other working examples appreciated. Michael Steve Mosher wrote: > michael could you and brenda assist Tom > > Tom Yates wrote: >> On Sun, 5 Oct 2008, Steve Mosher wrote: >> >>> Thanks, >>>Maybe you could work with micheal to put this on the wiki. >> >> i also wrote up my positive experiences with openmoko (see at >> http://www.teaparty.net/technotes/openmoko-2.html , if you like). is >> there some mileage in a wiki page where people can link to their >> writeups, each with perhaps a paragraph of "this is what i managed to >> do, and it's documented here and here and here"? >> >> i know in an ideal world i'd've written all my stuff up on the wiki >> itself, but i just writing it all down was hard enough work; >> wikialising it was more than i could bear, and i may not be the only >> such person. >> >> > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
michael could you and brenda assist Tom Tom Yates wrote: > On Sun, 5 Oct 2008, Steve Mosher wrote: > >> Thanks, >>Maybe you could work with micheal to put this on the wiki. > > i also wrote up my positive experiences with openmoko (see at > http://www.teaparty.net/technotes/openmoko-2.html , if you like). is > there some mileage in a wiki page where people can link to their > writeups, each with perhaps a paragraph of "this is what i managed to do, > and it's documented here and here and here"? > > i know in an ideal world i'd've written all my stuff up on the wiki > itself, but i just writing it all down was hard enough work; wikialising > it was more than i could bear, and i may not be the only such person. > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Joel Newkirk wrote: > On Wed, 08 Oct 2008 09:42:00 -0700, Michael Shiloh <[EMAIL PROTECTED]> > wrote: >> Tom Yates wrote: >>> On Sun, 5 Oct 2008, Steve Mosher wrote: >>> Thanks, Maybe you could work with micheal to put this on the wiki. >>> i also wrote up my positive experiences with openmoko (see at >>> http://www.teaparty.net/technotes/openmoko-2.html , if you like). is >>> there some mileage in a wiki page where people can link to their >>> writeups, each with perhaps a paragraph of "this is what i managed to >> do, >>> and it's documented here and here and here"? >>> >>> i know in an ideal world i'd've written all my stuff up on the wiki >>> itself, but i just writing it all down was hard enough work; wikialising >>> it was more than i could bear, and i may not be the only such person. >>> >>> >> Great post. I'll extract some things for the wiki. You of course are >> invited to do the same. >> >> I don't think we have a specific page linking to other people's pages. >> Usually they are linked in various relevant sections (e.g. since you >> give an excellent wifi writeup, yours might be a good page to link to >> from our wifi section). Perhaps we need to rethink this (on the >> documentation list). > > What about > http://wiki.openmoko.org/wiki/FreeRunner:_Selected_Blogs_and_Articles? Is > it intended strictly for blogs and 'news' articles? Excellent. Done. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, 08 Oct 2008 09:42:00 -0700, Michael Shiloh <[EMAIL PROTECTED]> wrote: > Tom Yates wrote: >> On Sun, 5 Oct 2008, Steve Mosher wrote: >> >>> Thanks, >>>Maybe you could work with micheal to put this on the wiki. >> >> i also wrote up my positive experiences with openmoko (see at >> http://www.teaparty.net/technotes/openmoko-2.html , if you like). is >> there some mileage in a wiki page where people can link to their >> writeups, each with perhaps a paragraph of "this is what i managed to > do, >> and it's documented here and here and here"? >> >> i know in an ideal world i'd've written all my stuff up on the wiki >> itself, but i just writing it all down was hard enough work; wikialising >> it was more than i could bear, and i may not be the only such person. >> >> > > Great post. I'll extract some things for the wiki. You of course are > invited to do the same. > > I don't think we have a specific page linking to other people's pages. > Usually they are linked in various relevant sections (e.g. since you > give an excellent wifi writeup, yours might be a good page to link to > from our wifi section). Perhaps we need to rethink this (on the > documentation list). What about http://wiki.openmoko.org/wiki/FreeRunner:_Selected_Blogs_and_Articles? Is it intended strictly for blogs and 'news' articles? j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Tom Yates wrote: > On Sun, 5 Oct 2008, Steve Mosher wrote: > >> Thanks, >>Maybe you could work with micheal to put this on the wiki. > > i also wrote up my positive experiences with openmoko (see at > http://www.teaparty.net/technotes/openmoko-2.html , if you like). is > there some mileage in a wiki page where people can link to their > writeups, each with perhaps a paragraph of "this is what i managed to do, > and it's documented here and here and here"? > > i know in an ideal world i'd've written all my stuff up on the wiki > itself, but i just writing it all down was hard enough work; wikialising > it was more than i could bear, and i may not be the only such person. > > Great post. I'll extract some things for the wiki. You of course are invited to do the same. I don't think we have a specific page linking to other people's pages. Usually they are linked in various relevant sections (e.g. since you give an excellent wifi writeup, yours might be a good page to link to from our wifi section). Perhaps we need to rethink this (on the documentation list). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Sun, 5 Oct 2008, Steve Mosher wrote: > Thanks, >Maybe you could work with micheal to put this on the wiki. i also wrote up my positive experiences with openmoko (see at http://www.teaparty.net/technotes/openmoko-2.html , if you like). is there some mileage in a wiki page where people can link to their writeups, each with perhaps a paragraph of "this is what i managed to do, and it's documented here and here and here"? i know in an ideal world i'd've written all my stuff up on the wiki itself, but i just writing it all down was hard enough work; wikialising it was more than i could bear, and i may not be the only such person. -- Tom Yates - http://www.teaparty.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Thanks, Maybe you could work with micheal to put this on the wiki. Ed Kapitein wrote: > Hi Mathias, > > I even took it one step further. > I can not get it to work properly on channel 11, so i set my accesspoint to > channel 1. > And i changed the script a little: > Exec=xterm -e "ifconfig eth0 down ; iwconfig eth0 txpower off channel 0 ; > while killall wpa_supplicant; do echo 'Killing wpa_sup'; done ; killall > udhcpc ; wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf > -D wext -B; sleep 10; udhcpc" > > Now it is working every time. > I am using 2008.latest (081004) and a linksys WAP54G accesspoint, running > Firmware Version: 3.05. > in mixed mode, broadcast enabled, encryption WPA-Personal, passphrase > without a space charachter in it. > ( i am no sure if any of this matters, but it gives the settings with which > i have it working) > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Hi Mathias, I even took it one step further. I can not get it to work properly on channel 11, so i set my accesspoint to channel 1. And i changed the script a little: Exec=xterm -e "ifconfig eth0 down ; iwconfig eth0 txpower off channel 0 ; while killall wpa_supplicant; do echo 'Killing wpa_sup'; done ; killall udhcpc ; wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B; sleep 10; udhcpc" Now it is working every time. I am using 2008.latest (081004) and a linksys WAP54G accesspoint, running Firmware Version: 3.05. in mixed mode, broadcast enabled, encryption WPA-Personal, passphrase without a space charachter in it. ( i am no sure if any of this matters, but it gives the settings with which i have it working) -- View this message in context: http://n2.nabble.com/-2008.9--Wifi-very-unreliable-tp1128409p1299065.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Jay Vaughan <[EMAIL PROTECTED]> writes: >> As much as I love my FR, I must admit that the whole experience had >> me thinking lustful thoughts about my wife's iPhone... > > > I would say just get an iPhone. I did. Its much more fun to develop > for a *platform* rather than a constant dogs-breakfast of disaster. > Until someone in the Freerunner world turns the thing into a stable > platform, its just going to go on and on forever with nothing ever > being fixed, stably, and dependably. > > I mean, give me a break. Its October, and people are *still* > wrestling with WLAN configuration. Can you hackers not see how stupid > it is to be fussing with 'pretty stuff' when the most basic things > don't even work? > > I've given up on Freerunner development. Until there is a stable > image that provides an Operating System (what we have now: Inoperable) > its just not worth the fuss. The Freerunner project has been > murdered, in my opinion, by hobby horsing hackers who have nothing but > hatred for the end users that *could* be using the thing. Just to add some perspective, for my intended applications the iPh*ne is not an option. On the other hand, any suitable open handheld gnu/linux device with gps and phone hardware would work. If competing hardware forfilling these requirements showed up, I could easily switch hardware. > ; > -- > Jay Vaughan -- Joakim Verona ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Thu, Oct 2, 2008 at 2:36 PM, Stroller <[EMAIL PROTECTED]>wrote: > Nishit, > > The company that sold you your Freerunner offered you refund, already. > > I assumed that you would take this, leave the list and STOP FUCKING > WHINING. > > I guess this was too much for me to hope for, huh? > > Dude, I will decide what to say, till the time I return the FR, if I decide to do so. If you don't like what I say, complain to the list maintainers. Otherwise, hold your tongue or come up with a solution. I have showed my commitment to a cause by putting my money where my mouth is, and I didn't do it because I wanted to hop on to the embedded linux shebang. If I feel that I have been let down, I have every right to say so. Refunds do not make up for lost time. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
vale, > i think this should also be a high priority aspect to work on for > Openmoko. It is, and for Atheros too. We are working on improving the driver (there are several driver variants actually), we are working on getting all of this into mainline kernel.org, we are working with Atheros to open up more possibilities with regards to reflashing the chip, providing 'thin' firmwares that allow monitor/injection modes etc. Any help is appreciated, bug reports with clear reproduction steps are very helpful too. Best Regards, Wolfgang On Oct 2, 2008, at 9:19 PM, vale wrote: > > calm down, > > its a fact, that freerunners wlan is far away from optimum. > > try a wget shortly after doing ifup eth0 -> everything works > try wget some minutes later (no suspend/resume in between) from same > server > -> no download, even if ping still works > ifdown eth0, ifup eth0 -> wget works again > > same with opkg install, update, upgrade etc. > > under 2007.2, 2008.08, debian ... > > -> wlan drivers not working well > > i think this should also be a high priority aspect to work on for > Openmoko. > > bye > > vale > > Stroller-2 wrote: >> >> >> On 1 Oct 2008, at 12:28, Nishit Dave wrote: >>> >>> All this discussion does not help if you realize that even after >>> placing the FR *next* to the blooming router, you get reported a >>> signal strength of 65%. What does the hardware expect, building the >>> router *inside* the FR? >> >> Nishit, >> >> The company that sold you your Freerunner offered you refund, >> already. >> >> I assumed that you would take this, leave the list and STOP FUCKING >> WHINING. >> >> I guess this was too much for me to hope for, huh? >> >> Stroller. >> >> >> _______ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> >> > > -- > View this message in context: > http://n2.nabble.com/-2008.9--Wifi-very-unreliable-tp1128409p1133869.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > > ___ > 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: [2008.9] Wifi very unreliable
thats cool ... wish it would work here too, but my experience is different. doesn't matter if i try @university @home @public places or @highly secured wlans with project partners. wlan gets stuck after a few minutes of inactivity. i don't know why. how can i stop this power thing over wlan? perhaps that is the problem ... i like my freerunner, but sometimes its frustrating not beeing able to rely on basic things as wlan is. i hope its getting better soon :) vale Matthias Apitz wrote: > > El día Thursday, October 02, 2008 a las 04:39:01PM +0100, Alastair Johnson > escribió: > >> vale wrote: >> > add a sleep 500 to your loop ;) > > I run this script for an hour or so: > > [EMAIL PROTECTED]:~# cat wifi.sh > #!/bin/sh > cd /tmp > while true; do > > rm 1M > wget http://www.unixarea.de/1M > date ; echo -n "now sleeping 300 sec ... " > sleep 300 > echo awaked > > done > > and there has been no problem all this time; as well ifconfig does not > show any error packets: > > [EMAIL PROTECTED]:~# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:12:CF:8E:FC:5F > inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 > inet6 addr: fe80::212:cfff:fe8e:fc5f/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:302728 errors:0 dropped:0 overruns:0 frame:0 > TX packets:131532 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:454345265 (433.2 MiB) TX bytes:10145574 (9.6 MiB) > > and if you compare the RX/TX values with those from the last post: > > RX packets:285483 errors:0 dropped:0 overruns:0 frame:0 > TX packets:121870 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:431367301 (411.3 MiB) TX bytes:9439240 (9.0 MiB) > > you see that moving from office to my home, i.e. from one AP to another, > I did not rebooted; I just ifdow / ifup with my script the eth0 > interface; > >> > >> > which image / kernel are you using? >> >> You should perhaps ask what AP he's using, or whether he has the power >> management enabled on the wifi. Some APs apparently get upset by power >> managed devices, and the Freerunner enables power management of the wifi >> by default to preserve battery. My wrt54g certainly gets upset from time >> to time if I connect with the freerunner, sometimes refusing to talk to >> _anything_ over wifi afterwards until rebooted. > > my AP at home is a SMCWBR14-G2 EU one; regardless of the FR already in > the past sometime this get stuck and needs a power-cycle; not during the > test today; > > the actual iwconfig values are: > > # iwconfig eth0 > eth0 AR6000 802.11g ESSID:"tarara" > Mode:Managed Frequency:2.442 GHz Access Point: > 00:13:F7:0D:08:48 > Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 > Retry:on > Encryption key:X Security mode:open > Power Management:off > Link Quality:207/94 Signal level:-144 dBm Noise level:-96 dBm > Rx invalid nwid:0 Rx invalid crypt:1487 Rx invalid frag:0 > Tx excessive retries:55 Invalid misc:0 Missed beacon:64 > > HIH > > matthias > > -- > Matthias Apitz > Manager Technical Support - OCLC GmbH > Gruenwalder Weg 28g - 82041 Oberhaching - Germany > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e <[EMAIL PROTECTED]> - w http://www.oclc.org/ > http://www.UnixArea.de/ > b http://gurucubano.blogspot.com/ > A computer is like an air conditioner, it stops working when you open > Windows > Una computadora es como aire acondicionado, deja de funcionar si abres > Windows > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-2008.9--Wifi-very-unreliable-tp1128409p1134675.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Thursday, October 02, 2008 a las 04:39:01PM +0100, Alastair Johnson escribió: > vale wrote: > > add a sleep 500 to your loop ;) I run this script for an hour or so: [EMAIL PROTECTED]:~# cat wifi.sh #!/bin/sh cd /tmp while true; do rm 1M wget http://www.unixarea.de/1M date ; echo -n "now sleeping 300 sec ... " sleep 300 echo awaked done and there has been no problem all this time; as well ifconfig does not show any error packets: [EMAIL PROTECTED]:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:12:CF:8E:FC:5F inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::212:cfff:fe8e:fc5f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:302728 errors:0 dropped:0 overruns:0 frame:0 TX packets:131532 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:454345265 (433.2 MiB) TX bytes:10145574 (9.6 MiB) and if you compare the RX/TX values with those from the last post: RX packets:285483 errors:0 dropped:0 overruns:0 frame:0 TX packets:121870 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:431367301 (411.3 MiB) TX bytes:9439240 (9.0 MiB) you see that moving from office to my home, i.e. from one AP to another, I did not rebooted; I just ifdow / ifup with my script the eth0 interface; > > > > which image / kernel are you using? > > You should perhaps ask what AP he's using, or whether he has the power > management enabled on the wifi. Some APs apparently get upset by power > managed devices, and the Freerunner enables power management of the wifi > by default to preserve battery. My wrt54g certainly gets upset from time > to time if I connect with the freerunner, sometimes refusing to talk to > _anything_ over wifi afterwards until rebooted. my AP at home is a SMCWBR14-G2 EU one; regardless of the FR already in the past sometime this get stuck and needs a power-cycle; not during the test today; the actual iwconfig values are: # iwconfig eth0 eth0 AR6000 802.11g ESSID:"tarara" Mode:Managed Frequency:2.442 GHz Access Point: 00:13:F7:0D:08:48 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:X Security mode:open Power Management:off Link Quality:207/94 Signal level:-144 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:1487 Rx invalid frag:0 Tx excessive retries:55 Invalid misc:0 Missed beacon:64 HIH matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
> As much as I love my FR, I must admit that the whole experience had > me thinking lustful thoughts about my wife's iPhone... I would say just get an iPhone. I did. Its much more fun to develop for a *platform* rather than a constant dogs-breakfast of disaster. Until someone in the Freerunner world turns the thing into a stable platform, its just going to go on and on forever with nothing ever being fixed, stably, and dependably. I mean, give me a break. Its October, and people are *still* wrestling with WLAN configuration. Can you hackers not see how stupid it is to be fussing with 'pretty stuff' when the most basic things don't even work? I've given up on Freerunner development. Until there is a stable image that provides an Operating System (what we have now: Inoperable) its just not worth the fuss. The Freerunner project has been murdered, in my opinion, by hobby horsing hackers who have nothing but hatred for the end users that *could* be using the thing. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Thu, Oct 2, 2008 at 9:19 AM, vale <[EMAIL PROTECTED]> wrote: > > its a fact, that freerunners wlan is far away from optimum. > > [...] > > -> wlan drivers not working well > > i think this should also be a high priority aspect to work on for Openmoko. I definitely agree. I was recently at a conference and trying to use my freerunner as a mobile web device with the conference wlan - an open network, so I didn't have to worry about encryption. I connected with my laptop a number of times, and everything ran smoothly - however, my FR gave me no end of problems. If I rebooted and tried connecting with Mofi, I could sometimes connect - maybe 1 time in 3. Once I connected, I could browse for a while with Minimo (which worked quite nicely), but then it would hang, and I'd have to reboot several times again before I could get connected again. I've had similar experiences before - I can rarely connect to our open guest network at my office, I've never managed to connect successfully the few times I've tried at Cafe's with free wifi, and I haven't managed to get it to connect at all to our wifi network at home. As much as I love my FR, I must admit that the whole experience had me thinking lustful thoughts about my wife's iPhone... BTW - I'm running FDOM 20080913. Warren ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
vale wrote: > add a sleep 500 to your loop ;) > > which image / kernel are you using? You should perhaps ask what AP he's using, or whether he has the power management enabled on the wifi. Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. My wrt54g certainly gets upset from time to time if I connect with the freerunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Thursday, October 02, 2008 a las 07:35:23AM -0700, vale escribió: > > add a sleep 500 to your loop ;) will do later at home and post the results; > > which image / kernel are you using? Om2008.9-gta02-20080916.rootfs.jffs2 Om2008.9-gta02-20080916.uImage.bin matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
add a sleep 500 to your loop ;) which image / kernel are you using? thx vale Matthias Apitz wrote: > > El día Thursday, October 02, 2008 a las 06:19:30AM -0700, vale escribió: > >> >> calm down, >> >> its a fact, that freerunners wlan is far away from optimum. >> >> try a wget shortly after doing ifup eth0 -> everything works >> try wget some minutes later (no suspend/resume in between) from same >> server >> -> no download, even if ping still works >> ifdown eth0, ifup eth0 -> wget works again >> >> same with opkg install, update, upgrade etc. >> >> under 2007.2, 2008.08, debian ... >> >> -> wlan drivers not working well > > I can't ACK that anymore; I have wget ten times a file of 22 MByte right > now: > > # for i in 1 2 3 4 5 6 7 8 9 10 ; do rm file ; wget > http://albatros/share/sisis-dev/guru/file; done > Connecting to albatros (10.0.1.98:80) > file100% > || 22942k > 00:00:00 ETA > (10x) > > without any kind of hick-ups; > and the interface does not show any kind of error: > > [EMAIL PROTECTED]:~# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:12:CF:8E:FC:5F > inet addr:10.0.1.217 Bcast:10.0.1.255 Mask:255.255.255.0 > inet6 addr: fe80::212:cfff:fe8e:fc5f/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:285483 errors:0 dropped:0 overruns:0 frame:0 > TX packets:121870 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:431367301 (411.3 MiB) TX bytes:9439240 (9.0 MiB) > > [EMAIL PROTECTED]:~# iwlist eth0 scan > eth0 Scan completed : > Cell 01 - Address: 00:04:E2:A1:76:0B > ESSID:"santaclara" > Mode:Master > Frequency:2.442 GHz (Channel 7) > Quality=16/94 Signal level=-79 dBm Noise level=-95 > dBm > Encryption key:on > Extra:bcn_int=100 > Extra:wpa_ie=... > > > i.e. Wifi for me it works fine now; > > matthias > > -- > Matthias Apitz > Manager Technical Support - OCLC GmbH > Gruenwalder Weg 28g - 82041 Oberhaching - Germany > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e <[EMAIL PROTECTED]> - w http://www.oclc.org/ > http://www.UnixArea.de/ > b http://gurucubano.blogspot.com/ > A computer is like an air conditioner, it stops working when you open > Windows > Una computadora es como aire acondicionado, deja de funcionar si abres > Windows > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-2008.9--Wifi-very-unreliable-tp1128409p1134044.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Thursday, October 02, 2008 a las 06:19:30AM -0700, vale escribió: > > calm down, > > its a fact, that freerunners wlan is far away from optimum. > > try a wget shortly after doing ifup eth0 -> everything works > try wget some minutes later (no suspend/resume in between) from same server > -> no download, even if ping still works > ifdown eth0, ifup eth0 -> wget works again > > same with opkg install, update, upgrade etc. > > under 2007.2, 2008.08, debian ... > > -> wlan drivers not working well I can't ACK that anymore; I have wget ten times a file of 22 MByte right now: # for i in 1 2 3 4 5 6 7 8 9 10 ; do rm file ; wget http://albatros/share/sisis-dev/guru/file; done Connecting to albatros (10.0.1.98:80) file100% || 22942k 00:00:00 ETA (10x) without any kind of hick-ups; and the interface does not show any kind of error: [EMAIL PROTECTED]:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:12:CF:8E:FC:5F inet addr:10.0.1.217 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::212:cfff:fe8e:fc5f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:285483 errors:0 dropped:0 overruns:0 frame:0 TX packets:121870 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:431367301 (411.3 MiB) TX bytes:9439240 (9.0 MiB) [EMAIL PROTECTED]:~# iwlist eth0 scan eth0 Scan completed : Cell 01 - Address: 00:04:E2:A1:76:0B ESSID:"santaclara" Mode:Master Frequency:2.442 GHz (Channel 7) Quality=16/94 Signal level=-79 dBm Noise level=-95 dBm Encryption key:on Extra:bcn_int=100 Extra:wpa_ie=... i.e. Wifi for me it works fine now; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
calm down, its a fact, that freerunners wlan is far away from optimum. try a wget shortly after doing ifup eth0 -> everything works try wget some minutes later (no suspend/resume in between) from same server -> no download, even if ping still works ifdown eth0, ifup eth0 -> wget works again same with opkg install, update, upgrade etc. under 2007.2, 2008.08, debian ... -> wlan drivers not working well i think this should also be a high priority aspect to work on for Openmoko. bye vale Stroller-2 wrote: > > > On 1 Oct 2008, at 12:28, Nishit Dave wrote: >> >> All this discussion does not help if you realize that even after >> placing the FR *next* to the blooming router, you get reported a >> signal strength of 65%. What does the hardware expect, building the >> router *inside* the FR? > > Nishit, > > The company that sold you your Freerunner offered you refund, already. > > I assumed that you would take this, leave the list and STOP FUCKING > WHINING. > > I guess this was too much for me to hope for, huh? > > Stroller. > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-2008.9--Wifi-very-unreliable-tp1128409p1133869.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On 1 Oct 2008, at 12:28, Nishit Dave wrote: > > All this discussion does not help if you realize that even after > placing the FR *next* to the blooming router, you get reported a > signal strength of 65%. What does the hardware expect, building the > router *inside* the FR? Nishit, The company that sold you your Freerunner offered you refund, already. I assumed that you would take this, leave the list and STOP FUCKING WHINING. I guess this was too much for me to hope for, huh? Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, 2008-10-01 at 16:58 +0530, Nishit Dave wrote: > On Wed, Oct 1, 2008 at 6:05 AM, Sarton O'Brien > <[EMAIL PROTECTED]> wrote: ... > > > All this discussion does not help if you realize that even after > placing the FR *next* to the blooming router, you get reported a > signal strength of 65%. What does the hardware expect, building the > router *inside* the FR? > Dont forget that wifi drivers in general are HIGHLY inaccurate with regards to signal strength and any other figure you care to name. The mad-wifi drivers on linux used to give wildly varying figures from version to version on the same laptop a couple of years ago as an example. Also have a look at what many windows drivers report ... They are really only useful as a relative figure within the device/version on the day of use (yes, they can be that bad :( BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, Oct 1, 2008 at 5:49 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > On Wed, 2008-10-01 at 17:36 +0530, Nishit Dave wrote: > > On Wed, Oct 1, 2008 at 5:22 PM, Xavier Bestel <[EMAIL PROTECTED]> > > wrote: > > On Wed, 2008-10-01 at 16:58 +0530, Nishit Dave wrote: > > > > > > > All this discussion does not help if you realize that even > > after > > > placing the FR *next* to the blooming router, you get > > reported a > > > signal strength of 65%. What does the hardware expect, > > building the > > > router *inside* the FR? > > > > > > Note that interferences may weaken an otherwise perfectly good > > signal. > > So the proximity isn't always synonymous with good signal > > strengh. > > > >Xav > > > > No? > > Well, the closer you are, the better the signal is. > But in my building, there are many other wifi networks. And in the > evening, when they are all in use, I get a worst signal even when near > my AP, whereas e.g. during the night it's better. At least I seem to > have observed that. > > Have you used Occam's Razor on that? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, 2008-10-01 at 17:36 +0530, Nishit Dave wrote: > On Wed, Oct 1, 2008 at 5:22 PM, Xavier Bestel <[EMAIL PROTECTED]> > wrote: > On Wed, 2008-10-01 at 16:58 +0530, Nishit Dave wrote: > > > > All this discussion does not help if you realize that even > after > > placing the FR *next* to the blooming router, you get > reported a > > signal strength of 65%. What does the hardware expect, > building the > > router *inside* the FR? > > > Note that interferences may weaken an otherwise perfectly good > signal. > So the proximity isn't always synonymous with good signal > strengh. > >Xav > > No? Well, the closer you are, the better the signal is. But in my building, there are many other wifi networks. And in the evening, when they are all in use, I get a worst signal even when near my AP, whereas e.g. during the night it's better. At least I seem to have observed that. Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, Oct 1, 2008 at 5:22 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > On Wed, 2008-10-01 at 16:58 +0530, Nishit Dave wrote: > > > > All this discussion does not help if you realize that even after > > placing the FR *next* to the blooming router, you get reported a > > signal strength of 65%. What does the hardware expect, building the > > router *inside* the FR? > > Note that interferences may weaken an otherwise perfectly good signal. > So the proximity isn't always synonymous with good signal strengh. > >Xav > No? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, 2008-10-01 at 16:58 +0530, Nishit Dave wrote: > All this discussion does not help if you realize that even after > placing the FR *next* to the blooming router, you get reported a > signal strength of 65%. What does the hardware expect, building the > router *inside* the FR? Note that interferences may weaken an otherwise perfectly good signal. So the proximity isn't always synonymous with good signal strengh. Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, Oct 1, 2008 at 6:05 AM, Sarton O'Brien <[EMAIL PROTECTED]>wrote: > > I use testing and have varied success with wifi. I don't bother with trying > to > identify what going on by what's being reported. It has been stated on here > that the issues with the driver are great enough that statistics may be > skewed. > > What I have witnessed is that sometimes it appears the wireless hardware is > next to useless ... but then under a different update or on another day it > functions flawlessly even in a problematic area of the house. When I was > running stable with no real updates coming down, I couldn't even be > bothered > with wireless. > > At the moment, I am having issues. Selecting wireless 'on' results in > nothing > being displayed. I have to push all my scripts back across so I haven't > tested > manually yet. > > So in summary, I don't think it's worth attempting to figure this out as an > end user as yet. I believe it's driver/kernel related. The hardware itself > is > quite new so it doesn't really surprise me. I'd wait for a statement as > _everybody_ has this problem. I can't imagine the devs are sitting there > with > freerunners and working wireless ;) > > All this discussion does not help if you realize that even after placing the FR *next* to the blooming router, you get reported a signal strength of 65%. What does the hardware expect, building the router *inside* the FR? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Wed, 2008-10-01 at 10:10 +0200, Matthias Apitz wrote: > El día Tuesday, September 30, 2008 a las 08:52:14PM +0800, William Kenworthy > escribió: > > > On Tue, 2008-09-30 at 14:37 +0200, Matthias Apitz wrote: > ... > > Hi William, > > A bit inspired by your commands since yesterday I have changed the > desktop file /usr/share/applications/Wifi-up.desktop into this: > ... I will use your desktop icon version - better than typing it in the terminal! also the -u isnt in gentoo's wpa_supplicant either, but: [EMAIL PROTECTED]:~# wpa_supplicant -h wpa_supplicant v0.6.3 Copyright (c) 2003-2008, Jouni Malinen <[EMAIL PROTECTED]> and contributors This program is free software. You can distribute it and/or modify it under the terms of the GNU General Public License version 2. Alternatively, this software may be distributed under the terms of the BSD license. See README and COPYING for more details. usage: wpa_supplicant [-BddhKLqqtuvwW] [-P] [-g] \ -i -c [-C] [-D] [-p] \ [-b] [-f] \ [-N -i -c [-C] [-D] \ [-p] [-b] ...] drivers: wext = Linux wireless extensions (generic) hostap = Host AP driver (Intersil Prism2/2.5/3) wired = wpa_supplicant wired Ethernet driver options: -b = optional bridge interface name -B = run daemon in the background -c = Configuration file -C = ctrl_interface parameter (only used if -c is not) -i = interface name -d = increase debugging verbosity (-dd even more) -D = driver name -g = global ctrl_interface -K = include keys (passwords, etc.) in debug output -t = include timestamp in debug messages -h = show this help text -L = show license (GPL and BSD) -p = driver parameters -P = PID file -q = decrease debugging verbosity (-qq even less) -u = enable DBus control interface -v = show version -W = wait for a control interface monitor before starting -N = start describing new interface example: wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf [EMAIL PROTECTED]:~# ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Tuesday, September 30, 2008 a las 08:52:14PM +0800, William Kenworthy escribió: > On Tue, 2008-09-30 at 14:37 +0200, Matthias Apitz wrote: > > El día Tuesday, September 30, 2008 a las 08:11:48PM +1000, Alex Osborne > > escribió: > > > > > Matthias Apitz wrote: > > > > I'm trying to bring up the eth0 with > > > > > > > ># ifup eth0 > > > > > > > > > ... > > > > matthias > > Hi Matthias, I am using these scripts with the unmodified Om 2008.9 > system successfully to connect to a linksys wrt150 running wpa. The > only caveat is that the FR has a good signal when connecting. Turn on > wifi using the settings dialog first - dont select anything else. Same > with mofi etc - if you have used them, reboot first. Then you should be > able to connect/reconnect at will. It seems that some of the background > apps are reluctant to let go of the connection. ... Hi William, A bit inspired by your commands since yesterday I have changed the desktop file /usr/share/applications/Wifi-up.desktop into this: [Desktop Entry] Encoding=UTF-8 Name=Wifi-up Comment=Bring Wifi up with ifup eth0 Exec=xterm -e "ifdown eth0 ; iwconfig eth0 txpower auto channel 1 ; killall wpa_supplicant ; killall udhcp ; ifup eth0 ; sleep 20" Icon=wifi Terminal=false Type=Application Categories=Application;Utilities; SingleInstance=true StartupNotify=true i.e. inserted your iwconfig/killall sequence before bringing up the interface; and now it is associating *every* time in my Wifi area at home (WEP) and in my office (WPA); it even reconnects fine, when I'm leaving the area and re-enter or when I moved from office to home; if I have some time I will investigate why this is now working; maybe there was always some of the wpa_supplicant (the one with the -u flag) left over; don't know what the -u option means, this option does not exist in FreeBSD's wpa_supplicant and the FR has no man pages installed; are they available somewhere in Internet to check? you can imagine how happy I am; thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Tuesday 30 September 2008 19:06:28 Matthias Apitz wrote: > this works very unreliable; in (let's say) 8 of 10 cases it can't > associate to the AP, even not after fresh re-boots and independently if > the AP at my home works with WEP or in my office with WPA; > > what can I do? is someone willing to look into the debug output of the > wpa_supplicant? or do I need somehow an update in the kernel drivers? > > I've installed as well lint-wifi; this does not even see the AP next > door and to which I'm now after 2-3 tries connected too; strange, isn't > it? there must be something broken in kernel land, I think; I use testing and have varied success with wifi. I don't bother with trying to identify what going on by what's being reported. It has been stated on here that the issues with the driver are great enough that statistics may be skewed. What I have witnessed is that sometimes it appears the wireless hardware is next to useless ... but then under a different update or on another day it functions flawlessly even in a problematic area of the house. When I was running stable with no real updates coming down, I couldn't even be bothered with wireless. At the moment, I am having issues. Selecting wireless 'on' results in nothing being displayed. I have to push all my scripts back across so I haven't tested manually yet. So in summary, I don't think it's worth attempting to figure this out as an end user as yet. I believe it's driver/kernel related. The hardware itself is quite new so it doesn't really surprise me. I'd wait for a statement as _everybody_ has this problem. I can't imagine the devs are sitting there with freerunners and working wireless ;) Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On 30/09/2008, at 10:37 PM, Matthias Apitz wrote: > Wireless event: cmd=0x8b1a len=18 > Authentication with 00:04:e2:a1:76:0b timed out. > Added BSSID 00:04:e2:a1:76:0b into blacklist Yeah. That's exactly the same sort of thing I was seeing, which clearing the essid seems to help with most of the time. I occasionally find the wifi just stops working completely for no apparent reason, ping and all other traffic fails but it otherwise seems normal from the iwconfig and ifconfig output. Other times I get pages and pages of this rapidly flooded in dmesg: AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX AR6000 disconnected from XX:XX:XX:XX:XX:XX without any line breaks and where the XX is the access point address. The only thing that seems to fix it when it does that is to reboot. Cheers, Alex ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Tue, 2008-09-30 at 14:37 +0200, Matthias Apitz wrote: > El día Tuesday, September 30, 2008 a las 08:11:48PM +1000, Alex Osborne > escribió: > > > Matthias Apitz wrote: > > > I'm trying to bring up the eth0 with > > > > > ># ifup eth0 > > > > > > ... > > matthias Hi Matthias, I am using these scripts with the unmodified Om 2008.9 system successfully to connect to a linksys wrt150 running wpa. The only caveat is that the FR has a good signal when connecting. Turn on wifi using the settings dialog first - dont select anything else. Same with mofi etc - if you have used them, reboot first. Then you should be able to connect/reconnect at will. It seems that some of the background apps are reluctant to let go of the connection. myth1 root # cat wap #!/bin/sh # Turn on wifi at the settings dialog first! ifdown eth0 iwconfig eth0 txpower auto channel 1 killall wpa_supplicant killall udhcp wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B ; ifup eth0 ___ myth1 root # cat nowap #!/bin/sh ifdown eth0 killall wpa_supplicant iwconfig eth0 txpower off -- William Kenworthy <[EMAIL PROTECTED]> Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
El día Tuesday, September 30, 2008 a las 08:11:48PM +1000, Alex Osborne escribió: > Matthias Apitz wrote: > > I'm trying to bring up the eth0 with > > > ># ifup eth0 > > > >this works very unreliable; in (let's say) 8 of 10 cases it can't > >associate to the AP, even not after fresh re-boots and independently if > >the AP at my home works with WEP or in my office with WPA; > > > I found that with wpa_supplicant there was a problem with disconnecting > from an AP. The essid would apparantly not get cleared properly on the > card (although iwconfig would show it as cleared) and until you manually > cleared it, wpa_supplicant would just sit in a loop trying to connect > and getting authentication timeouts. You can see these message if you > run wpa_cli. I worked around it by adding a pre-up that clears the essid: > > allow-hotplug eth0 > iface eth0 inet manual > wpa-driver wext > wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf > pre-up iwconfig eth0 essid off > > iface default inet dhcp > iface home inet dhcp > > This seems to work reliably for me except that I still have to ifdown > and ifup when I move to a different AP. So if manually connecting with > iwconfig works for you, you could try same workaround. Here's what my > wpa_supplicant.conf looks like: I have as well the feeling that, when I was associated once and leaving the AP physically, I can't re-associate anymore, even not after a boot; I tried your hint about 'iwconfig eth0 essid off' but it does not improve the situation; I've now filed a bug report as https://docs.openmoko.org/trac/ticket/2045 with also a wpa_supplicant debug session; it tries to associate: Trying to associate with 00:04:e2:a1:76:0b (SSID='santaclara' freq=2442 MHz) ... State: SCANNING -> ASSOCIATING wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT) ... Wireless event: cmd=0x8b1a len=18 Authentication with 00:04:e2:a1:76:0b timed out. Added BSSID 00:04:e2:a1:76:0b into blacklist No keys have been configured - skip key clearing State: ASSOCIATING -> DISCONNECTED wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT) ... matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Alex Osborne wrote:
> Matthias Apitz wrote:
>> I'm trying to bring up the eth0 with
>>
>> # ifup eth0
>>
>> this works very unreliable; in (let's say) 8 of 10 cases it can't
>> associate to the AP, even not after fresh re-boots and independently if
>> the AP at my home works with WEP or in my office with WPA;
>>
> I found that with wpa_supplicant there was a problem with disconnecting
> from an AP. The essid would apparantly not get cleared properly on the
> card (although iwconfig would show it as cleared) and until you manually
> cleared it, wpa_supplicant would just sit in a loop trying to connect
> and getting authentication timeouts. You can see these message if you
> run wpa_cli. I worked around it by adding a pre-up that clears the essid:
>
> allow-hotplug eth0
> iface eth0 inet manual
> wpa-driver wext
> wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
> pre-up iwconfig eth0 essid off
>
> iface default inet dhcp
> iface home inet dhcp
>
> This seems to work reliably for me except that I still have to ifdown
> and ifup when I move to a different AP. So if manually connecting with
> iwconfig works for you, you could try same workaround. Here's what my
> wpa_supplicant.conf looks like:
>
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
>
> network={
> ssid="XXX"
> key_mgmt=NONE
> wep_key0=XX
> wep_tx_keyidx=0
> id_str="home"
> }
>
> network={
> key_mgmt=NONE
> }
>
> Note that this is with Debian, not 2008.9 -- I'm not sure whether
> Om2008.9 supports exactly the same /etc/network/interfaces syntax as Debian.
2007.2 was missing some of the scripts (and more?) needed to support
wpa-roam when I tried it. Haven't checked in 2008.x yet. The news about
essid is interesting though.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Okay, I've filed bug #2043 about this. Go ahead and add info if you like. https://docs.openmoko.org/trac/ticket/2043 Citando Daniel Hedblom <[EMAIL PROTECTED]>: > Im also inclined to think its a hardware/driver problem and have > nothing to do with wpa_supplicant or any other highlevel stuff. I > fully understand if higher stuff is left to the community but i did > expect the kernel and low level stuff to work a bit better than now > when i bought the phone. It could ofcourse be just some phones thats > broken and most works well because of some faulty batch. > > Does anyone know if work is happening on the kernel side of wifi or is > it an orphan right now needing more people? > > //danielh > > 2008/9/30 <[EMAIL PROTECTED]>: >> Hi all. >> Now that you mention this, I think the problem is Hardware based. >> I've bought an Asus Eee 901 :D, and now I have a means of comparison >> in terms of WiFi reception. >> My conclusion is that the Neo FR's wifi sucks. >> Example1: >> - my home AP has WPA; sitting 2 meters away from it, the FR show 50% >> signal strength. Okay, you can say that's too close and they are >> "shouting" at each other, causing signal corruption. Very well, I take >> it 10 meters away, behind a couple of normal walls. The signal >> strength drops all the way, right down to 5%, which is pretty >> unusable. The Eee901 has 100% signal strength in the vicinity of the >> AP, and behind those walls shows 30%. >> Example2: >> - at work, the Eee901 picks up 4 weak networks, the strongest one at >> 35% strength and joins (no security) without problems. The FR picks up >> only the stronger one at 8%, and it cannot join it. >> >> This has convinced me that either the wifi on the FR has serious >> hardware problems, or the software is misguiding it. Anyway, it needs >> serious attention. >> Has anyone filed bugs on this wifi problem? >> >> Vasco. >> >> Citando Xavier Bestel <[EMAIL PROTECTED]>: >> >>> On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote: Hello, I'm using the Wifi-method described in http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf for all my known access points (which is just a copy of that I'm using daily and stable in my two FreeBSD based laptops); and I'm trying to bring up the eth0 with # ifup eth0 this works very unreliable; in (let's say) 8 of 10 cases it can't associate to the AP, even not after fresh re-boots and independently if the AP at my home works with WEP or in my office with WPA; >>> >>> I found that, for WEP networking, the only working way is to manually >>> configure the interface: >>> iwconfig eth0 key >>> iwconfig eth0 essid >>> udhcpc eth0 >>> >>> And even then, it's not guaranteed to work, or if it works, it won't for >>> long. >>> >>> HTH, >>> Xav >>> >>> >>> >>> ___ >>> 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 >> > > ___ > 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: [2008.9] Wifi very unreliable
Im also inclined to think its a hardware/driver problem and have nothing to do with wpa_supplicant or any other highlevel stuff. I fully understand if higher stuff is left to the community but i did expect the kernel and low level stuff to work a bit better than now when i bought the phone. It could ofcourse be just some phones thats broken and most works well because of some faulty batch. Does anyone know if work is happening on the kernel side of wifi or is it an orphan right now needing more people? //danielh 2008/9/30 <[EMAIL PROTECTED]>: > Hi all. > Now that you mention this, I think the problem is Hardware based. > I've bought an Asus Eee 901 :D, and now I have a means of comparison > in terms of WiFi reception. > My conclusion is that the Neo FR's wifi sucks. > Example1: > - my home AP has WPA; sitting 2 meters away from it, the FR show 50% > signal strength. Okay, you can say that's too close and they are > "shouting" at each other, causing signal corruption. Very well, I take > it 10 meters away, behind a couple of normal walls. The signal > strength drops all the way, right down to 5%, which is pretty > unusable. The Eee901 has 100% signal strength in the vicinity of the > AP, and behind those walls shows 30%. > Example2: > - at work, the Eee901 picks up 4 weak networks, the strongest one at > 35% strength and joins (no security) without problems. The FR picks up > only the stronger one at 8%, and it cannot join it. > > This has convinced me that either the wifi on the FR has serious > hardware problems, or the software is misguiding it. Anyway, it needs > serious attention. > Has anyone filed bugs on this wifi problem? > > Vasco. > > Citando Xavier Bestel <[EMAIL PROTECTED]>: > >> On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote: >>> Hello, >>> >>> I'm using the Wifi-method described in >>> >>> http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces >>> >>> i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf >>> for all my known access points (which is just a copy of that I'm using >>> daily and stable in my two FreeBSD based laptops); and I'm trying to bring >>> up the eth0 with >>> >>> # ifup eth0 >>> >>> this works very unreliable; in (let's say) 8 of 10 cases it can't >>> associate to the AP, even not after fresh re-boots and independently if >>> the AP at my home works with WEP or in my office with WPA; >> >> I found that, for WEP networking, the only working way is to manually >> configure the interface: >> iwconfig eth0 key >> iwconfig eth0 essid >> udhcpc eth0 >> >> And even then, it's not guaranteed to work, or if it works, it won't for >> long. >> >> HTH, >> Xav >> >> >> >> ___ >> 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 > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Tue, Sep 30, 2008 at 3:27 PM, <[EMAIL PROTECTED]> wrote: > Hi all. > Now that you mention this, I think the problem is Hardware based. > I've bought an Asus Eee 901 :D, and now I have a means of comparison > in terms of WiFi reception. > My conclusion is that the Neo FR's wifi sucks. > Example1: > - my home AP has WPA; sitting 2 meters away from it, the FR show 50% > signal strength. Okay, you can say that's too close and they are > "shouting" at each other, causing signal corruption. Very well, I take > it 10 meters away, behind a couple of normal walls. The signal > strength drops all the way, right down to 5%, which is pretty > unusable. The Eee901 has 100% signal strength in the vicinity of the > AP, and behind those walls shows 30%. > Example2: > - at work, the Eee901 picks up 4 weak networks, the strongest one at > 35% strength and joins (no security) without problems. The FR picks up > only the stronger one at 8%, and it cannot join it. > > This has convinced me that either the wifi on the FR has serious > hardware problems, or the software is misguiding it. Anyway, it needs > serious attention. > Has anyone filed bugs on this wifi problem? > > Vasco. > You're doing better than me. I was getting a 35% signal strength from my wifi router (Linksys RangePlus) at the same distance. My laptop showed the signal strength to be 'excellent'. Now that I think of it, I got better performance when I had set the FR down next to the router. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Matthias Apitz wrote:
> I'm trying to bring up the eth0 with
>
> # ifup eth0
>
> this works very unreliable; in (let's say) 8 of 10 cases it can't
> associate to the AP, even not after fresh re-boots and independently if
> the AP at my home works with WEP or in my office with WPA;
>
I found that with wpa_supplicant there was a problem with disconnecting
from an AP. The essid would apparantly not get cleared properly on the
card (although iwconfig would show it as cleared) and until you manually
cleared it, wpa_supplicant would just sit in a loop trying to connect
and getting authentication timeouts. You can see these message if you
run wpa_cli. I worked around it by adding a pre-up that clears the essid:
allow-hotplug eth0
iface eth0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
pre-up iwconfig eth0 essid off
iface default inet dhcp
iface home inet dhcp
This seems to work reliably for me except that I still have to ifdown
and ifup when I move to a different AP. So if manually connecting with
iwconfig works for you, you could try same workaround. Here's what my
wpa_supplicant.conf looks like:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
ssid="XXX"
key_mgmt=NONE
wep_key0=XX
wep_tx_keyidx=0
id_str="home"
}
network={
key_mgmt=NONE
}
Note that this is with Debian, not 2008.9 -- I'm not sure whether
Om2008.9 supports exactly the same /etc/network/interfaces syntax as Debian.
Cheers,
Alex
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
Hi all. Now that you mention this, I think the problem is Hardware based. I've bought an Asus Eee 901 :D, and now I have a means of comparison in terms of WiFi reception. My conclusion is that the Neo FR's wifi sucks. Example1: - my home AP has WPA; sitting 2 meters away from it, the FR show 50% signal strength. Okay, you can say that's too close and they are "shouting" at each other, causing signal corruption. Very well, I take it 10 meters away, behind a couple of normal walls. The signal strength drops all the way, right down to 5%, which is pretty unusable. The Eee901 has 100% signal strength in the vicinity of the AP, and behind those walls shows 30%. Example2: - at work, the Eee901 picks up 4 weak networks, the strongest one at 35% strength and joins (no security) without problems. The FR picks up only the stronger one at 8%, and it cannot join it. This has convinced me that either the wifi on the FR has serious hardware problems, or the software is misguiding it. Anyway, it needs serious attention. Has anyone filed bugs on this wifi problem? Vasco. Citando Xavier Bestel <[EMAIL PROTECTED]>: > On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote: >> Hello, >> >> I'm using the Wifi-method described in >> >> http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces >> >> i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf >> for all my known access points (which is just a copy of that I'm using >> daily and stable in my two FreeBSD based laptops); and I'm trying to bring >> up the eth0 with >> >> # ifup eth0 >> >> this works very unreliable; in (let's say) 8 of 10 cases it can't >> associate to the AP, even not after fresh re-boots and independently if >> the AP at my home works with WEP or in my office with WPA; > > I found that, for WEP networking, the only working way is to manually > configure the interface: > iwconfig eth0 key > iwconfig eth0 essid > udhcpc eth0 > > And even then, it's not guaranteed to work, or if it works, it won't for > long. > > HTH, > Xav > > > > ___ > 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: [2008.9] Wifi very unreliable
El día Tuesday, September 30, 2008 a las 11:28:18AM +0200, Xavier Bestel
escribió:
> On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote:
> > Hello,
> >
> > I'm using the Wifi-method described in
> >
> > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces
> >
> > i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf
> > for all my known access points (which is just a copy of that I'm using
> > daily and stable in my two FreeBSD based laptops); and I'm trying to bring
> > up the eth0 with
> >
> > # ifup eth0
> >
> > this works very unreliable; in (let's say) 8 of 10 cases it can't
> > associate to the AP, even not after fresh re-boots and independently if
> > the AP at my home works with WEP or in my office with WPA;
>
> I found that, for WEP networking, the only working way is to manually
> configure the interface:
> iwconfig eth0 key
> iwconfig eth0 essid
> udhcpc eth0
As I said, with WEP at home I have had it working today morning (sometimes)
with:
# cat /etc/network/interfaces
...
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
up route del default gw 192.168.0.200
down route add default gw 192.168.0.200
# cat /etc/wpa_supplicant/wpa_supplicant.conf
...
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="tarara"
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=
}
and then the eth0 just comes up (sometimes) with:
# ifup eth0
and DHCP IP and DNS from my AP;
there are some minor bugs in the two shell scripts
/etc/wpa_supplicant/*.sh which I've had to fix too (sed of busybox does not
know the flag --quiet);
matthias
--
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
A computer is like an air conditioner, it stops working when you open Windows
Una computadora es como aire acondicionado, deja de funcionar si abres Windows
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Tue, 2008-09-30 at 11:42 +0200, Matthias Apitz wrote:
> El día Tuesday, September 30, 2008 a las 11:28:18AM +0200, Xavier Bestel
> escribió:
>
> > On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote:
> > > Hello,
> > >
> > > I'm using the Wifi-method described in
> > >
> > > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces
> > >
> > > i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf
> > > for all my known access points (which is just a copy of that I'm using
> > > daily and stable in my two FreeBSD based laptops); and I'm trying to bring
> > > up the eth0 with
> > >
> > > # ifup eth0
> > >
> > > this works very unreliable; in (let's say) 8 of 10 cases it can't
> > > associate to the AP, even not after fresh re-boots and independently if
> > > the AP at my home works with WEP or in my office with WPA;
> >
> > I found that, for WEP networking, the only working way is to manually
> > configure the interface:
> > iwconfig eth0 key
> > iwconfig eth0 essid
> > udhcpc eth0
>
> As I said, with WEP at home I have had it working today morning (sometimes)
> with:
>
> # cat /etc/network/interfaces
> ...
> iface eth0 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
> up route del default gw 192.168.0.200
> down route add default gw 192.168.0.200
>
> # cat /etc/wpa_supplicant/wpa_supplicant.conf
> ...
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> network={
> ssid="tarara"
> scan_ssid=0
> key_mgmt=NONE
> wep_tx_keyidx=0
> wep_key0=
> }
>
> and then the eth0 just comes up (sometimes) with:
>
> # ifup eth0
>
> and DHCP IP and DNS from my AP;
>
> there are some minor bugs in the two shell scripts
> /etc/wpa_supplicant/*.sh which I've had to fix too (sed of busybox does not
> know the flag --quiet);
Look at 'dmesg'. When the wifi driver starts spewing messages about
failed connexions, in my experience the device is hosed.
Xav
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.9] Wifi very unreliable
On Tue, 2008-09-30 at 11:06 +0200, Matthias Apitz wrote: > Hello, > > I'm using the Wifi-method described in > > http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces > > i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf > for all my known access points (which is just a copy of that I'm using > daily and stable in my two FreeBSD based laptops); and I'm trying to bring > up the eth0 with > > # ifup eth0 > > this works very unreliable; in (let's say) 8 of 10 cases it can't > associate to the AP, even not after fresh re-boots and independently if > the AP at my home works with WEP or in my office with WPA; I found that, for WEP networking, the only working way is to manually configure the interface: iwconfig eth0 key iwconfig eth0 essid udhcpc eth0 And even then, it's not guaranteed to work, or if it works, it won't for long. HTH, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[2008.9] Wifi very unreliable
Hello, I'm using the Wifi-method described in http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf for all my known access points (which is just a copy of that I'm using daily and stable in my two FreeBSD based laptops); and I'm trying to bring up the eth0 with # ifup eth0 this works very unreliable; in (let's say) 8 of 10 cases it can't associate to the AP, even not after fresh re-boots and independently if the AP at my home works with WEP or in my office with WPA; what can I do? is someone willing to look into the debug output of the wpa_supplicant? or do I need somehow an update in the kernel drivers? I've installed as well lint-wifi; this does not even see the AP next door and to which I'm now after 2-3 tries connected too; strange, isn't it? there must be something broken in kernel land, I think; or should I file a bug track report? Thx for a helping hand matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
