Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
Hi Radek, all, Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using 2.6.39 kernel edit /etc/modules, remove or comment out line with ar6000, reboot and report if your resume issues are gone. I've been using 2.6.39 with ar6000 commented in /etc/modules in the last week and I've not encountered the resume so far. Editing /etc/modules I noticed that snd-soc-neo1973-wm8753 is repeated three times. Is it the right behaviour? Thank you very much! By the way, gnuchess does not seem to work on this last QtMoko release. Is this a my problem or is it a common one? I've a suggestion for you developers: in the scripts menu (top left icon in the mail menu) it would be great if the script could be return some kind of feedback. For example, each category (such as GPS standby) should present a slide button with the two (or more) possible values (checked against the script behind, if possible). Indeed, it should be something similar to neocontrol... Sorry for proposing instead of coding, but my lack of knowledge is too big :-( Regards Radek Cheers, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: testing the free calypso software
Hi David, Michael, all, thanks a lot for your work, it is very emotional to see this little piece of freedom rising! I'm still not brave enough to risk my only (I mean in all my life time so far) mobile phone, but I will soon ;-) By the way, I think that your work, with the right notes about being experimental and so on of course, should also be in the official wiki. A small question about the procedure you describe: is the t191 cable only needed to backup the vital parts of the calypso memory or also to write the new firmware? By the way, yes, a distro able to flash and back-up everything without additional cables would be very appreciated. Internationalist greetings, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: testing the free calypso software
I did not publish it in the mailing list, so here is link to my manual: http://norayr.arnet.am/log/?p=113 If anyone who has wiki account wants to use it as reference, or even to copy the text entirely, feel free and encouraged to do that. 01/27/14 07:17 -ում, Giacomo 'giotti' Mariani-ը գրել է: Hi David, Michael, all, thanks a lot for your work, it is very emotional to see this little piece of freedom rising! I'm still not brave enough to risk my only (I mean in all my life time so far) mobile phone, but I will soon ;-) By the way, I think that your work, with the right notes about being experimental and so on of course, should also be in the official wiki. A small question about the procedure you describe: is the t191 cable only needed to backup the vital parts of the calypso memory or also to write the new firmware? By the way, yes, a distro able to flash and back-up everything without additional cables would be very appreciated. Internationalist greetings, Giacomo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: testing the free calypso software
Giacomo 'giotti' Mariani giacomomari...@yahoo.it wrote: Hi David, Michael, all, thanks a lot for your work, it is very emotional to see this little piece of freedom rising! You're welcome. :-) I'm still not brave enough to risk my only (I mean in all my life time so far) mobile phone, but I will soon ;-) There is nothing at risk really - if the leo2moko firmware doesn't work for you for some reason, you can always revert to moko11, using either our flashing tools or the official moko11 flasher. Even in the case of the FFS with the RF calibration values etc, there is absolutely no danger of corrupting this FFS if you issue loadtool commands exactly per the instructions. Saving a backup copy of the FFS sectors is a precaution just in case you erase or write to the wrong part of the flash. If you have this backup saved, you can always restore it. In the absolute worst case scenario imaginable, if someone does lose their RF calibration values and has no backup copy anywhere, you should be able to send your FR to some lab to get it recalibrated. I don't offer such service currently because I haven't acquired the necessary RF test equipment and process knowledge yet, but when I start building my own Calypso phones, I will obviously need to get them calibrated, and once we have the knowledge and the setup to do it, Harhan Engineering Co. will also offer recalibration services to Freerunner users. By the way, I think that your work, with the right notes about being experimental and so on of course, should also be in the official wiki. As much as I would love to see it happen, I doubt that the powers controlling that wiki will ever allow it. A small question about the procedure you describe: is the t191 cable only needed to backup the vital parts of the calypso memory or also to write the new firmware? Both if you use the uSD system which David just released; neither if you get FreeCalypso loadtools running on the Linux processor of your FR like Norayr did. Oh, and just to be clear as to exactly what the vital parts of the calypso memory in question are: the only entity that lives in the GSM modem's flash memory besides the firmware image (which is exactly the same in a device as it is on the web at the official download URL) is the flash file system, or FFS. The FFS in Openmoko's modems takes up exactly 448 KiB of flash space (64 KiB x 7); per TI's design it is structured like a UNIX file system (directory tree, forward-slash- separated pathnames, case-sensitive etc) and stores a bunch of things: * The modem's IMEI; * RF calibration values; * ID strings which say that your device is a Neo1973 GTA02 made by FIC/OpenMoko - Om's late firmwares (moko10/11) appear to not use these strings from FFS (fw returns hard-coded strings instead), but my leo2moko fw returns the strings from FFS following TI's canon; * Some dynamic data written into the FFS (the fw always mounts the FFS with R/W access, TI's fw has no concept of a read-only mount for the FFS) during the operational lifetime of the modem: history of what SIM cards this modem saw, dialed/received/missed calls, and probably received SMS as well - I have yet to play with the latter. Just this weekend I wrote a new utility for examining FFS images read out of TI-based GSM devices (our beloved FR being one of them); this new tiffs utility (with mokoffs and pirffs wrappers) supercedes my earlier mpffs-* tools I wrote and released last summer. The new utility allows one to list and extract not only the current file content of the FFS (i.e., what one sees when mounting the file system normally), but also those files which have been logically deleted or overwritten, but not yet reclaimed, i.e., not truly gone. Hence the tool can be used to do forensics on Freerunner modems - I suspect many of you probably never thought about the modem's flash memory remembering the history of what SIM cards you had in there, what numbers you called or received calls from, and probably your SMS exchanges too... The just-described utility currently lives in the freecalypso-sw tree on Bitbucket: http://lists.openmoko.org/pipermail/community/2013-August/068850.html Look in the ffstools directory. Now I need to write some more documentation and make a release tarball for the FTP site. Stay tuned; I'll post here when I make that release. By the way, yes, a distro able to flash and back-up everything without additional cables would be very appreciated. Of course... Shortage of qualified volunteer manpower is our only limit. VLR, SF ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: testing the free calypso software
On Mon 27 January 2014 19:26:19 Michael Spacefalcon wrote: Giacomo 'giotti' Mariani giacomomari...@yahoo.it wrote: By the way, I think that your work, with the right notes about being experimental and so on of course, should also be in the official wiki. As much as I would love to see it happen, I doubt that the powers controlling that wiki will ever allow it. That's a bold misconception. OM wiki isn't censored, it just gets cleaned of SPAM and obviously incorrect AND hazardous info, like e.g. somebody suggesting to run wear tests against NAND to verify its formatting. /j 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: testing the free calypso software
Hi Giacomo To clarify, there are two methods. The method I describe requires a cable as you run loadtools on your PC. The method Norayr describes does not need a cable as loadtools is run on the freerunner. It was and is my intention to produce an sdcard distro that allows either method. The cable is not expensive though if you don't want to wait a month or so. As for risk - as has been said, if the worst comes to the worst, there are the two methods on the wiki to fall back on. I've flashed the calypso to leo2moko, back to moko11 and back to leo2moko again using the cable / loadtools on PC method. I'm so confident about this (with wheezy on the PC) that I even proceeded with an attempted flash by the other method *after* seeing loadtools report fail with the backup routine. I'd propose that as a good indicator - if you can't run the backup routine successfully, don't proceed with a flash attempt. It's likely my failure with the loadtools on freerunner / no cable method was because my sdcard distro has an ancient kernel. Obviously loadtools has not been widely tested yet, but I'd say there is zero risk with cable method and wheezy on the PC and I'd be very surprised if that does not apply to all recent and current versions of Gnu/Linux. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: testing the free calypso software
joerg Reisenweber jo...@openmoko.org wrote: That's a bold misconception. OM wiki isn't censored, it just gets cleaned of SPAM and obviously incorrect AND hazardous info, like e.g. somebody suggesting to run wear tests against NAND to verify its formatting. But I still think that it would be better for FreeCalypso to have its own identity that is separate and independent from Openmoko, i.e., its own mailing list, its own website (wikified or otherwise) etc. As a result of my involvement on another mailing list (on a topic that is totally unrelated to mobile phones), I became aware of this document from the ISO Technical Committee on terminology: http://www.ucolick.org/~sla/leapsecs/ISOTC37toITURA.pdf Simply put, the authors of the above statement from ISO TC37 emphasize the importance of using terms which have a 1:1 mapping to the concepts they are meant to stand for, i.e., 1 concept = 1 term. As you and others have made it perfectly clear on numerous occasions, the term Openmoko was never meant to stand for the concept of free (or open) GSM modem; instead this term (according to you and other high-standing community members, which I obviously am not) stands for a different concept, namely that of a free application processor with a black box modem attached as a peripheral. And because the name Openmoko rightfully belongs to you and your former boss Sean Moss- Pultz, it is not my place to try to change its meaning. (In fact, Dr. HNS is effectively invoking this term=concept equivalence of Openmoko = free AP with a black box modem as a peripheral when he asserts the legitimacy of his GTA04 product as a non-downgrade successor to Om products.) But I am working with a completely different concept, namely that of a free GSM device, be it a modem or a complete dumbphone. And because it is an entirely different concept than that which is mapped by the term Openmoko, by the principles of ISO TC37 my new concept calls for a new term for referring to it. Hence the name FreeCalypso was born: I came up with this name about this time last year, following exactly the line of reasoning I've just outlined, and my first public announcement of FreeCalypso was this one: http://lists.openmoko.org/pipermail/community/2013-February/068270.html The FreeCalypso project is very much in need of its own web/list home under the ifctf.org domain name, which currently features only an FTP site. My desire is to create a lists.ifctf.org host first, hosting Mailman mailing lists exactly like Openmoko and almost all FOSS projects and technical communities have nowadays - anything else would be seen as substandard, and therefore unattractive to me. A website for FreeCalypso (wikified or not) can be created later, but my first focus is on the lists host on which we can create a proper new mailing list for FreeCalypso. And because I already have my own physical datacenter on my own physical turf, I *will not* buy hosting from someone else who would ask me to agree to their TOS or AUP or the like - hence my only option is to use my own physical hardware. A SAS JBOD chassis is already on its way to me from ebay, already paid for; the drives are next - as soon as I gather the cash to buy 6 SAS drives of some non-laughable capacity (I refuse to use SATA, and I desire 6 drives to start with for a raidz2 ZFS configuration - I'll be running OpenSXCE), I will finally have the necessary hw, and will begin the setup/configuration work. VLR, SF ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
On Monday, January 27, 2014 02:29:10 PM Giacomo 'giotti' Mariani wrote: Hi Radek, all, Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using 2.6.39 kernel edit /etc/modules, remove or comment out line with ar6000, reboot and report if your resume issues are gone. I've been using 2.6.39 with ar6000 commented in /etc/modules in the last week and I've not encountered the resume so far. Hi, well it's quite stable, but not rock stable, at least not for me :( I had encountered problem that the phone wouldnt wake with POWER button. So i tried call from another phone. The screen turned on, but was unresponsive. I tried connecting USB, but this did not work too. Editing /etc/modules I noticed that snd-soc-neo1973-wm8753 is repeated three times. Is it the right behaviour? No. It needs to be there only once. I messed it in the rootfs howto while trying to figure list of modules needed. It shouldnt hurt, but once is enough. Fixed this in git now. By the way, gnuchess does not seem to work on this last QtMoko release. Is this a my problem or is it a common one? Hmm maybe i can take a look. I've a suggestion for you developers: in the scripts menu (top left icon in the mail menu) it would be great if the script could be return some kind of feedback. For example, each category (such as GPS standby) should present a slide button with the two (or more) possible values (checked against the script behind, if possible). Indeed, it should be something similar to neocontrol... These are just shell scripts. But yes, with GUI helper tool they could work like this. I implemented tool for showing QT message boxes already here: https://github.com/radekp/qtmoko/tree/master/src/tools/qui maybe extending this with sliders could work. Sorry for proposing instead of coding, but my lack of knowledge is too big :-( No problem :) BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
