Now I will read again

Hi Fernando and others:
I have a Gigabyte GA-Q170TN and want to use the Mini-PCIe (was using an mSATA 1TB boot/system here) for 4G modem the consequence is I
I also want to move Boot to and NVME plugged into the PCIex4 slot.
Unfortunately, Gigabyte never saw fit to enable the NVMe functionality (which works fine with the Windows 10 NVMe driver as a secondary drive).
I followed the methods in post #1 of this thread but cannot get any boot option.
I tried many things without success then thought I would compare their Q170 sister motherboards (ATX and not mini-ITX)
So used the UEFITool 0.26 to extract and insert the 4 x NVME modules I found.

The only additional feature I got was a section in BIOS Setup that displays the M.2 drive info but no settings that could select or change boot options.
There appears to be some issue with the Setup bios not enabling or searching for M.2/NVMe boot devices.

To assist analysis I have included a comparison using text compare from exported reports.
Any clues you could provide that could help would be greatly appreciated?

https://www.dropbox.com/s/x77yw9geicrrgk...e-bios.pdf?dl=0

Motherboards in question can be found here:
https://www.gigabyte.com/Embedded-Comput...pport-dl-driver
https://www.gigabyte.com/Motherboard/GA-...support-dl-bios

Many Thanks, Rod!

Zitat von Fernando im Beitrag #4395

---

@RocketRod:
If you want to get help from my side, you should follow my guide, which is within the start post of this thread.

---

Zitat von RocketRod im Beitrag #4394

---

I followed the methods in post #1 of this thread but cannot get any boot option.

---

Also are you aware of a tool or approach that can be used to decompile the modules?

@RocketRod Just FYI : "CSM" is a module used for legacy boot. I have it on my ASUS motherboard.

As I said before I have already done that process of using "the UEFITool and to insert the NvmExpressDxe_4.ffs module" as you recommend (exactly) before and it did not work for me.
The result is that no NVME drive is selectable as the Boot drive nor appears in F12 (boot drive select)

I think the problem here is that AMI MMTool is not fully compatible with the Gigabyte firmware configuration (i also experienced those problems)
The strange thing though is I tried using the UBU script (which seems to script the use of MMTool) and it did work to update the drivers.
I just tried that more just out of interest in the UBU tool's use than trying to achieve anything with it.
But I was able to flash from a FreeDOS boot disk with a modded EFIFlash. Which for now seems to be the only way I have been able to update any BIOS mod - thus bypassing verification checks.

I am contemplating just trying to flash the whole BIOS from the other sister motherboard since they are so similar.

Thanks, Yes, I do realise all that as I have done a couple of other motherboards using your method and setup Windows 10 boot manager successfully and seen "SS PATA" or something like that.
This motherboard is a little different than most previous issues because its BIOS has been deliberately hobbled from supporting NVME even though it was originally developed to support NVME (sister boards do)
There is at least one remnant in it that proves this in relation to NVME power management that can be seen in the BIOS strings in the AMI MMTool.
I will spend some more time later playing. I was just hoping you could shed some more light on the details highlighted in PDF I linked to that compared the two BIOS drivers.
I may even pose the question to Gigabyte as to why they removed the NVME support although I am not expecting that will lead anywhere.. perhaps if they can see the use case they MAY comply with an update that reinstates the native NVME support
I will keep everyone informed.


BTW:
You can see what is probably equivalent to CsmCore as
CsmDxe driver at 02:093

and others at
CsmBlockIo driver at 02:175
CsmVideoo driver at 02:176

refer: https://www.dropbox.com/s/x77yw9geicrrgk...e-bios.pdf?dl=0

sorry I cant find my latest post in the forums so I posting here

for some odd reason why 2 "windows boot manager" entries shows as boot option 1 and 2 with single 970 evo using pcie adapter.

I only use single drive. every thing seems normal in this...

I tried both links and both are bootable because both have the exact same info as "windows boot manager" as option 1 and 2. if i disable csm then pata ss is shows up with both boot option....