On Thu, 5 Feb 2009 11:27:01 +0200
Alon Levy wrote:
> worked for me on the neo1973 (minus sms, which is the same problem I
> had with previous versions).
What kind of problem is that?
I did a quick search in trac, but couldn't find any bug about it.
Regards,
Daniel Willmann
signature.asc
Descr
On Thu, 2009-02-12 at 09:59 +0530, Andy Green wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Somebody in the thread at some point said:
>
> | Rename the file from checkroot.sh to checkroot, and it achieves the same
> | effect (it is run in a shell instead of being sourced).
> |
> |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Rename the file from checkroot.sh to checkroot, and it achieves the same
| effect (it is run in a shell instead of being sourced).
|
| As I said previously, this was an upstream OE bug which made it's way
|
Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle wrote:
> |
> |> Until current rootfs' get fixed, I dropped the 'ro' option in
> |> the boot options.
> |
> | Thanks to all of you for you help. But I tried something else : Marek
> | Li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle wrote:
|
|> Until current rootfs' get fixed, I dropped the 'ro' option in
|> the boot options.
|
| Thanks to all of you for you help. But I tried something else
On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle wrote:
> Until current rootfs' get fixed, I dropped the 'ro' option in
> the boot options.
Thanks to all of you for you help. But I tried something else : Marek
Lindner just provided the steps for fixing the image. Here it is:
Not sure whether some
Olivier Migeot schrieb:
> - GTA02
> - images (.tar.gz and .bin) from the fso-stable tree.
> - basic uBoot (no update whatsoever since purchase)
> - and of course, booting on the SD card (once again, I don't want to
> break every part at once)
>
>
>
I succesfully use
openmoko-fso-image-glibc
Werner Almesberger escribió:
> Kosa wrote:
>> GTA02v5 # setenv menu_10 Boot for FSO V: setenv bootargs
>> ${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
>> ${mtdparts} rw\; mmcinit\; fatload mmc 1 0x3200 ${sd_image_name}\;
>> bootm 0x3200
>
> A quick remark: You proba
Kosa wrote:
> GTA02v5 # setenv menu_10 Boot for FSO V: setenv bootargs
> ${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
> ${mtdparts} rw\; mmcinit\; fatload mmc 1 0x3200 ${sd_image_name}\;
> bootm 0x3200
A quick remark: You probably want to escape the dollar signs as w
Olivier Migeot escribió:
> Hello ev'ryone.
>
> It's been a while since Freesmartphone's latest milestone (the
> so-called "milestone 5") is out. However, and as willing as I am to
> test it, I still didn't manage to get past the "root not remouted
> read-write as it should" problem.
>
> I saw a l
Hello ev'ryone.
It's been a while since Freesmartphone's latest milestone (the
so-called "milestone 5") is out. However, and as willing as I am to
test it, I still didn't manage to get past the "root not remouted
read-write as it should" problem.
I saw a lot of discussion about how to fix this wi
On Sun, Feb 8, 2009 at 1:34 AM, Petr Vanek wrote:
>>Rename checkroot.sh to just checkroot (remove the .sh).
>>This is an upstream OE bug which made it's way into FSO ms5 - it also
>
> no change here, still ends up ro. shr 29.1, all upgraded now, qi
Doesn't work here either (GTA02, uboot, booting
>Rename checkroot.sh to just checkroot (remove the .sh).
>This is an upstream OE bug which made it's way into FSO ms5 - it also
no change here, still ends up ro. shr 29.1, all upgraded now, qi
Petr
___
support mailing list
support@lists.openmoko.org
h
Rename checkroot.sh to just checkroot (remove the .sh).
This is an upstream OE bug which made it's way into FSO ms5 - it also affected
nslu2-linux SlugOS images.
-- Rod
-Original Message-
From: Joel Newkirk
Date: Sunday, Feb 8, 2009 8:18 am
Subject: Re: FSO Milestone 5
To: Suppor
gt; 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
>>&
>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 shoul
2009/2/7 Simon Comeau Martel
>
> / 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
Wher
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 sh
> 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 phon
ry 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?
>
> --
&g
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
-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
l
Thanks for all the replies, I have downloaded the files and will reflash
tonight. I'll let you know how it goes.
On Fri, Feb 6, 2009 at 11:55 AM, Simon Comeau Martel wrote:
> 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,
> inst
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.
--
Simon Comeau Martel
si...@comeau.info
https://comeau.info
yves mahe wrote:
> I think the problem arise when you try to boot FSO M5 from SD.
> The filesystem is mou
I think the problem arise when you try to boot FSO M5 from SD.
The filesystem is mounted read-only and X don't start.
Unfortunately, it seems that right now, nobody has a patch to correct that.
See also
http://n2.nabble.com/Freesmartphone.org-Milestone-5-%27Calling-All-Stations%27-Release-tp22610
I had that problem.
It was happening to me when I booted with Qi.
Booting from uBoot (from NOR) solved the problem.
After that first 'successful' boot, the GUI start if I boot from Qi, but
then I get other problems. ie: GSM doesn't work.
Booting from uBoot solve the problem.
I have no idea why
worked for me on the neo1973 (minus sms, which is the same problem I had
with previous versions).
used
http://downloads.freesmartphone.org/fso-stable/milestone5/om-gta01/openmoko-fso-image-glibc-ipk--20090202-om-gta01.rootfs.jffs2and
http://downloads.freesmartphone.org/fso-stable/milestone5/om-gta
Has anyone gotten milestone 5 to work? I've tried 5 of the rootfs images
and all I get is a prompt. I keep rebooting, yet same thing.
If you have, can you send me the exact names of the images you used?
Thanks.
--
Paul
Email - pault...@gmail.com
There were moments when he looked on evil simp
28 matches
Mail list logo
