@ e.v.o
You can set your micrcode from the place you specified.
"Select: 7 -> m"
@ ALL
There is a suggestion to remove all files and folders IRST (e) from the folder "Modules\IRST".
Instead, leave only 2 empty folders "Modules\IRST" and "Modules\IRSTe", in which the user can put the file versions that are relevant to him.
Thus, it will be possible to select the proper versions, and not what UBU offers,
The IRST and IRSTe files will be in a separate archive.
According to my knowledge it is vice versa:
Intel RST(e) RAID ROM: v13.2.2.2224
Intel RST(e) EFI RaidDriver: 13.2.0.2134
@ Fernando
Oops! Confused. :))
This is partly why I propose to remove all IRST(e) files from UBU, so that users can add the necessary versions themselves.
Added:
[Discussion] UBU Tool related Questions, Reports and Suggestions (201)
But the main reason, such a radical proposal, is that users are more actively studying the materials, and not mindlessly updated everything in a row.
For the first time on my Asus z87-ws bios 2004, i have a bios verifiaction fail while trying to flash via the usb flash system, up to 1.65.3 i never had a fail before ???
I update everything as usual, but not the cpu microcode
I left it to the version 19.
no the newly created bios with updates fails security verification while trying to flash, tried again and again, but not updating the cpu microcode since the version 19 is good for OC if i need it, but im not using it.
Everything seems to update ok, no errors prompts ?? saved as ws87.cap but fail security checks ??
IE: if i try with the computer off, and push the flash button, the file is read and fail, if i use the ez flash option in the bios, the security fail warning is seen
This version is not good for me, tried 3 times, an older version is fine 1.65 … before the AMD mmtool removal.
I think this will make it harder for some people but from my point of view it’s the better solution. Maybe a link to this forum and the thread where one could download the corresponding EFI/ROM would be a good idea
@ coromonadalix
I did not get anything.
There is no particular difference between the versions 1.65.x and the current one.
How do you flash BIOS, EZ-Flash or USB BIOS Flashback?
The file size after UBU, 8194K?
@ e.v.o
Perhaps it will be difficult, but only for those who make updates without hesitation.
Links to pages are listed in the Info section.
On asus z87-ws and others boards you put an usb dongle with the bios file, in my case XXX.cap, you push the rear flash update recovery button (dont know exact name), and it flash itself for aroud 3-5 minutes, now it fails
If i go in the tool box inside the uefi bios, i select the file and it will flash after the security checks … but now it fails
Ill do some checks in the bios, but i did not change anything, and i have some profiles saved, that i load just in case the bios is resetted (cmos cleared) to save time.
File size is 8,390,656 bytes, the same as my original 2004 version ??
I am a bit confused when modifying an ASRock B350 Gaming K4 version 2.60 bios (AMD Ryzen platform).
UBU scanned the bios without any problem, reported it Aptio 5, and entered the select option for update screen.
but in addition to reporting a EFI Realtek UNDI ready to update, which is supposed to be as it has a RTL8111GR GbE card, it also reported a OROM Broadcom Boot Agent and a “Unknown Broadcom LAN Version”. But there is not even such a chip on it! To make matters worse, when I tried to update the Realtek EFI module, the Broadcom module got replaced too. That is, after modding, the “Unknown Version” was changed to EFI Broadcom UNDI 17.2.2.
As my personal guess, Asrock may have built this BIOS and BIOSes for other boards simutanously to reduce engineering workload. And some boards have Broadcom card so they need this. But for my board, It is useless and maybe ASRock disabled or removed the EFI module (maybe filling the content with 0 or so, don’t know) causing it to show “unknown version”, but it will be obviously replaced by a working version after the update process. I don’t know whether it will cause problem since I have to confirm the BIOS is fail-free before flashing.
Maybe add an option to update the Realtek one only, leaving the Broadcom one untouched?
BIOS link: http://asrock.pc.cdn.bitgravity.com/BIOS…K4(2.60)ROM.zip
Also, may I ask why the OROM Realtek Boot Agent GE can’t be updated? The latest version is 2.65 and it has been in the “modules” directory. Also, when I hit 8 and entered the “Other Option ROM in FFS” and it shows like the second screenshot.
Sorry if I’ve done anything wrong.
@asto
I have not yet been supporting AMD for Aptio V.
Added:
@asto
At me to you the big request, please look, what for the chip LAN Broadcomm on a motherboard?
@SoniX
I’m very sorry but I can’t quite understand the English in your second request
. You asked me to look for the very Asrock mothboard that used Broadcom LAN, is that correct?
@SoniX
It’s not simply decoupled, but it neither has such a thing nor has a place to solder it. It’s impossible for me to know the exact model of the chip.
Hello
With UBU, I see the last microcode 21 for Broadwell-E and 3A for Haswell-E, but in the Sonix changelog (on the other topic) I do not see them
These are microcodes for these platforms ?
Thanks
@ tistou77
- CPU Microcode 3A for Haswell-E 0306F2
- CPU Microcode 21 for Broadwell-E 0406F1
These microcodes were included in UBU v1.67, which was not officially released.
Now I added these microcodes to the release 1.68
@ asto
Do not update the LAN files yet.
You have files LAN Btoadcomm of different versions:
- OROM LAN Broadcomm v17, and EFI LAN Broadcomm v4.
I’m not sure that replacing versions from the 4th to the 17th is correct.
Therefore, I need to know the number of the LAN Btoadcomm chip installed.
Hello,My board is MSI Z170,after I’ve updated microcode,the resualt is like this:
±----------------------------------------------------------+
|No| CPUID | Platform | Version | Date | Size Hex |
±-±---------±---------±---------±-----------±---------+
|01| 000906E9 | 22 | 00000058 | 09-03-2017 | 00017C00 |
|02| 000506E3 | 36 | 000000BA | 09-04-2017 | 00018000 |
±----------------------------------------------------------+
MPDT Boot - YES
FIT in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
01 mCode Adrress - FFE70F30
02 mCode Adrress - FFE88730
03 mCode Adrress - FFEA0330
04 mCode Adrress - FFEB2B30
05 mCode Adrress - FFECA330
Attention!!!
Check the Address in the FIT
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFE70F30 + 0x00017C00 = 0xFFE88B30
Is it Ok?Could I flash it?
Thanks!
@ 496175433
If you use KabyLake then Yes. If SkyLake, then you need to correct the address in FIT.
02 mCode Adrress - FFE88730 -> FFE88B30