Re: Trouble flashing 2008.08
Mike MacHenry wrote: The problem is I can't figure out which of roughly 50 files from the this list I should download. http://buildhost.openmoko.org/daily/freerunner/200808/20080806/ You are looking for: The ASU/2008.8 rootfs http://buildhost.openmoko.org/daily/freerunner/200808/20080806/openmoko-qtopia-x11-image-om-gta02.jffs2 and the latest kernel: http://buildhost.openmoko.org/daily/freerunner/200808/20080806/uImage-om-gta02-latest.bin Brian ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Trouble flashing 2008.08
Mike MacHenry wrote: I'm using a neo freerunner and I am having a rather difficult time figuring out how to flash 2008.08 image that I was take to from the openmoko.com download link. From reading the wiki I've figured out that I need a kernel image and a rootfs image. Then I am supposed to boot into NOR flash mode and run the following two commands: dfu-util -a kernel -R -D /path/to/uImage dfu-util -a rootfs -R -D rootfs_filename.jffs2 The problem is I can't figure out which of roughly 50 files from the this list I should download. http://buildhost.openmoko.org/daily/freerunner/200808/20080806/ I tried several combinations of files that ended in jffs2 for the rootfs file and files that had gta02 and ended in .bin for the kernel image. Mostly the result I get is the openmoko splash screen when the device starts staying on the screen forever. I once got the machine to boot into a running distro but the machine was incredibly unreliable. Clicking on an icon gave a totally black screen, there were no buttons at the bottom of the app but it looked like there should be. Pressing the power button had no effect either. I think I'm just downloading the wrong images. I used qtopia the other day and it worked fine so my hardware is not busted. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, not being an expert, i installed the root filesystem (Openmoko-Freerunner-20080424-om-gta02.rootfs.jffs2) and flashed the kernel (uImage-2.6.24+git20080424-om-gta02.bin) when I had got mine cocked up. This took it back to 'as received' condition, and then i opkd update, upgrade once i got the usb networking going again. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Capacitor for snuffing interference to GPS antenna
Jim Colton wrote: Hey OpenMoko.com hardware team, Is the voltage on this cap. okay for me to use for the hardware solution to the GPS Problem? Capacitance is what you suggested... I want to put into place on mine if it is okay. http://www.westfloridacomponents.com/mm5/merchant.mvc?Screen=PRODProduct_Code=MON001Category_Code=MonolithicCapacitors-Chip-SurfaceMountStore_Code=wfc http://www.westfloridacomponents.com/mm5/merchant.mvc?Screen=PRODProduct_Code=MON001Category_Code=MonolithicCapacitors-Chip-SurfaceMountStore_Code=wfc I recommend NOT doing this until we understand the problem a bit better. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | DFU this into the kernel partition and you should be good for Debian, I | use these kernels with it myself all day. | | | How do I DFU this into the microSD's kernel paritition? Sorry I was explaining the NAND case. You can use it fine on microSD just mount the microSD on your laptop / PC and copy that file over to the correct partition as uImage.bin. Then unmount, return it to Freerunner and you should boot OK. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkialkYACgkQOjLpvpq7dMpSGgCfcRfuOIyiYc5B9SsHqJF00BXH TrEAoIdQ31HLHkP/ZsJfuzOqlfBLePYk =l7vu -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Kernel with built-in usb drivers / building the kernel cheatsheet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I understand that the usb tether drivers were moved out as kernel | modules. However, for the Debian port to work, I need them as part of | the kernel. Can someone point me to how I can re-compile the latest | kernel with the drivers included? | | I am a OpenEmbedded newbie and have minimal experience with the Moko | Makefile (i.e. I haven't done any modifications, just done a normal build). I don't think you need to do this, but of course it is a nice thing to be able to do anyway. You will know more about the OE side than me by the sound of it, but I can give you the steps to build the kernel standalone with the moredrivers config. ~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6 ~ - git checkout origin/stable ~ - edit ./build to point to your compiler path ~ - cp defconfig-2.6.24 .config ~ - ./build That gets you a uImage.bin you can DFU or copy into your SD Card filesystem. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkial1oACgkQOjLpvpq7dMr4fgCcDW3gW/SUfaSoeDF13HNo9nNh QJcAniA7Jcmy1mZvuoTwJ0Ts0GKPV+lb =BdM7 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
No network after flashing 200808
Hi, After flashing 200808 with kernel and rootfs from 20080806, I have no usb and no working wifi. Wifi connects, the wireless AP says so. but a quick nmap of my network show no new IP picked up from DHCP. Should I reflash the kernel with an older one (which?) and add the usb-net modules and then reflash with 200808 kernal? Matt ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No network after flashing 200808
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | After flashing 200808 with kernel and rootfs from 20080806, I have no | usb and no working wifi. | Wifi connects, the wireless AP says so. but a quick nmap of my | network show no new IP picked up from DHCP. | | Should I reflash the kernel with an older one (which?) and add the | usb-net modules and then reflash with 200808 kernal? That may not be the cause if you have a U-Boot from a week or more ago. ~ It can knock out your USB functionality 50% of the time. If that's the case, just update U-Boot with DFU. The issue with USB module should be resolved before yesterday in the packaging, so the rootfs should have the modules, therefore I wonder if it is the above. Otherwise, this kernel (eventually intended to be a recovery / backup kernel) has more modules built-in, including USB over Ethernet: you can DFU it in and it will get you going again. http://warmcat.com/uImage-moredrivers-stable_507c3c1ba3921bb7.bin - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiap1oACgkQOjLpvpq7dMrj2ACglOrsg72dR06Nc0icpYT03epZ 2A4AoIWrWc95xysTcX6sOn2KWpKQsZWR =udAp -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Debian : Touchscreen calibration
Following the instructions at : http://wiki.openmoko.org/wiki/Debian#Get_touchscreen_working , I was able to get touchscreen to work as a mouse. But, the cursor is way off from where I am touching. I am guessing the calibration mentioned there is not accurate anymore? Has anyone managed to get it working on Freerunner? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian : Touchscreen calibration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Following the instructions at : | http://wiki.openmoko.org/wiki/Debian#Get_touchscreen_working , I was | able to get touchscreen to work as a mouse. But, the cursor is way off | from where I am touching. I am guessing the calibration mentioned there | is not accurate anymore? Has anyone managed to get it working on Freerunner? The instructions there are not right. He gives canned numbers when these vary by individual Freerunner. You need to install tslib and its utilities (no idea what package, but it probably is packaged), and run ts_calibrate when it exits after you touch the crosshairs in sequence, the magic numbers it spits to console are the numbers you need to use for your actual touchscreen. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiasF8ACgkQOjLpvpq7dMpkxwCgkqMCAt3pkW1sGFWFcyc4KV1O bbEAnjk9HC3dUi9i04JTcZ9UAcf8+qLp =D7as -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
Sorry I was explaining the NAND case. You can use it fine on microSD just mount the microSD on your laptop / PC and copy that file over to the correct partition as uImage.bin. Then unmount, return it to Freerunner and you should boot OK. It works fine but reboot fails saying that CRC check fails for uImage.bin. I copy it again into the correct partition and again it works once, before failing again on reboot. Doesn't make sense to me. Or could it be getting corrupted because I am switching off and not shutting down? (I don't have a physical keyboard for it and power off is my only option). ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: inotify support in Kernel
How can I do this? (enabling inotify support in the kernel) set in kernel configuration and recompile kernel. if the kernel is supposed to run with debian and hal, i wonder why it would be missing ... ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: inotify support in Kernel
On Thu, Aug 7, 2008 at 2:06 PM, arne anka [EMAIL PROTECTED] wrote: How can I do this? (enabling inotify support in the kernel) set in kernel configuration and recompile kernel. if the kernel is supposed to run with debian and hal, i wonder why it would be missing ... It wasn't :D .. I am using the ASU kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Kernel with built-in usb drivers
I understand that the usb tether drivers were moved out as kernel modules. However, for the Debian port to work, I need them as part of the kernel. Can someone point me to how I can re-compile the latest kernel with the drivers included? Any chance you could be convinced to fix Debian so that it doesn't have this requirement? ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Unnecessary rant - Was: Re: USB networking in Ubuntu
How do I update my kernel by the packaging from inside the Freerunner? with opkg. usually opkg upgrade will upgrade the kernel as well. make sure your fr does not go to sleep while doing the upgrade and reboot afterwards to use the new kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
Doesn't make any sense to me either... can you md5sum the broken copy before overwriting it? Ok. Will do that the next time I get it. Also, I was using the ASU kernel so far. Switched to the one from the link you provided. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Kernel with built-in usb drivers
On Thu, Aug 7, 2008 at 2:09 PM, Jay Vaughan [EMAIL PROTECTED] wrote: I understand that the usb tether drivers were moved out as kernel modules. However, for the Debian port to work, I need them as part of the kernel. Can someone point me to how I can re-compile the latest kernel with the drivers included? Any chance you could be convinced to fix Debian so that it doesn't have this requirement? You mean the Debian kernel to have usb tether drivers built in? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Doesn't make any sense to me either... can you md5sum the broken copy | before overwriting it? | | | Ok. Will do that the next time I get it. Also, I was using the ASU | kernel so far. Switched to the one from the link you provided. We have it configured in our defconfigs, dunno why the ASU one doesn't have it. CONFIG_INOTIFY=y - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiatbUACgkQOjLpvpq7dMpadQCeLg5yfP2JXdwOjvyH3Ky8DPdo 3icAoIz9JlJJXY+1v9/BCT5NzZqb2y9c =1PJd -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Kernel with built-in usb drivers / building the kernel cheatsheet
standalone with the moredrivers config. ~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6 ~ - git checkout origin/stable ~ - edit ./build to point to your compiler path ~ - cp defconfig-2.6.24 .config ~ - ./build That gets you a uImage.bin you can DFU or copy into your SD Card filesystem. can someone please put this onto the wiki/debian page? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Kernel with built-in usb drivers / building the kernel cheatsheet
On Thu, Aug 7, 2008 at 2:23 PM, arne anka [EMAIL PROTECTED] wrote: standalone with the moredrivers config. ~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6 ~ - git checkout origin/stable ~ - edit ./build to point to your compiler path ~ - cp defconfig-2.6.24 .config ~ - ./build That gets you a uImage.bin you can DFU or copy into your SD Card filesystem. can someone please put this onto the wiki/debian page? Added at http://wiki.openmoko.org/wiki/Debian#.28Optional.29_Recompiling_Kernel_to_Add_Drivers Please correct me if wrong location or other problem with this. Thanks Ed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
On Thu, Aug 7, 2008 at 3:35 PM, sparky mat [EMAIL PROTECTED] wrote: On Thu, Aug 7, 2008 at 3:24 PM, Andy Green [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | | Doesn't make any sense to me either... can you md5sum the broken | copy | | before overwriting it? | | | | | The MD5 is : missing :-) But I had a thought, did you do this ext2 or ext3? ext3 is the better choice since the journalling is very forgiving of various transgressions. ext2 itself is pretty fragile. I got distracted with getting the MD5 and send it accidentally. Yes, I am using ext3. I read that ext3 journals a lot and could possibly thrash my card. Is it ok to use it? Typo: Yes, I am using *ext2* . Trying it with ext3 now. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
One of the things to like about SD Card and other card / stick memory is it hides many of the details of raw NAND from us, like bad blocks, error correcting codes and in this case wear levelling. I have run my mailserver on a 1G USB stick (hooked up to an ARM board I designed for another customer) for 2 years 24 / 7 now formatted ext3, that gets pretty hammered, no trouble. So I can't guarantee your particular card isn't broken for wear levelling, but cheap random USB stick doesn't care in the least about ext3 and I didn't see any trouble from SD with ext3 either. Trying out ext3 now. :-) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Trouble flashing 2008.08
Brian C wrote: Mike MacHenry wrote: The problem is I can't figure out which of roughly 50 files from the this list I should download. http://buildhost.openmoko.org/daily/freerunner/200808/20080806/ You are looking for: The ASU/2008.8 rootfs http://buildhost.openmoko.org/daily/freerunner/200808/20080806/openmoko-qtopia-x11-image-om-gta02.jffs2 FYI, that image is not ASU/2008.08, since buildhost builds from the org.openmoko.dev branch, not the org.openmoko.asu.* branches. So whilst it might give an idea of what ASU might look like, it will certainly have lots of bugs and features (e.g. the FSO theme) which definitely are not in the image you get when you build from the correct branch. -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No network after flashing 200808
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | After flashing 200808 with kernel and rootfs from 20080806, I have no | usb and no working wifi. | Wifi connects, the wireless AP says so. but a quick nmap of my | network show no new IP picked up from DHCP. | | Should I reflash the kernel with an older one (which?) and add the | usb-net modules and then reflash with 200808 kernal? That may not be the cause if you have a U-Boot from a week or more ago. ~ It can knock out your USB functionality 50% of the time. If that's the case, just update U-Boot with DFU. The issue with USB module should be resolved before yesterday in the packaging, so the rootfs should have the modules, therefore I wonder if it is the above. Otherwise, this kernel (eventually intended to be a recovery / backup kernel) has more modules built-in, including USB over Ethernet: you can DFU it in and it will get you going again. http://warmcat.com/uImage-moredrivers-stable_507c3c1ba3921bb7.bin - -Andy I flashed uboot at the same time, so all were from 20080806 I'll give the moredrivers a whirl... Thanks ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Capacitor for snuffing interference to GPS antenna
Thomas Coppens escreveu: 2008/8/7 Michael Shiloh [EMAIL PROTECTED]: I recommend NOT doing this until we understand the problem a bit better. Michael Statements on these mailing list are often confusing because the origin isn't very clear at times. Perhaps there's a need for an official signature in messages originating from OpenMoko staff? Just a thought. Just check the person's name/email against the list at http://wiki.openmoko.org/wiki/Who_is_Who, and you will even know his/her attributions within Openmoko[1]. [1] List compiled mostly by random non-Openmoko passers-by. Might be incomplete or misleading. -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
One of the things to like about SD Card and other card / stick memory is it hides many of the details of raw NAND from us, like bad blocks, error correcting codes and in this case wear levelling. I have run my mailserver on a 1G USB stick (hooked up to an ARM board I designed for another customer) for 2 years 24 / 7 now formatted ext3, that gets pretty hammered, no trouble. So I can't guarantee your particular card isn't broken for wear levelling, but cheap random USB stick doesn't care in the least about ext3 and I didn't see any trouble from SD with ext3 either. Trying out ext3 now. :-) Having some trouble compiling the kernel. I followed the (new) instructions posted on the Debian page in the wiki. However, when I hit ./build , mkimage just displays the command syntax and quits. I am compiling on Ubuntu 8.04. mkimage was not available and based on the recommendation, I installed jigit. Even as I speak, I am reading the jigit package description and something tells me this is not what I want. So which mkimage should I install for the ./build script ? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian - How to install the kernel
So which mkimage should I install for the ./build script ? probably uboot-mkimage available in debian/unstable. dunno if in ubunu too. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB Networking troubles
michael cole [EMAIL PROTECTED] writes: This is not a Freerunner issue -- I am able to ssh into FR using UBS networking but I simply cannot get the Freerunner to ping anything other than the desktop it is connected to. The issue almost certainly has something to do with the iptables/nat setup on the desktop computer. Can you run http://iki.fi/lindi/print-net-settings on your desktop system and report the output? It should print all relevant network information. Also, desktop$ sudo tcpdump -i usb0 -n icmp desktop$ sudo tcpdump -i eth0 -n icmp while running freerunner$ ping 192.168.1.1 could be useful. What does tcpdump print in that case? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB Networking troubles
On Thu, Aug 7, 2008 at 2:54 PM, Timo Juhani Lindfors [EMAIL PROTECTED]wrote: michael cole [EMAIL PROTECTED] writes: This is not a Freerunner issue -- I am able to ssh into FR using UBS networking but I simply cannot get the Freerunner to ping anything other than the desktop it is connected to. The issue almost certainly has something to do with the iptables/nat setup on the desktop computer. Can you run http://iki.fi/lindi/print-net-settings on your desktop system and report the output? It should print all relevant network information. Also, desktop$ sudo tcpdump -i usb0 -n icmp desktop$ sudo tcpdump -i eth0 -n icmp while running freerunner$ ping 192.168.1.1 could be useful. What does tcpdump print in that case? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support This is my script to login and configure . Hope it works for you. #!/bin/bash clear /etc/rc.d/iptables start iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 sysctl -w net.ipv4.ip_forward=1 ifconfig usb0 192.168.0.200 iptables -t filter -F FORWARD scp /etc/resolv.conf [EMAIL PROTECTED]:/etc ssh [EMAIL PROTECTED] -- Phillip Tribble Rushers Blog http://rusher.webhop.org If you don't take one step forward, you will always be one step behind ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB Networking troubles
debian/unstable amd64, 2.6.26. my /etc/network/interfaces says for usb networking allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.0 network 192.168.0.0 post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 post-up echo 1 /proc/sys/net/ipv4/ip_forward post-up iptables -P FORWARD ACCEPT you should try the last three lines in a shell, to see if helpful messages come up (i had to build an additional iptables module). ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB Networking troubles
Hi Timo: Here is the output from print-net-settings (run on desktop): = print-net-settings output # ./print-net-settings + LC_ALL=C + date Thu Aug 7 22:26:53 UTC 2008 + hostname armstrong + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/ip_forward 1 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/all/proxy_arp 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/default/proxy_arp 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/eth0/proxy_arp 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/lo/proxy_arp 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/usb0/proxy_arp 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/all/rp_filter 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/default/rp_filter 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/eth0/rp_filter 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/lo/rp_filter 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat /proc/sys/net/ipv4/conf/usb0/rp_filter 0 + for i in /proc/sys/net/ipv4/ip_forward '/proc/sys/net/ipv4/conf/*/proxy_arp' '/proc/sys/net/ipv4/conf/*/rp_filter' '/proc/net/bonding/bond*' + cat '/proc/net/bonding/bond*' cat: /proc/net/bonding/bond*: No such file or directory + ip rule list 0: from all lookup 255 32766: from all lookup main 32767: from all lookup default ++ ip rule list ++ cut '-d ' -f4 ++ sort ++ uniq + for i in '`ip rule list|cut -d'\'' '\'' -f4|sort|uniq`' + ip route list table 255 broadcast 192.168.1.0 dev eth0 proto kernel scope link src 192.168.1.200 broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1 broadcast 192.168.1.192 dev usb0 proto kernel scope link src 192.168.1.200 broadcast 192.168.1.255 dev eth0 proto kernel scope link src 192.168.1.200 broadcast 192.168.1.255 dev usb0 proto kernel scope link src 192.168.1.200 broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1 local 192.168.1.200 dev eth0 proto kernel scope host src 192.168.1.200 local 192.168.1.200 dev usb0 proto kernel scope host src 192.168.1.200 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1 + for i in '`ip rule list|cut -d'\'' '\'' -f4|sort|uniq`' + ip route list table default + for i in '`ip rule list|cut -d'\'' '\'' -f4|sort|uniq`' + ip route list table main 192.168.1.192/26 dev usb0 proto kernel scope link src 192.168.1.200 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.200 default via 192.168.1.1 dev eth0 + ip link show 1: lo: LOOPBACK,UP,1 mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:1b:3f:f5:d4 brd ff:ff:ff:ff:ff:ff 86: usb0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000 link/ether ba:f3:e6:14:4a:e3 brd ff:ff:ff:ff:ff:ff + ip addr show 1: lo: LOOPBACK,UP,1 mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:1b:3f:f5:d4 brd ff:ff:ff:ff:ff:ff inet 192.168.1.200/24 brd 192.168.1.255 scope global eth0 inet6 fe80::230:1bff:fe3f:f5d4/64 scope link valid_lft forever preferred_lft forever 86: usb0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000 link/ether ba:f3:e6:14:4a:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.1.200/26 brd 192.168.1.255 scope global usb0 inet6 fe80::b8f3:e6ff:fe14:4ae3/64 scope link valid_lft
Re: USB Networking troubles
This is posted with the hope someone can look at the current state of my Freerunner connection to the desktop and just see something that is not right. I am sure the answer is simple and am reluctant to ask the community for non-FR help but perhaps others are struggling with similar network issues in getting their FR hooked up to the Internet. My basic setup: router - 192.168.1.1 desktop - 192.168.1.200 freerunner - 192.168.1.202 You mean it looks something like this: 192.168.1.1 192.168.1.200 192.168.1.202 routerswitch---desktop--freerunner / / other_stuff 192.168.1.x and everything on the left has a netmask of 255.255.255.0? If that's so forget about the FreeRunner talking to anything but the desktop. In fact, be suprised and grateful if it's doing that much. The routing table you gave is horrible and it will stop working if you re-start the non-usb network interface on your machine. You need different subnets on the two desktop NICs to have any hope. The only possible way around this fact is to use ethernet bridging instead of routing on the desktop, and that's such an ugly hack that I refuse to work up directions for configuring it. I've never seen it done on a network that worked right. Your desktop needs to act as a ROUTER for the FreeRunner. A router by definition is connected to two or more *different* networks. From the perspective of the stuff on the left, the 192.168.1.192/26 subnet the FreeRunner is on is not a different network - it's a few addresses on the same network. (This is what netmasks are about. Basically, they tell the computer how big the neighborhood is.) Which means they aren't sending packets for the FreeRunner through the desktop, they're just ARPing and expecting the FreeRunner to respond, but since it's on a different network, it can't hear the ARPs. Packets from the FreeRunner probably do reach their destinations, but the reply packets don't come back, which means you don't get a ping response and can't establish any kind of connection. The easiest way to fix this is probably to use your half-working setup to SSH into the FreeRunner and reconfigure it to use, say, 192.168.2.202, then do the same with the desktop side of the USB ethernet connection. Then kill the iptables rules in your nat table POSTROUTING chain. You can either: 1) Leave them gone and put a static route to 192.168.2.192/26 in your router, specifying your desktop's 192.168.1.x address as the gateway OR (exclusive, do not do both of these things) 2) specify on the desktop an iptables rule to NAT all packets coming from the USB network - something like 'iptables -t nat -A POSTROUTING -s 192.168.2.192/26 -j MASQUERADE'. Whichever you choose, you'll need the FORWARD chain in the filter table in its current permissive state. You'll also want to double-check that sysctl net.ipv4.ip_forward=1. The simplest way to check this is 'cat /proc/sys/net/ipv4/ip_forward'. Hope that helps. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: /qtopia/ weird problems after yesterdays' opkg upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 1. klogd went very busy and dmesg got full of | evbug.c: Event. Dev: NULL, Type: 0, Code: 0, Value: 0 | evbug.c: Event. Dev: NULL, Type: 2, Code: 0, Value: 54 | evbug.c: Event. Dev: NULL, Type: 2, Code: 1, Value: 18 There's a module called evbug that is getting inserted for some reason, I killed building it today in the configs we use so it should be gone tomorrow. It just seems to exist to spew in syslog. | Aug 7 22:12:19 om-gta02 user.warn kernel: Alignment trap: mediaplayer (1436) PC=0x42ef7d10 Instr=0xe592c008 Address=0x0009 FSR 0x013 | isn't alignment trap signals for memory management issues? Alignment in ARM is quite interesting... http://warmcat.com/_wp/2007/05/25/the-alignment-monster/ short story is this is just a warning and was handled. | after a bit of waiting mediaplayer stopped crashing and started to play the | ringtone fine and then I started to hear ringtone again while receiving a phone | call just for once... on a next phone call -- same 'vibration only' (and | mediaserver being very busy) and media player doesn't play -- just sits waiting | -- cpu is not busy. | | rebooted again (no busy klogd this time), didn't play tone, started media | player -- started to play it and then started to play it while accepting the | phone calls. Can't guess about that. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkibh2cACgkQOjLpvpq7dMrw+ACfaM1cIwIOxra83ufEU5DzGLmi h0QAnjn2/sMrmzXBHT6YxHRtzbCnnSDu =yqaH -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Terminal in default package?
Can we please put terminal in the default package list for ASU again? When it first comes up, bluez is useless (no net support), I've yet to get the default wifi handler to get any wifi setup, and the only way to get on is via USB. And now in the latest image... USB is acting up again. I flashed the daily build (8/7) and it's just not liking me. :P For some reason the WinXP box I have is blue-screening when connect the neo. When I connect to the Win2K box I have, it's showing the connection, but then saying Network cable unplugged. I have an ancient Slackware system running, but it's so old it doesn't have USB support really. Any ideas whats going on? (And yes, I've rebooted everything 6 times and wait for the freerunner to boot fully before plugging it in...) If I had a terminal in the default package I could at least peck in and see whats going on... As it is, I have no way in or out... Oh.. And how are you supposed to power down in 2008.8? The power button seems to do nothing unless you hold it a long time (long hold shut off), and using shutdown (when I was able to terminal in) kills the X server, but runs out of processes for this init level and dies. Not pretty. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support