Zitat von 100PIER im Beitrag #1370

---

I have done modded tests again.
If I take the ORIGINAL ASUS 2104 BIOS (18September2013) and make a modd with UBU V 1.10.2 the 3 modules are properly detected and modded BIOS works fine. OK.
But If you take the original ASUS 2104 BIOS and make a modd with UBU V 1.9.1 and then modd again the obtained BIOS but using the UBU V 1.10.2 you should have the '2 modules' only problem I reported you.

---

Hello there,

I updated all possible modules include CPU microcode with UBU 1.8.X and it works like a charm since.
My questios:

Is there some advantage to mod my bios with latest iteration of UBU since there are
some update algorithm changes, but there are no newer module versions for my mobo.
My mobo: ASUS P8Z77-V PRO, moded bios 2104, MEI v8.1.52.1496

Is possible to lost some bios functionality due to biosmod ? I apparently lost possibility to save
bios profile. To be exact, i can save profile to usb/hdd but if i try to load profile from usb/hdd bios freezes and i have to
hard reset PC. Loading bios profile works ok from bios. Hope asus owners do understand what i mean.

PS: I appreciate work put in to this forum. Valuable souce of information. Keep up good work.

Hi all, I have a question. ASUS just released a new bios and the change log says 1.Support 5th-Generation Intel Core Processors. But when i look at the versions in the MM tool it is the same as the prior version and does not show any new micro code in the newer bios...Pic is below...I am viewing this correctly? They also still have not disabled TSX instruction as both contain update revision 19 right? TY for the help..

[img][/img]

antandshell,

Hello, Far i know i have maximus 7 hero its uses on bios and in boot v19 microcode but if its get to windows its use 01C ASUS mobos have rog1 and rog3 if something else prase them if bios update contain someting newer its use this newer. In werid option its use in boot 19 and in windows 01C microcode in windows but in ubu its never show up i have TSX disabled with bios witch released some days ago. i not used UBU to update microcode in latest bios.

Hi Margus,

I seen it updating rog 1 & 3 after the bios update but i had no idea what that was. I kind of get what you are saying but if you open cpuz will it show TSX on yours? can you post a screen shot of cpuz?

Thank you,

Anthony

Zitat von Margus im Beitrag #1374

---

antandshell,

Hello, Far i know i have maximus 7 hero its uses on bios and in boot v19 microcode but if its get to windows its use 01C ASUS mobos have rog1 and rog3 if something else prase them if bios update contain someting newer its use this newer. In werid option its use in boot 19 and in windows 01C microcode in windows but in ubu its never show up i have TSX disabled with bios witch released some days ago. i not used UBU to update microcode in latest bios.

---

@lordkag

I am in some confusion. The main source files S-D
EFI Broadcomm v16.8.5 Version Offset from UNDI_VER 0x1CA
OROM Broacomm v16.8.0
What does Broadcomm to the company Hewlett-Packard???
In OROM and EFI files contains Hewlett Packard or HP.

Added:
By the way, I know. You do not come across a more recent version of the firmware for the NEC USB3.0 than the attached file?

Added2:

Zitat von lordkag im Beitrag #1292

---

- you need to change the lines from 106-109 to the ones bellow. You need %%~nxi because %%i will give you the full pathname and you are trying to use a local variable as a global.

---

cpu-z shows nothing about tsx

If i go to bios under cpu tab shows that its use microcode 19 if i boot to os and open xtu or cpu-z nothing is about tsx.
I wonder if i open new bios with ubu there i not found new microcode all is 19 but xtu found that i use microcode 0x1C its putted that microcode somwere unknown location.

@Fernando
I detect a download problem from the forum link site:

Why this problem ?
However, No problem to download from the Developper link site.
Regards

I thank you for the information. Do you know what the differences are for microcode 06C31A and 06C31C . According to Intel Processor identification utility my cpu has 06c31A code. So Cpu-z must be reporting incorrectly.

Zitat von ex58 im Beitrag #1323

---

Zitat

---

I understand everything you are saying. I was aware of the issue and when i got the chip i was very surprised to see the extension enabled. I even updated to latest asus bios 2012 for my mobo which was dated 10/17/14 and tsx was still there. I am going to ask Intel on there forums as I thought the same thing as you do until i seen so many posted with extension listed.

---

OK,
I can confirm that TSX instruction is still enabled with Microcode 06C319.
Disabled is with 06C31A and 06C31C.

---

@SoniX

I have noticed the same thing about latest Broadcom files. I think that HP just rebranded the OROMs, nothing more. This is my take on them:
- the EFI is clean. It is signed by Microsoft and I doubt Broadcom or Microsoft would allow a third party in the process. There are some rules in the EFI world.
- the OROMs are rebranded. I think that the code is still the same, just that address relocation took place during compilation, because the HP sign-on message is bigger. You can see this in the files attached, where Broadcom 16.2.1 folder has files from official Broadcom_Ethernet_Software_Kit_16.2.4.1, from normal Broadcom release and HP release. While 1a=1b and 3a=3b, 2a is a little different from 2b. Can you ask someone with Broadcom Lan to test this new 16.8.5 OROM? He/she should just enable Lan Boot and make it the first boot option. If the PXE screen appears and there is an attempt to load a remote OS (with the expected failure), then the file is good on all boards.
- the version does appear the be all over the place. Here is a new method: if the next byte after 554E44495F564552 is NOT 00, then the version follows the pattern. If the first byte after pattern is 00, then start from 0x110 after pattern and test if the version is not 000000 and that 21 bytes of 00 follows.



Found AMD 7.0.0-00085 in this HP. Again, they updated only the first ID, but the second ID can be obtained really easy.

There is a problem with Intel Ivy GOP 3.0.1006, which is seen as Sandy GOP.

I did found a few months ago a Nec-Renesas uPD720201-202 USB3 Firmware 2.0.2.6 (K2026090.mem) in a Lenovo BIOS. It has a full header, which means it can be used with NEC flashers.

Zitat von lordkag im Beitrag #1380

---

Broadcom - HP LAN OROM 16.8.5.

---

Zitat

---

Found AMD 7.0.0-00085

---

Later added to UBU.

Zitat

---

There is a problem with Intel Ivy GOP 3.0.1006, which is seen as Sandy GOP.

---

Oops! This problem and the version 3.0.1003. I'll fix DrvVer.

Zitat

---

I did found a few months ago a Nec-Renesas uPD720201-202 USB3 Firmware 2.0.2.6 (K2026090.mem) in a Lenovo BIOS. It has a full header, which means it can be used with NEC flashers.

---

Flashed my NEC USB 3.0 discrete controller. All is well. Used files from the update package from here. All works well! :) Can also try to make one deployed by module-based update file version 2.0.2.4, and put on Station-Drivers.

There is a new Broadcom Ethernet Software Kit Version 16.8.4.1 Gold at Station-drivers.com
If you can check it.

Thanks