When I tried to run a QEMU virtual machine for fedora-17 using kernel-3.3.0-0.rc4.git3.1.fc17.armv5tel, the kernel displayed the message:
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.3.0-0.rc4.git3.1.fc17.armv5tel (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.7.0 20120206 (Red Hat 4.7.0-0.11) (GCC) ) #1 Thu Feb 23 13:10:33 EST 2012
[ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: ARM-Versatile PB
[ 0.000000] INITRD: 0x00d00000+0x00a89878 overlaps in-use memory region - disabling initrd
...and the system failed to boot.
I am currently running Fedora-17 with the Fedora-15 kernel, but I want to try compiling the kernel from http://fedora.c3sl.ufpr.br/linux/development/17/source/SRPMS/k/kernel-3.3.0-1.fc17.src.rpm as a binary RPM for both QEMU and a development board I have.
So, what went wrong in the generation of kernel-3.3.0-0.rc4.git3.1.fc17.armv5tel ? I want to avoid making the same mistake and ending up with an unbootable kernel. Is it enough to have this updated source RPM?
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
