From: vwyodapink <vwy...@gm...> - 2010-05-17 19:32:07
|
equip: Overo Fire Summit expansion board Connected by console on board V Jan 13 2010 SD Card has most current down-loadable desktop version >From searching through here on the site I have been able to get my over fire to connect with wifi to my router with no key. Has a ipv6 address router shows its connected, but I cant ping or update or anything. What could be causing this? I have also tried loading the most current desktop image on my SD card and have gotten to the same end result everything appears to be connected but it appears as if something is blocking it. It also shows that the lease is failing but it is getting an IP. Let me know if I can post any other particular info to help diagnose. Though it will not stay connected for very long and if I do ifdown wlan0 then ifup wlan0 it will occasionally connected again to the router but then it will still not ping anything nor will it stay connected. Here are the only things I can find that seem relevant U-Boot 2009.11 (Jan 13 2010 - 07:00:40) OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 256 MB NAND: 256 MiB *** Warning - bad CRC or NAND, using default environment though from what I found in one post someone said this OK, is that correct? And here is wifi related: Starting udev udev: starting version 141 ads7846 spi1.0: touchscreen, irq 274 ads7846 spi1.0: no device detected, test read result was 0x00000000 lib80211: common routines for IEEE802.11 drivers libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin Remounting root file system... NET: Registered protocol family 10 libertas: 00:50:43:02:fe:01, fw 9.70.3p24, cap 0x0000030b libertas: wlan0: Marvell WLAN 802.11 adapter ALSA: Restoring mixer settings... Configuring network interfaces... ADDRCONF(NETDEV_UP): wlan0: link is not ready ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending select for 192.168.3.10... Sending select for 192.168.3.10... Sending select for 192.168.3.10... No lease, failing done. Starting portmap daemon: portmap. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.ip_forward = 1 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting OpenBSD Secure Shell server: sshd done. Starting advanced power management daemon: No APM support in kernel (failed.) Starting ntpd: done Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: CSR build ID 0x0C-0x5C Device setup complete ttyS1 bluetoothd hid2hci rfcomm. Waiting for connection on channel 1 Starting Network connection manager daemon: NetworkManager. Starting PVR ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready PVRSRV_PIXEL_FORMAT_RGB565 Starting GPE display manager: gpe-dm Thanks for any help on this -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28581791.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Bernhard Wörndl-A. <bw...@xd...> - 2010-05-17 19:37:43
|
Hey =) If says - No lease, failing no correct IP has been obtained, you can try to set the IP manually - ifconfig wlan0 192.168.x.x There actually was a discussion about the DHCP failing in the lastest versions. You might be connected, and just not get a correct IP to work with. Regards *Bernhard Wörndl-Aichriedler* Am 17.05.2010 21:32, schrieb vwyodapink: > equip: > Overo Fire > Summit expansion board > Connected by console > on board V Jan 13 2010 > SD Card has most current down-loadable desktop version > > > > From searching through here on the site I have been able to get my over fire > to connect with wifi to my router with no key. Has a ipv6 address router > shows its connected, but I cant ping or update or anything. What could be > causing this? > > I have also tried loading the most current desktop image on my SD card and > have gotten to the same end result everything appears to be connected but it > appears as if something is blocking it. It also shows that the lease is > failing but it is getting an IP. Let me know if I can post any other > particular info to help diagnose. > > Though it will not stay connected for very long and if I do ifdown wlan0 > then ifup wlan0 it will occasionally connected again to the router but then > it will still not ping anything nor will it stay connected. > > Here are the only things I can find that seem relevant > > U-Boot 2009.11 (Jan 13 2010 - 07:00:40) > > OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz > Gumstix Overo board + LPDDR/NAND > I2C: ready > DRAM: 256 MB > NAND: 256 MiB > *** Warning - bad CRC or NAND, using default environment > > though from what I found in one post someone said this OK, is that correct? > > And here is wifi related: > Starting udev > udev: starting version 141 > ads7846 spi1.0: touchscreen, irq 274 > ads7846 spi1.0: no device detected, test read result was 0x00000000 > lib80211: common routines for IEEE802.11 drivers > libertas_sdio: Libertas SDIO driver > libertas_sdio: Copyright Pierre Ossman > libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin > libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin > Remounting root file system... > NET: Registered protocol family 10 > libertas: 00:50:43:02:fe:01, fw 9.70.3p24, cap 0x0000030b > libertas: wlan0: Marvell WLAN 802.11 adapter > ALSA: Restoring mixer settings... > Configuring network interfaces... ADDRCONF(NETDEV_UP): wlan0: link is not > ready > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > udhcpc (v1.13.2) started > run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 > Sending discover... > Sending select for 192.168.3.10... > Sending select for 192.168.3.10... > Sending select for 192.168.3.10... > No lease, failing > done. > Starting portmap daemon: portmap. > net.ipv4.conf.default.rp_filter = 1 > net.ipv4.conf.all.rp_filter = 1 > net.ipv4.ip_forward = 1 > Turning echo off on /dev/ttyS1 > INIT: Entering runlevel: 5 > Starting system message bus: dbus. > Starting Hardware abstraction layer hald > Starting OpenBSD Secure Shell server: sshd > done. > Starting advanced power management daemon: No APM support in kernel > (failed.) > Starting ntpd: done > Starting syslogd/klogd: done > * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon > [ ok ] > Starting Bluetooth subsystem: > CSR build ID 0x0C-0x5C > Device setup complete > ttyS1 bluetoothd hid2hci rfcomm. > Waiting for connection on channel 1 > Starting Network connection manager daemon: NetworkManager. > Starting PVR > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > PVRSRV_PIXEL_FORMAT_RGB565 > Starting GPE display manager: gpe-dm > > > > > > Thanks for any help on this > > > > |
From: vwyodapink <vwy...@gm...> - 2010-05-17 20:01:57
|
I tried what you suggested and it gave me the IP4 address and I am able to ping the router. The router itself has no security on it right now what so ever. Trying to ping my cable modem I get network unreachable. So its not leaving my router now. I double checked to make sure that there is nothing on the routers end that could block it, just to be sure and still with the onboard nand image and the latest desktop image give me the same results of getting to ping the router but not being able to leave the router. Thanks for the help so far. Here are the results: overo login: root root@overo:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2328 (2.2 KiB) TX bytes:2328 (2.2 KiB) wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) root@overo:~# ifconfig wlan0 192.168.3.5 root@overo:~# ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 inet addr:192.168.3.5 Bcast:192.168.3.255 Mask:255.255.255.0 inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:4231 (4.1 KiB) root@overo:~# ping 192.168.3.1 PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data. 64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=8.85 ms 64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=3.14 ms 64 bytes from 192.168.3.1: icmp_seq=3 ttl=64 time=2.41 ms 64 bytes from 192.168.3.1: icmp_seq=4 ttl=64 time=2.71 ms ^C --- 192.168.3.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 2.411/4.280/8.850/2.651 ms root@overo:~# ping 192.168.0.1 connect: Network is unreachable root@overo:~# Bernhard Wörndl-Aichriedler wrote: > > Hey =) > > If says - > > No lease, failing > > no correct IP has been obtained, you can try to set the IP manually - > ifconfig wlan0 192.168.x.x > > There actually was a discussion about the DHCP failing in the lastest > versions. > You might be connected, and just not get a correct IP to work with. > > > Regards > > *Bernhard Wörndl-Aichriedler* > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28588087.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Bernhard Wörndl-A. <bw...@xd...> - 2010-05-17 20:08:12
|
On Mon, May 3, 2010 at 9:34 PM, roystonvasey<mik...@ma...> wrote: > I've found the problem with dhclient. > It is unable to write the leases file to /var/lib/dhcp/dhclient.leases > There is a directory /var/lib/dhcp3/ which i assume is for the leases. > I created a directory/var/lib/dhcp/ and all works fine. Regards *Bernhard Wörndl-Aichriedler* Am 17.05.2010 22:06, schrieb Bernhard Wörndl-Aichriedler: > Hey again! > > As far as good =) The problem with your cable modem is just because > you haven't set a default gateway. > Bot now we know that it's nothing "big". > > I'll have a look for the path to fix the dhcp problem. > > > Regards > > *Bernhard Wörndl-Aichriedler* > > Am 17.05.2010 22:01, schrieb vwyodapink: >> I tried what you suggested and it gave me the IP4 address and I am able to >> ping the router. The router itself has no security on it right now what so >> ever. Trying to ping my cable modem I get network unreachable. So its not >> leaving my router now. I double checked to make sure that there is nothing >> on the routers end that could block it, just to be sure and still with the >> onboard nand image and the latest desktop image give me the same results of >> getting to ping the router but not being able to leave the router. Thanks >> for the help so far. >> >> Here are the results: >> overo login: root >> root@overo:~# ifconfig >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:36 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:2328 (2.2 KiB) TX bytes:2328 (2.2 KiB) >> >> wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 >> inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) >> >> root@overo:~# ifconfig wlan0 192.168.3.5 >> root@overo:~# ifconfig wlan0 >> wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 >> inet addr:192.168.3.5 Bcast:192.168.3.255 Mask:255.255.255.0 >> inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:4231 (4.1 KiB) >> >> root@overo:~# ping 192.168.3.1 >> PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data. >> 64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=8.85 ms >> 64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=3.14 ms >> 64 bytes from 192.168.3.1: icmp_seq=3 ttl=64 time=2.41 ms >> 64 bytes from 192.168.3.1: icmp_seq=4 ttl=64 time=2.71 ms >> ^C >> --- 192.168.3.1 ping statistics --- >> 4 packets transmitted, 4 received, 0% packet loss, time 3004ms >> rtt min/avg/max/mdev = 2.411/4.280/8.850/2.651 ms >> root@overo:~# ping 192.168.0.1 >> connect: Network is unreachable >> root@overo:~# >> >> >> >> Bernhard Wörndl-Aichriedler wrote: >> >>> Hey =) >>> >>> If says - >>> >>> No lease, failing >>> >>> no correct IP has been obtained, you can try to set the IP manually - >>> ifconfig wlan0 192.168.x.x >>> >>> There actually was a discussion about the DHCP failing in the lastest >>> versions. >>> You might be connected, and just not get a correct IP to work with. >>> >>> >>> Regards >>> >>> *Bernhard Wörndl-Aichriedler* >>> >>> >> > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Bernhard Wörndl-A. <bw...@xd...> - 2010-05-17 20:49:16
|
Hey! Have you tried to remove the network manager? You can just remove it's init script from /etc/init.d and test the result? As i think back, Network Manager troubled me to... Regards *Bernhard Wörndl-Aichriedler* Am 17.05.2010 22:30, schrieb vwyodapink: > For me on the onboard nand that I was just shipped with I have the same exact > setup as you and did as you said but that did not work for me. I would still > have to do ifconfig wlan0 192.168.x.x to give it an ipv4 address and I get > the adress and can ping the router but it does not stay connected for very > long after and I can not ping past the router still. I noticed while booting > though that it says it gets and address and everything but not true once you > log in. It kind of seems like Network Manager is causing some issue because > as you will it obtains the address and then goes through a few more steps > then Network Manager starts and it then once you log in no address. Also > looking in the dhcp3 folder the leases that are in there are for eth0 and I > do not see anything for wlan0 > > lib80211: common routines for IEEE802.11 drivers > libertas_sdio: Libertas SDIO driver > libertas_sdio: Copyright Pierre Ossman > libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin > libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin > Remounting root file system... > NET: Registered protocol family 10 > libertas: 00:50:43:02:fe:01, fw 9.70.3p24, cap 0x0000030b > libertas: wlan0: Marvell WLAN 802.11 adapter > ALSA: Restoring mixer settings... > Configuring network interfaces... ADDRCONF(NETDEV_UP): wlan0: link is not > ready > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > udhcpc (v1.13.2) started > run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 > Sending discover... > Sending discover... > Sending select for 192.168.3.13... > libertas: problem fetching packet from firmware > Lease of 192.168.3.13 obtained, lease time 86400 > run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 > adding dns 192.168.3.1 > done. > Starting portmap daemon: portmap. > net.ipv4.conf.default.rp_filter = 1 > net.ipv4.conf.all.rp_filter = 1 > net.ipv4.ip_forward = 1 > Turning echo off on /dev/ttyS1 > INIT: Entering runlevel: 5 > Starting system message bus: dbus. > Starting Hardware abstraction layer hald > Starting OpenBSD Secure Shell server: sshd > done. > Starting advanced power management daemon: No APM support in kernel > (failed.) > Starting ntpd: done > Starting syslogd/klogd: done > * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon > [ ok ] > Starting Bluetooth subsystem: > CSR build ID 0x0C-0x5C > Device setup complete > ttyS1 bluetoothd hid2hci rfcomm. > Waiting for connection on channel 1 > Starting Network connection manager daemon: NetworkManager. > Starting PVR > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > PVRSRV_PIXEL_FORMAT_RGB565 > Starting GPE display manager: gpe-dm > > > Now with the latest desktop version on my SD card different results. When I > went to the /var/lib folder there was already a dhcp folder but no dhcp3 > folder in there. > > Thanks for such quick responses and helping me debug this. Very much > appreciated I havent felt like such a linux noob in a long time until I just > got my fire :P > > > > > > > > Bernhard Wörndl-Aichriedler wrote: > >> On Mon, May 3, 2010 at 9:34 PM, roystonvasey<mik...@ma...> >> wrote: >> >> >> >>> I've found the problem with dhclient. >>> It is unable to write the leases file to /var/lib/dhcp/dhclient.leases >>> There is a directory /var/lib/dhcp3/ which i assume is for the leases. >>> I created a directory/var/lib/dhcp/ and all works fine. >>> >> >> >> >> Regards >> >> *Bernhard Wörndl-Aichriedler* >> >> >> >> > |
From: vwyodapink <vwy...@gm...> - 2010-05-17 21:06:27
|
Here is another error that is coming up for me WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x140/0x220() NETDEV WATCHDOG: wlan0 (libertas_sdio): transmit queue 0 timed out Modules linked in: bufferclass_ti omaplfb pvrsrvkm ipv6 libertas_sdio libertas lib80211 ads7846 [<c00f778c>] (unwind_backtrace+0x0/0xdc) from [<c0119e68>] (warn_slowpath_common+0x4c/0x80) [<c0119e68>] (warn_slowpath_common+0x4c/0x80) from [<c0119ed8>] (warn_slowpath_fmt+0x28/0x38) [<c0119ed8>] (warn_slowpath_fmt+0x28/0x38) from [<c03de09c>] (dev_watchdog+0x140/0x220) [<c03de09c>] (dev_watchdog+0x140/0x220) from [<c0122b88>] (run_timer_softirq+0x188/0x204) [<c0122b88>] (run_timer_softirq+0x188/0x204) from [<c011edb4>] (__do_softirq+0x78/0x100) [<c011edb4>] (__do_softirq+0x78/0x100) from [<c011ee7c>] (irq_exit+0x40/0x94) [<c011ee7c>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2af4>] (__irq_svc+0x34/0x80) Exception stack(0xc061bf70 to 0xc061bfb8) bf60: 00000000 40000013 40000013 c065a668 bf80: c061a000 c061df50 c061dd88 c0659c0c 8002aa64 411fc083 0000001f 00000000 bfa0: c062c3f0 c061bfbc c0101f40 c0101f78 60000013 ffffffff [<c00f2af4>] (__irq_svc+0x34/0x80) from [<c0101f78>] (omap3_pm_idle+0x4c/0x50) [<c0101f78>] (omap3_pm_idle+0x4c/0x50) from [<00000000>] (0x0) ---[ end trace 7e2d78c4b449b8ee ]--- libertas: tx watch dog timeout deleting NetworkManager from /etc/init.d did nothing for me though seems to stay connected longer now though. Bernhard Wörndl-Aichriedler wrote: > > Hey! > > Have you tried to remove the network manager? > You can just remove it's init script from /etc/init.d and test the result? > > As i think back, Network Manager troubled me to... > > Regards > > *Bernhard Wörndl-Aichriedler* > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28588858.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: vwyodapink <vwy...@gm...> - 2010-05-18 19:20:49
|
Just wondering if anyone else has any ideas? Or if someone has a working method for getting wifi to work on the Overo Fire? I have been trying for a few days now and I still can not get it past my router with no security though what was done above has helped some I still cant get to the net. -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28599698.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Victhor <vic...@gm...> - 2010-05-18 19:36:21
|
Try this script I found on the BackTrack forums, while it's says it's for WPA networks, it should work just as well on open networks, as it has an option to do that. http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 Also, if you have a GUI on your device, try installing the NetworkManager applet, it works for me :) > Just wondering if anyone else has any ideas? Or if someone has a working > method for getting wifi to work on the Overo Fire? I have been trying for a > few days now and I still can not get it past my router with no security > though what was done above has helped some I still cant get to the net. |
From: vwyodapink <vwy...@gm...> - 2010-05-18 22:50:46
|
I tried that script and have had no more luck than before but a new message came up that I have not seen before ADDRCONF(NETDEV_CHANGE): wlan0: then I did ifdown wlan0 and got this cat: /var/run/udhcpc.wlan0.pid: No such file or directory I have no GUI as of yet, when I try and run X on the latest desktop version listed for DL it does not run and I read on the OE wiki that more packages need to be DL'd to make it work. The wifi on my fire is the only way I have to connect to the net. If you have the fire do you happen to remember what specifically you had to do to get the wifi up? I have tried a ton with the listed directions and various ways online from searching and while I can get as far as the router never gets out of the router. No other computers have this issue on the network. Victhor Foster wrote: > > Try this script I found on the BackTrack forums, while it's says it's > for WPA networks, it should work just as well on open networks, as it > has an option to do that. > http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 > Also, if you have a GUI on your device, try installing the > NetworkManager applet, it works for me :) >> Just wondering if anyone else has any ideas? Or if someone has a working >> method for getting wifi to work on the Overo Fire? I have been trying for >> a >> few days now and I still can not get it past my router with no security >> though what was done above has helped some I still cant get to the net. > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28602348.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: vwyodapink <vwy...@gm...> - 2010-05-19 05:39:42
|
Well just to let anyone know who may have this issue as well I am not 100% solved but I am actually getting to the net now. Here is what I did. edit /etc/sysctl.conf edit dhclient.conf edit network/interfaces right now its working on a no encryption network. once I rebooted it was on the net and I was able to ping google and different devices on the network. Now here is whats happening. I right now am only able to use the console until I can figure out the hdmi issue I have but though its connected it will at random times even while I am typing spit out a watchdog error libertas: tx watch dog timeout also when I run iwconfig the results make no sense root@overo:~# iwconfig lo no wireless extensions. wlan0 IEEE 802.11b/g ESSID:"dwight" Mode:Managed Frequency:2.412 GHz Access Point: 00:1F:33:ED:E0:8E Bit Rate:54 Mb/s Tx-Power=13 dBm Retry short limit:8 RTS thr=2347 B Fragment thr=2346 B Encryption key:off Power Management:off Link Quality=85/100 Signal level=-55 dBm Noise level=-90 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:896 Invalid misc:228072 Missed beacon:0 root@overo:~# libertas: tx watch dog timeout does not list it having an actual ip address neither a ipv4 nor ipv6 address. but if I run dhclient it shows what address its bound to. root@overo:~# dhclient Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/wlan0/00:50:43:02:fe:01 Sending on LPF/wlan0/00:50:43:02:fe:01 Sending on Socket/fallback DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.17 -- renewal in 34284 seconds. root@overo:~# Not really sure where to look from here but I will keep tinkering until I get it or someone comes up with a better suggestion. Thanks for every ones help so far. vwyodapink wrote: > > I tried that script and have had no more luck than before but a new > message came up that I have not seen before > ADDRCONF(NETDEV_CHANGE): wlan0: > then I did ifdown wlan0 and got this > cat: /var/run/udhcpc.wlan0.pid: No such file or directory > > I have no GUI as of yet, when I try and run X on the latest desktop > version listed for DL it does not run and I read on the OE wiki that more > packages need to be DL'd to make it work. The wifi on my fire is the only > way I have to connect to the net. > > If you have the fire do you happen to remember what specifically you had > to do to get the wifi up? I have tried a ton with the listed directions > and various ways online from searching and while I can get as far as the > router never gets out of the router. No other computers have this issue on > the network. > > > > > Victhor Foster wrote: >> >> Try this script I found on the BackTrack forums, while it's says it's >> for WPA networks, it should work just as well on open networks, as it >> has an option to do that. >> http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 >> Also, if you have a GUI on your device, try installing the >> NetworkManager applet, it works for me :) >>> Just wondering if anyone else has any ideas? Or if someone has a working >>> method for getting wifi to work on the Overo Fire? I have been trying >>> for a >>> few days now and I still can not get it past my router with no security >>> though what was done above has helped some I still cant get to the net. >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28604326.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: vwyodapink <vwy...@gm...> - 2010-05-19 06:09:11
|
Here is a fresh boot you can see there a few errors while its booting now. This is the May 15th desktop image for DL seems to be if the packets get to large or it starts DLing at to high a speed it complains about the TX error. Hope this might help someone figure out the error here: Rebooting... Restarting system. �tصb�$U @ @ @D��` @ @ Texas Instruments X-Loader 1.4.2 (May 15 2010 - 08:29:16) Reading boot sector Loading u-boot.bin from mmc U-Boot 2009.11 (May 15 2010 - 08:30:32) OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max clock-720Mhz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 256 MB NAND: 256 MiB In: serial Out: serial Err: serial Board revision: 0 No EEPROM on expansion board Die ID #48340004000000000403730511019004 Net: No ethernet found. Hit any key to stop autoboot: 0 mmc1 is available reading boot.scr ** Unable to read "boot.scr" from mmc 0:1 ** reading uImage 3159064 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Angstrom/2.6.33/overo Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3159000 Bytes = 3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.33 (st...@ww...) (gcc version 4.3.3 (GCC) ) #1 Sat May 15 08:39:29 PDT 2010 CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Gumstix Overo Memory policy: ECC disabled, Data cache writeback OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp ) SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 Reserving 12582912 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS2,115200n8 mpurate=500 vram=12M omapfb.mode=dvi:800x600MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 128MB 128MB = 256MB total Memory: 240640k/240916k available, 21228k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB) lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc00f2000 ( 936 kB) .text : 0xc00f2000 - 0xc05f6000 (5136 kB) .data : 0xc061a000 - 0xc0659980 ( 255 kB) Hierarchical RCU implementation. NR_IRQS:402 Clocking rate (Crystal/Core/MPU): 26.0/331/500 MHz Could not get uart4_ick Could not get uart4_fck Reprogramming SDRC clock to 331882352 Hz GPMC revision 5.0 IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP GPIO hardware version 2.5 OMAP clockevent source: GPTIMER1 at 32768 Hz Console: colour dummy device 80x30 Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok devtmpfs: initialized regulator: core version 0.5 NET: Registered protocol family 16 Found NAND on CS0 hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available Switched to new clocking rate (Crystal/Core/MPU): 26.0/500/331 MHz OMAP DMA hardware revision 4.0 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: Initialized TWL4030 USB module regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VDVI: 1800 mV normal standby i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz Advanced Linux Sound Architecture Driver Version 1.0.22.1. Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource 32k_counter musb_hdrc: version 6.0, musb-dma, host, debug=0 musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 2.6.33 musb-hcd usb usb1: SerialNumber: musb_hdrc hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. msgmni has been set to 470 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) OMAP DSS rev 2.0 OMAP DISPC rev 3.0 OMAP VENC rev 2 OMAP DSI rev 1.0 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand.0": 0x000000000000-0x000000080000 : "xloader" 0x000000080000-0x000000240000 : "uboot" 0x000000240000-0x000000280000 : "uboot environment" 0x000000280000-0x000000680000 : "linux" 0x000000680000-0x000010000000 : "rootfs" smsc911x: Driver version 2008-10-21. smsc911x: Driver version 2008-10-21. usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: OMAP-EHCI Host Controller usb usb2: Manufacturer: Linux 2.6.33 ehci_hcd usb usb2: SerialNumber: ehci-omap.0 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) mice: PS/2 mouse device common for all mice twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 i2c /dev entries driver OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec twl4030_wdt twl4030_wdt: Failed to register misc device twl4030_wdt: probe of twl4030_wdt failed with error -16 Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCILL protocol initialized wacom driver registered usbcore: registered new interface driver usbhid usbhid: USB HID core driver usbcore: registered new interface driver snd-usb-audio No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4 overo SoC init asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok ALSA device list: #0: overo (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.14 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 ThumbEE CPU extension supported. Power Management for TI OMAP3. VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 fbcvt: 800x600@60: CVT Name - .480M3-R Console: switching to colour frame buffer device 100x37 regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2010-05-15 13:02:54 UTC (1273928574) Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address 7902 mmcblk0: mmc0:7902 SD08G 7.42 GiB mmcblk0: p1 p2 mmc1: new SDIO card at address 0001 kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing init memory: 936K INIT: version 2.86 booting Please wait: booting... Starting udev udev: starting version 151 Remounting root file system... udevadm settle - timeout of 3 seconds reached, the event queue contains: /sys/devices/platform/ehci-omap.0/usb2/2-0:1.0 (553) /sys/devices/platform/i2c_omap.1/i2c-1/1-0048 (557) /sys/devices/platform/i2c_omap.1/i2c-1/1-0049 (558) /sys/devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_gpio/gpio/gpiochip192 (559) /sys/devices/platform/i2c_omap.1/i2c-1/1-004a (560) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b (561) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.17/regulator/regulator.0 (562) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.18/regulator/regulator.1 (563) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.19/regulator/regulator.2 (564) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.3/regulator/regulator.4 (565) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.5/regulator/regulator.5 (566) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_reg.6/regulator/regulator.3 (567) /sys/devices/platform/i2c_omap.1/i2c-1/1-004b/twl_rtc/rtc/rtc0 (568) /sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:7902 (573) /sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:7902/block/mmcblk0 (574) /sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:7902/block/mmcblk0/mmcblk0p1 (575) /sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:7902/block/mmcblk0/mmcblk0p2 (576) /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc1/mmc1:0001 (578) /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1 (579) /sys/devices/platform/musb_hdrc/usb1/1-0:1.0 (581) /sys/devices/platform/omap2_mcspi.1/spi1.0 (584) /sys/devices/platform/omap2_mcspi.1/spi1.1 (585) lib80211: common routines for IEEE802.11 drivers ads7846 spi1.0: touchscreen, irq 274 ads7846 spi1.0: no device detected, test read result was 0x00000000 libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin libertas: 00:50:43:02:fe:01, fw 9.70.3p24, cap 0x0000030b libertas: wlan0: Marvell WLAN 802.11 adapter Caching udev devnodes Populating dev cachemv: cannot stat `/tmp/uname': No such file or directory NET: Registered protocol family 10 ALSA: Restoring mixer settings... Configuring network interfaces... ADDRCONF(NETDEV_UP): wlan0: link is not ready ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server] [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val] [-sf script-file] [interface] If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhc...@is... mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting. Failed to bring up wlan0. done. Starting portmap daemon: portmap. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 1 net.ipv4.conf.all.log_martians = 1 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting syslog-ng:. Starting OpenBSD Secure Shell server: sshd done. Starting advanced power management daemon: No APM support in kernel (failed.) Starting ntpd: done Starting Samba: smbd nmbd. Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: CSR build ID 0x0C-0x5C Device setup complete ttyS1 bluetoothd hid2hci rfcomm. Waiting for connection on channel 1 Starting Network connection manager daemon: NetworkManager. Starting PVR Usage: insmod filename [args] WARNING: Could not open '/lib/modules/2.6.33/kernel/drivers/gpu/pvr/pvrsrvkm.ko': No such file or directory FATAL: Could not open '/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko': No such file or directory WARNING: Could not open '/lib/modules/2.6.33/kernel/drivers/gpu/pvr/pvrsrvkm.ko': No such file or directory FATAL: Could not open '/lib/modules/2.6.33/kernel/drivers/gpu/pvr/bufferclass_ti.ko': No such file or directory mknod: missing operand after `0' Try `mknod --help' for more information. chmod: cannot access `/dev/pvrsrvkm': No such file or directory cups: started scheduler. Starting GPE display manager: gpe-dm .-------. | | .-. | | |-----.-----.-----.| | .----..-----.-----. | | | __ | ---'| '--.| .-'| | | | | | | | |--- || --'| | | ' | | | | '---'---'--'--'--. |-----''----''--' '-----'-'-'-' -' | '---' The Angstrom Distribution overo ttyS2 Angstrom 2010.4-test-20100513 overo ttyS2 overo login: ------------[ cut here ]------------ WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x140/0x220() NETDEV WATCHDOG: wlan0 (libertas_sdio): transmit queue 0 timed out Modules linked in: ipv6 libertas_sdio libertas ads7846 lib80211 [<c00f778c>] (unwind_backtrace+0x0/0xdc) from [<c0119e68>] (warn_slowpath_common+0x4c/0x80) [<c0119e68>] (warn_slowpath_common+0x4c/0x80) from [<c0119ed8>] (warn_slowpath_fmt+0x28/0x38) [<c0119ed8>] (warn_slowpath_fmt+0x28/0x38) from [<c03de09c>] (dev_watchdog+0x140/0x220) [<c03de09c>] (dev_watchdog+0x140/0x220) from [<c0122b88>] (run_timer_softirq+0x188/0x204) [<c0122b88>] (run_timer_softirq+0x188/0x204) from [<c011edb4>] (__do_softirq+0x78/0x100) [<c011edb4>] (__do_softirq+0x78/0x100) from [<c011ee7c>] (irq_exit+0x40/0x94) [<c011ee7c>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2af4>] (__irq_svc+0x34/0x80) Exception stack(0xc061bf78 to 0xc061bfc0) bf60: 00000000 40000013 bf80: 40000013 c065a668 c061a000 c061df50 c061dd88 c0659c0c 8002aa64 411fc083 bfa0: 0000001f 00000000 c062c3f0 c061bfc0 c0101f40 c00f3e94 60000013 ffffffff [<c00f2af4>] (__irq_svc+0x34/0x80) from [<c00f3e94>] (cpu_idle+0x58/0xa8) [<c00f3e94>] (cpu_idle+0x58/0xa8) from [<c0008950>] (start_kernel+0x250/0x2b4) [<c0008950>] (start_kernel+0x250/0x2b4) from [<80008034>] (0x80008034) ---[ end trace 47fea1308ff35715 ]--- libertas: tx watch dog timeout vwyodapink wrote: > > Well just to let anyone know who may have this issue as well I am not 100% > solved but I am actually getting to the net now. Here is what I did. > edit /etc/sysctl.conf > edit dhclient.conf > edit network/interfaces right now its working on a no encryption network. > once I rebooted it was on the net and I was able to ping google and > different devices on the network. Now here is whats happening. > > I right now am only able to use the console until I can figure out the > hdmi issue I have but though its connected it will at random times even > while I am typing spit out a watchdog error > libertas: tx watch dog timeout > > also when I run iwconfig the results make no sense > root@overo:~# iwconfig > lo no wireless extensions. > > wlan0 IEEE 802.11b/g ESSID:"dwight" > Mode:Managed Frequency:2.412 GHz Access Point: > 00:1F:33:ED:E0:8E > Bit Rate:54 Mb/s Tx-Power=13 dBm > Retry short limit:8 RTS thr=2347 B Fragment thr=2346 B > Encryption key:off > Power Management:off > Link Quality=85/100 Signal level=-55 dBm Noise level=-90 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:896 Invalid misc:228072 Missed beacon:0 > > root@overo:~# libertas: tx watch dog timeout > > does not list it having an actual ip address neither a ipv4 nor ipv6 > address. but if I run dhclient it shows what address its bound to. > root@overo:~# dhclient > Internet Systems Consortium DHCP Client V3.1.2p1 > Copyright 2004-2009 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/sw/dhcp/ > > Listening on LPF/wlan0/00:50:43:02:fe:01 > Sending on LPF/wlan0/00:50:43:02:fe:01 > Sending on Socket/fallback > DHCPREQUEST on wlan0 to 255.255.255.255 port 67 > DHCPACK from 192.168.3.1 > bound to 192.168.3.17 -- renewal in 34284 seconds. > root@overo:~# > > Not really sure where to look from here but I will keep tinkering until I > get it or someone comes up with a better suggestion. Thanks for every ones > help so far. > > > > > vwyodapink wrote: >> >> I tried that script and have had no more luck than before but a new >> message came up that I have not seen before >> ADDRCONF(NETDEV_CHANGE): wlan0: >> then I did ifdown wlan0 and got this >> cat: /var/run/udhcpc.wlan0.pid: No such file or directory >> >> I have no GUI as of yet, when I try and run X on the latest desktop >> version listed for DL it does not run and I read on the OE wiki that more >> packages need to be DL'd to make it work. The wifi on my fire is the only >> way I have to connect to the net. >> >> If you have the fire do you happen to remember what specifically you had >> to do to get the wifi up? I have tried a ton with the listed directions >> and various ways online from searching and while I can get as far as the >> router never gets out of the router. No other computers have this issue >> on the network. >> >> >> >> >> Victhor Foster wrote: >>> >>> Try this script I found on the BackTrack forums, while it's says it's >>> for WPA networks, it should work just as well on open networks, as it >>> has an option to do that. >>> http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 >>> Also, if you have a GUI on your device, try installing the >>> NetworkManager applet, it works for me :) >>>> Just wondering if anyone else has any ideas? Or if someone has a >>>> working >>>> method for getting wifi to work on the Overo Fire? I have been trying >>>> for a >>>> few days now and I still can not get it past my router with no security >>>> though what was done above has helped some I still cant get to the net. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> > > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28604451.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: H. G. <shi...@gm...> - 2010-08-05 16:43:46
|
Hello vwyodapink, I was having trouble connecting my Overo Fire on Palo43 to my WEP router until I changed the execute permissions in NetworkManager. The only thing is that I can't ping anything. I was wondering if any fixes you did might help me able to ping my router? Any tips? Anybody else find a solution to a non pinging Overo Fire? Any help would be appreciated Thanks, Jesse vwyodapink wrote: > > Well just to let anyone know who may have this issue as well I am not 100% > solved but I am actually getting to the net now. Here is what I did. > edit /etc/sysctl.conf > edit dhclient.conf > edit network/interfaces right now its working on a no encryption network. > once I rebooted it was on the net and I was able to ping google and > different devices on the network. Now here is whats happening. > > I right now am only able to use the console until I can figure out the > hdmi issue I have but though its connected it will at random times even > while I am typing spit out a watchdog error > libertas: tx watch dog timeout > > also when I run iwconfig the results make no sense > root@overo:~# iwconfig > lo no wireless extensions. > > wlan0 IEEE 802.11b/g ESSID:"dwight" > Mode:Managed Frequency:2.412 GHz Access Point: > 00:1F:33:ED:E0:8E > Bit Rate:54 Mb/s Tx-Power=13 dBm > Retry short limit:8 RTS thr=2347 B Fragment thr=2346 B > Encryption key:off > Power Management:off > Link Quality=85/100 Signal level=-55 dBm Noise level=-90 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:896 Invalid misc:228072 Missed beacon:0 > > root@overo:~# libertas: tx watch dog timeout > > does not list it having an actual ip address neither a ipv4 nor ipv6 > address. but if I run dhclient it shows what address its bound to. > root@overo:~# dhclient > Internet Systems Consortium DHCP Client V3.1.2p1 > Copyright 2004-2009 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/sw/dhcp/ > > Listening on LPF/wlan0/00:50:43:02:fe:01 > Sending on LPF/wlan0/00:50:43:02:fe:01 > Sending on Socket/fallback > DHCPREQUEST on wlan0 to 255.255.255.255 port 67 > DHCPACK from 192.168.3.1 > bound to 192.168.3.17 -- renewal in 34284 seconds. > root@overo:~# > > Not really sure where to look from here but I will keep tinkering until I > get it or someone comes up with a better suggestion. Thanks for every ones > help so far. > > > > > vwyodapink wrote: >> >> I tried that script and have had no more luck than before but a new >> message came up that I have not seen before >> ADDRCONF(NETDEV_CHANGE): wlan0: >> then I did ifdown wlan0 and got this >> cat: /var/run/udhcpc.wlan0.pid: No such file or directory >> >> I have no GUI as of yet, when I try and run X on the latest desktop >> version listed for DL it does not run and I read on the OE wiki that more >> packages need to be DL'd to make it work. The wifi on my fire is the only >> way I have to connect to the net. >> >> If you have the fire do you happen to remember what specifically you had >> to do to get the wifi up? I have tried a ton with the listed directions >> and various ways online from searching and while I can get as far as the >> router never gets out of the router. No other computers have this issue >> on the network. >> >> >> >> >> Victhor Foster wrote: >>> >>> Try this script I found on the BackTrack forums, while it's says it's >>> for WPA networks, it should work just as well on open networks, as it >>> has an option to do that. >>> http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 >>> Also, if you have a GUI on your device, try installing the >>> NetworkManager applet, it works for me :) >>>> Just wondering if anyone else has any ideas? Or if someone has a >>>> working >>>> method for getting wifi to work on the Overo Fire? I have been trying >>>> for a >>>> few days now and I still can not get it past my router with no security >>>> though what was done above has helped some I still cant get to the net. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> > > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p29356371.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: J. L. <vwy...@gm...> - 2010-08-05 23:41:53
|
what results do you get when you ping your router and ping say www.google.com? For me on the desktop version all I had to do was select the correct network key type enter the key and hit connect. Where I had my issues was when I was initially trying to connect it was just through the console port on my summit board. and I ended up having to manually do what network manager does as well as kill NM to be able to connect while I was connecting through the console port. Not sure if its fully fixed yet as I still occasionally see the issue but dhcp was erroring out before automatically connecting. I seem to really only have issues and problems connecting when I am using my fire with the desktop image and not booting into it as a desktop top. I will ocassionally have it just boot everything but the xserver, or through the console port and I run into problems. I am sure if you can post some more info about your situation some can help you better than me, I am really new here and not to experienced. On Thu, Aug 5, 2010 at 9:43 AM, H. Gonzalez <shi...@gm...> wrote: > > Hello vwyodapink, > > I was having trouble connecting my Overo Fire on Palo43 to my WEP router > until I changed the execute permissions in NetworkManager. > > The only thing is that I can't ping anything. I was wondering if any fixes > you did might help me able to ping my router? Any tips? > > Anybody else find a solution to a non pinging Overo Fire? > > Any help would be appreciated > > Thanks, > Jesse > > > vwyodapink wrote: >> >> Well just to let anyone know who may have this issue as well I am not 100% >> solved but I am actually getting to the net now. Here is what I did. >> edit /etc/sysctl.conf >> edit dhclient.conf >> edit network/interfaces right now its working on a no encryption network. >> once I rebooted it was on the net and I was able to ping google and >> different devices on the network. Now here is whats happening. >> >> I right now am only able to use the console until I can figure out the >> hdmi issue I have but though its connected it will at random times even >> while I am typing spit out a watchdog error >> libertas: tx watch dog timeout >> >> also when I run iwconfig the results make no sense >> root@overo:~# iwconfig >> lo no wireless extensions. >> >> wlan0 IEEE 802.11b/g ESSID:"dwight" >> Mode:Managed Frequency:2.412 GHz Access Point: >> 00:1F:33:ED:E0:8E >> Bit Rate:54 Mb/s Tx-Power=13 dBm >> Retry short limit:8 RTS thr=2347 B Fragment thr=2346 B >> Encryption key:off >> Power Management:off >> Link Quality=85/100 Signal level=-55 dBm Noise level=-90 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:896 Invalid misc:228072 Missed beacon:0 >> >> root@overo:~# libertas: tx watch dog timeout >> >> does not list it having an actual ip address neither a ipv4 nor ipv6 >> address. but if I run dhclient it shows what address its bound to. >> root@overo:~# dhclient >> Internet Systems Consortium DHCP Client V3.1.2p1 >> Copyright 2004-2009 Internet Systems Consortium. >> All rights reserved. >> For info, please visit http://www.isc.org/sw/dhcp/ >> >> Listening on LPF/wlan0/00:50:43:02:fe:01 >> Sending on LPF/wlan0/00:50:43:02:fe:01 >> Sending on Socket/fallback >> DHCPREQUEST on wlan0 to 255.255.255.255 port 67 >> DHCPACK from 192.168.3.1 >> bound to 192.168.3.17 -- renewal in 34284 seconds. >> root@overo:~# >> >> Not really sure where to look from here but I will keep tinkering until I >> get it or someone comes up with a better suggestion. Thanks for every ones >> help so far. >> >> >> >> >> vwyodapink wrote: >>> >>> I tried that script and have had no more luck than before but a new >>> message came up that I have not seen before >>> ADDRCONF(NETDEV_CHANGE): wlan0: >>> then I did ifdown wlan0 and got this >>> cat: /var/run/udhcpc.wlan0.pid: No such file or directory >>> >>> I have no GUI as of yet, when I try and run X on the latest desktop >>> version listed for DL it does not run and I read on the OE wiki that more >>> packages need to be DL'd to make it work. The wifi on my fire is the only >>> way I have to connect to the net. >>> >>> If you have the fire do you happen to remember what specifically you had >>> to do to get the wifi up? I have tried a ton with the listed directions >>> and various ways online from searching and while I can get as far as the >>> router never gets out of the router. No other computers have this issue >>> on the network. >>> >>> >>> >>> >>> Victhor Foster wrote: >>>> >>>> Try this script I found on the BackTrack forums, while it's says it's >>>> for WPA networks, it should work just as well on open networks, as it >>>> has an option to do that. >>>> http://forums.remote-exploit.org/feature-requests/6222-wpa-connect-script.html#post25191 >>>> Also, if you have a GUI on your device, try installing the >>>> NetworkManager applet, it works for me :) >>>>> Just wondering if anyone else has any ideas? Or if someone has a >>>>> working >>>>> method for getting wifi to work on the Overo Fire? I have been trying >>>>> for a >>>>> few days now and I still can not get it past my router with no security >>>>> though what was done above has helped some I still cant get to the net. >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> >> >> > > -- > View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p29356371.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Bernhard Wörndl-A. <bw...@xd...> - 2010-05-17 20:06:21
|
Hey again! As far as good =) The problem with your cable modem is just because you haven't set a default gateway. Bot now we know that it's nothing "big". I'll have a look for the path to fix the dhcp problem. Regards *Bernhard Wörndl-Aichriedler* Am 17.05.2010 22:01, schrieb vwyodapink: > I tried what you suggested and it gave me the IP4 address and I am able to > ping the router. The router itself has no security on it right now what so > ever. Trying to ping my cable modem I get network unreachable. So its not > leaving my router now. I double checked to make sure that there is nothing > on the routers end that could block it, just to be sure and still with the > onboard nand image and the latest desktop image give me the same results of > getting to ping the router but not being able to leave the router. Thanks > for the help so far. > > Here are the results: > overo login: root > root@overo:~# ifconfig > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:36 errors:0 dropped:0 overruns:0 frame:0 > TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2328 (2.2 KiB) TX bytes:2328 (2.2 KiB) > > wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 > inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > root@overo:~# ifconfig wlan0 192.168.3.5 > root@overo:~# ifconfig wlan0 > wlan0 Link encap:Ethernet HWaddr 00:50:43:02:FE:01 > inet addr:192.168.3.5 Bcast:192.168.3.255 Mask:255.255.255.0 > inet6 addr: fe80::250:43ff:fe02:fe01/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:4231 (4.1 KiB) > > root@overo:~# ping 192.168.3.1 > PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data. > 64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=8.85 ms > 64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=3.14 ms > 64 bytes from 192.168.3.1: icmp_seq=3 ttl=64 time=2.41 ms > 64 bytes from 192.168.3.1: icmp_seq=4 ttl=64 time=2.71 ms > ^C > --- 192.168.3.1 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time 3004ms > rtt min/avg/max/mdev = 2.411/4.280/8.850/2.651 ms > root@overo:~# ping 192.168.0.1 > connect: Network is unreachable > root@overo:~# > > > > Bernhard Wörndl-Aichriedler wrote: > >> Hey =) >> >> If says - >> >> No lease, failing >> >> no correct IP has been obtained, you can try to set the IP manually - >> ifconfig wlan0 192.168.x.x >> >> There actually was a discussion about the DHCP failing in the lastest >> versions. >> You might be connected, and just not get a correct IP to work with. >> >> >> Regards >> >> *Bernhard Wörndl-Aichriedler* >> >> > |
From: vwyodapink <vwy...@gm...> - 2010-05-17 20:30:21
|
For me on the onboard nand that I was just shipped with I have the same exact setup as you and did as you said but that did not work for me. I would still have to do ifconfig wlan0 192.168.x.x to give it an ipv4 address and I get the adress and can ping the router but it does not stay connected for very long after and I can not ping past the router still. I noticed while booting though that it says it gets and address and everything but not true once you log in. It kind of seems like Network Manager is causing some issue because as you will it obtains the address and then goes through a few more steps then Network Manager starts and it then once you log in no address. Also looking in the dhcp3 folder the leases that are in there are for eth0 and I do not see anything for wlan0 lib80211: common routines for IEEE802.11 drivers libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin Remounting root file system... NET: Registered protocol family 10 libertas: 00:50:43:02:fe:01, fw 9.70.3p24, cap 0x0000030b libertas: wlan0: Marvell WLAN 802.11 adapter ALSA: Restoring mixer settings... Configuring network interfaces... ADDRCONF(NETDEV_UP): wlan0: link is not ready ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending select for 192.168.3.13... libertas: problem fetching packet from firmware Lease of 192.168.3.13 obtained, lease time 86400 run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 adding dns 192.168.3.1 done. Starting portmap daemon: portmap. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.ip_forward = 1 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting OpenBSD Secure Shell server: sshd done. Starting advanced power management daemon: No APM support in kernel (failed.) Starting ntpd: done Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: CSR build ID 0x0C-0x5C Device setup complete ttyS1 bluetoothd hid2hci rfcomm. Waiting for connection on channel 1 Starting Network connection manager daemon: NetworkManager. Starting PVR ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready PVRSRV_PIXEL_FORMAT_RGB565 Starting GPE display manager: gpe-dm Now with the latest desktop version on my SD card different results. When I went to the /var/lib folder there was already a dhcp folder but no dhcp3 folder in there. Thanks for such quick responses and helping me debug this. Very much appreciated I havent felt like such a linux noob in a long time until I just got my fire :P Bernhard Wörndl-Aichriedler wrote: > > On Mon, May 3, 2010 at 9:34 PM, roystonvasey<mik...@ma...> > wrote: > > >> I've found the problem with dhclient. >> It is unable to write the leases file to /var/lib/dhcp/dhclient.leases >> There is a directory /var/lib/dhcp3/ which i assume is for the leases. >> I created a directory/var/lib/dhcp/ and all works fine. > > > > > Regards > > *Bernhard Wörndl-Aichriedler* > > > -- View this message in context: http://old.nabble.com/Overo-Fire-WIFI-issues---Connected-to-router-tp28581791p28588445.html Sent from the Gumstix mailing list archive at Nabble.com. |