i seling my moko i just dont have time to play with him
itslike new for good price a...@nanocom.co.il from israel ----- Original Message ----- From: <support-requ...@lists.openmoko.org> To: <support@lists.openmoko.org> Sent: Saturday, February 07, 2009 10:23 AM Subject: support Digest, Vol 8, Issue 13 > Send support mailing list submissions to > support@lists.openmoko.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openmoko.org/mailman/listinfo/support > or, via email, send a message with subject or body 'help' to > support-requ...@lists.openmoko.org > > You can reach the person managing the list at > support-ow...@lists.openmoko.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of support digest..." > > > Today's Topics: > > 1. Re: FSO Milestone 5 (Andy Green) > 2. Re: FSO Milestone 5 (Simon Comeau Martel) > 3. Re: FSO Milestone 5 (Joel Newkirk) > 4. Re: FSO Milestone 5 (Carl Lobo) > 5. Re: FSO Milestone 5 (Simon Comeau Martel) > 6. Re: Power Adaptor. (Alex (Maxious) Sadleir) > 7. Re: FSO Milestone 5 (Erland Lewin) > 8. Re: FSO Milestone 5 (Petr Vanek) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 06 Feb 2009 22:37:00 +0000 > From: Andy Green <a...@openmoko.com> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: <498cbb8c.6030...@openmoko.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Somebody in the thread at some point said: > > | My install of FSO M5 is not on a SD card. > | > | As I said, all my problems where related to the fact I was using Qi, > | instead of uBoot. > > It's not immediately obvious how Qi can trash the GSM connection and > leave everything else OK. As in, if that was a feature we wanted to add > to Qi, I don't know how we would do that. > > - -Andy > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkmMursACgkQOjLpvpq7dMqycgCeOYeFRaTw8G6rooGvEPVdwGxf > qYcAn1ZfCdWEOOSYyYlNuKci8koEPRRW > =WlMW > -----END PGP SIGNATURE----- > > > > ------------------------------ > > Message: 2 > Date: Fri, 06 Feb 2009 18:57:03 -0500 > From: Simon Comeau Martel <si...@comeau.info> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: <498cce4f.9060...@comeau.info> > Content-Type: text/plain; charset=ISO-8859-1 > > I have no idea how it is possible. > > All I know is that if I boot Milestone 5 via Qi, get the following > message in zhone: > > Usage: Requested ressource GSM with error. > > And the problem is reproducible; it happen every time. > > I guess that there could be something causing some kernel module not to > load? > > Maybe I should try upgrading to a more recent version of Qi? The one I > use is: > > qi-s3c2442-master_2ad3ce6ff57753e3.udfu > (md5sum: 88979a8310a98d7a2189977194cb2607) > > Let me know if there is anything I can do to diagnose that problem. > > Is FSO Milestone 5 working fine for someone who use Qi? > > -- > Simon Comeau Martel > si...@comeau.info > https://comeau.info > > Andy Green wrote: >> Somebody in the thread at some point said: >> >> | My install of FSO M5 is not on a SD card. >> | >> | As I said, all my problems where related to the fact I was using Qi, >> | instead of uBoot. >> >> It's not immediately obvious how Qi can trash the GSM connection and >> leave everything else OK. As in, if that was a feature we wanted to add >> to Qi, I don't know how we would do that. >> >> -Andy > > _______________________________________________ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > > > ------------------------------ > > Message: 3 > Date: Fri, 6 Feb 2009 20:28:29 -0500 > From: Joel Newkirk <freerun...@newkirk.us> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: <b9afe9b3ff2f34c95bc1151f7de6b...@localhost> > Content-Type: text/plain; charset="UTF-8" > > On Fri, 06 Feb 2009 18:57:03 -0500, Simon Comeau Martel > <si...@comeau.info> > wrote: >> I have no idea how it is possible. >> >> All I know is that if I boot Milestone 5 via Qi, get the following >> message in zhone: >> >> Usage: Requested ressource GSM with error. >> >> And the problem is reproducible; it happen every time. >> > > Read-only filesystem. Once you've booted and see the GSM error in Zhone, > open a terminal and try "touch test" - you'll get an error noting that the > rootfs is read-only. Qi mounts rootfs read-only at the start - I believe > /etc/init.d/checkroot.sh is where it's supposed to be remounted > read/write. > > Many things will be 'broken' in this state, like you cannot SSH into it > because dropbear doesn't start properly when it can't write, and just > about > everything with frameworkd is broken. > > Presuming this is the case (I'm betting;) try > > mount -o remount,rw / > /etc/init.d/frameworkd restart > > stop Zhone, restart it, and it should be able to activate GSM... > > > I've not worked through the logic in /etc/init.d/checkroot.sh or anything > yet to see where this is failing, but putting the remount command at the > top of that script will restore your FR to usefulness, remounting / rw > fairly early in the boot process. (checkroot.sh is supposed to check the > rootfs for errors /if/ it's ext2/3, and remount r/w afterwards, but > doesn't > seem to remount root if it's booted from jffs2 in NAND. As I said I've > not > followed the logic of the script yet but am guessing that if it's not > ext2/3 it never reaches the remount,rw statement there.) > > > j > > > >> I guess that there could be something causing some kernel module not to >> load? >> >> Maybe I should try upgrading to a more recent version of Qi? The one I >> use is: >> >> qi-s3c2442-master_2ad3ce6ff57753e3.udfu >> (md5sum: 88979a8310a98d7a2189977194cb2607) >> >> Let me know if there is anything I can do to diagnose that problem. >> >> Is FSO Milestone 5 working fine for someone who use Qi? >> >> -- >> Simon Comeau Martel >> si...@comeau.info >> https://comeau.info >> >> Andy Green wrote: >>> Somebody in the thread at some point said: >>> >>> | My install of FSO M5 is not on a SD card. >>> | >>> | As I said, all my problems where related to the fact I was using Qi, >>> | instead of uBoot. >>> >>> It's not immediately obvious how Qi can trash the GSM connection and >>> leave everything else OK. As in, if that was a feature we wanted to add >>> to Qi, I don't know how we would do that. >>> >>> -Andy >> >> _______________________________________________ >> 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 > -- > Joel Newkirk > http://jthinks.com (blog) > http://newkirk.us/om (FR stuff) > > > > > ------------------------------ > > Message: 4 > Date: Sat, 7 Feb 2009 07:46:05 +0530 > From: Carl Lobo <carll...@gmail.com> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: > <df0f90190902061816x380f0f09ge20b4127f67f0...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > >> It's not immediately obvious how Qi can trash the GSM connection and >> leave everything else OK. As in, if that was a feature we wanted to add >> to Qi, I don't know how we would do that. > > This happened to me a couple of times, even rebooting didn't fix it. I > had to completely power down the phone and start it again for it to > start working again. I couldn't look into it then, but I saw several > messages from gsm muxd saying "Unable to open channel CALL". If it > happens again I'll try and check if power cycling the GSM from the > console helps. > > > > ------------------------------ > > Message: 5 > Date: Fri, 06 Feb 2009 21:22:51 -0500 > From: Simon Comeau Martel <si...@comeau.info> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: <498cf07b.7020...@comeau.info> > Content-Type: text/plain; charset=ISO-8859-1 > > You are right; > > / is in read-only mode when I boot from Qi. (and in rw mode when I boot > from uBoot) > > The problem is not in 'checkroot.sh' itself; I compared that file from > Milestone 5 to the one I had on a previous testing version which worked > fine, and the file is exactly the same... Something must have change > elsewhere. > > -- > Simon Comeau Martel > si...@comeau.info > https://comeau.info > > > Joel Newkirk wrote: >> On Fri, 06 Feb 2009 18:57:03 -0500, Simon Comeau Martel >> <si...@comeau.info> >> wrote: >>> I have no idea how it is possible. >>> >>> All I know is that if I boot Milestone 5 via Qi, get the following >>> message in zhone: >>> >>> Usage: Requested ressource GSM with error. >>> >>> And the problem is reproducible; it happen every time. >>> >> >> Read-only filesystem. Once you've booted and see the GSM error in Zhone, >> open a terminal and try "touch test" - you'll get an error noting that >> the >> rootfs is read-only. Qi mounts rootfs read-only at the start - I believe >> /etc/init.d/checkroot.sh is where it's supposed to be remounted >> read/write. >> >> Many things will be 'broken' in this state, like you cannot SSH into it >> because dropbear doesn't start properly when it can't write, and just >> about >> everything with frameworkd is broken. >> >> Presuming this is the case (I'm betting;) try >> >> mount -o remount,rw / >> /etc/init.d/frameworkd restart >> >> stop Zhone, restart it, and it should be able to activate GSM... >> >> >> I've not worked through the logic in /etc/init.d/checkroot.sh or anything >> yet to see where this is failing, but putting the remount command at the >> top of that script will restore your FR to usefulness, remounting / rw >> fairly early in the boot process. (checkroot.sh is supposed to check the >> rootfs for errors /if/ it's ext2/3, and remount r/w afterwards, but >> doesn't >> seem to remount root if it's booted from jffs2 in NAND. As I said I've >> not >> followed the logic of the script yet but am guessing that if it's not >> ext2/3 it never reaches the remount,rw statement there.) >> >> >> j >> >> >> >>> I guess that there could be something causing some kernel module not to >>> load? >>> >>> Maybe I should try upgrading to a more recent version of Qi? The one I >>> use is: >>> >>> qi-s3c2442-master_2ad3ce6ff57753e3.udfu >>> (md5sum: 88979a8310a98d7a2189977194cb2607) >>> >>> Let me know if there is anything I can do to diagnose that problem. >>> >>> Is FSO Milestone 5 working fine for someone who use Qi? >>> >>> -- >>> Simon Comeau Martel >>> si...@comeau.info >>> https://comeau.info >>> >>> Andy Green wrote: >>>> Somebody in the thread at some point said: >>>> >>>> | My install of FSO M5 is not on a SD card. >>>> | >>>> | As I said, all my problems where related to the fact I was using Qi, >>>> | instead of uBoot. >>>> >>>> It's not immediately obvious how Qi can trash the GSM connection and >>>> leave everything else OK. As in, if that was a feature we wanted to >>>> add >>>> to Qi, I don't know how we would do that. >>>> >>>> -Andy >>> _______________________________________________ >>> 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 > > > > ------------------------------ > > Message: 6 > Date: Sat, 7 Feb 2009 14:57:28 +1100 > From: "Alex (Maxious) Sadleir" <maxi...@gmail.com> > Subject: Re: Power Adaptor. > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: > <1e5d79990902061957u6c397cb2s309a35bb7c17e...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > It happened to me once too! Australian 240V plug. > > On Sat, Feb 7, 2009 at 5:54 AM, Chris Syntichakis <ch...@c-64.mobi> wrote: > >> >> Hi, >> >> I had a nice experience with the power adaptor. I just charged the FR and >> after this, I took of the adaptor from the mains. Then accidentally, I >> touched both the pins of the plug (of the adaptor) and guess that.. I >> felt >> a >> small shock! >> >> Now, what's this? Bad construction? of they forgot to put a some >> diodes...? >> >> chris >> -- >> View this message in context: >> http://n2.nabble.com/Power-Adaptor.-tp2285864p2285864.html >> Sent from the Openmoko Support mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.openmoko.org/pipermail/support/attachments/20090207/573e4d1c/attachment-0001.htm > > ------------------------------ > > Message: 7 > Date: Sat, 7 Feb 2009 09:21:16 +0100 > From: Erland Lewin <erl...@lewin.nu> > Subject: Re: FSO Milestone 5 > To: Support for Openmoko Device Owners <support@lists.openmoko.org> > Message-ID: > <a3fe38cf0902070021l1d9a5bdfwa60967907b93b...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > 2009/2/7 Simon Comeau Martel <si...@comeau.info> >> >> / is in read-only mode when I boot from Qi. (and in rw mode when I boot >> from uBoot) > > > I believe you need a file /boot/append-GTA02 (given that you are using a > GTA02 model), which on my Freerunner contains: > > rw loglevel=8 rootdelay=5 glamo_core.slow_memory=1 > > Where rw is supposed to signal that the filesystem is to be mounted in > read-write mode. > > Could the problem be with this file? > > /Erland > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.openmoko.org/pipermail/support/attachments/20090207/106309f2/attachment-0001.htm > > ------------------------------ > > Message: 8 > Date: Sat, 7 Feb 2009 10:27:47 +0100 > From: Petr Vanek <van...@penguin.cz> > Subject: Re: FSO Milestone 5 > To: support@lists.openmoko.org > Message-ID: <20090207102747.5bd49...@penguin.cz> > Content-Type: text/plain; charset=US-ASCII > >>I believe you need a file /boot/append-GTA02 (given that you are using >>a GTA02 model), which on my Freerunner contains: >> >>rw loglevel=8 rootdelay=5 glamo_core.slow_memory=1 > > > what you say is correct but we are treating symptoms, rather then > addressing the issue. as andy pointed, the rootfs should be mounted ro > at first and then remounted to rw which is not happening for some > reason unknown (yet) to us. > > Petr > > > > > > > ------------------------------ > > _______________________________________________ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > > End of support Digest, Vol 8, Issue 13 > ************************************** > _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
