Re: qtopia - kernel panic
El Tuesday, 9 de September de 2008 04:32:36 Edgar D' Souza va escriure: Hi Bernhard, Wow - but earlier posts (in this very thread, I think) implied that this was not possible - to boot from an ext3 partition by treating it as ext2... The problem is that if the desired filesystem is compiled as a module. When the neos try to mount / can only use built-in filesystems support. Newer ext2 is built-in on newer kernels but there used to be ext3 alone. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
To see how easy it is to move from one to the other: this creates an ext3 from ext2: tune2fs -j device and this the other way round: tune2fs -O ^has_journal device; e2fsck device While you could move from ext2 to ext3 with a running writeable mounted partition without any problems, the other way round is more problematic and should only be done with unmounted partitions. regards On Tue, Sep 9, 2008 at 4:32 AM, Edgar D' Souza [EMAIL PROTECTED]wrote: On Mon, Sep 8, 2008 at 6:08 PM, Bernhard Schauer [EMAIL PROTECTED] wrote: Hi Ed, as ext2 is a subset of ext3 it is also mountable as ext2 (but then without journalling). It is required that the Filesystem was clean unmounted before to do that. Hi Bernhard, Wow - but earlier posts (in this very thread, I think) implied that this was not possible - to boot from an ext3 partition by treating it as ext2... Well, I did my sdcard partition as ext2, but I think I need to read up about ext3/ext2 to understand what you have said. Thanks for the info! Regards Ed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
The problem is that if the desired filesystem is compiled as a module. When the neos try to mount / can only use built-in filesystems support. Yes and ext2 is available built-in along with ext3. regards, Bernhard ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
AFAI remember, he said his rootfs was ext3 not ext2 Cheers Ed. Hi Ed, as ext2 is a subset of ext3 it is also mountable as ext2 (but then without journalling). It is required that the Filesystem was clean unmounted before to do that. best regards, Bernhard ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Mon, Sep 8, 2008 at 3:03 PM, Bernhard Schauer
[EMAIL PROTECTED] wrote:
Hi Ali,
sorry for that delay, but I was on vacation last week. If this issue was not
solved, I'd suggest to enter the following on bootscreen:
setenv bootargs console=ttySAC2,115200 rootfstype=ext2 root=/dev/mmcblk0p2
rootdelay=5 ${mtdparts} init=/sbin/init ro
mmcinit
fatload mmc 1 0x3200 ${sd_image_name}
bootm 0x3200
AFAI remember, he said his rootfs was ext3 not ext2
Cheers
Ed.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Mon, Sep 8, 2008 at 6:08 PM, Bernhard Schauer [EMAIL PROTECTED] wrote: Hi Ed, as ext2 is a subset of ext3 it is also mountable as ext2 (but then without journalling). It is required that the Filesystem was clean unmounted before to do that. Hi Bernhard, Wow - but earlier posts (in this very thread, I think) implied that this was not possible - to boot from an ext3 partition by treating it as ext2... Well, I did my sdcard partition as ext2, but I think I need to read up about ext3/ext2 to understand what you have said. Thanks for the info! Regards Ed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Mon, Sep 1, 2008 at 9:31 AM, Ali [EMAIL PROTECTED] wrote:
Hi,
This is the output of printenv on u-boot prompt.
=
menu_1=Boot from microSD (FAT+ext2): setenv bootargs ${bootargs_base}
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} init=/sbin/init
ro; mmcinit; fatload mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
[...]
menu_9=Boot 200808 from microSD (FAT+ext3): setenv bootargs ${bootargs_base}
rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
Although a n00b at this myself, the only difference I can see between
menu_1 and menu_9 above is that menu_1 contains an init=/sbin/init
clause while menu_9 does not... however, when I tried Qtopia on SD
(FAT + ext2) I didn't muck around with any of this, and menu_1 worked
fine for me... is it possible that adding the init=/sbin/init clause
would help?
Ed.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
Just to clarify - you are following these steps: 1) Boot Freerunner to Nand 2) Connect via USB cable on host 3) On host terminal giving the following commands: sudo chown uucp.uucp /dev/ttyACM0 followed by sudo cu -l /dev/ttyACM0 and you are getting a connected on the host but no U-Boot prompt on the host? Is this correct? Rakshat On Fri, Aug 29, 2008 at 1:37 PM, rakshat hooja [EMAIL PROTECTED] wrote: This is what i get when i try connect to u-boot through cu. 1) I connect the usb and start the new freerunner u-boot menu. 2) Then i use this command at host prompt.: [EMAIL PROTECTED] /]# sudo chown uucp.uucp /dev/ttyACM0 [EMAIL PROTECTED] /]# sudo cu -l /dev/ttyACM0 Connected.t This is wha ti get on host pc. I try selecting the console on the usb but it comes back to the same menu on freerunner. Console to USB is already default. setting console to USB will come back to the same menu. just try pressing enter after the connected on the host andd you should get GTA02v5 # U-Boot prompt. Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
rakshat hooja wrote: Just to clarify - you are following these steps: 1) Boot Freerunner to Nand 2) Connect via USB cable on host 3) On host terminal giving the following commands: sudo chown uucp.uucp /dev/ttyACM0 followed by sudo cu -l /dev/ttyACM0 and you are getting a connected on the host but no U-Boot prompt on the host? Is this correct? Rakshat On Fri, Aug 29, 2008 at 1:37 PM, rakshat hooja [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: This is what i get when i try connect to u-boot through cu. 1) I connect the usb and start the new freerunner u-boot menu. 2) Then i use this command at host prompt.: [EMAIL PROTECTED] /]# sudo chown uucp.uucp /dev/ttyACM0 [EMAIL PROTECTED] /]# sudo cu -l /dev/ttyACM0 Connected.t This is wha ti get on host pc. I try selecting the console on the usb but it comes back to the same menu on freerunner. Console to USB is already default. setting console to USB will come back to the same menu. just try pressing enter after the connected on the host andd you should get GTA02v5 # U-Boot prompt. Rakshat ___ support mailing list support@lists.openmoko.org mailto:support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com http://www.firefox.com -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com http://www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support - Just to clarify - you are following these steps: 1) Boot Freerunner to Nand 2) Connect via USB cable on host 3) On host terminal giving the following commands: sudo chown uucp.uucp /dev/ttyACM0 followed by sudo cu -l /dev/ttyACM0 and you are getting a connected on the host but no U-Boot prompt on the host? -- Yes exactly this is what is happening. I am also pressing enter on the host after getting connected. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
rakshat hooja wrote:
Just to clarify - you are following these steps:
1) Boot Freerunner to Nand
2) Connect via USB cable on host
3) On host terminal giving the following commands:
sudo chown uucp.uucp /dev/ttyACM0
followed by
sudo cu -l /dev/ttyACM0
and you are getting a connected on the host but no U-Boot prompt on
the host?
Is this correct?
Rakshat
On Fri, Aug 29, 2008 at 1:37 PM, rakshat hooja [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
This is what i get when i try connect to u-boot through cu.
1) I connect the usb and start the new freerunner u-boot menu.
2) Then i use this command at host prompt.:
[EMAIL PROTECTED] /]# sudo chown uucp.uucp /dev/ttyACM0
[EMAIL PROTECTED] /]# sudo cu -l /dev/ttyACM0
Connected.t
This is wha ti get on host pc.
I try selecting the console on the usb but it comes back to
the same menu on freerunner.
Console to USB is already default. setting console to USB will
come back to the same menu. just try pressing enter after the
connected on the host andd you should get
GTA02v5 # U-Boot prompt.
Rakshat
___
support mailing list
support@lists.openmoko.org mailto:support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
--
--
Please use Firefox as your web browser. Its protects you from
spyware and is also a very feature rich browser.
www.firefox.com http://www.firefox.com
--
--
Please use Firefox as your web browser. Its protects you from spyware
and is also a very feature rich browser.
www.firefox.com http://www.firefox.com
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
I was able to access u-boot terminal and changed the environment
variable mentioned in the website and saved env variable and i switch
off the phone .This is the environment i set.
setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base}
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\;
fatload mmc 1 0x3200 \${sd_image_name}\; bootm 0x3200
Start the neo-freerunner with Nand u-boot menu ,a new entry is displayed
and i select the new entry to boot the microsd card .
I get the same kernel panic.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Fri, Aug 29, 2008 at 7:04 PM, arne anka [EMAIL PROTECTED] wrote:
I was able to access u-boot terminal and changed the environment
variable mentioned in the website and saved env variable and i switch
off the phone .This is the environment i set.
setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs
\${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
\${mtdparts} ro\; mmcinit\; fatload mmc 1 0x3200 \${sd_image_name}\;
bootm 0x3200
Start the neo-freerunner with Nand u-boot menu ,a new entry is displayed
and i select the new entry to boot the microsd card .
I get the same kernel panic.
TRy this if your kernel is on FAT and rootfs on ext3
setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs
\${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5
\${mtdparts} ro\; mmcinit\; fatload mmc 1 0x3200
\${sd_image_name}\; bootm 0x3200
Rakshat
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
TRy this if your kernel is on FAT and rootfs on ext3
setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base}
rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\;
fatload mmc 1 0x3200 \${sd_image_name}\; bootm 0x3200
Rakshat
I have tried this also .But the same problem.kernel panic
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
of course, what did you expect? afair your root is ext3 and you set again ext2 rootfstype should read _ext3_ ... rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 ... make sure that you got a recent u-boot. and please: do not simply hit reply and send but shorten the mails! I have even tried with rootfstype=ext3 .I have same kernel panic error.Anyways i just expect the u-boot the qtopia image and i keep the previous discussion in my mail so that others can follow it and help me out. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
rakshat hooja wrote: On Wed, Aug 27, 2008 at 7:13 PM, arne anka [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I did connect to the cu using this command : cu -l /dev/ttyACM0 But still the same response its going back to the menu Are you not getting the u-boot terminal on the host PC? Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support No,I am not getting the u-boot terminal on host pc .I have connected the cu and tried to select the option for usb.It is returning back th same u-bootmenu on freerunner. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Fri, Aug 29, 2008 at 9:08 AM, syed yaqoob ali [EMAIL PROTECTED]wrote: rakshat hooja wrote: On Wed, Aug 27, 2008 at 7:13 PM, arne anka [EMAIL PROTECTED] wrote: I did connect to the cu using this command : cu -l /dev/ttyACM0 But still the same response its going back to the menu Are you not getting the u-boot terminal on the host PC? Rakshat -- No,I am not getting the u-boot terminal on host pc .I have connected the cu and tried to select the option for usb.It is returning back th same u-bootmenu on freerunner. What happens on the host computer after you run cu -l /dev/ttyACM0 And did you do sudo chown uucp.uucp /dev/ttyACM0 before running cu? My output is as follows [EMAIL PROTECTED]:~$ sudo chown uucp.uucp /dev/ttyACM0 [EMAIL PROTECTED]:~$ sudo cu -l /dev/ttyACM0 Connected. ut: usbtty Err: usbtty PCB rev: 0x000 Power: 0mA switching led 2 0 switching led 2 1 switching led 2 0 GTA02v5 # DEVICE_CONFIGURED: 1 DEVICE_CONFIGURED: 1 GTA02v5 # works each and every time. Also in new kernels you no longer need to set console to USB as it is already set by default (atleast in my experience. Update me if this works. Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
rakshat hooja wrote: On Fri, Aug 29, 2008 at 9:08 AM, syed yaqoob ali [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: rakshat hooja wrote: On Wed, Aug 27, 2008 at 7:13 PM, arne anka [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I did connect to the cu using this command : cu -l /dev/ttyACM0 But still the same response its going back to the menu Are you not getting the u-boot terminal on the host PC? Rakshat No,I am not getting the u-boot terminal on host pc .I have connected the cu and tried to select the option for usb.It is returning back th same u-bootmenu on freerunner. What happens on the host computer after you run cu -l /dev/ttyACM0 And did you do sudo chown uucp.uucp /dev/ttyACM0 before running cu? My output is as follows [EMAIL PROTECTED]:~$ sudo chown uucp.uucp /dev/ttyACM0 [EMAIL PROTECTED]:~$ sudo cu -l /dev/ttyACM0 Connected. ut: usbtty Err: usbtty PCB rev: 0x000 Power: 0mA switching led 2 0 switching led 2 1 switching led 2 0 GTA02v5 # DEVICE_CONFIGURED: 1 DEVICE_CONFIGURED: 1 GTA02v5 # works each and every time. Also in new kernels you no longer need to set console to USB as it is already set by default (atleast in my experience. Update me if this works. Rakshat ___ support mailing list support@lists.openmoko.org mailto:support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com http://www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support This is what i get when i try connect to u-boot through cu. 1) I connect the usb and start the new freerunner u-boot menu. 2) Then i use this command at host prompt.: [EMAIL PROTECTED] /]# sudo chown uucp.uucp /dev/ttyACM0 [EMAIL PROTECTED] /]# sudo cu -l /dev/ttyACM0 Connected. This is wha ti get on host pc. I try selecting the console on the usb but it comes back to the same menu on freerunner. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
rakshat hooja wrote: On Wed, Aug 27, 2008 at 9:47 AM, syed yaqoob ali [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Yorick Moko wrote: On Tue, Aug 26, 2008 at 2:56 PM, syed yaqoob ali [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: arne anka wrote: Warning : unable to open an initial console Kernel panic - not syncing : no init found .try passing init= option to kernel what file systesm did you use on these partitions and how did you proceed exactly when installing? ___ support mailing list support@lists.openmoko.org mailto:support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, I have used vfat for first partition and ext3 for the second partition. This is the procedure i have followed for installing qtopia on sdcard. My Host PC has FC 9. 1) connected to Neo freerunner by SSH 2) Partitioned SD card : fdisk /dev/mmcblk0 created a 8 mb partition for kernel and another one for the rootfs which took up all the remaining space Command (m for help): d Selected partition 1 Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-983, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (18-983, default 18): Using default value 18 Last cylinder or +size or +sizeM or +sizeK (18-983, default 983): Using default value 983 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy 3)Got an fdisk warning so umounted : umount /dev/mmcblk0p1 redone the step2 again.No error second time. 4)Formatted the SDcard : for first partition. a) mkfs.vfat /dev/mmcblk0p1 for second partition. b)mkfs.ext3 /dev/mmcblk0p2 5)Mounted the sdcard: mount /dev/mmcblk0p1 /media/card mkdir /media/card/boot mkdir /media/mmcblk0p2 mount /dev/mmcblk0p2 /media/mmcblk0p2 6)unpacked qtopia: got this two files : uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin qtopia-4.3.2-gta02-rootfs-07172049.jffs2 7)Mounted the rootfs on loopback device: export loop=$(losetup -f) losetup $loop rootfs.jffs2 modprobe block2mtd block2mtd=$loop,131072 modprobe jffs2 modprobe mtdblock mkdir mntpnt mount -t jffs2 -o ro /dev/mtdblock0 mntpnt 8)created compressed tarball. tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -c mntpnt 9)Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner: scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz [EMAIL PROTECTED]:/media/mmcblk0p2/ mailto:[EMAIL PROTECTED]:/media/mmcblk0p2/ 10)Unpack the rootfilesystem: cd /media/mmcblk0p2 tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm -f /media/mmcblk0p2/boot/* 11) Installed kernel. mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin scp uImage.bin [EMAIL PROTECTED]:/media/card/boot/ mailto:[EMAIL PROTECTED]:/media/card/boot/ scp uImage.bin [EMAIL PROTECTED]:/media/card/ mailto:[EMAIL PROTECTED]:/media/card/ 12)shutdown and boot in qtopia. Booted from Sdcard Now when kernel is booting .It's giving kernel panic. Regards Syed Yaqoob Ali ___ support mailing list support@lists.openmoko.org mailto:support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support As far as I know: whan you want to boot fat + ext3 you need to edit u-boot entry fat + ext2 works straight out of the box (after updating u-boot) ___ support mailing list support@lists.openmoko.org mailto:support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support How do i edit the u-boot entry for booting fat + ext3 ? Can someone pls provide the procedure. Have you tried the procedure on this wiki page http://wiki.openmoko.org/wiki/Booting_from_SD#Add_uboot_boot_entry Rakshat
Re: qtopia - kernel panic
I am trying to boot into the NAND uboot menu. But when i am selecting the set console to usb .It is returining back to the same menu again. you need to connect with cu or neocon or another terminal -- see http://wiki.openmoko.org/wiki/Bootloader#Bootloader_prompt btw: please cut the forwarded text to a sensible minimum, having to scroll down several pages for a few lines of new text is rather tedious. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Wed, Aug 27, 2008 at 7:13 PM, arne anka [EMAIL PROTECTED] wrote: I did connect to the cu using this command : cu -l /dev/ttyACM0 But still the same response its going back to the menu Are you not getting the u-boot terminal on the host PC? Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
arne anka wrote: Warning : unable to open an initial console Kernel panic - not syncing : no init found .try passing init= option to kernel what file systesm did you use on these partitions and how did you proceed exactly when installing? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, I have used vfat for first partition and ext3 for the second partition. This is the procedure i have followed for installing qtopia on sdcard. My Host PC has FC 9. 1) connected to Neo freerunner by SSH 2) Partitioned SD card : fdisk /dev/mmcblk0 created a 8 mb partition for kernel and another one for the rootfs which took up all the remaining space Command (m for help): d Selected partition 1 Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-983, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (18-983, default 18): Using default value 18 Last cylinder or +size or +sizeM or +sizeK (18-983, default 983): Using default value 983 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy 3)Got an fdisk warning so umounted : umount /dev/mmcblk0p1 redone the step2 again.No error second time. 4)Formatted the SDcard : for first partition. a) mkfs.vfat /dev/mmcblk0p1 for second partition. b)mkfs.ext3 /dev/mmcblk0p2 5)Mounted the sdcard: mount /dev/mmcblk0p1 /media/card mkdir /media/card/boot mkdir /media/mmcblk0p2 mount /dev/mmcblk0p2 /media/mmcblk0p2 6)unpacked qtopia: got this two files : 1. uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin 2. qtopia-4.3.2-gta02-rootfs-07172049.jffs2 7)Mounted the rootfs on loopback device: export loop=$(losetup -f) losetup $loop rootfs.jffs2 modprobe block2mtd block2mtd=$loop,131072 modprobe jffs2 modprobe mtdblock mkdir mntpnt mount -t jffs2 -o ro /dev/mtdblock0 mntpnt 8)created compressed tarball. tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -c mntpnt 9)Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner: scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz [EMAIL PROTECTED]:/media/mmcblk0p2/ 10)Unpack the rootfilesystem: cd /media/mmcblk0p2 tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm -f /media/mmcblk0p2/boot/* 11) Installed kernel. mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin scp uImage.bin [EMAIL PROTECTED]:/media/card/boot/ scp uImage.bin [EMAIL PROTECTED]:/media/card/ 12)shutdown and boot in qtopia. Booted from Sdcard Now when kernel is booting .It's giving kernel panic. Regards Syed Yaqoob Ali ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
Yorick Moko wrote: On Tue, Aug 26, 2008 at 2:56 PM, syed yaqoob ali [EMAIL PROTECTED] wrote: arne anka wrote: Warning : unable to open an initial console Kernel panic - not syncing : no init found .try passing init= option to kernel what file systesm did you use on these partitions and how did you proceed exactly when installing? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Hi, I have used vfat for first partition and ext3 for the second partition. This is the procedure i have followed for installing qtopia on sdcard. My Host PC has FC 9. 1) connected to Neo freerunner by SSH 2) Partitioned SD card : fdisk /dev/mmcblk0 created a 8 mb partition for kernel and another one for the rootfs which took up all the remaining space Command (m for help): d Selected partition 1 Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-983, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (18-983, default 18): Using default value 18 Last cylinder or +size or +sizeM or +sizeK (18-983, default 983): Using default value 983 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy 3)Got an fdisk warning so umounted : umount /dev/mmcblk0p1 redone the step2 again.No error second time. 4)Formatted the SDcard : for first partition. a) mkfs.vfat /dev/mmcblk0p1 for second partition. b)mkfs.ext3 /dev/mmcblk0p2 5)Mounted the sdcard: mount /dev/mmcblk0p1 /media/card mkdir /media/card/boot mkdir /media/mmcblk0p2 mount /dev/mmcblk0p2 /media/mmcblk0p2 6)unpacked qtopia: got this two files : uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin qtopia-4.3.2-gta02-rootfs-07172049.jffs2 7)Mounted the rootfs on loopback device: export loop=$(losetup -f) losetup $loop rootfs.jffs2 modprobe block2mtd block2mtd=$loop,131072 modprobe jffs2 modprobe mtdblock mkdir mntpnt mount -t jffs2 -o ro /dev/mtdblock0 mntpnt 8)created compressed tarball. tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -c mntpnt 9)Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner: scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz [EMAIL PROTECTED]:/media/mmcblk0p2/ 10)Unpack the rootfilesystem: cd /media/mmcblk0p2 tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm -f /media/mmcblk0p2/boot/* 11) Installed kernel. mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin scp uImage.bin [EMAIL PROTECTED]:/media/card/boot/ scp uImage.bin [EMAIL PROTECTED]:/media/card/ 12)shutdown and boot in qtopia. Booted from Sdcard Now when kernel is booting .It's giving kernel panic. Regards Syed Yaqoob Ali ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support As far as I know: whan you want to boot fat + ext3 you need to edit u-boot entry fat + ext2 works straight out of the box (after updating u-boot) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support How do i edit the u-boot entry for booting fat + ext3 ? Can someone pls provide the procedure. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Wed, Aug 27, 2008 at 9:47 AM, syed yaqoob ali [EMAIL PROTECTED]wrote: Yorick Moko wrote: On Tue, Aug 26, 2008 at 2:56 PM, syed yaqoob ali [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: arne anka wrote: Warning : unable to open an initial console Kernel panic - not syncing : no init found .try passing init= option to kernel what file systesm did you use on these partitions and how did you proceed exactly when installing? ___ support mailing [EMAIL PROTECTED]://lists.openmoko.org/mailman/listinfo/support Hi, I have used vfat for first partition and ext3 for the second partition. This is the procedure i have followed for installing qtopia on sdcard. My Host PC has FC 9. 1) connected to Neo freerunner by SSH 2) Partitioned SD card : fdisk /dev/mmcblk0 created a 8 mb partition for kernel and another one for the rootfs which took up all the remaining space Command (m for help): d Selected partition 1 Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-983, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (18-983, default 18): Using default value 18 Last cylinder or +size or +sizeM or +sizeK (18-983, default 983): Using default value 983 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy 3)Got an fdisk warning so umounted : umount /dev/mmcblk0p1 redone the step2 again.No error second time. 4)Formatted the SDcard : for first partition. a) mkfs.vfat /dev/mmcblk0p1 for second partition. b)mkfs.ext3 /dev/mmcblk0p2 5)Mounted the sdcard: mount /dev/mmcblk0p1 /media/card mkdir /media/card/boot mkdir /media/mmcblk0p2 mount /dev/mmcblk0p2 /media/mmcblk0p2 6)unpacked qtopia: got this two files : uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin qtopia-4.3.2-gta02-rootfs-07172049.jffs2 7)Mounted the rootfs on loopback device: export loop=$(losetup -f) losetup $loop rootfs.jffs2 modprobe block2mtd block2mtd=$loop,131072 modprobe jffs2 modprobe mtdblock mkdir mntpnt mount -t jffs2 -o ro /dev/mtdblock0 mntpnt 8)created compressed tarball. tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -c mntpnt 9)Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner: scp [EMAIL PROTECTED]:/media/mmcblk0p2/ 10)Unpack the rootfilesystem: cd /media/mmcblk0p2 tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz rm -f /media/mmcblk0p2/boot/* 11) Installed kernel. mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin scp uImage.bin [EMAIL PROTECTED]:/media/card/boot/ scp uImage.bin [EMAIL PROTECTED]:/media/card/ 12)shutdown and boot in qtopia. Booted from Sdcard Now when kernel is booting .It's giving kernel panic. Regards Syed Yaqoob Ali ___ support mailing [EMAIL PROTECTED]://lists.openmoko.org/mailman/listinfo/support As far as I know: whan you want to boot fat + ext3 you need to edit u-boot entry fat + ext2 works straight out of the box (after updating u-boot) ___ support mailing [EMAIL PROTECTED]://lists.openmoko.org/mailman/listinfo/support How do i edit the u-boot entry for booting fat + ext3 ? Can someone pls provide the procedure. Have you tried the procedure on this wiki page http://wiki.openmoko.org/wiki/Booting_from_SD#Add_uboot_boot_entry Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
