On Wed, Oct 14, 2009 at 10:52:04AM +0200, Thomas Franck wrote:
What I found weird, though, is: I put my old 8GB SD card in the new one
(I used the 512MB card for the booting tests) and it had a very hard
time with it (a lot of bad sectors).. now, I put the card the adapter
and the reader..
Maksim 'max_posedon' Melnikau wrote:
As for you, I defently don't understand why you can't boot from uSD, plz
try some very old images.
Will hopefully be able to try some more tonight..
In the end I ordered a new FR.. got it yesterday.. :D
Hope to get the other one up and running again,
Maksim 'max_posedon' Melnikau wrote:
As for you, I defently don't understand why you can't boot from uSD, plz
try some very old images.
it's all the same for me.. :( stalls..
and I made sure that it indeed uses the SDcard..
Cheers,
--
Thomas
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Hm... can you try compile your own kernel without nand/jffs2 support at all?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
* Thomas Franck wrote, Il 14/10/2009 22:42:
Maksim 'max_posedon' Melnikau wrote:
As for you, I defently don't understand why you can't boot from uSD, plz
try some very old images.
it's all the same for me.. :( stalls..
and I made sure that it indeed uses the SDcard..
I have
Maksim 'max_posedon' Melnikau wrote:
Hm... can you try compile your own kernel without nand/jffs2 support at all?
I can try.. but it will take some time.. need to set up an environment
for that.. I'm a Win32 developer.. and my first try of building the SHR
failed with loads of errors that I had
Maksim 'max_posedon' Melnikau wrote:
I still think that its somehow connected with kernel, at least:
[snip: ugly Kernel Messages]
doesn't looks good
How did you manage to copy those messages? is it because it eventually
boots your FR?
Cheers,
--
Thomas
On Fri, Oct 9, 2009 at 10:23 AM, Thomas Franck thomas.fra...@gmx.comwrote:
How did you manage to copy those messages? is it because it eventually
boots your FR?
Yes, as I said before, NOR uBoot still can boot my neo, so, I copied it
from dmesg output.
Anyway, there I can see kernel bug(I
I still think that its somehow connected with kernel, at least:
[21474549.35] INFO: RCU detected CPU 0 stall (t=4294909870/2000
jiffies)
[21474549.35] [c002dcac] (dump_stack+0x0/0x14) from [c0073ec8]
(__rcu_pending+0x80/0x21c)
[21474549.35] [c0073e48] (__rcu_pending+0x0/0x21c) from
El Friday, 2 de October de 2009 22:41:24 Thomas Franck va escriure:
If those lines are repeating then the kernel has not panicked and is
runing
with a mounted rootfs.
You can try to ssh to the phone or see if it is recognized as an
cdc-ethernet on the pc ( if you are using shr or
On Fri, Oct 2, 2009 at 10:38 PM, Thomas Franck thomas.fra...@gmx.comwrote:
Maksim 'max_posedon' Melnikau wrote:
Try NOR uBoot (at least I use that),
also, you shouldn't by new FR, just boot from SD is always a solution.
Doesn't work for me..
I prepared the 512MB card to boot (following
Yorick Moko wrote:
Have you tried flashin qi and using it to boot from SD?
just trying.. still jiffies, mean CPU stall..
Say, how do I know if Qi is booting off the SD card?
Cheers,
--
Thomas
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Computer system analysis is like child-rearing;
Sebastian Krzyszkowiak wrote:
CPU stall? Leave FR turned on for few hours on that message. About
half year ago I have few times the same problem, and leaving it for 10
minutes helped for me. And I still don't know, what was the cause of
that ;x
Sadly, it didn't help me.. :( it just goes on
On 10/2/09, Thomas Franck thomas.fra...@gmx.com wrote:
Maksim 'max_posedon' Melnikau wrote:
Try NOR uBoot (at least I use that),
also, you shouldn't by new FR, just boot from SD is always a solution.
Doesn't work for me..
I prepared the 512MB card to boot (following the wiki) and booted
Maksim 'max_posedon' Melnikau wrote:
Try NOR uBoot (at least I use that),
also, you shouldn't by new FR, just boot from SD is always a solution.
Doesn't work for me..
I prepared the 512MB card to boot (following the wiki) and booted SDcard
via NOR.. same game.. CPU stall messages.. :(
think
Jose Luis Perez Diez wrote:
If those lines are repeating then the kernel has not panicked and is runing
with a mounted rootfs.
You can try to ssh to the phone or see if it is recognized as an cdc-ethernet
on the pc ( if you are using shr or om2009 that means the module g-eher is
El Wednesday, 30 de September de 2009 21:31:23 Thomas Franck va escriure:
WAY more output.. but no successful boot.. :(
still get the
drivers/input/touchscreen/s3c2410_ts.c: stylus_updown lost event!
drivers/input/touchscreen/s3c2410_ts.c:stylus_action bug.
On 9/30/09, Thomas Franck thomas.fra...@gmx.com wrote:
Maksim 'max_posedon' Melnikau wrote:
So, try uboot.
ok.. I tried uBoot again..
WAY more output.. but no successful boot.. :(
still get the
drivers/input/touchscreen/s3c2410_ts.c: stylus_updown lost event!
Hi..!
Maksim 'max_posedon' Melnikau wrote:
Try NOR uBoot (at least I use that),
will try that when I'm home.. Joachim Ott also suggested I try NOR boot
and I did without success.. (with Qi installed, though)
also, you shouldn't by new FR, just boot from SD is always a solution.
right..
Hi..
This is a re-post from the support ML.. community is way more active,
hope to get some more hints here.. :)
I can access the NOR boot menu.. and since then I have reflashed the
kernel, the system image and the boot loader..
I also disassembled the FR (for the first time!!) to see if I can
I have same missages too, Qi can't boot my system from nand too,
BUT It successfully boots with uboot (actually not always, but boots),
there is opinion that Qi doesn't handle badblocks on nand correctly,
or smth like this.
So, try uboot.
On 9/30/09, Thomas Franck thomas.fra...@gmx.com wrote:
Maksim 'max_posedon' Melnikau wrote:
I have same missages too, Qi can't boot my system from nand too,
BUT It successfully boots with uboot (actually not always, but boots),
there is opinion that Qi doesn't handle badblocks on nand correctly,
or smth like this.
So, try uboot.
Cool.. so
Maksim 'max_posedon' Melnikau wrote:
So, try uboot.
ok.. I tried uBoot again..
WAY more output.. but no successful boot.. :(
still get the
drivers/input/touchscreen/s3c2410_ts.c: stylus_updown lost event!
drivers/input/touchscreen/s3c2410_ts.c:stylus_action bug.
23 matches
Mail list logo