<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
I have yet to read about this so may be chiming in too early but...<BR>
<BR>
If the issue is UEFI related all you have to do is disable that in the BIOS or lower it in priority of the boot sequence so that it doesn't invoke. Flash a legacy BIOS (if available as well) but keep in mind that EFI/UEFI are standards that allow you to make your own pre-boot environment. Worth further reading online and originally developed by Intel as "The Framework" if memory serves....RinL<BR>
<BR>
<BR>
On Fri, 2011-10-21 at 09:34 -0400, Derek Atkins wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Mike Harrison <<A HREF="mailto:cluon@geeklabs.com">cluon@geeklabs.com</A>> writes:
> On Thu, 20 Oct 2011, Bob Toxen wrote:
>> <A HREF="http://www.fsf.org/campaigns/secure-boot-vs-restricted-boot/statement">http://www.fsf.org/campaigns/secure-boot-vs-restricted-boot/statement</A>
>
> Done.
>
> Remember the real vote is with your wallet. Support the hardware
> manufacturers that support your choice in OS. Which, while it goes
> without saying, they usually have little knowledge that you are using
> their hardware with Linux. As a group, we tend to just "make it work",
> It helps a lot to let the manufacturer and/or retailer know you
> bought it because it works with Linux.
my understanding is that there would be a BIOS switch to turn this off.
-derek
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>