I’ve been using manjaro just fine, but I can’t seem to dual boot from it anymore despite the fact that I get the grub options GUI menu, this happens when I hook a NVMe Windows 11 SSD to my motherboard (which boots just fine) but I can’t boot to manjaro linux. I get grub and then once I press “manjaro linux” I wait for 20 seconds with a black screen, the computer restarts and never starts manjaro. How do I fix this? is there a way to create an option for Windows 11 from the grub bootloader screen?
How would we know, when you’re being this frugal with information? There could be several explanations for what you are experiencing.
For starters, one of your systems could be installed in native UEFI mode and the other one in legacy BIOS emulation mode.
The fact that you are only seeing the grub
menu appear after plugging in the Windows drive suggests that you’ve got two copies of grub
— one on the regular drive and one on the Windows drive. This latter one would be the one giving you the grub
menu. But then again, it’s also the one that fails to boot Manjaro, while — at least, going by what you write — the grub
without the menu on the Manjaro drive boots normally.
If we’re going to speculate a bit more, it is not unthinkable that you have Secure Boot enabled, and that the grub
on the Manjaro drive was configured for that while the one on the Windows drive was not. We don’t know, because you are not giving us any information.
Yes of course there is. Enabling the os_prober
in /etc/default/grub
and running update-grub
should take care of that.
As the matter of fact, you’ve been around here long enough by now to know this, and especially so given that this subject regularly comes up here at the forum. And then there’s also the Arch Wiki page on grub
.
Tell you what, with your Windows drive plugged in, you can start by giving us the output of…
sudo fdisk -l
You can do this from the live USB, by the way. You don’t even need to chroot
.
The grub menu always appears. (and it’s the same exact one as if the NVMe wasn’t hooked)
That and fast boot is disabled.
I could give tons of information, I don’t know what’s more relevant. I also tried disabling CSM, sata mode to ahci, i tried disabling completely booting from the NVMe SSD from the bios (Gigabyte b550 m k).
So then what exactly is the problem? Without the Windows drive plugged in, Manjaro boots normally, but with the Windows drive plugged in, it fails to boot? Does that describe the problem?
yes, exactly
If you try booting up by way of the boot manager menu of the UEFI itself — I don’t know what it’s like on your system, but on my motherboard, I can bring up that menu by pressing F11 during the cold boot process, when the computer is running its POST routines — then can you boot in either Manjaro or Windows?
And which entries do you see in that boot menu? I would expect there to be at least three, and possibly more for USB devices and/or optical drives. The ones I would expect to see on your system would be…
- UEFI OS
- Manjaro
- Windows
The “UEFI OS” entry would be the default fallback entry, starting from the EFI/boot/bootx64.efi
file in the $esp
on the primary drive. The “Manjaro” entry would be EFI/Manjaro/grubx64.efi
, which should be identical to EFI/boot/bootx64.efi
. The “Windows” entry uses a more elaborate construct under the EFI
directory of the $esp
.
Best would be to try booting with each of those three entries, so that we know which one does and which one does not work.
It could be a problem with your (so-called) EFI variables, which are the entries in the UEFI’s CMOS memory that correspond to the files in the $esp
partition. And the priority of those can be set, by the way, with the command efibootmgr
, but let’s first try and see where the problem is located.
Note: It’s already very late here in my time zone, and I’ll be going soon, but maybe — and hopefully, because I don’t do Windows-related stuff — someone else will pick up on this thread in the meantime.
It’s been solved for now, I think it has something to do with plugging my manjaro flash drive and playing with the boot sequence in the motherboard configuration. I’ll post some more about it
Please do. Other members may at some point be running into the same problem.
I’m no more informed about the OP’s issue than I was after reading the first post.
If you say so.
Please ensure that;
- Each OS is installed and configured as pure UEFI (disable Legacy/MBR booting) → including the Installer medium (
DVD/ISO/USB
) which must also have booted as UEFI. - Fast Startup (this is not Fast Boot) is disabled in Windows →
powercfg /h off
from a command prompt with elevated permissions (as Administrator). - Manjaro is selected as first in boot order in your UEFI BIOS settings.
os-prober
is enabled in/etc/default/grub
→ UncommentGRUB_DISABLE_OS_PROBER=false
.
If all of these factors are confirmed, then Manjaro and Windows should co-exist in a multi-boot scenario.
Note that Windows 11 (24H2) may add some (as yet) undocumented complication into the mix; for example, re-enabling Secure Boot unexpectedly.
A workaround may need to be employed to allow Windows 11 to boot without Secure Boot;
If in the unlikely event that one OS is installed properly as UEFI, and the other one isn’t, the best resolve is to start from scratch with the OS that isn’t, making certain the above bullet points are attended to.
Regards.
In future, please do.
A first post containing some irrelevancy is always better than containing effectively no actionable information, and asking “How do I fix this?”
Always give as much detail as possible, and this will always be appreciated by those wishing to help.
This also extends to;
System Information
While information from *-fetch
type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;
Output of the inxi
command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
- inxi man pages (Arch Manual)
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
The NVMe device had an OS beforehand and I don’t know if this one was UEFI, I formatted the device to gpt and ntfs, and installed Tiny11 and never had anymore problems. I use dual boot all the time now, from the UEFI menu.
Well, it seems you have everything under control.
As there seems to be no clear issue or solution, and you haven’t provided system information, as requested, I see no reason why this topic should not be closed.
Regards.