¿Cómo ejecutar la reparación de arranque cuando Ubuntu es inaccesible y hay conflictos en la configuración del BIOS? (Arranque dual)

¿Cómo ejecutar la reparación de arranque cuando Ubuntu es inaccesible y hay conflictos en la configuración del BIOS? (Arranque dual)

Tengo una computadora configurada para arranque dual con Ubuntu y Windows 10, que funcionó bien durante varios meses. Recientemente, Ubuntu inició Blackscreening cuando se inició mediante Grub o anulación de arranque del BIOS (la causa probable es una actualización de Windows 10).

Actualicé un USB con Boot-Repair y puedo iniciar correctamente a través de Live USB. Sin embargo, Boot-Repair requiere arrancar con los modos CSM/Legacy deshabilitados. Cuando desactivo CSM en BIOS, aparece un error al iniciar con el mensaje "Tarjeta VGA no compatible con UEFI, la configuración de CSM se ha cambiado para compatibilidad" que parece volver a habilitar CSM automáticamente sin ninguna opción para deshabilitarlo, lo que me impide usando la reparación de arranque.

¿Qué debo hacer?

EDITAR: Mi tarjeta gráfica no es compatible con el modo UEFI. No tengo idea de cómo se supone que debo ejecutar Boot-Repair ahora.

Extracto del resumen de información de arranque de reparación de arranque:

 => No boot loader is installed in the MBR of /dev/sda.
 => Windows 7/8/10/11/2012 is installed in the MBR of /dev/sdb.
 => Windows 7/8/10/11/2012 is installed in the MBR of /dev/sdc.

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 7/2008: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi 
                       /efi/Boot/mmx64.efi /efi/ubuntu/grubx64.efi 
                       /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi 
                       /efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi 
                       /efi/Microsoft/Boot/bootmgr.efi

sda2: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 

sda3: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 8 or 10
    Boot files:        /Windows/System32/winload.exe

sda4: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/10/11/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdb1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/10/11/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdc1: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 

sdc2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdc3: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdc4: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 22.04.2 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub

sdd: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Operating System:  
    Boot files:        /boot/grub/grub.cfg


================================ 2 OS detected =================================

OS#1:   Ubuntu 22.04.2 LTS on sdc4
OS#2:   Windows 8 or 10 on sda3

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would purge (in order to unsign) and reinstall the grub-efi of
sdc4,
using the following options:  sdc3/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file

Blockers in case of suggested repair: __________________________________________

The current session is in BIOS-compatibility mode. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode. 64bits detected. Please use this software in a 64bits session. (Please use Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd) which contains a 64bits-compatible version of this software.) This will enable this feature.

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the Ubuntu 22.04.2 LTS entry (sdc3/efi/****/grub****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\grub****.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.

información relacionada