Re: wpa_supplicant not dettecting association?
Joachim Ott wrote: 2009/3/5 Daniel Benoy dan...@benoy.name: Also, I rebooted the thing and it got an IP just fine. (!?) Also I see that it got alerted through the wpa_cli action stuff at boot time just like I was expecting it to do earlier... I'm working on the theory that the timeout in wpa_supplicant is too short.. it would explain the flakyness. Unfortunately the timeout value is hard coded, so I'll have to mess around to test that. also 'iwconfig eth0 power off' seems to make the issues go away. All this intermittant behavior is reinforcing my theory that the timeout is too short and various factors make the time it takes shorter or longer causing intermittant behavior. Shame on wpa_supplicant for not making the timeout configurable. If this is really an open AP, you don't need to hassle with wpa_supplicant, just do: iwconfig eth0 essid kitsune Then use dhclient to get an IP. Sometimes it's useful to force the removal of any previous key: iwconfig eth0 essid kitsune key off ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo for DATA acquisition with USB
I'd use an Arduino and hook up the sensor to the Arduino inputs. Gives you immediate access to a huge range of voltage or resistive sensors, and probably very easy to interface to I2C, OneWire, SPI, etc. sensors. Hundreds of examples on the web. Perhaps even thousands. I'm pretty sure that Arduino to FreeRunner has already been demonstrated to work. Don't forget to put your USB port in host mode, and pay attention to the power discussions on the wiki and in the archives. M lakshmikanth wrote: I want to read data from the sensor(any) to Neo(Openmoko freerunner) with the USB port. Do we have any readily available chips which are compatible to Neo OS (OM2007.2 or what so ever) for reading the data from USB? I have checked out CP2102, but it has drivers in rpm format.same with Telos chip... Is it possible to install drivers of the format .rpm or .dep ... is there any method to do that?? If we have to develop one such system, then what are the steps to be followed:like which microcontroller and peripheral chips to be used and how to develop firmware for them. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
Marco Trevisan (Treviño) wrote: Leonti Bielski wrote: As I get it it is unfortunately impossible to upgrade the firmware at home because of NDA - only Openmoko Inc. employee can do that. I hope (but doubt it ) it will will be available to the public someday in the future. Why? Isn't it a binary blob? I can't understand why they can't release the firmware binary... Two issues: 1. If we allow you to update the firmware, then our own standard of openness requires that we give you the source. Due to NDA with chip manufacturer, and probably FCC regulations as well, we're not allowed to give you the source, so therefore we chose not to allow you to update the firmware. 2. The NDA with the chip manufacturer does not allow us to distribute the update utility. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
Joel Newkirk wrote: On Tue, 14 Oct 2008 04:58:51 +1000, Lorn Potter [EMAIL PROTECTED] wrote: Michael 'Mickey' Lauer wrote: This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). I would say it has more to do with firmware. I have a gta01 that does this, a gta02 prototype that does it and a production FR that does not. All using the same gui, same sim, same tower, same operator, same network traffic. Using sleep mode on my production FR, stops it from properly waking up on phone calls and sms, so this is not reliable in stopping the bouncy calypso. I'm assuming that said firmware is field-upgradeable, right? :) So once a fix is devised it won't be just for newly-produced handsets, as might be the case with 'ordinary' cellphones. ;) I'm seeing this issue on a GTA02v6 (August production) with frameworkd and zhone. Don't recall ever observing it on my previous (pre-RMA, June production) GTA02v5, but it's possible that it's just frameworkd+zhone making it more visible to me. Inquiry shows me HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8, though /proc/cpuinfo lists revision 0360. Carrier is T-Mobile in US, but I'm permanently roaming on either Suncom (being folded into T-Mobile now) or Cingular/ATT, and I've seen this happening on both roaming networks. This bug seems to be much worse with ATT than T-mobile. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: NetworkManager in Intrepid breaks my FreeRunner's Internet connection
Jeffrey Ratcliffe wrote: I've just upgraded my Hardy desktop to Intrepid and now have network problems. This is my /etc/network/interfaces auto lo iface lo inet loopback auto usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.0 network 192.168.0.0 up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 up echo 1 /proc/sys/net/ipv4/ip_forward up iptables -P FORWARD ACCEPT down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 This worked fine with Hardy, but the desktop cannot see the network. If I comment out auto usb0 and everything below, I can access the rest of the network, but then, of course, my FreeRunner no longer has Internet access. Sure sounds like a routing issue. Can you post your routing table? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: neo1973 does not power on.
| After a recent reboot, the system never came back. Pushing the power button | causes nothing to happen. I don't even seem to get into uboot(no logo screen). See if this helps: pull the battery, wait a few seconds, then hold down AUX key and keep it down, reapply battery, hold power button in too, let go of AUX then let go of power button. Andy, For the curious, and for further enlightenment, can you explain what that does? Thanks, Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Revive Freerunner with USB power?
Joachim Ott wrote: 2008/9/10 Michael Shiloh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Joachim Ott wrote: Before trying this: would it work to give USB power to the pins where the battery connects in order to revive the FR or will that cause damage in the device? The output of the USB is about 4.56 V and (I think) 500 mA. It's fine. Just be very careful. If the polarity is wrong, or you touch the wrong pins, or you give the wrong voltage you will almost certainly damage your FreeRunner. Hook everything up, then get a friend to look and confirm you've done it correctly before you turn on the USB power. I have done it successfully. See here: http://nop0.blogspot.com/2008/09/revive-openmoko-neo-freerunner-with-usb.html Excellent. I have been meaning to document this procedure but my pictures aren't anywhere near as good as yours. I'll link to your blog. Thanks! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Revive Freerunner with USB power?
William Kenworthy wrote: I'm having to do this on a regular basis - why? 1 out of every 3 or so nights, I wake up (~6-8hrs) and find the FR dead. :( Only GSM is running and its on dimlock The battery is always fully charged when checked just before I retire. In some cases I have left it on charge, confirmed its charging and still wake to a dead phone. BillK There is a known bug that after fully charging the phone would turn off the charger and forget to turn it back on again as the phone became discharged. Look in the archives - I think it was last week this was discussed. Might be on the kernel or device-owners list. Should probably also be in TRAC. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Revive Freerunner with USB power?
Joachim Ott wrote: Before trying this: would it work to give USB power to the pins where the battery connects in order to revive the FR or will that cause damage in the device? The output of the USB is about 4.56 V and (I think) 500 mA. It's fine. Just be very careful. If the polarity is wrong, or you touch the wrong pins, or you give the wrong voltage you will almost certainly damage your FreeRunner. Hook everything up, then get a friend to look and confirm you've done it correctly before you turn on the USB power. To protect ourselves we have to say that OpenMoko does not recommend this procedure so do so at your own risk. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Revive Freerunner with USB power?
Joachim Ott wrote: 2008/9/10 Michael Shiloh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Joachim Ott wrote: Before trying this: would it work to give USB power to the pins where the battery connects in order to revive the FR or will that cause damage in the device? The output of the USB is about 4.56 V and (I think) 500 mA. It's fine. Just be very careful. If the polarity is wrong, or you touch the wrong pins, or you give the wrong voltage you will almost certainly damage your FreeRunner. Hook everything up, then get a friend to look and confirm you've done it correctly before you turn on the USB power. Don't worry. I will use isolated alligator clips and check before, that + goes to the red clip and - to the black clip and check once more, to which pins red and black must be connected. I will also take pictures of that operation. Better than alligator clips, I like the mini-hooks from E-Z Hook [1]. Been using these since college and I would never use anything else. [1] http://www.e-z-hook.com/Html/MiniHooks.html ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: installDebianOnNeo.sh failed
Matthias Barmeier wrote: Hi, I tried several 2.6.24 images, but with all 2.6.24 images I always get this message mount: unknown filesystem type 'ext2' Why is ext2 unknown on a 2.6.24 image ?? Ciao Matthias Juan Cañete schrieb: Hi, I didn't know it, so I asked. Someone reported the same problem. Try flashing the same kernel image that you'll install on debian and install debian from that. best regards El Tue, 09 Sep 2008 17:43:09 +0200 Matthias Barmeier [EMAIL PROTECTED] dijo: Hi, I know which version is installed. uname -a gives [EMAIL PROTECTED]:~$ uname -a Linux fic-gta01 2.6.22.5-moko11 #1 PREEMPT Sat Dec 1 03:40:58 CET 2007 armv4tl unknown I installDebianNeo.sh seem to be: KERNEL_IMAGE=http://downloads.openmoko.org/framework/milestone2/uImage-2.6.24+gitr0+7a1370a816b9348dd8f36a667905dd3533cefc9b-r4-om-gta01.bin Ciao Matthias Juan Cañete schrieb: Hi, which kernel version are you installing debian from? which kernel version are you installing in debian? best regards. El Tue, 09 Sep 2008 16:11:28 +0200 Matthias Barmeier [EMAIL PROTECTED] dijo: Hi, when I try to install Debian on my neo1973 the install script terminates with: * Setting empty root password I: System configured I: Done with stage configuration Running stage kernel Installing kernel image and modules * Dowloading kernel image Connecting to downloads.openmoko.org[88.198.93.219]:80 uImage.bin 100% || 1758 KB 00:00:00 ETA * Downloading kernel modules * Running depmod WARNING: Couldn't open directory /lib/modules/2.6.22.5-moko11: No such file or directory FATAL: Could not open /lib/modules/2.6.22.5-moko11/modules.dep.temp for writing: No such file or directory What can I do ? Ciao Matthias Sounds like the kernel is missing ext2 support. There is a separate list for Debian support - that's where you should turn for help. Start here: http://wiki.openmoko.org/wiki/Debian#Support Sincerely, Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Bluetooth convenience scripts
Daniel Benoy wrote:
I found a useful python script on Gentoo's boards for using the bluez-utils
d-bus interface for activating bluetooth keyboards so that they will connect
automatically when you turn them on. I've also modified it and created one
that does the same thing for A2DP headsets, and I've decided to share :) The
keyboard one can/must be used in lieu of hidd, so it's for newer versions of
bluez-utils (Available in the testing and unstable feeds)
You also have to bond (pair) the devices first. Instructions for that are
here: http://wiki.bluez.org/wiki/HOWTO/Bonding (Feel free to make a
convenience script for the bonding process too)
You may also have to run:
dbus-send --system --type=method_call --print-reply --dest=org.bluez
/org/bluez/hci0 org.bluez.Adapter.SetTrusted? string:AA:BB:CC:DD:EE:FF (Feel
free to add this to the script)
If you want to use an A2DP headset you can add an entry like this to your
/etc/asound.conf
pcm.bluetooth {
type bluetooth
device AA:BB:CC:DD:EE:FF
profile auto
}
And then you can tell alsa aware applications to use it for output. i.e.:
mplayer -ao alsa:device=bluetooth nifty.mp3
(I believe you can also name it pcm.!default and it will become the default.)
Thanks! This is very helpful.
I'd like to add this to the wiki, but I'm just learning my way around
Bluetooth. Can you help me find the place for it?
Perhaps in
http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Advanced_Audio_Distribution_Profile_.28A2DP.29
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Delete Manual_Debian? (was: Re: GPS device missing in debian)
Chris Jenks wrote: On Thu, 4 Sep 2008, Joachim Breitner wrote: Hi, Manual_Debian is still of interest to people who, well, want to do it manually, or learn more about the system. But if it confuses people then yes, go ahead and delete it. Greetings, Joachim It seems useful to me. Maybe enlarge the disclaimer at the top? This seems like the best solution to me. As a policy, we are trying desperately to make the wiki useful. To do this we have to aggressively reduce the number of pages. Thus my attitude. In this case, though, there seems to be a compelling reason for keeping the page. Thanks all of you for your thoughtful input. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[Fwd: getting error while trying to flash my neo freerunner]
Original Message Subject: getting error while trying to flash my neo freerunner Date: Thu, 04 Sep 2008 19:31:43 +0200 From: Detructor [EMAIL PROTECTED] Reply-To: List for Openmoko community discussion [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hey guys, I hope you can help me, I've the following problem: When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 sometimes the download starts and then I get the error. When I get the neo in June, I could flash it without getting this error. My operating system: Ubuntu 8.04.1 I ask here, because I can't find anything about this error in the www (only 3 entries in google and none of it helps). hope for help Detructor == Hi, What command line did you use? One cause of this error is when you give the wrong argument to dfu-util, e.g. -a u-boot while flashing a kernel image. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: getting error while trying to flash my neo freerunner
Detructor wrote: Am Donnerstag, den 04.09.2008, 11:11 -0700 schrieb Michael Shiloh: Detructor wrote: I've used the command out of the wiki...for example sudo ./dfu-util -a rootfs -R -D ./Om2008.8-gta02-20080904.rootfs.jffs2 I'm using the standard terminal from gnome Hey guys, I hope you can help me, I've the following problem: When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 sometimes the download starts and then I get the error. When I get the neo in June, I could flash it without getting this error. My operating system: Ubuntu 8.04.1 I ask here, because I can't find anything about this error in the www (only 3 entries in google and none of it helps). hope for help Detructor == Hi, What command line did you use? One cause of this error is when you give the wrong argument to dfu-util, e.g. -a u-boot while flashing a kernel image. Michael And is your u-boot a recent version? Although if it's not it will be hard to update until we solve this problem. Does this problem persist for kernel and u-boot too? Can you check the integrity of the image you're trying to flash with md5sum? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support - yep for kernel, too. but with some luck I got the kernel flashed (I tried it 20 times, than it was flashed ;)) - nope I never flashed u-boot and yep it is the correct image (md5 is correct) This could be the cause of your trouble. Your u-boot may be quite out of date. By the way, have you tried flashing with the NOR u-boot? If that works, I would recommend you right away flash a new u-boot into NAND, then use that new u-boot to flash your kernel and rootfs. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: getting error while trying to flash my neo freerunner
Detructor wrote: Am Donnerstag, den 04.09.2008, 12:32 -0700 schrieb Michael Shiloh: Detructor wrote: Am Donnerstag, den 04.09.2008, 11:11 -0700 schrieb Michael Shiloh: Detructor wrote: I've used the command out of the wiki...for example sudo ./dfu-util -a rootfs -R -D ./Om2008.8-gta02-20080904.rootfs.jffs2 I'm using the standard terminal from gnome Hey guys, I hope you can help me, I've the following problem: When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 sometimes the download starts and then I get the error. When I get the neo in June, I could flash it without getting this error. My operating system: Ubuntu 8.04.1 I ask here, because I can't find anything about this error in the www (only 3 entries in google and none of it helps). hope for help Detructor == Hi, What command line did you use? One cause of this error is when you give the wrong argument to dfu-util, e.g. -a u-boot while flashing a kernel image. Michael And is your u-boot a recent version? Although if it's not it will be hard to update until we solve this problem. Does this problem persist for kernel and u-boot too? Can you check the integrity of the image you're trying to flash with md5sum? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support - yep for kernel, too. but with some luck I got the kernel flashed (I tried it 20 times, than it was flashed ;)) - nope I never flashed u-boot and yep it is the correct image (md5 is correct) This could be the cause of your trouble. Your u-boot may be quite out of date. By the way, have you tried flashing with the NOR u-boot? If that works, I would recommend you right away flash a new u-boot into NAND, then use that new u-boot to flash your kernel and rootfs. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, I've tried just 10 seconds ago to flash u-boot via NAND...after three tries, the 4th get it on the phone...after that, I choosed power off and restarted the phone...back in NAND, I tried to flash the rootfs again...but, there was the same error. I don't know why this error occurs, but 2 weeks before, I've flashed the freerunner several times without that problem... errhm, before you ask: the u-boot version that I've flashed is from here: http://downloads.openmoko.org/releases/Om2008.8-update/ Try to flash the NAND u-boot while using the u-boot in NOR. IIRC this was prefereable for some reason. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: getting error while trying to flash my neo freerunner
Detructor wrote: Am Donnerstag, den 04.09.2008, 12:47 -0700 schrieb Michael Shiloh: Detructor wrote: Am Donnerstag, den 04.09.2008, 12:32 -0700 schrieb Michael Shiloh: Detructor wrote: Am Donnerstag, den 04.09.2008, 11:11 -0700 schrieb Michael Shiloh: Detructor wrote: I've used the command out of the wiki...for example sudo ./dfu-util -a rootfs -R -D ./Om2008.8-gta02-20080904.rootfs.jffs2 I'm using the standard terminal from gnome Hey guys, I hope you can help me, I've the following problem: When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 sometimes the download starts and then I get the error. When I get the neo in June, I could flash it without getting this error. My operating system: Ubuntu 8.04.1 I ask here, because I can't find anything about this error in the www (only 3 entries in google and none of it helps). hope for help Detructor == Hi, What command line did you use? One cause of this error is when you give the wrong argument to dfu-util, e.g. -a u-boot while flashing a kernel image. Michael And is your u-boot a recent version? Although if it's not it will be hard to update until we solve this problem. Does this problem persist for kernel and u-boot too? Can you check the integrity of the image you're trying to flash with md5sum? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support - yep for kernel, too. but with some luck I got the kernel flashed (I tried it 20 times, than it was flashed ;)) - nope I never flashed u-boot and yep it is the correct image (md5 is correct) This could be the cause of your trouble. Your u-boot may be quite out of date. By the way, have you tried flashing with the NOR u-boot? If that works, I would recommend you right away flash a new u-boot into NAND, then use that new u-boot to flash your kernel and rootfs. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, I've tried just 10 seconds ago to flash u-boot via NAND...after three tries, the 4th get it on the phone...after that, I choosed power off and restarted the phone...back in NAND, I tried to flash the rootfs again...but, there was the same error. I don't know why this error occurs, but 2 weeks before, I've flashed the freerunner several times without that problem... errhm, before you ask: the u-boot version that I've flashed is from here: http://downloads.openmoko.org/releases/Om2008.8-update/ Try to flash the NAND u-boot while using the u-boot in NOR. IIRC this was prefereable for some reason. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support same result... Ouch. I'm out of ideas. We need help from someone more expert with dfu-util than I. Let me see what I can find. We might also ask on the kernel list and on the IRC channel. Finally, we can take a look in the dfu-util source and see what reasons are for error -71. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: getting error while trying to flash my neo freerunner
Detructor wrote: When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 Is that error copy-and-pasted? A friend is looking through the source and is not finding even [dfu_download anywhere. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: getting error while trying to flash my neo freerunner
When I try to flash the neo on my laptop I get a Starting download: [dfu_download error -71 sometimes the download starts and then I get the error. When I get the neo in June, I could flash it without getting this error. Someone on IRC suggested these. A bit of a long shot, but when all else fails: 1. Try unplugging all other USB devices, in case dfu-util is getting confused 2. Don't use a hub 3. Plug in to the very same USB port that you used when it used to work M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS device missing in debian
Chris Jenks wrote: I installed using the script at http://wiki.debian.org/DebianOnFreeRunner and, after turning on GPS, tried cat /dev/ttySAC1 but this just returns to the prompt without showing any data. Then I found the /dev/s3c2410_serial1 mentioned at http://wiki.openmoko.org/wiki/Manual_Debian#GPS but now I realize that page is obsolete (relative to the first). If http://wiki.openmoko.org/wiki/Manual_Debian is obsolete it should be deleted. Since I've not installed Debian yet I'm not qualified to make that decision. Can I get some confirmation that Manual_Debian is obsolete so that it can be deleted? Thanks, Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Tony, any idea what that error means? I searched a little and failed to find. Lynn Nguyen wrote: I get: [ 459.596147] usb 3-1.3: new full speed USB device using uhci_hcd and address 27 [ 459.744465] usb 3-1.3: device not accepting address 27, error -71 I don't have any USBs showing up in tty when I plug it in. Lynn On Mon, Sep 1, 2008 at 7:59 PM, Michael Shiloh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Lynn Nguyen wrote: I tried the sequence but still the same errors. Should I have a /dev/ttyUSB1 when I plug in the debug board? because i dont... Lynn Did you check other devices? It may have shown up on a different tty. what does dmesg or tail -f /var/log/messages say as you plug in the USB cable? Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: New battery semi-charged but not charging, is protection-circuit broken?
ankostis wrote: On Mon, Sep 1, 2008 at 6:28 AM, Michael Shiloh [EMAIL PROTECTED] wrote: Did you update u-boot and kernel? There was a bug awhile back causing USB insertions to be only partially recognized. I have not updated UBoot and i cannot do it anymore since the battery has fallen significantly making it impossible to enter into USB ACM. I've used kernel from 2008.8 and FSO (2 days ago), nothing too recently. I thinki i've seen the bug you mention, when it requires to insert the USB twice in order to enter 'Charging status. But yet, no real current flows into the battery and the battery's reported capacity remains 0. Yesterday, the current_now started to show some non-zero values, but judging from the voltage_now, the battery did not actually charge. Michael, I would really like to know if there is any possibility of reviving the battery or if i should definitely contact the reseller for a new one, since i live in a different country from the reseller it and it will take some time to receive a new battery. If you're feeling adventurous, try to revive the battery using Joerg's unofficial instructions [1], then update u-boot and kernel, then see if charging works better. If you're not feeling adventurous, ask your reseller for a new battery, and if it works, then return the old one as faulty. Michael [1] http://wiki.openmoko.org/wiki/Charging_battery_directly ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: New battery semi-charged but not charging, is protection-circuit broken?
ankostis wrote: On Mon, Sep 1, 2008 at 7:14 PM, Michael Shiloh [EMAIL PROTECTED] wrote: ankostis wrote: On Mon, Sep 1, 2008 at 6:28 AM, Michael Shiloh [EMAIL PROTECTED] wrote: Did you update u-boot and kernel? There was a bug awhile back causing USB insertions to be only partially recognized. I have not updated UBoot and i cannot do it anymore since the battery has fallen significantly making it impossible to enter into USB ACM. I've used kernel from 2008.8 and FSO (2 days ago), nothing too recently. I thinki i've seen the bug you mention, when it requires to insert the USB twice in order to enter 'Charging status. But yet, no real current flows into the battery and the battery's reported capacity remains 0. Yesterday, the current_now started to show some non-zero values, but judging from the voltage_now, the battery did not actually charge. Michael, I would really like to know if there is any possibility of reviving the battery or if i should definitely contact the reseller for a new one, since i live in a different country from the reseller it and it will take some time to receive a new battery. If you're feeling adventurous, try to revive the battery using Joerg's unofficial instructions [1], then update u-boot and kernel, then see if charging works better. If you're not feeling adventurous, ask your reseller for a new battery, and if it works, then return the old one as faulty. Michael [1] http://wiki.openmoko.org/wiki/Charging_battery_directly I've tried this already since the current voltage has fallen below the booting threshold, by supplying extra current from a separate supplier directly to the battery receptors. Yet i think Michael, that we are not dealing with a dead battery that needs reviving, but with a broken protection circuit that does not accept the charging current. If i could suggest a solution that would be first to deeply-discharge the battery in order to reset the protection-cpu, and then start charging it. Is this a viable solution? Interesting theory. I don't know how the protection circuit works, and whether deeply-discharging will reset it. You might post this question on the kernel list - the people who would know this should all be there. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO rox!
Linus Gasser wrote: sparky mat a écrit : I know OM2008.8 is the flagship distro at the moment, but FSO so totally rocks. :-) . Here are the things that I liked about it 1) GPRS!! The d-bus interface makes it so much simpler/easier to enable GPRS. 2) Aux button locks the screen. Screen lock is a must for me, and using the Aux button makes a lot of sense! 3) TangoGPS by default. This is my fav. GPS app so far :-) 4) Zhone. I actually like the big and bright user interface of Zhone. It may be only a test UI, but I love it. Neat and simple. 5) Terminal + QWERTY keyboard. I would like to try it. For the moment I have OM2008.8 installed, also with TangoGPS. Where did you get the kernel/images for FSO? I searched to no avail... Hi! If you visit http://wiki.openmoko.org/wiki/Distributions and look at http://wiki.openmoko.org/wiki/Distributions#FSO_-_freesmartphone.org you will be directed to http://downloads.openmoko.org/framework/milestone2/ or http://shr.bearstech.com/ Have fun! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: HW problems ...
Pietro Abate wrote: forgot to say. The datecode on my freerunner is 20080728 It also powers up with the charger and no battery. What is the version of your hardware? [EMAIL PROTECTED]:~# libgsmd-tool -m shell libgsm-tool - (C) 2006-2007 by Harald Welte and OpenMoko, Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY rv # # Get revision revision: HW: GTA02BV5, GSM: Is the wiki now outdated ? pp On Fri, Aug 22, 2008 at 05:14:30PM +0200, Pietro Abate wrote: Hi all, I've read of the hw problems in the wiki. Now I got my freerunner the other day and I can boot without a battery (while reading the wiki, I understood that this wasn't possible) and I can see a tiny soldering between the 3rd and 4th pin of the sd card (this should be related to the GPS problem). Have these two HW bugs been fixed in the new freerunners shipped recently ? This news would make me happy :) I don't know, but other readers of this list will know and respond. And a last question. Can I use the freerunner without a gsm sim card ? Yes ATM I don't have one and it seems the default system gets stuck in the gsm registering loop. As expected with no SIM card. You can purchase a pay-as-you-go for as little as $10, if you want. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: possible GSM buzz hardware fix (was Sales?)
Joerg (or anyone else that might know): Would just desoldering the mic part of the jack also fix the problem? Assuming I can eventually get a bluetooth headset working, I don't anticipate ever using the headset jack for anything other than listening to audio; so, I don't need the mic part. Before any of you start doing this be aware: * My understanding is that the jack as the cause of the GSM buzz has NOT been confirmed to everyones satisfaction. * If you apply a soldering iron to your Freerunner and damage the Freerunner, I'm pretty sure we won't replace it for free. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: HW problems ...
Nicolas Dufresne wrote: Le vendredi 22 août 2008 à 18:50 +0100, Zack Mollusc a écrit : Mine powers up on the mains charger too! Mine says date code 20080717 and arrived complete with the cap soldered on the sd card socket. I can relax about letting the battery going flat now :-) Is this fixable (by experts) on previous phones ? I wouldn't mind to pay for the service ... this way I won't get paranoïd when I'm far from a USB source. Hi Nicolas, I'd sure like to know what version of hardware you have. There was some discussion of adding a larger capacitor somewhere, I'm not sure if that was the only modification or in fact whether it helped at all. There was also a lot of work being done on the software side by delaying powering up various components until sufficient power was confirmed. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GNOME on Debian/Freerunner
sparky mat wrote: And here.. we... go http://www.sparkymat.net/images/gnome1.png http://www.sparkymat.net/images/gnome2.png http://www.sparkymat.net/images/gnome3.png http://www.sparkymat.net/images/gnome4.png http://www.sparkymat.net/images/gnome5.png http://www.sparkymat.net/images/gnome6.png That is just beautiful. I want. Please send me your notes and I'll turn into a wiki page (while I do it myself). Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GNOME on Debian/Freerunner
sparky mat wrote: Not very productive, but I have GNOME running on my Freerunner!! :-) . I should say it feels so good. Is it ok to attach images to mails to the mailing list? Way cool. If you don't have the time to make a nice wiki page, please post here whatever notes you have and I'll turn them into a wiki page. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
arne anka wrote: Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need shouldn't be to hard -- but where to put the image? it would at least be about 512mb -- with a reasonable number of downloads ones traffic limit might be reached very soon. I'd be happy to host this on downloads.openmoko.org. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Openmoko Flasher - Unable to Flash Root File System - Error 60
Marcus, I'll echo what Nikolaus says and much stronger: It is a wiki, and depends on community input. Your experience will help us, so thanks for volunteering. We do have quite a number of Mac users who will appreciate your work. Thanks, Michael Dr. H. Nikolaus Schaller wrote: Well it was mostly me :-) During 1973 ages. Plus some others who updated networking issues. But feel free to add things. It is a Community Wiki... Nikolaus Am 13.08.2008 um 17:45 schrieb Marcus Stong: Thanks for the help with getting dfu-util working in Terminal on the Mac. Is anyone currently managing the Mac OS X page in the wiki. These better instructions for running dfu-util should be posted. I'll volunteer to update it and a couple other things if no one is currently keeping that page up to date. Marcus Rod Whitby wrote: Dr. H. Nikolaus Schaller wrote: Am 13.08.2008 um 14:35 schrieb Rod Whitby: Please advise people to use '-a rootfs' instead of '-a 5', since - a 5 will break the next time that Openmoko decides to change the mtd layout (as did happen between GTA01 and GTA02). Ah, that explains everything. Does someone have a good list of all allowed values of -a? And, are they the same between GTA01 and GTA02? At least the following are: u-boot, kernel, rootfs -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Compiling C on the phone
Dirk Bergstrom wrote: Andrew Chu wrote: Sounds like you're missing binutils, or symlinks to the assembler and linker: opkg install binutils then: ln -s /usr/bin/arm-angstrom-linux-gnueabi-as /usr/bin/as Actually, there's a binutils-symlinks package that does all that. Dunno why it's a separate package... Hope that helps, It does indeed. hello.c built just fine, and so did the pycrypto stuff. I had to install python-compile, but then the install went through as well. Thanks very much. I'll write this up in the wiki later today. Thanks Dirk. This is very cool. The ability to compile on my phone is something I want to be able to show off. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Compiling C on the phone
sparky mat wrote: Thanks Dirk. This is very cool. The ability to compile on my phone is something I want to be able to show off. M I agree! I am compiling Ruby 1.9 on my phone!! Please wikify! ___ 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: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Olivier Berger wrote: Andy Green [EMAIL PROTECTED] writes: Somebody in the thread at some point said: | Could someone point to these valid u-boot*.bin files please ? | http://buildhost.openmoko.org/daily/freerunner/200808/20080804/uboot-gta02v5-latest.bin Alright, it's the one I had picked. | and got a message displayed advertising some april version (which I | unfortunately didn't write down)... so I'm puzzled :( Are you sure that it is not 4th Aug -- looks like 8th April in some countries? I doubt the latest symlink is broken for so many months. Might be that... No way to start over :( | How could I check which version I'm using on my FR and if it's | up-to-date or not ? At the moment we don't stamp the image with the git head of the sources it came from, we should move to that. I guess so. There's a build date on the menu Well... should it read U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) on first line, then ? ... I'd expect something closer from now :-/ and coming out of the serial console as you saw. Same hopefully ;) : GTA02v5 # version U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) At the moment this one is up to date for today and has the USB Insane Spam Mode fixes. http://buildhost.openmoko.org/daily/freerunner/200808/20080804/u-boot-gta02v5-1.3.1+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin Tried it and get the same versions (means the link are OK on the download site). I thought about trying something : # ./dfu-util -a u-boot -R -U current-uboot.bin # strings current-uboot.bin | grep git U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4 2008 - 02:33:52) Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb So obviously, the version on u-boot's prompt is not meanlingful, then... :( Should I file a bug report ? I would consider it a bug that the version on u-boot's prompt is not meaningful, although I know in some cases that comes out of the source control package automatically and is not easily fixed. Is that the case in our case, or is this an error that can be fixed? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | # strings current-uboot.bin | grep git | U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4 2008 - 02:33:52) | Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb | | So obviously, the version on u-boot's prompt is not meanlingful, | then... :( | | Should I file a bug report ? | | | I would consider it a bug that the version on u-boot's prompt is not | meaningful, although I know in some cases that comes out of the source | control package automatically and is not easily fixed. Is that the case | in our case, or is this an error that can be fixed? It turned out the guy was booting his NOR U-Boot and reporting the version data from that. He said his NAND U-Boot version string when he did see it was good (ie, had the correct date and git hash). Ah. Then all is well. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS issue final state?
Christoph Anton Mitterer wrote: Hi. Is it possible that one of the OpenMoko team members put up a wiki-page (probably protected from changes) or something similar,... and provide there the most recent, official and authoritative information about the GPS issue? Everybody knows about the two fixes (SW and HW) but a lot of different information is floating around what they actually do, which of them is definitely confirmed to work, whether it is suggested to apply both or only one of them or if only both together can give the best results. I've subscribed all the ML's and read all posts,.. but I think this is still not clear. I can also remember an eMail from (I think) Joerg where he suggested to not apply the HW fix yet, as it's not yet official. What's the current state on the HW fix? Did you already negotiate if: - users should apply it themselves - this is done by sellers (Pulster, OM Shop, etc.)? - etc ? What will happen to the warranties? Which is the recommended capacitator (I mean which manufacturer, the type and size is already listed in dozen places,..)? Would be really nice to have all this in a central and protected location, where only official OM team members can write to. Thanks, Chris. I'm part of Openmoko and I'm not clear on the fix either. I'm trying to come up with two side-by-side tests we can run, one with the SW fix, one without, that is easy to document and requires the same distro, then test w/ two different kernel images (one with, one without the SW fix). Then we'll ask everyone to run this test and post their results, with and without an SD card installed. So 4 tests all together. Then we might get a sense of whether the SW only fix is sufficient. Any advice appreciated. M ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Freerunner (GTK2007.2) has suddenly become unbootable
casaubon wrote: Niccolo Rigacci wrote: I got the same problem, solved flashing a kernel image via the U-Boot menu. Here my notes (in Italian, sorry): http://www.rigacci.org/wiki/doku.php/doc/appunti/hardware/freerunner#flashing_del_kernel I got the missing kernel image (uImage-something.bin) from the http://buildhost.openmoko.org/daily/freerunner/ and followed the instruction here: http://wiki.openmoko.org/wiki/Flashing_Openmoko Remember also to copy the image file into /boot/ once you can ssh the Neo again. -- Niccolo Rigacci Thanks for the help, but I am still having problems. I followed the instructions here: http://wiki.openmoko.org/wiki/Boot_from_sd_card Hey Jon, Why introduce another unknown into the equation? I recommend you follow Niccolo's advice and follow the instructions at http://wiki.openmoko.org/wiki/Flashing_Openmoko If you can't boot into NAND FLASH, use the failsafe u-boot image in NOR FLASH. Regards, Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: With new freerunner, I cannot make outgoing calls or recieve incomming calls with Att cell service.
Hi Greg, The first thing to do is take the SIM card that is failing to ATT and ask them for a new SIM card. It is a well known problem that as parts of the cellphone system are upgraded, old SIM cards may not work. The other thing to do is to add details of your failed SIM card to our database at http://wiki.openmoko.org/wiki/FreeRunner_unable_to_work_with_3G_SIM_cards Write back with the results of this test and we'll go from there. Thanks, Michael Shiloh Gregory Meyer wrote: I have two SIMs. One is a T-Mobile pre-paid, and it works fine. The other is an ATT 3G and it doesn't work. When that SIM is in, the Freerunner just says registering in the upper left of the screen. On Sat, Jul 19, 2008 at 1:17 PM, Greg Bonett [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver, Does the phone indicate that its connected to a network or (name of the carrier) or does it say registering.. What kind of SIM card do you have? - -Greg MR BROWN wrote: I recieved my new freerunner on Friday July 18. I flashed the new phone with all new images, inserted my 3G sim card and tried to make and recieve calls. There was no response in either case. I have read that a new sim card is one possible solution so I will pick one up in a little while. Anyone have any ideas? Oliver ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SSH into Freerunner
In summary from other posts: 1. Since Freerunner is on subnet 192.168.0.*, you must configure your USB0 port on the same subnet (not '1') 2. You need to set up a route to 192.168.0.202 via usb0 3. I am able to route 192.168.0.202 via usb0 while the rest of my network is 192.168.0.* via eth1, even though this seems a little illogical. I do this: sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0 sudo route add 192.168.0.202 usb0 shawn sullivan wrote: I've been unable to SSH into my phone. I did: ifconfig usb0 192.168.1.200 netmask 255.255.255.0 but when I do: ssh [EMAIL PROTECTED] it can't find the host. i've tried disabling the firewall; no dice. Here's my routing table: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 default dslmodem.domain 0.0.0.0 UG0 0 0 eth0 It appears that there is no route to the USB port, but I'm not sure how to enable that. Can someone help me out? I'm running Ubuntu. I did verify that the phone is on USB0, but I cannot get any results when I ping the IP address. thx . . .shawn Colan Lash wrote: Thanks to everyone, who responded. It turned out, that disabling the firewall fixed the problem. If anyone is still interested, this is my routing table. desktop:~$ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 *255.255.255.0 U 0 0 0 eth0 192.168.0.0 *255.255.255.0 U 0 0 0 usb0 link-local *255.255.0.0 U 0 0 0 eth0 default192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Colan On Wed, Jul 16, 2008 at 6:14 PM, Stroller [EMAIL PROTECTED] wrote: On 17 Jul 2008, at 00:57, Colan Lash wrote: ... I can ping 192.168.0.200 and get a response. This is pinging the desktop machine. But if I ping 192.168.0.202, I get and Operation not permitted error: desktop:~$ ping -I usb0 192.168.1.202 PING 192.168.1.202 (192.168.1.202) from 192.168.1.103 usb0: 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted --- 192.168.1.202 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms First two hits indicate firewall: http://www.google.com/search?q=ping:+sendmsg:+Operation+not+permitted Is Shorewall installed on this machine? Can you `/etc/init.d/iptables stop`? I would be grateful if you could post in PLAIN-TEXT to the mailing list. For parts of your message You have chosen a font which is unreadably small on my system. If you post in plain text then _I_ can choose the font size in which I wish to read your message. Stroller. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
