New home for the New FDOM
hexdump /dev/input/event2 produces no output. If you're using FDOM try replacing neod with a different copy to see if that solves it. there was previously no file called /usr/bin/neod cd /tmp wget http://westhoffswelt.de/data/blog/moko_eightball/neod cp neod /usr/bin/neod chmod u+x /usr/bin/neod I did this and rebooted. No change. Should there be an executing process running neod? There isn't in any case. I tried running it from a terminal session and got: ** (neod:1544): DEBUG: opened 3 input nodes. ** (neod:1544): DEBUG: added fd 4 to list of watchers ** (neod:1544): DEBUG: added fd 5 to list of watchers ** (neod:1544): DEBUG: added fd 6 to list of watchers ** (neod:1544): DEBUG: mainmenu powersave reset ** (neod:1544): DEBUG: setting debug output to false ** (neod:1544): DEBUG: mainmenu powersave reset ** (neod:1544): DEBUG: requested to set display brightness 100 ** (neod:1544): DEBUG: backlight_node_dir = pcf50633-bl ** (neod:1544): DEBUG: detected backlight in sysfs as '/sys/class/backlight/pcf50633-bl/brightness' ** (neod:1544): DEBUG: scanned maximum brightness for '/sys/class/backlight/pcf50633-bl/brightness' = '63' ** (neod:1544): DEBUG: writing '63' to '/sys/class/backlight/pcf50633-bl/brightness' ** (neod:1544): DEBUG: panel mainmenu sound init W: client-conf.c: Failed to open configuration file '/etc/pulse/client.conf': No such file or directory ** (neod:1544): DEBUG: mainmenu sound state callback. state = 1 ** (neod:1544): DEBUG: sound init ok. threaded mainloop started ** (neod:1544): DEBUG: mainmenu sound state callback. state = 5 ** (neod:1544): DEBUG: neod_buttonactions_initial_update ** (neod:1544): DEBUG: charger already inserted Any other suggestions? Thanks, Jonathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
I've also tried FDOMizer yesterday, and I had to patch it by hand in a few cases. Mainly, I had to update a few download links from angstrom-distribution.org . Citando Jonathan Schultz [EMAIL PROTECTED]: I just tried updating my FDOM using FDOMizer from the 20080927 version and have had some gains but a few losses and problems. Some of the applications work but others (notably GnuChess and Openmoocow) don't. In particular GnuChess just goes and consumes all available CPU without apparently doing anything. OpenMooCow doesn't appear to do anything either but at least doesn't take any CPU time. I'm guessing here but I'd think that all those forced dependencies are likely to be causing problems. For example I only have gtk+ v 2.10.14-r2 instead of 2.12.11; libglib-2.0.0 v 2.6.16.1-r4 instead of 2.16.4; libcairo2 v 1.4.10-r0 instead of 1.6.4. Should I be using a different repository here? There were a couple of files that the script attempted to download from angsgtrom that weren't available. Curiously enough the files that are available are older versions than those requested by the script. These are: http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-protocol-msn_2.5.1-r0.1_armv4t.ipk http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-libjabber_2.5.0-r0_armv4t.ipk There was something funny about the rc.local file, which the script update-rc.d expected to find in /etc/init.d but which were in /etc I copied it then re-ran update-rc.d and things looked a bit better. I suspect that I'd be better off abandoning the FDOMizer script and reinstalling the latest version, which seems a pity because update scripts are a great idea. Cheers, Jonathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Please send it to me and I will upload it, :) El jue, 30-10-2008 a las 11:07 +, Vasco Névoa escribió: I've also tried FDOMizer yesterday, and I had to patch it by hand in a few cases. Mainly, I had to update a few download links from angstrom-distribution.org . Citando Jonathan Schultz [EMAIL PROTECTED]: I just tried updating my FDOM using FDOMizer from the 20080927 version and have had some gains but a few losses and problems. Some of the applications work but others (notably GnuChess and Openmoocow) don't. In particular GnuChess just goes and consumes all available CPU without apparently doing anything. OpenMooCow doesn't appear to do anything either but at least doesn't take any CPU time. I'm guessing here but I'd think that all those forced dependencies are likely to be causing problems. For example I only have gtk+ v 2.10.14-r2 instead of 2.12.11; libglib-2.0.0 v 2.6.16.1-r4 instead of 2.16.4; libcairo2 v 1.4.10-r0 instead of 1.6.4. Should I be using a different repository here? There were a couple of files that the script attempted to download from angsgtrom that weren't available. Curiously enough the files that are available are older versions than those requested by the script. These are: http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-protocol-msn_2.5.1-r0.1_armv4t.ipk http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-libjabber_2.5.0-r0_armv4t.ipk There was something funny about the rc.local file, which the script update-rc.d expected to find in /etc/init.d but which were in /etc I copied it then re-ran update-rc.d and things looked a bit better. I suspect that I'd be better off abandoning the FDOMizer script and reinstalling the latest version, which seems a pity because update scripts are a great idea. Cheers, Jonathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
New home for the New FDOM
I believe it is a combination of inestability of accelerometers and sound if any of those elementes doesn't work mookow, still silent on even it doesn't open at all, it uses to work with the Neo just rebooted. as experiment you can execute the Moocow throug terminal and if no detect any sound device it will log the moos in the terminal. When I execute openmoocow through the terminal I see no output whatsoever. Is it supposed to open a screen or does it only do sound? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
A screen should show up. It won't if your accelerometers aren't working. To check this run: hexdump /dev/input/event2 which should give you output from the accelerometer that openmoocow uses. If you're using FDOM try replacing neod with a different copy to see if that solves it. Some people have reported accelerometers starting only once every few boots so try rebooting. Here's a neod that works for me: cd /tmp wget http://westhoffswelt.de/data/blog/moko_eightball/neod cp neod /usr/bin/neod chmod u+x /usr/bin/neod Happy mooing! -Nick On Fri, Oct 31, 2008 at 9:49 AM, Jonathan Schultz [EMAIL PROTECTED]wrote: I believe it is a combination of inestability of accelerometers and sound if any of those elementes doesn't work mookow, still silent on even it doesn't open at all, it uses to work with the Neo just rebooted. as experiment you can execute the Moocow throug terminal and if no detect any sound device it will log the moos in the terminal. When I execute openmoocow through the terminal I see no output whatsoever. Is it supposed to open a screen or does it only do sound? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
New home for the New FDOM
I just tried updating my FDOM using FDOMizer from the 20080927 version and have had some gains but a few losses and problems. Some of the applications work but others (notably GnuChess and Openmoocow) don't. In particular GnuChess just goes and consumes all available CPU without apparently doing anything. OpenMooCow doesn't appear to do anything either but at least doesn't take any CPU time. I'm guessing here but I'd think that all those forced dependencies are likely to be causing problems. For example I only have gtk+ v 2.10.14-r2 instead of 2.12.11; libglib-2.0.0 v 2.6.16.1-r4 instead of 2.16.4; libcairo2 v 1.4.10-r0 instead of 1.6.4. Should I be using a different repository here? There were a couple of files that the script attempted to download from angsgtrom that weren't available. Curiously enough the files that are available are older versions than those requested by the script. These are: http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-protocol-msn_2.5.1-r0.1_armv4t.ipk http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libpurple-libjabber_2.5.0-r0_armv4t.ipk There was something funny about the rc.local file, which the script update-rc.d expected to find in /etc/init.d but which were in /etc I copied it then re-ran update-rc.d and things looked a bit better. I suspect that I'd be better off abandoning the FDOMizer script and reinstalling the latest version, which seems a pity because update scripts are a great idea. Cheers, Jonathan [EMAIL PROTECTED]:~/FDOMizer# ./FDOMizer This script will actualize a raw 2008.X distribution or any previous version FDOMin the FDOM20081023 version Select your current version: 1) OpenMoko_Release 3) FDOM20080913 5) FDOM20080927 2) FDOM20080905 4) FDOM20080925 6) fixmeonlyplease #? 5 Downloading http://downloads.openmoko.org/repository/Multiverse/Packages.gz Inflating http://downloads.openmoko.org/repository/Multiverse/Packages.gz Updated list of available packages in /var/lib/opkg/daily-Multiverse Downloading http://downloads.openmoko.org/repository/Multiverse/Packages.sig Signature check failed Downloading http://downloads.openmoko.org/repository/Om2008.8/all/Packages.gz Inflating http://downloads.openmoko.org/repository/Om2008.8/all/Packages.gz Updated list of available packages in /var/lib/opkg/daily-all Downloading http://downloads.openmoko.org/repository/Om2008.8/all/Packages.sig Signature check failed Downloading http://downloads.openmoko.org/repository/Om2008.8/armv4t/Packages.gz Inflating http://downloads.openmoko.org/repository/Om2008.8/armv4t/Packages.gz Updated list of available packages in /var/lib/opkg/daily-armv4t Downloading http://downloads.openmoko.org/repository/Om2008.8/armv4t/Packages.sig Signature check failed Downloading http://jalimo.evolvis.org/repository/openmoko/all/Packages.gz Inflating http://jalimo.evolvis.org/repository/openmoko/all/Packages.gz Updated list of available packages in /var/lib/opkg/jalimo Downloading http://jalimo.evolvis.org/repository/openmoko/all/Packages.sig Signature check failed Downloading http://jalimo.evolvis.org/repository/openmoko/armv4t/Packages.gz Inflating http://jalimo.evolvis.org/repository/openmoko/armv4t/Packages.gz Updated list of available packages in /var/lib/opkg/jalimo-armv4t Downloading http://jalimo.evolvis.org/repository/openmoko/armv4t/Packages.sig Signature check failed Downloading http://downloads.openmoko.org/repository/Om2008.8/neo1973/Packages.gz Inflating http://downloads.openmoko.org/repository/Om2008.8/neo1973/Packages.gz Updated list of available packages in /var/lib/opkg/daily-neo1973 Downloading http://downloads.openmoko.org/repository/Om2008.8/neo1973/Packages.sig Signature check failed Downloading http://downloads.openmoko.org/repository/Om2008.8/om-gta02/Packages.gz Inflating http://downloads.openmoko.org/repository/Om2008.8/om-gta02/Packages.gz Updated list of available packages in /var/lib/opkg/daily-om-gta02 Downloading http://downloads.openmoko.org/repository/Om2008.8/om-gta02/Packages.sig Signature check failed Collected errors: * Failed to download http://downloads.openmoko.org/repository/Multiverse/Packages.sig, error 404 * Failed to download http://downloads.openmoko.org/repository/Om2008.8/all/Packages.sig, error 404 * Failed to download http://downloads.openmoko.org/repository/Om2008.8/armv4t/Packages.sig, error 404 * Failed to download http://jalimo.evolvis.org/repository/openmoko/all/Packages.sig, error 404 * Failed to download http://jalimo.evolvis.org/repository/openmoko/armv4t/Packages.sig, error 404 * Failed to download http://downloads.openmoko.org/repository/Om2008.8/neo1973/Packages.sig, error 404 * Failed to download http://downloads.openmoko.org/repository/Om2008.8/om-gta02/Packages.sig, error 404 Upgrading angstrom-version on root from 1:P1-Snapshot-20081028-r1 to 1:P1-Snapshot-20081029-r1... Downloading
Re: Fdom speed (was Re: New home for the New FDOM)
What simple ananlysis could be started in a terminal to gather data about what is eating what during usage? These results should indicate why FDOM is s slow and what should be done to speed it up. Leonti Bielski wrote: I think something is lowing down FDOM, maybe this is gestures daemon (someone at some point said it eats a lot of CPU power)? And another thing - it takes years to login via ssh to Freerunner with FDOM. With other distributions I just enter 'ssh [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]', press Enter and immediately press Enter when it asks for password. But with FDOM I actually have to wait till it gives me password promt. This happens not only with the lates distribution but with all FDOM I tried. But I still use sometimes to check for new things available for Freerunner. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
On Tue, Oct 28, 2008 at 9:06 AM, Pander [EMAIL PROTECTED] wrote: What simple ananlysis could be started in a terminal to gather data about what is eating what during usage? These results should indicate why FDOM is s slow and what should be done to speed it up. top? r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
I mean short interval and non disturbing logging top while doing normal phone functions. Looking at top in a terminal and testing phone functions do not go together easily. Any ideas? On Tue, October 28, 2008 09:09, Risto H. Kurppa wrote: On Tue, Oct 28, 2008 at 9:06 AM, Pander [EMAIL PROTECTED] wrote: What simple ananlysis could be started in a terminal to gather data about what is eating what during usage? These results should indicate why FDOM is s slow and what should be done to speed it up. top? r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
Use top on a ssh sesion on a externa pc conected trough usb El mar, 28-10-2008 a las 11:56 +0100, Pander escribió: I mean short interval and non disturbing logging top while doing normal phone functions. Looking at top in a terminal and testing phone functions do not go together easily. Any ideas? On Tue, October 28, 2008 09:09, Risto H. Kurppa wrote: On Tue, Oct 28, 2008 at 9:06 AM, Pander [EMAIL PROTECTED] wrote: What simple ananlysis could be started in a terminal to gather data about what is eating what during usage? These results should indicate why FDOM is s slow and what should be done to speed it up. top? r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Le jeudi 23 octobre 2008 à 06:40 -0600, [EMAIL PROTECTED] a écrit : Hi there, There is a new FDOM release uploaded at ... no, NOT at compartida.net as the topic suggest FDOM has a new home at http://www.tuxbrain.com/fdom_en.html Hi, I've just installed this latest FDOM on the SDCard. I was previously using QtopiaExtended and I can't help but notice that Qtopia seems to run faster. For example, with FDOM, I have to wait 5s after a start the Dialer application before I can enter a phone number. Am I the only one experiencing that ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Fdom speed (was Re: New home for the New FDOM)
Hi, I've just installed this latest FDOM on the SDCard. I was previously using QtopiaExtended and I can't help but notice that Qtopia seems to run faster. For example, with FDOM, I have to wait 5s after a start the Dialer application before I can enter a phone number. Am I the only one experiencing that ? I think the difference is that FDOM is written mostly in Python, which is an interpreted language, whereas Qte is written in C(++?) which is compiled. Compiled stuff usually is faster. Paul -- Behold the turtle. He makes progress only when he sticks his neck out. -James Bryant Conant http://www.nlpagan.net Running on Mandriva Linux 2008 and Ubuntu 8.04 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
Le lundi 27 octobre 2008 à 18:09 +0100, Paul a écrit : Hi, I've just installed this latest FDOM on the SDCard. I was previously using QtopiaExtended and I can't help but notice that Qtopia seems to run faster. For example, with FDOM, I have to wait 5s after a start the Dialer application before I can enter a phone number. Am I the only one experiencing that ? I think the difference is that FDOM is written mostly in Python, which is an interpreted language, whereas Qte is written in C(++?) which is compiled. Compiled stuff usually is faster. The dialer application is not written in python, is it ? It seems to me the same as in qtopia. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
I think something is lowing down FDOM, maybe this is gestures daemon (someone at some point said it eats a lot of CPU power)? And another thing - it takes years to login via ssh to Freerunner with FDOM. With other distributions I just enter 'ssh [EMAIL PROTECTED]', press Enter and immediately press Enter when it asks for password. But with FDOM I actually have to wait till it gives me password promt. This happens not only with the lates distribution but with all FDOM I tried. But I still use sometimes to check for new things available for Freerunner. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
Trying adding the freerunner FDOM IP to your /etc/hosts file with an alias. For example: 192.168.0.202 freerunner -- Denis Galvão AsteriskBrasil.org On 27/10/2008, at 17:18, Leonti Bielski wrote: And another thing - it takes years to login via ssh to Freerunner with FDOM. With other distributions I just enter 'ssh [EMAIL PROTECTED]', press Enter and immediately press Enter when it asks for password. But with FDOM I actually have to wait till it gives me password promt. This happens not only with the lates distribution but with all FDOM I tried. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
Denis is right. It's trying to do a reverse DNS lookup. This plauges all incorrectly configured linux distros. At least every so often on any one I use. Gestures daemon does use a bit but only 5% I believe. Just check with top. I turn it off anyway as I don't use it at the moment: update-rc.d -f gesd-neo2 remove I think... -Nick On Tue, Oct 28, 2008 at 5:18 AM, Leonti Bielski [EMAIL PROTECTED] wrote: I think something is lowing down FDOM, maybe this is gestures daemon (someone at some point said it eats a lot of CPU power)? And another thing - it takes years to login via ssh to Freerunner with FDOM. With other distributions I just enter 'ssh [EMAIL PROTECTED]', press Enter and immediately press Enter when it asks for password. But with FDOM I actually have to wait till it gives me password promt. This happens not only with the lates distribution but with all FDOM I tried. But I still use sometimes to check for new things available for Freerunner. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fdom speed (was Re: New home for the New FDOM)
On Tue, 28 Oct 2008 10:16:10 +1000, nick d. [EMAIL PROTECTED] wrote: Denis is right. It's trying to do a reverse DNS lookup. This plauges all incorrectly configured linux distros. At least every so often on any one I use. Gestures daemon does use a bit but only 5% I believe. Just check with top. I turn it off anyway as I don't use it at the moment: update-rc.d -f gesd-neo2 remove I think... -Nick On Tue, Oct 28, 2008 at 5:18 AM, Leonti Bielski [EMAIL PROTECTED] wrote: I think something is lowing down FDOM, maybe this is gestures daemon (someone at some point said it eats a lot of CPU power)? And another thing - it takes years to login via ssh to Freerunner with FDOM. With other distributions I just enter 'ssh [EMAIL PROTECTED]', press Enter and immediately press Enter when it asks for password. But with FDOM I actually have to wait till it gives me password promt. This happens not only with the lates distribution but with all FDOM I tried. But I still use sometimes to check for new things available for Freerunner. Leonti To overcome the rDNS delay try adding 192.168.0.200 omhost or something similar to /etc/hosts. So when an SSH connection comes in from 192.168.0.200 it doesn't drop to DNS lookup but defers to the /etc/hosts file. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
*Updated Duke3D a version without sound but that works like a charm an has a semitransparent buttons Nice to know people appreciate my work ;) By the way, I fixed the .desktop file (I'm like you, I don't like testing so much...) Turning sound back on is just a matter of changing the config file. -- Charles-Henri ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Thanks for GNUChess! Steve Ben Hussey wrote: ftp://ftp.tuxbrain.com/openmoko/fdom/[EMAIL PROTECTED] wrote: Hi there, There is a new FDOM release uploaded at ... no, NOT at compartida.net as the topic suggest FDOM has a new home at http://www.tuxbrain.com/fdom_en.html and if you ask yourself why is because Tuxbrain is my brand new company and I finally have my own server to upload those light images Saergio please configure compartida as mirror if you don't mind This release is plenty of new things, the first and I believe the most Important is that you don't need to reflash your neo to FDOMize it :) Thank's to Nacho, Armin and all of you who have give us ideas and links we have created the FDOMizer :) It can be considered a instruction's log of what we do from a OM2008.X to transform it to a FDOM, The script has been structured to be able to update previous versions of FDOM to the latests one. even it has a only fix option in case some opkg update upgrade mess up things... better to say try to put order in the mess we created without success :) I have to say we have no much time to test it so surelly this is the most unstable release of FDOM we have released, but thanks of the script you will know exactly what we have done an will be easy to know how to fix it, if you want to collaborate to improve Fdomizer for next release fell free to register on the devel list. Here is a few of the improvement we have added to this new version (maybe some of them will half-work and one or two doesn't work at all yet but surely in near future they will) you can take a look directly at the script to see what and how is installed. here I post a list commented that can be used as guide to next steps (fix all that doesn't work out of the box) *dillo (this is FAST app definition ;) it's a pity it doesn't comes with ssl included) *ePdfview, not tested yet *gutenflash (is so geek app that is a must), *qt-x11 calculator works fine :) *lint-wifi(no wifi arround when I tested) *fbreader(install but not apear on the main screen, must investigate why) *Updated remoko to 0.3.2 (do not work for a dependency problem python-textutils packages seem to have bad MD5 from every where I try to download) In the game part :) *Updated Duke3D a version without sound but that works like a charm an has a semitransparent buttons *Pingus :) since I know it exists I was willing to have them on the neo *of course the venerated openmoocow!!! so silly that you must smile any time you upside down your neo *And this one is for steve GNUChess ;) And a lot of cosmetic fixes(arrange icons, submenus, search bar on contacts...) and some no so cosmetic (hwclock, alsa states, storage issue...) thanks to Armin And if you visit the page you will see one thing even my coadmins doesn't wait for }8-) Things to improve that I'm not proud of, GPL stuff, I was intended to document where any piece of code comes from but I have no time to do that, so I will try to improve this making comments on the script itself any time I put a binaries directly and revamped confs. Pindgin It has been update in angstrom repository and it segfaults, surely is dependency issue but I need more time to test. In the first start you must disable automated sleep for a couple of minutes to let the system time to stabilize. Well surely you will discover a lot more things to not to be proud of, but that's what we like it, FAT and DIRTY ;) David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions, watch out!! there is a Linux in you pocket ;) The link titled, ftp://ftp.tuxbrain.com/openmoko/fdom/releases, points to the same url but with FDOM in capital letters. So I get a file not found error. The fdom needs to be changed to lowercase in the url. -Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
New home for the New FDOM
Hi there, There is a new FDOM release uploaded at ... no, NOT at compartida.net as the topic suggest FDOM has a new home at http://www.tuxbrain.com/fdom_en.html and if you ask yourself why is because Tuxbrain is my brand new company and I finally have my own server to upload those light images Saergio please configure compartida as mirror if you don't mind This release is plenty of new things, the first and I believe the most Important is that you don't need to reflash your neo to FDOMize it :) Thank's to Nacho, Armin and all of you who have give us ideas and links we have created the FDOMizer :) It can be considered a instruction's log of what we do from a OM2008.X to transform it to a FDOM, The script has been structured to be able to update previous versions of FDOM to the latests one. even it has a only fix option in case some opkg update upgrade mess up things... better to say try to put order in the mess we created without success :) I have to say we have no much time to test it so surelly this is the most unstable release of FDOM we have released, but thanks of the script you will know exactly what we have done an will be easy to know how to fix it, if you want to collaborate to improve Fdomizer for next release fell free to register on the devel list. Here is a few of the improvement we have added to this new version (maybe some of them will half-work and one or two doesn't work at all yet but surely in near future they will) you can take a look directly at the script to see what and how is installed. here I post a list commented that can be used as guide to next steps (fix all that doesn't work out of the box) *dillo (this is FAST app definition ;) it's a pity it doesn't comes with ssl included) *ePdfview, not tested yet *gutenflash (is so geek app that is a must), *qt-x11 calculator works fine :) *lint-wifi(no wifi arround when I tested) *fbreader(install but not apear on the main screen, must investigate why) *Updated remoko to 0.3.2 (do not work for a dependency problem python-textutils packages seem to have bad MD5 from every where I try to download) In the game part :) *Updated Duke3D a version without sound but that works like a charm an has a semitransparent buttons *Pingus :) since I know it exists I was willing to have them on the neo *of course the venerated openmoocow!!! so silly that you must smile any time you upside down your neo *And this one is for steve GNUChess ;) And a lot of cosmetic fixes(arrange icons, submenus, search bar on contacts...) and some no so cosmetic (hwclock, alsa states, storage issue...) thanks to Armin And if you visit the page you will see one thing even my coadmins doesn't wait for }8-) Things to improve that I'm not proud of, GPL stuff, I was intended to document where any piece of code comes from but I have no time to do that, so I will try to improve this making comments on the script itself any time I put a binaries directly and revamped confs. Pindgin It has been update in angstrom repository and it segfaults, surely is dependency issue but I need more time to test. In the first start you must disable automated sleep for a couple of minutes to let the system time to stabilize. Well surely you will discover a lot more things to not to be proud of, but that's what we like it, FAT and DIRTY ;) David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions, watch out!! there is a Linux in you pocket ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Hi, On Thu, Oct 23, 2008 at 2:40 PM, [EMAIL PROTECTED] wrote: Hi there, There is a new FDOM release uploaded at ... no, NOT at compartida.net as the topic suggest FDOM has a new home at http://www.tuxbrain.com/fdom_en.html FDOMizer looks good, but how can I tell what my current FDOM-distribution is? I could check the files, ofocurse, but being able to see it from a file (or perhaps the FDOMizer can somehow tell?) would be more automagic :-) Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Hi! Great to see a new release with new software! What's the easiest way to see a changelog? It was great to have it on the wiki page but now it's gone.. I think users would like to see what are the changes since the last version. I know that you can use the svn to check it but.. It's a bother and everybody don't know how to do it.. (I think I'd be able to do it with some svn reference). So please make it easily available somewhere! Thanks! r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
ftp://ftp.tuxbrain.com/openmoko/fdom/[EMAIL PROTECTED] wrote: Hi there, There is a new FDOM release uploaded at ... no, NOT at compartida.net as the topic suggest FDOM has a new home at http://www.tuxbrain.com/fdom_en.html and if you ask yourself why is because Tuxbrain is my brand new company and I finally have my own server to upload those light images Saergio please configure compartida as mirror if you don't mind This release is plenty of new things, the first and I believe the most Important is that you don't need to reflash your neo to FDOMize it :) Thank's to Nacho, Armin and all of you who have give us ideas and links we have created the FDOMizer :) It can be considered a instruction's log of what we do from a OM2008.X to transform it to a FDOM, The script has been structured to be able to update previous versions of FDOM to the latests one. even it has a only fix option in case some opkg update upgrade mess up things... better to say try to put order in the mess we created without success :) I have to say we have no much time to test it so surelly this is the most unstable release of FDOM we have released, but thanks of the script you will know exactly what we have done an will be easy to know how to fix it, if you want to collaborate to improve Fdomizer for next release fell free to register on the devel list. Here is a few of the improvement we have added to this new version (maybe some of them will half-work and one or two doesn't work at all yet but surely in near future they will) you can take a look directly at the script to see what and how is installed. here I post a list commented that can be used as guide to next steps (fix all that doesn't work out of the box) *dillo (this is FAST app definition ;) it's a pity it doesn't comes with ssl included) *ePdfview, not tested yet *gutenflash (is so geek app that is a must), *qt-x11 calculator works fine :) *lint-wifi(no wifi arround when I tested) *fbreader(install but not apear on the main screen, must investigate why) *Updated remoko to 0.3.2 (do not work for a dependency problem python-textutils packages seem to have bad MD5 from every where I try to download) In the game part :) *Updated Duke3D a version without sound but that works like a charm an has a semitransparent buttons *Pingus :) since I know it exists I was willing to have them on the neo *of course the venerated openmoocow!!! so silly that you must smile any time you upside down your neo *And this one is for steve GNUChess ;) And a lot of cosmetic fixes(arrange icons, submenus, search bar on contacts...) and some no so cosmetic (hwclock, alsa states, storage issue...) thanks to Armin And if you visit the page you will see one thing even my coadmins doesn't wait for }8-) Things to improve that I'm not proud of, GPL stuff, I was intended to document where any piece of code comes from but I have no time to do that, so I will try to improve this making comments on the script itself any time I put a binaries directly and revamped confs. Pindgin It has been update in angstrom repository and it segfaults, surely is dependency issue but I need more time to test. In the first start you must disable automated sleep for a couple of minutes to let the system time to stabilize. Well surely you will discover a lot more things to not to be proud of, but that's what we like it, FAT and DIRTY ;) David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions, watch out!! there is a Linux in you pocket ;) The link titled, ftp://ftp.tuxbrain.com/openmoko/fdom/releases, points to the same url but with FDOM in capital letters. So I get a file not found error. The fdom needs to be changed to lowercase in the url. -Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Also, the tarball unpacks everything into var/tmp/root/. If I move everything from there into the root directory of the SD partition it boots, although I can't start contacts or the dialer. That could be something I did wrong, though. What kernel should we be using with this? Ben Hussey wrote: The link titled, ftp://ftp.tuxbrain.com/openmoko/fdom/releases, points to the same url but with FDOM in capital letters. So I get a file not found error. The fdom needs to be changed to lowercase in the url. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
Quoting Matt Luzum [EMAIL PROTECTED]: Also, the tarball unpacks everything into var/tmp/root/. If I move everything from there into the root directory of the SD partition it boots, although I can't start contacts or the dialer. That could be something I did wrong, though. No surely something I did wrong any body sees what's wrong in this sentece to make a tarball of a neo rootfs? #ssh [EMAIL PROTECTED] tar -cp /var/tmp/root -C /var/tmp/root|gzip - Fat_and_Dirty_OM.200808-updates.20080909.rootfs.tar.gz What kernel should we be using with this? the standard OM200809 kernel Ben Hussey wrote: The link titled, ftp://ftp.tuxbrain.com/openmoko/fdom/releases, points to the same url but with FDOM in capital letters. So I get a file not found error. The fdom needs to be changed to lowercase in the url. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Hey watch out!! there's a Linux in you pocket!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New home for the New FDOM
On Friday 24 October 2008 07:33:04 David Samblas wrote: Quoting Matt Luzum [EMAIL PROTECTED]: Also, the tarball unpacks everything into var/tmp/root/. If I move everything from there into the root directory of the SD partition it boots, although I can't start contacts or the dialer. That could be something I did wrong, though. I don't think so. This was happening to me on testing and was due to a missing ld.so.cache. I had to uncomment ldconfig form the startup scripts to prevent this from occurring. I'm not sure what the correct fix really is, as I'm not sure as to the intended layout of the filesystem. No surely something I did wrong any body sees what's wrong in this sentece to make a tarball of a neo rootfs? #ssh [EMAIL PROTECTED] tar -cp /var/tmp/root -C /var/tmp/root|gzip - Fat_and_Dirty_OM.200808-updates.20080909.rootfs.tar.gz I'd say it's fine but you can abbreviate a bit by using 'tar cpzf' which will incorporate gzip. I think tar will preserve permissions automatically aswell, it's only when extracting I believe. Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community