On 8/10/20 2:53 PM, Carlos E.R. wrote:
On 10/08/2020 20.31, DennisG wrote:
On 8/10/20 1:55 PM, Carlos E. R. wrote:
On 10/08/2020 15.16, JJM de Faber wrote:
On 10-08-2020 15:06, Carlos E. R. wrote:
On 10/08/2020 14.02, Carlos E. R. wrote:
On Monday, 2020-08-10 at 13:37 +0200, Carlos E. R. wrote:
>> long snip
Thanks, but that doesn't solve the issue that something is changing what I write there, and trying to boot something else instead of openSUSE.
Just a wild guess . . . is it possible that device.map is the cuprit? If the grub install is incorrectly determining the boot order from its bios guess (when there is no device.map file) or there is an incorrect device.map file present, it is possible that the wrong location will be called. Or possibly grub2-mkconfig put an error in the grub.cfg file?
No device map in efi/grub.
My current culprit is either the BIOS is altering the list for some reason of its own, or some automatic process in openSUSE is doing it. There is no other explanation.
#1 seems the most probable, as when I edit the list in the BIOS itself, then it works. So the program "efibootmgr" is doing something the BIOS doesn't accept.
What I will do next is use a shorter name without the "_" char.
Another wild guess: Problem with filesystem labels or UUID's? Grub2-mkconfig uses one or the other of those to build grub.cfg.