@SoniX

fixed and reuploaded at the previous link. Thanks.

@Sylar76
Should I just flash this file?

@adel23444

You could try to generate the new bios file with the latest GOP Updater version I've linked few posts above.

Hello, and thanks for such a great tool and knowledge on the topic.

I'm using it to add UEFI support to a GK106 board. Its OEM manufacturer provides a non-UEFI BIOS for it. Why do I look for an UEFI GPU BIOS? In order to passthrough the GPU into an UEFI virtual machine: the host Linux OS uses the integrated Intel GPU, and the Windows VM will benefit from the discrete Nvidia GPU. That's the goal. The UEFI BIOS dump file is not intended to be flashed on the real GPU, it's only given as a parameter to the virtualization software, so that he initializes the GPU properly in the VM (i.e. it passes the clean POST BIOS to the VM, and I understood that providing a self-made dump of the GPU BIOS is not good, because that BIOS would be dirty/tainted). To some extent, maybe I'll have to flash it for real for the whole sequence to work flawlessly, but that's not the goal.

At the moment, I've some warnings when using the tool and cannot find the reason why. Input sequence: 1/ "GOP is not present. Do you want ..?" Y, 2/ "GPU arch?" 8 (i.e. GK1xx_MXM)




Here is the BIOS file that provided that output: https://www.techpowerup.com/vgabios/1498...00m-2048-130612 (there's a single "official" BIOS - at TechPowerUp - for that GPU, what https://www.techpowerup.com/vgabios/?arc...l=Quadro+K2100M shows). ROM is 98KB.
For that run, I used the latest v1.9.8.b along with the latest python version on a bare metal Windows 10 x64 OS.

The generated ROM is 172 KB.

Note that TechPowerUp has some unofficial Dell BIOS for the same GPU, Dell OEM this time. This one has UEFI-support: https://www.techpowerup.com/vgabios/163744/163744 . I didn't diff BIOSes yet.

Other things I tried:

• Using arch 4 (i.e. GK1xx, no MXM): same result
• Removing the Nvflash header from the BIOS file (i.e. everything until the first "U" character in text), before applying on the GOP Updater: same result
• Downloaded the HP system BIOS update for the laptop that embeds this GPU: https://support.hp.com/us-en/drivers/sel...mId/ob-212595-1 . The system BIOS embeds the GPU BIOS seemingly, that's a tight coupling between the integrated and discrete GPUs. Un7zipped the "exe" file, un7zipped the single "bin" file found in it. Then hex-searched the whole set of "rom" files for the "GK106" text string. I finally found 2 identical files, which are very similar to the one at TechPowerUp
• Applied that ROM on the GOP updater: got the same warnings output as shown above
• Dumping the system BIOS to a flashdrive from the laptop's BIOS UI: obtained the exact same file than what extracted from the HP system BIOS update "exe" (the big "bin"), along with other files; un7zipped the big "bin" in the same way, obtained the same GPU ROM file

• With the initial BIOS, I get error code 31 in Windows peripherals manager: "The driver trying to start is not the same as the driver for the POSTed display adapter". This may be due to the VM system BIOS being UEFI without CSM, that fails to load the GPU BIOS. Or this may be due to the passed-through Nvidia GPU to be the 2nd graphics adapter in the VM, i.e. not the primary adapter that was in charge while POSTing/booting the VM
• With the GOPed BIOS, error moves to a code 43: "Windows has stopped this device because it has reported problems". I'm not sure if the updated driver won over the first error, or triggered an error with a stronger precedency ;)

Hello guys i need your help!
I have the Evga gtx550ti with non uefi bios. Gigabyte released an uefi bios for gtx550ti back in 2012.What i want is to cut the uefi gop driver from gigabyte bios and flash it to evga non-uefi bios. I have tried it with a new version of uefi gop driver and the uefi boot works but with some artifacts at startup.I want to try the older version from the gigabyte bios to see if the artifacts still exist. Can anyone help me? i have attached my evga stock bios(non uefi) and the gigabyte uefi bios.
So what i need is a modded gop updater that flashes the version from the gigabyte file and not the latest one.

@ektorasdj

Try the one I attached below.

@Rockz

The Warning messages are referred to the whole absence of UEFI GOP data inside the original bios. Of course, when you add the uefi part, the bios size increases. In your case I'd try to flash the new bios with uefi gop tables on VGA
and see if it works in a VM full uefi behaviour.

Thanks for the fast response. I have already flashed the bios image with the 0x1001F (May 3 2013 @ 15720600 ) version and it works great expect some artifacts after passing the bios screen(on uefi csm disabled boot).
Thats why i want to try the version 0x10017 (Nov 15 2012 @ 14390738 ) from the gigabyte bios to see if those artifacts still exist.What i dont know how to do is to put to 0x10017 version to gop updater.

In the attached file above, I've copied the EVGA legacy bios together with the UEFI part of the Gigabyte bios and then updated the whole structure. Did you try my file to see if you still have artifacts ?

Anyway below I've attached a new file with the UEFI GOP taken from the Gigabyte.

I just tried it your bios and the artifacts are still there.Those artifacts happening before login screen and after the bios+os have loaded.I have not found any problem with games and it only happens with csm is disabled.
I want to try the older version that gigabyte has for my gtx 550ti as a last test to be sure.
I have attached the image with the artifacts ,nothing serious but still...

Edit: The bios you just attached in nvidia_rom_info(evga_test.zip) shows no uefi support did you perhaps upload the original?

Try this new one, I've modded gopuefi in order to accomodate the uefi part from gigabyte like you requested.

Artifacts are still there. It seems the gop driver version isnt the culprit(Who knows maybe its the mobo fault.). I will test further and see from where those artifacts come from.
Thanks for everything and sorry for taking up your time, you really helped me!

It could also be the motherboard bios.

Thanks for input Sylar. In fact, I had found some sample of someone adding UEFI support to a BIOS that initially had none, using the GOP updater too ( https://www.techpowerup.com/forums/threa...95/post-3851793 ).

And he got no warnings or whatsoever. So I thought what I screened is not only due to the ROM having no UEFI part inside.

Some side infos I spotted today:
- From linux, I could only dump the GPU ROM from host (i.e. "cat /sys/path/to/gpu > myDump.rom") while setting HybridMode to "disabled" (i.e. Intel GPU disabled and Nvidia GPU enabled), and booting the host in UEFI-with-CSM. Booting in UEFI-no-CSM or legacy granted me no access to the "/sys/path/to/gpu" file (i.e. "I/O error" when displaying/cating it). With both that HybridMode=disabled and UEFI=UEFI-no-CSM settings in BIOS, I spotted that some new info appears at top-left corner now when the computer boots. As if the system BIOS enabled some special variant of itself.
- From linux, from host still, nvflash_linux could not generate the ROM dump (i.e. it states "Image size: 0 bytes", "IFR-only image")

I'll let you know what happened when I'll have flashed the ROM of the GOP-updater I generated earlier.

@Sylar76 I didn't flash the ROM, but I provided the virtualization software with it.
- With the initial ROM, I've no POST when the VM boots
- With the GOPupdated one, I've POST and land into windows. The latest or older Nvidia drivers will then install with no error message (no previous Nvidia drivers were installed, it's a brand new Windows 10 running here). But then, the devices manager shows the GPU as "error code 43". That is, the GPU sits there, still with the default Windows 2D driver. This may be due to the VBIOS, as much as not. I'm clueless about that atm.

That's still a big improvement from the initial no-POST situation.