Re: Installing v35
Hi On Tue, 2012-01-31 at 18:45 +1100, Liz wrote: Sadly, I don't have Power and Aux buttons confused. I don't have access to NAND from the Power button. Both boot methods start the NOR bootloader. If you can't start the NAND bootloader and your Freerunner starts the NOR bootloader everytime, it may be possible that your AUX button got stuck somehow. A friend had the same problem with his brand new Freerunner. He was able to fix the problem himself, but he needed to replace (or resolder, don't remember) the AUX button. Are you able to cycle through the menu items in the bootloader by pressing AUX? If you can your AUX button is working. Korbi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First SSH to FR: Permission denied
Hi Try 192.168.0.202, the IP you tried is your desktop :) I've also done this many times until i added this line to /etc/hosts on my desktop: 192.168.0.202 om cu Korbi On Wed, 2009-06-10 at 20:17 -0500, Mike wrote: Hello -- I just got the FR. Very nice! I am trying to SSH to FR to check the firmware version. I can ping 192.168.0.200 with 0% loss. However, when I ssh r...@192.168.0.200 and enter either blank (as suggested in the Wiki) or root password at the prompt I get Permission denied, please try again. What is the problem? Thank you for your time, Mike. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Korbinian Rosenegger k.roseneg...@schmidham.net 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: Debuzzing
Hi Is it possible to bring the devices to you in person? This could save shipping costs for all of us who can use the S-Bahn without additional costs or pass the A995 regularly since it's about 1 km from the next S-Bahn station (Deisenhofen) or less than 4 km from the A995 to your address in Oberhaching (distances measured in Google Maps). cu Korbi On Tue, 2009-04-28 at 22:30 +0200, Dr.H.NikolausS wrote: Dear community, it is the philisophy of Golden Delicious Computers to find solutions for important topics that the community has and can't solve alone. Therefore, we (Golden Delicious Computers and TRIsoft) have worked behind the scenes and are close to offer a Buzz rework solution that can in principle serve all Freerunner Owners in the EU harmonized market. 1) We have identified a very good professional SMD rework company in Munich, Germany who are capable and willing to do the rework at low cost and high quality, but only if we deliver batches of collected devices. Since we are experienced in collecting incoming and outgoing shipments, the combination is the solution. 2) Therefore we plan to offer this service to all Openmoko owners within the EU harmonized market / tax union (to avoid re-import/export hassle). Please note that there will be a rework fee. The final price is not yet clear (expected to be less than 30 EUR incl. shipment) because we are in intensive discussions with Openmoko how they can help to reduce this fee for you. 3) Rework will take approx. 1 week and could start immediately, provided we get the promised replacement components in time. 4) If you are interested, please register yourself and your device at the following link. We will then follow up with details about handling, address to send to, time schedule, final pricing etc. http://www.handheld-linux.com/wiki.php?page=Buzz-Rework So stay tuned, Nikolaus Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community 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: Workaround for using speech-dispatcher without blocking /dev/dsp for other apps
Hi On Sun, 2009-01-18 at 12:08 +0100, Francesco de Virgilio wrote: Interesting workaround ;) Thanks :) Pratically, the only modules to cheange from alsa to oss (for me) are: - espeak.conf - festival.conf - flite.conf - ibmtts.conf But, for a n00b like me, it is not clear how the /etc/init.d/speech-dispatcher file should be adapted. Could you provide directly the adapted file? It's attached to this mail. I'm also setting LANG to de...@utf-8 for getting correct german speech output, otherwise Straße would be spoken as Stra-s-z-e for example. So you may also set this to your language. cu Korbi speech-dispatcher Description: application/shellscript 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
Workaround for using speech-dispatcher without blocking /dev/dsp for other apps
Hi Many of you had problems with openmoocow not mooing or lightsaber not starting and complaining about No available audio device. This is often (always?) caused by speech-dispatcher blocking /dev/dsp. So here's a workaround for using speech-dispatcher without blocking the sound device for applications that use OSS. It's using the OSS output of speech-dispatcher and starting it with the alsa-oss wrapper for using ALSA. The reason for this is because the OSS output opens the sound device only when needed for speech output while the ALSA output keeps it open all the time (which wouldn't be a problem when using ALSA only since then the drivers can do mixing, but the OSS compability layer in the kernel does not support mixing (as fas as i understood it, has to be done in userspace with dmix)). I tried it with dmix on my freerunner, but it sounds rather bad, so I found this workaround. Steps to do: - Install alsa-oss and add a missing link: opkg install alsa-oss ln -s /usr/lib/libaoss.so.0 /usr/lib/libaoss.so - Change the output method of all used modules in /etc/speech-dispatcher/modules/*.conf from alsa to oss - Use the aoss wrapper in /etc/init.d/speech-dispatcher. Do this twice there (once for start in line 18, once for restart in line 31). Change the second line from --exec $DAEMON to --exec aoss -- $DAEMON: start-stop-daemon --start --quiet --pidfile $PIDFILE \ --exec aoss -- $DAEMON - Restart speech-dispatcher - Enjoy openmoocow or ko-lightsaber while speech-dispatcher is running I hope I haven't forgot a step here. If any of you has a better solution please let us know. (Of course you also can run lightsaber or openmoocow with the aoss wrapper without touching speech-dispatcher. Maybe this is the better solution, but then you have to touch every app that uses OSS, and maybe you'll get similar bad quality as with dmix like I did.) Maybe someone knows if it is possible to let speech-dispatcher behave the same with the alsa output method to open the sound device only when it's needed? Have fun :) Korbi 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: Freerunner LightSaber
Hi On Sat, 2009-01-17 at 18:30 +0100, Francesco de Virgilio wrote: Great app, but... On 2008.12 I've installed python-pygame and this follows when I try to run the program: r...@om-gta02:~# export DISPLAY=:0 r...@om-gta02:~# ko-lightsaber Traceback (most recent call last): File /usr/bin/ko-lightsaber, line 32, in module pygame.mixer.init() pygame.error: No available audio device Any tip? Try stopping speech-dispatcher or running lightsaber with the aoss wrapper. Also have a look at my other mail (Workaround for speech-dispatcher) when this works for you. cu Korbi 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: [Om2008.9] runaway proc events/0 automatic reboot
Hi On Thu, 2009-01-15 at 16:21 +0100, Matthias Apitz wrote: my small script monitoring the events/0 proc is logging as well when the runaway occures, date and uptime: # cat runaway.log Wed Jan 14 01:20:04 CET 2009 01:20:04 up 18:26, 0 users, load average: 0.42, 0.63, 0.49 Thu Jan 15 14:49:19 CET 2009 14:49:19 up 18:26, 0 users, load average: 0.53, 0.76, 0.64 do you see the interesting point? the problem is uptime-driven! 18 * 3600 + 26 * 60 = 66360 Interesting, since it is only ~14 Minutes above 65536 and your script checks about every 10 Minutes (i think). So maybe there's a unsigned int overflow or a similar problem somewhere? cu Korbi 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: buzz fix (was: Pulster offer - Freerunner now 249 eur)
Hi Christoph, On Sun, 2009-01-11 at 12:55 +0100, Matthias Apitz wrote: Could you please also make an offer for the hardware buzz fix in DE: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf Would be great! It would be great if you could offer all hardware fixes that are possible to do like the GPS-Fix for all GTA02v5 owners: http://wiki.openmoko.org/images/5/5b/SOP_for_GPS_capacitor_rework.pdf http://wiki.openmoko.org/images/d/dd/Gta02_gps_10pf_rework_sop.pdf Even the software fix works fine, when you already have heated up your soldering iron for the buzz fix it should only take few minutes to add the capacitor :) I'm not sure if there are other bug fixes, but if there are one, offer them, please :) cu Korbi 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: [FSO][M4] Missing Components?
Hi On Tue, 2008-11-11 at 16:59 -0800, SCarlson wrote: I've just flashed openmoko-fso-illume-image-glibc-ipk--2008-om-gta02.rootfs.jffs2 and its accompanying uImage. The machine loads, and I see Alarm,Snapshot,Terminal icons. Zhone does not run.(even after several reboots). I could not find it on the filesystem with (find | grep zhone)(from root). Am I missing something here? I'm probably missing something horribly obvious, so I'd thought I'd ask. I had the same problem, it's missing in the image, but you can install it by logging in over ssh and use opkg: opkg update opkg install zhone Ignore the errors about failing signature checks when updating the package lists. cu Korbi 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: [om2008.9/FDOM] Charging or Long Power On = Crashing?
Hi On Mon, 2008-10-13 at 22:20 -0700, Boris Wong wrote: I'm working on a theory of prolonged charging leading to the crashing of the Freerunner in FDOM/om2008.9. I'm not saying it's definite, but I have had some experiences of my phone ending up in kernel panic and where the screen would not turn on after overnight charging without suspension. Here is the scenario: I plug in my Freerunner to the wall adaptor, to let it charge overnight. I do not use suspension, but I do have the screen turn off automatically. I sometimes don't unplug/plug it in again to make the charging indicator (red light and the charging symbol on the screen) appear. In the morning (6+ hours later), the phone will be in kernel panic or the device will be on without the screen (calls and things get through, monitor does not come on). The questionable theory: Is there any chance that, since the kernel is not aware that the device is charging (even though the device still charges to full), will create crashes or reverse the loop of the battery indicators? I'm aware that this is a smart battery which can dish out statistics. If the FR does not know that it is charging, but the power is going up, I might think that that may cause problems with the logging and power handling from the kernel. Just a theory, but I really want to get rid of kernel panics and crashes after not shutting down for a long time. Any other theories floating out there that we might want to consider? -Boris I have the same problem, charging my Freerunner from 40-50% remaining battery let it freeze almost reliable. And just like you I (normally) don't use suspend. But sometimes I also have freezes when it runs some time, and sometimes after rebooting it it freezes again within minutes. This mostly happened when it got power over USB (500mA over car adapter, battery was fully charged at that time IIRC), and it was noticeable warm at the back and front. Another freeze was a few weeks ago on a warm sunny day when I was outside with the freerunner in my pocket, and it also got pretty warm. At all times I had GPS turned on (except for the freezes at charge time. So one of my theories is a thermal problem, but a short test was not able to prove that, although the Freerunner froze after reaching 100% (started at about 40%), the day before it froze at 25%, charging was started at 20%. At that time I ran battery.py (available somewhere in the wiki), also I'm running this program mostly when charging, but the freezes seem to be more unlikely when not running it. This brings me to my second theory, something like a race condition in the battery driver or somewhere, since battery.sh polls the bat status quite often. If it should matter, I'm running Om2008 with the latest updates, but my Freerunner with freezes Om2008 since I have it. I can't tell anything about Om2007 because I installed Om2008 right after unpacking and eating my gummi bears ;) Thanks Christoph! :) cu Korbi 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: Extended battery pack
Hi community :) On Thu, 2008-08-21 at 12:31 +1000, Robert William Hutton wrote: In order to use TangoGPS over extended periods, I created myself an extended battery pack for the Neo FreeRunner from bits and pieces I had lying around. Check out my blog post for instructions: http://helms-deep.cable.nu/~rwh/blog/?p=42 Nice project, power everywhere where you can get AA batteries :) For those who don't want to build a battery pack or who are just to lazy to do that, here's a small rechargeable USB power pack, 2000mAh capacity and 1000mA output current, for 18,50 Euro: NAVILOCK 41406 http://www.reichelt.de/?ARTICLE=80419 And another one from APC, with similar specifications, but higher output current and an included USB charger, for 46,95 Euro: APC UPB10-EC http://www.reichelt.de/?ARTICLE=74033 I guess Reichelt is only interesting for Germany since you have to order at least for 150 Euro otherwise, and also shipping will be more expensive, but I'm sure you can find these or similar products in other shops. Happy Freerunning :) cu Korbi 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
