Re: Request about Boot Repair Disk

2024-01-30 Thread Max Nikulin

On 28/01/2024 01:03, fran...@libero.it wrote:
If I use SuperGrub cd by 
manual booting I can access to debian and boot it. So I used Boort 
Repair Disk 64 to try to repair, but it gave me a report advicing me to 
ask online with that report here under: (it is a long report)


I have no idea concerning these tools

sda1: 
File system: vfat

Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi


No efi/debian here despite it looks like an EFI System Partition


efibootmgr -v
No BootOrder is set; firmware will attempt recovery


It should be set and debian installer does it.


df480f092e56b632513b4616bdeade95 sda1/Boot/bootx64.efi


Either mangled output and really it is efi/boot/bootx64.efi, a boot file 
for removable device or some installer put files in a wrong folder. In 
the former case, some firmwares may give this option higher priority.



df480f092e56b632513b4616bdeade95 sda1/Microsoft/Boot/bootmgfw.efi
0a70ebdfe73694eb6188f70e81b47a79 sda1/Microsoft/Boot/bootmgr.efi



Can you help me to obtain to have Grub with the 2 OSes at booting?


Did you have grub-efi-amd64-signed and shim-signed installed? Looks like 
you installed Linux in legacy mode instead of UEFI one.




Re: Request about Boot Repair Disk

2024-01-28 Thread DdB
Am 27.01.2024 um 19:03 schrieb fran...@libero.it:
> (it is a long report)
This is interesting ... BUT i lack the required experience:
Neither do i use Windows nor a notebook, but i would guess, that the
last paragraph from your report contains the root cause of your problem:

> Please do not forget to make your UEFI firmware boot on the Debian GNU/Linux 
> 12 (bookworm) entry (sda1/efi//shim.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\\shim.efi ( will be updated in 
> the final message) > 

As you already found by yourself, both systems are setup to be bootable
in uefi mode, and uefi by default has some way of making a choice
(either at boot time of through changing the boot order permanently)
GRUB is not strictly necessary for this to happen, but it can be used in
the mix. What would be very good to know, is, how is your firmware
manufactured and what does it allow? How does it cooperate?

If you want to get a better understanding of the UEFI boot process (with
or without grub), i recommend reading the documentation at
https://www.rodsbooks.com/linux-uefi/

good luck