[HowTo] Get full NVMe Support for all Systems with an AMI UEFI BIOS

OK, Disk Manager + Paragon HD Manager screen…:

SD.png

PM.png

@iX-9 :
Thanks for the screenshots.
Contrary to you I still doubt, that the Samsung 960 EVO SSD is bootable by a system, which doesn’t have an EFI bootloader and an NVMe “DXE Driver”. Your screenshots verify, that the usually hidden 100 MB sized EFI partition with the Windows Boot Manger is still present within your bootable system disk drive.
Please do your announced test with your Intel 7-Series chipset mainboard without native NVMe support (no NVMe.ffs module within the BIOS).

Hi Fernando! …again! :slight_smile:
Just keep pushing you:
I deleted and zeroed that unused EFI partition!
And wrong nothing hapened, windows starts as normal!

SD2.png

PM2.png

Hello Fernando,
Just found this great forum and very happy about it.
Want to ask you one thing. I did a mistake by buying Chinese nvme 250 GB card. So it’s practically noname I would say. There is a name, KINGSPEC, but I doubt it makes any difference. Anyway, I tried this card in a few motherboards, in mine, gigabyte x470 ultra gaming, then office computer with AB350M-Gaming 3 and msi gaming notebook and it is not recognized in any of them. So I was wondering, this ssd is defective or since gigabyte have a list of compatible nvme ssd in their support webpage of this motherboards, it is just not compatible? So I don’t know should I open case against seller and get refund or should I try your bios modding for getting support for ssd’s which is not in supported list?
Thank you.

@iX-9 :
That is an interesting result.
Please remove the Linux partition from your NVMe SSD and repeat your test with an older Intel Chipset system without having inserted any NVMe DXE Driver module into the BIOS.


@shrisha :
Welcome to the Win-RAID Forum!

If an NVMe SSD doesn’t work at all on a system, which natively has full NVMe support, it is obviously faulty.
My suggestion: Give it back the SSD to the merchant where you bought it and get the refund.

Regards
Dieter (alias Fernando)

I thought so too, Thank you Fernando.

Deleted Linux, nothing more left for possible EFI, but still boots as normal.

SD3.png

PM3.png



( We are talking about the new GB X470 Aorus Gaming 7 WiFi motherboard! )

On old 7-Series system, without NVMe-modified BIOS, dont need to test this, it dont work!
Without modded BIOS, its absolutely unbootable with EVO960.
Some time before, I modified its BIOS exactly that way, as specified in the first post of this thread, just add single NVMe module.
From that time, the system is UEFI bootable with EVO960, I used it till now.
But it is NOT Legacy bootable…

@iX-9 :
Thank you for your last report, which verifies, that the Samsung 960 EVO SSD itself doesn’t contain an NVMe Option ROM (contrary to the Samsung 950 Pro). This means, that systems with no native or added NVMe support are not able to boot off the Samsung 960 EVO SSD.
For your find, that the Gigabyte X470 Aorus Gaming 7 WiFi mainboard is able to boot off the Samsung 960 EVO in LEGACY mode, I have only 2 possible explanations:
a) The BIOS of this specific mainboard contains an NVMe Option ROM (outside the “DXE Driver” Volume). I haven’t yet seen any report, which indicates this possibility.
b) It uses the EFI NVMe module, no matter which BIOS settings and partition scheme the user has chosen.
You can find it out by flashing a BIOS, where you have removed the DXE Driver named Nvme. If you should till be able to boot off the Samsung 960 EVO, it would be the proof, that the BIOS contains an NVMe Option ROM module. Maybe you can find, extract and offer this Option ROM module. That would be really perfect!

@Fernando ,

I looked into iX-9’s bios and found where all his option roms are kept in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0 and not one of them is Nvme related. Most likely its option b like you said in that his efi module has support somehow via the CSM. Very interesting find non-the less…

So, finaly tested the extracted modules in old 7-Series system:

1.) In first try I use four of FFS:

1.png


- It dont work, no SSD detected.

2.) In second try I use all six modules:

2.png


- It dont work, no SSD detected.

3.) Next I added also NVMe_Expres_4 module from this thread:

3.png


- This worked like before: SSD is detected and UEFI-only bootable.


- This means that my extracted modules do nothing, are skipped.
- Looking at the last screenshot: I found that FFS from this thread dont contain “Dependency” and “Version” section. Maybe I should remove these sections from my FFS’s? But HOW??

The only extracted module, which may have been usable for a mainboard BIOS without native NVMe support, is the file named Nvme.ffs. All other modules are not usable by the system BIOS modules of a mainboard without native NVMe support.

This would not help at all.

What about to add also this section?

CSM.png



If it boots through CSM…

You can try it, but I doubt, that you wll succeed.
By the way: The structure and the System BIOS files of AMI Aptio V BIOSes are quite different from AMI Aptio IV ones. Bad consequence: The transplantation of the related modules from an AMI Aptio V to an AMI Aptio IV BIOS is a high-risk action. The related mainboard may be bricked thereafter.

Hello,

i’m stuck at the DXE integration, i’ve tried to find DXE but it not show’s up in UEFITool0.22.4 am i getting something wrong? Link

My board is a Asrock X79 Extreme4.

1.jpg

@ich777 :
Here is the DXE Driver Volume of your mainboard BIOS:

Here is the DXE Driver Volume.png



My the way: The last listed DXE Driver is named “aDefaultDXE”.

@Fernando thank you, didn’t see it because the window is to small :smiley:

…and thank you for the hint :wink:
Hope you’re doing well and thank you for this great board!

Regards

Hello all!

First of all - congratulations for Fernando for having the best bios modding forum on the net! I’ve used your guides many times in the past without any issues. Same with NVMe mod, however curiosity makes me to write my first post. I’ve done my mod some time ago (in 2017 I guess) with v3 of the NvmExpressDxE. Recently bought NVMe drive which works and boots as described on Z87 board. Few days ago I’ve check the thread again and noticed that file has been updated to v4. So my question is: are there any advantages on V4 compared to V3? My mind is a bit twisted and everything need to be updated, so I’m torn - leave it or update?

Thanks!
D.

Fernando, would you happen to know the NVMe version for that one you uploaded in this forum post? 1.3 or newer i suppose?.. maybe 1.3c or something? Just curious

@darrecky :
Welcome to the Win-RAID Forum and thanks for your positive feedback!
When you update the NvmExpressDxe module to v4, you will not benefit regarding the functionality and the performance of the SSD, but you may get a shorter boot time and enhanced compatibility for future NVMe SSDs resp. their NVMe Controller.
If I were you, I would do it.
Regards
Dieter (alias Fernando)

I do not really understand. Which “NVMe version” (driver or BIOS module) and which Forum post do you mean?

I do not really understand. Which “NVMe version” (driver or BIOS module) and which Forum post do you mean?


I mean specifications. Sorry for not going over that in detail
https://en.wikipedia.org/wiki/NVM_Express