Comment # 5 on bug 951962 from David Medina

I will provide this info as soon as I can. I am not at my computer right now.

One thing: remember that this has happened to me in three different systems,
not just on the AMD with the interchangeable disks, all with nothing installed
before, except the Intel desktop that fist had Opensuse in legacy mode. All
this hardware is just one and a half years old.

So:
>"openSUSE wouldn't overwrite it (bootx64.efi) if it exist before installation"

It didn't exist. On the AMD the installation was performed on a blank disk, so
there was no previously efi partition. 

In that system, I have found that I need to have the bootx64.efi entry in case
the bios doesn't want to boot the "distro's name" because I have changed the
disk. Debian only creates a "debian" entry, so I always create the "boot" one 
before powering off and change the disk and that's it. Then it never fails. But
I think this is not the point...

On the Intel desktop, back again with Opensuse in legacy mode now, I have
repeatedly permformed an EFI test installation on an external USB drive to see
if opensuse could be installed on its hard drive, in EFI mode. Same (bad)
result every time: I only can boot it with the help of refind. And it is not
that the hardware can not boot EFI, I have run this kind of test, for example,
with Fedora and Manjaro, and they booted fine. The screenshot I provided was of
this test with Opensuse. On the AMD it's exactly the same but with the 4.2
kernel because last week I bought a new disk. I will privide that as well...

Thanks,