Etesting

Grub_Manual.4ALL

发表于 | 分类于 |

Introduction

Grub is a kind of boot loader to load kernel into RAM and run it.

After rebooting board every time, the UEFI will firstly try to download the grub binary and run it firstly.

Then grub binary will load the kernel and start it with cmdline and dtb file according to the configurations in grub.cfg.

They include:

1
2
3
grubaa64.efi    # The grub binary executable program for ARM64 architecture
grubarm32.efi   # The grub binary executable program for ARM32 architecture
grub.cfg        # The grub config file which will be used by grub binary

Where to get them, please refer to Readme.txt.

Grub config file

You can edit a grub.cfg file to support various boot mode or multi boot partitions, follow is an example.

You should change them acoording to your real local environment.

Note: D05 only supports booting system via ACPI mode with Centos, Debian, Ubuntu.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
#
# Sample GRUB configuration file
#
# Boot automatically after 0 secs.
set timeout=5
# By default, boot the Euler/Linux
set default=d05_centos_nfs_acpi
# Booting from PXE with mini rootfs
menuentry "D05 minilinux PXE(ACPI)" --id d05_minilinux_pxe_acpi {
    set root=(tftp,192.168.1.107)
    linux /Image acpi=force pcie_aspm=off rootwait rdinit=/init crashkernel=256M@32M 
    initrd /mini-rootfs-arm64.cpio.gz
}
# Booting from Centos NFS
menuentry "D05 Centos NFS(ACPI)" --id d05_centos_nfs_acpi {
    set root=(tftp,192.168.1.107)
    linux /Image acpi=force pcie_aspm=off rdinit=/init rootwait crashkernel=256M@32M  root=/dev/nfs rw nfsroot=192.168.1.107:/home/<user>/tftp/rootfs_ubuntu64 ip=dhcp
}
# Booting from Centos SATA
menuentry "D05 Centos SATA(ACPI)" --id d05_centos_sata_acpi{
    search --no-floppy --fs-uuid --set=root <UUID>
    linux /Image acpi=force pcie_aspm=off rdinit=/init rootwait crashkernel=256M@32M root=PARTUUID=<PARTUUID> rootfstype=ext4 rw
}
# Booting from PXE with mini rootfs
menuentry "D03 minilinux PXE(ACPI)" --id d03_minilinux_pxe_acpi {
    set root=(tftp,192.168.1.107)
    linux /Image rdinit=/init pcie_aspm=off rootwait crashkernel=256M@32M rdinit=/init console=ttyS0,115200 earlycon=hisilpcuart,mmio,0xa01b0000,0,0x2f8  acpi=force
    initrd /mini-rootfs-arm64.cpio.gz
}
# Booting from Centos NFS
menuentry "D03 Ubuntu NFS(ACPI)" --id d03_ubuntu_nfs_acpi {
    set root=(tftp,192.168.1.107)
    linux /Image rdinit=/init pcie_aspm=off console=ttyS0,115200 earlycon=hisilpcuart,mmio,0xa01b0000,0,0x2f8 root=/dev/nfs rw nfsroot=192.168.1.107:/home/ftp/user/rootfs_ubuntu64 acpi=force ip=dhcp
}
# Booting from Centos SATA
menuentry "D03 Ubuntu SATA(ACPI)" --id d03_ubuntu_sata_acpi {
    search --no-floppy --fs-uuid --set=root <UUID>
    linux /Image acpi=force pcie_aspm=off rdinit=/init rootwait root=PARTUUID=<PARTUUID> rootfstype=ext4 rw console=ttyS0,115200 earlycon=hisilpcuart,mmio,0xa01b0000,0,0x2f8
}
# Booting from eMMC with mini rootfs
menuentry "HiKey minilinux eMMC" --id HiKey_minilinux_eMMC {
    linux /Image_HiKey rdinit=/init console=tty0 console=ttyAMA3,115200 rootwait rw loglevel=8 efi=noruntime
    initrd /mini-rootfs.cpio.gz
    devicetree /hi6220-hikey.dtb
}
# Booting from eMMC with Ubuntu
menuentry "HiKey Ubuntu eMMC" --id HiKey_Ubuntu_eMMC {
    linux /Image_HiKey rdinit=/init console=tty0 console=ttyAMA3,115200 root=/dev/mmcblk0p9 rootwait rw loglevel=8 efi=noruntime
    devicetree /hi6220-hikey.dtb
}
# Booting from SD card with Ubuntu
menuentry "HiKey Ubuntu SD card" --id HiKey_Ubuntu_SD {
    linux /Image_HiKey rdinit=/init console=tty0 console=ttyAMA3,115200 root=/dev/mmcblk1p1 rootwait rw loglevel=8 efi=noruntime
    devicetree /hi6220-hikey.dtb
}
menuentry 'HiKey Fastboot mode' {
    chainloader (hd0,gpt6)/fastboot.efi
}

Note: You should only select the parts from above sample which are suitable for your real situation.

files structure bootable partition

Normally they are placed into bootable partition as following structure.

1
2
3
4
5
6
7
sdx-------EFI
|       |
|       GRUB2------grubaa64.efi   # grub binary file only for ARM64 architecture
|
|-------------grub.cfg            # grub config file
|
|-------------Image               # kernel Image file only for D02 platform

Note: In case of booting by PXE mode:

  1. The grub binary and grub.cfg files must be placed in the TFTP root directory.
  2. The names and positions of kernel image and dtb must be consistent with the corresponding grub config file.
  3. The grub binary name (grubxxx.efi) must be consistent with the “filename” in /etc/dhcp/dhcpd.conf, for more detail, please refer to Setup_PXE_Env_on_Host.md
  4. If you use D02 board, you should not input DTB in the grub.cfg but you must flash the DTB file into spiflash to avoid a known Mac address duplicate issue.

You can get more information from the Deploy_Manual.md guide.

FAQ

If you want to modify grub.cfg command line temporarily. Type “E” key into grub modification menu. You will face problem that the “backspace” key not woking properly. You can fix backspace issue by changing terminal emulator’s configuration.

For gnome-terminal: Open “Edit” menu, select “Profile preferences”.
In “Compatibility” page, select “Control-H” in “Backspace key generates” listbox.
For Xterm: press Ctrl key and left botton of mouse, and toggle on “Backarrow key (BS/DEL)” in mainMenu.

热评文章