Booting Issues

I did it however I’m still having black screen after doing that.View attachment 24558

That looks like it's off.
What I mean is:
1. Press "Power On"
2. Keep pressing "Delete" or "F12" on your keyboard until you see the BIOS menu.
 


That looks like it's off.
What I mean is:
1. Press "Power On"
2. Keep pressing "Delete" or "F12" on your keyboard until you see the BIOS menu.
Trust me I did it. It might be looking like I just only turned on PC Monitor however it was loading up PC before just only each time I'm turning on PC I can just only load up Ubuntu Linux 24.04.02 LTS PC instead of Microsoft Windows 11 PC. It can't be properly loaded up after pressing F12 or DEL PC keyboard buttons because of black screen control unit already got manually turned on by me anyway. Believe me or not,but this is exactly of what keeps happening right now.
 
Trust me I did it. It might be looking like I just only turned on PC Monitor however it was loading up PC before just only each time I'm turning on PC I can just only load up Ubuntu Linux 24.04.02 LTS PC instead of Microsoft Windows 11 PC. It can't be properly loaded up after pressing F12 or DEL PC keyboard buttons because of black screen control unit already got manually turned on by me anyway. Believe me or not,but this is exactly of what keeps happening right now.
If you can't enter the UEFI/BIOS, you have a motherboard issue. It's a separate thing but it complicates this. We can try poking around GRUB though... Try starting up the PC and keep pressing Shift until you see the GRUB menu.
If for whatever reason that doesn't work, my suggestion is to run efibootmgr -v in the CLI. Post the output here.
 
Try starting up the PC and keep pressing Shift until you see the GRUB menu.

if installed with secure boot enabled, it could be the escape key.

I find this is usually a timing issue. Don't just press and hold the specific key. Press it over and over again in rapid succession as you're turning the power on. If it's F10, start pressing that button over and over again as you turn the power on.

Also, I dimly recall a computer that would not let me access UEFI/BIOS if I rebooted. It would only work on a full restart. It was easiest to turn it off entirely and then start the system with the above mentioned button mashing technique.
 
If you can't enter the UEFI/BIOS, you have a motherboard issue. It's a separate thing but it complicates this. We can try poking around GRUB though... Try starting up the PC and keep pressing Shift until you see the GRUB menu.
If for whatever reason that doesn't work, my suggestion is to run efibootmgr -v in the CLI. Post the output here.
CLI? Is it Terminal?
 
If you can't enter the UEFI/BIOS, you have a motherboard issue. It's a separate thing but it complicates this. We can try poking around GRUB though... Try starting up the PC and keep pressing Shift until you see the GRUB menu.
If for whatever reason that doesn't work, my suggestion is to run efibootmgr -v in the CLI. Post the output here.
I did it anyway and here's what I got.
Screenshot from 2025-03-11 16-02-21.png
 
Hmm... I wonder if it'd be worth trying to change the boot order? Maybe setting 0000 to the first position, at least long enough to see if Windows loads. You'd do that with efibootmgr -o ****.****,****,****. In this case you'd set it 0000,0001,0005,0003.
 
Okay here's full hexadecimal code. With code quotations.
Code:
luke1@luke1-B450-AORUS-ELITE:~$ efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0005,0003,0000
Boot0000* Windows Boot Manager    HD(1,GPT,2de3f79c-3c9c-4bdc-a2b5-11bafe679468,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000079000100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 9c f7 e3 2d 9c 3c dc 4b a2 b5 11 ba fe 67 94 68 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 79 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Ubuntu    HD(1,GPT,db1768d7-216d-47b6-9637-bcd4a8d95d70,0x800,0x219800)/File(\EFI\UBUNTU\SHIMX64.EFI)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 98 21 00 00 00 00 00 d7 68 17 db 6d 21 b6 47 96 37 bc d4 a8 d9 5d 70 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 55 00 42 00 55 00 4e 00 54 00 55 00 5c 00 53 00 48 00 49 00 4d 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0003* CD/DVD Drive    BBS(CDROM,,0x0)0000474f00004e4fbb00000001000000750048004c002d00440054002d005300540020004200440044005600440052005700200043004800300038004c0053003100300000000501090003000000007fff040002010c00d041030a0000000001010600010801010600020003120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63900480039004900310042003000430031003100200032002000200020002000200020002000200000007fff04000000424f
      dp: 05 01 09 00 03 00 00 00 00 / 7f ff 04 00
    data: 00 00 47 4f 00 00 4e 4f bb 00 00 00 01 00 00 00 75 00 48 00 4c 00 2d 00 44 00 54 00 2d 00 53 00 54 00 20 00 42 00 44 00 44 00 56 00 44 00 52 00 57 00 20 00 43 00 48 00 30 00 38 00 4c 00 53 00 31 00 30 00 00 00 05 01 09 00 03 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 01 08 01 01 06 00 02 00 03 12 0a 00 02 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 39 00 48 00 39 00 49 00 31 00 42 00 30 00 43 00 31 00 31 00 20 00 32 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f
Boot0005* Hard Drive    BBS(HD,,0x0)0000474f00004e4fad000000010000007500530053004400500052002d00430058003400300030002d003000310054002d004700320000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000470031005700370030003500330020003400200020002000200020002000200020002000200000007fff04000000424f00004e4fad000000010000007500530061006e004400690073006b002000530044005300530044004100320034003000470000000501090002000000007fff040002010c00d041030a0000000001010600010801010600020003120a000300ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63700310031003000390032003500340032003000360030002000200020002000200020002000200000007fff04000000424f
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 00 00 47 4f 00 00 4e 4f ad 00 00 00 01 00 00 00 75 00 53 00 53 00 44 00 50 00 52 00 2d 00 43 00 58 00 34 00 30 00 30 00 2d 00 30 00 31 00 54 00 2d 00 47 00 32 00 00 00 05 01 09 00 02 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 03 01 01 01 06 00 01 00 03 12 0a 00 00 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 30 00 47 00 31 00 57 00 37 00 30 00 35 00 33 00 20 00 34 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f 00 00 4e 4f ad 00 00 00 01 00 00 00 75 00 53 00 61 00 6e 00 44 00 69 00 73 00 6b 00 20 00 53 00 44 00 53 00 53 00 44 00 41 00 32 00 34 00 30 00 47 00 00 00 05 01 09 00 02 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 01 08 01 01 06 00 02 00 03 12 0a 00 03 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 37 00 31 00 31 00 30 00 39 00 32 00 35 00 34 00 32 00 30 00 36 00 30 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f
luke1@luke1-B450-AORUS-ELITE:~$
Now without code quotations(of where probably you can see even more things further details).
So at least I can be sure that at least I copied and pasted everything that might be felt needed.
luke1@luke1-B450-AORUS-ELITE:~$ efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0005,0003,0000
Boot0000* Windows Boot Manager HD(1,GPT,2de3f79c-3c9c-4bdc-a2b5-11bafe679468,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000079000100000010000000040000007fff0400
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 9c f7 e3 2d 9c 3c dc 4b a2 b5 11 ba fe 67 94 68 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 79 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Ubuntu HD(1,GPT,db1768d7-216d-47b6-9637-bcd4a8d95d70,0x800,0x219800)/File(\EFI\UBUNTU\SHIMX64.EFI)
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 98 21 00 00 00 00 00 d7 68 17 db 6d 21 b6 47 96 37 bc d4 a8 d9 5d 70 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 55 00 42 00 55 00 4e 00 54 00 55 00 5c 00 53 00 48 00 49 00 4d 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0003* CD/DVD Drive BBS(CDROM,,0x0)0000474f00004e4fbb00000001000000750048004c002d00440054002d005300540020004200440044005600440052005700200043004800300038004c0053003100300000000501090003000000007fff040002010c00d041030a0000000001010600010801010600020003120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63900480039004900310042003000430031003100200032002000200020002000200020002000200000007fff04000000424f
dp: 05 01 09 00 03 00 00 00 00 / 7f ff 04 00
data: 00 00 47 4f 00 00 4e 4f bb 00 00 00 01 00 00 00 75 00 48 00 4c 00 2d 00 44 00 54 00 2d 00 53 00 54 00 20 00 42 00 44 00 44 00 56 00 44 00 52 00 57 00 20 00 43 00 48 00 30 00 38 00 4c 00 53 00 31 00 30 00 00 00 05 01 09 00 03 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 01 08 01 01 06 00 02 00 03 12 0a 00 02 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 39 00 48 00 39 00 49 00 31 00 42 00 30 00 43 00 31 00 31 00 20 00 32 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f
Boot0005* Hard Drive BBS(HD,,0x0)0000474f00004e4fad000000010000007500530053004400500052002d00430058003400300030002d003000310054002d004700320000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000470031005700370030003500330020003400200020002000200020002000200020002000200000007fff04000000424f00004e4fad000000010000007500530061006e004400690073006b002000530044005300530044004100320034003000470000000501090002000000007fff040002010c00d041030a0000000001010600010801010600020003120a000300ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63700310031003000390032003500340032003000360030002000200020002000200020002000200000007fff04000000424f
dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
data: 00 00 47 4f 00 00 4e 4f ad 00 00 00 01 00 00 00 75 00 53 00 53 00 44 00 50 00 52 00 2d 00 43 00 58 00 34 00 30 00 30 00 2d 00 30 00 31 00 54 00 2d 00 47 00 32 00 00 00 05 01 09 00 02 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 03 01 01 01 06 00 01 00 03 12 0a 00 00 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 30 00 47 00 31 00 57 00 37 00 30 00 35 00 33 00 20 00 34 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f 00 00 4e 4f ad 00 00 00 01 00 00 00 75 00 53 00 61 00 6e 00 44 00 69 00 73 00 6b 00 20 00 53 00 44 00 53 00 53 00 44 00 41 00 32 00 34 00 30 00 47 00 00 00 05 01 09 00 02 00 00 00 00 7f ff 04 00 02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 01 08 01 01 06 00 02 00 03 12 0a 00 03 00 ff ff 00 00 7f ff 04 00 01 04 3e 00 ef 47 64 2d c9 3b a0 41 ac 19 4d 51 d0 1b 4c e6 37 00 31 00 31 00 30 00 39 00 32 00 35 00 34 00 32 00 30 00 36 00 30 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 00 00 7f ff 04 00 00 00 42 4f
luke1@luke1-B450-AORUS-ELITE:~$
 
Last edited:
Yup, as I feared, you installed GRUB to your Windows partition (240GB) as well. So that means you are booting from the disk that windows is on (240GB). So you have been booting from a GRUB install on your Windows disk (240GB) into your Ubuntu install on your Ubuntu disk (1TB). Hence update-grub is failing (it is updating the GRUB install on the 1TB disk). As @KGIII has said, set Windows to boot first if you need access to Windows.

Sadly, you need to actually access your BIOS settings to "fix" things coz like I said, efibootmgr has certain limits. So until you can get into there you're sunk...
That said, after logging into Windows, make sure you disable fastboot and power off completely. Else Windows does weird stuff. That may even be why you can access the BIOS menu when you power on.

You could also try wiping your boot list:
efibootmgr -b xxxx -B
for each entry, cold boot, and let the BIOS do its thing (rescan + repopulate)

Another option is a quick attempt at a reinstall may work but you need to find the ESP partition on the 1TB, reinstall geub, and then try to set the new boot priority. If nothing has changed since the discs screenshot:
mount /dev/sda1 /mnt/
grub-install --target=x86_64-efi --efi-directory=/mnt/efi --bootloader-id=GRUBNEW
umount /dev/sda1
Note: you may need to do the above in a chroot, not sure why, but there you have ir

Don't feel overwhelmed, I like to add lots of info for people stumbling on this post. Just start with getting back into your BIOS either booring right into Windows or erasing the existing entries and forcing the BIOS to rescan.
 
Last edited:
I'm semi-optimistic that the Windows bootload will show the Linux boot option.

Yes, this is possible. Well, it was. Windows was quite happy to show the option to boot to Linux with their bootloader - if the OS knows the other OS exists.

So, I'm a bit optimistic in those regards. I'm not very optimistic, just a little.
 
What about this alternative method? So what can I do to properly make doubly bootable operating systems from Ubuntu Linux 24.04.02 LTS PC into for instance nowadays Microsoft Windows 11 PC...etc.?
Screenshot from 2025-03-19 18-35-50.png
 
Last edited:
Definitely reinstalling GRUB and ensuring the menu is visible (Unhide boot menu) is a good start. Not sure if Boot Repair runs os-prober, but I assume so. Not sure you want to restore old EFI files files since os-prober will repopulate them. I'm not 100% on the Backup and rename Windows EFI files, but I'm assuming that option will make it effectively only boot GRUB and then have an entry that'll chainload bootmgfw.efi for Windows. That's ultimately what you want... Although who knows what Windows does next update. I feel like I dodged a major bullet switching away from dual systems back on Win7 as I have had countless people here and IRL with dual-boot issues when it comes to Windows 10 (and now 11).

Side note: I don't want to be that guy who says, "Ah just change 100% to Linux... <insert MS is so evil rant>" but I think it may be time to assess the ROI of the effort you're going to. I mean I've been forced to use Windows 10 because Amazon are jerks and KC doesn't support Linux (which is funny since AWS is powered by Linux), and on my rig, I run Windows 10 in a VM. I get decent speeds without going full baremetal by giving it 10GB RAM and a raw partition instead of an image files, a'la -drive format=raw,file=/dev/sdc1 (requires permissions, i.e. add your user to disks) and while it's still slow, Windows is slow and once it has booted, it's not much slower that most Window 10 laptops.... but I'm just putting it out there. I don't really want to be the zaelot from Church of Linuxology telling you that you must give everything unto Lord Linux, because there's an evil guy in a mountain on Krypton shooting bad luck beams at you or whatever, should you not convert.
 
Definitely reinstalling GRUB and ensuring the menu is visible (Unhide boot menu) is a good start. Not sure if Boot Repair runs os-prober, but I assume so. Not sure you want to restore old EFI files files since os-prober will repopulate them. I'm not 100% on the Backup and rename Windows EFI files, but I'm assuming that option will make it effectively only boot GRUB and then have an entry that'll chainload bootmgfw.efi for Windows. That's ultimately what you want... Although who knows what Windows does next update. I feel like I dodged a major bullet switching away from dual systems back on Win7 as I have had countless people here and IRL with dual-boot issues when it comes to Windows 10 (and now 11).

Side note: I don't want to be that guy who says, "Ah just change 100% to Linux... <insert MS is so evil rant>" but I think it may be time to assess the ROI of the effort you're going to. I mean I've been forced to use Windows 10 because Amazon are jerks and KC doesn't support Linux (which is funny since AWS is powered by Linux), and on my rig, I run Windows 10 in a VM. I get decent speeds without going full baremetal by giving it 10GB RAM and a raw partition instead of an image files, a'la -drive format=raw,file=/dev/sdc1 (requires permissions, i.e. add your user to disks) and while it's still slow, Windows is slow and once it has booted, it's not much slower that most Window 10 laptops.... but I'm just putting it out there. I don't really want to be the zaelot from Church of Linuxology telling you that you must give everything unto Lord Linux, because there's an evil guy in a mountain on Krypton shooting bad luck beams at you or whatever, should you not convert.
Something more like this?
Screenshot from 2025-03-20 20-49-56.png
 
Intuition tells me along those lines minus "Restore EFI backups"... Just intuition. As I said, I don't actually know what commands the program is using. Unfortunately I'm a terminal guy, so I'm trying to interpret GUI-lingo as best I can.
But yeah, you have nothing to lose at this point. There's no risk to your data and if it comes down to it, there are still more options, but let's stick with this for now.
 
Well there is one thing you can do to be able to boot and fix just about anything. Download this distro:
Version: Full (SysV Init)
Burn to a USB drive (you have a whole lot of options if you're not comfy with dd if=antiX-23.2_x64-full.iso of=/dev/sdX bs=4096 like rufus, etcher, and others, I have no idea because I use dd because dd works, lol)

When you boot into antiX, you'll be able to chainload from the start menu, and you can edit/repair/etc. things once you're able to see what's going on...
At this point I'm thinking a full wipe of both ESPs, then only having the one Grub install on the Windows disk as it'll play nicer... But first see if you can boot both OSes from the antiX live disk.
 
I'd enable Secure Boot in Grub, it'll use shimm which gets around all those annoying compatibility issues. You can disable secure boot in your BIOS/UEFI but Windows might complain, it complains about everything. You'd do wise to Purge GRUB before reinstall for obvious reasons of all these dangling installs. If you have a graphics card or iGPU that even might not be (fully) supported, you want to add "nomodeset". And I'd Repair Windows boot files (if this util's up to date on that).

In short (recommendations):

Main Options
  • Reinstall Grub
  • Use Standard EFI file
  • Backup and rename Windows EFI files
  • Unhide boot menu 20 seconds
GRUB Location
  • OS to boot by default: /dev/sdb2
  • Separate /boot/efi partition: /dev/sda -- This is tricky, will likely be a smoother ride to uncheck and just keep it on sdb, but it will mean you'll have to have both disks inside and working, so up to you. Gomen.
GRUB Options
  • Secure Boot
  • Purge GRUB before reinstalling it
  • Upgrade GRUB to its most recent version
  • Add kernel parameter: nomodeset
Other Options
  • Repair Windows boot files
  • Upload report to pastebin -- then it's accessible and linkable here if things go pear-shaped
  • Check Internet Connection -- Obviously

Good luck and may the force be with you.
 



Latest posts

Top