Re: community Digest, Vol 221, Issue 9

2011-02-05 Thread Gennady Kupava
В Птн, 04/02/2011 в 16:18 +0100, giacomo 'giotti' mariani пишет:
 On 02/04/2011 16:08, community-requ...@lists.openmoko.org wrote:
Hi

Just flashed qtmoko v31 in NAND.
It hangs on first boot with kernel panic:

UBIFS error (pid 1): mount_ubifs: 'compressor lzo is not compiled in
Kernel-panic - not syncing: VFS: Unable to mount root fs on
onknown-block(0,0)

Usind qtmoko kernel  qi:


-rw-r--r--  1 user group 29088 feb  4 12:59 qi-31.udfu
-rw-r--r--  1 user group 93585408 feb  4 13:03 qtmoko-debian-v31.ubi
-rw-r--r--  1 user group  2218272 feb  4 12:58 uImage-v31.bin

Any idea?
  Same here.
 
  http://lists.openmoko.org/pipermail/community/2010-December/063993.html
 
  I had QtMoko v28 in NAND(jffs).
  Installed QtMoko v30(ubifs) to NAND. Worked fine.
  Installed Debian to SD with install.sh script started from NAND QtMoko.
 Debian worked
  Installed SRH(ubifs) to NAND. Worked.
  Installed QtMoko v30 to NAND. Can't boot. Same error as yours.
  With some random multiple reflashing of kernel/rootfs/u-boot-env
  managed to make QtMoko v30 boot from NAND.
  Upgraded to QtMoko v31. Can't boot. Same error as yours.
  Kernel complains it cant find root fs. Pity it doesn't show boot
  options in the panic message.
  Installed QtMoko v28 to NAND(jffs). Boots fine.
  QtMoko v31 from SD boots fine and shows regular NAND partition layout.
 
  neo:~# cat /proc/mtd
  dev:size   erasesize  name
  mtd0: 0020 0001 physmap-flash.0
  mtd1: 0004 0002 qi
  mtd2: 0004 0002 depr-ub-env
  mtd3: 0080 0002 kernel
  mtd4: 000a 0002 depr
  mtd5: 0004 0002 identity-ext2
  mtd6: 0f6a 0002 rootfs
 
  Have no idea how to debug this. The problem manifests only on some
  phones so no hope for help from people who know.
  Can someone enlighten me how the partitions are marked in NAND?
 
 I have a similar problem, with gena2x uboot:
 with qtmoko 31 and 32 in NAND, uboot gives me somenthig like:
 
 wrong data CRC
 
 the 28.2 one works good
 any idea?

Yes, i saw this at least 3 times with other users. Cause is you have
wrong environment (u-boot setup). 

Cause of 'wrong data CRC' on NAND is older settings. In old u-boots
configs (and in read-only NOR u-boot config) it's set:

nand read.e 0x3200 kernel 0x20;

Which mean 'load 2Mb from NAND to ram'. if kernel 2mb, it load only
part of kernel and you getting 'wrong CRC' cause kernel had header with
CRC sum and it is checked upon boot.

You should set this to nand read.e 0x3200 kernel 0x30; to load
kernels up to 3Mb...

Now, usual problems:

1. you booting NOR instead of NAND boot (check first line in boot
screen)

2. you forgot to flash u-boot environment (read
http://wiki.openmoko.org/wiki/U-boot-gena2x )

3. you forgot to setup your u-boot environment (read
http://wiki.openmoko.org/wiki/U-boot-gena2x )

Go read that FAQ and ensure you did everything mentioned in it.

Gennady.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: community Digest, Vol 221, Issue 9

2011-02-04 Thread giacomo 'giotti' mariani

On 02/04/2011 16:08, community-requ...@lists.openmoko.org wrote:

  Hi
  
  Just flashed qtmoko v31 in NAND.

  It hangs on first boot with kernel panic:
  
  UBIFS error (pid 1): mount_ubifs: 'compressor lzo is not compiled in

  Kernel-panic - not syncing: VFS: Unable to mount root fs on
  onknown-block(0,0)
  
  Usind qtmoko kernel  qi:
  
  
  -rw-r--r--  1 user group 29088 feb  4 12:59 qi-31.udfu

  -rw-r--r--  1 user group 93585408 feb  4 13:03 qtmoko-debian-v31.ubi
  -rw-r--r--  1 user group  2218272 feb  4 12:58 uImage-v31.bin
  
  Any idea?

Same here.

http://lists.openmoko.org/pipermail/community/2010-December/063993.html

I had QtMoko v28 in NAND(jffs).
Installed QtMoko v30(ubifs) to NAND. Worked fine.
Installed Debian to SD with install.sh script started from NAND QtMoko.
   Debian worked
Installed SRH(ubifs) to NAND. Worked.
Installed QtMoko v30 to NAND. Can't boot. Same error as yours.
With some random multiple reflashing of kernel/rootfs/u-boot-env
managed to make QtMoko v30 boot from NAND.
Upgraded to QtMoko v31. Can't boot. Same error as yours.
Kernel complains it cant find root fs. Pity it doesn't show boot
options in the panic message.
Installed QtMoko v28 to NAND(jffs). Boots fine.
QtMoko v31 from SD boots fine and shows regular NAND partition layout.

neo:~# cat /proc/mtd
dev:size   erasesize  name
mtd0: 0020 0001 physmap-flash.0
mtd1: 0004 0002 qi
mtd2: 0004 0002 depr-ub-env
mtd3: 0080 0002 kernel
mtd4: 000a 0002 depr
mtd5: 0004 0002 identity-ext2
mtd6: 0f6a 0002 rootfs

Have no idea how to debug this. The problem manifests only on some
phones so no hope for help from people who know.
Can someone enlighten me how the partitions are marked in NAND?


I have a similar problem, with gena2x uboot:
with qtmoko 31 and 32 in NAND, uboot gives me somenthig like:

wrong data CRC

the 28.2 one works good
any idea?

Regards

PS What about the boot complaining abaut fsck.auto not found?
__
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community