diff options
Diffstat (limited to 'en/preparing')
| -rw-r--r-- | en/preparing/bios-setup/arm.xml | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/en/preparing/bios-setup/arm.xml b/en/preparing/bios-setup/arm.xml index 57034e553..b35e479bb 100644 --- a/en/preparing/bios-setup/arm.xml +++ b/en/preparing/bios-setup/arm.xml @@ -29,12 +29,12 @@ </sect2> <sect2 arch="armhf" id="armhf-uboot-images"> - <title>Debian-provided u-boot (system firmware) images</title> + <title>Debian-provided U-Boot (system firmware) images</title> <para> - Debian provides u-boot images for various armhf systems that can load - their u-boot from an SD card at &armmp-uboot-img;. The u-boot builds - are offered in two formats: raw u-boot components and a ready-made - card image that can easily be written onto an SD card. The raw u-boot + Debian provides U-Boot images for various armhf systems that can load + their U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds + are offered in two formats: raw U-Boot components and a ready-made + card image that can easily be written onto an SD card. The raw U-Boot components are provided for advanced users; the generally recommended way is to use one of the ready-made SD card images. They are named <system-type>.sdcard.img.gz and can be written to a card e.g. @@ -46,14 +46,14 @@ card wipes all previous contents of the card! </para> <para> - If Debian provides a u-boot image for your system, it is recommended - that you use this image instead of the vendor-provided u-boot, as the + If Debian provides a U-Boot image for your system, it is recommended + that you use this image instead of the vendor-provided U-Boot, as the version in Debian is usually newer and has more features. </para> </sect2> <sect2 arch="arm" id="uboot-macsetting"> - <title>Setting the ethernet MAC address in u-boot</title> + <title>Setting the ethernet MAC address in U-Boot</title> <para> The MAC address of every ethernet interface should normally be globally unique, and it technically has to be unique within its @@ -84,9 +84,9 @@ administered address. </para> <para> - On systems using u-boot as system firmware, the ethernet MAC address + On systems using U-Boot as system firmware, the ethernet MAC address is placed in the <quote>ethaddr</quote> environment variable. - It can be checked at the u-boot command prompt with the command + It can be checked at the U-Boot command prompt with the command <quote>printenv ethaddr</quote> and can be set with the command <quote>setenv ethaddr ca:ff:ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</quote> makes the assignment permanent. @@ -94,31 +94,31 @@ </sect2> <sect2 arch="arm" id="uboot-relocation-issues"> - <title>Kernel/Initrd/Device-Tree relocation issues in u-boot</title> + <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 + 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 <quote>Starting kernel ...</quote>, + U-Boot shows the message <quote>Starting kernel ...</quote>, but the system freezes afterwards without further output. These issues have been solved with - newer u-boot versions from v2014.07 onwards. + newer U-Boot versions from v2014.07 onwards. </para> <para> - If the system has originally used a u-boot version older than + 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 + 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 + 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 - <quote>env default bootm_size; saveenv</quote> at the u-boot prompt. + bootm_size to the new U-Boot's default value by running the command + <quote>env default bootm_size; saveenv</quote> at the U-Boot prompt. </para> <para> Another possibility to circumvent relocation-related problems is to run the command <quote>setenv fdt_high ffffffff; setenv initrd_high - 0xffffffff; saveenv</quote> at the u-boot prompt to completely disable + 0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable the relocation of the initial ramdisk and the device-tree blob. </para> </sect2> |