Hello
I'm trying to migrate an existing MPC8540 based system's 2.4 kernel to 2.6.15.1 kernel. I have made configuration changes accordingly and got the kernel image. Please find attached the .config file.
Also, made changes to rc.sysinit, fstab, halt etc to support sys file system and other 2.6 related changes. I have updated busybox binary image to busybox-1.6.0. Now when i use the rootfs.gz image along with kernel image and try to boot from memory using UBoot for the target system I get:
## Booting image at 00200000 ...
Image Name: Linux-2.6.15.1
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1298592 Bytes = 1.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00a00000 ...
Image Name: RAM disk
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 8628956 Bytes = 8.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 3f763000, end 3ff9dadc ... OK
and it just hangs there. When i try to use only kernel image i get the error:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
I'm new to this. Please help.
Thanks
| Attachment | Size |
|---|---|
| config_mod_new.txt | 27.46 KB |
are you sure about your
are you sure about your UBoot "bootargs".. what is your ram size 1GB?
The UBoot commands that I
The UBoot commands that I used are:
setenv ipaddr 192.168.**.**
setenv serverip 192.168.**.**
tftp 200000 vmlinux.UBoot
tftp a00000 rootfs.gz
bootm 200000 a00000
I have tried providing root=/dev/ram0 as arguments using make menuconfig and CONFIG_CMDLINE_BOOL option.
The system works fine with 2.4 kernel image which has a lot of ppc, asm and ide etc related patches. I haven't applied any patches for 2.6.15.1 kernel yet, since it supports MPC8540 and e500.
Please help.
Thanks
A Solution towards the loading of RAMDISK by Uboot
Hi Abhi,
Here I am sharing some information, hope it would help you. Because
I also have similar bitter experience while i was working with MPC8548 processer with e500 core and Uboot with 1.4 version.
As far as my knowledge the issue like "Unable to mount ramdisk image using UBoot while upgrading to 2.6.15 kernel for a MPC8540 based target" is not related to any linux kernel version.
Actually in this case it is not able to load the Ramdisk ...So
my suggestions are as follows:
1. Check the size of Ramdisk and the size of RAM.
2. Check the address where Uboot is loading the Ramdisk.
3. Check the Uboot environment variable "ramboot".
4. Set the ramboot properly by using setenv command.
I hope if you focus these points then issue will be resolved.
Good Luck...
JP
Unable to boot MPC8540 target while migrating to 2.6.15 kernel
Hello, I have made a 2.6.15 kernel image configured for MPC8540 using ARCH=ppc and while trying to boot using UBoot, it hangs at this point:
## Booting image at 00200000 ...
Image Name: Linux-2.6.15.1
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 850966 Bytes = 831 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
mpc8540ads_init(): exit Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
mpc8540ads_setup_arch()Dÿ
I have posted my config file earlier.
How should i proceed with this? Please help...
Thanks
check Console baudrate
Check your console baudrate, because right around that time the console_init() gets called to setup the console and if U-boot is not using the same baud rate then you will have problems. You can set it up on your bootargs in U-boot which baud rate to pass to the kernel.
U-boot bot from flash fails with 1GB of RAM
I have a similar to abhi (the boot hangs after loading the kernel and initrd image) when I use 1GB DIMM. Anything else works fine. I am using SPD config in U-boot which correctly identifies the memory size.
Nash:
Is there some known problem with 1GB configurations?
Thanks,
Marc