Re: qtomoko v31 boot ploblems
O Sábado, 5 de Febreiro de 2011, Gennady Kupava escribiu: > I just described why that kernel message appears, wants lzo -> no lzo > module -> no mount -> panic. > > Most probably David just did some mistake flashing Qi, kernel or rootfs. > He should first just recheck everything. Othewise for me only Thank you Gennady and Ivan! I've just flashed u-boot-env again, with Gennady's uboot and Gennady's uboot sample environment, and now it boots. Flashing qi again, makes the error appear again, so it seems Qi reads u-boot- env... Now qtomoko dies after a long suspend, but that's another history :( I've had a lot of trouble with my Neo and uboot+suspend (lately gsm died after a suspend when using shr-u), so it might be uboot fault... -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
On 02/06/2011 00:33, community-requ...@lists.openmoko.org wrote: 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... Thank you very much! Giacomo __ 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
Re: qtomoko v31 boot ploblems
В Сбт, 05/02/2011 в 19:31 +0100, Radek Polak пишет: > Ivan Matveev wrote: > > > So everyone who installs QtMoko v31 to NAND and uses Qi shell have this > > problem? > > I am personally using this configuration and it works for me. I am wondering > why it thinks it's lzo. All qtmoko ubifs images are created with: > > mkfs.ubifs -r /tmp/qtmoko-debian -o qtmoko-debian.ubifs -x zlib -m 2048 -e > 126976 -c 2047 > > Note the -zlib option. I think your bootloader is ok, because it tries to > mount ubi. So the problem is most likely in rootfs NAND partition. Kernel > probably reads the compression type (lzo) from your old SHR installation (SHR > uses lzo). But i have no idea why. > > Maybe it would be interesting to reflash it and then boot from SD card and > check if it's flashed ok by dumping the rootfs NAND partition and comparing > with the downloaded image. > > Another option could be booting from SD card and flashing rootfs to NAND with > nandwrite, but i have never done this so cant help much. > > Maybe i could still do jffs2 images for stable releases, if that would help. Hi Radek & Ivan. I just described why that kernel message appears, wants lzo -> no lzo module -> no mount -> panic. Most probably David just did some mistake flashing Qi, kernel or rootfs. He should first just recheck everything. Othewise for me only questionable part is bootloader which load some options from some places and contains some options which only known to person who compiled it. Booting from SD just attempt to mount you NAND fs is next step to solve issue. Other alternative is to boot with NAND u-boot with kernel option and see if it will work. Other alternative to recompile Qi with that option and see if it will work. > I am wondering why it thinks it's lzo. Only idea that this preference is not stored somehow, of it 'attempts' to use lzo somehow before reading that preference. But this is only wild guesses. > Maybe i could still do jffs2 images for stable releases, if that would help. IMHO, this is actually bad idea, as UBI is much better from any point of view, and providing jffs2 version actually will confuse users. Also, where is no reason for ubi not to work, at least it is good idea to figure out what is cause of current issue before providing such 'workarounds'. Best regards, Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
Ivan Matveev wrote: > So everyone who installs QtMoko v31 to NAND and uses Qi shell have this > problem? I am personally using this configuration and it works for me. I am wondering why it thinks it's lzo. All qtmoko ubifs images are created with: mkfs.ubifs -r /tmp/qtmoko-debian -o qtmoko-debian.ubifs -x zlib -m 2048 -e 126976 -c 2047 Note the -zlib option. I think your bootloader is ok, because it tries to mount ubi. So the problem is most likely in rootfs NAND partition. Kernel probably reads the compression type (lzo) from your old SHR installation (SHR uses lzo). But i have no idea why. Maybe it would be interesting to reflash it and then boot from SD card and check if it's flashed ok by dumping the rootfs NAND partition and comparing with the downloaded image. Another option could be booting from SD card and flashing rootfs to NAND with nandwrite, but i have never done this so cant help much. Maybe i could still do jffs2 images for stable releases, if that would help. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
On Sat, 05 Feb 2011 11:16:03 +0300 Gennady Kupava wrote: > В Птн, 04/02/2011 в 13:59 +0100, David Garabana Barro пишет: > > 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? > > Hi, i had this error. > > UBIFS support 2 compression algorithms, zlib and lzo. They can be > mixed with one filesystem. You may specify which one will be used then > creating new files. It can be scepified as mount option. The default > is lzo. lzo is significantly faster but produce bigger files. > > The qtmoko kernel have only zlib compiled in, is if you just run > kernel you'll see your message. To avoid it you should add mount > option for mounting rootfs. it's mount -o compr=zlib and kernel > parameter "rootflags=compr=zlib". this should be active in your > bootloader. So everyone who installs QtMoko v31 to NAND and uses Qi shell have this problem? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
В Птн, 04/02/2011 в 13:59 +0100, David Garabana Barro пишет: > 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? Hi, i had this error. UBIFS support 2 compression algorithms, zlib and lzo. They can be mixed with one filesystem. You may specify which one will be used then creating new files. It can be scepified as mount option. The default is lzo. lzo is significantly faster but produce bigger files. The qtmoko kernel have only zlib compiled in, is if you just run kernel you'll see your message. To avoid it you should add mount option for mounting rootfs. it's mount -o compr=zlib and kernel parameter "rootflags=compr=zlib". this should be active in your bootloader. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
On Fri, 4 Feb 2011 13:59:00 +0100 David Garabana Barro 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? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtomoko v31 boot ploblems
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? signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
