Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 fixing. Messing around with modprobe commands is too cumbersome on such a device, slightly more tolerable on PCs that have real keyboards. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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. I usually run wpa_supplicant. Failing that, I connect to WEP networks using iwlist iwconfig commands directly. Even these low-level tools fails most of the time. Occationally iwlist eth0 scan will work, but repeat the command and eth0 suddenly doesn't support scanning. And of course it won't ever connect to any access point. Similiarly, iwconfig may claim there is no support for setting the essid. Having low-level stuff like iwconfig fail is what makes me suspect a kernel problem. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 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 most of the time. Occationally iwlist eth0 scan will work, but repeat the command and eth0 suddenly doesn't support scanning. And of course it won't ever connect to any access point. Similiarly, iwconfig may claim there is no support for setting the essid. Having low-level stuff like iwconfig fail is what makes me suspect a kernel problem. I may confirm this, I got unexpected wow events (it was already reported), playing with enabling/disabling wifi in FSO after a bit put the wifi chip in an unusable state with a strange framework log error (similiar to expecting power set to 0 but failed), when this happens the command iwconfig eth0 power off crashes and the kernel oops. Other problems with wpa roaming mode that seems to not work, wpa_action is missing, wpa_cli does not reports all connect/disconnect errors and so on. 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. The network nightmare :) Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 most of the time. Occationally iwlist eth0 scan will work, but repeat the command and eth0 suddenly doesn't support scanning. And of course it won't ever connect to any access point. Similiarly, iwconfig may claim there is no support for setting the essid. Having low-level stuff like iwconfig fail is what makes me suspect a kernel problem. The low-level tools even fail on open and Mac filtered networks, I'm not finding any bug reports on SHR's bug tracking system but I may upgrade my phone today and test with the latest kernel and everything, if no one has already tried that. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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. I have not tried bluetooth networking before, but I have no problems with USB networking with this kernel, so there is hope! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
-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 Jimerson wrote: | 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 /etc/network/interfaces so that eth0 uses wpa_supplicant, which I have the file setup with the APs and everything, and when I try and ifup eth0 it goes though the configurations but stops at a "No lease failing" error. I have been at this for a while trying to get it to work and all my attempts have failed. If anyone has any kind of suggestion, or if they have had this problem with this version of SHR-Testing please reply, I getting desperate and will try anything to get it to work. | | - | | ___ | Openmoko community mailing list | community@lists.openmoko.org | http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkn2/HUACgkQvuFuLCp9giBV0QCgsEYQCCY3HQnZkQOiSEhrtosy BKQAnA3bhCWCKiHGJ8KPs+OT4JWMA48f =LzHl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 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 most of the time. Occationally iwlist eth0 scan will work, but repeat the command and eth0 suddenly doesn't support scanning. And of course it won't ever connect to any access point. Similiarly, iwconfig may claim there is no support for setting the essid. 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. solar.george 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: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 it. 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 most of the time. Occationally iwlist eth0 scan will work, but repeat the command and eth0 suddenly doesn't support scanning. And of course it won't ever connect to any access point. Similiarly, iwconfig may claim there is no support for setting the essid. 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 tried that once, too, which resulted in a kernel panic. The funny thing was that I was in the middle of a phone call, which went on nevertheless until the other side hung up. Smartphones are interesting devices :D solar.george Regards, Konstantin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
-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 it. i'd recommend knjmokowifi also for managing connections, it works very nicely Yeah, for me it's the best network manager ever created for FR ;) - -- Francesco de Virgilio *Ubuntu-it Member and Wiki Editor* mailto:frad...@ubuntu-it.org http://wiki.ubuntu-it.org/FrancescoDeVirgilio *Wikimedia projects contributor* http://en.wikipedia.org/wiki/User:Fradeve11 *OpenStreetMap Mapper* http://www.openstreetmap.org/user/Fradeve11 *Blog* http://fradeve.netsons.org Love - Peace - Freedom - Free Software GPG 0x6482E056 (FP B996 A12C BD52 2A9B CDD3 812D 462D 93B0 6482 E056) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3kgcACgkQRi2TsGSC4FbdEgCgiIPe6SPES7zjr+nn/kZp88hE ROAAoKU92L1AcwzUMemvAQ6LrOh1RoBz =Adl7 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 connect to any AP. I have set up the /etc/network/interfaces so that eth0 uses wpa_supplicant, which I have the file setup with the APs and everything, and when I try and ifup eth0 it goes though the configurations but stops at a No lease failing error. I have been at this for a while trying to get it to work and all my attempts have failed. If anyone has any kind of suggestion, or if they have had this problem with this version of SHR-Testing please reply, I getting desperate and will try anything to get it to work. I solved at least the no lease problem hacking a bit /etc/udev/scripts/network.sh, basically when eth0 is added it launches wpa_supplicant with -W (wait for wpa_cli) instead of ifup, after launches wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh, the last is a script called when some event happens (CONNECT/DISCONNECT), on CONNECT it launches udhcpc, and as eth0 is already associated and authenticated I finally get a lease. I think this may be obtained using wpa-roam too in a more elegant way, but it failed and I'm a bit lazy to read an incomplete file set. An issue is that power cycling the AP resulted in kernel reporting ar6000 disconnected/connected but wpa_cli was not notified, after that the freerunner continued to stay connected but I do not know if moving to another configured network will notify a new association and a new IP or I have to disable/reenable wifi. This works starting/stopping wifi from shr-settings too without the need of launch mofi. I toggled wifi several times and it worked on a wpa-psk network without problems, so I *suppose* that udhcpc when launched with the eth0 not associated creates problems. Tomorrow I'll try with the wpa2-enterprise network and report. Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 /etc/network/interfaces so that eth0 uses wpa_supplicant, which I have the file setup with the APs and everything, and when I try and ifup eth0 it goes though the configurations but stops at a No lease failing error. I have been at this for a while trying to get it to work and all my attempts have failed. If anyone has any kind of suggestion, or if they have had this problem with this version of SHR-Testing please reply, I getting desperate and will try anything to get it to work. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 was no one-night-stand with me and eth0! But your troubles make me worry! Hope anyone can help! Matthias Adam Jimerson schrieb: 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 /etc/network/interfaces so that eth0 uses wpa_supplicant, which I have the file setup with the APs and everything, and when I try and ifup eth0 it goes though the configurations but stops at a No lease failing error. I have been at this for a while trying to get it to work and all my attempts have failed. If anyone has any kind of suggestion, or if they have had this problem with this version of SHR-Testing please reply, I getting desperate and will try anything to get it to work. ___ 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: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 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 was no one-night-stand with me and eth0! But your troubles make me worry! Hope anyone can help! Matthias Adam Jimerson schrieb: 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 /etc/network/interfaces so that eth0 uses wpa_supplicant, which I have the file setup with the APs and everything, and when I try and ifup eth0 it goes though the configurations but stops at a No lease failing error. I have been at this for a while trying to get it to work and all my attempts have failed. If anyone has any kind of suggestion, or if they have had this problem with this version of SHR-Testing please reply, I getting desperate and will try anything to get it to work. ___ 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: [SHR-Testing] Wireless Frustration (was: Re: [SHR-Testing] /etc/network/interfaces edit question)
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 very nicely ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
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 through /var r...@om-gta02 ~ $ grep -lr wlan /var grep: /var/volatile/tmp/enlightenment-root/disp-localhost:0.0-1443|0: No such device or address grep: /var/volatile/tmp/.X11-unix/X0: No such device or address grep: /var/volatile/run/wpa_supplicant/eth0: No such device or address grep: /var/volatile/run/sdp: No such device or address grep: /var/volatile/run/avahi-daemon/socket: No such device or address grep: /var/volatile/run/dbus/system_bus_socket: No such device or address /var/volatile/run/ifstate and maybe a strings /boot/vmlinuz | grep wlan I have have in /boot is append-GTA02 uImage uImage-2.6.29-rc3 uImage-GTA02.bin 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 boot param. It seems that my wireless card is eth0 already, but it just isn't wanting to work. I don't remember what I did but I managed to get my freerunner to do a scan on eth0 and work it just wasn't able to connect (all the APs it found are mac filtered and I didn't request to have its mac added yet) but when I am at home where I know it is able to connect (I was able to use wireless before I upgraded SHR-testing) it can't or I get a device not found. All attempts to work with wlan0 gives me a device not found error no matter what, so further work on that is pointless. 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: [SHR-Testing] /etc/network/interfaces edit question
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 # Wired or wireless interfaces iface eth0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf iface eth1 inet dhcp # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr auto usb0 iface usb0 inet static address 192.168.0.202 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.0.200 up echo nameserver 208.67.222.222 /etc/resolv.conf up echo nameserver 208.67.220.220 /etc/resolv.conf # Bluetooth networking iface bnep0 inet dhcp can someone tell me what I am doing wrong to get wireless working as eth0? On Thu, Apr 23, 2009 at 8:29 PM, Adam Jimerson vend...@gmail.com wrote: 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 wlan0 (even though it is commented out) produces a Interface doesn't support scanning so it seems that I don't have eth0 correctly configured for wireless. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
/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 that makes the interfaces. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
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 udev.rules I checked them but I didn't see anything that looked like it configured network devices, then again it doesn't help that I don't know what I am looking for. On Fri, Apr 24, 2009 at 10:11 AM, arne anka openm...@ginguppin.de wrote: /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 that makes the interfaces. ___ 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: [SHR-Testing] /etc/network/interfaces edit question
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/udev.rules:SUBSYSTEM==aoe, KERNEL==discover, NAME=etherd/%k /etc/udev/rules.d/udev.rules:SUBSYSTEM==aoe, KERNEL==err, NAME=etherd/%k /etc/udev/rules.d/udev.rules:SUBSYSTEM==aoe, KERNEL==interfaces, NAME=etherd/%k /etc/udev/rules.d/udev.rules:SUBSYSTEM==aoe, KERNEL==revalidate, NAME=etherd/%k On Fri, Apr 24, 2009 at 10:42 AM, arne anka openm...@ginguppin.de wrote: since you started a new thread w/o sufficiently quoting or explaining your issue, i am not sure, if the name you _have_ is wlan0 or ethX (where X != 0). in either case my first attempt would be to grep through /etc/udev/ for the static part (ie wlan or eth): grep -r wlan /etc/udev/ and if something turnes up to have a lokk at the line in question. f ex the rule mentioned reads SUBSYSTEM==net, ACTION==add, DRIVERS==?*, ATTR{address}==00:1a:a0:a0:f8:18, ATTR{type}==1, KERNEL==eth*, NAME=eth0 ATTR(address) denotes the mac address. ___ 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: [SHR-Testing] /etc/network/interfaces edit question
/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 be interesting: grep -Ir wlan /etc/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
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?) modinf modulename would be interesting. and the, grepping /etc for wlan would be interesting: grep -Ir wlan /etc/ As far as I know the driver is built-in the kernel as for grepping /etc for wlan this is all it get /etc/network/interfaces /etc/network/if-pre-up.d/wireless-tools ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
/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 boot param. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
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
Re: [SHR-Testing] /etc/network/interfaces edit question
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 list then playing with it again, but now it doesn't want to grab an IP from the DHCP server. It may have something to do with the fact that I have two networks in the wpa_supplicant.conf and my freerunner is able to detect both, there priority levels are a bit off one is at 100 and the other is at 98 I'm sure this may be causing this problem. 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: [SHR-Testing] /etc/network/interfaces edit question
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 http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Testing] /etc/network/interfaces edit question
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 wlan0 (even though it is commented out) produces a Interface doesn't support scanning so it seems that I don't have eth0 correctly configured for wireless. 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
[SHR-Testing] /etc/network/interfaces edit question
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 out what I am doing wrong. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community