Re: SHR - Trying to configure phone for a wireless demo...
On Wednesday 09 September 2009 01:39:54 Paul Fertser wrote: You certainly want to consult http://wiki.openmoko.org/wiki/FSO_Resources wikipage; it's frameworkd syncing resources on startup and thus turning everything off. Thanks Paul. I installed the fsoraw utility (funny, I did a opkg search fsoraw and found nothing, then I did a opkg list | grep -i fsoraw and saw it in the list. Then I typed opkg install fsoraw and voila, it installed). I managed to get the fsoraw utility to start the wpa_supplicant applications and I could see the wpa handshake being done on the AP (Access Point) side. Then the udhcpc (busybox dhcp client) started up and did it's usual round of ignoring the response to its DHCPDISCOVER messages (this is why I want to get dhclient). Eventually it actually did send a DHCPACK and it had an IP address. I spent too long congratulating myself and gloating because just as I issued the ssh r...@wifi-ip-address-of-my-neo the AP log said that the wifi had been disassociated and the Neo was showing that the wifi timed out due to inactivity. This is a few steps forward. Thanks for the help. Cheers!! -- To Err is human, to forgive is NOT company policy. John Dowd S/W Contractor email: jdowd at gmail dot com Cell: (613)316-7884 Home: (613)234-7884 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 - Trying to configure phone for a wireless demo...
John Dowd jdowds...@gmail.com writes: On Wednesday 09 September 2009 01:39:54 Paul Fertser wrote: You certainly want to consult http://wiki.openmoko.org/wiki/FSO_Resources wikipage; it's frameworkd syncing resources on startup and thus turning everything off. ... I managed to get the fsoraw utility to start the wpa_supplicant applications and I could see the wpa handshake being done on the AP (Access Point) side. Then the udhcpc (busybox dhcp client) started up and did it's usual round of ignoring the response to its DHCPDISCOVER messages (this is why I want to get dhclient). Eventually it actually did send a DHCPACK and it had an IP address. I spent too long congratulating myself and gloating because just as I issued the ssh r...@wifi-ip-address-of-my-neo the AP log said that the wifi had been disassociated and the Neo was showing that the wifi timed out due to inactivity. Looks like you want to try wmiconfig -i eth0 --power=maxperf trick. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR - Trying to configure phone for a wireless demo...
On Friday 04 September 2009 16:23:51 George Brooke wrote: usb0 should now be ethX just look in dmesg to see what number its taken. solar.george Respectfully, who cares what the interface is called on the Neo side, this does not reflect back to the device (in this case a laptop) at the other end of the usb cable. That device (the laptop) does not see any ethernet i/f because the Neo is not starting one. Cheers!! -- To Err is human, to forgive is NOT company policy. John Dowd S/W Contractor email: jdowd at gmail dot com Cell: (613)316-7884 Home: (613)234-7884 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 - Trying to configure phone for a wireless demo...
On Tuesday 08 September 2009 15:50:26 John Dowd wrote: On Friday 04 September 2009 16:23:51 George Brooke wrote: usb0 should now be ethX just look in dmesg to see what number its taken. solar.george Respectfully, who cares what the interface is called on the Neo side, this does not reflect back to the device (in this case a laptop) at the other end of the usb cable. That device (the laptop) does not see any ethernet i/f because the Neo is not starting one. Cheers!! I mean on the laptop side 1. Plug neo into laptop 2. run dmesg on laptop [ 9359.352059] usb 2-2: new full speed USB device using uhci_hcd and address 2 [ 9359.566175] usb 2-2: configuration #1 chosen from 2 choices [ 9359.914928] eth2: register 'cdc_ether' at usb-:00:1d.0-2, CDC Ethernet Device, 00:1f:11:01:70:8f [ 9359.915323] usbcore: registered new interface driver cdc_ether [ 9359.962215] udev: renamed network interface eth2 to eth5 3. look for lines like the above which tell you that my neo is at eth5 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 - Trying to configure phone for a wireless demo...
On Tuesday 08 September 2009 11:00:52 George Brooke wrote: I mean on the laptop side 1. Plug neo into laptop 2. run dmesg on laptop [ 9359.352059] usb 2-2: new full speed USB device using uhci_hcd and address 2 [ 9359.566175] usb 2-2: configuration #1 chosen from 2 choices [ 9359.914928] eth2: register 'cdc_ether' at usb-:00:1d.0-2, CDC Ethernet Device, 00:1f:11:01:70:8f [ 9359.915323] usbcore: registered new interface driver cdc_ether [ 9359.962215] udev: renamed network interface eth2 to eth5 3. look for lines like the above which tell you that my neo is at eth5 Bingo, it works and you are correct, it's now on eth1. Good thing I put that Respectfully at the start of my reply or I might have to buy your beer for the rest of my life. Cheers!! -- To Err is human, to forgive is NOT company policy. John Dowd S/W Contractor email: jdowd at gmail dot com Cell: (613)316-7884 Home: (613)234-7884 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 - Trying to configure phone for a wireless demo...
On Tuesday 08 September 2009 16:11:17 John Dowd wrote: On Tuesday 08 September 2009 11:00:52 George Brooke wrote: I mean on the laptop side 1. Plug neo into laptop 2. run dmesg on laptop [ 9359.352059] usb 2-2: new full speed USB device using uhci_hcd and address 2 [ 9359.566175] usb 2-2: configuration #1 chosen from 2 choices [ 9359.914928] eth2: register 'cdc_ether' at usb-:00:1d.0-2, CDC Ethernet Device, 00:1f:11:01:70:8f [ 9359.915323] usbcore: registered new interface driver cdc_ether [ 9359.962215] udev: renamed network interface eth2 to eth5 3. look for lines like the above which tell you that my neo is at eth5 Bingo, it works and you are correct, it's now on eth1. Good thing I put that Respectfully at the start of my reply or I might have to buy your beer for the rest of my life. Cheers!! No problem, glad it got sorted out. 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 - Trying to configure phone for a wireless demo...
On Tuesday 08 September 2009 12:24:41 George Brooke wrote: No problem, glad it got sorted out. solar.george I can now manually configure the wireless interface but I need to come up automatically during boot and start the dhcp client. I can see that the kernel does boot and somewhere during init the interface is brought up. However, somewhere later during the init the wireless interface is being shutdown. If I go into the Setup application I can see that the wireless option is turned off. If I turn it back on it then the interface does come up. However, it is not persistent across boots. How do I turn off the current system setting of turning off the wireless interface? I have a wlan script in the /etc/init.d directory and once I manually bring up the wireless interface I can run it and it does configure the interface properly. Also, I'm running into the same problem with the busybox udhcpc application that I've seen before. It does not see the DCHPOFFER from the AP. It ignores it and continues to issue the DCHPDISCOVER. There was a application dhclient that ran on the OM2009 distro. Is there anything available here on the unstable SHR? One person mentioned that the problem was that the Signal level (which is -147dBm) is way too low and should be at least -90dBm. Where would I change this? I have some control over the AP if that is where the change needs to be. And on more piece of information that I need I can bring up the shell on the Neo but the keyboard that pops up does not have an obvious way to insert (or type) a carriage return. There has to be a way? Cheers!! -- To Err is human, to forgive is NOT company policy. John Dowd S/W Contractor email: jdowd at gmail dot com Cell: (613)316-7884 Home: (613)234-7884 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 - Trying to configure phone for a wireless demo...
On Tuesday 08 September 2009 21:40:59 John Dowd wrote: And on more piece of information that I need I can bring up the shell on the Neo but the keyboard that pops up does not have an obvious way to insert (or type) a carriage return. There has to be a way? drag down on the kbd, up to change layouts left-right for space right-left for backspace you might be better off with the terminal layout (should be installed by default, just press on the up arrow on the right and select terminal) 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 - Trying to configure phone for a wireless demo...
John Dowd jdowds...@gmail.com writes: I can now manually configure the wireless interface but I need to come up automatically during boot and start the dhcp client. I can see that the kernel does boot and somewhere during init the interface is brought up. However, somewhere later during the init the wireless interface is being shutdown. You certainly want to consult http://wiki.openmoko.org/wiki/FSO_Resources wikipage; it's frameworkd syncing resources on startup and thus turning everything off. If I go into the Setup application I can see that the wireless option is turned off. If I turn it back on it then the interface does come up. However, it is not persistent across boots. How do I turn off the current system setting of turning off the wireless interface? I have a wlan script in the /etc/init.d directory and once I manually bring up the wireless interface I can run it and it does configure the interface properly. Start your script after frameworkd and use fsoraw accordingly. Also, I'm running into the same problem with the busybox udhcpc application that I've seen before. It does not see the DCHPOFFER from the AP. It ignores it and continues to issue the DCHPDISCOVER. There was a application dhclient that ran on the OM2009 distro. Is there anything available here on the unstable SHR? If dhclient is not in the feeds, i'm sure one of SHR folks (dos1, you ;) ) can add it. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR - Trying to configure phone for a wireless demo...
John Dowd jdowds...@gmail.com writes: Is there a magic combination here that I can put together so that I can use the wireless interface with the SHR load? The latest unstable SHR; then opkg update opkg upgrade; then please read FSO_resources wikipage. SHR testing is basically an unsupported snapshot. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR - Trying to configure phone for a wireless demo...
On Friday 04 September 2009 16:32:50 John Dowd wrote: I would like to do this demo using the more recent SHR loads since the om2008 series seems to be abandoned. I have a few issues and I'm wondering if someone knows how to get around them. I've put the lastest stable load of SHR on. I have been able to get the wireless to work by modifying the various wpa_supplicant and init.d files by hand but, the phone comes up without the wireless chip turned on so I have to go into the settings application and actually turn it on. It's not persistent. I then have to run my init script and then it connects (I can see the wpa handshaking being done on my AP). However the DHCP client dhclient doesn't appear to be available under SHR and I have to fall back to busybox's udhcpc. It just doesn't seem to work. According to the SHR project page, I could use Mokonnect to configure all of this but it's not available to the stable version and I tried to load the unstable package but it gives me startup errors and then gacks. I've tried to put a unstable SHR load on the Neo but then I run into all sorts of incompatibility issues and I get things like the usb0 interface is unavailable and I therefore can't then get at the Neo to fix things. usb0 should now be ethX just look in dmesg to see what number its taken. 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
