At the grub menu, I hit, c to get to a grub shell, and then use 'configfile' command pointed to /boot/loader.0/grub.cfg - it reads that configuration file instead of the one on /boot/efi/EFI/fedora/grub.cfg, and both 23.29 and 23.34 tree menu entries appear. Both contain an error, however. They both use 'linux16' and 'initrd16' instead of 'linuxefi' and 'initrdefi'. Something is very confused about whether this is a BIOS or UEFI system. If I change those commands to linuxefi and initrdefi, I can boot either tree. There is something... maybe. My fstab looks like this: UUID=908cb4df-410b-47e4-afb1-872255bd1244 /boot ext4 defaults 1 2 UUID=5956-63D8 /boot/efi vfat umask=0077,shortname=winnt,x-systemd.automount,noauto 0 2 UUID=8b0c4840-4fc7-4782-a4c0-25fec8a40dd4 / btrfs defaults 0 0 Normally grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg run manually causes /boot/efi to be mounted automatically in a split second. So, is rpm-ostree looking to see first if /boot/efi exists for any reason? What determines whether grub2-mkconfig -o is directed to /boot/efi/EFI/fedora, vs /boot/grub2? Thing is, there is no /boot/grub2/grub.cfg at all... neither of the correct locations got a grub.cfg. The correct grub.cfg (minus the wrong linux command) is in /boot/loader.0. Wonky. Chris Murphy _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
