Installed uImage has wrong load addr

which package?

I've tested 1602 and 1605 kernel with load/entry addr 0x8000 and 0x2000000 (mkimage manually) and all kernels with load/entry addr 0x8000 boot successfully, 0x2000000 do not.

The uImage on ports.u.c with load/entry addr 0x8000 as well.

Then I do more research. login to z2 which looks like the filesystem is precise, and the load/entry addr of /boot/uImage is 0x2000000, though in flash-kernel:dove_flash_kernel, the uImage is generated with "-a 0x00008000 -e 0x00008000"

My point of view is that the kernel load addr in /usr/share/flash-kernel/db/all.db for armadaxp shall be move to 0x8000

@Jani,

For armadaxp on Quantal. Sorry, forget to mention that.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1026835

I erred when porting armadaxp support in Precise forward to the flash-kernel sync in Debian. I conflated the kernel load address embedded into the uImage with the address that the uImage is initially loaded to. The attached branch fixes the problem and makes load addresses consistent with what we used in Precise and our installation instructions.

Note that users should load uImage into 0x2000000 and uInitrd into 0x1100000, not 0x8000. The embedded 0x8000 inside the uImage will be used by U-Boot after the uImage itself is loaded.

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu15

---------------
flash-kernel (3.0~rc.4ubuntu15) quantal; urgency=low

  * Fix armadaxp kernel load address (LP: #1026835).
 -- Robie Basak <email address hidden> Tue, 31 Jul 2012 16:31:30 +0100