Tim*_*Tim 0 ubuntu boot-loader uefi
这台装有 Lubuntu 18.04 的笔记本电脑是否安装了引导加载程序并使用它?如果不是,它用什么代替?它的启动过程是怎样的?
笔记本电脑是否使用 UEFI 而不是 BIOS?UEFI 除了替代 BIOS 之外,是引导加载程序吗?
我按照https://unix.stackexchange.com/a/137587/674查找引导加载程序。
谢谢。
$ sudo parted -l
[sudo] password for t:
Model: ATA TOSHIBA MQ01ABF0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 EFI System Partition boot, esp
2 538MB 500GB 500GB ext4
$ sudo dd if=/dev/sda bs=512 count=1 2>&1 | grep GRUB
$ sudo dd if=/dev/sda bs=512 count=1 2>&1 | grep LILO
$ sudo ./bootinfoscript --stdout
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/BOOT/fbx64.efi /efi/ubuntu/fwupx64.efi
/efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi
/efi/ubuntu/shimx64.efi
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 18.04.2 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 976,773,167 976,773,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 1,050,623 1,048,576 EFI System partition
/dev/sda2 1,050,624 976,771,071 975,720,448 Data partition (Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 0C1E-EE69 vfat
/dev/sda2 7a7ed7ca-d939-49d6-8951-ba573929f41f ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda1 /boot/efi vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda2 / ext4 (rw,relatime,errors=remount-ro,data=ordered)
=========================== sda2/boot/grub/grub.cfg: ===========================
--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=1
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
linux /boot/vmlinuz-4.15.0-45-generic root=UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f ro quiet splash $vt_handoff
initrd /boot/initrd.img-4.15.0-45-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
menuentry 'Ubuntu, with Linux 4.15.0-45-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-45-generic-advanced-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
echo 'Loading Linux 4.15.0-45-generic ...'
linux /boot/vmlinuz-4.15.0-45-generic root=UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.15.0-45-generic
}
menuentry 'Ubuntu, with Linux 4.15.0-45-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-45-generic-recovery-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
echo 'Loading Linux 4.15.0-45-generic ...'
linux /boot/vmlinuz-4.15.0-45-generic root=UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.15.0-45-generic
}
menuentry 'Ubuntu, with Linux 4.15.0-20-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-20-generic-advanced-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
echo 'Loading Linux 4.15.0-20-generic ...'
linux /boot/vmlinuz-4.15.0-20-generic root=UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.15.0-20-generic
}
menuentry 'Ubuntu, with Linux 4.15.0-20-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-20-generic-recovery-7a7ed7ca-d939-49d6-8951-ba573929f41f' {
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7a7ed7ca-d939-49d6-8951-ba573929f41f
else
search --no-floppy --fs-uuid --set=root 7a7ed7ca-d939-49d6-8951-ba573929f41f
fi
echo 'Loading Linux 4.15.0-20-generic ...'
linux /boot/vmlinuz-4.15.0-20-generic root=UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.15.0-20-generic
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------
=============================== sda2/etc/fstab: ================================
--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=7a7ed7ca-d939-49d6-8951-ba573929f41f / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=0C1E-EE69 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
--------------------------------------------------------------------------------
=================== sda2: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-7fBr4xK8/Tmp_Log: No such file or directory
Run Code Online (Sandbox Code Playgroud)
是的,那台笔记本电脑安装了 UEFI 版本的 GRUB 引导加载程序 - 您可以看到该/efi/ubuntu/grubx64.efi
文件。但是没有安装MBR 风格的引导加载程序,如输出所示
=> No boot loader is installed in the MBR of /dev/sda
Run Code Online (Sandbox Code Playgroud)
不,从技术上讲,UEFI 不是引导加载程序。
UEFI 是一种系统固件,它取代了现代 PC 上的 BIOS。引导加载程序可以定义为“相对简单的东西(与实际的操作系统相比),它利用系统固件提供的服务来加载实际的操作系统。”
系统固件最初控制系统,因此它将决定引导加载程序应该是什么样的。传统的 PC BIOS 基本上会:
在现代系统上,446 字节几乎不足以覆盖可能的磁盘访问接口(旧 C/H/S 和现代 LBA),然后加载引导加载程序的其余部分,这些引导加载程序通常嵌入主引导之间的空间记录和第一个分区的开始。
另一方面,UEFI 将:
如果您使用该sudo efibootmgr -v
命令,您将看到系统固件和引导加载程序之间的链接:UEFI 引导顺序设置。它们存储在系统的电池供电 NVRAM 内存中(= 基本上与 BIOS 设置存储在具有 BIOS 而不是 UEFI 的系统上的位置相同),并为每个配置的引导加载程序指定四件事:
在您的情况下,在 UEFI 引导顺序中注册的引导加载程序实际上可能不是/efi/ubuntu/grubx64.efi
,而是/efi/ubuntu/shimx64.efi
:UEFI 安全引导垫片引导加载程序。它由 Microsoft 签名,因此应该可以在基本上所有支持 UEFI 安全启动的 64 位 x86 系统上加载。它具有 Canonical 的安全启动证书的内置副本,并且它使用该证书(或可选地安装到系统 NVRAM 中作为机器所有者密钥或 MOK 的任何其他证书)以加密方式验证它加载的下一个文件,按照惯例,grubx64.efi
文件位于同一目录shimx64.efi
中。
如果您的系统没有启用安全启动,则可以跳过此步骤,并且\efi\ubuntu\grubx64.efi
可以直接在 UEFI 启动顺序设置中指定。
对于可移动媒体和引导加载程序可能未在 NVRAM 设置中注册的其他情况,UEFI 还包括回退引导加载程序路径。对于 64 位 x86 架构,它是\efi\boot\bootx64.efi
. 如果此文件存在于可移动媒体上的 FAT32 分区中,则该媒体可有效引导UEFI。
在系统固件中嵌入 UEFI 兼容的引导加载程序在技术上是可能的(实际上很容易)。但这使得更新引导加载程序变得困难,这通常是特定于特定操作系统或操作系统系列的。因此,您通常更有可能在设备而非通用计算机中看到此类嵌入式引导加载程序。