I used manual partition via the GUI in the installation setup. I have previously freed about 750GB in Windows and then splitted it. Encrypted is only the main partition, so swap and boot should not be affected.
lsblk -o +UUID:
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part /boot/efi 1E19-[REDACTED]
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 171.9G 0 part DCD64FD0[REDACTED]
├─nvme0n1p4 259:4 0 506M 0 part 0CAE1592AE[REDACTED]
├─nvme0n1p5 259:5 0 20G 0 part /boot 6c38d4ba-c[REDACTED]
├─nvme0n1p6 259:6 0 750G 0 part 28b8e50c-[REDACTED
│ └─luks-28b8e50c-[REDACTED] 253:0 0 750G 0 crypt / 6c29f5b8-3967-[REDACTED]
└─nvme0n1p7 259:7 0 11.3G 0 part [SWAP] 40cb92bc-[REDACTED]
nvme0n1p3 is the normal windows partition, 2 and 4 are recovery and boot partitions from windows afair.
p1, p3 and p4 do not have UUIDs, if that’s for any relevance.
No, I don’t see any boot menu. First I see is the input field for luks
In this case LUKS shouldn’t affect it from my experience, as system accesses LUKS after grub plays its part.
20G is way to big for /boot (1G should be enough, 2 is plenty) – but that’s not the problem here.
efibootmgr output seems ok too, although Boot0003 and 0004 are sort of doubled up.
I’m out of ideas at this point, two more wild guesses (with low chances of success).
Please run sudo grub2-editenv create and reboot.
In your UEFI boot menu (accessed though BIOS/UEFI settings, or [F8] on ASUS motherboards, or some other hotkey on other ones) you should see two entries named Fedora (corresponding to Boot0003 and Boot0004 from output above). Can you please manually boot each of these to see if by chance it’ll make any difference? It shouldn’t but still… )
Also can you please paste contents of your /boot/efi/EFI/fedora/grub.cfg file either here or on https://paste.fedoraproject.org/? It doesn’t contain any sensitive data. I don’t think UUIDs are sensitive – they are in this file.
BIOS (UEFI) generally has a key you can press to choose which EFI file you want to boot (which OS), I know Solus OS (another distro) doesn’t use GRUB and relies on this method entirely for EFI installs. Your BIOS should detect all valid EFI files and show a tidy GRUB alternative. What make and model is your computer?
I somewhat wasn’t able to figure out how to actually enter it, although I followed the tutorial in the manual. It would only show something on screen when the Windows Login appeared. (I accessed the fedora installation stick through Settings -> Update -> Recovery -> Advanced -> Boot from removable)
@xtym The solution provided in the linked thread did not help me either
@mrharrison, I’ve checked grub.cfg contents you’ve posted, and as far as I can tell it’s correct. It shows timeout set to 25 seconds (as you’ve set through grub.cfg), it shows menu entry for your windows partition correctly.
It looks like some problem with grub we’ve had here on Ask Fedora some time ago, I’ll try to find a link to share with you. That one was some kind of misunderstanding between grub and some BIOSes.
If that’s the issue here as well (can’t be sure, but it looks like it), then updating your BIOS has some small chance of helping you. You can do it from HP Support Assistant program from your Windows system.
EDIT: This is the thread I was thinking of, but it actually doesn’t look like your case. I’ll post it here just in case we have something alike (if not exactly similar):
Do you actually have access to your Windows, can you boot into it?
Regarding boot menu I was talking about (and @andrewnet did too). I couldn’t find instructions specific to your model, but all the HP notebook I’ve seen (seversal, not that many) and one monoblock PC all have this configuration. You can access HP’s boot menu by pressing [ESC] right after power on, when you see an HP logo on the screen. I just press it rapidly several times until I see the menu usually. It should display the menu alike to detailed here:
Also you can press [F10] instead of ESC to access you BIOS/UEFI setup screen, or [F9] for boot device selection.
There are 2 ways trough Bios and trough Fedora, lets try Fedoras way first:
1- Check that your boot order didn’t change:
If you still have boot order 0000 how windows boot loader lets put this in first place.
sudo efibootmgr - o 0000,0003,0004,0001,0002,0005,0006
Note -->0000 = windows boot loader if it did change the code, change it, place in first position the boot order than ddo reference to the windows boot loader, check what your windows boot loader is active, (it is active if you see the symbol * in them like this one:
If reinstall didn’t the trick, you can start windows 10 like indicate before and try a clean reinstall of fedora with default partition table in place of personal configuration to check if there was some step than get wrong.
Can you try just avoiding Grub and pressing ‘esc’ or ‘f9’ right after you first boot. Like I said it’s a bit of a misconception that Grub is needed for EFI multi booting, I’ve always seen options in the BIOS/UEFI it’s self in regards to selecting which EFI to boot.
One of the disadvantages of Anaconda installer is that without warning it relies on the hybride mbr in case you boot from usb/legacy_bios but you have gpt/partitions_talbe ,This sometimes causes problems(at least I personally caused some problems previously).
This was previously I do not know now if this behavior is still adopted.
Well, first of all, you should be able to enter BIOS regardless of what’s installed on your computer. And I think it can help us understand/resolve your issue with dualboot and grub menu.
Is there a chance your monitor just doesn’t power-up / show image fast enough for you to see HP logo and/or grub menu – before booting actually starts??
Can you please try to enter BIOS like this:
Powerdown you computer.
Press Power button on the computer’s case to power it up – and right after that –
Rapidly press [Esc] on the keyboard without stopping until you see something on the screen.
Tell us here what do you see ))) Ideally you should see HP’s start menu I’ve described above.
If you don’t see HP’s menu, then please try the same sequence after reboot, not power-down, and with keys [F10] and [F9] each.
Also if you have some kind of wireless keyboard, there’s a small chance it doesn’t reconnect fast enough after reboot/power up for BIOS to register keypresses. In such a case it would be good to try any wired keyboard – at least temporarely, until we understand what’s going on.
Two more things you can try (again, with very small chance of working) – you can set them in one go they wouldn’t conflict – are:
in /etc/default/grub set
– this should tell grub to wait indefinitely until you make a decision (by pressing enter on one of the entries). Also if you see black screen after reboot – please try pressing [up] and [down] arrows on a keyboard regardless – before pressing Enter.
and also comment this line (by setting # character before it)
– this should make grub show you graphical menu instead of text console one. This is to check if your computer for some reason has trouble with displaying console text grub menu.
I did so also before the Fedora installation, but nothing happened.
@youssefmsourani the outputs of sudo parted /dev/sda print are:
File or Directory not found
I tried with a second monitor and nothing appears. And I don’t think that my Monitor is not fast enough. I am actually able to enter Windows and Fedora respectively by choosing with the arrow-keys and then pressing enter. But it still doesn’t show anything on screen - no matter how long I wait. So I don’t think this is the issue.
That’s the problem - nothing appears, no matter how long I wait. Neither works with F10 nor F9
This looks like grub menu does work as it should – it just doesn’t show you anything on the screen for some reason.
So you see just black screen with nothing on it? Don’t your monitor report “No signal”?
Well, no. First of all, as I’ve said earlier, regardless off bootloader (grub) and OS (Windows, Fedora, etc.) you have – and even without an OS – after powering up your computer you should be able to see BIOS/UEFI startup sequence (often replaced by colorful manufacturer’s logo) and be able to enter BIOS/UEFI settings.
While this doesn’t use fancy 3D capabilities of your GPU – it still does activate and use GPU in basic text/graphics mode.
And this is exactly what you can’t see for some reason. Once more, it doesn’t look like grub or Fedora issue, more like a hardware one. Maybe for some reason your computer tries to output initial BIOS/UEFI image to another video output, not the one you have you monitor connected to (though it’s a bit strange). And after the OS starts (Fedora or Windows) – it correctly detect your monitor and outputs video to it.
This is an official guide for 875-0000 series Omens (for some reason there’s no such guide for 875-1000 ones) about accessing UEFI/BIOS settings:
Fixes issue where HDMI monitor not be detected and cause system to hang in POST.
Although your system doesn’t hang in POST (i.e. right after startup), it looks like it actually can’t detect your HDMI monitor.
So I think you can try these things:
Connect – at least temporarely – a monitor (it can be a second one) to some other video output you have available (DVI one, for example). Of course, you need to have cable and monitor input available to do so. Ideally would be to try all the video outputs available (there can also be multiple HDMI outputs on your computer).
As you can now access Windows – you can use HP Support Assistant program to check if BIOS update is available for your computer. I’d apply it if it is.
One problem I had shortly after uefi became common was similar. (I had previously never used uefi)
I had a new laptop that had windows installed and wanted to dual boot with windows/fedora.
Knowing that uefi required the EFI partition I blindly created a new EFI partition for fedora and left the windows EFI partition alone.
Installing fedora using the new EFI partition went well, but from the grub menu I could only boot to fedora. I could only boot to windows by using the BIOS menu and selecting the correct UEFI boot device.
When I realized that fedora grub was unable to access the windos boot manager because it was on a different EFI partition I deleted the fedora EFI partition, reinstalled fedora using the same EFI partition as windows already had, and everything worked fine afterward.
My problem came from not understanding UEFI so the second efi partition blocked grub access to the first (windows) efi partition.
Someone passed his HP Omen 17 to me – he wants Fedora.
So far, it hasn’t been fun. How did @mrharrison manage to get to the graphical installer in the first place? This one freezes after starting User:1000 (or something like that). With the latest nightly build (rawhide) of Netinstall, I get graphical installer but then it freezes again at the slightest change in settings. Perhaps I should start another thread
I updated it through the HP Assistant but am still unable to see the UEFI/GRUB
I already tried with HDMI on another monitor and USB-C on my normal Monitor - neither worked. I will try with DisplayPort but need to buy a cable first.
I only have one EFI-Partition
Yeah I also struggled with coming to the GUI since I never see the UEFI to change the boot order. I think I somehow changed under normal windows the boot order or it even is default to first boot from USB-Sticks. I used fedora MediaWriter to create the bootable stick.
@mrharrison, I think at this point it can be useful to contact HP’s tech support (if you can, of course). Inability to enter BIOS/UEFI settings is quite an inconvenience in my book – and has nothing to do with Fedora or grub specifically.
I wouldn’t even mention Fedora to them (so that not to confuse them), I’d just state that I can’t access BIOS/UEFI settings, monitor stays black.
One more thing to check/try is this. Windows has an option somewhere in the Settings app to reboot to UEFI settings. Can you try this and see if you can see anything on your screen? If it does boot to UEFI settings but you can’t see anything – [Ctrl]+[Alt]+[Del] or reset button on your case should reboot your computer to normal startup sequence.