ATeal wrote:Is there a guide, a how to, something with clear instructions (this is not something I've ever had to do as I said, or anything like) on how to get it working, Secure boot cannot be disabled - first thing we checked for.
If it's an x86/x86-64 computer with a Windows 8 logo, then Secure Boot can
be disabled. The user interface might not be obvious (maybe it's behind a door marked "beware of the leopard"), but Microsoft requires that Secure Boot can be disabled on x86/x86-64 computers with Windows 8 logos. If it's an ARM-based computer, OTOH, Microsoft requires that Secure Boot can not
be disabled. On a computer like that, your best bet in the short term is to return it and make it clear why
it's being returned. I expect that a workaround will be available within a few months, but I can't promise that.
The only page I know of that provides anything resembling step-by-step instructions for dealing with Secure Boot is this page of mine
on the topic. It's still a little rough and unclear on a few points, though, because the relevant Linux software is still under development and because details vary greatly from one computer to another. You could also check out Matthew Garrett's blog.
He's a former Red Hat developer who wrote the Shim boot loader, which is Red Hat's/Fedora's tool for booting with Secure Boot active. SUSE and Ubuntu are apparently going to be using the same software, so it's starting to look like Shim will soon be semi-standard in the Linux community.
bigj231 wrote:On x86 systems, you can try EasyBCD.
No, EasyBCD is useful only on BIOS systems, according to its own FAQ.