You are not logged in.
Head_on_a_Stick wrote:Please post the output of this command from the problematic machine:
efibootmgr -u
here it is
Sorry OP, I forgot that Ubuntu's options are different. I wanted to see the actual EFI loaders so I think we need
efibootmgr -uv
And please use code tags rather than quote tags when posting terminal output. Use the Edit button on your posts to change this, it will make the thread more readable. Thanks.
Try deleting more and more entries as you go.
I really don't think randomly deleting boot entries is helpful. We could end up bricking the OP's machine.
"It's impossible for a white person to believe in capitalism and not believe in racism. You can't have capitalism without racism."
— Malcolm X
Offline
heres the output
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0014,000D,000E,0007,0008,0009,000A,000B,000C,0013
Boot0000 BIOS Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0002 Diagnostic Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003 Recovery and Utility FvFile(0b150fda-3bdd-4406-9859-448177476993)
Boot0004 Diagnostic Program FvFile(29f85733-2b1a-4821-8f61-2614778c0c73)
Boot0005 Diagnostic Progrogram ROM VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,c0f527e7c05f4d498df59dc81ac2cfdd00)
Boot0007* Drive0 HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0008* Drive2 HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot0009* Drive4 HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f604)
Boot000A* Drive5 HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f605)
Boot000B* CD/DVD Drive: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,23e6a6e08bae6940adb9a7b5c5f00628)
Boot000C* NETWORK: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000D* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot000E* USB CD/DVD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,d630a9056829ce41861e8c380ff2225a)
Boot000F* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot0010* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot0011* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0012* Erase Disk FvFile(43f9b080-c902-4737-b306-487050f7caa5)
Boot0013* ubuntu HD(2,GPT,abd906a8-ec78-437e-ad84-763b6b0787cf,0x1000,0x100800)/File(\EFI\ubuntu\shimx64.efi)
Boot0014* ubuntu HD(2,GPT,6a2a8886-59cb-402b-ae91-8bbe11f89674,0x1000,0x100800)/File(\EFI\ubuntu\shimx64.efi)
And please use code tags rather than quote tags when posting terminal output.
Sorry, updated it
Offline
Your first post doesn't show cmdpath in the output, but it's used by the embeded grub.cfg to load the grub.cfg on the ISO.
First things, first. Confirm whether this is even the correct GRUB you're launching. Run:
cat (memdisk)/boot/grub/grub.cfg
and see if it matches https://gitlab.archlinux.org/archlinux/ … #L588-L595 .
It it matches, try:
configfile (cd0)/EFI/BOOT/grub.cfg
(cd0) may need to be (cd1), (cd2), etc., run ls to see which devices are available.
Offline
Confirm whether this is even the correct GRUB you're launching. Run:
cat (memdisk)/boot/grub/grub.cfg
It matches
It it matches, try:
configfile (cd0)/EFI/BOOT/grub.cfg
the output of ls is
(memdisk) (hd0) (hd0,msdos1) (hd1) (hd1,gpt3) (hd1,gpt1) (cd0)
so i went with cd0, and it just cleared the console and when doing ls again there was a new device called (proc)
Last edited by vrik (2023-01-31 11:43:29)
Offline
And (cd0)/EFI/BOOT/grub.cfg matches https://gitlab.archlinux.org/archlinux/ … b/grub.cfg , right?
Best I can suggest is creating the installation medium using https://wiki.archlinux.org/title/USB_fl … NU/Linux_4 and editing EFI/BOOT/grub.cfg on it. E.g. trying to comment out "terminal_output gfxterm" or some other line and see if it helps or not.
Or just try typing out the grub.cfg line-by-line and see where it goes wrong.
Offline
It it matches, try:
configfile (cd0)/EFI/BOOT/grub.cfg
this worked, its just that the first time i tried it i chose the wrong device.
Thanks everyone for help!
Offline
Just to confirm, when you first get dumped in the GRUB shell, there's no cmdpath in the output of set, right?
And just for curiosity, what was the correct device name for you?
Offline
what was the correct device name for you?
it was (hd0,msdos2), i knew what device it was using a very primitive method of ls > unplugging the usb > ls > checking whats missing
there's no cmdpath in the output of set, right?
now that its fixed there is no way for me to check it, though in my initial post i gave the output of set and there seems to be nothing related to cmdpath (could have been a error on my end because i had no way to copy the output so i wrote the output by hand)
Last edited by vrik (2023-01-31 12:06:45)
Offline