diff options
| -rw-r--r-- | de/boot-installer/arm.xml | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/de/boot-installer/arm.xml b/de/boot-installer/arm.xml index b59cd6710..60d49ae9c 100644 --- a/de/boot-installer/arm.xml +++ b/de/boot-installer/arm.xml @@ -238,8 +238,42 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} ${fdt_addr_r}-Parameter einfach weg. </para> </sect3> + + <sect3 arch="armhf" id="boot-armhf-netboot.tar.gz"> + <title>Pre-built netboot tarball</title> + <para> + &debian; provides a pre-built tarball (&armmp-netboot-tarball;) + that can simply be unpacked on your tftp server and contains + all files necessary for netbooting. It also includes a boot + script that automates all steps to load the installer. Modern + U-Boot versions contain a tftp autoboot feature that becomes + active if there is no bootable local storage device (MMC/SD, + USB, IDE/SATA/SCSI) and then loads this boot script from the + tftp server. Prerequisite for using this feature is that you + have a dhcp server in your network which provides the client + with the address of the tftp server. + </para> + <para> + If you would like to trigger the tftp autoboot feature from the + U-Boot commandline, you can use the follwing command: + <informalexample><screen>run bootcmd_dhcp</screen></informalexample> + </para> + <para> + To manually load the bootscript provided by the tarball, you can + alternatively issue the following commands at the U-Boot prompt: + +<informalexample><screen> +setenv autoload no +dhcp +tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr +source ${scriptaddr} +</screen></informalexample> + + </para> + </sect3> </sect2> + <sect2 arch="arm64" condition="bootable-usb" id="usb-boot"> <title>Booten von USB-Stick mit UEFI</title> |