[SOLVED] After installing Fedora, Windows won't boot

colorpurple21859 · 11-04-2020, 05:09 PM

@ mrmazda, attempting to create a menuentry to load fedora grub.cfg within ubuntu grub menu.

computersavvy · 11-04-2020, 05:14 PM

Quote:

Originally Posted by mrmazda

/boot/grub2/grub.cfg would be for a Fedora installation. In any Debian derivative (e.g. Ubuntu) there is only /boot/grub/grub.cfg.

That is true for a Fedora install using MBR. When using uefi on Fedora it is /boot/efi/EFI/fedora/grub.cfg

mrmazda · 11-04-2020, 05:17 PM

Quote:

Originally Posted by colorpurple21859

@ mrmazda, attempting to create a menuentry to load fedora grub.cfg within ubuntu grub menu.

Grub.cfg won't be found looking in a grub2 directory on a Ubuntu installation, just like grub.cfg won't be found looking in a grub directory on a Fedora installation.

colorpurple21859 · 11-04-2020, 05:26 PM

Quote:

When using uefi on Fedora it is /boot/efi/EFI/fedora/grub.cfg

I didn't know that fedora had moved it to the efi partition, that was going to be my next step.

mrmazda · 11-04-2020, 05:28 PM

Quote:

Originally Posted by computersavvy

When using uefi on Fedora it is /boot/efi/EFI/fedora/grub.cfg

Not on my UEFI Fedoras. On mine only *.efi and BOOTX64.CSV live there.

Code:

# inxi -S
System:    Host: asa88 Kernel: 5.10.0-0.rc1.20201028gited8780e3f2ec.57.fc34.x86_64 x86_64 bits: 64 Console: tty 2
           Distro: Fedora release 34 (Rawhide)
# ls -l /boot/efi/EFI/fedora/
total 6902
-rwx------ 1 root root     110 Oct  2  2018 BOOTX64.CSV
-rwx------ 1 root root 2271560 Dec  5  2019 grubx64.efi
-rwx------ 1 root root 1159560 Oct  2  2018 mmx64.efi
-rwx------ 1 root root 1210776 Oct  2  2018 shim.efi
-rwx------ 1 root root 1210776 Oct  2  2018 shimx64.efi
-rwx------ 1 root root 1204496 Oct  2  2018 shimx64-fedora.efi

colorpurple21859 · 11-04-2020, 05:30 PM

Quote:

Not on my UEFI Fedoras. On mine only *.efi and BOOTX64.CSV live there.

It must have been something that has changed recently, my installs of fedora are the same as yours.

computersavvy · 11-04-2020, 07:11 PM

Quote:

Originally Posted by mrmazda

Not on my UEFI Fedoras. On mine only *.efi and BOOTX64.CSV live there.

Code:

# inxi -S
System:    Host: asa88 Kernel: 5.10.0-0.rc1.20201028gited8780e3f2ec.57.fc34.x86_64 x86_64 bits: 64 Console: tty 2
           Distro: Fedora release 34 (Rawhide)
# ls -l /boot/efi/EFI/fedora/
total 6902
-rwx------ 1 root root     110 Oct  2  2018 BOOTX64.CSV
-rwx------ 1 root root 2271560 Dec  5  2019 grubx64.efi
-rwx------ 1 root root 1159560 Oct  2  2018 mmx64.efi
-rwx------ 1 root root 1210776 Oct  2  2018 shim.efi
-rwx------ 1 root root 1210776 Oct  2  2018 shimx64.efi
-rwx------ 1 root root 1204496 Oct  2  2018 shimx64-fedora.efi

You are running rawhide which is in development and does not always comply with the standard usage in the released versions.

[root@laptop lib]# inxi -S
System: Host: laptop.home.domain Kernel: 5.8.16-200.fc32.x86_64 x86_64 bits: 64 Desktop: GNOME 3.36.7
Distro: Fedora release 32 (Thirty Two)
[root@laptop lib]# ls -l /boot/efi/EFI/fedora/
total 15592
-rwx------. 1 root root 112 Oct 2 2018 BOOTIA32.CSV
-rwx------. 1 root root 110 Oct 2 2018 BOOTX64.CSV
drwx------. 2 root root 4096 Sep 23 15:38 fonts
-rwx------. 1 root root 1598728 Sep 15 08:05 gcdia32.efi
-rwx------. 1 root root 2528520 Sep 15 08:05 gcdx64.efi
-rwx------. 1 root root 6075 Dec 23 2019 grub.cfg
-rwx------. 1 root root 1024 Nov 4 15:36 grubenv
-rwx------. 1 root root 1598728 Sep 15 08:05 grubia32.efi
-rwx------. 1 root root 2528520 Sep 15 08:05 grubx64.efi
-rwx------. 1 root root 927824 Oct 2 2018 mmia32.efi
-rwx------. 1 root root 1159560 Oct 2 2018 mmx64.efi
-rwx------. 1 root root 1210776 Oct 2 2018 shim.efi
-rwx------. 1 root root 975536 Oct 2 2018 shimia32.efi
-rwx------. 1 root root 969264 Oct 2 2018 shimia32-fedora.efi
-rwx------. 1 root root 1210776 Oct 2 2018 shimx64.efi
-rwx------. 1 root root 1204496 Oct 2 2018 shimx64-fedora.efi

Some of those are left over from a couple upgrades, but that is where grub.cfg lives.

mrmazda · 11-04-2020, 09:52 PM

I'm running lots of Fedoras on lots of PCs. The one currently booted to Rawhide has 32 and 33 as well, where neither have grub.cfg in /boot/efi/EFI/fedora/.

Regardless, it's not necessary for OP to find Fedora's grub.cfg. OP wants Ubuntu to have priority, so Fedora need not have grub* installed. He only needs UEFI to give priority to Ubuntu's installation and as a result its Grub, while Ubuntu's os-prober ought to be able to find Fedora's kernels and initrds as long as lsmod shows the BTRFS kernel module is loaded when Ubuntu's grub-mkconfig (normally as update-grub on Ubuntu) is run.

colorpurple21859 · 11-05-2020, 07:16 PM

Quote:

while Ubuntu's os-prober ought to be able to find Fedora's kernels and initrds as long as lsmod shows the BTRFS kernel module is loaded when Ubuntu's grub-mkconfig (normally as update-grub on Ubuntu) is run.

That is the problem ubuntu's grub isn't picking up fedora's kernels off the boot partition. My ubuntu doesn't pick it up either, even if I mount fedora filesystem along with fedora boot partition, ubuntu grub still doesn't pick it up.

colorpurple21859 · 11-05-2020, 07:28 PM

I think I have a solution,
boot into fedora open a terminal

Code:

sudo nano /etc/default/grub

set this line to this if it is set to true or commented out.

Code:

GRUB_ENABLE_BLSCFG=false

Code:

sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

exit out boot into ubuntu, If you edited /etc/40_custom as per computersavvy in post 44, I think fedora grub menu will come up allowing you to boot fedora from ubuntu.

whois1230 · 11-06-2020, 03:26 PM

Quote:

Originally Posted by colorpurple21859

I think I have a solution,
boot into fedora open a terminal

Code:

sudo nano /etc/default/grub

set this line to this if it is set to true or commented out.

Code:

GRUB_ENABLE_BLSCFG=false

Code:

sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

exit out boot into ubuntu, If you edited /etc/40_custom as per computersavvy in post 44, I think fedora grub menu will come up allowing you to boot fedora from ubuntu.

It didn't work.

Code:

#!/bin/sh
exec tail -n +3 $0
# 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.
menuentry 'fedora config file'{
insmod btrfs
configfile (hd0,1)/EFI/fedora/grub.cfg
}

whois1230 · 11-06-2020, 03:29 PM

Quote:

Originally Posted by computersavvy

do "sudo ls /mnt/efi/fedora"
if it fails then you need to mount your efi partition at /mnt/efi with "sudo mount /dev/sda1 /mnt/efi"
then "sudo ls /mnt/efi/fedora" to verify you see the grub.cfg file there.

Then the previous code from post #39 would be changed as

Code:

#!/bin/sh
exec tail -n +3 $0
# 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.
menuentry 'fedora config file'{
insmod btrfs
configfile (hd0,1)/EFI/fedora/grub.cfg
}

Code:

user@Lenovo-ideapad-110-17IKB:~$  sudo nano /etc/grub.d/40_custom
[sudo] password for user: 
user@Lenovo-ideapad-110-17IKB:~$ sudo ls /mnt/efi/fedora
ls: cannot access '/mnt/efi/fedora': No such file or directory
user@Lenovo-ideapad-110-17IKB:~$ sudo mount /dev/sda1 /mnt/efi
mount: /mnt/efi: mount point does not exist.
user@Lenovo-ideapad-110-17IKB:~$ sudo ls /mnt/efi/fedora
ls: cannot access '/mnt/efi/fedora': No such file or directory
user@Lenovo-ideapad-110-17IKB:~$

colorpurple21859 · 11-06-2020, 06:25 PM

post the contents of fedora /etc/default/grub
post the contents of EFI/fedora/grub.cfg on the efi partition.
post the contents of ubuntu /etc/grub.d/40_custom

computersavvy · 11-06-2020, 07:10 PM

Quote:

Originally Posted by colorpurple21859

I didn't know that fedora had moved it to the efi partition, that was going to be my next step.

It has been at that location as long as I have been using UEFI with fedora. At least for the last 6 or more years.

mrmazda · 11-06-2020, 07:30 PM

Interesting finding such a difference between Fedora & openSUSE, since I've been using both for 14 years.