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
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
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
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,
-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
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:
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
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:
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
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
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
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
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
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
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
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
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]
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
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
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
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
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
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
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
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
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
--
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
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
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
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 ;
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?
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
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
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
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
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
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
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
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
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
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
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
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
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%
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
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
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
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
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;
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
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
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
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
53 matches
Mail list logo
