From 9453bc812688278b2f937286ae788ac45b0468a8 Mon Sep 17 00:00:00 2001 From: Wookey Date: Fri, 17 Apr 2015 04:37:04 +0000 Subject: Add instructions for arm64 machines: Juno, Mustang. Restrict armel/armhf info to those manual arches Rewrite 'graphics card' section to 'graphics hardware' to cover arm and x86 --- en/boot-installer/arm.xml | 112 +++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 101 insertions(+), 11 deletions(-) (limited to 'en/boot-installer/arm.xml') diff --git a/en/boot-installer/arm.xml b/en/boot-installer/arm.xml index 1c0152ce9..c9369470c 100644 --- a/en/boot-installer/arm.xml +++ b/en/boot-installer/arm.xml @@ -1,7 +1,8 @@ - + + Boot image formats On ARM-based systems in most cases one of two formats for boot images @@ -13,7 +14,7 @@ uImage/uInitrd are image formats designed for the U-Boot firmware that - is used on many ARM-based systems. Older U-Boot versions can only + is used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions can only boot files in uImage/uInitrd format, so these are often used on older armel systems. Newer U-Boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, @@ -24,20 +25,22 @@ For systems using a multiplatform kernel, besides kernel and initial ramdisk a so-called device-tree file (or device-tree blob, dtb) is needed. It is specific to each supported system - and contains a description of the particular hardware. + and contains a description of the particular hardware. The dtb + should be supplied on the device by the firmware, but in practice a + newer one often needs to be loaded. Console configuration - The netboot tarball (), the - hd-media tarball () and the installer - SD-card images () use the - (platform-specific) default console that is defined by U-Boot in the - console variable. In most cases that is a serial - console, so on those platforms you by default need a serial console - cable to use the installer. + The netboot tarball (), and the installer + SD-card images () use + the (platform-specific) default console that is defined by + U-Boot in the console variable. In most cases + that is a serial console, so on those platforms you by default + need a serial console cable to use the installer. On platforms which also support a video console, you can modify the @@ -46,6 +49,86 @@ + + Console configuration + + The graphical installer is not enabled on the arm64 &d-i; images + for jessie so the serial console is used. The console device + should be detected automatically from the firmware, but if it not then after + you boot linux from the GRUB menu you will see a 'Booting Linux' + message then nothing more. + + + If you hit this issue you will need to set a specific console config on the kernel command line. + Hit e for 'Edit Kernel command-line' + at the GRUB menu, and change + --- quiet + to + console=<device>,<speed> + e.g. + console=ttyAMA0,115200n8 + When finished hit Control +x to continue booting with new setting. + + + + + Juno Installation + + Juno has UEFI so the install is straightforward. The most + practical method is installing from USB-stick. You need up to + date firmware for USB-booting to work. Builds from &url-juno-firmware; after March + 2015 tested OK. Consult Juno documentation on firmware updating. + + + Prepare a standard arm64 CD image on a USB-stick. Insert it in + one of the USB ports on the back. Plug a serial cable into the + upper 9-pin D on the back. If you need networking (netboot + image) plug the ethernet cable into the socket on the front of + the machine. + + + Run a serial console at 115200, 8bit no parity, and boot the + Juno. It should boot from the USB-stick to a GRUB menu. + The console config is not correctly detected on Juno so just hitting + return will show no kernel output. Set the console to +console=ttyAMA0,115200n8 + as described in (). Control +x to boot should show you the &d-i; screens, + and allow you to proceed with a standard installation. + + + + + Applied Micro Mustang Installation + + UEFI is available for this machine but it is normally shipped + with uboot so you will need to either install UEFI firmware + first then use standard boot/install methods, or use uboot boot + methods. Also USB is not supported in the jessie kernel so + installing from a USB-stick does not work. You must use a serial + console to control the installation because the graphical + installer is not enabled on the arm64 architecture. + + + The recommended install method is to copy the &d-i; kernel and + initrd onto the hard drive, using the openembedded system + supplied with the machine, then boot from that to run the + installer. Alternatively use TFTP to get the kernel/dtb/initrd + copied over and booted (). After + installation, manual changes to boot from the installed image + are needed. + + + Run a serial console at 115200, 8bit no parity, and boot the + machine. Reboot the machine and when you see "Hit any key to + stop autoboot:" hit a key to get a Mustang# prompt. Then use + uboot commands to load and boot the kernel, dtb and initrd. + + + + Booting by TFTP &boot-installer-intro-net.xml; @@ -180,7 +263,14 @@ source ${scriptaddr} - + + Booting from USB Memory Stick with UEFI + +&boot-installer-intro-usb.xml; + + + + Booting from a USB stick in U-Boot -- cgit v1.2.3