Difference between revisions of "Unified Extensible Firmware Interface/Hardware"

From ArchWiki
Jump to: navigation, search
m (Add Link to Wikipedia ''Atom (system on chip)" page)
(25 intermediate revisions by 7 users not shown)
Line 29: Line 29:
 
=== Lenovo ThinkPad x121e ===
 
=== Lenovo ThinkPad x121e ===
  
==== Required info ====
+
# Model: Lenovo ThinkPad x121e 3045CTO
 
+
# Processor: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel
# System OEM/Vendor (like Dell, HP, Lenovo etc.) and Model (like ThinkPad x121e etc.) - all info needed
+
# BIOS/UEFI vendor: Phoenix SecureCore Tiano
#* Lenovo ThinkPad x121e 3045CTO
+
# Could create a working entry in UEFI Boot menu using efibootmgr.
# Processor with the model number (full info like Intel Core i7 xxxx 1.8 GHz - for eg.)
+
# Have not managed to launch UEFI shell.
#* Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel
+
# Filesystem of UEFI System Partition : FAT16. FAT32 does ''NOT'' work. More info at https://bbs.archlinux.org/viewtopic.php?id=131149.
# Chipset info (Intel P67 or H67 etc.)
+
#* Still not sure how to identify this (see original thread for a couple of possibilities!)
+
# Motherboard with full model number - required if desktop, optional for laptop
+
#* N/A
+
# BIOS/UEFI vendor - AMI Aptio, Phoenix SecureCore Tiano, Insyde H2O etc. (very important) with updated month/year (will be shown as copyright year in some firmwares)
+
#* On original install:
+
#** Phoenix SecureCore Tiano
+
#** Date: 10/25/2011
+
#** Vendor: LENOVO
+
#** Version: 8QET53WW (1.14 )
+
#* After BIOS update:
+
#** Date: 01/11/2012
+
#** Version: 8QET54WW (1.15 )
+
# Were you able to create a working entry in UEFI Boot menu using efibootmgr? Any specific issues like black screen or something like http://forum-en.msi.com/index.php?topic=153411.0 ?
+
#* Yes. No.
+
# If you were able to launch the UEFI Shell in ways other than using {{ic|(USB)/efi/boot/bootx64.efi}} or Archboot, how?
+
#* Have not managed to launch UEFI shell...
+
# Output of UEFI Shell "ver" command.
+
#* See previous answer.
+
# If efibootmgr did not work for you and you were able to launch UEFI Shell, did you use bcfg command to create UEFI Boot Menu entry? Did bcfg created boot entry work for you?
+
#* N/A
+
# Filesystem of UEFI System Partition? FAT32 or FAT16? (Mostly it should be FAT32 but some firmwares have problems with it, which is a violation of UEFI Spec.)
+
#* FAT16. FAT32 does ''NOT'' work.
+
#* More info at https://bbs.archlinux.org/viewtopic.php?id=131149.
+
  
 
==== Additional notes ====
 
==== Additional notes ====
Line 65: Line 41:
 
* Cannot get it to boot from a GPT disk in BIOS mode.
 
* Cannot get it to boot from a GPT disk in BIOS mode.
 
* I did not try archboot.
 
* I did not try archboot.
----
 
  
 
=== Intel DZ77GA-70K ===
 
=== Intel DZ77GA-70K ===
Line 99: Line 74:
 
# Any graphics/video card issues that occur in UEFI boot alone and not in BIOS boot? Like Nvidia closed-source driver's lack of Kernel Mode Setting etc.
 
# Any graphics/video card issues that occur in UEFI boot alone and not in BIOS boot? Like Nvidia closed-source driver's lack of Kernel Mode Setting etc.
 
#* Kernel hangs after attempting to boot, no graphics output after changing to the kernel. Graphics output before that is fine.
 
#* Kernel hangs after attempting to boot, no graphics output after changing to the kernel. Graphics output before that is fine.
 +
 +
==== Additional notes ====
 +
More info at [https://bbs.archlinux.org/viewtopic.php?id=146990 archlinux forums] and [http://unix.stackexchange.com/questions/45312/how-can-i-tell-if-i-have-a-bug-with-my-kernel-or-with-my-bios-firmware stack overflow]. Similar problems with [http://comments.gmane.org/gmane.linux.redhat.fedora.devel/167170 a different motherboard]. Seems to be a buggy uefi implementation by intel.
 +
 +
mihanson on '''2013-07-21''': tried with latest BIOS, version 0066, and the results are the same as the above.  No go in UEFI mode on the Intel DZ77GA-70K.
 
----
 
----
 +
 
=== Asus M5A99X EVO ===
 
=== Asus M5A99X EVO ===
 
# System OEM/Vendor
 
# System OEM/Vendor
Line 122: Line 103:
 
#* No
 
#* No
  
==== Additional notes ====
+
----
More info at [https://bbs.archlinux.org/viewtopic.php?id=146990 archlinux forums] and [http://unix.stackexchange.com/questions/45312/how-can-i-tell-if-i-have-a-bug-with-my-kernel-or-with-my-bios-firmware stack overflow]. Similar problems with [http://comments.gmane.org/gmane.linux.redhat.fedora.devel/167170 a different motherboard]. Seems to be a buggy uefi implementation by intel.
+
 
 +
=== Lenovo Thinkpad Edge E430 3254-DAQ ===
 +
 
 +
The below information was added by user [[User:The.ridikulus.rat]] .
 +
 
 +
==== System Info ====
 +
 
 +
# [[Lenovo_ThinkPad_Edge_E430|Lenovo Thinkpad Edge E430]] 3254-DAQ (India)
 +
# Intel Core i5 3210M 2.50 GHz (3rd Gen aka Ivy Bridge), 4 GB DDR3 RAM
 +
# Intel HM77 Express Chipset
 +
# UEFI Firmware Vendor : Phoenix SecureCore Tiano
 +
# UEFI/BIOS Version : [http://support.lenovo.com/en_IN/downloads/detail.page?DocID=DS033265 H0ET91WW] (2.51)
 +
# Embedded Controller Version : H0HT91WW (2.51)
 +
# UEFI Specification/Revision : 2.31 (ie. 2.3.1)
 +
# Lenovo UEFI/BIOS Build Date : 01-APR-2013
 +
# External Ports: 3 USB 3.0, 1 USB 2.0, 1 VGA, 1 HDMI, 1 RJ45 Ethernet/LAN port (Realtek), 1 ExpressCard 34 port, 1 3.5mm Headphones jack
 +
# 1 Tray-Load CD/DVD Writer
 +
# Switchable Graphics : Intel HD Graphics 4000 and Nvidia GeForce 610M (1GB Dedicated RAM)
 +
# WiFi / WLAN Card : Intel Centrino Wireless-N 2230 (B/G/N + Bluetooth 4.0)
 +
 
 +
==== Observations ====
 +
 +
# UEFI Secure Boot support is present in firmware, but I have currently disabled it. System came pre-installed with Windows 7 Pro x64 in BIOS-MBR mode, with BIOS version 1.14 (which did not include UEFI Secure Boot).
 +
# After BIOS update, all boot entries got erased and I had to recreate them using efibootmgr.
 +
# Using a 1 GiB FAT32 UEFISYS partition (/dev/sda1) mounted at /boot/efi (i.e. separate from /boot). Kernel and initramfs files synced during update using [[UEFI_Bootloaders#Sync_EFISTUB_Kernel_in_UEFISYS_partition_using_Systemd]].
 +
# No issues with efibootmgr for creating entries for rEFInd and GRUB 2.x . But unable to create direct EFISTUB entries as described at [[UEFI_Bootloaders#Using_efibootmgr_entry]] (echo'ed kernel parameters are truncated by efibootmgr).
 +
# Currently using rEFInd (textonly mode) as main boot manager (1st in boot menu) with grub-efi-x86_64 (2nd in boot menu) and grub-bios installed as fallback. rEFInd is first in boot menu (installed at {{ic|<UEFISYS>/EFI/refind/refindx64.efi}}). No need for {{ic|/EFI/Microsoft/Boot/bootmgfw.efi}} hack. Dual-booting Windows 8 Pro x64 UEFI-GPT (chainloaded from rEFInd/GRUB) works without any issues. Windows boot files are stored in same UEFISYS partition.
 +
# Both UEFI Shell v2 and v1 work, launched from rEFInd or grub-efi-x86_64. No option in the firmware setup/menu to directly launch the shell.
 +
# Currently using only intel and nouveau drivers. Haven't yet tried nvidia binary drivers and bumblebee graphics switching support. Kernel Mode Setting enabled.
 +
# grub-bios works if the firmware is changed to boot "Legacy only" without any boot/active flag in 0xEE Protective MBR partition entry.
 +
# Gummiboot v8 works fine without any errors.
 +
# Using only PARTUUID in /etc/fstab and in bootloader config files.
 +
 
 +
==== Important Info ====
 +
 
 +
I didn't use Archiso or Archboot to install the system. I transferred the Arch installation from my old Sony Vaio laptop to my new Thinkpad E430 using an external USB HDD and rsync from within SystemRescueCD, after manually creating the partitions using GParted, and then manually setup fstab and rEFInd. After that I rebooted into Arch and installed grub-efi-x86_64 and grub-bios.
 +
 
 +
======From WonderWoofy======
 +
 
 +
On an E430-3254(CTO) I had the same issues as the.ridikulus.rat with efibootmgr and truncated kerl command line parameters.  This usually lead to the inability of the kernel to find the initramfs. What I ended up doing is putting the kernel and intramfs in the root of the ESP, and from there the efibootmgr entries worked nicely.  This does lead to an ESP that is not organized in the recommended way though.
 +
 
 +
Also, I did actually install via Archboot, and all worked fine. I have actually installed twice on this machine, once to a Momentus XT and once to a Samsung 830.  The first time I used a CD, and therefore selected the "UEFI First" preference in the bios.  This supposedly will try UEFI (\EFI\boot\bootx64.efi) first, and if that fails it will look to the MBR.  Unfortunately, it did not honor this setting for the optical drive, and I had to turn off legacy bios mode entirely to get it to boot in UEFI from the CD.  Interestingly, this "UEFI First" setting works just fine for interal drives. USB flash drives are a whole different story though, and more information can be found [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#Create_UEFI_bootable_USB_from_ISO here].
 +
----
 +
 
 +
=== System76 Galago UltraPro ===
 +
 
 +
==== System Info ====
 +
 
 +
* System76 Galago UltraPro (Clevo W740SU)
 +
* intel core i7 4750HQ 2.0GHz
 +
* intel HM87 Chipset
 +
* Original firmware version unknown, but from American Megatrends Inc.
 +
* Boot in UEFI mode only possible by starting an UEFI shell via the BIOS setup ({{ic|$esp/shellx64.efi}})
 +
* UEFI menu entries could be created by using efibootmgr, but without them being shown in the bootup menu
 +
* ESP filesystem: FAT32
 +
* '''Note:''' UEFI boot is not officially supported by System76
 +
 
 +
==== Fix ====
 +
 
 +
* Download the Clevo W740SU firmware from [http://repo.palkeo.com/clevo-mirror/W740SU/].
 +
* Flash it using any FreeDOS live medium
 +
* The new firmware is from American Megatrends Inc. V.4.6.5 08/13/2013
 +
* The new firmware doesn't support mixed BIOS and UEFI support, so you have to manually switch if you want to boot from a medium that doesn't support UEFI.
 +
----
 +
 
 +
=== Intel Atom System-on-Chip ===
 +
 
 +
Intel Atom System-on-Chip (SoC) is the Intel's answer to ARM SoC, primarily targeting Smartphones and Tablets (not regular Desktop and Notebook PCs).
 +
 
 +
{{Note|This section was written based on information available online, not based on experience by an actual user of any Intel Atom SoC system.}}
 +
 
 +
{{Note|Intel Atom SoC systems that ship with Windows 8/8.1 32-bit provide 32-bit UEFI-only firmware with no BIOS compatibility option (no CSM). In UEFI terms these systems are called Class 3 systems (this term is not specific to 32-bit), ie. UEFI-only with no BIOS CSM. These Atom SoC systems are therefore called as 32-bit UEFI Class 3 systems, and these can be booted only using a 32-bit UEFI bootable USB, which is not provided by default in [[Archiso]] (official install iso) and [[Archboot]]. These systems also come with UEFI Secure Boot enabled by default, but the firmware setup provides option(s) to disable Secure Boot as mandated by Microsoft for x86 systems.}}
 +
 
 +
'''Related Links:'''
 +
* [[Wikipedia:Atom (system on chip)]]
 +
 
 +
==== MinnowBoard ====
 +
 
 +
The MinnowBoard is an Intel Atom SoC based board similar to Raspberry Pi or BeagleBoard. It ships with [http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Welcome Tianocore UDK] based 32-bit UEFI-only firmware which does not contain CSM support (no Legacy BIOS boot). The embedded Atom processor is supports only 32-bit, hence it is not possible to replace the 32-bit UEFI in the board with 64-bit (x86_64) UEFI. See below links for more info.
 +
 
 +
'''Related Links:'''
 +
* http://www.minnowboard.org/
 +
* http://www.elinux.org/MinnowBoard
 +
* http://uefidk.intel.com/content/minnowboard-uefi-firmware
 +
 
 +
==== Intel Atom SoC Clover Trail ====
 +
 
 +
Intel Atom SoC Clover Trail processors are 32-bit only, hence they contain only 32-bit UEFI firmware. Officially Intel has stated that Linux will not be supported in Clover Trail tablets. Apart from this, Intel has not released the Clover Trail power-management and (PowerVR based) graphics code for Linux. Hence these systems may not work reliably with Linux.
 +
 
 +
'''Related Links:'''
 +
* http://download.lenovo.com/luc/dml/Tablet2_Imaging_considerations.pdf
 +
* http://arstechnica.com/information-technology/2012/09/intel-declares-clover-trail-atom-processor-a-no-linux-zone/
 +
 
 +
==== Intel Atom SoC Bay Trail ====
 +
 
 +
Intel Atom SoC Bay Trail processors actually support 64-bit, but these tablets ship with only Windows 8/8.1 32-bit (not 64-bit) because of a feature called '''Connected Standby''' which is mandated by Microsoft to be enabled, but currently supported only by Windows 8/8.1 32-bit version (not 64-bit, as of October 2013). '''Connected Standby''' requirements (by Microsoft) include tablets to support only UEFI boot (hence no BIOS CSM) and UEFI bitness to match the OS bitness (hence 32-bit UEFI for sake of Win 8/8.1 32-bit). With only 32-bit UEFI and lack of BIOS compatibility, even Windows XP/Vista/7 32-bit (no UEFI support) and 64-bit (cannot boot in 32-bit UEFI) cannot be installed in these systems. These systems are truly locked to Windows 8/8.1 32-bit (UEFI mode).
 +
 
 +
In these systems it should (theoretically) be possible to install 64-bit Linux provided the kernel is instructed to not access EFI runtime code using the '''noefi''' kernel parameter, due to the kernel/UEFI bitness mismatch. Unlike Clover Trail, Intel has stated that Bay Trail will support Android (which is based on Linux), and its graphics is based on Intel HD graphics (not PowerVR). Therefore, Bay Trail systems may work better with Linux compared to Clover Trail.
 +
 
 +
'''Related Links:'''
 +
* [[Wikipedia:Connected Standby]]
 +
* http://www.pcworld.com/article/2048599/windows-81-tablets-with-64bit-atom-chips-not-coming-until-q1.html

Revision as of 11:49, 5 November 2013

Required info

  1. System OEM/Vendor (like Dell, HP, Lenovo etc.) and Model (like ThinkPad x121e etc.) - all info needed
  2. Processor with the model number (full info like Intel Core i7 xxxx 1.8 GHz - for eg.)
  3. Chipset info (Intel P67 or H67 etc.)
  4. Motherboard with full model number - required if desktop, optional for laptop
  5. BIOS/UEFI vendor - AMI Aptio, Phoenix SecureCore Tiano, Insyde H2O etc. (very important) with updated month/year (will be shown as copyright year in some firmwares)
  6. Were you able to create a working entry in UEFI Boot menu using efibootmgr? Any specific issues like black screen or something like http://forum-en.msi.com/index.php?topic=153411.0 ?
  7. If you were able to launch the UEFI Shell in ways other than using (USB)/efi/boot/bootx64.efi or Archboot, how?
  8. Output of UEFI Shell "ver" command.
  9. If efibootmgr did not work for you and you were able to launch UEFI Shell, did you use bcfg command to create UEFI Boot Menu entry? Did bcfg created boot entry work for you?
  10. Filesystem of UEFI System Partition? FAT32 or FAT16? (Mostly it should be FAT32 but some firmwares have problems with it, which is a violation of UEFI Spec.)
  11. Any graphics/video card issues that occur in UEFI boot alone and not in BIOS boot? Like Nvidia closed-source driver's lack of Kernel Mode Setting etc.
Note: In any user discussion in irc , forum or mailing lists etc. regarding UEFI, add your system info here and link to this page in the discussion to help solve the issue(s) quickly.

Original Post: https://bbs.archlinux.org/viewtopic.php?id=133074.


Lenovo ThinkPad t420s

  • intel core i7 2640M 2.80GHz
  • Phoenix SecureCore Tiano, 2011
  • UEFI bios version 8CET51WW (1.31), dated 2011-11-29
  • efibootmgr can create entries in menu just fine. looks good.
  • FAT32

Lenovo ThinkPad x121e

  1. Model: Lenovo ThinkPad x121e 3045CTO
  2. Processor: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel
  3. BIOS/UEFI vendor: Phoenix SecureCore Tiano
  4. Could create a working entry in UEFI Boot menu using efibootmgr.
  5. Have not managed to launch UEFI shell.
  6. Filesystem of UEFI System Partition : FAT16. FAT32 does NOT work. More info at https://bbs.archlinux.org/viewtopic.php?id=131149.

Additional notes

  • Works fine with MBR partition map in BIOS mode.
  • Also works fine with GPT partition map in UEFI mode but ONLY if the EFI partition is formatted as fat 16.
  • Cannot get it to boot from a GPT disk in BIOS mode.
  • I did not try archboot.

Intel DZ77GA-70K

  1. System OEM/Vendor (like Dell, HP, Lenovo etc.) and Model (like ThinkPad x121e etc.) - all info needed
    • Intel DZ77GA-70K
  2. Processor with the model number (full info like Intel Core i7 xxxx 1.8 GHz - for eg.)
    • Intel Core i7 3770K
  3. Chipset info (Intel P67 or H67 etc.)
    • Z77
  4. Motherboard with full model number - required if desktop, optional for laptop
    • Intel DZ77GA-70K
  5. BIOS/UEFI vendor - AMI Aptio, Phoenix SecureCore Tiano, Insyde H2O etc. (very important) with updated month/year (will be shown as copyright year in some firmwares)
    • (from hardinfo, under a bios boot)
 -BIOS-
  Date		: 07/13/2012
  Vendor		: Intel Corp. (www.intel.com)
  Version		: GAZ7711H.86A.0049.2012.0713.1518
 -Board-
  Name		: DZ77GA-70K
  Vendor		: Intel Corporation (www.intel.com)
  1. Were you able to create a working entry in UEFI Boot menu using efibootmgr? Any specific issues like black screen or something like http://forum-en.msi.com/index.php?topic=153411.0 ?
    • No. Linux cannot boot through uefi on this motherboard, with this bios revision.
  2. If you were able to launch the UEFI Shell in ways other than using (USB)/efi/boot/bootx64.efi or Archboot, how?
    • No, however bootx64.efi works, archboot does not.
  3. Output of UEFI Shell "ver" command.
 UEFI Interactive Shell v2.0
 Copyright 2009-2011 Intel(r) Corporation. All rights reserved. Beta build 1.0
 UEFI v2.31 (American Megatrends, 0x0004028D)
  1. If efibootmgr did not work for you and you were able to launch UEFI Shell, did you use bcfg command to create UEFI Boot Menu entry? Did bcfg created boot entry work for you?
    • booting through bcfg produced the same results as booting from the shell, didn't work.
  2. Filesystem of UEFI System Partition? FAT32 or FAT16? (Mostly it should be FAT32 but some firmwares have problems with it, which is a violation of UEFI Spec.)
    • Both FAT32 and FAT16 do not work.
  3. Any graphics/video card issues that occur in UEFI boot alone and not in BIOS boot? Like Nvidia closed-source driver's lack of Kernel Mode Setting etc.
    • Kernel hangs after attempting to boot, no graphics output after changing to the kernel. Graphics output before that is fine.

Additional notes

More info at archlinux forums and stack overflow. Similar problems with a different motherboard. Seems to be a buggy uefi implementation by intel.

mihanson on 2013-07-21: tried with latest BIOS, version 0066, and the results are the same as the above. No go in UEFI mode on the Intel DZ77GA-70K.


Asus M5A99X EVO

  1. System OEM/Vendor
    • Asus M5A99X EVO
  2. Processor with the model number
    • AMD FX(tm)-8150 Eight-Core Processor
  3. Chipset info
    • AMD 990X/SB950
  4. BIOS/UEFI vendor
  Vendor: American Megatrends Inc.
  Version: 0901
  Release Date: 12/02/2011
  1. Were you able to create a working entry in UEFI Boot menu using efibootmgr?
    • Yes
  2. If you were able to launch the UEFI Shell in ways other than using (USB)/efi/boot/bootx64.efi
    • Yes, option in the Exit menu of the UEFI BIOS "Launch UEFI from system partition"
  3. Output of UEFI Shell "ver" command.
    • To be updated
  4. Filesystem of UEFI System Partition? FAT32 or FAT16?
    • FAT32
  5. Any graphics/video card issues that occur in UEFI boot alone and not in BIOS boot? Like Nvidia closed-source driver's lack of Kernel Mode Setting etc.
    • No

Lenovo Thinkpad Edge E430 3254-DAQ

The below information was added by user User:The.ridikulus.rat .

System Info

  1. Lenovo Thinkpad Edge E430 3254-DAQ (India)
  2. Intel Core i5 3210M 2.50 GHz (3rd Gen aka Ivy Bridge), 4 GB DDR3 RAM
  3. Intel HM77 Express Chipset
  4. UEFI Firmware Vendor : Phoenix SecureCore Tiano
  5. UEFI/BIOS Version : H0ET91WW (2.51)
  6. Embedded Controller Version : H0HT91WW (2.51)
  7. UEFI Specification/Revision : 2.31 (ie. 2.3.1)
  8. Lenovo UEFI/BIOS Build Date : 01-APR-2013
  9. External Ports: 3 USB 3.0, 1 USB 2.0, 1 VGA, 1 HDMI, 1 RJ45 Ethernet/LAN port (Realtek), 1 ExpressCard 34 port, 1 3.5mm Headphones jack
  10. 1 Tray-Load CD/DVD Writer
  11. Switchable Graphics : Intel HD Graphics 4000 and Nvidia GeForce 610M (1GB Dedicated RAM)
  12. WiFi / WLAN Card : Intel Centrino Wireless-N 2230 (B/G/N + Bluetooth 4.0)

Observations

  1. UEFI Secure Boot support is present in firmware, but I have currently disabled it. System came pre-installed with Windows 7 Pro x64 in BIOS-MBR mode, with BIOS version 1.14 (which did not include UEFI Secure Boot).
  2. After BIOS update, all boot entries got erased and I had to recreate them using efibootmgr.
  3. Using a 1 GiB FAT32 UEFISYS partition (/dev/sda1) mounted at /boot/efi (i.e. separate from /boot). Kernel and initramfs files synced during update using UEFI_Bootloaders#Sync_EFISTUB_Kernel_in_UEFISYS_partition_using_Systemd.
  4. No issues with efibootmgr for creating entries for rEFInd and GRUB 2.x . But unable to create direct EFISTUB entries as described at UEFI_Bootloaders#Using_efibootmgr_entry (echo'ed kernel parameters are truncated by efibootmgr).
  5. Currently using rEFInd (textonly mode) as main boot manager (1st in boot menu) with grub-efi-x86_64 (2nd in boot menu) and grub-bios installed as fallback. rEFInd is first in boot menu (installed at <UEFISYS>/EFI/refind/refindx64.efi). No need for /EFI/Microsoft/Boot/bootmgfw.efi hack. Dual-booting Windows 8 Pro x64 UEFI-GPT (chainloaded from rEFInd/GRUB) works without any issues. Windows boot files are stored in same UEFISYS partition.
  6. Both UEFI Shell v2 and v1 work, launched from rEFInd or grub-efi-x86_64. No option in the firmware setup/menu to directly launch the shell.
  7. Currently using only intel and nouveau drivers. Haven't yet tried nvidia binary drivers and bumblebee graphics switching support. Kernel Mode Setting enabled.
  8. grub-bios works if the firmware is changed to boot "Legacy only" without any boot/active flag in 0xEE Protective MBR partition entry.
  9. Gummiboot v8 works fine without any errors.
  10. Using only PARTUUID in /etc/fstab and in bootloader config files.

Important Info

I didn't use Archiso or Archboot to install the system. I transferred the Arch installation from my old Sony Vaio laptop to my new Thinkpad E430 using an external USB HDD and rsync from within SystemRescueCD, after manually creating the partitions using GParted, and then manually setup fstab and rEFInd. After that I rebooted into Arch and installed grub-efi-x86_64 and grub-bios.

From WonderWoofy

On an E430-3254(CTO) I had the same issues as the.ridikulus.rat with efibootmgr and truncated kerl command line parameters. This usually lead to the inability of the kernel to find the initramfs. What I ended up doing is putting the kernel and intramfs in the root of the ESP, and from there the efibootmgr entries worked nicely. This does lead to an ESP that is not organized in the recommended way though.

Also, I did actually install via Archboot, and all worked fine. I have actually installed twice on this machine, once to a Momentus XT and once to a Samsung 830. The first time I used a CD, and therefore selected the "UEFI First" preference in the bios. This supposedly will try UEFI (\EFI\boot\bootx64.efi) first, and if that fails it will look to the MBR. Unfortunately, it did not honor this setting for the optical drive, and I had to turn off legacy bios mode entirely to get it to boot in UEFI from the CD. Interestingly, this "UEFI First" setting works just fine for interal drives. USB flash drives are a whole different story though, and more information can be found here.


System76 Galago UltraPro

System Info

  • System76 Galago UltraPro (Clevo W740SU)
  • intel core i7 4750HQ 2.0GHz
  • intel HM87 Chipset
  • Original firmware version unknown, but from American Megatrends Inc.
  • Boot in UEFI mode only possible by starting an UEFI shell via the BIOS setup ($esp/shellx64.efi)
  • UEFI menu entries could be created by using efibootmgr, but without them being shown in the bootup menu
  • ESP filesystem: FAT32
  • Note: UEFI boot is not officially supported by System76

Fix

  • Download the Clevo W740SU firmware from [1].
  • Flash it using any FreeDOS live medium
  • The new firmware is from American Megatrends Inc. V.4.6.5 08/13/2013
  • The new firmware doesn't support mixed BIOS and UEFI support, so you have to manually switch if you want to boot from a medium that doesn't support UEFI.

Intel Atom System-on-Chip

Intel Atom System-on-Chip (SoC) is the Intel's answer to ARM SoC, primarily targeting Smartphones and Tablets (not regular Desktop and Notebook PCs).

Note: This section was written based on information available online, not based on experience by an actual user of any Intel Atom SoC system.
Note: Intel Atom SoC systems that ship with Windows 8/8.1 32-bit provide 32-bit UEFI-only firmware with no BIOS compatibility option (no CSM). In UEFI terms these systems are called Class 3 systems (this term is not specific to 32-bit), ie. UEFI-only with no BIOS CSM. These Atom SoC systems are therefore called as 32-bit UEFI Class 3 systems, and these can be booted only using a 32-bit UEFI bootable USB, which is not provided by default in Archiso (official install iso) and Archboot. These systems also come with UEFI Secure Boot enabled by default, but the firmware setup provides option(s) to disable Secure Boot as mandated by Microsoft for x86 systems.

Related Links:

MinnowBoard

The MinnowBoard is an Intel Atom SoC based board similar to Raspberry Pi or BeagleBoard. It ships with Tianocore UDK based 32-bit UEFI-only firmware which does not contain CSM support (no Legacy BIOS boot). The embedded Atom processor is supports only 32-bit, hence it is not possible to replace the 32-bit UEFI in the board with 64-bit (x86_64) UEFI. See below links for more info.

Related Links:

Intel Atom SoC Clover Trail

Intel Atom SoC Clover Trail processors are 32-bit only, hence they contain only 32-bit UEFI firmware. Officially Intel has stated that Linux will not be supported in Clover Trail tablets. Apart from this, Intel has not released the Clover Trail power-management and (PowerVR based) graphics code for Linux. Hence these systems may not work reliably with Linux.

Related Links:

Intel Atom SoC Bay Trail

Intel Atom SoC Bay Trail processors actually support 64-bit, but these tablets ship with only Windows 8/8.1 32-bit (not 64-bit) because of a feature called Connected Standby which is mandated by Microsoft to be enabled, but currently supported only by Windows 8/8.1 32-bit version (not 64-bit, as of October 2013). Connected Standby requirements (by Microsoft) include tablets to support only UEFI boot (hence no BIOS CSM) and UEFI bitness to match the OS bitness (hence 32-bit UEFI for sake of Win 8/8.1 32-bit). With only 32-bit UEFI and lack of BIOS compatibility, even Windows XP/Vista/7 32-bit (no UEFI support) and 64-bit (cannot boot in 32-bit UEFI) cannot be installed in these systems. These systems are truly locked to Windows 8/8.1 32-bit (UEFI mode).

In these systems it should (theoretically) be possible to install 64-bit Linux provided the kernel is instructed to not access EFI runtime code using the noefi kernel parameter, due to the kernel/UEFI bitness mismatch. Unlike Clover Trail, Intel has stated that Bay Trail will support Android (which is based on Linux), and its graphics is based on Intel HD graphics (not PowerVR). Therefore, Bay Trail systems may work better with Linux compared to Clover Trail.

Related Links: