On Mon 06 Dec 2021 at 10:56:29 (+0100), fran...@libero.it wrote: > unfortunately, nothing David suggested worked,
Yes, that happens, usually because the initial conditions were different from those assumed. Eg, Grub could have been in a different state, as the commands I was using are typically in response to a Grub> prompt, rather than a Grub Rescue> prompt. I'm also not certain what results from a failure to load normal.mod. But most importantly, without being told what /you/ do (not what I said to do), and without the responses, it's very difficult to help any further. For example, in your original post, there was no explanation of how you came by having a BIOS Boot partition. Which Howto did you follow that encouraged you to create it? Knowing that might well have helped others explain what your problem was, were we able to read what the entire intended strategy was. > so I finally set it on in the bios Legacy (via F12) and then reinstalled > Debian. > > Now if I turn on, Grub appears with Debian that starts (even if it takes a > while to boot) and if I want to use Windows, at boot, I have to click F12 and > select boot with UEFI and then Windows 10 starts. > > I tried to install os-prober on Debian, but it is already installed and doing > update-grub, but Windows is not shown (Probably because it is inserted in the > UEFI boot). > > Is there any way to fix this mess? That depends how often you switch between Windows and Debian. If it's infrequent, then you can just call it a feature. I did that for over a year with a bread-winning Windows installation that I was not willing to touch. If not, then you need to retry installing Debian in UEFI mode while making copious notes. Cheers, David.
