Intel Planning To End Legacy BIOS Support By 2020

Chat about just about anything else
User avatar
Lucap
Level 5
Level 5
Posts: 650
Joined: Tue May 24, 2016 1:40 am

Intel Planning To End Legacy BIOS Support By 2020

Postby Lucap » Sun Nov 19, 2017 4:58 am

Intel Planning To End Legacy BIOS Support By 2020

https://www.phoronix.com/scan.php?page= ... S-EOL-2020

By 2020, they will be supporting no less than UEFI Class 3, which means only UEFI support and no more legacy BIOS or CSM compatibility support mode. But that's not going to force on UEFI Secure Boot unconditionally: Secure Boot enabled is considered UEFI Class 3+.

User avatar
Lucap
Level 5
Level 5
Posts: 650
Joined: Tue May 24, 2016 1:40 am

Re: Intel Planning To End Legacy BIOS Support By 2020

Postby Lucap » Sun Nov 19, 2017 5:20 am

Why has this been moved to open chat when it's was on topic of how Intel have no plans to comply with googles wish to remove Intels Minix and their EFi control?

If anyone is interested this topic is in reply to the criticism of their UEFi control that they will make it even harder in regards to how they wish a PC to be run.

viewtopic.php?f=60&t=256656

User avatar
Moem
Level 11
Level 11
Posts: 3965
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: Intel Planning To End Legacy BIOS Support By 2020

Postby Moem » Sun Nov 19, 2017 5:25 am

It's really a different subject and deserves to be discussed as such.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

michael louwe
Level 6
Level 6
Posts: 1179
Joined: Sun Sep 11, 2016 11:18 pm

Re: Intel Planning To End Legacy BIOS Support By 2020

Postby michael louwe » Sun Nov 19, 2017 5:56 am

UEFI technology came together with Secure Boot and was mostly initiated and implemented by M$ with all new OEM Win 8 computers in 2012. It replaced Legacy BIOS technology.

Legacy BIOS technology was based on an open platform and it is left to the users how to secure their BIOS, eg by setting a BIOS password. Computer dummies may ignorantly install infected bootable software from the Web, similar to computer dummies getting their OS infected by ignorantly clicking email attachments, downloading infected torrent files, visiting infected porn-sites, etc. There is no technology cure for 'stupid', eg Win 10 S or Secure Boot/UEFI or Windows Anti-virus programs, etc, cannot stop computer dummies from doing stupid things on the Web.
... I think UEFI/Secure Boot is just FUD for M$ to lock-down their desktop OS world marketshare by preventing or making it difficult for competing OS(especially Linux) to be self-installed by competent users.

No doubt, Legacy BIOS technology is lacking, eg limited to a tiny 16bit MBR Boot Partition, 4 Primary partitions and 2TB in disk size. The new UEFI technology is an improvement. But the way that UEFI and Secure Boot were implemented in 2012 smacked of securing world marketshare for M$ and certain OEMs(eg Intel).

Secure Boot requires a bootloader to be signed by M$'s Verisign before it can be installed and the certificate signing service costs about US$100 per year. Ubuntu, Fedora, LM, etc had to pay to get their EFI bootloaders signed or approved, supposedly as secure non-malware. Minor Linux distros who could not afford to pay this yearly signing fee to M$'s Verisign require Secure Boot to be disabled before their bootloaders can be installed.

Initially in 2012, M$ wanted Secure Boot to be permanently enabled on new OEM Windows computers but they backed down after much opposition from the tech industry and users. Certain Surface devices from M$ have Secure Boot permanently enabled, eg ARM-based Surface RT. M$ will soon be introducing ARM-based Win 10 Surface devices. Will Secure Boot in such devices be permanently enabled.?

With the 2015-released Win 10, M$ told the OEMs that it is up to their discretion whether they want to have Secure Boot permanently enabled. Seems, a few of the OEMs are trying to make Secure Boot permanently enabled for their new 2017 computers by not allowing non-Windows EFI bootloaders to be installed. After much complaints from consumers, the OEMs issued BIOS firmware updates to allow the booting of non-Windows EFI bootloaders.

Certain high-end OEM Win 8.x/10 computers, eg Acer, Asus and HP, have an obstructive or pro-M$ BIOS setting for "select an UEFI file as trusted for executing", ... https://itsfoss.com/no-bootable-device-found-ubuntu/ and [ viewtopic.php?t=236560 ]
... The above latest(= 2017) OEM laptops, eg Acer E and S series, may have even removed this BIOS setting(= "No bootable device" after installing Linux and cannot be fixed), but may be restored by a new BIOS firmware update from the OEMs... [ viewtopic.php?f=46&t=254948 ]

Most Surface devices already have UEFI permanently enabled, ie cannot use Legacy BIOS mode for OS installation, purportedly required because of the Connected Standby feature for mobile devices. So, beware.

Installing an OS in Legacy BIOS mode is much simpler than in UEFI mode, eg when reinstalling Windows in a dual-boot system = need to reinstall Grub or grub-efi-amd64.

So, the likely endgame for M$ and Intel is to abolish Legacy BIOS mode and have Secure Boot permanently enabled, so as to be able to permanently impose their Wintel oligopoly.

User avatar
Lucap
Level 5
Level 5
Posts: 650
Joined: Tue May 24, 2016 1:40 am

Re: Intel Planning To End Legacy BIOS Support By 2020

Postby Lucap » Sun Nov 19, 2017 6:10 am

michael louwe wrote:UEFI technology came together with Secure Boot and was mostly initiated and implemented by M$ with all new OEM Win 8 computers in 2012. It replaced Legacy BIOS technology.


Wrong it was intel......... :)

It started with Intel back in the 2002 or 2003 that wanted UEFI so they could take control of their future plans of the CPU and BIOS AMT remote function which has led to the current situation of the MiniX fiasco as it's also used in conjunction with their wish for TPM control.

20 Apr 2006
https://www.theregister.co.uk/2006/04/2 ... anta_rosa/

April 17, 2007
https://www.bit-tech.net/news/tech/uefi ... he_bios/1/

Microsoft simply does not currently support UEFI

michael louwe
Level 6
Level 6
Posts: 1179
Joined: Sun Sep 11, 2016 11:18 pm

Re: Intel Planning To End Legacy BIOS Support By 2020

Postby michael louwe » Sun Nov 19, 2017 7:14 am

@ Lucap, .......

Lucap wrote:.

.
Your bit-tech link is dated 2007 and UEFI technology was only fully implemented by M$ in 2012. A good up-to-date write-up about UEFI and Secure Boot is at ...
https://en.wikipedia.org/wiki/Unified_E ... _Interface

Like I said before, Legacy BIOS is a very old technology and needed to be replaced. Intel initiated UEFI as a replacement for their Itanium servers during the mid-1990s but it was M$ who "enforced" UEFI technonlogy and Secure Boot in 2012. UEFI technology is CPU-agnostic but Secure Boot is mostly controlled by M$ through signed certificates = not OS-agnostic.

The way that UEFI and Secure Boot were "enforced" by M$ has left a bitter taste among most non-Windows users. So, the main "culprit" here is M$, not Intel. Look at how M$ abolished Legacy BIOS technology and made Secure Boot permanently enabled in their Surface devices and some of their Signature Edition computers. It is only a matter of time before the other computer OEMs follow suit.

To some corporations and their IT Admins, UEFI's Remote Management feature at the boot level is useful(eg Intel ME/AMT/vPro), similar to the Windows Remote Desktop Protocol feature at the OS level. Even AMD chips offer the UEFI's Remote Management feature. Anyway, this remote access feature can be disabled by the users.


Return to “Open chat”