I am not at all familiar with Uefi workings, so the following comment is neither a solution nor even a theory, simply a question for others that are familiar with Uefi to consider.
I see that in my /boot/efi folder I have the following files: ls -l /boot/efi/EFI/Microsoft/Boot/ total 480 -rwxr-xr-x 1 root root 122880 Nov 24 12:01 bootmgfw.efi* -rwxr-xr-x 1 root root 122880 Nov 24 12:01 bootmgfw.efi.grb* -rwxr-xr-x 1 root root 122880 Nov 24 12:01 bootx64.efi* -rwxr-xr-x 1 root root 122880 Nov 24 12:01 bootx64.efi.grb* So the question is why have I got Microsoft files in my /boot/efi folder when I have no Microsoft installation, and could this have any bearing on this bug? One thing is obvious, the only thing that can have put them there is Ubiquity. Bear in mind that I used the 'Replace Windows' option to install Ubuntu, not 'Install alongside'. Given that, then Ubiquity really has no need to create such files. Obviously dual booters would probably find these files very necessary but not anyone who is completely removing Windows. The thought springs to mind that these might be some sort of signatures required to implement 'Secure Boot'. But since my machine does not support 'Secure Boot' again they are surely unnecessary. I can't read the files (hex?) so I don't know what is in them. Anyway it is just something for you to think about, I might be very wide of the mark in believing this has anything to do with the basic problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubiquity/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
