2009/2/4 Oleg Sadov sa...@linux-ink.ru:
...
# iwconfig eth0 essid my-wifi
After that system hangs up and blinking by red LED in AUX button.
Seems like restricted key is key point for this situation -- with open
key all works good.
Can someone try to reproduce this situation? May be
[ Copying devel because that's where most of the WLAN-related
discussions are taking place. ]
Joachim Ott wrote:
I have the same except that the LED is not flashing. The system hangs,
I had to remove the battery.
I've attached a patch with a work-around to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
[4.965000] AR6000 connected event on freq 2437 with bssid my AP MAC
address listenInterval=100, beaconInterval = 100, beaconIeLen = 22
assocReqLen=59 assocRespLen =59
[4.965000] Network:
On Thursday 05 February 2009, Dylan Semler wrote:
On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson
openm...@mazikeen.demon.co.ukwrote:
I often get the above even with a working wpa_supplicant.conf because the
dhcp
discover starts being sent immediately, not after association, so dhcp
times
eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91
inet addr:169.254.6.255 Bcast:169.254.255.255
It seems to look like it's connected
nope. it's not.
the ip address shown is a generic one, assigned by avahi in absence of a
real one.
i don't know, what you did to obtain an
On Thu, Feb 5, 2009 at 3:09 AM, Andy Green a...@openmoko.com wrote:
Somebody in the thread at some point said:
| It seems to look like it's connected, but I still can't ping google, the
| AP, or access the internet.
usb0 is up too.
I use usb to ssh into the phone.
But, the missing
On Thu, Feb 5, 2009 at 5:56 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote:
'SetResourcePolicy WiFi enabled' tells FSO to power up the WiFi
irrespective
of whether any apps have issued 'RequestResource WiFi'. Before I do this I
have no eth0 available.
Yeah, but it seems to also configure
What about eth0?
inet6 addr: fe80::212:cfff:fe8f:3391/64
same thing basically, though probably not assigned by avahi but something
random (do you use ipv6 at home? does the fr kernel support ipv6 at all?)
___
support mailing list
On Thu, Feb 5, 2009 at 11:10 AM, arne anka openm...@ginguppin.de wrote:
What about eth0?
inet6 addr: fe80::212:cfff:fe8f:3391/64
same thing basically, though probably not assigned by avahi but something
random (do you use ipv6 at home? does the fr kernel support ipv6 at all?)
I just
On Wed, Feb 4, 2009 at 1:40 AM, Michael 'Mickey' Lauer
mic...@openmoko.orgwrote:
That's correct behaviour due to auto-release. Please read the usage
introduction at http://docs.freesmartphone.org/usage-intro.html
If you can't stay on the bus, use SetResourcePolicy.
My bad, I hadn't read
2009/2/4 Dylan Semler dylan.sem...@gmail.com:
...
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not
Am Wednesday 04 February 2009 10:08:37 schrieb Dylan Semler:
mic...@openmoko.orgwrote:
That's correct behaviour due to auto-release. Please read the usage
introduction at http://docs.freesmartphone.org/usage-intro.html
If you can't stay on the bus, use SetResourcePolicy.
My bad, I
On Wednesday 04 February 2009, Dylan Semler wrote:
On Wed, Feb 4, 2009 at 1:40 AM, Michael 'Mickey' Lauer
mic...@openmoko.orgwrote:
That's correct behaviour due to auto-release. Please read the usage
introduction at http://docs.freesmartphone.org/usage-intro.html
If you can't stay on
04/02/2009 10:51 +, Andy Green wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| r...@om-gta02:~# ifup eth0
| WPA: Configuring Interface
| ioctl[SIOCSIWENCODEEXT]: Operation not supported
| ioctl[SIOCSIWENCODEEXT]: Operation not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points
| successfully scaned by iwlist.
|
| Since the previous Jan 5th basis I understood the kernel had, there are
| relatively few patches.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| r...@om-gta02:~# ifup eth0
| WPA: Configuring Interface
| ioctl[SIOCSIWENCODEEXT]: Operation not supported
| ioctl[SIOCSIWENCODEEXT]: Operation not supported
| ioctl[SIOCSIWENCODEEXT]: Operation not
В Срд, 04/02/2009 в 15:57 +, Andy Green пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points
| successfully scaned by iwlist.
|
| Since the previous Jan 5th basis I
On Wed, Feb 4, 2009 at 4:51 AM, Andy Green a...@openmoko.com wrote:
What's dmesg have to say about all this excitement?
After SetResourcePolicy Wifi enable I get the following new lines in dmesg:
[21474827.275000] s3c2440-sdi s3c2440-sdi: host detect has no irq available
[21474827.275000]
On Wed, Feb 4, 2009 at 4:38 AM, Michael 'Mickey' Lauer
mic...@openmoko.orgwrote:
Am Wednesday 04 February 2009 10:08:37 schrieb Dylan Semler:
I don't _think_ it's a configuration issue, as my setup hasn't changed
since M4 and I'm using the same config files.
I'm afraid the new kernel
On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote:
I often get the above even with a working wpa_supplicant.conf because the
dhcp
discover starts being sent immediately, not after association, so dhcp
times
out before association is complete. Bringing the
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver
Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler:
It seems that my prior FSO wifi configuration no longer works with M5.
Did you request WiFi with the Usage API?
--
:M:
___
support mailing list
support@lists.openmoko.org
I'm having the same problem.
Dylan Semler wrote:
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
On Tue, Feb 3, 2009 at 8:20 PM, Michael 'Mickey' Lauer
mic...@openmoko.orgwrote:
Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler:
It seems that my prior FSO wifi configuration no longer works with M5.
Did you request WiFi with the Usage API?
I guess I did not. Now I run
Am Dienstag, den 03.02.2009, 22:13 -0600 schrieb Dylan Semler:
On Tue, Feb 3, 2009 at 8:20 PM, Michael 'Mickey' Lauer
mic...@openmoko.org wrote:
Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler:
It seems that my prior FSO wifi configuration no longer
works
25 matches
Mail list logo