Either I am doing something wrong, or this doesn’t seem to be quite working.
When I run bootnetia64.efi from the debian-installer package I just get the GRUB prompt – no config was loaded. I can’t even manually load one with “configfile” since it doesn’t seem to be able to parse the partition table.
grub> ls
(hd0) (cd0)
When I run the GRUB that was installed by my previous OS installation (grubia64.efi), it does parse the HD partitions correctly
grub> ls
(hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cd0)
and, if I force the configfile to point at the debian-installer one, it does start installation correctly.
So, what’s the deal with bootnetia64.efi? Does it need to load all the mod files that are present in the “grub” directory in order to understand GPT partitions? If that’s the case, why is it not loading them? Do relative paths not work? In other words, does the debian-installer folder need to be on a specific, hardcoded, path within the EFI partition?
Thanks.
_____
Pedro