Linux boot menu shows up instead of manjaro (Dual booting)

If you restart your machine now, do you get to Manjaro's Grub boot menu?

1 Like

Nope.
Still the same. Check the image attached if it might show something to you.
Imagepipe_0

...still not convinced.

■■■■ i totally forgot about that. Extremely sorry.
I will just do it now.
Update : yes i just tested with test -d /sys/firmware/efiand it gave UEFI as output.

I guess no since there's

because of

While it should have been -l /EFI/manjaro/grubx64.efi.

1 Like

@openminded, I don't understand why:

/File(EFImanjarogrubx64.efi)

But see (scroll to #3):

And (scroll to "UEFI - additional commands [Must be done in UEFI]") :

Looks the format is indeed:

\EFI\Manjaro\grubx64.efi

1 Like

Btw guys i just installed Lubuntu along with mint and manjaro and it replaced manjaro's grub with its own.
Tho i still cant boot manjaro from that.
Also could it be because of my BIOS which is old?

Ubuntu, Fedora, openSUSE, etc, literally everything except Arch-based distros cannot boot Manjaro or Arch due to differences in Grub implementation between them. Try the following:

sudo efibootmgr -b 0003 -B
sudo efibootmgr -b 0001 -B
sudo efibootmgr -c -d /dev/sda -p 1 -w -L "Manjaro" -l /EFI/manjaro/grubx64.efi -v

and post the output after the last command here.

@Marte
I can't say for sure what's wrong or right, I can only speak for myself, and according to my experience, regular slashes always work. I created a numerous amount of entries with such commands during these several years I've been using Manjaro and other Linux distros with various bootloaders, be it fwupd, memtest, kernel, rEFInd, shim or systemd-boot. It worked every time.
Of course, it could be some UEFI bug on @Manjaroftw's side. This exceeds the scope of my knowledge.

2 Likes

Installing another system with a bootloader incapable of booting Manjaro would not solve your initial issue.

At this point, perhaps as a kind of "workaround", you could use a custom.cfg containing an entry for booting Manjaro, in Mint's /boot/grub

2 Likes

As long as it works, why not.
I was just following the syntax "literally" and apparently it didn't work in this case.

1 Like
sudo efibootmgr -b 0003 -B
[sudo] password for XYZ: 
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 3000,3002,3003,2001,2002,2003
Boot0000* ubuntu
Boot0002* EFI HDD Device (ST500LM012 HN-M500MBB)
Boot0010* USB Hard Drive (UEFI) - MXT-USB
Boot0011* USB Hard Drive - MXT-USB
Boot0012* USB Hard Drive (UEFI) - MXT-USB
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* Internal Hard Disk or Solid State Disk
Boot3001* Internal Hard Disk or Solid State Disk
Boot3002* Internal Hard Disk or Solid State Disk
Boot3003* Internal Hard Disk or Solid State Disk
Boot3004* Internal Hard Disk or Solid State Disk
[nihal@nihal-hp650notebookpc ~]$ sudo efibootmgr -b 0001 -B
Could not delete variable: No such file or directory
[nihal@nihal-hp650notebookpc ~]$ sudo efibootmgr -c -d /dev/sda -p 1 -w -L "Manjaro" -l /EFI/manjaro/grubx64.efi -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0001,3000,3002,3003,2001,2002,2003
Boot0000* ubuntu        HD(1,MBR,0xd82f32de,0x800,0xa6800)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* EFI HDD Device (ST500LM012 HN-M500MBB)        PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,MBR,0xd82f32de,0x800,0xa6800)RC
Boot0010* USB Hard Drive (UEFI) - MXT-USB       PciRoot(0x0)/Pci(0x1a,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x0,0x5cf8f0,0x2000)RC
Boot0011* USB Hard Drive - MXT-USB      BBS(7,�,0x500).......................................................................
Boot0012* USB Hard Drive (UEFI) - MXT-USB       PciRoot(0x0)/Pci(0x1a,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x0,0x5cf8f0,0x2000)RC
Boot2001* USB Drive (UEFI)      RC
Boot2002* Internal CD/DVD ROM Drive (UEFI)      RC
Boot3000* Internal Hard Disk or Solid State Disk        RC
Boot3001* Internal Hard Disk or Solid State Disk        RC
Boot3002* Internal Hard Disk or Solid State Disk        RC
Boot3003* Internal Hard Disk or Solid State Disk        RC
Boot3004* Internal Hard Disk or Solid State Disk        RC
Boot0001* Manjaro       HD(1,MBR,0xd82f32de,0x800,0xa6800)/File(\EFI\manjaro\grubx64.efi)

actually i just wanted to try lubuntu as both manjaro and mint are running slow on this laptop due to only 2gb ram , nothing else.

The lazy way to change the boot order is to first boot into Manjaro and then open a terminal and run

sudo grub-install

Most of the time the grub-install defaults are correct, but sometimes the long form is required. The command populates the grub bootstrap and sets Manjaro first in boot order. update-grub just populates the grub menu.

Custom.cfg is a good option or try MX-linux which can boot Manjaro.

If you use the mint or lubuntu grub menu, you can boot Manjaro using the fallback (advanced menu) option. It won't load the micro-code but it should get to the desktop so that you can fix grub from Manjaro.

2 Likes

I tried grub-install and -update commands just now. Didnt work.
Will check the others tomorrw after a sleep.
I really do appreciate everyone's help ! :smiley:

What specific errors did you get?

It might be helpful to post

inxi -Fxxxza --no-host

A reboot was necessary after that. Instead you issued grub-install and now who knows what config you have there... Only efibootmgr -v will tell.

1 Like
inxi -Fxxxza --no-host
System:    Kernel: 5.6.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6-x86_64 root=UUID=343072ef-2892-4ea1-b9f5-1845cdaba0fe rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: KDE Plasma 5.18.5 tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: Hewlett-Packard product: HP 650 Notebook PC v: 0886110000005B10002600000 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 1858 v: 65.34 serial: <filter> UEFI: Insyde v: F.39 date: 05/13/2014 
Battery:   ID-1: BAT0 charge: 4.9 Wh condition: 38.0/38.0 Wh (100%) volts: 11.7/10.8 model: HP type: Li-ion serial: N/A 
           status: Charging 
CPU:       Topology: Dual Core model: Intel Core i3-2328M bits: 64 type: MT MCP arch: Sandy Bridge family: 6 model-id: 2A (42) 
           stepping: 7 microcode: 2F L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 17564 
           Speed: 798 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Hewlett-Packard driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0116 
           Display: x11 server: X.Org 1.20.8 driver: intel unloaded: modesetting alternate: fbdev,vesa compositor: kwin_x11 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.0.7 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k5.6.15-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel 
           port: 3000 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: eno1 state: down mac: <filter> 
           Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Hewlett-Packard driver: ath9k v: kernel 
           port: 3000 bus ID: 02:00.0 chip ID: 168c:0032 
           IF: wlo1 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 2-1.4:6 chip ID: 0cf3:311d serial: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 7.93 GiB (1.7%) 
           ID-1: /dev/sda vendor: Seagate model: ST500LM012 HN-M500MBB size: 465.76 GiB block size: physical: 4096 B 
           logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0002 scheme: MBR 
Partition: ID-1: / raw size: 66.12 GiB size: 64.59 GiB (97.67%) used: 7.92 GiB (12.3%) fs: ext4 dev: /dev/sda8 
Sensors:   System Temperatures: cpu: 45.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 187 Uptime: 3m Memory: 1.77 GiB used: 833.0 MiB (46.1%) Init: systemd v: 245 Compilers: gcc: 10.1.0 
           Shell: bash v: 5.0.17 running in: yakuake inxi: 3.0.37 



efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 3000,3001,3002,2001,2002,2003
Boot0000* ubuntu        HD(1,MBR,0xd82f32de,0x800,0xa6800)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* manjaro       HD(1,MBR,0xd82f32de,0x800,0xa6800)/File(\EFI\manjaro\grubx64.efi)
Boot0002* EFI HDD Device (ST500LM012 HN-M500MBB)        PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,MBR,0xd82f32de,0x800,0xa6800)RC
Boot0010* USB Hard Drive (UEFI) - MXT-USB       PciRoot(0x0)/Pci(0x1a,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x0,0x5cf8f0,0x2000)RC
Boot0011* USB Hard Drive - MXT-USB      BBS(7,�,0x500).......................................................................
Boot0012* USB Hard Drive (UEFI) - MXT-USB       PciRoot(0x0)/Pci(0x1a,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x0,0x5cf8f0,0x2000)RC
Boot2001* USB Drive (UEFI)      RC
Boot2002* Internal CD/DVD ROM Drive (UEFI)      RC
Boot3000* Internal Hard Disk or Solid State Disk        RC
Boot3001* Internal Hard Disk or Solid State Disk        RC
Boot3002* Internal Hard Disk or Solid State Disk        RC
Boot3004* Internal Hard Disk or Solid State Disk        RC

should i just go for a clean install maybe?

If I understand this correctly, it is the output from live system booted from USB stick?

If so, do sudo efibootmgr -c -d /dev/sda -p 1 -w -L "Manjaro" -l /EFI/manjaro/grubx64.efi -v and reboot to BIOS with no USB stick plugged in. There you should find Manjaro in Boot options along with ubuntu and move it to the top of the list, making it the first boot entry. Then reboot, and you should see Manjaro's grub able to boot your Manjaro system.

Forum kindly sponsored by