diff options
| author | Karsten Merker <merker@debian.org> | 2014-05-18 15:20:24 +0000 |
|---|---|---|
| committer | Karsten Merker <merker@debian.org> | 2014-05-18 15:20:24 +0000 |
| commit | a8f05ac5f9eb866cfad638aef324e424184e777b (patch) | |
| tree | a938455b37e4a74c759fe2fd74dd533c6f6d6c6d /en/preparing | |
| parent | 53dc8f7efc00de28ac1d02fd8b0e74856727529e (diff) | |
| download | installation-guide-a8f05ac5f9eb866cfad638aef324e424184e777b.zip | |
installation guide:
Add a "Kernel/Initrd/Device-Tree relocation issues in u-boot" subsection in the
"Pre-Installation Hardware and Operating System Setup" section.
Diffstat (limited to 'en/preparing')
| -rw-r--r-- | en/preparing/bios-setup/arm.xml | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/en/preparing/bios-setup/arm.xml b/en/preparing/bios-setup/arm.xml index c47e2323f..f639c7c1d 100644 --- a/en/preparing/bios-setup/arm.xml +++ b/en/preparing/bios-setup/arm.xml @@ -68,3 +68,32 @@ the command <quote>saveenv</quote> makes the assignment permanent. </para> </sect2> + + <sect2 arch="arm" id="uboot-relocation-issues"> + <title>Kernel/Initrd/Device-Tree relocation issues in u-boot</title> + <para> + On some systems with older u-boot versions there can be problems with + properly relocating the Linux kernel, the initial ramdisk and the + device-tree blob in memory during the boot process. In this case, + u-boot shows the message "Starting kernel ...", but the system freezes + afterwards without further output. These issues have been solved with + newer u-boot versions from v2014.07 onwards. + </para> + <para> + If the system has originally used a u-boot version older than + v2014.07 and has been upgraded to a newer version later, the problem + might still occur even after upgrading u-boot. Upgrading u-boot + usually does not modify the existing u-boot environment variables and + the fix requires an additional environment variable (bootm_size) to be + set, which u-boot does automatically only on fresh installations + without existing environment data. It is possible to manually set + bootm_size to the new u-boot's default value by running the command + "env default bootm_size; saveenv" at the u-boot prompt. + </para> + <para> + Another possibility to circumvent relocation-related problems is to + run the command "setenv fdt_high ffffffff; setenv initrd_high + 0xffffffff; saveenv" at the u-boot prompt to completely disable + the relocation of the initial ramdisk and the device-tree blob. + </para> + </sect2> |