Re: The epoch is upon me.
2011/1/11 Łukasz Pankowski lukp...@o2.pl Benjamin Deering ben_deer...@swissmail.org writes: effect to make ffalarms useless ... I thought that had to do with an fsotdld issue (http://trac.freesmartphone.org/ticket/596) You are right, I did not have it on the top of my mind since I use the workaround: As a temporary workaround one can enable otimed subsystem in /etc/frameworkd.conf: [otimed] disable = 0 (http://shr-project.org/trac/ticket/1253) Ben Thanks, this workaround ... works! :D d ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Thank you for the hint!. I followed the references and boot v31 with Qi. For this I created the empty file 'noboot-GTA02' and put it to /boot in the partitions for debian and shr-u. This works just fine. But: After I use Debian on the 1st Partition and stopped it later and wanted to start again QtMoko, Qi came in kernel panic. There was the message, that mtdblocck6 can't be read (I don't remember the the exact content now). I suspect that wrong boot options had been created (in mtdblock6?) that do not match with the file system for UBIFS. I had to reflash QtMoko completly again (qi, kernel and filesystem). Currently I do not want to start my alternative distributions again because I fear the problem could occur again. Is there perhaps another way to reconstruct the right Qi boot options in this case than to reflash the freerunner? Thanks in advance! Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5918157.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-Devel] some advertising
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11.01.2011 19:03, schrieb Sylvain Paré: Hi all! I did a video today http://vimeo.com/18663899 Hey! I did a video as well, showing my new dual-booting solution called Bootr: http://vimeo.com/18744450 With Bootr you can switch between WebOS and SHR at bootup. Bootr lives here: https://github.com/slyon/bootr Slyon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNLyR4AAoJEGGMlCflhefE26sIAKQDRXK0iYZaLWKHv/k6+DgB 6P2ZerWaVGafIdehc7vg8OQQZlqIUCUbws9jWHhRpqrbWg/08XDhqXaYB7hpJlgp PuEq9kCwDNeX18pHEB8vgZVo3UbSv45ViFu/aRQ3A5hE6VymcD9m23RJAnqPnWOp 26P28vWeY2bHY183lWONNQy9wBad1dUDIwkHmK4sUlw7eh1EnLeR0vFGNkaCE2c3 TaNnMicDdnaPgFzsCTSRO8vuV89iWtD3q5H8/DDsn+qU1zMky1C8Juk2kGEmtonT 5LJzaTmE398n4oSuXeLcSNYNZoICCXp5Sty/LyxxJiJ5m/X6laqEmhGMtigGHZ0= =mnTi -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
On Thursday 13 January 2011, sferic wrote: Thank you for the hint!. I followed the references and boot v31 with Qi. For this I created the empty file 'noboot-GTA02' and put it to /boot in the partitions for debian and shr-u. This works just fine. But: After I use Debian on the 1st Partition and stopped it later and wanted to start again QtMoko, Qi came in kernel panic. There was the message, that mtdblocck6 can't be read (I don't remember the the exact content now). I suspect that wrong boot options had been created (in mtdblock6?) that do not match with the file system for UBIFS. I had to reflash QtMoko completly again (qi, kernel and filesystem). Currently I do not want to start my alternative distributions again because I fear the problem could occur again. Is there perhaps another way to reconstruct the right Qi boot options in this case than to reflash the freerunner? Qi boot options for NAND are compiled in, and can only be modified by flashing a modified Qi. I don't think debian would mess with your bootloader, and it shouldn't mess with the kernel in NAND if booted from iSD. It could be that debian was expecting to see something other than UBIFS on mtdblock6 and managed to mess it up. You probably wouldn't have had cause to check for errors in debian's boot messages though. If that is what's happened you should only need to reflash the rootfs, and the cure would be to tell debian about the UBIFS partition using a combination of extra boot parameters and /etc/fstab entries. I've not tried UBIFS yet, so don't ask me what they need to be, but /proc/cmdline in QtMoko should help. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-Devel] some advertising
@GNUtoo: thx ;) @EdorFaus: thx but not lot of access ( perhaps i should move to php.. but I have more intersting things to do : ) ) @Slyon: coool to see it in video! ( forgaive me I pass through long webos booting :) ) /me looking forward to merge this into fso-installer! 2011/1/13 Lukas Märdian lukasmaerd...@googlemail.com -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11.01.2011 19:03, schrieb Sylvain Paré: Hi all! I did a video today http://vimeo.com/18663899 Hey! I did a video as well, showing my new dual-booting solution called Bootr: http://vimeo.com/18744450 With Bootr you can switch between WebOS and SHR at bootup. Bootr lives here: https://github.com/slyon/bootr Slyon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNLyR4AAoJEGGMlCflhefE26sIAKQDRXK0iYZaLWKHv/k6+DgB 6P2ZerWaVGafIdehc7vg8OQQZlqIUCUbws9jWHhRpqrbWg/08XDhqXaYB7hpJlgp PuEq9kCwDNeX18pHEB8vgZVo3UbSv45ViFu/aRQ3A5hE6VymcD9m23RJAnqPnWOp 26P28vWeY2bHY183lWONNQy9wBad1dUDIwkHmK4sUlw7eh1EnLeR0vFGNkaCE2c3 TaNnMicDdnaPgFzsCTSRO8vuV89iWtD3q5H8/DDsn+qU1zMky1C8Juk2kGEmtonT 5LJzaTmE398n4oSuXeLcSNYNZoICCXp5Sty/LyxxJiJ5m/X6laqEmhGMtigGHZ0= =mnTi -END PGP SIGNATURE- ___ 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
