The graphical installer is (experimentally) enabled on the arm64 debian-installer images, but on some devices you may still have to use the serial console. The console device should be detected automatically from the firmware, but if it is 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 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 http://releases.linaro.org/members/arm/platforms/latest/ after March 2015 tested OK. Consult Juno documentation on firmware updating.

Prepare a standard arm64 CD/DVD 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 serial port 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 Enter will show no kernel output. Set the console to

console=ttyAMA0,115200n8

(as described in Phần 5.1.1, “Console configuration”). Control+x to boot should show you the debian-installer screens, and allow you to proceed with a standard installation.

UEFI is available for this machine but it is normally shipped with U-Boot so you will need to either install UEFI firmware first then use standard boot/install methods, or use U-Boot boot methods. 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 debian-installer 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 (Phần 5.1.4.1, “TFTP-booting in U-Boot”). 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 U-Boot commands to load and boot the kernel, dtb and initrd.

Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration).

The server-side setup to support network booting is described in Phần 4.4, “Chuẩn bị tập tin để khởi động qua mạng TFTP”.

setenv autoload no
dhcp

setenv ipaddr <ip address of the client>
setenv netmask <netmask>
setenv serverip <ip address of the tftp server>
setenv dnsip <ip address of the nameserver>
setenv gatewayip <ip address of the default gateway>

saveenv

printenv kernel_addr_r ramdisk_addr_r fdt_addr_r

setenv kernel_addr_r 0x46000000
setenv fdt_addr_r 0x47000000
setenv ramdisk_addr_r 0x48000000

tftpboot ${kernel_addr_r} <filename of the kernel image>
tftpboot ${fdt_addr_r} <filename of the dtb>
tftpboot ${ramdisk_addr_r} <filename of the initial ramdisk image>

setenv bootargs console=ttyS0,115200 rootwait panic=10

bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}

If your computer will boot from USB, this will probably be the easiest route for installation. Assuming you have prepared everything from Phần 3.6.1, “Chọn thiết bị khởi động” and Phần 4.3, “Chuẩn bị tập tin để khởi động thanh bộ nhớ USB”, just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with a graphical boot menu (on hardware that supports it). Here you can select various installer options, or just hit Enter.

The graphical version of the installer is only available for a limited number of architectures, including 64-bit ARM. The functionality of the graphical installer is essentially the same as that of the text-based installer as it basically uses the same programs, but with a different frontend.

Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the text-based “newt” frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen.

Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer.

Ghi chú

The graphical installer requires significantly more memory to run than the text-based installer: 640MB. If insufficient memory is available, it will automatically fall back to the text-based “newt” frontend. If the amount of memory in your system is below 260MB, the graphical installer may fail to boot at all while booting the text-based installer would still work. Using the text-based installer is recommended for systems with little available memory.