Re: WiFi issue in Qtmoko v44 for Freerunner

[Radek Polak]

On Saturday 21 April 2012 03:16:23 Tiago Bortoletto Vaz wrote:

> It's not possible to connect to closed wireless networks in v44 because it
> seems to reset the encription settings every time it tries to authenticate.
> Anyone having the same issue out there? Any fix around? :)

Hi,
i think i noticed it too. It's probably related to rework of the wifi scan 
dialog. I will take a look at it.

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi issue in Qtmoko v44 for Freerunner

[Tiago Bortoletto Vaz]

On Sat, 21 Apr 2012 12:02:51 +0300, Timo Juhani Lindfors wrote
> Timo Juhani Lindfors  writes:
> > I personally use the following script to connect to WiFi. If you replace
> > ESSID and PASSWORD it might help you.
> 
> Oh and you also might want to replace "wlan" with "eth0" or whatever 
> you call your wifi interface.

Thanks Timo, I'm doing something similar while I don't get the fancy qt
interface working. I guess this regression wont be hard to fix once the
(almost) same code used to work well in previous versions. I'll try to find
some time for it.

Regards,

--
Tiago Bortoletto Vaz
http://tiagovaz.org
0xA504FECA - http://pgp.mit.edu


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi issue in Qtmoko v44 for Freerunner

[urodelo]

Hello.
Wifi isn't working on my fr  v44 too, same situation, closed wifi where  
before I could connect to.


urodelo


On Sat, 21 Apr 2012 05:16:23 +0200, Tiago Bortoletto Vaz  
 wrote:



Hi Radek, Freerunners,

It's not possible to connect to closed wireless networks in v44 because  
it
seems to reset the encription settings every time it tries to  
authenticate.

Anyone having the same issue out there? Any fix around? :)

thanks,

--
Tiago Bortoletto Vaz
http://tiagovaz.org
0xA504FECA - http://pgp.mit.edu



--
用斯斯！


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi issue in Qtmoko v44 for Freerunner

[Timo Juhani Lindfors]

Timo Juhani Lindfors  writes:
> I personally use the following script to connect to WiFi. If you replace
> ESSID and PASSWORD it might help you.

Oh and you also might want to replace "wlan" with "eth0" or whatever you
call your wifi interface.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi issue in Qtmoko v44 for Freerunner

[Timo Juhani Lindfors]

"Tiago Bortoletto Vaz"  writes:
> It's not possible to connect to closed wireless networks in v44 because it
> seems to reset the encription settings every time it tries to authenticate.
> Anyone having the same issue out there? Any fix around? :)

I personally use the following script to connect to WiFi. If you replace
ESSID and PASSWORD it might help you.


killall dhclient
killall wpa_supplicant
om wifi power 0
sleep 1
om wifi power 1
sleep 1
om wifi maxperf wlan 1
sleep 1
/sbin/wpa_supplicant -B -s -P /var/run/wpa_supplicant.wlan.pid -i wlan -D  wext 
-t -ddd -C /var/run/wpa_supplicant
sleep 4
wpa_cli -p /var/run/wpa_supplicant -i wlan add_network
wpa_cli -p /var/run/wpa_supplicant -i wlan set_network 0 ssid "\"ESSID\""
wpa_cli -p /var/run/wpa_supplicant -i wlan set_network 0 psk "\"PASSWORD\""
wpa_cli -p /var/run/wpa_supplicant -i wlan enable_network 0
sleep 8
dhclient -d wlan


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi-Tool (or GPRS-Tool modified)

[Esteban Monge]

def set_status(self, label):
status = os.system("ifconfig eth0")
if status == 0:
status = "WiFi Power On"
label.set_text(status)
label.modify_fg(gtk.STATE_NORMAL, gtk.gdk.color_parse("green"))

else:
status = "WiFi Power Off"
label.set_text(status)
label.modify_fg(gtk.STATE_NORMAL, gtk.gdk.color_parse("red"))

This part of the script check if WiFi is Power On or Power Off, maybe
prevents the bad use of the script, in my case work good.

-- 
http://nuevaeracr.blogspot.com
Linux user number 478378
Linux machine number 386687
Tec. Esteban Monge Marín
Tel: (506) 8379-3562

“No habrá manera de desarrollarnos y salir de
la pobreza mientras los pocos negocios
grandes de nuestro medio se entreguen a las
economías foráneas y nosotros nos
quedemos con solo negocios de pobre,
mientras en vez de ser propietarios de nuestro
propio país nos convirtamos en un ejército de
empleados del exterior”
José Figueres Ferrer, 1952.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi-Tool (or GPRS-Tool modified)

[Petr Vanek]

On Mon, 5 Oct 2009 14:09:19 -0600
Esteban Monge  (EM) wrote:

>Hello I  readed this page:
>http://wiki.openmoko.org/wiki/FSO_Resources
>
>You suggest use the command
>
>fsoraw -r WiFi

if you for example enable wifi via shr-settings and then use any script
that uses fso-raw by default, the resource will get released upon
the spripts exit... which imho is bad - it should read the status of the
resource before action and when leaving leave it in the state it was in,
or?

Petr


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi-Tool (or GPRS-Tool modified)

[Paul Fertser]

Esteban Monge  writes:
>     def wifi_on(self, button):
>         os.system("mdbus -s org.freesmartphone.odeviced 
> /org/freesmartphone/Device/PowerControl/WiFi
> org.freesmartphone.Resource.Enable")

Are you sure you know exactly what FSO resources concept is about and
have you seen FSO_Resources wikipage?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi-Tool (or GPRS-Tool modified)

[Paul Fertser]

Esteban Monge  writes:
> Hello I  readed this page:
> http://wiki.openmoko.org/wiki/FSO_Resources
>
> You suggest use the command
>
> fsoraw -r WiFi

For shell scripts, yes. For your own programs you can call
RequestResource and ReleaseResource directly.

HTH
-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi-Tool (or GPRS-Tool modified)

[Esteban Monge]

Hello I  readed this page:
http://wiki.openmoko.org/wiki/FSO_Resources

You suggest use the command

fsoraw -r WiFi

-- 
http://nuevaeracr.blogspot.com
Linux user number 478378
Linux machine number 386687
Tec. Esteban Monge Marín
Tel: (506) 8379-3562

“No habrá manera de desarrollarnos y salir de
la pobreza mientras los pocos negocios
grandes de nuestro medio se entreguen a las
economías foráneas y nosotros nos
quedemos con solo negocios de pobre,
mientras en vez de ser propietarios de nuestro
propio país nos convirtamos en un ejército de
empleados del exterior”
José Figueres Ferrer, 1952.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Paul Fertser]

Nicola Mfb  writes:
> On Fri, Sep 4, 2009 at 10:07 PM, Paul Fertser wrote:
>> Can you confirm it's a regression and if yes, in which version it did work
>> without issues?
>
> I cannot confirm, I always had problem in some ways.
> It may be only due the fact that as I developed nwa I stressed a lot
> wifi during time.

I see. Our main wifi-related goal currently is not to actually fix the
driver, it's rather to bandaid it to avoid most easily reproducible
races most of the time.

I do not consider races with rfkill at all currently, i can't see why
spend time on that since rfkill is redudant and useless in our case.

> Another hint is the wow interrupt, I noted it a lot of time, is it
> harmful?

Probably it means only that an unpowered module was powered, i don't
think that's something to worry about.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Nicola Mfb]

On Fri, Sep 4, 2009 at 11:59 PM, Nicola Mfb wrote:
> On Fri, Sep 4, 2009 at 10:07 PM, Paul Fertser wrote:
> [...]
[...]
>> Can you confirm it's a regression and if yes, in which version it did work
>> without issues?

I forgot to say an important thing: thanks for your effort!
Keep up the good work on the kernel, we really need it ;)

Nicola

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Nicola Mfb]

On Fri, Sep 4, 2009 at 10:07 PM, Paul Fertser wrote:
[...]
> Quite interesting indeed. Can you possibly provide a way to reproduce it
> without nwa using some bash or minimal python script?

Yes, I'll try with standard tools, anyway when nwa quits it remove
eth0 from the list of interfaces managed by wpa_supplicant via a dbus
call.
I do not know exactly what wpa_supplicant does in such case, and as it
happens only some times I just guess the driver goes in some race
condition state.

> Can you confirm it's a regression and if yes, in which version it did work
> without issues?

I cannot confirm, I always had problem in some ways.
It may be only due the fact that as I developed nwa I stressed a lot
wifi during time.

Another hint is the wow interrupt, I noted it a lot of time, is it harmful?

Regards

Nicola

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Paul Fertser]

Hi,

Thanks for the feedback.

On Fri, Sep 04, 2009 at 04:13:28PM +0200, Nicola Mfb wrote:
> > Nicola Mfb  writes:
> >> I built a3587e4ed77974adfb057af261aaeea4022018e8 and commented the HTC
> >> line suggested in your patch
> > andy-tracking HEAD, that's right revision.
... 
> rebooted and tryied with nwa, starting and quitting about 4/5 times resulted 
> in:
...
> [  743.62] Backtrace:
> [  743.62] [] (wmi_cmd_send+0x0/0xb4 [ar6000]) from
> [] (wmi_bssfilter_cmd+0x8c/0x98 [ar6000])
> [  743.62]  r7: r6:c6fbec20 r5: r4:c7ac8284
> [  743.62] [] (wmi_bssfilter_cmd+0x0/0x98 [ar6000]) from
> [] (ar6000_ioctl_siwscan+0x11c/0x148 [ar6000])

Quite interesting indeed. Can you possibly provide a way to reproduce it
without nwa using some bash or minimal python script?

Can you confirm it's a regression and if yes, in which version it did work
without issues?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Nicola Mfb]

On Fri, Sep 4, 2009 at 2:14 PM, Paul Fertser wrote:
> Nicola Mfb  writes:
>> I built a3587e4ed77974adfb057af261aaeea4022018e8 and commented the HTC
>> line suggested in your patch
>
> Oh no! We reverted Werner's patch and with that nothing should be
> commented, it should work as is. And yes, you're building
> andy-tracking HEAD, that's right revision.

Damn me! looking in the images directory and stucked in the old duscussion ;)
reflashed again and upgraded to be sure to use the last kernel:

opkg list_installed |grep "kernel ":
kernel - 2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5 -

rebooted and tryied with nwa, starting and quitting about 4/5 times resulted in:

[  692.365000] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1)
[  692.365000] eth0 (sdio_ar6000): not using net_device_ops yet
[  692.425000] AR6000 Reg Code = 0x4060
[  715.78] mmc1: card 0001 removed
[  715.82] ar6000_wow interrupt
[  715.985000] s3c2440-sdi s3c2440-sdi: powered down.
[  715.985000] s3c2440-sdi s3c2440-sdi: powered down.
[  719.815000] s3c2440-sdi s3c2440-sdi: host detect has no irq available
[  719.815000] mapped channel 0 to 0
[  719.955000] s3c2440-sdi s3c2440-sdi: powered down.
[  719.955000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).
[  719.955000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).
[  719.96] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).
[  719.965000] s3c2440-sdi s3c2440-sdi: initialisation done.
[  719.97] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).
[  719.98] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).
[  719.995000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).
[  720.005000] mmc1: queuing CIS tuple 0x01 length 3
[  720.065000] mmc1: queuing CIS tuple 0x1a length 5
[  720.085000] mmc1: queuing CIS tuple 0x1b length 8
[  720.085000] s3c2440-sdi s3c2440-sdi: running at 25000kHz
(requested: 25000kHz).
[  720.085000] s3c2440-sdi s3c2440-sdi: running at 25000kHz
(requested: 25000kHz).
[  720.095000] mmc1: queuing CIS tuple 0x80 length 1
[  720.095000] mmc1: queuing CIS tuple 0x81 length 1
[  720.095000] mmc1: queuing CIS tuple 0x82 length 1
[  720.095000] mmc1: new SDIO card at address 0001
[  721.14] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1)
[  721.16] eth0 (sdio_ar6000): not using net_device_ops yet
[  721.225000] AR6000 Reg Code = 0x4060
[  743.61] Unable to handle kernel NULL pointer dereference at
virtual address 002c
[  743.61] pgd = c6f0
[  743.615000] [002c] *pgd=36d3e031, *pte=, *ppte=
[  743.62] Internal error: Oops: 17 [#1] PREEMPT
[  743.62] Modules linked in: sco bnep ar6000
snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx_i2s snd_soc_s3c24xx
s3cmci btusb rfcomm ppp_generic slhc ohci_hcd ipv6 hidp snd_soc_wm8753
l2cap snd_soc_core bluetooth snd_pcm snd_timer snd_page_alloc g_ether
snd
[  743.62] CPU: 0Not tainted  (2.6.29-rc3 #1)
[  743.62] PC is at wmi_cmd_send+0x8c/0xb4 [ar6000]
[  743.62] LR is at wmi_cmd_send+0x54/0xb4 [ar6000]
[  743.62] pc : []lr : []psr: 8013
[  743.62] sp : c6de9d38  ip : c6de9d38  fp : c6de9d54
[  743.62] r10: c6d02000  r9 :   r8 : 
[  743.62] r7 :   r6 :   r5 : c6fbec20  r4 : 0009
[  743.62] r3 :   r2 :   r1 : c6fbec20  r0 : c7ac8282
[  743.62] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  743.62] Control: c000717f  Table: 36f0  DAC: 0015
[  743.62] Process wpa_supplicant (pid: 1300, stack limit = 0xc6de8268)
[  743.62] Stack: (0xc6de9d38 to 0xc6dea000)
[  743.62] 9d20:
c7ac8284 
[  743.62] 9d40: c6fbec20  c6de9d7c c6de9d58 bf14f114
bf14ccbc c0058cb4 
[  743.62] 9d60: c6de8000 c6ffa460   c6de9dbc
c6de9d80 bf145bdc bf14f098
[  743.62] 9d80: 0064 00cd 6013  c6d788e0
c0058b90 c6de9d98 c6de9d98
[  743.62] 9da0: c6de9e90 013c c02bd2d4 8b18 c6de9e24
c6de9dc0 c0292238 bf145ad0
[  743.62] 9dc0: 0001 c6de9e34 c6ffa000  c6de9e0c
  
[  743.62] 9de0:   c6de9e0c 8b18 c6de9e80
c08f9f50 c6de9e24 8b18
[  743.62] 9e00: c6de9e80 c08f9f50 bed4dbd8  c6de8000
 c6de9e5c c6de9e28
[  743.62] 9e20: c0291c28 c0291fbc bf145ac0 c6de9e38 c6de9e4c
8b18 c00630b8 
[  743.62] 9e40: 8b18 bed4dbd8 c6de9e80 c08f9f50 c6de9ed4
c6de9e60 c0220910 c0291b04
[  743.62] 9e60: 6013 c6de9f78 c6de9e9c c6de9e78 c00662f4
c0062c40 c6de9eb4 c76963b8
[  743.62] 9e80: 30687465    
  
[  743.62] 9ea0:  c7690610 c6de9ed4 c6ce6440 8b18
bed4dbd8 bed4dbd8 c0029fc4
[  743.62] 9ec0: c6de8000 bed4dbd8 c6de9ef4 c6de9ed8 c0210470
c0220274  c6ce6440
[  743.62] 9ee0: 

Re: Wifi driver stability improved -- wrong patch reverted

[William Kenworthy]

my mistake - looks like a meta-package ... :(

BillK



On Fri, 2009-09-04 at 21:29 +0800, William Kenworthy wrote:
> That link looks like its only 762 bytes - somethings wrong?
> 
> On Fri, 2009-09-04 at 16:21 +0400, Paul Fertser wrote:
> > Nicola Mfb  writes:
> > >> I remember you were testing the fsoraw method and indeed proved that it
> > >> doesn't work properly with the latest kernel. After some discussion we
> > >> reverted the offending patch and now the latest SHR kernel should provide
> > >> the same level of stability as .28.
> > >>
> > >> Please try again and report the results.
> > >
> > > I'm not sure but latest SHR kernel seems to be
> > > 2d158aae9d8d36f575504f59884ed8e80802efe2, and that does not include
> > > the wifi revert.
> > 
> > http://build.shr-project.org/shr-unstable/ipk/om-gta02/kernel-2.6.29-rc3_2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5_om-gta02.ipk
> > 
> > opkg update && opkg upgrade should deliver it automatically.
> > 
-- 
William Kenworthy 
Home in Perth!


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[William Kenworthy]

That link looks like its only 762 bytes - somethings wrong?

On Fri, 2009-09-04 at 16:21 +0400, Paul Fertser wrote:
> Nicola Mfb  writes:
> >> I remember you were testing the fsoraw method and indeed proved that it
> >> doesn't work properly with the latest kernel. After some discussion we
> >> reverted the offending patch and now the latest SHR kernel should provide
> >> the same level of stability as .28.
> >>
> >> Please try again and report the results.
> >
> > I'm not sure but latest SHR kernel seems to be
> > 2d158aae9d8d36f575504f59884ed8e80802efe2, and that does not include
> > the wifi revert.
> 
> http://build.shr-project.org/shr-unstable/ipk/om-gta02/kernel-2.6.29-rc3_2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5_om-gta02.ipk
> 
> opkg update && opkg upgrade should deliver it automatically.
> 
-- 
William Kenworthy 
Home in Perth!


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Paul Fertser]

Nicola Mfb  writes:
>> I remember you were testing the fsoraw method and indeed proved that it
>> doesn't work properly with the latest kernel. After some discussion we
>> reverted the offending patch and now the latest SHR kernel should provide
>> the same level of stability as .28.
>>
>> Please try again and report the results.
>
> I'm not sure but latest SHR kernel seems to be
> 2d158aae9d8d36f575504f59884ed8e80802efe2, and that does not include
> the wifi revert.

http://build.shr-project.org/shr-unstable/ipk/om-gta02/kernel-2.6.29-rc3_2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5_om-gta02.ipk

opkg update && opkg upgrade should deliver it automatically.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Paul Fertser]

Nicola Mfb  writes:
> I built a3587e4ed77974adfb057af261aaeea4022018e8 and commented the HTC
> line suggested in your patch

Oh no! We reverted Werner's patch and with that nothing should be
commented, it should work as is. And yes, you're building
andy-tracking HEAD, that's right revision.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Vinzenz Hersche]

Am Freitag, 4. September 2009 13.08:05 schrieb Paul Fertser:
> Hi,
> 
> I remember you were testing the fsoraw method and indeed proved that it
> doesn't work properly with the latest kernel. After some discussion we
> reverted the offending patch and now the latest SHR kernel should provide
> the same level of stability as .28.
> 
> Please try again and report the results.
> 
hello paul,
i saw the commit, tried it, and it's realy great!
since this i've ben able to connect every wlan :)

thx!

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[arne anka]

> I remember you were testing the fsoraw method and indeed proved that it
> doesn't work properly with the latest kernel. After some discussion we
> reverted the offending patch and now the latest SHR kernel should provide
> the same level of stability as .28.
>
> Please try again and report the results.


sounds great!
but i am on debian and thus have probably to wait for the pkg-fso guys to  
create a new package, because i am not sure how (and if) the kernel differ  
between debian and shr.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi driver stability improved -- wrong patch reverted

[Nicola Mfb]

On Fri, Sep 4, 2009 at 1:08 PM, Paul Fertser wrote:
> Hi,
>
> I remember you were testing the fsoraw method and indeed proved that it
> doesn't work properly with the latest kernel. After some discussion we
> reverted the offending patch and now the latest SHR kernel should provide
> the same level of stability as .28.
>
> Please try again and report the results.

I'm not sure but latest SHR kernel seems to be
2d158aae9d8d36f575504f59884ed8e80802efe2, and that does not include
the wifi revert.

I built a3587e4ed77974adfb057af261aaeea4022018e8 and commented the HTC
line suggested in your patch, and my freerunner crashed, but anyway I
played too much with my oe tree and I'm quite sure I was wrong
somewhere (as the HTC line is on a different position than your patch
suggests). I'm going to rebuild again and report.

Regards

 Nicola

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi problems, WPA/WEP differences

[Fox Mulder]

Same here. 24 worked stable but 29 doesn't work at all. Connection to AP
seems established but no data transfer between freerunner and AP with
new kernels.

Johny Tenfinger wrote:
> My AP worked well with .24 kernel. With .28 and .29 it doesn't (I've
> connected once for about month)
> 
> 2009/4/5, Paul Fertser :
>> Cameron Frazier  writes:
>>> On Sat, 2009-04-04 at 16:25 +0200, Davide Scaini wrote:
 ...
 i use a wep static ip network and a dhcp  wpa one, i have some
 interfaces files that i switch between.
 ...
>>> I can get a DHCP WEP network to connect fine (work), but at home (DHCP
>>> WPA) I get nothing.  You mention that you have different interface
>>> files, coul dyou describe the differences between them.
>> I've had successful connections with open, WEP and WPA networks. And i've
>> seen an AP i couldn't connect at all too. It looks like FR's wifi is
>> incompatible with some APs, no matter if encryption is used or
>> not. See http://docs.openmoko.org/trac/ticket//1250 for example.
>>
>> To sum up: FR's wifi has 2 kinds of known problems: incompatibility
>> with particular APs and instability of the internal firmware.
>>
>> Using an old (pre-.28) kernel is not recommended due to stability
>> issues. Also i think Werner is still going to finish his daemon to
>> promptly power-cycle the wifi module on internal firmware crash; that
>> can improve stability somewhat.
>>
>> I wouldn't hope these compatibility issues will ever be fixed, so my
>> advice is: trade your AP for the one FR can work with.
>>
>> --
>> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
>> mailto:fercer...@gmail.com
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
> 
> ___
> 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: Wifi problems, WPA/WEP differences (was: Re: [SHR] from debian to shr ; -))

[Dylan Semler]

On Sun, Apr 5, 2009 at 4:13 AM, Johny Tenfinger  wrote:

> My AP worked well with .24 kernel. With .28 and .29 it doesn't (I've
> connected once for about month)
>
>
I'm in this boat as well

Dylan
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi problems, WPA/WEP differences (was: Re: [SHR] from debian to shr ; -))

[Johny Tenfinger]

My AP worked well with .24 kernel. With .28 and .29 it doesn't (I've
connected once for about month)

2009/4/5, Paul Fertser :
> Cameron Frazier  writes:
>> On Sat, 2009-04-04 at 16:25 +0200, Davide Scaini wrote:
>>> ...
>>> i use a wep static ip network and a dhcp  wpa one, i have some
>>> interfaces files that i switch between.
>>> ...
>>
>> I can get a DHCP WEP network to connect fine (work), but at home (DHCP
>> WPA) I get nothing.  You mention that you have different interface
>> files, coul dyou describe the differences between them.
>
> I've had successful connections with open, WEP and WPA networks. And i've
> seen an AP i couldn't connect at all too. It looks like FR's wifi is
> incompatible with some APs, no matter if encryption is used or
> not. See http://docs.openmoko.org/trac/ticket//1250 for example.
>
> To sum up: FR's wifi has 2 kinds of known problems: incompatibility
> with particular APs and instability of the internal firmware.
>
> Using an old (pre-.28) kernel is not recommended due to stability
> issues. Also i think Werner is still going to finish his daemon to
> promptly power-cycle the wifi module on internal firmware crash; that
> can improve stability somewhat.
>
> I wouldn't hope these compatibility issues will ever be fixed, so my
> advice is: trade your AP for the one FR can work with.
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fercer...@gmail.com
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi NOT work on fso-image

[David Reyes Samblas Martinez]

please search the list for wifi and fso milestone5 and you'll find the solution.
If your are to lazy for that please follow this link
http://n2.nabble.com/-FSO-milestone-5--No-wifi---td2333773ef1958.html#a2333773

2009/2/24 Daniel.Li :
> Dear All,
> I just downloaded below combination from
> http://downloads.freesmartphone.org/fso-stable/milestone5/om-gta02/
>
> fso-image-om-gta02.jffs2 + uImage-om-gta02-latest.bin
>
> So I login SSH thought USB and wanna try wifi, but get
>
> r...@om-gta02:~# iwlist eth0 scan
> eth0      Interface doesn't support scanning.
>
>
> I have noticed that wifi is working under command IF, see
> http://wiki.openmoko.org/wiki/Distributions
>
>
> How can I fix the problem? Thanks.
>
> --
> Daniel.Li 
> PALFocus (http://palfocus.oicp.net)
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>



-- 
David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora, GP2X the Wiz, Letux 400, Arduino
Hey, watch out!!! There's a linux in your pocket!!!

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi - wep or wpa enabled

[ant]

On Friday 19 December 2008 05:58:06 Rodney Myers wrote:
> Default install.
>
> Does the wifi work only with wpa? or does it also work with wep?
>
> My internal wifi is wep enabled only, and  I cannot get the phone to
> recognize the key.

Way back when I first got my phone, on the factory install, I managed to get 
it to talk WEP (using iwconfig etc at the command line). It was a bit flaky - 
eg you had to set things in a certain order and sometimes you had to wait a 
couple of minutes if you put the key in wrong. So /theoretically/ it can be 
made to work. Having said that, I've not got it to work on 2008.x or FSO 
recently (not even with wpa_supplicant) , and have more or less given up; if 
I'm out of the house/office wifi ain't gonna be helpful to me, and in the 
house/office I'm never >10ft away from a running linux box with USB.

There's still a few of us about stuck with WEP - yes I know it's breakable but 
on the other hand getting WPA working means me buying a) new laptop b) new 
wireless router c) new wireless bridge.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi - wep or wpa enabled

[Xavier Bestel]

Hi Rodney,

On Thu, 2008-12-18 at 21:58 -0800, Rodney Myers wrote:
> Default install.
> 
> Does the wifi work only with wpa? or does it also work with wep?
> 
> My internal wifi is wep enabled only, and  I cannot get the phone to  
> recognize the key.

In my experience none of the GUI tools work with WEP, but using a
terminal you can manage to make the FR sort-of work, i.e. it sometimes
connects to a WEP network for a short while.
Apparently with latest kernels this is fixed (the driver side, not the
UI side), I've had better experience with Andy's tracking kernel.

Xav



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi using GUI in 2008.9

[arne anka]

> My accesspoint is configured in wpa_supplicant, but the gui keeps asking  
> me
> for the key. Should I just not fill it in then?

dunno. never used any gui for wlan on the fr.
but i'd expect any gui to checl with wpa_supplicant.conf first -- what  
your gui obviously not does.
maybe grepping either in your home directory or in /etc (since 2008.9  
probably lets run you the fr as root) for the name of your ap might reveal  
a file which you could monitor?
but soem of these password helpers use to store passwords after successful  
login only, so you're probaly forced to type the correct phrase.
you could, though, put the phrase in a file, scp it to the fra nd try if  
c&p will work.

last idea: bug the developers of the gui.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi using GUI in 2008.9

[Peter Nijs]

On Sunday 07 December 2008 12:17:19 arne anka wrote:
> > Isn't there a way to preload the neo with the key via ssh in a config
> > file?
>
> /etc/wpa_supplicant/wpa_supplicant.conf

My accesspoint is configured in wpa_supplicant, but the gui keeps asking me 
for the key. Should I just not fill it in then?

depeje

>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community




signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi using GUI in 2008.9

[arne anka]

> Isn't there a way to preload the neo with the key via ssh in a config  
> file?

/etc/wpa_supplicant/wpa_supplicant.conf

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi "shelf gadget"

[pike]

Hi

thanks for the answer.

 > You probably want to be
> looking at the Settings program to see what happens when wifi is 
> switched on/off there (as that's actually switching the wifi chip on or 
> off).

Aha. Indeed, going to Settings/WIFI is the only
way to make the icon appear that I know sofar.

I'm confused why this is not mentioned anywhere -
on my FR, not even MOFI will do anything before
I 'wake up the wifi chip' (by going to
Settings/WIFI).

It seems as if other users just always have their
WIFI on ? This comment [1] seems to suggest the same.
Not here, it's off by default.


[1] 
http://wiki.openmoko.org/wiki/Talk:Neo_FreeRunner_Wifi#disabling_wifi_on_startup


strange,
*-pike

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi "shelf gadget"

[Michael Sheldon]

If I remember correctly the gadget is always there (just not visible), 
it gets reports from the wifiget application and only displays an icon 
when there's signal strength to report. It doesn't do anything to switch 
on/off the wifi it just constantly monitors it. You probably want to be 
looking at the Settings program to see what happens when wifi is 
switched on/off there (as that's actually switching the wifi chip on or 
off).

  Cheers,
   Mike.

pike wrote:
> Hi
> 
> what exactly is it that makes the "wifi icon"
> show up in the "shelf gadgets" ?
> 
> whatever I try, wifi won't seem to work
> if the icon is not showing.
> 
> /etc/init.d/networking restart ;doesn't help
> ifdown eth0; ifup eth0; doesn't help
> udhcpc; doesn't help
> 
> but the latter two options have success
> when the icon is showing (which may be caused
> by something else that's being changed by the
> application that also shows the icon, ofcourse).
> 
> in any case, when I ever get to write a
> script that works properly, i want to
> show the icon, as well :-) how would I do that ?
> 
> 
> curious,
> *-pike
> 
> 
> 
> 
> 
> ___
> 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: WIFI Connector Application

[Sarton O'Brien]

On Friday 26 September 2008 19:18:43 Matthias Apitz wrote:
> I've typed in the key in the FR again and again but it always said
> after some time 'ERROR Unable to join network'

Yeah, it looks like there is quite a bit of separation between all the 
different facilities.

The 'Settings->Wifi' GUI sort of works. If you select a network and enter a 
key (I've only tried WPA-PSK-TKIP), switch to a terminal, wait for the 
wireless indicator to appear and then issue 'udhcpc eth0', it all works.

The error has always appeared for me but the facility has still worked. Better 
yet, the latest testing update seems to allow the wireless indicator to 
disappear when you select wireless off.

This is with no wpa_supplicant.conf.

Manually launching wpa_supplicant is trivial for debugging, just bump up the 
verbosity and omit the '-B'.

I get the impression that a lot of the facilities haven't yet been configured 
to utilise any one particular network management scheme ... heard of 
resolvconf? ;)

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[Matthias Apitz]

El día Thursday, September 25, 2008 a las 08:02:18PM +0100, Al Johnson escribió:

> > I think the work that wpa_supplicant daemon does is only to control the
> > association to the AP and bringing up the interface; then in FreeBSD
> > a devd (device daemon) lets you describe what to do else, for example
> > launch a script when IF_UP; in this script you may, based on the MAC of
> > the AP, do whatever is needed: ifconfig static IP or DHCP or 
> >
> > it is similiar to what I have described here for the cdce0 (USB) interface:
> >
> > http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD
> >
> > a logic like that must exist in Debian too, I'm wrong?
> > and this is not much scripting work, or?
> 
> Exactly. The logic exists in debian. wpa_supplicant associates with the 
> access 
> point then some scripts apply the configuration you set 
> in /etc/network/interfaces that matches the AP it associated with. 
> Unfortunately in 2007.2 the bit that applies the settings is missing. For 
> someone who knows their way around the inner workings of the debian system it 
> would probably be easy to fix, but I don't. Since ASU was moving to use 
> connman instead of the debian method of network management I didn't see the 
> benefit in digging deeper at the time. 

Well, today morning I started investigating the Wifi of the FR gadget:

I configured the MAC addr of the eth0 of FR into my AP; 

I enabled the Wifi in the settings and FR saw my home SSID and asked for
the key; this AP at home is WEP protected and the 'password' (which I
normaly use in my laptop) is something like this wpa_supplicant entry:

 network={
 ssid="tarara"
 scan_ssid=1
 key_mgmt=NONE
 wep_tx_keyidx=0
 wep_key0=42FEEDDEAFBABEDEAFBEEFAA55
 }

I've typed in the key in the FR again and again but it always said
after some time 'ERROR Unable to join network'

then I SSH'ed into the FR and configured by hand:

# cat /etc/network/interfaces:
...
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# cat /etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="tarara"
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=42FEEDDEAFBABEDEAFBEEFAA55
}

and restarted the eth0 interface with:

# ifdown eth0 && ifup eth0

this produced the following output:

sed: unrecognized option `--quiet'
BusyBox v1.9.1 (2008-09-04 08:23:57 CST) multi-call binary

Usage: sed [-efinr] pattern [files...]

WPA: Terminating
sed: unrecognized option `--quiet'
BusyBox v1.9.1 (2008-09-04 08:23:57 CST) multi-call binary

Usage: sed [-efinr] pattern [files...]

WPA: Configuring Interface
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending select for 192.168.2.100...
Lease of 192.168.2.100 obtained, lease time 86400
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
adding dns 192.168.2.1

the network came up fin, including DNS:

# ping www.muc.de
PING www.muc.de (193.149.48.10): 56 data bytes
64 bytes from 193.149.48.10: seq=0 ttl=246 time=96.697 ms
64 bytes from 193.149.48.10: seq=1 ttl=246 time=114.740 ms
64 bytes from 193.149.48.10: seq=2 ttl=246 time=232.842 ms
64 bytes from 193.149.48.10: seq=3 ttl=246 time=154.134 ms
64 bytes from 193.149.48.10: seq=4 ttl=246 time=377.435 ms
64 bytes from 193.149.48.10: seq=5 ttl=246 time=88.150 ms

the routing looks a bit broken: note there are two default gateways:

# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
193.149.48.10   192.168.2.1 255.255.255.255 UGH   0 0  0 eth0
192.168.2.0 0.0.0.0 255.255.255.0   U 0 0  0 eth0
192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0 usb0
0.0.0.0 192.168.2.1 0.0.0.0 UG0 0  0 eth0
0.0.0.0 192.168.0.200   0.0.0.0 UG0 0  0 usb0

it would be nice to create some icon in the Om2008.9 desktop to launch
this "ifdown eth0 && ifup eth0", but I already learned that this is
another complex storry and at the moment I can't compile the eet library
for modifying the desktop at all; so I have to live with the command on
the sheel (which is not a big thing);

in my office the AP runs WPA-PSK and it seems that it is not associating
at all; the entry in /etc/wpa_supplicant/wpa_supplicant.conf reads:

network={
ssid="santaclara"
key_mgmt=WPA-PSK
psk="XXX"
}

again, it is the same as I use in my laptop; and I have no idea why it
does not associate; can I launch somehow the wpa_supplicant in FR in
debug mode? or I will enable the debugging in the AP and have a look

Re: WIFI Connector Application

[Arigead]

Thanks to everybody who relied to this thread you have given my much 
food for thought.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[William Kenworthy]

On Thu, 2008-09-25 at 15:16 +0100, Arigead wrote:
> Hello all,
> I'm looking for an application which if it exists great and if it 
> don't exist I'll maybe try and implement it in C, if what I'm thinking 
> is even possible. I've not done too much investigating into Wifi as I 
> believe that it has its issues on the FR.
> 
At the time I installed dd-wrt on my AP, there was a script that did
exactly this.  Looked for local known/unknown networks and picked the
best one to connect to - target was an environment (appartment block)
that had a number of unsecured AP's that continually changed.  The AP
just auto-connected to the one it thought best.

Moral issues aside, that looks like the way to do it.  A quick look at
the dd-wrt site doesnt show it now, but some searching should show it.

Also noticed they have a new HAL that can do Atheros WiSOC - not sure if
that includes the AR-6000.

BillK




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[Al Johnson]

On Thursday 25 September 2008, Matthias Apitz wrote:
> El día Thursday, September 25, 2008 a las 03:50:21PM +0100, Al Johnson 
escribió:
> > On Thursday 25 September 2008, Matthias Apitz wrote:
> > > El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead
> >
> > escribió:
> > > > Hello all,
> > > > I'm looking for an application which if it exists great and if it
> > > > don't exist I'll maybe try and implement it in C, if what I'm
> > > > thinking is even possible. I've not done too much investigating into
> > > > Wifi as I believe that it has its issues on the FR.
> > >
> > >   ...
> > >
> > > Isn't wpa_supplicant doing exactly this (it does for me on my normal
> > > laptop) having /etc/wpa_supplicant.conf as the database for all your
> > > known Wifi networks?
> >
> > It would do if all the debian network scripts are in place. Last time I
> > tried (some time ago now) wpa_supplican would connect, but the scripts
> > that are supposed to run on connection to sort out IP, DNS etc. were
> > missing.
>
> I think the work that wpa_supplicant daemon does is only to control the
> association to the AP and bringing up the interface; then in FreeBSD
> a devd (device daemon) lets you describe what to do else, for example
> launch a script when IF_UP; in this script you may, based on the MAC of
> the AP, do whatever is needed: ifconfig static IP or DHCP or 
>
> it is similiar to what I have described here for the cdce0 (USB) interface:
>
> http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD
>
> a logic like that must exist in Debian too, I'm wrong?
> and this is not much scripting work, or?

Exactly. The logic exists in debian. wpa_supplicant associates with the access 
point then some scripts apply the configuration you set 
in /etc/network/interfaces that matches the AP it associated with. 
Unfortunately in 2007.2 the bit that applies the settings is missing. For 
someone who knows their way around the inner workings of the debian system it 
would probably be easy to fix, but I don't. Since ASU was moving to use 
connman instead of the debian method of network management I didn't see the 
benefit in digging deeper at the time. 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[Minh Ha Duong]

>launch a script when IF_UP; in this script you may, based on the MAC of
>the AP, do whatever is needed: ifconfig static IP or DHCP or 
>a logic like that must exist in Debian too, I'm wrong?
>and this is not much scripting work, or?

Yes, in Debian here is how I do it:

http://minh69.blogspot.com/2008/04/setting-up-debian-etch-to-automatically.html

Minh

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[Matthias Apitz]

El día Thursday, September 25, 2008 a las 03:50:21PM +0100, Al Johnson escribió:

> On Thursday 25 September 2008, Matthias Apitz wrote:
> > El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead 
> escribió:
> > > Hello all,
> > > I'm looking for an application which if it exists great and if it
> > > don't exist I'll maybe try and implement it in C, if what I'm thinking
> > > is even possible. I've not done too much investigating into Wifi as I
> > > believe that it has its issues on the FR.
> >
> > ...
> >
> > Isn't wpa_supplicant doing exactly this (it does for me on my normal
> > laptop) having /etc/wpa_supplicant.conf as the database for all your
> > known Wifi networks?
> 
> It would do if all the debian network scripts are in place. Last time I tried 
> (some time ago now) wpa_supplican would connect, but the scripts that are 
> supposed to run on connection to sort out IP, DNS etc. were missing.

I think the work that wpa_supplicant daemon does is only to control the
association to the AP and bringing up the interface; then in FreeBSD
a devd (device daemon) lets you describe what to do else, for example
launch a script when IF_UP; in this script you may, based on the MAC of
the AP, do whatever is needed: ifconfig static IP or DHCP or 

it is similiar to what I have described here for the cdce0 (USB) interface:

http://wiki.openmoko.org/wiki/Usb_networking#FreeBSD

a logic like that must exist in Debian too, I'm wrong?
and this is not much scripting work, or?

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: WIFI Connector Application

[Al Johnson]

On Thursday 25 September 2008, Matthias Apitz wrote:
> El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead 
escribió:
> > Hello all,
> > I'm looking for an application which if it exists great and if it
> > don't exist I'll maybe try and implement it in C, if what I'm thinking
> > is even possible. I've not done too much investigating into Wifi as I
> > believe that it has its issues on the FR.
>
>   ...
>
> Isn't wpa_supplicant doing exactly this (it does for me on my normal
> laptop) having /etc/wpa_supplicant.conf as the database for all your
> known Wifi networks?

It would do if all the debian network scripts are in place. Last time I tried 
(some time ago now) wpa_supplican would connect, but the scripts that are 
supposed to run on connection to sort out IP, DNS etc. were missing.

2008.8/9 appears to be using connman which is supposed to do a similar job to 
NetworkManager. 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI Connector Application

[Matthias Apitz]

El día Thursday, September 25, 2008 a las 03:16:43PM +0100, Arigead escribió:

> Hello all,
> I'm looking for an application which if it exists great and if it 
> don't exist I'll maybe try and implement it in C, if what I'm thinking 
> is even possible. I've not done too much investigating into Wifi as I 
> believe that it has its issues on the FR.
...

Isn't wpa_supplicant doing exactly this (it does for me on my normal
laptop) having /etc/wpa_supplicant.conf as the database for all your
known Wifi networks?

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: WIFI Connector Application

[Christ van Willegen]

Hello,

On Thu, Sep 25, 2008 at 4:16 PM, Arigead <[EMAIL PROTECTED]> wrote:
> I've not tagged this email [2008.09] or anything. I'm using 2008.09 but
> I'll use this on any distro if it exists and if it has to be written I
> don't want to write it for a specific Distro.

I think that at the moment the Mofi application comes closest to what
you describe here...

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Xavier Bestel]

On Fri, 2008-09-12 at 00:18 +1000, Alex (Maxious) Sadleir wrote:
> The solution is absurdly simple.
> Use udhcpc not dhclient. Both are installed on 2008.8, only udhcpc
> does the right thing.

So .. it works, thanks, but as noted by Tore it works only once after a
reboot. Even letting the FR suspend causes the wifi to fail.

I see there are some open bugs about wifi in the bug tracker. I think
I'll let my FR sleep for a few weeks, waiting for the bugs to be
resolved.

Thanks,
Xav



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Marco Trevisan (Treviño)]

> Hi
> 
> If you manage to get a DHCP reply it means that the WIFI connection is 
> OK. But my experience is that WIFI can only connect once. So to test out 
> the setup I would reboot. Do the iwconfig then do the ifconfig with a 
> know address and then see if you can ping.
> 
> Is anyone else have problem to connect WIFI to different access points 
> in one session (I had the same problem when I tried the Debian 
> distribution, but I assume they have the same wifi driver)

Yes, I do.
BTW in the kernel ml there was the idea of puttin the wifi driver in a 
module, so it will be possible to reload it and maybe to workaround this 
issue.

-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Xavier Bestel]

On Fri, 2008-09-12 at 00:18 +1000, Alex (Maxious) Sadleir wrote:
> The solution is absurdly simple.
> Use udhcpc not dhclient. Both are installed on 2008.8, only udhcpc
> does the right thing.

Thanks, I'll try when I'm back home (not today).

Xav




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Olivier Berger]

Christian Weßel <[EMAIL PROTECTED]> writes:

> Am Donnerstag, den 11.09.2008, 15:51 +0200 schrieb Xavier Bestel:
>> Ok, I'll try that. Or maybe some rmmod+modprobe first.
>> 
>
> Please report your results.

Preferably on the support list ;-)

Please, people, help triage message to appropriate lists.

Regards,
-- 
Olivier BERGER 
(OpenPGP: 1024D/B4C5F37F)
http://www.olivierberger.com/weblog/

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[William Kenworthy]

Does "iwconfig power on" then "iwconfig power off" help?

(turns powersaving on then off - somewhat counter-intuitive :)

BillK

On Thu, 2008-09-11 at 15:51 +0200, Xavier Bestel wrote:
> On Thu, 2008-09-11 at 15:39 +0200, Tore Martin Hagen wrote:
> > Hi
> > 
> > If you manage to get a DHCP reply it means that the WIFI connection is 
> > OK. But my experience is that WIFI can only connect once. So to test out 
> > the setup I would reboot. Do the iwconfig then do the ifconfig with a 
> > know address and then see if you can ping.
> 
> Now that's impractical, seeing how long the boot time is :(
> Ok, I'll try that. Or maybe some rmmod+modprobe first.
> 
> Thanks,
>   Xav
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
-- 
William Kenworthy <[EMAIL PROTECTED]>
Home in Perth!

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Alex (Maxious) Sadleir]

The solution is absurdly simple.
Use udhcpc not dhclient. Both are installed on 2008.8, only udhcpc does the
right thing.

For example...
Dhclient:
[EMAIL PROTECTED]:~# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

can't create /var/lib/dhcp/dhclient.leases: No such file or directory
Listening on LPF/eth0/00:12:cf:8e:f0:0e
Sending on   LPF/eth0/00:12:cf:8e:f0:0e
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.0.1.100
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.0.1.100
DHCPDECLINE on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6

udhcpc:
[EMAIL PROTECTED]:~# udhcpc  eth0
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending select for 10.0.1.214...
Lease of 10.0.1.214 obtained, lease time 4294967295
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
adding dns 10.0.1.100

Much better result with the latter :)

On Thu, Sep 11, 2008 at 5:52 PM, Xavier Bestel <[EMAIL PROTECTED]>wrote:

> Hi,
>
> I have a FR whith 2008.8 + latest updates, and I can't connect to any
> wifi network with the GUI. The "settings" page shows correctly the list
> of available APs, when I click on one it asks for a password, and that's
> all.
>
> At home, I have a WEP network (which is working very well), and I could
> try connecting with the commandline. An iwlist scan shows the APs, then
> iwconfig essid and key connect to the AP, but that's all.
> When I then run "dhclient eth0", it goes into an infinite loop where it
> receives an OFFER, then does a DECLINE.
>
> Here is the log seen from the server side (dnsmasq):
>
> Sep 10 23:37:17 awak dnsmasq[14577]: DHCPREQUEST(ath0) 
> 192.168.4.17800:19:7d:87:60:4e
> Sep 10 23:37:17 awak dnsmasq[14577]: DHCPACK(ath0) 
> 192.168.4.17800:19:7d:87:60:4e
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPDISCOVER(ath0) 00:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPOFFER(ath0) 
> 192.168.4.17900:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPDISCOVER(ath0) 00:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPOFFER(ath0) 
> 192.168.4.17900:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPREQUEST(ath0) 
> 192.168.4.17900:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPACK(ath0) 
> 192.168.4.17900:12:cf:8e:fe:59
> Sep 10 23:37:50 awak dnsmasq[14577]: DHCPDECLINE(ath0) 
> 192.168.4.17900:12:cf:8e:fe:59
> Sep 10 23:37:53 awak dnsmasq[14577]: DHCPDISCOVER(ath0) 00:12:cf:8e:fe:59
> Sep 10 23:37:53 awak dnsmasq[14577]: DHCPOFFER(ath0) 
> 192.168.4.18000:12:cf:8e:fe:59
> Sep 10 23:37:53 awak dnsmasq[14577]: DHCPREQUEST(ath0) 
> 192.168.4.18000:12:cf:8e:fe:59
> Sep 10 23:37:53 awak dnsmasq[14577]: DHCPACK(ath0) 
> 192.168.4.18000:12:cf:8e:fe:59
> Sep 10 23:37:53 awak dnsmasq[14577]: DHCPDECLINE(ath0) 
> 192.168.4.18000:12:cf:8e:fe:59
> Sep 10 23:37:56 awak dnsmasq[14577]: DHCPDISCOVER(ath0) 00:12:cf:8e:fe:59
> etc.
>
> dhclient on the FR shows the same kind of thing.
>
>
> Any hint ?
>
> Thanks,
>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: WiFi doesn't work

[Christian Weßel]

Am Donnerstag, den 11.09.2008, 15:51 +0200 schrieb Xavier Bestel:
> Ok, I'll try that. Or maybe some rmmod+modprobe first.
> 

Please report your results.
-- 

mfg/br, christian

Flurstraße 14
29640 Schneverdingen
Germany

E-Mail: [EMAIL PROTECTED]
Telefon: +49 5193 97 14 95
Mobile:  +49 171 357 59 57
http://wesselch.homelinux.org


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Tore Martin Hagen]

> Now that's impractical, seeing how long the boot time is :(
> Ok, I'll try that. Or maybe some rmmod+modprobe first.
>   
The problem is that it is not a module.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Xavier Bestel]

On Thu, 2008-09-11 at 15:39 +0200, Tore Martin Hagen wrote:
> Hi
> 
> If you manage to get a DHCP reply it means that the WIFI connection is 
> OK. But my experience is that WIFI can only connect once. So to test out 
> the setup I would reboot. Do the iwconfig then do the ifconfig with a 
> know address and then see if you can ping.

Now that's impractical, seeing how long the boot time is :(
Ok, I'll try that. Or maybe some rmmod+modprobe first.

Thanks,
Xav



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Tore Martin Hagen]

Hi

If you manage to get a DHCP reply it means that the WIFI connection is 
OK. But my experience is that WIFI can only connect once. So to test out 
the setup I would reboot. Do the iwconfig then do the ifconfig with a 
know address and then see if you can ping.

Is anyone else have problem to connect WIFI to different access points 
in one session (I had the same problem when I tried the Debian 
distribution, but I assume they have the same wifi driver)

/Tore


Xavier Bestel wrote:
>
> Is the GUI thing (in "settings" from 2008.8) supposed to work with a WEP
> network ?
>
> Thanks,
> 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: WiFi doesn't work

[Xavier Bestel]

On Thu, 2008-09-11 at 14:28 +0200, Tore Martin Hagen wrote:
> The problem is not WLAN but the dhcp client, as you see you get a 
> response, but then you send back a DHCPDECLINE.
> 
> What you can do is to stop the dhcp client and then configure the 
> interface manually.
> 
> ifconfig eth0 192.168.4.180 netmask 255.255.255.0

I tried that, but I couldn't get a ping to get through.
Even after manually fiddling with routes to be sure they were setup
correctly, I couldn't get anything to work.
USB works perfectly though.

Is the GUI thing (in "settings" from 2008.8) supposed to work with a WEP
network ?

Thanks,
Xav



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi doesn't work

[Tore Martin Hagen]

The problem is not WLAN but the dhcp client, as you see you get a 
response, but then you send back a DHCPDECLINE.

What you can do is to stop the dhcp client and then configure the 
interface manually.

ifconfig eth0 192.168.4.180 netmask 255.255.255.0

/Tore

Xavier Bestel wrote:
> Any hint ?
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi totally broken in Om2008.8?

[Daniel Hedblom]

This was what i found out yesterday.  Setting the AP to 802.11g was
the only way i could make it work. The sad part of this is that many
public and other APs don't run 802.11g so this solution only helps on
my own AP. Out of the house its not so easy to get a connection.

2008/5/14 Bryan DeLuca <[EMAIL PROTECTED]>:
> On Sat, 6 Sep 2008 17:13:26 +0200
> "Daniel Hedblom" <[EMAIL PROTECTED]> wrote:
>
>> Im trying to get wifi going on my freerunner but i havent got any
>> success yet at all. I have tried the various tips in the wiki but
>> whatever i do packets seems to end up in the bit-bucket. Even as
>> ifconfig shows packets going through eth0 both in and out nothing gets
>> past the wireless driver when i check on the Wireless AP or on another
>> computer with wireshark. Disabling usb0 and its default route havent
>> helped. I regard myself as a pretty seasoned Linux user ( +10 years )
>> but this phone has me beaten for now.
>>
>> I have also tried with Trolltechs Qtopia image and i have the same
>> problem there. Am i fighting windmills, just plain thick or is my wifi
>> nic in the phone perhaps broken?
>>
>
> I was having Wifi trouble under every distro until I remembered that I 
> disabled 802.11G on my AP.  I'm pretty anal about how tightly configured my 
> AP is, which can shoot you in the foot if you forget all the fancy stuff you 
> setup months ago.   Looks like the FreeRunner radio only supports G.  After 
> that I had no problem connecting with WPA2.
>
> Hope this helps.
> -Bryan
> --
> Bryan DeLuca <[EMAIL PROTECTED]>
>
> ___
> 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: Wifi totally broken in Om2008.8?

[Bryan DeLuca]

On Sat, 6 Sep 2008 17:13:26 +0200
"Daniel Hedblom" <[EMAIL PROTECTED]> wrote:

> Im trying to get wifi going on my freerunner but i havent got any
> success yet at all. I have tried the various tips in the wiki but
> whatever i do packets seems to end up in the bit-bucket. Even as
> ifconfig shows packets going through eth0 both in and out nothing gets
> past the wireless driver when i check on the Wireless AP or on another
> computer with wireshark. Disabling usb0 and its default route havent
> helped. I regard myself as a pretty seasoned Linux user ( +10 years )
> but this phone has me beaten for now.
> 
> I have also tried with Trolltechs Qtopia image and i have the same
> problem there. Am i fighting windmills, just plain thick or is my wifi
> nic in the phone perhaps broken?
> 

I was having Wifi trouble under every distro until I remembered that I disabled 
802.11G on my AP.  I'm pretty anal about how tightly configured my AP is, which 
can shoot you in the foot if you forget all the fancy stuff you setup months 
ago.   Looks like the FreeRunner radio only supports G.  After that I had no 
problem connecting with WPA2.

Hope this helps.
-Bryan
-- 
Bryan DeLuca <[EMAIL PROTECTED]>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi totally broken in Om2008.8?

[Stefan Strahl]

Hi Daniel :)

I also had troubles first getting Wifi running with Om2008.08. What
did you do so far to the config? I assume "iwlist eth0 scan" is
working? My "D'oh"-experience was that I needed to use WPA2 in the
wpa_supplicant.conf and not WPA. Here is what I did to get it running:

1) create /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
   ssid="THISISNOWIFI"
   scan_ssid=1
   proto=RSN
   key_mgmt=WPA-PSK
   pairwise=CCMP TKIP
   group=TKIP CCMP
   psk=""
   priority=50
}

# WPA:
network={
  ssid="THISISNOWIFI"
  proto=WPA
  key_mgmt=WPA-PSK
  pairwise=TKIP
  group=TKIP
  scan_ssid=1
  psk=""
  priority=10
}

# WEP:
network={
 ssid="NETGEAR"
 scan_ssid=1
 key_mgmt=NONE
 wep_tx_keyidx=0
 wep_key0=
 priority=8
}

# Open:
network={
 ssid="your ssid"
 key_mgmt=NONE
 priority=5
}

then edit in /etc/network/interfaces

auto eth0
iface eth0 inet dhcp
   wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


then I did a

iwconfig eth0 essid THISISNOWIFI

and finally

ifdown eth0
ifup eth0

Do you see any "WPA" or "udhcc" messages?

:) stefan
:) stefan

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI on FR

[julien cubizolles]

Le vendredi 29 août 2008 à 09:01 +0200, Jean-Eric Cuendet a écrit :
> 
> 
> 
> The raster image works brilliantly and this doesn't seem to be
> a problem fyi.
> 
> Is it Om2008.8 update from 25 august?
> Or is there some other image? Where?

You can get it here :
http://download.enlightenment.org/misc/

Julien.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI on FR

[Sarton O'Brien]

On Friday 29 August 2008 17:01:36 Jean-Eric Cuendet wrote:
> > The raster image works brilliantly and this doesn't seem to be a problem
> > fyi.
>
> Is it Om2008.8 update from 25 august?
> Or is there some other image? Where?

Download the raster image for gta02 here:

http://download.enlightenment.org/misc/

It's a modified om2008 ... there's quite a bit of updating (opkg update&&opkg 
upgrade) but the end result seems to work quite well and it's inline with the 
current stable development repos so ... yay :)

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI on FR

[Jean-Eric Cuendet]

>
> The raster image works brilliantly and this doesn't seem to be a problem
> fyi.


Is it Om2008.8 update from 25 august?
Or is there some other image? Where?


>
>
> For anyone testing images, I've been through nearly all and the raster
> image
> updated using the official om2008 repos works very nicely.
>
> Good work rasterman! Greatly appreciated (sorry if I got any spelling
> wrong),
>
> 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: WIFI on FR

[Sarton O'Brien]

On Friday 29 August 2008 15:29:52 Sarton O'Brien wrote:
> It's likely to be the nameserver issue most people experience. For some
> reason the nameserver obtained via udhcpc is not written to the symlinked
> location of resolv.conf (/var/run/resolv.conf).

The raster image works brilliantly and this doesn't seem to be a problem fyi.

For anyone testing images, I've been through nearly all and the raster image 
updated using the official om2008 repos works very nicely.

Good work rasterman! Greatly appreciated (sorry if I got any spelling wrong),

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI on FR

[Sarton O'Brien]

On Friday 29 August 2008 15:01:21 Jean-Eric Cuendet wrote:
> Hi,
> I'm unable to make the wifi working on my FR
> Could someone explain how to do it?
> I have an open access point, with DHCP. My laptop connects and works well
> with it.
>
> I go to Settings, then choose WIFI, then click on it : it passes to ON
> Then, after some seconds, I see my WIFI ESSID. I click on it (is that what
> should do) and nothing happens...

Are you obtaining a dhcp lease from your router?

It's likely to be the nameserver issue most people experience. For some reason 
the nameserver obtained via udhcpc is not written to the symlinked location of 
resolv.conf (/var/run/resolv.conf).

It's probably a good idea to ssh/terminal in and check iwconfig/ifconfig, make 
sure you have an IP and then modify the network scripts to add your nameserver 
to /var/run/resolv.conf

Somebody on here suggested adding the nameserver to a location on flash, so it 
may be that the symlink for /etc/resolv.conf is overwritten by the networking 
scripts in which case the file will either be /etc/resolv.conf or 
/etc/networking/eth0 ... or something like that. This is off the top of my 
head.

Stay tuned for a more comprehensive reply ... from someone else :)

Ahh there it is ... a wiki link ... of course :) ... but I'll send this 
redundant information just in case ... this thread will be archived anyway and 
there may be information lacking on the wiki.

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WIFI on FR

[Robert William Hutton]

Jean-Eric Cuendet wrote:
> Hi,
> I'm unable to make the wifi working on my FR
> Could someone explain how to do it?

http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi

Cheers,

Rob

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Jay Vaughan]

> SettingsGUI still has to be ported to GTA02 and the FSO image. This is
> what I'll be doing here during the next days.


I'll be very happy to test on GTA02 and GTA01 concurrently, and help  
out any way I can. I think SettingsGUI could make a lot of mundane OM  
tasks a lot more pleasant, frankly ..

;
--
Jay Vaughan





___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Kristian 'kriss' Mueller]

> > I've spent a great deal of time messing with WIFI also.  Once I get  
> > some
> > more experience with the OM platform, I might contribute to
> > building a gui network manager.
>
> I really believe that a lot of the common system administration-type  
> tasks - such as setting up WLAN, setting up GPRS routing, etc. - can  
> and should be wrapped up in very easy-to-write tools with a GUI.  For  
> example, the SettingsGUI progress was awesome, maybe because its  
> python-based, and perhaps we all should be looking to extend this app  
> to include the more detailed admin procedures?

Thanks Jay!

Actually I am integrating mofi panel after John Beaven contected me:
 http://projects.openmoko.org/projects/mofi/

SettingsGUI still has to be ported to GTA02 and the FSO image. This is
what I'll be doing here during the next days.

If anyone wants to try it out and give feedback, see the SVN repository
at our neo1973-germany trac:
 http://neo1973-germany.de/wiki/SettingsGUI


Greetings from Berlin
Kristian
-- 
/* Web: http://www.mput.de  | Tel:+49 (0)170/6692447  *
 * Blog:http://mput.de/blog | ICQ:93248497*
 * GPG-ID:  4BBB6525 (..2009)   | Jabber: [EMAIL PROTECTED]*
 * Twitter: kristian_m  | MSN:[EMAIL PROTECTED] */


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Dietmar Friede]

On Sunday 20 July 2008, Charles Hill wrote:
> After two days of fighting with WPA2-PSK and getting nowhere, I figured
> something out.
>
> My WAP doesn't broadcast the SSID.  Normally, this isn't a problem as I
> specify the SSID in the wpa_supplicant.conf file.  But when I turned ON
> broadcast of SSID, I connected immediately and it even properly updated my
> resolv.conf file.
>

I used the following wpa_supplicant.conf and had no problems to connect
to a hidden SSID:

[EMAIL PROTECTED]:~# cat /etc/wpa_supplicant/wpa_supplicant.conf
# WPA-PSK/TKIP

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
ssid="HIDDEN"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk="what ever"
}

[EMAIL PROTECTED]:~# 
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B ; ifup 
eth0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
udhcpc (v1.11.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
Sending discover...
Sending discover...
Sending select for 192.168.1.9...
Lease of 192.168.1.9 obtained, lease time 268435455
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
adding dns 192.168.1.21

Dietmar Friede
PS.: The FR is really great. Good work!!!

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Mikael Berthe]

* Tommi Kärkkäinen <[EMAIL PROTECTED]> [2008-07-16 19:21 +0200]:
> 
> It seems random when I can connect and when I can't. It seems DHCP 
> occasionally fails to give the config. At times, however, I am able to 
> connect and use the wifi, and even then I am getting the ioctl message.

Maybe udhcpc gives up before the AP is associated?

BTW, it looks like adding
  iwconfig eth0 essid $ESSID channel $CHANNEL
just before calling wpa_supplicant speeds up things for me.

It hasn't failed since I started doing that, FWIW.

Regards,
-- 
MiKael

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Tommi Kärkkäinen]

Indeed it does. I started thinking if there was something like that late 
last night, but wasn't sure if it's replicable. It seems it is now.

Thanks for the info.

Bumbl kirjoitti:
> For me udhcpc only fails the first time it is run to get the correct data
> If you run it immediatly after the first try it succeeds.
> Tommi Kärkkäinen wrote:
>> Stephen Shelton kirjoitti:
>>
>>   
>>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>>> which would lead me to believe the kernel is unhappy...
>>> 
>> Even more specifically, is the message "ioctl[SIOCSIWENCODEEXT]: 
>> Operation not supported"? I get that too, but it doesn't prevent me from 
>> using my WPA-PSK WLAN. Something else is... :)
>>
>> It seems random when I can connect and when I can't. It seems DHCP 
>> occasionally fails to give the config. At times, however, I am able to 
>> connect and use the wifi, and even then I am getting the ioctl message.
>>
>> I hope this was at least of some help to you.
>>
>>
>> Tommi
>>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Bumbl]

For me udhcpc only fails the first time it is run to get the correct data
If you run it immediatly after the first try it succeeds.
Tommi Kärkkäinen wrote:
> Stephen Shelton kirjoitti:
>
>   
>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>> which would lead me to believe the kernel is unhappy...
>> 
>
> Even more specifically, is the message "ioctl[SIOCSIWENCODEEXT]: 
> Operation not supported"? I get that too, but it doesn't prevent me from 
> using my WPA-PSK WLAN. Something else is... :)
>
> It seems random when I can connect and when I can't. It seems DHCP 
> occasionally fails to give the config. At times, however, I am able to 
> connect and use the wifi, and even then I am getting the ioctl message.
>
> I hope this was at least of some help to you.
>
>
> Tommi
>
> ___
> 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: wifi

[Bumbl]

I do get nameresolution only sometimes although resolv.conf lists the 
correct nameserver.
You have to try a few ifup eth0 and ifdown eth0 and it has proven 
helpful to run commands more than once (e.g. ping www.openmoko.org 2-3 
times after each other)

Bastian Feder wrote:
> Hi,
> I also managed to connect to WPA2 and open hotspots. But do not get a
> nameresolution. I will work on that tonight ... perhabs I find the
> problem.
> Any idea on your side? Do you get nameresolution?
>
> hf
> Bastian
>
> On Wed, Jul 16, 2008 at 7:16 PM, Matthew Lane <[EMAIL PROTECTED]> wrote:
>   
>> Stephen Shelton wrote:
>> 
>>> I've been beating my head against the wall trying to get my FR to connect 
>>> to any
>>> secured wireless AP. It has no trouble connecting if there is no 
>>> encryption, but
>>> I've had no luck otherwise.
>>>
>>> If anyone has had a better experience than me, perhaps you could take a 
>>> look at
>>> the "GTA02 WLAN" page on the wiki 
>>> (http://wiki.openmoko.org/wiki/GTA02_WLAN) and
>>> contribute or clean up.
>>>
>>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>>> which would lead me to believe the kernel is unhappy...
>>>
>>> Much thanks to anyone who might contribute...
>>>
>>>   
>> I've spent a great deal of time messing with WIFI also.  Once I get some
>> more experience with the OM platform, I might contribute to building a
>> gui network manager.
>>
>> I also get that error message when starting udhcpc.  All the tricks lie
>> in your wpa_supplicant.conf file located in /etc/wpa_supplicant/.  There
>> are a few [poorly] written syntax tutorials to create this
>> wpa_supplicant, but once you get the swing of it, it's not too bad.
>> What kind of network are you attempting to connect to?  I haven't
>> figured out how to connect to my university's PEAP network yet, but I
>> have gotten WPA2 & Open networks to connect successfully.
>>
>> ___
>> 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: wifi

[julien cubizolles]

Le mercredi 16 juillet 2008 à 20:03 +0200, julien cubizolles a écrit :

> But it was just once, when I got the Freerunner. Now, after several opkg
> upgrades (don't know if it's related thoug), I can't get it to get a
> lease anymore.

It's working again ! Here are my settings :

/etc/network/interfaces
 
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

and /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=var/volatile/run/wpa_supplicant
eapol_version=1
ap_scan=1

# WPA:
network={
  ssid="myssid"
  scan_ssid=1
  psk="mypasskey"
  priority=10
}


I just get an error message from sed :
sed : unrecognized option "--quiet"
But otherwise the wlan is working fine.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Jay Vaughan]

> I've spent a great deal of time messing with WIFI also.  Once I get  
> some
> more experience with the OM platform, I might contribute to
> building a gui network manager.
>



One thing that really needs to be clear among us all right now is that  
there are those who have hacked things together to make the OM work  
for their situation, and left it at that, and then there are those who  
are yet to do so.

Those of us who have worked out how to bend the phone to our will need  
to write up our procedures and make them more widely known - through  
the wiki and these lists - so that we can have a sort of working  
framework for further apps development.

I really believe that a lot of the common system administration-type  
tasks - such as setting up WLAN, setting up GPRS routing, etc. - can  
and should be wrapped up in very easy-to-write tools with a GUI.  For  
example, the SettingsGUI progress was awesome, maybe because its  
python-based, and perhaps we all should be looking to extend this app  
to include the more detailed admin procedures?

;
--
Jay Vaughan





___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Bob Frank]

I would also like to see NetworkManager on the FreeRunner.  Preferably v0.7,
it's not out yet, but its still much better than 0.6, and the API and code
makes a lot more sense to me.  And with all the work that Dan Williams put
into the OLPC version of it, it shouldn't be too heavy in resources.  Once I
setup my computer for building I'll probably start to port it, but I have no
idea how long that will be.

-Bob Frank

On Wed, Jul 16, 2008 at 7:47 PM, Russell Sears <[EMAIL PROTECTED]>
wrote:

> Stephen Shelton wrote:
> > On Wed, Jul 16, 2008 at 07:36:29PM +0200, Christophe Badoit wrote:
> >> For WEP, I'm currently connecting with :
> >>
> >> ifconfig eth0 up
> >> iwconfig eth0 essid any
> >> iwconfig eth0 key 'mykey'
> >> iwconfig eth0 essid 'myssid'
> >> ifup eth0
> >>
> >> Something strange, I am unable to set the key (iwconfig key) if the
> >> essid is not "any".
> >>
> >> I began patching wifi-radar (a wifi python/gtk app) for the FR, if I've
> >> got enough time, I'll try to release it.
> >>
> >> - --
> >> Christophe Badoit
> >
> > I was able to connect to my WEP network doing the above. Thanks for the
> > pointer... that should get me started!
> >
> > I'd rather see wicd used as a gui; my experience with wifi-radar has been
> just
> > awful. The UI locks up frequently, is it even using any multi threading?
> Wicd
> > has worked very nicely for me, and seems a bit more configurable.
>
> Not to jump into a religious war, but why not use something based on
> NetworkManager?
>
> It provides clean separation between the scripting / hardware
> interfacing stuff and the gui.  It also supports multiple types of
> network devices (I use it to for the ethernet and wifi on my laptop, and
> it seems to know what pppd and modems are...).
>
> It supports all sorts of crazy network security protocols, including
> many of the wifi ones and openvpn.  It's the default under ubuntu these
> days, and is distribution and gui toolkit agnostic.  There are GUIs for
> qt and gtk (and perhaps others).  I think there are also command line
> utilities, though I've never needed them.
>
> Regardless of which GUI is added, it probably should also know about
> usb0, and GPRS so that it's easy to switch between networks, and to tell
> if you're burning through your cell phone data plan or using wifi... ;)
>
> -Rusty
>
> >
> > I'd really like to see someone who knows what they are talking about
> update that
> > wiki page; I'm sure that's a sore spot for quite a few new openmoko
> users...
> >
>
> ___
> 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: wifi

[Russell Sears]

Stephen Shelton wrote:
> On Wed, Jul 16, 2008 at 07:36:29PM +0200, Christophe Badoit wrote:
>> For WEP, I'm currently connecting with :
>>
>> ifconfig eth0 up
>> iwconfig eth0 essid any
>> iwconfig eth0 key 'mykey'
>> iwconfig eth0 essid 'myssid'
>> ifup eth0
>>
>> Something strange, I am unable to set the key (iwconfig key) if the
>> essid is not "any".
>>
>> I began patching wifi-radar (a wifi python/gtk app) for the FR, if I've
>> got enough time, I'll try to release it.
>>
>> - --
>> Christophe Badoit
> 
> I was able to connect to my WEP network doing the above. Thanks for the
> pointer... that should get me started!
> 
> I'd rather see wicd used as a gui; my experience with wifi-radar has been just
> awful. The UI locks up frequently, is it even using any multi threading? Wicd
> has worked very nicely for me, and seems a bit more configurable.

Not to jump into a religious war, but why not use something based on 
NetworkManager?

It provides clean separation between the scripting / hardware 
interfacing stuff and the gui.  It also supports multiple types of 
network devices (I use it to for the ethernet and wifi on my laptop, and 
it seems to know what pppd and modems are...).

It supports all sorts of crazy network security protocols, including 
many of the wifi ones and openvpn.  It's the default under ubuntu these 
days, and is distribution and gui toolkit agnostic.  There are GUIs for 
qt and gtk (and perhaps others).  I think there are also command line 
utilities, though I've never needed them.

Regardless of which GUI is added, it probably should also know about 
usb0, and GPRS so that it's easy to switch between networks, and to tell 
if you're burning through your cell phone data plan or using wifi... ;)

-Rusty

> 
> I'd really like to see someone who knows what they are talking about update 
> that
> wiki page; I'm sure that's a sore spot for quite a few new openmoko users...
> 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Stephen Shelton]

On Wed, Jul 16, 2008 at 07:36:29PM +0200, Christophe Badoit wrote:
> For WEP, I'm currently connecting with :
> 
> ifconfig eth0 up
> iwconfig eth0 essid any
> iwconfig eth0 key 'mykey'
> iwconfig eth0 essid 'myssid'
> ifup eth0
> 
> Something strange, I am unable to set the key (iwconfig key) if the
> essid is not "any".
> 
> I began patching wifi-radar (a wifi python/gtk app) for the FR, if I've
> got enough time, I'll try to release it.
> 
> - --
> Christophe Badoit

I was able to connect to my WEP network doing the above. Thanks for the
pointer... that should get me started!

I'd rather see wicd used as a gui; my experience with wifi-radar has been just
awful. The UI locks up frequently, is it even using any multi threading? Wicd
has worked very nicely for me, and seems a bit more configurable.

I'd really like to see someone who knows what they are talking about update that
wiki page; I'm sure that's a sore spot for quite a few new openmoko users...

-- 
Stephen Shelton
[EMAIL PROTECTED]
http://www.stephenashelton.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Bastian Feder]

HI,
I recently found a german (sry) description of someone who manged to
get the WLan up and running:

http://freeyourphone.de/portal_v1/viewtopic.php?f=5&t=252


As far as I understand he added:

ifdown usb0

to the start section and

ifup usb0

to the stop section of the shell script propagated by the openmoko wiki.

I'll give it a try ;o)

Bastian


On Wed, Jul 16, 2008 at 8:03 PM, julien cubizolles <[EMAIL PROTECTED]> wrote:
> Le mercredi 16 juillet 2008 à 11:56 -0500, Stephen Shelton a écrit :
>> I've been beating my head against the wall trying to get my FR to connect to 
>> any
>> secured wireless AP. It has no trouble connecting if there is no encryption, 
>> but
>> I've had no luck otherwise.
>>
>> If anyone has had a better experience than me, perhaps you could take a look 
>> at
>> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
>> and
>> contribute or clean up.
>
>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>> which would lead me to believe the kernel is unhappy...
>
> I could connect to my WPA2 protected wlan following the indications on
> the above page even though I was getting the same message.
>
> But it was just once, when I got the Freerunner. Now, after several opkg
> upgrades (don't know if it's related thoug), I can't get it to get a
> lease anymore.
>
> I tried running wpa_supplicant in foreground (ie without the -B swith)
> to catch additionnal error messages. I get :
>
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
>
> After that, udhcpc0 can't get a lease and goes
>
> Sending discover...
> Sending discover...
> Sending discover...
> run-parts: /etc/udhcpc.d/99avahi-autoipd exited with code 1
>
> forever...
>
> Julien.
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>



-- 
--
spread the word ... see www.browsehappy.com ;o)

Calvin: Weekends don't count unless you spend them doing something
completely pointless.

Join the Greater IBM Connection (http://www.xing.com/premiumgroup-6291.d26b7d)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Bastian Feder]

Hey Julian,
I had the same problem and fixed this by adding :

up echo nameserver [IPofYourRouter]  > /etc/resolv.conf


to the eth0 section of your /etcnetwork/interfaces - file.

hope that helps

Bastian

On Wed, Jul 16, 2008 at 8:03 PM, julien cubizolles <[EMAIL PROTECTED]> wrote:
> Le mercredi 16 juillet 2008 à 11:56 -0500, Stephen Shelton a écrit :
>> I've been beating my head against the wall trying to get my FR to connect to 
>> any
>> secured wireless AP. It has no trouble connecting if there is no encryption, 
>> but
>> I've had no luck otherwise.
>>
>> If anyone has had a better experience than me, perhaps you could take a look 
>> at
>> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
>> and
>> contribute or clean up.
>
>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>> which would lead me to believe the kernel is unhappy...
>
> I could connect to my WPA2 protected wlan following the indications on
> the above page even though I was getting the same message.
>
> But it was just once, when I got the Freerunner. Now, after several opkg
> upgrades (don't know if it's related thoug), I can't get it to get a
> lease anymore.
>
> I tried running wpa_supplicant in foreground (ie without the -B swith)
> to catch additionnal error messages. I get :
>
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
>
> After that, udhcpc0 can't get a lease and goes
>
> Sending discover...
> Sending discover...
> Sending discover...
> run-parts: /etc/udhcpc.d/99avahi-autoipd exited with code 1
>
> forever...
>
> Julien.
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>



-- 
--
spread the word ... see www.browsehappy.com ;o)

Calvin: Weekends don't count unless you spend them doing something
completely pointless.

Join the Greater IBM Connection (http://www.xing.com/premiumgroup-6291.d26b7d)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[julien cubizolles]

Le mercredi 16 juillet 2008 à 11:56 -0500, Stephen Shelton a écrit :
> I've been beating my head against the wall trying to get my FR to connect to 
> any
> secured wireless AP. It has no trouble connecting if there is no encryption, 
> but
> I've had no luck otherwise.
> 
> If anyone has had a better experience than me, perhaps you could take a look 
> at
> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
> and
> contribute or clean up.

> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
> which would lead me to believe the kernel is unhappy...

I could connect to my WPA2 protected wlan following the indications on
the above page even though I was getting the same message.

But it was just once, when I got the Freerunner. Now, after several opkg
upgrades (don't know if it's related thoug), I can't get it to get a
lease anymore.

I tried running wpa_supplicant in foreground (ie without the -B swith)
to catch additionnal error messages. I get :

ioctl[SIOCGIWSCAN]: Resource temporarily unavailable

After that, udhcpc0 can't get a lease and goes 

Sending discover...
Sending discover...
Sending discover...
run-parts: /etc/udhcpc.d/99avahi-autoipd exited with code 1

forever...

Julien.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Christophe Badoit]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Stephen Shelton a écrit :
> I've been beating my head against the wall trying to get my FR to connect to 
> any
> secured wireless AP. It has no trouble connecting if there is no encryption, 
> but
> I've had no luck otherwise.
> 
> If anyone has had a better experience than me, perhaps you could take a look 
> at
> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
> and
> contribute or clean up.
> 
> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
> which would lead me to believe the kernel is unhappy...
> 
> Much thanks to anyone who might contribute...

For WEP, I'm currently connecting with :

ifconfig eth0 up
iwconfig eth0 essid any
iwconfig eth0 key 'mykey'
iwconfig eth0 essid 'myssid'
ifup eth0

Something strange, I am unable to set the key (iwconfig key) if the
essid is not "any".

I began patching wifi-radar (a wifi python/gtk app) for the FR, if I've
got enough time, I'll try to release it.

- --
Christophe Badoit

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIfjGdynEdw4rmTRkRAiIFAJ9w8aZUeT7KGHsTiPDZAmhfDaRpdQCfcq7T
2KAkm80GmXR5aSDsQdLSBw4=
=Ovzk
-END PGP SIGNATURE-


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Bastian Feder]

Hi,
I also managed to connect to WPA2 and open hotspots. But do not get a
nameresolution. I will work on that tonight ... perhabs I find the
problem.
Any idea on your side? Do you get nameresolution?

hf
Bastian

On Wed, Jul 16, 2008 at 7:16 PM, Matthew Lane <[EMAIL PROTECTED]> wrote:
> Stephen Shelton wrote:
>> I've been beating my head against the wall trying to get my FR to connect to 
>> any
>> secured wireless AP. It has no trouble connecting if there is no encryption, 
>> but
>> I've had no luck otherwise.
>>
>> If anyone has had a better experience than me, perhaps you could take a look 
>> at
>> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
>> and
>> contribute or clean up.
>>
>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>> which would lead me to believe the kernel is unhappy...
>>
>> Much thanks to anyone who might contribute...
>>
> I've spent a great deal of time messing with WIFI also.  Once I get some
> more experience with the OM platform, I might contribute to building a
> gui network manager.
>
> I also get that error message when starting udhcpc.  All the tricks lie
> in your wpa_supplicant.conf file located in /etc/wpa_supplicant/.  There
> are a few [poorly] written syntax tutorials to create this
> wpa_supplicant, but once you get the swing of it, it's not too bad.
> What kind of network are you attempting to connect to?  I haven't
> figured out how to connect to my university's PEAP network yet, but I
> have gotten WPA2 & Open networks to connect successfully.
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>



-- 
--
spread the word ... see  www.browsehappy.com ;o)

Calvin: Weekends don't count unless you spend them doing something
completely pointless.

Join the Greater IBM  Connection (http://www.xing.com/premiumgroup-6291.d26b7d)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Tommi Kärkkäinen]

Stephen Shelton kirjoitti:

> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
> which would lead me to believe the kernel is unhappy...

Even more specifically, is the message "ioctl[SIOCSIWENCODEEXT]: 
Operation not supported"? I get that too, but it doesn't prevent me from 
using my WPA-PSK WLAN. Something else is... :)

It seems random when I can connect and when I can't. It seems DHCP 
occasionally fails to give the config. At times, however, I am able to 
connect and use the wifi, and even then I am getting the ioctl message.

I hope this was at least of some help to you.


Tommi

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: wifi

[Matthew Lane]

Stephen Shelton wrote:
> I've been beating my head against the wall trying to get my FR to connect to 
> any
> secured wireless AP. It has no trouble connecting if there is no encryption, 
> but
> I've had no luck otherwise.
>
> If anyone has had a better experience than me, perhaps you could take a look 
> at
> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
> and
> contribute or clean up.
>
> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
> which would lead me to believe the kernel is unhappy...
>
> Much thanks to anyone who might contribute...
>   
I've spent a great deal of time messing with WIFI also.  Once I get some 
more experience with the OM platform, I might contribute to building a 
gui network manager.

I also get that error message when starting udhcpc.  All the tricks lie 
in your wpa_supplicant.conf file located in /etc/wpa_supplicant/.  There 
are a few [poorly] written syntax tutorials to create this 
wpa_supplicant, but once you get the swing of it, it's not too bad.  
What kind of network are you attempting to connect to?  I haven't 
figured out how to connect to my university's PEAP network yet, but I 
have gotten WPA2 & Open networks to connect successfully.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi chip squeezes 802.11n into MicroSD cards

[Dr. H. Nikolaus Schaller]

Am 10.01.2008 um 21:29 schrieb Michael Shiloh:

Yeah, cool. Can you toss this up on the wiki in the appropriate  
section?


If someone can help me to tell what "the appropriate section" is...


Dr. H. Nikolaus Schaller wrote:

Something interesting - could be good to see in GTA03:
http://www.linuxdevices.com/news/NS8925554018.html
___
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: WiFi chip squeezes 802.11n into MicroSD cards

[Michael Shiloh]

Yeah, cool. Can you toss this up on the wiki in the appropriate section?

Michael

Dr. H. Nikolaus Schaller wrote:

Something interesting - could be good to see in GTA03:

http://www.linuxdevices.com/news/NS8925554018.html

___
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: WiFi chip squeezes 802.11n into MicroSD cards

[andy selby]

Would the fact that the microSD card is buried inside the neo
attenuate the signal?
Looks like a good way of retro-fitting wi-fi into my GTA01

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Jeff Andros]

On 8/25/07, Bartlomiej Zdanowski AutoGuard Ltd. <[EMAIL PROTECTED]>
wrote:
>
>
>  Memory card under the SIM card (why? there's seemingly loads of space).
>
>  If there would be USB2 there will be no need to remove SD card much
> often. But still SD will be removed more often that SIM card, so maybe it
> should be somewhere else. Some phones had a SIM card slot directly in case
> like laptops have SD slots (if they have). Maybe Neo can have SD slot at the
> side of case.
> 
>
>
A while back Sean commented on this
http://lists.openmoko.org/pipermail/community/2006-November/000385.html
"seemingly loads of space" you mean in the case, or on the PCB? because the
PCB looks relatively cramped to me

-- 
Jeff
O|||O
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Ian Stirling]

Bartlomiej Zdanowski AutoGuard Ltd. wrote:

Hi.
Giles, your criticism is constructive and good so it leads to better 
device development. But there are some points that I don't agree.

Giles Jones pisze:


Port layout seemingly done at random, poor layout. USB/power connector better 
at bottom of device.
 


No chance since there are antennas on both sides of device.



This isn't strictly required.

As I see it, with minimal case redesign only.

http://wiki.openmoko.org/images/thumb/6/62/Gta01b_v3_case_top_open_pcb_lift_white.jpg/700px-Gta01b_v3_case_top_open_pcb_lift_white.jpg
Shift GPS ceramic antenna 'back' by 5mm or so.
Redesign the mainboard to extend up to the top of the case on that side, 
past the GPS antenna.

Mount a right-angle mini-B connector there.


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Bartlomiej Zdanowski AutoGuard Ltd.]

Hi.
Giles, your criticism is constructive and good so it leads to better 
device development. But there are some points that I don't agree.

Giles Jones pisze:

Port layout seemingly done at random, poor layout. USB/power connector better 
at bottom of device.
  

No chance since there are antennas on both sides of device.

Battery removal could be easier.
  
I don't have such problem. Everytime I remove back cover (with pain in 
my figers :( and that's the real problem) the battery almost pops out by 
it's own will... Maybe we have slightly different phones.

Memory card under the SIM card (why? there's seemingly loads of space).
  
If there would be USB2 there will be no need to remove SD card much 
often. But still SD will be removed more often that SIM card, so maybe 
it should be somewhere else. Some phones had a SIM card slot directly in 
case like laptops have SD slots (if they have). Maybe Neo can have SD 
slot at the side of case.

2.5mm audio jack (use 3.5mm like Nokia N95 to get mp3 marketshare)
  

True, but remember about microphone and fourth "pin" in phones' jack.

Power button location (location towards top is better, mine's also a bit 
sticky/spongey).
  
It doesn't bother me much but it's hard to push. We bought also 
white-orange Neo and my colleagues have used pen (sic!) to push it and 
there are some blue marks on button because of this.

Aux button looks like IR port (does it have any use outside of the bootloader?)
  
The same thought about black Neos but white one have this button white 
also so it's not confusing.

GSM antenna is at bottom of phone, should be at top of phone.
  
At the top there is a GPS antenna which *SHOULD* be there and that 
because GSM went on bottom.



Best regards,

--
*Bartlomiej Zdanowski*
Programmer
Product Research & Development Department
AutoGuard & Insurance Ltd.

Place of registration: Regional Court for the Capital City of Warsaw
Registration no.: 029534
Share capital: 1 059 000 PLN
Polish VAT and tax ID no.: PL1132219747
Omulewska 27 street
04-128 Warsaw
Poland
phone +48 22 611 69 23
www.autoguard.pl 
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Tim Shannon]

It was actually a joke.  If cell frequencies caused cancer, everyone would
be dead by now, because there are a lot worse stuff floating in the air.

On 8/24/07, AVee <[EMAIL PROTECTED]> wrote:
>
> On Friday 24 August 2007 15:18, Tim Shannon wrote:
> > I don't know about you guys, but personally I'd rather have the
> > electromagnetic radiation traveling under my chin, then through my
> brain,
> > but maybe brain cancer doesn't scare you as much.
>
> Braincancer may scare me, high frequency radio waves do not.
>
> AVee
>
> ___
> 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: WiFi vs. speaker

[AVee]

On Friday 24 August 2007 15:18, Tim Shannon wrote:
> I don't know about you guys, but personally I'd rather have the
> electromagnetic radiation traveling under my chin, then through my brain,
> but maybe brain cancer doesn't scare you as much.

Braincancer may scare me, high frequency radio waves do not.

AVee

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Tim Shannon]

I don't know about you guys, but personally I'd rather have the
electromagnetic radiation traveling under my chin, then through my brain,
but maybe brain cancer doesn't scare you as much.



On 8/24/07, Eric Johnson <[EMAIL PROTECTED]> wrote:
>
> Giles Jones wrote:
> > GSM antenna is at bottom of phone, should be at top of phone.
> >
> >
> I thought the idea of having the antenna at the bottom was so that the
> signal isn't attenuated by your head so much during a call.
> [At least someone told me that was a good thing on the RAZRs and it
> sounded convincing]
>
>
> Eric
>
> ___
> 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: WiFi vs. speaker

[Eric Johnson]

Giles Jones wrote:

GSM antenna is at bottom of phone, should be at top of phone.

  
I thought the idea of having the antenna at the bottom was so that the 
signal isn't attenuated by your head so much during a call.
[At least someone told me that was a good thing on the RAZRs and it 
sounded convincing]



Eric

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: WiFi vs. speaker

[Giles Jones]

Mark Haury <[EMAIL PROTECTED]> wrote :

> C'mon, guys, do you _really_ need that big hole right through the case? 
> Why don't you keep the stereo speakers and put the WiFi in that wasted 
> space instead 

The GSM antenna is next to the hole, not the best place for a wifi module.

I do agree with the comment about stereo, it is one feature a lot of phones 
lack and there's a few that have stereo which makes ringtone playback clearer. 
If you're clever you can make ringtones where the bass is in the left and the 
rest of the signal in the right. Should be clearer with some music.

You won't see any case changes as it has been stated previously that changing 
the tooling would be too expensive (this is a new project and it needs to grow 
gradually).

My comments on the Neo1973 hardware are below, I like this phone and want it to 
succeed, but at the same time being critical makes something better. If you 
aren't critical about a product before it gets to the press then you probably 
care more about money than success.

I don't really want to start off flamewars or have some of these design 
decisions explained to me as I don't think many of them can be explained (other 
than carelessness or for form factor reasons). Please just take the points on 
board when designing future hardware.

Likes:

It's light for its size.

I like the rubberised surface, hard wearing.

VGA screen is superb.

No creaks or rattles.

Open source :)

Generous accessories for the price.

Seemingly decent headphones.

Dislikes:

Back cover design is terrible and will easily break, especially given how 
tricky it is to remove.

Port layout seemingly done at random, poor layout. USB/power connector better 
at bottom of device.

Battery removal could be easier.

Memory card under the SIM card (why? there's seemingly loads of space).

2.5mm audio jack (use 3.5mm like Nokia N95 to get mp3 marketshare)

Power button location (location towards top is better, mine's also a bit 
sticky/spongey).

Aux button looks like IR port (does it have any use outside of the bootloader?)

GSM speed

Battery it at top of the phone unlike pretty much every other phone.

GSM antenna is at bottom of phone, should be at top of phone.

No dedicated volume up or down (important during a call when the screen 
backlight has switched off).

Fiddly SIM card holder.

Earpiece hole, the ear piece foam is visible? (looks like black fluff).


---
G O Jones





___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi (was Re: community Digest, Vol 15, Issue 1)

[Martin Lefkowitz]

Thats great!  Curious to know how open Marvell is to this?  Do you have
access to their firmware spec and driver porting guide?

Marty


Marcin Juszkiewicz wrote:
> Dnia poniedziałek, 19 lutego 2007, Martin Lefkowitz napisał:
>   
>>> Date: Mon, 19 Feb 2007 07:58:04 +0100
>>> From: Marcin Juszkiewicz <[EMAIL PROTECTED]>
>>>   
>
>   
>>> Marvel 8385 can be connected to SDIO, CF, SPI and it is one of chips
>>> you are talking about.
>>>   
>> Yes, and it looks like there is at least a project for the driver.
>> Started 11/06.  No release yet.
>> 
>
> I know. I'm one of people which created that project. Instead of creating 
> another driver we are moving to work with upstream (libertas/olpc 
> project).
>
>   


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi (was Re: community Digest, Vol 15, Issue 1)

[Marcin Juszkiewicz]

Dnia poniedziałek, 19 lutego 2007, Martin Lefkowitz napisał:
> > Date: Mon, 19 Feb 2007 07:58:04 +0100
> > From: Marcin Juszkiewicz <[EMAIL PROTECTED]>

> > Marvel 8385 can be connected to SDIO, CF, SPI and it is one of chips
> > you are talking about.
>
> Yes, and it looks like there is at least a project for the driver.
> Started 11/06.  No release yet.

I know. I'm one of people which created that project. Instead of creating 
another driver we are moving to work with upstream (libertas/olpc 
project).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

  catholic god himself invented autotools just for amusement
  first there was the great flood, then the plague, now autotools



___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi again

[Wolfgang S. Rupprecht]

Marty, thanks for the interesting insight.

Martin Lefkowitz writes:
> what both Atheros and Broadcom have done is have a binary that
> handles the interface for the chip that needs to be included in the
> opensource project.

>From my limited understanding, it appears that both Broadcom and
Marvell use an embedded ARM chip also.  An interesting blog entry by
Jim Gettys (at http://www.gettysfamily.org/wordpress/?p=27 ) mentions
how Marvell helped free up the Marvel wifi driver.  He also talks
about how the Marvell chip is crucial to the OLPC low power goals.
(Although the 300mw estimate for the running chip strikes me as kind
of high for use on a cell phone where one has maybe 3 watt-hours of
battery all together.)

> BTW it's interesting that the HTC uses the ACX100.  I actually designed,
> and developed the first version of, that interface for TI.  

I wonder how its power compares.  I'd certainly expect TI to have more
engineering and manufacturing talent on hand for building a really low
power wifi chip.

-wolfgang
-- 
Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi again

[Martin Lefkowitz]

They've gotten GSM to the point to where it uses a standard AT command
set (I think it's standard).  This means the driver is very simple.  The
current Wifi chips have a different approach.  They leverage the
resources on the host (i.e. scatter gather) and have the upper layer MAC
functions in the driver.  There is no standard interface there. I have
not looked at what Intel did (I would be surprised if it were any
different), but what both Atheros and Broadcom have done is have a
binary that handles the interface for the chip that needs to be included
in the opensource project.  I know with Atheros it taints the kernel.  I
know it used to be a pain in the ass to build on not as popular distros,
don't know what it's state is today though.

BTW it's interesting that the HTC uses the ACX100.  I actually designed,
and developed the first version of, that interface for TI.  That one is
different than the others in that the ACX100 (at least when I was
involved in it around 2000-02) was that it was so cheap for TI to put an
ARM core into a chipset, as well as the fact that at the time the 802.11
standard was not as mature as it is today (and it's still not mature
today).  802.11e was no wheres near complete.  That the ARM was used to
hide the registers/low level real time functions and  hardware functions
from the host --  that was my idea anyway.  I have not looked at the
opensource project but there should only be a software to software
interface necessary during it's operational phase.


Marty


> Date: Sat, 17 Feb 2007 19:29:25 -0800
> From: "Wolfgang S. Rupprecht"
>
>
>   
>> > This has been discussed many, many times in the last month.  According
>> > to Sean, no wifi chips that both are low-power and have open specs.
>> 
>
> It sounds like the GPS and GSM chips aren't open spec either.  That
> didn't stop them from being included.
>
> I wonder if openmoko could benefit from using whatever the OLPC (One
> Laptop Per Child) folks are using.  They are also going for low-power,
> but perhaps their definition of low-power is quite a bit higher than a
> cell phone's definition of low power.
>
> -wolfgang
> -- Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
>
>   


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi again

[Mikko Rauhala]

la, 2007-02-17 kello 19:29 -0800, Wolfgang S. Rupprecht kirjoitti:
> > This has been discussed many, many times in the last month.  According
> > to Sean, no wifi chips that both are low-power and have open specs.
> 
> It sounds like the GPS and GSM chips aren't open spec either.  That
> didn't stop them from being included.

True, but especially with the GSM chip it's a rather different
situation. It's rather hard to make and sell an open GSM stack,
unfortunately. I'm willing to view that mostly as an accessory of our
free system.

As for the GPS, it does seem to be more of a compromise, since it
requires the proprietary daemon bit on our otherwise free software
running SoC. However, I appreciate that the team are aiming for an open
device, but have bootstrapping problems. Also, the daemon in practice is
not as intrusive as a WLAN driver would be, even if ideologically
they're not much different; at least with the userland daemon there
shouldn't be much of an issue in upgrading the rest of the system, esp.
the kernel.

Hopefully later there will be more choice of good and more open
hardware, especially if they can say "we sold 2^n of our last phone, so
you want to work with us on an even more open version" :] (I also
suspect that somebody will make an open daemon replacement, but don't
have the expertise for that myself; FIC may or may not be able to
distribute that sort of thing by default but I'd be happy for simple
availability.)

> I wonder if openmoko could benefit from using whatever the OLPC (One
> Laptop Per Child) folks are using.

That's been mentioned and Sean noted it. It may yet prove fruitful in
future OpenMoko devices, yes, but of course I'm also only guessing from
a non-FIC standpoint.

-- 
Mikko Rauhala   - [EMAIL PROTECTED] - http://www.iki.fi/mjr/>
Transhumanist   - WTA member - http://www.transhumanism.org/>
Singularitarian - SIAI supporter - http://www.singinst.org/>


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wifi again

[Wolfgang S. Rupprecht]

> This has been discussed many, many times in the last month.  According
> to Sean, no wifi chips that both are low-power and have open specs.

It sounds like the GPS and GSM chips aren't open spec either.  That
didn't stop them from being included.

I wonder if openmoko could benefit from using whatever the OLPC (One
Laptop Per Child) folks are using.  They are also going for low-power,
but perhaps their definition of low-power is quite a bit higher than a
cell phone's definition of low power.

-wolfgang
-- 
Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/


___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community