I don't know well the VM behaviour but if you flash the correct gop uefi table, VGA can boot in "real environment" as a Full-UEFI system.

Hi,
I have a problem with the GOPupd tool. I try to update vBIOS of MX150 (GP108) card (link to the image: https://cernbox.cern.ch/index.php/s/BEXhHhpcYGMeTWb) using the tool in the latest version (1.9.8.b). The Nvidia flash tool shows the following information for my original vBIOS:
$ ./nvflash_linux --version vga.rom

NVIDIA Firmware Update Utility (Version 5.414.0)
Simplified Version For OEM Only
IFR Data Size : 0 bytes
Image Size : 180736 bytes
Version : 86.08.11.00.29
~CRC32 : E1265835
Image Hash : 05507E5C2517B6A7F24370C493BDDF40
OEM String : NVIDIA
Vendor Name : NVIDIA Corporation
Product Name : GP108 Board
Product Revision : Chip Rev
Device Name(s) : GeForce MX150
Board ID : F107
PCI ID : 10DE-1D10
Subsystem ID : 17AA-225E
Hierarchy ID : Normal Board
Chip SKU : 650-0
Project : 2902-0000
CDP : N/A
Build Date : 04/11/17
Modification Date : 09/06/17
Build GUID : 4E71C004CA014FE3BC64F3B718CFB814
UEFI Support : No
UEFI Version : N/A
UEFI Variant Id : N/A ( Unknown )
UEFI Signer(s) : Unsigned
InfoROM Version : N/A
InfoROM Backup Exist : NO
License Placeholder : Absent
GPU Mode : N/A
Sign-On Message : GP108 E2902 SKU 0 VGA BIOS

However, after the updated image (link: https://cernbox.cern.ch/index.php/s/eitrxVCDB3Lc5An) generated with the tool for GP1xx (number 7) GPU architecture contains the errors reported by the nvflash:
$ ./nvflash_linux --version vga_updGOP.rom

NVIDIA Firmware Update Utility (Version 5.414.0)
Simplified Version For OEM Only

ERROR: PCI Block corrupted - size mismatch

Do you know how could we fix it?

Did you try a different nvflash version ?

Anyway it would be nice to have sources of GOP Uefi Updater in order to accomodate also the incoming Turing vga cards.

Some new bits regarding the patching issue I met with a Quadro K2100M for an HP Zbook 15 Mobile Workstation ( previous posts: AMD and Nvidia GOP update (No requests, DIY) (35) , AMD and Nvidia GOP update (No requests, DIY) (35) , AMD and Nvidia GOP update (No requests, DIY) (35) ).

Reminders: I run a linux. So I cloned a tiny installed-Windows to an USB stick, in order to boot it bare-metal on the laptop. I still run the OEM system BIOS (that ties the VBIOS of the discrete Nvidia GPU). The Nvidia discrete GPU is only in use as primary graphics when the BIOS is set to HybridGraphics=disabled. What follows uses this context.

What I saw from that USB-hosted Windows installation: the Nvidia drivers provided by HP installs fine, and device shows no error 43 in the end. I can access the Nvidia control panel.

What is more interesting about VBIOS:

• The latest Windows version of Nvflash couldn't dump it: same error as obtained in the reference post message of this topic ("IFR-only image"). I tried dumping with both HybridGraphics=disabled and HybridGraphics=enabled set in BIOS: same results
• Only once the Nvidia drivers were installed, that registry hex key got created: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001\Session\vbios": you'll find it attached

I don't know what to say @Rockz.

@Sylar76 :
I have tried the latest version (original post) and a bit older (5.265) and both report the same error. I don't expect it's a problem of nvflash as it works properly for the original vBIOS. Moreover, the one generated with GOPudp doesn't solve the famous Nvidia "Error 43" in KVM (although, despite my precautions, a source of this could be still somewhere else).
Can I help somehow, to fix the tool so it generates a proper vBIOS for newer NVIDIA GPUs like mine?

You have to force flash under nvflash as any modded bios in order to be properly flashed.

@Sylar76:
I don't want to flash my GPU. I need a UEFI compatible vBIOS in order to have a discreet GPU assigned to a virtual machine (KVM). Thus, I need to generate a valid vBIOS. I think currently it's simply either ignored by KVM or NVIDIA drivers inside the virtual machine.
I assume that for other vBIOS, the users didn't report a modded image which would be corrupted, did they? Thus I think GOPupd has a bug which we could address.

I can't figure out that bug yet.

@Sylar76: Do you need more information from me?
In my original message, I enclosed the original vBIOS file (properly recognised by nvflash) and the output file generated by GOPudp.

The bios you linked in your post is very very strange. How did you obtain that ?

The original one or the one produced by GOPupd?
The original one was extracted by UEFITool (https://github.com/LongSoft/UEFITool) from the BIOS of the Lenovo T480 laptop (https://pcsupport.lenovo.com/ch/en/produ...nloads/DS502355). I believe it's fine, as nvflash doesn't report any problems.

I'm not sure about that. Could you dump the original bios using nvflash instead of uefi tool ?

@Sylar76 : I can't dump it using nvflash, as this graphics card doesn't come with a separate EEPROM to store vBIOS (https://gist.github.com/Misairu-G/616f7b...tract-you-vbios). The vBIOS of this GPU is stored inside UEFI of the laptop and stored in the EEPROM which is shared for the whole machine.