Enabling CSM fails, can somebody recommend a bootloader
Hi, I am currently building a new PC. Migrating the drives from an Intel Celeron with integrated GPU, mobo Gigabyte GA-B85M-D3H to an Intel Core i3 13th Gen, mobo Gigabyte B760M DS3H DDR4 does cause some issues. The PC is a Linux multi-boot machine. The old SATA SSDs are all MBR drives, a new NVMe SSD is a GPT drive. The old PC's bootloader is syslinux. The Arch install's root directory holds all kernels, the Arch kernels, but also the kernels from the other Linux installs (an ancient Suse, Ubuntu etc.). Disabling Intel platform trust technology and secure boot works, but enabling CSM (legacy boot) fails. I read that on modern Intel machines CSM cannot be enabled, when using the internal GPU. I wonder if this is correct?! I also read, if I need to stay with EFI boot, that continuing using syslinux for a multi-boot Linux machine without chainloading, by keeping all kernels in one partition, could become a PITA or even impossible. Does anybody know, if it's possible to enable CSM? Maybe I forgot to disable or enable something else, before enabling CSM can work. As a temporarily workaround, to continue building the new PC, I installed Xubuntu, from a pendrive that was at hand. It installed GRUB2, so I can boot Arch Linux from the old MBR drive. If I should need to stay with CSM disabled and if syslinux should not work to boot all Linux installs, is there another alternative bootloader available that is similar to syslinux? If possible I will not stay with GRUB2. FWIW aur/r8125-dkms (chaotic-aur/r8125-dkms) works without issues [1]. Thank you aravance! Regards, Ralf [1] https://aur.archlinux.org/packages/r8125-dkms
Hi,
I am currently building a new PC. Migrating the drives from an Intel Celeron with integrated GPU, mobo Gigabyte GA-B85M-D3H to an Intel Core i3 13th Gen, mobo Gigabyte B760M DS3H DDR4 does cause some issues.
what about systemd-boot? Regards Bjoern
On Mon, 2023-03-27 at 10:53 +0200, Bjoern Franke wrote:
what about systemd-boot?
Hi, IIUC systemd-boot needs EFISTUB, IOW I would need to drop my old operating system museum, a vintage Suse 11.2 with a 2.6 kernel for example has got no EFISTUB. Assuming I would do without the museum, then the modern kernels would have to be in the ESP, a FAT partition without file permissions. Or do I misunderstand something? Regards, Ralf [1] [rocketmouse@archlinux ~]$ grep "LINUX /.boot/suse" /boot/syslinux/syslinux.cfg LINUX /.boot/suse11.2/boot/vmlinuz-2.6.31.6-rt19 [rocketmouse@archlinux ~]$ grep EFI_STUB /.boot/suse11.2/boot/config-2.6.31.6-rt19 || echo $? 1
On 4/2/23 04:04, Ralf Mardorf wrote:
Assuming I would do without the museum, then the modern kernels would have to be in the ESP, a FAT partition without file permissions. Or do I misunderstand something?
Ralf Here's a brief overview. There are 2 methods available for UEFI booting (see spec [1] for more details). Both require : - <esp> partition with GPT Type EF00 and VFAT filesystem - Method 1. <esp> typically mounted on "/boot" and Kernels and initrd bot reside in this partition along with loader and loader information. - Method 2. <esp> typically mounted as /efi and a separate Extended Boot Loader Partition (XBOOTLDR) which has GPT Type EA00 is used to hold kernels and initrds. This can be any filesystem for which efi drivers are available (see efifs package). These include ext4, btrfs etc. The XBOOTLDR partition is mounted on "/boot". With systemd-boot, which is clean, simple and very robust, one simply copies the efi drivers to /efi/EFI/systemd/drivers. Hope this makes it more clear. [1] XBOOTLDR https://uapi-group.org/specifications/specs/discoverable_partitions_specific...
On 4/2/23 07:44, Genes Lists wrote:
[1] XBOOTLDR https://uapi-group.org/specifications/specs/discoverable_partitions_specific...
Oops, Forgot to provide this link as well: https://uapi-group.org/specifications/specs/boot_loader_specification/
Does this method 2 mean making 3 partitions?
On Sun, Apr 2, 2023, 7:13 AM Genes Lists
On 4/2/23 07:44, Genes Lists wrote:
[1] XBOOTLDR
https://uapi-group.org/specifications/specs/discoverable_partitions_specific...
Oops, Forgot to provide this link as well:
https://uapi-group.org/specifications/specs/boot_loader_specification/
On 4/2/23 12:07, Matthew Blankenbeheler wrote:
Does this method 2 mean making 3 partitions?
The UEFI spec requires that the Extended Boot Loader be its own partition of type XBOOTLDR (gpt EA00) - so yes thats correct. 1 partition for <esp> (/efi), 1 for extended boot loader (/boot) and whatever else you need for root, home, data etc. in this setup the (strong) recommendation is to mount esp as /efi and NOT as /boot/efi. hope that helps. gene
On Sun, 2023-04-02 at 07:44 -0400, Genes Lists wrote:
Here's a brief overview.
Thank you! I just noticed that I've got already issues with not that old kernels. At the moment I'm using GRUB. $ pacman -Q linux linux-rt linux-lts linux-rt-lts linux 6.2.9.arch1-1 linux-rt 6.2.0.3.realtime1-3 linux-lts 6.1.22-1 linux-rt-lts 5.15.96.61.realtime1-2 I can boot the kernels version 6+, but not the 5.15-rt or my 4.19-rt. Running "journalctl -b -..." provides some hints, but for the moment I don't care. Booting an Ubuntu kernel 5.4.0 works. Regards, Ralf
On Mon, 2023-03-27 at 10:40 +0200, Ralf Mardorf wrote:
I read that on modern Intel machines CSM cannot be enabled, when using the internal GPU. I wonder if this is correct?!
Gigabyte support confirmed it. This is correct. The answer to my CSM (legacy boot) related request translated from German to English (US) by https://www.deepl.com/de/translator : "Dear Gigabyte customer thank you for contacting us. We will be happy to review your request and look for a solution for you. The GPU of the CPU is not able to do Legacy Mode anymore, this would require a PCIe VGA. The OS Linux is not supported by us, also we do not offer drivers. Your GIGABYTE Team"
participants (4)
-
Bjoern Franke
-
Genes Lists
-
Matthew Blankenbeheler
-
Ralf Mardorf