Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
1. Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
2. Cloned linux-linaro-2.6.37. Changed to source directory
3. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
4. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled EARLY_PRINTK)
5. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
6. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
7. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install INSTALL_MOD_PATH=/media/rootfs
8. cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
Regards, Avik
Hi Avik,
On 01/31/2011 11:57 AM, Avik Sil wrote:
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
I believe you're right. Is there a uInitrd file in your boot partition? At least, that's how things are in Ubuntu on ARM.... In this case, you also need some modules in the uInitrd file.
If you have such a file, you could manually update your uInitrd to include the modules for your kernel. You will find details on http://omappedia.org/wiki/Development_With_Ubuntu (that's how I was making experimental changes to Ubuntu's uInitrd files)
Another cleaner way could be to produce a new Debian package for your kernel, and run linaro-image-tools again, but that's a bit less straighforward.
I'm sure the other guys more familiar with the hardware packs will give you better advise.... I just shared what I know.
Cheers,
Michael.
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
I believe you're right.
Em, not necessarily... I used both hand-made and distribution-made Linaro kernels with Linaro filesystem but without initrd. And it did complain about modules indeed, but carried on.
How about adding "--debug" (yes, with two dashes) to your kernel command line to see what is the upstart actually doing?
Cheers!
Paweł
On Mon, Jan 31, 2011 at 11:57 AM, Avik Sil avik.sil@linaro.org wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
this one feels odd as beagle is omap3
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
yes, you also need to update uInitrd if you use the "default" linaro boot cmdline.
short intro is: 12:22 < asac> aviksil: cp /usr/bin/qem-arm-static /mnt/rootfs/usr/bin/ 12:22 < asac> aviksil: sudo chroot /mnt/rootfs 12:22 < asac> update-initramfs -kYOUR_KVERSION -c
On Mon, Jan 31, 2011 at 12:35 PM, Alexander Sack asac@linaro.org wrote:
On Mon, Jan 31, 2011 at 11:57 AM, Avik Sil avik.sil@linaro.org wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
this one feels odd as beagle is omap3
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
yes, you also need to update uInitrd if you use the "default" linaro boot cmdline.
short intro is: 12:22 < asac> aviksil: cp /usr/bin/qem-arm-static /mnt/rootfs/usr/bin/ 12:22 < asac> aviksil: sudo chroot /mnt/rootfs 12:22 < asac> update-initramfs -kYOUR_KVERSION -c
This will create something like /mnt/rootfs/boot/initrd.img-YOUR_VERSION.
With that you can use mkimage to create a uInitrd for your boot partition.
On Mon, Jan 31, 2011, Alexander Sack wrote:
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
this one feels odd as beagle is omap3
That's actually correct; omap2plus is meant to support OMAP2, OMAP3 and OMAP4 in the same binary kernel (OMAP2+)
On Mon, Jan 31, 2011 at 12:35:45PM +0100, Alexander Sack wrote:
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
yes, you also need to update uInitrd if you use the "default" linaro boot cmdline.
short intro is: 12:22 < asac> aviksil: cp /usr/bin/qem-arm-static /mnt/rootfs/usr/bin/ 12:22 < asac> aviksil: sudo chroot /mnt/rootfs 12:22 < asac> update-initramfs -kYOUR_KVERSION -c
Right. More precisely, the problem here is that you have an initrd configured but it's an initrd for the *wrong* kernel. You can either replace this initrd with one that matches the kernel, or you can fix the boot commandline to not look for an initrd. (The latter assumes you have all the drivers built in that are needed to get to the rootfs - which *should* be the case here.)
On Mon, Jan 31, 2011 at 10:57 AM, Avik Sil avik.sil@linaro.org wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
linaro-media-create makes an initramfs and installs it in the boot partition as "uInitrd". The default boot script is configured to load this and pass it to the kernel.
The initramfs appears to load and start up (I'm guessing the "Loading, please wait" comes from there), but the kernel may be missing some drivers needed to boot.
You might do better if you use the linaro kernel config:
Check out git://git.linaro.org/people/jcrigby/ubuntu/linux-linaro-natty.git master cat debian.linaro/config/config.common.ubuntu debian.linaro/config/armel/config.common.armel debian.linaro/config/armel/config.flavour.linaro-omap >.config yes '' | make oldconfig
This generally works for me -- the kernel seems to have adequate drivers built in that I don't need to update the initramfs.
Note that config selects a huge number of things to be built as modules, but you don't need to build them all just to get a bootable kernel. You just do "make uImage" initially.
- make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Presumably you mean "umount", not "sync"? ;)
Cheers ---Dave
On Mon, Jan 31, 2011 at 4:57 AM, Avik Sil avik.sil@linaro.org wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
Actually omap2plus_defconfig will only get you to a 99% bootable config for the beagle..
You still need to manually select CONFIG_GPIO_TWL4030 (which controls board specific things suchas power on mmc, power on ehci, etc..)
Discussion, Reasoning, etc here... http://www.spinics.net/lists/linux-omap/msg44076.html
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
Regards, Avik
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hi Avik,
Would you be willing to try the instructions I created for this at:
https://wiki.linaro.org/Mentoring/KernelDeploy
Especially the section labeled:
#Deploying the kernel to the SD card
These instructions worked on my Overo board.
--Matt
On 01/31/2011 03:57 AM, Avik Sil wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
Regards, Avik
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
After trying all the suggestions finally I had to resort to linaro kernel packaging (https://wiki.linaro.org/PackageYourOwnKernel) to deploy the kernel which gave me the maximum sane output, but still failed to get the shell: http://paste.ubuntu.com/560935/
I tried disabling UUID validation as given in https://wiki.linaro.org/Mentoring/KernelDeploy, but that too did not help.
Regards, Avik
On 31 January 2011 23:56, Matt Waddel matt.waddel@canonical.com wrote:
Hi Avik,
Would you be willing to try the instructions I created for this at:
https://wiki.linaro.org/Mentoring/KernelDeploy
Especially the section labeled:
#Deploying the kernel to the SD card
These instructions worked on my Overo board.
--Matt
On 01/31/2011 03:57 AM, Avik Sil wrote:
Hi,
I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I
executed
following:
- Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with
hwpack daily snapshot
hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz
and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly
on
my BB.
Cloned linux-linaro-2.6.37. Changed to source directory
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled
EARLY_PRINTK)
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
INSTALL_MOD_PATH=/media/rootfs
- cp arch/arm/boot/uImage /media/boot; sync
Everything went on smoothly. Then I put the SD card on BB and powered it
on.
I got a kernel panic: http://paste.ubuntu.com/560562
Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM?
Regards, Avik
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Tue, Feb 1, 2011 at 8:11 AM, Avik Sil avik.sil@linaro.org wrote:
After trying all the suggestions finally I had to resort to linaro kernel packaging (https://wiki.linaro.org/PackageYourOwnKernel) to deploy the kernel which gave me the maximum sane output, but still failed to get the shell: http://paste.ubuntu.com/560935/
I tried disabling UUID validation as given in https://wiki.linaro.org/Mentoring/KernelDeploy, but that too did not help.
you might still have the reference to that uuid in /etc/fstab that it's tripping over..
Regards,
On 02/01/2011 03:50 PM, Robert Nelson wrote:
On Tue, Feb 1, 2011 at 8:11 AM, Avik Sil avik.sil@linaro.org wrote:
After trying all the suggestions finally I had to resort to linaro kernel packaging (https://wiki.linaro.org/PackageYourOwnKernel) to deploy the kernel which gave me the maximum sane output, but still failed to get the shell: http://paste.ubuntu.com/560935/
I tried disabling UUID validation as given in https://wiki.linaro.org/Mentoring/KernelDeploy, but that too did not help.
you might still have the reference to that uuid in /etc/fstab that it's tripping over..
Mmm, the log suggests that you are still using an initrd (initramfs indeed).
Another possibility is a bootcmd setting in U-boot that says "root=UUID=xxxxxxx".
Before running "run bootcmd", you may display the value of 'bootcmd' and replace the 'root=UUID=xxxxxxx" setting by "root=/dev/mmcblk0p2".
Ubuntu's initramfs scripts use /proc/cmdline to find out which root filesystem to mount. This should fix your problem.
Crossing my fingers...
Cheers,
Michael.
On Tue, Feb 01, 2011 at 09:23:38PM +0100, Michael Opdenacker wrote:
On 02/01/2011 03:50 PM, Robert Nelson wrote:
On Tue, Feb 1, 2011 at 8:11 AM, Avik Sil avik.sil@linaro.org wrote:
After trying all the suggestions finally I had to resort to linaro kernel packaging (https://wiki.linaro.org/PackageYourOwnKernel) to deploy the kernel which gave me the maximum sane output, but still failed to get the shell: http://paste.ubuntu.com/560935/
I tried disabling UUID validation as given in https://wiki.linaro.org/Mentoring/KernelDeploy, but that too did not help.
you might still have the reference to that uuid in /etc/fstab that it's tripping over..
Mmm, the log suggests that you are still using an initrd (initramfs indeed).
Another possibility is a bootcmd setting in U-boot that says "root=UUID=xxxxxxx".
Before running "run bootcmd", you may display the value of 'bootcmd' and replace the 'root=UUID=xxxxxxx" setting by "root=/dev/mmcblk0p2".
Ubuntu's initramfs scripts use /proc/cmdline to find out which root filesystem to mount. This should fix your problem.
I've poked around at this with Avik; the problem seems to be that the omap2plus_defconfig doesn't enable the driver for the MMC interface by default.
Note that this root=UUID= line is set by linaro-media-create using the UUID of the newly-created root filesystem; it would be quite unusual for the fs UUID to change. All the same, we've ruled this out now.
hey i am also trying to boot linaro on Hackberry board. as i want linaro source code for my project, how can i get it? git clone git://git.linaro.org/kernel/linux-linaro-3.1.git is this link downloads linaro source code?
-
Alexander Sack -
Avik Sil -
Dave Martin -
Loïc Minier -
Matt Waddel -
Michael Opdenacker -
Pawel Moll -
Robert Nelson -
Steve Langasek -
swat