Page 4 of 13

Re: After install cannot boot

Posted: Tue Aug 15, 2023 2:59 pm
by Charlie Brown
I'm excited :biggrin:

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:01 pm
by Charlie Brown
In the meantime you can also:

Code: Select all

sudo apt dist-upgrade -y
(Not related to this issue... Just "40 packages can be upgraded." )

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:02 pm
by heydave
still the same error message and no boot.

Booting from the mx21 stick, into mx 23 on thesystem, this thing flies. I love mx. I dunno how I goofed this up.

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:04 pm
by Charlie Brown
Oh, then it's something else, not just a boot issue (efibootmgr also shows the boot order as we would like to set to: MX at #1 position ...)

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:06 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:58 pm Yeah, I guess I did all of those things.

Code: Select all

sudo grub-install --force-extra-removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX23 --recheck
[sudo] password for Katie:      
Installing for x86_64-efi platform.
Installation finished. No error reported.

Code: Select all

$ efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0001,0000,0004
Boot0000* Windows Boot Manager	HD(1,GPT,ee6665b6-7874-4cf2-9d78-4d034ddfba7a,0x100,0x10400)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* MX Linux	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0003* MX23	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) -  USB	PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO 

Code: Select all

$ find /boot/efi -ls
        1      4 drwxrwxr-x   3 root     root         4096 Dec 31  1969 /boot/efi
      113      4 drwxrwxr-x   4 root     root         4096 Aug 15 13:52 /boot/efi/EFI
      114      4 drwxrwxr-x   2 root     root         4096 Aug 15 13:52 /boot/efi/EFI/MX23
      115    136 -rw-rw-r--   1 root     root       139264 Aug 15 13:52 /boot/efi/EFI/MX23/grubx64.efi
      116      4 drwxrwxr-x   2 root     root         4096 Aug 15 13:52 /boot/efi/EFI/BOOT
      117    136 -rw-rw-r--   1 root     root       139264 Aug 15 13:52 /boot/efi/EFI/BOOT/BOOTX64.EFI 

Code: Select all

$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-10-amd64
Found initrd image: /boot/initrd.img-6.1.0-10-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
OK, thanks.
Now, let's try to tidy up some entries within UEFI in the NVRAM:
This way:
First that Windows guy:

Code: Select all

sudo efibootmgr -v -B -b 0
next the not used "MX Linux" entry:

Code: Select all

sudo efibootmgr -v -B -b 1
Now when you reboot during early bootup (aks "POST"), Press F9 or F10 to get into the UEFI boot options list.
Do yet get the MX23 listed.
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:12 pm
by heydave

Code: Select all

$ sudo efibootmgr -v -B -b 0
[sudo] password for Katie:      
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0004
Boot0001* MX Linux	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0002* rEFInd Boot Manager	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\refind\refind_x64.efi)
Boot0003* MX23	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) -  USB	PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO

Code: Select all

$ sudo efibootmgr -v -B -b 1
[sudo] password for Katie:      
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0003,0004
Boot0002* rEFInd Boot Manager	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\refind\refind_x64.efi)
Boot0003* MX23	HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) -  USB	PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
Rebooting now...

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:19 pm
by heydave
After hitting f9 boot options, I do not get mx23 listed. I get a window that says to select boot device, but my only choice is "bbot from EFI file" if I enter that,I get "No Valid file system Available"

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:28 pm
by heydave
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)
I dont think I have this in my BIOS

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:36 pm
by Charlie Brown
Although you already said you installed using the "whole disk" option, "just in case":

Code: Select all

sudo parted -l
Let's see if ESP has the flags ...

Re: After install cannot boot

Posted: Tue Aug 15, 2023 3:37 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 3:28 pm
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)
I dont think I have this in my BIOS
Ok; some of those UEFI-systems (PC-BIOS/UEFI)systesm) do only allow to preselct efi-booloader when secureboot is enabled. So you might enable secureboot again, and if there is an Supervisor-Password field you may also need set first such thing (write down use a simple one). WHen rebooted into UEFI-ssysem Setup with SecureBoot enabled you may need enter the supervisout password. (or may be not).
Now search again within UEFI-system to add an efi-file. Or the internal boot-drive to boot allow in efi-mode.
The check whether efi-loader are signed is not done now, only when booting. So you may disabled secureboot again.