here is my BIOS modification for ASUS F1A75-M PRO
https://drive.google.com/file/d/1ht3e5ms...32oCEYdaaF/view

@donaviamoris
Welcome to the win-raid forum!!!
Have you ever tried to flash the modded bios and succeeded to launch the system with NVME SSD in this mobos?

@Fernando
But BIOS boot option "Windows Boot Manager" will NOT be visible after having installed Win10 in UEFI mode onto the NVMe SSD in some MOBOs which I memtioned in the first post.

I agree with his opinion @lfb6 that these mobos's bioses were not completely UEFI compliant.

@Fernando
Thanks,I will post precisely henceforth.
Yes,I don't konw whether this post could help others,but I really don't want to mislead someone.

Hallo gloobox!

I noticed your comment regarding injecting NVMe boot support to intel DP45SG mobo. Well, thats exactly where I am heading to! Currently, my mobo is on the latest BIOS (0125) with the Xeon patch, running E5430. Now, since the mobo has two PCI-E slots, I would like run one for graphics and the other one with an Apple SSD-to-PCIE adapter, where my 512GB Samsung S4LN058A01-8030 will be placed (https://www.storagereview.com/images/YlR...KTdEq_huge.jpeg). It Sees the SSD in Win10, that is on a SATA HDD drive. I can even install Windows on that SSD as it is visible in Win10 install procedure, but it would not boot from it, obviously because of the lack of NVMe boot support in BIOS. Can you help me, please, how to make it?

I know I shall somehow inject the intel NVMe driver into the bios file and the flash it into the chip. But my last attempt ended up by non-posting mobo. So I desoldered the MX chip from the mobo and flashed it with the previously backuped .BIN file...

I obviously need some guidence to inject the NVMe driver correctly. Please, help.

Regards, George

@gloobox

On pre 2.0 UEFI the "windows boot manager" NVAR entry will be only shown as boot entry within the bios boot menu (F10).
The user could not select the entry from the bios setup as UEFI dual boot is unimplemented.

@GeorgettaCZ
could you dump the bios file from your mobo ?I think you'd better dump it by SPI programmer.

Hi I found this post through google and cip67m. I was able to insert the NVME module under csmcore into a rom provided by Lenovo. I haven’t flashed it, because after reading this thread it seems that flashing a Non-UEFI compliant legacy BIOS with NVME mod inserted through MMtool will cause it to not post?

Hi ryambo1987!

Well, to be honest, I never thought of that point of view! And you might be very true that injecting EFI NVME module into the "legacy only" bios structure might definately lead to a boot failure. On the other hand, according to this document https://www.intel.com/content/dam/suppor...ductGuide01.pdf this board already contains Framwork for EFI and according to this document https://www.intel.com/content/dam/suppor...echProdSpec.pdf it also support EFI boot sequence. Even though it's still disabled by default in the bios menu, it is there which means this board is sort of "UEFI ready" and shall be able to boot from EFI boot device. I believe this is how the Compatibility Support Mode alias CSM was born and started to appear in the bioses of all the manufacturers. It became a common part of every biso menu now.

But anyway, if you enable the UEFI boot in the bios menu, then boot from USB flash drive, lets say Windows installer, that was created on a modern Pc with UEFI BIOS and EFI boot as primary option form a GPT initiated drive, then this USB flash drive will no longer boot on any old Legacy bios based PC. But right because you enabled the EFI boot in the bios menu of the DP45SG board, it will boot from that USB drive on the DP45SG with no problem. And if proceeding with the intallation of Windows on a "new" non-initiated HDD or SSD, it will by default initate it in GPT not in MBR! You would later see that in Windows once you have finished the installation successfully. So maybe flashing the file modded by you shall not do any harm to any DP45SG board.

Would you share your modded file, please? I am very curious and interested in seeing that file!

Regards, George

Hi,

I recently got my hands on an Intel Server S3420GP. I opened the .cap file downloaded from the Intel support page with MMTool 5.00.0007 but there is no CSM module. When I try to insert the NVMe module "NvmExpressDxe_4.ffs" into what I think is the correct volume index it throws "Invalid Volume Index". I tried two other volumes but neither worked.

Extracting the ROM with AFUWINx64 and opening in MMTool throws "Error Loading Firmware Image (80000001h)".

https ://www .intel .com.au/content/www/au/en/support/products/50528/server-products/legacy-server-products/intel-server-board-s3420gp-family .html#drivers-software
Intel Server S3420GP Software Support

The most recent BIOS is under the "Intel® Server Board S3420GP BIOS Only Update" download and the file is R0054.cap

I have so far successfully modded 3 UEFI BIOS's with the NVMe driver but they all had the CSMCORE entry.

Regards, Kyle

Possibly not AMI bios. 6CE3993F-CF65-4348-8288-D99F06830944 has DXE entries and a CSM16 module, that's where one could try with UEFITool.

Hi @ky56

Intel bioses can be modded with the NVME module, but it needs to be done with a bios dump (ideally from a hardware programmer), rather than the .bio / .cap file.

Thanks @lfb6,

I was avoiding using UEFITool and even forgot about it after reading that it causes problems with pad files. Once I found a source for MMTool i've just been using that.

That said UEFITool worked great patching the .cap file on this board. Thanks for the GUID pointer. No need for a hardware programmer this time. I used the IFlash32.efi tool that comes with the BIOS updater to flash the .cap file on the built-in EFI Shell.

What i was surprised by was how much free space there is on the BIOS flash. In contrast to the other boards i've done i had to use the NvmExpressDxe_small.ffs. This one could fit the full NvmExpressDxe_4.ffs with heaps left over.

It's definitely an AMI BIOS but it may only be EFI and not UEFI as it's quite old. Neither MMTool or UBU will recognize the file.