http://bugzilla.opensuse.org/show_bug.cgi?id=1137061 Bug ID: 1137061 Summary: shim-install generates a EFI/opensuse/grub.cfg which does NOT mount btrfs subvolume /boot/grub2/x86_64-efi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: javispedro@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- To reproduce: In the grub2 x86-64 EFI boot prompt of a freshly installed TW, try to do "insmod linux" or any other GRUB module NOT builtin (note: 'linux', not 'linuxefi'; linuxefi is preloaded). Expected: Grub finds the module in $root/boot/grub2/x86_64-efi/linux.mod and loads it. Actual result: Grub complains about missing file, even when linux.mod /boot/grub2/x86_64-efi/linux.mod appears to exist! This also applies to modules listed in GRUB_PRELOAD_MODULES in /etc/defaults/grub and or modules loaded by /etc/grub.d/ scripts. The reason is that the btrfs subvolume /boot/grub2/x86_64-efi is NOT mounted by the time the Grub prompt appears and the scripts execute. This is because EFI/opensuse/grub.cfg in the EFI ESP (not /boot/grub2/grub.cfg) , which overrides Grub's builtin configuration file, does not force Grub to mount the /boot/grub2/x86_64-efi subvolume. Contents of EFI/opensuse/grub.cfg on my system: set btrfs_relative_path="yes" search --fs-uuid --set=root XXXX-XXXX-XXXX-XXXX set prefix=(${root})/boot/grub2 source "${prefix}/grub.cfg" Contents of Grub's builtin load.cfg (`strings /boot/grub2/x86_64-efi/grub.efi`): set btrfs_relative_path='y' btrfs-mount-subvol ($root) /boot/grub2/x86_64-efi @/boot/grub2/x86_64-efi The EFI/opensuse/grub.cfg file overrides load.cfg so the subvolume is never mounted. This EFI/opensuse/grub.cfg is generated on my system by script "shim-install", package 'shim'. Grep for 'make_grubcfg'. I can easily workaround this by forcing `btrfs-mount-subvol ($root) /boot/grub2/x86_64-efi @/boot/grub2/x86_64-efi` to be the first command that grub executesm even before 00_header. But the correct solution seems to be to fix shim-install. -- You are receiving this mail because: You are on the CC list for the bug.