Re: Kernel panic on Freerunner QtMoko boot
On Sunday, December 16, 2012 01:39:00 AM Harry Prevor wrote: Why is it that I can already boot, for example, Hackable1, which uses jffs2, with my current version of Qi, but I can't boot a jffs2 QtMoko without making changes to Qi then? What is the difference between Hackable1's jffs2 and QtMoko's jffs2? Hmm then you should use this qi also for QtMoko jffs2. Hard to tell why it does not boot. Do you have correct entry in etc/fstab? Also, installing QtMoko to microSD would theoretically fix all of this, right? Yup. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On 12/5/12, Radek Polak pson...@seznam.cz wrote: On Wednesday, December 05, 2012 12:20:55 PM Harry Prevor wrote: You can find and revert the qi commit here: https://github.com/radekp/qi I'm not sure what you mean by this so I didn't do it. Do I really need to make changes to Qi just to create a current jffs2 QtMoko image? Yes you really have to rebuild Qi, the ubifs command line is hardcoded there and you need to change it to jffs2 command line. Why is it that I can already boot, for example, Hackable1, which uses jffs2, with my current version of Qi, but I can't boot a jffs2 QtMoko without making changes to Qi then? What is the difference between Hackable1's jffs2 and QtMoko's jffs2? Also, installing QtMoko to microSD would theoretically fix all of this, right? -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
Looks like my previous message didn't go through. Here's what it said: On 12/2/12, Harry Prevor habsti...@gmail.com wrote: On 11/23/12, Radek Polak pson...@seznam.cz wrote: On Friday, November 23, 2012 03:33:42 PM Harry Prevor wrote: Can jffs2 images of QtMoko still be produced? I'm kind of hesitant to try the v26 release because I'd like to have the latest version for my Freerunner. What exact changes would I have to make to my tarball, and how would I go about changing bootloader arguments? You can find and revert the qi commit here: https://github.com/radekp/qi I'm not sure what you mean by this so I didn't do it. Do I really need to make changes to Qi just to create a current jffs2 QtMoko image? You can easily create jffs2 image from the tarbal as documented here: https://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt I tried to do this today, however I got stuck at some parts: 1. I can skip everything from Step 8 - install QtMoko except for what's under * Install it because I'm not uploading anything to SourceForge, right? 2. How would I go about completing the Step 9 - Linux kernel step? Should everything in this step be done in the qemu buildhost? Can I just download a source tarball instead of using git to check it out? What tarball should I download in that case? Thanks for your help. -- Harry Prevor -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On Wednesday, December 05, 2012 12:20:55 PM Harry Prevor wrote: You can find and revert the qi commit here: https://github.com/radekp/qi I'm not sure what you mean by this so I didn't do it. Do I really need to make changes to Qi just to create a current jffs2 QtMoko image? Yes you really have to rebuild Qi, the ubifs command line is hardcoded there and you need to change it to jffs2 command line. I tried to do this today, however I got stuck at some parts: 1. I can skip everything from Step 8 - install QtMoko except for what's under * Install it because I'm not uploading anything to SourceForge, right? Yes, you dont need to upload it anywhere... 2. How would I go about completing the Step 9 - Linux kernel step? Should everything in this step be done in the qemu buildhost? Can I just download a source tarball instead of using git to check it out? What tarball should I download in that case? I am building it in qemu buildhost. You can download the kernel package here: http://qtmoko.sourceforge.net/debian/ But for converting the tarball to jffs2 you even dont need this. The kernel is alreay installed in tarbal under /boot. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On 11/23/12, Radek Polak pson...@seznam.cz wrote: On Friday, November 23, 2012 03:33:42 PM Harry Prevor wrote: Can jffs2 images of QtMoko still be produced? I'm kind of hesitant to try the v26 release because I'd like to have the latest version for my Freerunner. What exact changes would I have to make to my tarball, and how would I go about changing bootloader arguments? You can find and revert the qi commit here: https://github.com/radekp/qi I'm not sure what you mean by this so I didn't do it. Do I really need to make changes to Qi just to create a current jffs2 QtMoko image? You can easily create jffs2 image from the tarbal as documented here: https://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt I tried to do this today, however I got stuck at some parts: 1. I can skip everything from Step 8 - install QtMoko except for what's under * Install it because I'm not uploading anything to SourceForge, right? 2. How would I go about completing the Step 9 - Linux kernel step? Should everything in this step be done in the qemu buildhost? Can I just download a source tarball instead of using git to check it out? What tarball should I download in that case? Thanks for your help. -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On 11/21/12, Ivan Matveev imatvee...@nm.ru wrote: I had a similar problem. Somehow it went away. See http://lists.openmoko.org/pipermail/community/2012-January/066196.html http://lists.openmoko.org/pipermail/community/2011-December/065998.html Hm. Oddly enough, I tried exactly that (flashing the kernel to u-boot, then reflashing qi, the kernel, and the rootfs all to their correct places), and I'm still getting the same panic. Right now I've got Hackable1 running because it was jffs2, but I'd really like to run QtMoko on my Freerunner. I was able to flash the QtMoko ubifs image a few weeks ago and it worked, so it's odd how nothing seems to be working now. Out of curiosity, why was the switch to ubifs made? Can jffs2 images of QtMoko still be produced? I'm kind of hesitant to try the v26 release because I'd like to have the latest version for my Freerunner. What exact changes would I have to make to my tarball, and how would I go about changing bootloader arguments? I'm not sure if I have Qi installed correctly, which may also be the issue; I flashed it successfully to u-boot, but when I boot while holding AUX to get to DFU mode where I do my flashing I still see U-Boot 1.3.2-moko12 at the top and *** BOOT MENU (NOR) *** as a header. Should I be seeing Qi instead? Any ideas about the above issues? -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On Friday, November 23, 2012 03:33:42 PM Harry Prevor wrote: Out of curiosity, why was the switch to ubifs made? ubsifs is faster and can do mmap. On the other side jffs2 images are smaller. Can jffs2 images of QtMoko still be produced? I'm kind of hesitant to try the v26 release because I'd like to have the latest version for my Freerunner. What exact changes would I have to make to my tarball, and how would I go about changing bootloader arguments? You can find and revert the qi commit here: https://github.com/radekp/qi You can easily create jffs2 image from the tarbal as documented here: https://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt I'm not sure if I have Qi installed correctly, which may also be the issue; I flashed it successfully to u-boot, but when I boot while holding AUX to get to DFU mode where I do my flashing I still see U-Boot 1.3.2-moko12 at the top and *** BOOT MENU (NOR) *** as a header. Should I be seeing Qi instead? No you cant see qi, it does not print anything, it just shortyly vibrates and blinks with led. qi is launched just with simple POWER button. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
I have qi installed. So how can I go to jiffs in nand if I have qtmoko residing on the sd-card? pressing the aux button after a short vibration during the first seconds of booting? as far as I remember my cumbersome way of booting jiffs in nand was the only way to do it, but I mighbt be mistaken. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
robin spielr...@web.de writes: I have qi installed. If you want to use u-boot you should install u-boot :) So how can I go to jiffs in nand if I have qtmoko residing on the sd-card? qi does not support changing boot options if you boot from nand. If the boot options force ubifs then you are out of luck with this particular build of qi. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On Wednesday, November 21, 2012 04:17:19 AM Harry Prevor wrote: Oddly enough, I am still getting this same UBIFS kernel panic even when I successfully flash a JFFS2 image I made of QtMoko onto the Freerunner. I made the image by unzipping the .tar.gz rootfs from SourceForge into a folder and then running mkfs.jffs2 -r qtmoko-rootfs/ -p -e 0x2 -o qtmoko-debian-gta02-v48.jffs2 on the folder. I then ran dfu-util -a rootfs -R -D qtmoko-debian-gta02-v48.jffs2 and it seemed to have flashed successfully, but I still get that darn error on every boot. I've also tried unzipping the .tar.gz into my ext3 uSD card, but it didn't seem to do anything either. Is there any reason that this should be happening? Are there any officially released non-UBIFS rootfses that I can use for the Freerunner? What specifically would y'alls reccommend to debug / fix this? There is still good old v26 release: http://sourceforge.net/projects/qtmoko/files/OldFiles/OldStable-GTA02-v26/ If you want to create jffs2 out of tarbal you also need to change /etc/fstab and most likely root and rootfstype arguments in bootloader. But maybe you could boot it with NOR uboot. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On Fri, 16 Nov 2012 22:19:24 -0500 Harry Prevor habsti...@gmail.com wrote: About a week ago I installed QtMoko on my Freerunner as it's first distribution and all was well. However, for reasons mostly unrelated to this post the install broke so I decided to reinstall QtMoko using instructions from here: http://sourceforge.net/apps/mediawiki/qtmoko/index.php?title=Installation However, to my surprise I wasn't able to get anything to work. Here's what I've tried so far to no avail: --Flashed the Qi bootloader several times; --Flashed the kernel several times to NAND; [...] I had a similar problem. Somehow it went away. See http://lists.openmoko.org/pipermail/community/2012-January/066196.html http://lists.openmoko.org/pipermail/community/2011-December/065998.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
Oddly enough, I am still getting this same UBIFS kernel panic even when I successfully flash a JFFS2 image I made of QtMoko onto the Freerunner. I made the image by unzipping the .tar.gz rootfs from SourceForge into a folder and then running mkfs.jffs2 -r qtmoko-rootfs/ -p -e 0x2 -o qtmoko-debian-gta02-v48.jffs2 on the folder. I then ran dfu-util -a rootfs -R -D qtmoko-debian-gta02-v48.jffs2 and it seemed to have flashed successfully, but I still get that darn error on every boot. I've also tried unzipping the .tar.gz into my ext3 uSD card, but it didn't seem to do anything either. Is there any reason that this should be happening? Are there any officially released non-UBIFS rootfses that I can use for the Freerunner? What specifically would y'alls reccommend to debug / fix this? -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
you can try the jffs from SHR, that's what I do. I flash them to nand with dfu-utils. then you shutdown the freerunner, hold the aux button and simulataneuously press the powerbutton, to get the boot menu. then you press power once again and it should hopefully start shr from nand. in this way you could also check if your sd-card is recocgnized. I had this once, that I had to clean the contacts of the sd-card before it was recocgnized and there- fore a boot from sd (Qtmoko) was possible. best regards robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
robin spielr...@web.de writes: dfu-utils. then you shutdown the freerunner, hold the aux button and simulataneuously press the powerbutton, to get the boot menu. If you do this then you are using the ancient u-boot from NOR. I would recommend installing boot loader to NAND instead, either u-boot or qi. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On 11/16/12, Harry Prevor habsti...@gmail.com wrote: Thanks ahead of time for responses. Well, I've decided to transcribe the entire picture for these five reasons: 1. I was somewhat bored; 2. The phone is useless without an operating system anyways; 3. I figure that posting information in text form may bring that one UNIX old-timer that reads all their mail in Pine one step closer to helping me; 4. I'd like to bump up my thread but posting something along the lines of BUMP! would be a bit too cliché; 5. I am absolutely desperate for any help or tips whatsoever anyone can provide, even if they are wrong. The transcribed text follows: [3.99] mmc0: queuing unknown CIS tuple 0x1b (8 bytes) [4.01] s3c-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [4.02] s3c-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [4.03] mmc0: queuing unknown CIS tuple 0x80 (1 bytes) [4.04] mmc0: queuing unknown CIS tuple 0x81 (1 bytes) [4.05] mmc0: queuing unknown CIS tuple 0x82 (1 bytes) [4.06] mmc0: new SDIO card at address 0001 [4.26] No device for DAI s3c24xx-i2s [4.27] No device for DAI Bluetooth [4.29] asoc: WM8753 HiFi - s3c24xx-i2s mapping ok [4.30] asoc: WM8753 Voice - Bluetooth mapping ok [4.71] input: neo1973gta02 Headset Jack as /devices/platform/soc-audio/sound/card0/input5 [4.74] ALSA device list: [4.75] #0: neo1973gta02 (WM8753) [4.76] TCP westwood registered [4.77] NET: Registered protocol family 17 [4.78] Bridge firewalling registered [4.86] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1) [4.93] regulator_init_complete: incomplete constraints, leaving memldo on [4.96] regulator_init_complete: incomplete constraints, leaving hcldo on [4.98] AR6000 Reg Code = 0x4060 [5.11] pcf50633-rtc pcf50633-rtc.0: setting system clock to 2000-01-01 05:38:23 UTC (946705103) [5.12] UBIFS error (pid 1): ubifs_get_sb: cannot open ubi0:om-gta02-rootfs, error -19 [5.13] VFS: Cannot open root device ubi0:om-gta02-rootfs or unknown-block(0,0) [5.14] Please append a correct root= boot option; here are the available partitions: [5.15] 1f002048 mtdblock0 (driver?) [5.16] 1f01 256 mtdblock1 (driver?) [5.15] 1f02 256 mtdblock2 (driver?) [5.15] 1f038192 mtdblock3 (driver?) [5.15] 1f04 640 mtdblock4 (driver?) [5.15] 1f05 256 mtdblock5 (driver?) [5.15] 1f06 252544 mtdblock6 (driver?) [5.22] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [5.23] Backtrace: [5.24] [c002b66c] (dump_backtrace+0x0/0x10c) from [c032b994] (dump_stack+0x18/0x1c) [5.25] r7:8001 r6:c0024a08 r5:c7ca r4:c0423a30 [5.27] [c032b97c] (dump_stack+0x0/0x1c) from [x032b9e4] (panic+0x4c/0xc8) [5.28] [c032b998] (panic+0x0/0xc8) from [c0008f20] (mount_block_root+0x1f8/0x2bc) [5.29] r3:c7c72ccc r2: r1:c7c19f78 r0:c03aa02c [5.30] [c0008d28] (mount_block_root+0x0/0x2bc) from [c00090e4] (prepare_namespace+0x94/0x1d0) [5.31] [c0009050] (prepare_namespace+0x0/0x1d0) from [c00084dc] (kernel_init+0x10c/0x148) [5.32] r5:c0023d74 r4:c0423080 [5.33] [c00083d0] (kernel_init+0x0/0x148) from [c00403a0] (do_exit+0x0/0x654) [5.34] r5: r4: Looking forward to any responses. -- Harry Prevor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
I'm afraid I can't help much, but... Harry Prevor habsti...@gmail.com writes: [5.12] UBIFS error (pid 1): ubifs_get_sb: cannot open ubi0:om-gta02-rootfs, error -19 This is obviously the key problem. Is ubi0:om-gta02-rootfs a valid specification of the device/partition where the rootfs is? Googling the error message leads to http://lists.openmoko.org/pipermail/community/2011-April/064811.html, which (in my interpretation): - suggests that ubifs may not yet be completely reliable - points to another thread that might have clues for you. Of course, in order to have a working phone, I guess you could install on SD instead. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
