On Wed, Mar 26, 2014 at 09:48:18AM -0400, Stefan Monnier wrote: > > Since my Mele A2000 keeps locking up when using the 3.4 kernel (as > reported here several months ago), I decided I should try the sunxi-next > kernel (my machine can be headless, it just needs USB and SATA support, > basically). > > So I got the sunxi-next branch from Github's linux-sunxi. Then did > > make sunxi_defconfig > LOADADDR=0x40008000 make uImage dtbs > > (note: this was run under Debian "stable" armhf on my Mele A2000) > then copied the files to my SD card. > Then at U-Boot's prompt I did: > > ext2load mmc 0 0x46000000 uImage > ext2load mmc 0 0x49000000 sun4i-a10-a1000.dtb
Hmmm, it looks odd. These boards are exactly the same? > env set fdt_high ffffffff > bootm 0x46000000 - 0x49000000 > > Admittedly, there's no initramfs set, but I figured I'll see about that later. > Problem is, this doesn't give me much. I get: > > ## Booting kernel from Legacy Image at 46000000 ... > Image Name: Linux-3.14.0-rc5-00084-ge8176a3 > Created: 2014-03-26 12:57:21 UTC > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1784832 Bytes = 1.7 MiB > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 49000000 > Booting using the fdt blob at 0x49000000 > Loading Kernel Image ... OK > Using Device Tree in place at 49000000, end 49006bde > > Starting kernel ... > > and that's it: no more output after that. > I'm using the U-Boot that comes with the "Fedora 19 remix", and my > "uEnv.txt" says "console=ttyS0,115200". With the 3.4 kernel, I usually > get output starting with > > [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=10c5387d > > any idea what might be going on? Is there a problem with the build > itself so Linux doesn't even get to outputting this first line. Or is > it outputting it somewhere else? Or did I get unlucky with a transient > problem in sunxi-next? I can't find anything obviously wrong aside from the DT itself. Can you enable CONFIG_EARLY_PRINTK, add earlyprintk to your bootargs. It will allow to have a bit more precise idea on where it fails. -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
