Win-Raid Forum (Drivers - Firmware - Modding) » BIOS Modding » BIOS Modding Guides and Problems » [ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions
RGhost still down.......thanks for mirror links.
Edit:
Download links working on RGhost,but ......main page is down.
Edit1:
Intel CPU Microcode (X99 system) 06F2 rev. 2D dated 2014/11/21
just an FYI for those updating 4790k microcode. TSX instruction is disabled when updating with the microcode that is in UBU. I had to update all others and flash again to get it back. pic attached, So in conclusion the second flash left the updated microcode intact but also added back the TSX instruction as seen in CPU-Z.

Zitat von SoniX im Beitrag #1349Zitat von antandshell im Beitrag #1348
ok so for devils canyon latest mc is 1c & supersedes 19 as shown in mm tool below.
Yes.
Added:
Microcode processor 06C1 and 06C2 are not needed. This engineering processors and almost never occur in sales for the casual user.
antandshell,
Intel disable TSX instruction long time ago .....
http://www.anandtech.com/show/8376/intel...leep-broadwelly
Not on devils canyon. It was the first Haswell to include the corrected TSX instruction & VT-D implemented.
http://www.extremetech.com/computing/185...ow-clock-speeds
http://ark.intel.com/products/80807/Inte...-up-to-4_40-GHz
Zitat von ex58 im Beitrag #1358
antandshell,
Intel disable TSX instruction long time ago .....
http://www.anandtech.com/show/8376/intel...leep-broadwelly
@SoniX
That Intel Lan sample was indeed 3.4.12, but for 10Gb. The strange part was that the pattern was also found in the header. What where the chances for that to happen?
I had a look at 10Gb and 40Gb. For 10Gb we can use "49006E00740065006C00280052002900200031003000470062004500" = "Intel(R) 10GbE" unicode; for 40Gb "49006E00740065006C00280052002900200034003000470062004500" = "Intel(R) 40GbE" unicode. I tested this on all my samples and all Intel_Lan_CD/PREBOOT.exe releases, it always works.
For 40Gb you can use [start_match - 0x23]. Samples are attached.
Are you sure that you want to add Intel GOP ValleyView support, which is for Bay-Trail = laptops/tablets? Because it is a mess, with versions as 7.0.x, 7.1.x, 7.2.x and probably 7.3.x soon and so on. I use a bunch of wild guesses in Extractor, but there is no reliable method of detecting the full version. And to this the x86/x64 separation and you get a wild picture. Samples attached.
I haven't yet looked at the code of UBU 1.9.0 or 1.10, but I noticed two errors:
- Broadcom UNDI is not updated, still at 16.2.2
- 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.![]()
Zitat von ex58 im Beitrag #1356Thanks ex58 for posting the Intel CPU Microcode for the X99 platform. How do you find out what the Intel CPU Microcode version is your BIOS you're using contains?
Edit1:
Intel CPU Microcode (X99 system) 06F2 rev. 2D dated 2014/11/21
I take it none of the modding tool available right now are able to mod the Intel CPU Microcode within the BIOS of the X99 platform?
Zitat von sinders im Beitrag #1361
Thanks ex58 for posting the Intel CPU Microcode for the X99 platform. How do you find out what the Intel CPU Microcode version is your BIOS you're using contains?
I take it none of the modding tool available right now are able to mod the Intel CPU Microcode within the BIOS of the X99 platform?
MMTool 5.0.0.0007
Zitat von antandshell im Beitrag #1359
Not on devils canyon. It was the first Haswell to include the corrected TSX instruction & VT-D implemented.
http://www.extremetech.com/computing/185...ow-clock-speeds
http://ark.intel.com/products/80807/Inte...-up-to-4_40-GHz
Your post is from July 2014 and my post from August 2014...so gues which info is newer.
Haswell-E: no TSX.....September 2014
http://us.hardware.info/reviews/5599/4/i...ions-but-no-tsx
Check all CPU and mostly they have TSX instruction :
http://ark.intel.com/products/series/751...sor-Series#@All
which is disabled by microcode.
Your post is about haswell-E? does not matter what date it is as we are discussing a 4790k . The cpu has a build date of 10/14 and shows tsx on every utility. Also every one reviewed shows tsx enabled. I searched for 4790k tsx disabled or removed and no hits....
Zitat von ex58 im Beitrag #1363Zitat von antandshell im Beitrag #1359
Not on devils canyon. It was the first Haswell to include the corrected TSX instruction & VT-D implemented.
http://www.extremetech.com/computing/185...ow-clock-speeds
http://ark.intel.com/products/80807/Inte...-up-to-4_40-GHz
Your post is from July 2014 and my post from August 2014...so gues which info is newer.
Haswell-E: no TSX.....September 2014
http://us.hardware.info/reviews/5599/4/i...ions-but-no-tsx
Check all CPU and mostly they have TSX instruction :
http://ark.intel.com/products/series/751...sor-Series#@All
which is disabled by microcode.
^
Good luck.
http://techreport.com/news/26911/errata-...-broadwell-cpus
TSX erratum:
http://www.intel.com/content/dam/www/pub...spec-update.pdf
Early BIOS's use early Intel Microcode,so in 4790K (ES and retail) review TSX is enabled.
TSX is disabled only for retail 4790K , by Intel Microcode in upcoming BIOS's.
Due to Erratum HSw136, TSX instructions are disabled and are only supported for software development.
Zitat von lordkag im Beitrag #1360And I'm confused in determining 10Gb or 40Gb of normal. :) I will make an additional check, and then by mistake, you can not replace the module. ;)
That Intel Lan sample was indeed 3.4.12, but for 10Gb. The strange part was that the pattern was also found in the header. What where the chances for that to happen?
I had a look at 10Gb and 40Gb. For 10Gb we can use "49006E00740065006C00280052002900200031003000470062004500" = "Intel(R) 10GbE" unicode; for 40Gb "49006E00740065006C00280052002900200034003000470062004500" = "Intel(R) 40GbE" unicode. I tested this on all my samples and all Intel_Lan_CD/PREBOOT.exe releases, it always works.
For 40Gb you can use [start_match - 0x23]. Samples are attached.
Zitat
Are you sure that you want to add Intel GOP ValleyView support, which is for Bay-Trail = laptops/tablets? Because it is a mess, with versions as 7.0.x, 7.1.x, 7.2.x and probably 7.3.x soon and so on. I use a bunch of wild guesses in Extractor, but there is no reliable method of detecting the full version. And to this the x86/x64 separation and you get a wild picture. Samples attached.
Of all the files GOP ValleyViev I only 7.0.xxxx. I would think, to introduce support for a replacement or not to enter
Zitat
I haven't yet looked at the code of UBU 1.9.0 or 1.10, but I noticed two errors:
- Broadcom UNDI is not updated, still at 16.2.2
- 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.
- LAN Broadcomm UNDI added later.
- It seems to work, but check again.
Thank you very much for the good advice. :)
Test the updated tools.
UEFITool v0.20.1
UEFIExtract v0.4.1
UEFIPatch v0.3.1
https://github.com/LongSoft/UEFITool/releases/latest
Zitat von ex58 im Beitrag #1362@sindersZitat von sinders im Beitrag #1361MMTool 5.0.0.0007
Thanks ex58 for posting the Intel CPU Microcode for the X99 platform. How do you find out what the Intel CPU Microcode version is your BIOS you're using contains?
I take it none of the modding tool available right now are able to mod the Intel CPU Microcode within the BIOS of the X99 platform?
Not so simple.
What motherboard? Attach the BIOS.
Important. There SPI-programmer?
Zitat von SoniX im Beitrag #1368As I have previously mentioned on the board, I have a ASUS Rampage V Extreme X99 board.
Not so simple.
What motherboard? Attach the BIOS.
Important. There SPI-programmer?
Here is the latest BIOS to date for the board.
http://dlcdnet.asus.com/pub/ASUS/mb/LGA2...E-ASUS-1001.zip
I don`t have a hardware SPI-programmer as yet thought I can still flash my modded BIOS using the BIOS USB
flashback feature because I have tested this out myself on my board when modding the BIOS with a
newer Intel RAID ROM module.
Thanks in advance for the help and feedback.
EDIT by Fernando: Unneeded quoted text deleted (to save space)
@sinders
Ok. Wait half an hour. Now gather FFS-files.