I also ran into the unknown Realtek EFI. BIOS is a few days old, so it canβt be an old EFI version.
SoniX, thanks for looking at that Dell Vostro 3670 bios. The first mis-flash was a head-scratcher. Iβll have to play with a hex editor - was trying to avoid that, and it still may be a bridge too far.
This will be an issue for the Dell Inspiron 3670 also, and probably all Dell computers that have the Winbond W25Q256JV 32MB bios chip.
Users recently reporting several issues with UBU and other tools pointed on the forum, need to understand the βmainβ issue hereβ¦specially regarding the biggest percentage of bios AMI Core basedβ¦
There is NO RECENT βleaksβ to the web of these tools, since the past Aptio IV based bios, to deal with recent Aptio V bios structures/advances, this was 10yrs ago and thatβs a βCenturyβ in this area of innovation.
Resulting this in several modifications to the users files getting bad bios mods, by using these toolsβ¦the only versions available but not suitable for modern bioses.
Many volumes/modules can be touched and the user donβt have the clue on what was moved/deleted/modifiedβ¦
These shared user developed tools are always tied to the manipulation of the bios vendor main code and the task becomes much harderβ¦(donβt want to say impossible) when such tools are part of the project and thereβs no technical information βoutsideβ for guidance and building.
With this i just want to pass the message, be patient and donβt expect βfixβ for all issues, at least in a shorth time period and think on the developer user passionβ¦ on the other side, that may not have the time, the health and the age/spirit from other timesβ¦
RTK UNDI 2.039
Alius optio:
set str_patt=00000000000000000000000000000000409A499A599A609AIf it finds more GOP, then add 00 to the beginning of the line.
1 Like
My CPU is i9-11900K and i5-11600K ,both come with built-in UHD750 iGPU. I have tried with or without adding 00 to the beginning of the strip line. This time,UBU does replace the GOP Xe driver correctly. There is no repeated or redundant replacement. My Z590 mobos did successful boot with a βbeepβ sound. Unfortunately, I got a blank screen after the βbeepβ sound and then boot procedure stopped. It seems the modified BIOS is accepted by the mobo and passes the self tests in the BIOS initialization. However, something wrong occurred to load the GOP Xe driver , which results in blank screen. I tested the GOP Xe 17.0.1085 driver in another LGA 1700 Z790 platform(i9-14900KS, UHD770 iGPU) without any modification in the UBU.cmd strip line and it works just fine. I assume the GOP Xe 17.0.1085 driver is universal to UHD750 and UHD770, but i donβt know why it works in Z790 platform but not in Z590 platform.
What are the VBT versions of each board?
1 Like
There is no point in offering a replace here, as you have nothing to replace. Lenovo BIOS + EFI file. Is the i219 EFI some new file? I canβt find an older version in my own collection. Of course, it could also be that I havenβt looked enough at Lenovo BIOSes.
a15_DVfix
I have corrected the DrvVer for old Realtek LAN, but it is possible that versions 050-056 will not be detected.
Edit:/Add
a15_DVfix2
1 Like
It recognizes it, but it does not display the real version number. v2.050 to v2.057 (not up to 56) will display the same non-real version (8.04F BD). However, the current state is better than the previous one, since the UBU can now replace the file. It replaces the βgoodβ with the βbadβ and vice versa.
Tested:
2.010, 2.013, 2.015, 2.021, 2.022, 2.023, 2.026, 2.027, 2.028, 2.030, 2.034, 2.035, 2.036, 2.037, 2.039, 2.040, 2.041, 2.042, 2.043, 2.044, 2.045, 2.046, 2.048, 2.049, 2.050, 2.052, 2.053, 2.054, 2.055, 2.056, 2.057, 2.058, 2.059, 2.060, 2.061, 2.063, 2.064, 2.065, 2.066, 2.067
mod: with fix2 almost everything works. There are two βdifferentβ files that you probably havenβt come across (53, 54). They still show up incorrectly. I also have two types of files from 56, but both are well displayed.
realtek_efi.rar (70.5 KB)
SoniX, I have attached infos of both BIOS as following.
ASUS Maximus XIII(Z590)
Gigabyte Z590 Aorus Elite.
UEFI BIOS Updater v1.80.a16
Changelog:
Added the option to use MMTool for files.Updated:
DrvVer 0.31.1.4 mCodes LGA 1151v2
Using mmtool_a5 and bypassing microcodes, no issues/problems.
a16 run:
Summary
Scanning BIOS file backupa.bin.
Please waitβ¦
Manufacturer - Default string
Model -Default string
BIOS release - 5.13 08/31/2023
BIOS version - 00.30
BIOS platform - AMI Aptio 5[EFI Drivers - Find and Extract]Intel RST GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629
Intel GOP SubGUID D8248140-88B5-4C14-9E9F-FD1CFA9D071E
AMI NVMe GUID 634E8DB5-C432-43BE-A653-9CA2922CC458
Realtek Undi GUID 4953F720-006D-41F5-990D-0AC7742ABB60
Intel GOP VBT GUID 56752DA9-DE6B-4895-8819-1945B6B76C22[OROM - Find and Extract]VBIOS in GUID FD41D244-F0FB-4FD0-8FD6-4276BD4323D0
OROM in GUID 7C3B8701-2C3B-49FA-A529-F31D441265B1
OROM in GUID 6357578A-52D1-4517-BE96-10391404754C
OROM in GUID 914AB3BE-A2C2-463A-B77D-F820FBBA180EUEFIReplace v0.25.0 will be used.
MMTool Aptio v5.02.0024You will use MMTool?0 - Do not use MMTool. (As in UBU v1.7x).
1 - Use MMTool. (If, after replacement without MMTool, XMP, OC, etc. do not work,)
Choice:1
Main Menu
[Current version in BIOS file]
1 - Disk Controller
EFI Intel RST RAID Driver - 17.8.1.4572
EFI NVMe Driver present
2 - Video OnBoard
EFI GOP Driver SKL-AML - 9.0.1085
RAW GOP VBT SKYLAKE - 221
3 - Network
EFI Realtek UNDI Driver - 2.041
4 - Other SATA Controller
5 - CPU MicroCode
View/Extract/Search/Replace
S - AMI Setup IFR Extractor
O - Option ROM in other GUIDs
0 - Exit
RS - Re-Scanning
A - About
Choice:1
Disk Controller
[Current version]
EFI Intel RST RAID Driver - 17.8.1.4572[Available version] EFI Intel RST RAID Driver - 17.8.4.46711 - Replace
X - Extracted
0 - Exit to Main Menu
Choice:1Intel RST GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volumeβs free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continueβ¦
File replaced
Rebuilding GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629. Waitβ¦
Done.EFI Intel RST RAID Driver - 17.8.4.4671Press any key to continue . . .
Video OnBoard [Current version] EFI GOP Driver SKL-AML - 9.0.1085 RAW GOP VBT SKYLAKE - 221 [Available version] EFI GOP Driver SKL-CML - 9.0.11131 - Replace GOP Driver
X - Extracted
0 - Exit to Main Menu
Choice:1
Intel GOP Driver SubGUID D8248140-88B5-4C14-9E9F-FD1CFA9D071E
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volumeβs free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continueβ¦
File replaced
Rebuilding GUID 26061B47-0B90-4FB4-A0D7-DA89B4AED49B. Waitβ¦
Done.EFI GOP Driver SKL-CML - 9.0.1113 RAW GOP VBT SKYLAKE - 221Press any key to continue . . .
Network [Current version] EFI Realtek UNDI Driver - 2.041 [Available version] EFI Realtek UNDI Driver - 2.0672 - Replace Realtek
X - Extracted
0 - Exit to Main Menu
Choice:2
Realtek GUID 4953F720-006D-41F5-990D-0AC7742ABB60
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volumeβs free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continueβ¦
File replaced
Rebuilding GUID 4953F720-006D-41F5-990D-0AC7742ABB60. Waitβ¦
Done.EFI Realtek UNDI Driver - 2.067Press any key to continue . . .
Main Menu [Current version in BIOS file]1 - Disk Controller
EFI Intel RST RAID Driver - 17.8.4.4671
EFI NVMe Driver present
2 - Video OnBoard
EFI GOP Driver SKL-CML - 9.0.1113
RAW GOP VBT SKYLAKE - 221
3 - Network
EFI Realtek UNDI Driver - 2.067
4 - Other SATA Controller
5 - CPU MicroCode
View/Extract/Search/Replace
S - AMI Setup IFR Extractor
O - Option ROM in other GUIDs
0 - Exit
RS - Re-Scanning
A - About
Choice:0
Yes, I did mention that another Z790 mobo(ASUS Z790 Dark hero) works just fine with the GOP Xe driver replaced. The GOP/VBT info is as following. Thank you for further investgation.
I think this is a similar situation with GOP 9.0.1082. Necesitaba una versiΓ³n VBT 221 o superiorβ¦
In your case, VBT 237 and 240 are installed on the Z590, and 250 on the Z790.
In order for GOP 17 to work correctly on different chipsets, you need to search and check all versions from 1060 to 1084.
1 Like
@SoniX, for my Vostro 3670 project, my hex editor work broke the FIT table, so I ran a16_DVfix5 just to compare/contrast.
When I ran a16_DVfix5 selecting the use of MMTool, I had no problem replacing microcodes. When I selected 0 - Do not use MMTool. (As in UBU v1.7x) Iβm getting the following:
mCode.ffs (2/2)
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Intel β
βββββ¬ββββββββββββ¬ββββββββ¬ββββββββββββ¬βββββββββββ¬βββββββββββββ¬ββββββββ¬ββββββββββ¬ββββββββββ¬βββββββ’
β # β Type β CPUID β Platforms β Revision β Date β State β Size β Offset β Last β
βββββΌββββββββββββΌββββββββΌββββββββββββΌβββββββββββΌβββββββββββββΌββββββββΌββββββββββΌββββββββββΌβββββββ’
β 1 β Microcode β 906EA β 22 (1,5) β F8 β 2024-02-01 β PRD β 0x19C00 β 0x18 β Yes β
βββββΌββββββββββββΌββββββββΌββββββββββββΌβββββββββββΌβββββββββββββΌββββββββΌββββββββββΌββββββββββΌβββββββ’
β 2 β Microcode β 906EB β 02 (1) β F6 β 2024-02-01 β PRD β 0x1A000 β 0x19C18 β Yes β
βββββΌββββββββββββΌββββββββΌββββββββββββΌβββββββββββΌβββββββββββββΌββββββββΌββββββββββΌββββββββββΌβββββββ’
β 3 β Microcode β 906EC β 22 (1,5) β F8 β 2024-02-01 β PRD β 0x1A000 β 0x33C18 β Yes β
βββββΌββββββββββββΌββββββββΌββββββββββββΌβββββββββββΌβββββββββββββΌββββββββΌββββββββββΌββββββββββΌβββββββ’
β 4 β Microcode β 906ED β 22 (1,5) β 100 β 2024-02-05 β PRD β 0x1A000 β 0x4DC18 β Yes β
βββββ§ββββββββββββ§ββββββββ§ββββββββββββ§βββββββββββ§βββββββββββββ§ββββββββ§ββββββββββ§ββββββββββ§βββββββNote: Microcode #1 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #2 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #3 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!Note: Microcode #4 is not in the database! You can help this project
by sharing it at https://win-raid.com forum. Thank you!
These microcodes will be entered into your BIOS fileR - Start replacement
A - Start replacement Alternative with MMTool
0 - Cancel
Choice:R
[Preparing for replacement]
BIOS file backup
[Replacement]
mCode FFS: The syntax of the command is incorrect.
The program ends and goes back to a dos prompt.
Edit1: Selecting R - Start replacement craps out. The assumption was that UEFIReplace would be used.
Selecting A - Start replacement Alternative with MMTool worked, but it worked when selecting MMTool at the beginning:
R - Start replacement
A - Start replacement Alternative with MMTool
0 - Cancel
Choice:A
[Preparing for replacement]
BIOS file backup
[Replacement]
Delete old mCode - 906EA 906EB 906EC 906ED
Insert new mCode - 906EA 906EB 906EC 906ED Real Pointer
FIT Offset - FFD50100 == FFD50100Real _FIT_01 mCode Offset - FFD50400 == FFD50400
mCode Size - 19C00
02 mCode Offset - FFD6A000 == FFD6A000
mCode Size - 1A000
03 mCode Offset - FFD84000 == FFD84000
mCode Size - 1A000
04 mCode Offset - FFD9E000 == FFD9E000
mCode Size - 1A000
Press any key to continue . . .
Edit2: Removing MMTool from the UBU_v1_80_a16_DVfix5 folder gives essentially the same output:
R - Start replacement
0 - Cancel
Choice:R
[Preparing for replacement]
BIOS file backup
[Replacement]
mCode FFS: The syntax of the command is incorrect.
@SoniX, DONβT CHANGE ANYTHING! Selecting 0 - Do not use MMTool. (As in UBU v1.7x) and then A - Start replacement Alternative with MMTool puts a Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1!!!
THANK YOU!
Thanks for reply. Do you mean I have to get GOP Xe driver 17.0.1084(or below) to work with Z590 BIOS ? GOP Xe driver 17.0.1085 only works for Z790 BIOS ?