03-14-2013
11:41 AM
- last edited on
03-06-2024
08:12 PM
by
ROGBot
http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Booting wrote:
The UEFI specification defines a "boot manager", a firmware policy engine that is in charge of loading the
OS loader and all necessary drivers. The boot configuration is controlled by a set of global NVRAM variables,
including boot variables that indicate the paths to the loaders.
OS loaders are a class of UEFI applications. As such, they are stored as files on a file system that can be
accessed by the firmware. Supported file systems include FAT32, FAT16 and FAT12. Supported partition table
schemes include MBR and GPT. UEFI does not rely on a boot sector.
Boot loaders can also be auto-detected by firmware, to enable booting on removable devices. Auto-detection
relies on a standardized file path to the OS loader, depending on the actual architecture to boot
(\EFI\BOOT\BOOT[architecture name].EFI, e.g. \EFI\BOOT\BOOTx64.EFI).
It is common for UEFI firmware to include a user interface to the boot manager, to allow the user to select
and load the operating system among the possible options.
http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Secure_boot wrote:
The UEFI 2.2 specification adds a protocol known as Secure boot, which can secure the boot process by
preventing the loading of drivers or OS loaders that are not signed with an acceptable digital signature.
When secure boot is enabled, it is initially placed in "Setup" mode, which allows a public key known as
the "Platform key" (PK) to be written to the firmware. Once the key is written, secure boot enters "User"
mode, where only drivers and loaders signed with the platform key can be loaded by the firmware. Additional
"Key Exchange Keys" (KEK) can be added to a database stored in memory to allow other certificates to be
used, but they must still have a connection to the private portion of the Platform key. Secure boot can
also be placed in "Custom" mode, where additional public keys can be added to the system that do not match
the private key.
http://wiki.phoenix.com/wiki/index.php/Compatibility_Support_Module wrote:
The CSM provides additional functionality to UEFI. This additional functionality permits the loading of
a traditional OS or the use of a traditional OpROM.
The CSM operates in two distinct environments:
Booting a traditional or non-EFI-aware OS.
Loading a UEFI-aware OS a device that is controlled by a traditional Option ROM.
The first operation, booting a traditional or non-EFI-aware OS, is the traditional environment.
It is expected that traditional OpROMs will be around long after traditional OSs have been replaced
by EFI-aware OSs. The code that is required to load a UEFI-aware OS is a subset of the code that is
required to boot a traditional (non-EFI-aware) OS.
01-26-2014 05:08 PM
01-26-2014 05:19 PM
Nodens wrote:
Are you sure you are selecting the proper drive? To troubleshoot try disconncting all drives except the RAID array and the drive with the installation media (DVD or flash drive). Also what drivers are you using?
04-13-2014 05:26 PM
05-06-2014 07:18 AM
05-06-2014 09:19 PM
05-31-2014 05:51 PM
06-01-2014 06:32 PM
thebski wrote:
Hi, I am having some trouble installing Windows 8.1 on 2 Samsung 840 Pros on a Rampage IV Formula. I have tried with CSM disabled and with CSM enabled and everything set to UEFI first as shown in the screenshot. In each case I set secure boot to other OS. I then create the raid array in UEFI. In both cases, as soon as I try to boot to the DVD drive with prefix uefi, it flashes the blue windows screen and then quits. If I have CSM disabled it will cycle back to the bios. If I have it enabled it will just sit on the black screen with the cursor at the top left corner flashing until I shut it off.
I feel like I've followed the guide, but I can't get Windows setup to start. GPUs are 780 Ti's as well, so I would think those should have new enough firmware.
Any ideas on what I'm doing wrong? Thanks!
Edit: I have bios 3504 installed on my board. The guide says 3404 but I assumed anything later worked as well. Just wanted to throw that in as well.
Edit #2: I figured out that I could not use my Blu Ray drive to install UEFI. It was somewhere in this thread, and that ended up being my problem. So I got everything installed, but I have another problem.
If I have SLI disabled, I would say the machine boots in about 10 seconds. Power button to Windows desktop in 10 seconds (guessing).
If I enabled SLI, it appears to load Windows fine, but the displays are really confused for a long time. They eventually get it straitened out, but it takes forever. Power button to desktop is more like 2 or 3 minutes in this case..
Is this a known problem? Has anyone else had this issue? I never noticed SLI affect boot times in the past, but something is very wrong with it here.
07-14-2014 03:04 PM
06-02-2014 10:58 PM
06-11-2014 02:42 AM