George Brooke wrote:
Having low-level stuff like iwconfig fail is what makes me suspect a
kernel problem.
Try rmmod a6000 (I think thats the correct module) them modprobing it again
as
that some times works for me.
I might try. But if it helps, then it is still a kernel bug that needs
Adam Jimerson wrote:
Well it is nice to see that I am not the only person with this problem,
for me Mofi doesn't even load, I am installing the one from opkg.org
http://opkg.org to see if I have any better luck with it.
I have trouble with wifi in SHR testing too. I suspect a kernel problem.
2009/4/28 Helge Hafting helge.haft...@hist.no:
Adam Jimerson wrote:
Well it is nice to see that I am not the only person with this problem,
for me Mofi doesn't even load, I am installing the one from opkg.org
http://opkg.org to see if I have any better luck with it.
I have trouble with wifi
On Tue, Apr 28, 2009 at 7:49 AM, Helge Hafting helge.haft...@hist.nowrote:
I have trouble with wifi in SHR testing too. I suspect a kernel problem.
I usually run wpa_supplicant. Failing that, I connect to WEP networks
using iwlist iwconfig commands directly. Even these low-level tools
fails
On Tue, Apr 28, 2009 at 8:15 AM, Nicola Mfb nicola@gmail.com wrote:
I ignored all these issues as before I used mainly BT networking and
USB, they works well with recent kernels, with olders BT stopped to
work after suspend/resume and with USB my laptop was often not able to
enumerate.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently, I playing around with Android beta 6 (from Koolu). Wireless
does not work there either.
Sometimes I can the FreeRunner is able to scan for networks, sometimes
not.
I was never able to get a connection with an access point.
Adam
On Tuesday 28 April 2009 12:49:44 Helge Hafting wrote:
Adam Jimerson wrote:
Well it is nice to see that I am not the only person with this problem,
for me Mofi doesn't even load, I am installing the one from opkg.org
http://opkg.org to see if I have any better luck with it.
I have trouble
George Brooke schrieb:
On Tuesday 28 April 2009 12:49:44 Helge Hafting wrote:
Adam Jimerson wrote:
Well it is nice to see that I am not the only person with this problem,
for me Mofi doesn't even load, I am installing the one from opkg.org
http://opkg.org to see if I have any better luck with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Paulson ha scritto:
2009/4/28 Adam Jimerson vend...@gmail.com:
Well it is nice to see that I am not the only person with this problem, for
me Mofi doesn't even load, I am installing the one from opkg.org to see if I
have any better luck with
2009/4/27 Adam Jimerson vend...@gmail.com:
I am still trying to get my wireless to work on the 4/16 release of
SHR-Testing, I can get a scan to work on eth0 every now and then and the
rest of the time I get a device does not support scanning error. No
matter if I can scan or not eth0 will not
I am still trying to get my wireless to work on the 4/16 release of
SHR-Testing, I can get a scan to work on eth0 every now and then and the
rest of the time I get a device does not support scanning error. No
matter if I can scan or not eth0 will not connect to any AP. I have set up
the
I had the same problems with the same image. But today, when i tried to
connect to the network of my university, it surprisingly worked.
I did the following:
powered up the device with shr-settings and started mofi.py in the terminal.
It worked fine until i switched the device off.
So, I hope that
Well it is nice to see that I am not the only person with this problem, for
me Mofi doesn't even load, I am installing the one from opkg.org to see if I
have any better luck with it.
On Mon, Apr 27, 2009 at 2:43 PM, matthias matthiasfels...@web.de wrote:
I had the same problems with the same
2009/4/28 Adam Jimerson vend...@gmail.com:
Well it is nice to see that I am not the only person with this problem, for
me Mofi doesn't even load, I am installing the one from opkg.org to see if I
have any better luck with it.
i'd recommend knjmokowifi also for managing connections, it works
On Friday 24 April 2009 11:15:52 am arne anka wrote:
/etc/network/if-pre-up.d/wireless-tools
containing?
It is a bash script, to be nice to the list I posted the contents in pastebin
here http://pastebin.com/m6d6284f0
mine on my desktop does nowhere mention the string wlan.
do a grep
Here is what I have for my interfaces configuration
/etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# Wireless interfaces
#iface wlan0 inet dhcp
#wireless_mode managed
#wireless_essid any
iface atml0 inet dhcp
#
/etc/network/interfaces has nothing, repeat, nothing to do with the
_naming_ of the interfaces!
it kicks in onyl after the interfaces are created already.
as i wrote already in my first answer: check the udev rules!
here on my desktop debian it is
/etc/udev/rules.d/70-persistent-net.rules
I don't have a udev rule like that here are the udev rules that I have
50-udev-default.rules 95-udev-late.rules
60-persistent-input.rules local.rules
60-persistent-storage-tape.rules permissions.rules
60-persistent-storage.rules run.rules
80-drivers.rules
Funny according to gmail it is the same thread, anyways when I did the grep
for wlan nothing was returned but eth returned this
r...@om-gta02 /etc/udev/rules.d $ grep -r eth /etc/udev/
/etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM==aoe,
NAME=etherd/%k, GROUP=disk
/etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM==aoe,
NAME=etherd/%k, GROUP=disk
well, that's not we are looking for.
next step: ist the driver built-in or loaded as module?
in case it is a module (which name?)
modinf modulename
would be interesting.
and the, grepping /etc for wlan would
On Fri, Apr 24, 2009 at 10:58 AM, arne anka openm...@ginguppin.de wrote:
/etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM==aoe,
NAME=etherd/%k, GROUP=disk
well, that's not we are looking for.
next step: ist the driver built-in or loaded as module?
in case it is a module (which name?)
/etc/network/if-pre-up.d/wireless-tools
containing? mine on my desktop does nowhere mention the string wlan.
do a grep through /var and maybe a
strings /boot/vmlinuz | grep wlan
if it is built-in and no udev rule exists, the name would be hardcoded and
can, if at all, only be overridden by a
check udev, i got a rule making eth0 eth1 when eth0 already existed --
dunno what genius created that one.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Thursday 23 April 2009 05:28:31 am arne anka wrote:
check udev, i got a rule making eth0 eth1 when eth0 already existed --
dunno what genius created that one.
Well it seems I managed to solve the device problem, after spending hours
messing with it breaking down sending a message to this
you should be able, to determine the ap associated to by using the iwutils.
does it also happen, when you execute the dhclient manually?
___
Openmoko community mailing list
community@lists.openmoko.org
On Thursday 23 April 2009 07:29:46 am arne anka wrote:
you should be able, to determine the ap associated to by using the iwutils.
does it also happen, when you execute the dhclient manually?
It seems something is not right in my network interfaces is not right, iwlist
scan on both eth0 and
Besides removing, or commenting out, the wlan0 configuration what else is
needed to switch eth0 back to being for the wireless instead of wireless?
After setting up wpa_supplicant and making the change I get an error about
how eth0 No such device, I can post any needed config files to help figure
27 matches
Mail list logo
