[ale] Micro$oft blocking Linux booting in hardware

Michael H. Warfield mhw at WittsEnd.com
Fri Oct 21 12:43:09 EDT 2011


On Fri, 2011-10-21 at 12:18 -0400, Rich Faulkner wrote: 
> I have yet to read about this so may be chiming in too early but...

> 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.

I've been following the discussions in the forums and some of that has
centered around whether the vendors will be supply that functionality,
to disable or downgrade the secure boot, or not.  Microsoft has publicly
stated that they (the vendors) are not required to and they (MS) are not
requiring them to.  I'm not quite sure what you mean by lowering it in
priority?  "It" being what?  The secure boot?

> 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.

If by legacy BIOS you mean the old style BIOS, that may become more and
more difficult as newer hardware becomes available.  Much of this will
require the extensibility framework of the UEFI.  It gets even worse if
one of the OSs you want to use IS one that requires UEFI (Windows 8
going down the road of OS X?).

Looking at coreboot, FKA LinuxBIOS, may be beneficial but then there
will be the ability to flash a coreboot image into newer motherboards,
which tends to be problematical.

> Worth further reading online and originally developed by
> Intel as "The Framework" if memory serves....RinL

Yeah, UEFI is a framework that includes a Forth interpreter for plugin
extensions.  Lots of good information on some of that up at the coreboot
site.

Regards,
Mike

> On Fri, 2011-10-21 at 09:34 -0400, Derek Atkins wrote:
> 
> > Mike Harrison <cluon at geeklabs.com> writes:
> > 
> > > On Thu, 20 Oct 2011, Bob Toxen wrote:
> > >> http://www.fsf.org/campaigns/secure-boot-vs-restricted-boot/statement
> > >
> > > 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
> 
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo

-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  mhw at WittsEnd.com
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 482 bytes
Desc: This is a digitally signed message part
Url : http://mail.ale.org/pipermail/ale/attachments/20111021/62ba7153/attachment.bin 


More information about the Ale mailing list