On Wed, Feb 11, 2009 at 9:34 AM, Marek Lindner wrote:
> Hope it helps someone,
Awesome, it works. Thanks a _lot_! :)
--
Olivier
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Hello Everyone,
On 2009 February 11 Wednesday 16:34:54 Marek Lindner wrote:
> On Wednesday 04 February 2009 19:00:19 Andy Green wrote:
> > Having rootfs mount ro initially is a safety feature, it'd be sad if we
> > have to take it out because the rootfs can't manage doing a mount
> > /dev/root / -o
On Wednesday 04 February 2009 19:00:19 Andy Green wrote:
> Having rootfs mount ro initially is a safety feature, it'd be sad if we
> have to take it out because the rootfs can't manage doing a mount
> /dev/root / -oremount,rw in the initscripts.
Not sure whether somebody was able to properly fix i
On Tue, Feb 03, 2009 at 03:07:00PM +0100, Petr Vanek wrote:
> >> It's a good guess... does mount say that it's still ro?
>
> i have flashed u-boot and it starts OK. reflashed qi and have the
> problem again. interestingly enough i tried to boot fso from nor menu
> once and then qi was able to bo
Olivier Migeot wrote (ao):
> Would anyone have an idea on how to fix that? There should be a way to
> explain uBoot how to deal with this, but I don't know it yet...
Isn't this just a bug in FSO MS5 and shouldn't we wait until MS5.1 gets
released?
I would rather not leave qi and have downgraded t
On Tue, Feb 3, 2009 at 11:58 AM, Olivier Migeot wrote:
> I've just tried the image on my SD card (no qi, then, I guess), and if
> fails all the same.
Ok, I tried again (my FR's battery being depleted in the meantime),
and here's the results. My FR is using uBoot, boots nicely on the
internal fla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>> It's a good guess... does mount say that it's still ro?
|
| i have flashed u-boot and it starts OK. reflashed qi and have the
| problem again. interestingly enough i tried to boot fso from nor menu
| once
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| | rw rootdelay=3 glamo_core.slow_memory=1
|
|
| that's for a SHR kernel mentioned somewhere on this list (
| uImage-2.6.28-rc4-ms5-fixes_34240a1c06ae3618.bin ) but not fixing the
| White
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|
| On Tue, Feb 3, 2009 at 9:48 PM, Petr Vanek mailto:van...@penguin.cz>> wrote:
|
| ...
| i understand that this is when you run system from sd card. i run
| system from NAND and for that i need
On Tue, Feb 3, 2009 at 9:48 PM, Petr Vanek wrote:
> ...
> i understand that this is when you run system from sd card. i run
> system from NAND and for that i need to edit the boot environment
>
...
> I had flashed u-boot back but would love to use qi again as it can start
> the neo on a short pwr
>Just create a textfile "/boot/append-GTA02" and put whatever is needed
>as kernel parameters in there - here is mine:
>rw rootdelay=3 glamo_core.slow_memory=1
>
>Refer to http://wiki.openmoko.org/wiki/Qi for more details
Stefan,
i understand that this is when you run system from sd card. i run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|
| opps.. the message saye "glamo3362.slow_memory" NOT glamo33362 as i wrote!
Wah my mistake... it really is glamo_core, it appears in /sys as
/sys/module/glamo_core/parameters/slow_memory
I read my wron
opps.. the message saye "glamo3362.slow_memory" NOT glamo33362 as i wrote!
Chris Syntichakis wrote:
>
>
> strange.. I get an "glamo33362.slow_memory" unknown boot option
> should I upgrade the QI?
>
> chris
>
>
> Andy Green wrote:
>>
>>
>> glamo3362.slow_memory=1
>>
>>
>>
>
>
--
strange.. I get an "glamo33362.slow_memory" unknown boot option
should I upgrade the QI?
chris
Andy Green wrote:
>
>
> glamo3362.slow_memory=1
>
>
>
--
View this message in context:
http://n2.nabble.com/Freesmartphone.org-Milestone-5-%27Calling-All-Stations%27-Release-tp2261004p2265242
Hi Andy,
| rw rootdelay=3 glamo_core.slow_memory=1
>
that's for a SHR kernel mentioned somewhere on this list (
uImage-2.6.28-rc4-ms5-fixes_34240a1c06ae3618.bin ) but not fixing the
White/Noisy SOD for me.
glamo3362.slow_memory=1
Your latest compiled kernel
uImage-moredrivers-GTA02_andy-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| I have the QT on the rootfs, so I put the FSO on a uSD (I have
installed the
| QI).
|
| ITS impossible to boot from the uSD, QI just seems to ignore the FSO
and it
| just boots to NAND kernel..
|
| I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/2/3 Stefan Fröbe mailto:frob...@googlemail.com>
|
|
| Just create a textfile "/boot/append-GTA02" and put whatever is
| needed as kernel parameters in there - here is mine:
| rw rootdelay=3
Hi,
I have the QT on the rootfs, so I put the FSO on a uSD (I have installed the
QI).
ITS impossible to boot from the uSD, QI just seems to ignore the FSO and it
just boots to NAND kernel..
I HAVE no problems with a similar uSD (has FDOM) but only with the FSO..
Chris
--
View this message in
On Tue, Feb 3, 2009 at 5:00 PM, c_c wrote:
>
> Hi,
> Same here. Needed the rw rootdelay=3 parameters for qi.
And what to do when the problems occurs _without_ qi?
Thanks ;)
--
LC
___
Openmoko community mailing list
community@lists.openmoko.org
http
Hi,
Same here. Needed the rw rootdelay=3 parameters for qi.
--
View this message in context:
http://n2.nabble.com/Freesmartphone.org-Milestone-5-%27Calling-All-Stations%27-Release-tp2261004p2264011.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
2009/2/3 Stefan Fröbe
>
> Just create a textfile "/boot/append-GTA02" and put whatever is needed as
> kernel parameters in there - here is mine:
> rw rootdelay=3 glamo_core.slow_memory=1
>
Thanks ! That did the trick with my Qi
___
Openmoko community m
On Tue, Feb 3, 2009 at 3:07 PM, Petr Vanek wrote:
...
> the trouble is that i don't know how to change the ro flag for qi (i
> can imagine i could place a kernel on my card and add append file with
> rw and root=/dev/mtd device and of the nand flash?)
Hi Petr,
Just create a textfile "/boot/appe
>> It's a good guess... does mount say that it's still ro?
i have flashed u-boot and it starts OK. reflashed qi and have the
problem again. interestingly enough i tried to boot fso from nor menu
once and then qi was able to boot it ok afterwards. so i am not sure
what exactly happens there for t
2009/2/3 Petr Vanek
> On Tue, 03 Feb 2009 09:28:17 +0100
> Michele Renda (MR) wrote:
>
> >On 03/02/2009 09:21, c_c wrote:
> >> Well, the
> >> openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz and
> >> openmoko-fso-illume-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz
> >> images bo
On Tue, Feb 3, 2009 at 12:43 PM, KaZeR wrote:
> Why that? Qi boots from uSD card first by default.
Yeah, but I never flashed my bootloader, so I'd like to know where Qi
would come from, then.
--
LC
___
Openmoko community mailing list
community@lists
> -Message d'origine-
> De : community-boun...@lists.openmoko.org
> [mailto:community-boun...@lists.openmoko.org] De la part de
> Olivier Migeot
> Envoyé : mardi 3 février 2009 11:58
> À : List for Openmoko community discussion
> Objet : Re: Freesmartphone.or
Hi,
Andy Green wrote:
>
> It's a good guess... does mount say that it's still ro?
>
Can't check. Busybox seems to be down too.
Andy Green wrote:
>
> Did it try to start X and left some log anywhere?
>
Well, all logs are on volatile - which evaporates when i try to mount the
uSD card on my
On Tue, Feb 3, 2009 at 11:47 AM, Petr Vanek wrote:
> this happens only with qi. could it be related to ro kernel
> parameter?
I've just tried the image on my SD card (no qi, then, I guess), and if
fails all the same.
--
LC
___
Openmoko community mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| this happens only with qi. could it be related to ro kernel
| parameter?
It's a good guess... does mount say that it's still ro? Normally an
initscript will take care about remount rw after it had opportu
On Tue, 03 Feb 2009 09:28:17 +0100
Michele Renda (MR) wrote:
>On 03/02/2009 09:21, c_c wrote:
>> Well, the
>> openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz and
>> openmoko-fso-illume-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz
>> images both boot and drop me into tty1 console
On 03/02/2009 09:21, c_c wrote:
> Well, the openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz and
> openmoko-fso-illume-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz images
> both boot and drop me into tty1 console. Cant get X to run on these. No
> busybox either.
>Any pointers ?
Hi,
Stefan Schmidt wrote:
>
> No more words from our side. Grab it while it's hot, have fun and happy
> hacking.
>
> http://downloads.freesmartphone.org/fso-stable/milestone5/
>
Well, the openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz and
openmoko-fso-illume-image-glibc-ipk--200
sorry this message is for the list too ;P
2009/2/3 David Reyes Samblas Martinez :
> bravo, awesome work guys.downloading a willing to take a look, I have
> some presentations this months in some universities and in one are
> very interested in dbus development :) comiing with this milestone 5
> sur
33 matches
Mail list logo
