Question for ASUS X79-DELUXE
Hi, I'm in doubt whether to add the NvmExpressDxe_3 module or "replace the body" of an existing module?
The X79-DELUXE has unofficial support for NVMe and can see the NVMe drive in the unmodded BIOS (but will not boot from it unless CSM is enabled).

Here's the current NVMe related DXE drivers in the unmodded BIOS:

Hi,

I compiled another NVME DXE driver file with the intention of keeping the size of the driver as small as possible by testing different compilers and versions of EDK2.
So this version I present to you all is only 15kb in size and was from EDK2-2014 and compiled with DDK3790 as opposed to Visual Studio or GCC which produce larger sized files.
I have not tested it. So it is untested but it may help if you have limited space in your volume.

Oh I forgot its only 32 Bit:

http://www.mediafire.com/file/qc1jd4k4i3ii5ki/nvme14.7z

Heres the 64 Bit version:

http://www.mediafire.com/file/8howlb5oppg5mmq/nvme14_64.7z

This one is 20Kb as opposed to 15Kb. Not sure if it matters of the efi driver is 32bit or 64bit? If anyone knows..

Thanks

@Fernando
Ok. No, the CSM problem is 100% related to the PCIe adapter (ASUS HYPER M.2 X4 MINI CARD) or the NVMe drive (Samsung 960 EVO). I had CSM disabled until today where I added those two pieces of hardware. I wonder what to try next to have CSM disabled if you don't recommend replacing any modules. Again, it does not have official support, so I guess the BIOS does not contain the required EFI module?

@davidm71:
Processor architecture of UEFI binaries have to match that of the UEFI firmware. As such you need to use 64-bit UEFI drivers when using a 64-bit UEFI firmware. Note that most motherboards come with a 64-bit UEFI firmware.

I have some ideas to refactor the EDK2 NVMe driver so that it only contains the bare minimum functionality and the binary is optimized for extremely small size. Is the community interested in having such an NVMe driver and is willing to test it?

Well theres still work to be done to get it smaller. I have not tried the 'Os' option on GCC to have it optimize the code. I can try later to recompile it but I think 20 kb is a good size. Of course thats with UDK 2014. The file sizes got bigger with each succesive release of EDK so there will be a trade off of size vs features i'm sure.

@Fernando
You were right. After booting with CSM enabled, I installed the OS (Proxmox) in UEFI mode and after that I disabled CSM and the POST message about not being able to boot went away.
For the record, the message was: "Warning. The current BIOS setting do no fully support the boot device. Press F1 to enter the BIOS Setup. Go to Advanced > Boot > CSM Parameters, and adjust the CSM settings to enable the boot device". I guess the BIOS gave the warning because the drive was empty and it could not find anything to boot.

Thanks! :)

Hello all, So I followed the initial guide and had somewhat successful results. I am running GA-990fxa-ud3-r5 rev(1.0) with a AMD FX8350 CPU and EVGA DDR3 1600 CL9 2 x4,2x8 total 24gig memory, Samsung PM961 128gb drive. So I modded in the NvmExpressDxe_3 module to the F2 bios and flashed using the @Bios Tool. After flashing and reboot the drive first appeared as PATA SSD1. I then installed Window 7 pro x64 from flash drive that had I had injected MS hotfixes into and the MSI SmartTool to add NVME driver and then Rufus to create flashdrive. I did notice after Install PATA SSD1 disappeared and was replaced with Samsung and serial number in Bios and Boot manager. I initially tested with bios raid turned on and seen no conflicts and also booted Fedora 22 from USB drive 3.0. The bios raid is now disabled and it is up and running but the somewhat comes in as I seem to now have system hangs that require hard boot to get out of. One I am posting to share results for anybody who is interested and Two I would like to ask about Using three extracted modules...Nvme.ffs, NVMEINT13.ffs, and NvmeSmm.ffs from a GA-990fx gaming F2 bios on my GA-990fxa-UD3-R5? Sorry not a good with my words but maybe this will be legible.

@Fernando Thank You

Yes I installed and booted with this being only drive present.
Yes when using Rufus I chose the GPT with UEFI.
Yes Boot Manager gave UEFI option as well as legacy option to boot...and yes I chose UEFI.
Yes the hidden EFI partition was installed onto the NVME SSD again was only drive present at install and I seen a third partition.

I have already added the 3 mods to the F2 but have yet to flash.I will gives results of success or not after I flash again.

Thank You.

@Harry

After installing Windows 7 did you boot from PATA SSD1/Samsung PM961 or "Windows Boot Manager"? Booting from PATA SSD1/Samsung PM961 will not work. You must select "Windows Boot Manager" as the bootable drive in BIOS and/or the Boot Manager.

@Paulos7
I think when I did the original flash and boot the Windows boot manager appeared but after installation of win 7 and reboot it disappeared and only have UEFI Samsung option, no windows boot manager appears in Bios or Boot Manager.

As Far as the adding three mods and flashing from the GA-990FX Gaming from my previous post....I used the @Bios Tool again just re-flashed again and it appears to be successful...OS(win 7) booted up no issues so far and now I will have to watch and see if the system hang continues. After re-flash I just noticed that I now have a Sata SM appearing as drive option in Bios and Boot manager. Sorry adding this stuff as I think of it....I noticed when using using the original flash with the NvmExpressDxe_3 when OS was loaded there appeared to be a noise moving through the display, not highly noticeable but there and I should have included my video adapter in my original post, my bad. It is a Msi Geforce GT 710 2gig card and I mention this because since the re-flash the noise is no longer present


I been reading through the forum for awhile but I have not stumbled across any post reporting a successful bios mod on the older non-UEFI boards, I have a Asrock X58 extreme I7-960 sittting on it I would love to move into UEFI but not being Gigabyte Dual Bios, I am not willing to risk it without some solid confirmation it could be done.