Trouble booting kernel since 2012.12.1
Having some trouble booting Linux from recent versions of barebox, and need some pointers about where to look.
I'm working with custom hardware based on the i.MX53. It is roughly comparable to the i.MX53 LOCO board, and I started with that board support as a base for my own port. Up through barebox 2012.12.1 things were working well. However, with the 2013.01 and 2013.02 releases I can't get the kernel to boot successfully. It always hangs after displaying the arch number, but before posting the message "Booting Linux on physical CPU 0". All the lines displayed up to that point are identical. I have tried booting a kernel via TFTP and root FS via NFS. Also with the rootfs loaded as an initrd. The same barebox environment, kernel, and rootfs works in both modes when I'm running 2012.12.1 or 2012.11.
I see that a new environment has been introduced during this time, but did not do anything to move over to it. Could this be the source of my problem, or need I look elsewhere ?
George
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Quoted 14 lines · George Pontis
Having some trouble booting Linux from recent versions of barebox, and need some pointers about where to look.
I'm working with custom hardware based on the i.MX53. It is roughly comparable to the i.MX53 LOCO board, and I started with that board support as a base for my own port. Up through barebox 2012.12.1 things were working well. However, with the 2013.01 and 2013.02 releases I can't get the kernel to boot successfully. It always hangs after displaying the arch number, but before posting the message "Booting Linux on physical CPU 0". All the lines displayed up to that point are identical. I have tried booting a kernel via TFTP and root FS via NFS. Also with the rootfs loaded as an initrd. The same barebox environment, kernel, and rootfs works in both modes when I'm running 2012.12.1 or 2012.11.
Quoted 3 lines
I see that a new environment has been introduced during this time, but did not do anything to move over to it. Could this be the source of my problem, or need I look elsewhere ?
Try booting with bootm -v -v
Also you could enable earlyprintk support in the kernel and pass the 'earlyprintk' parameter on the kernel command line.
Sascha
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox