diff options
author | Luca Monducci <luca.mo@tiscali.it> | 2015-01-27 21:24:55 +0000 |
---|---|---|
committer | Luca Monducci <luca.mo@tiscali.it> | 2015-01-27 21:24:55 +0000 |
commit | c63f968e19a37830f6436f620f1c3f5029da67bf (patch) | |
tree | 91f3633bc54ef75fc4810daa28e52640b3f06f45 /it/preparing/bios-setup | |
parent | eda682c9258ceee2d8f873f8f59dd8b36bf1c3af (diff) | |
download | installation-guide-c63f968e19a37830f6436f620f1c3f5029da67bf.zip |
Update italian d-i manual
Diffstat (limited to 'it/preparing/bios-setup')
-rw-r--r-- | it/preparing/bios-setup/arm.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/it/preparing/bios-setup/arm.xml b/it/preparing/bios-setup/arm.xml index 92eece206..2a13792f0 100644 --- a/it/preparing/bios-setup/arm.xml +++ b/it/preparing/bios-setup/arm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 69182 --> +<!-- original version: 69220 --> <sect2 arch="arm" id="arm-firmware-overview"> <!-- <title>ARM firmware</title> --> @@ -109,7 +109,7 @@ To avoid conflicts with existing officially-assigned MAC addresses, there is an address pool which is reserved for so-called <quote>locally administered</quote> addresses. It is defined by the value of two specific bits in the first byte of the address (the -article "MAC address" in the English language Wikipedia gives a +article <quote>MAC address</quote> in the English language Wikipedia gives a good explanation). In practice this means that e.g. any address starting with hexadecimal ca (such as ca:ff:ee:12:34:56) can be used as a locally administered address. @@ -156,7 +156,8 @@ permanente la modifica. 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 +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. --> @@ -180,7 +181,7 @@ 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. +<quote>env default bootm_size; saveenv</quote> at the u-boot prompt. --> Questo problema potrebbe comunque verificarsi anche se il sistema era @@ -198,8 +199,8 @@ promnpt di u-boot. <!-- 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 +run the command <quote>setenv fdt_high ffffffff; setenv initrd_high +0xffffffff; saveenv</quote> at the u-boot prompt to completely disable the relocation of the initial ramdisk and the device-tree blob. --> |