@lordkag
Hello!
When a new version Z.Extractor?
Version 5 is not working correctly with the OROM VBIOS SkyLake. Defined as Haswell-Broadwell.
Do not extract VBT for GOP SkyLake.
Do not determined the new OROM LAN Intel PXE CL.
Question. What do you think. New OROM LAN Intel PXE CL can be a substitute for Intel PXE GE and new EFI LAN Intel Gigabit UNDI be a substitute for Intel PRO/1000 UNDI?
Hey SoniX,
Earlier today, I happened to ask Lordkag of something similar regarding the Extractor. Basically I reported a small bug and also the incompatibility of the new 1151 stuff. He told me that although some bugs of v5 were fixed when reported,
a) he hasn’t released a new version yet with those fixes (of course these "fixes" are not 1151-related since those were reported today) and
b) he doesn’t have much time to work on it at the moment because of the other tools that he has written recently (Image finder/editor at UEFI SPI images, Award extractor/dummy.bin insertion , GOPUpd etc)
Also, because of the fact that usually lots of manual research needs to be done when new things emerge (1151 in this case), it might take more time. It would definitely help him to have some things determined before implementing them to Extractor as it will save time.
I replied here with his answer so that he doesn’t have to repeat himself. Hope it’s ok.
Ok. We will wait.
A replacement Intel LAN PXE GE and UNDI PRO/1000 to new LAN PXE CL and UNDI Gigabit should be tested. We will seek testers.
Pretty much what Plutomaniac said. I had fixed Skylake and CherryView when it appeared, but got carried away with the other scripts. I will upload the version I am currently using and later edit this message with a changelog and related work.
Edit: reuploaded the file
What was changed:
- python is now searched in PATH variables, so no more editing the bat with its location
- I added a coloured output, to have a better separation of the sections. For the time being it is only used when cecho is present, but if you like it, I can default to use cecho when it is appropriate.
- SkyLake and CherryView
- LSI SAS2 MPT UEFI
- Intel Lan UNDI now has the 10GbE/40GbE/Gigabit tagging. For Pro/1000 I leave it blank, since it is the most common format. For Pro/Server I see it in Intel’s readme that it is PCI only version, as opposed to PCIe for all others, so this one is less likely to be found.
- UEFIExtract.bat now prints the name of extracted file.
- a few fixes in getting OROM version
- the ME 1.5M Firmware is now checked for data after 0x17D000, to not be cut anymore. A better extraction for all type of ME FW is planned.
- since AMD pushed the firmwares to coreboot, I now have corrected the extraction of IMC and XHCI. SMU and PSP is only changed with Mullins, will be corrected later.
- AMD hasn’t enforced a specific sets of rules for microcodes, which leaves the OEMs to add all sorts of padding. I now check the padding and cut where it is needed.
- they also have one microcode released on the 13th month, so I had to adopt their calendar.
- I also left three new options that I happened to use. One is “text” which tries to extract ASCII or unicode text from a file, but no dictionary or anything. Another is “dellhdr” that tries to unpack the hdr from XPS 13 2015. And the last is “nvrun”, which I needed to get some ROMs from Nvidia executables.
Yes, it is possible that Intel is planning to switch to this CL version. But I don’t see it as a replacement, more like an upgrade. It is still Gigabit, like PRO/1000. And it is very similar to 6.0.23 for instance.
Extractor v6.rar (1.21 MB)
Before I update my CPU MicroCode for Intel IvyBridge-E only, MMTOOL indicates that BOOT is
set to YES for all VOLs.
After I update, all VOL boots are set to NO
I am using an Asus Rampage VI Extreme Black ED. Motherboard (Intel 4960X ivy-bridge CPU) &
untouched clean bios ver 0701 from asus for modding
Is this a bug ? What does this flag do anyway ?
Can you make me a scripted LGA2011ibe_BOOT_YES.ffs with instructions ?
Thanks,
Biozzz
RAMPAGE-IV-BLACK-EDITION-ASUS-0701.zip (4.79 MB)
I used this tool today for the first time and WOW, was I impressed. It is the EASIEST mod I have been involved in, thank you SOO much to the Maker
EDIT by Fernando: This post has been moved to the UBU discussion thread. The other UBU thread (Guide & News) is just for the guide and for SoniX, when he is releasing a new UBU version.
@Sonix
Hi mate, I’ve tried UBU 1.24 ILT on my Maximus VI Extreme (Z87) and it works like a charm.
I’ll test the new Intel LAN OROM and EFI but no issues so far.
Thanks for your hard work.
EDIT by Fernando: This post has been moved to the UBU discussion thread. The other UBU thread (Guide & News) is just for the guide and for SoniX, when he is releasing a new UBU version.
I am new in here but have been using UBU for a long time, I want to report 2 system bios that I am having trouble with 1.24:
Asus Maximus VII Hero: http://rghost.net/7xHH7Np5r
Lenovo ThinkServer TS140: https://download.lenovo.com/ibmdl/pub/pc…fbkta8a_dos.zip
For Asus, the bios include Haswell and Broadwell CPU Microcode, and UBU only allows to choose one. Once chosen either Haswell or Broadwell, the other will be removed. Will UBU in the future support keeping both CPU Microcodes?
For Lenovo, this problem existed for a long time. It will NEVER update Option 1 (RSTe OROM and EFI SATA drivers). It does not give error messages when I choose any version and at the end it will still show the old version when doing a re-scan.
I hope my comment will shape the future version as many new motherboard will support both 4th gen and 5th gen Intel CPUs.
The Lenovo is a very odd one that I cannot explain why the behavior.
@ killer23d:
Welcome at Win-RAID Forum and thanks for your contribution!
I am pretty sure, that SoniX, the developer of the UBU tool, will reply to your report.
Regards
Dieter (alias Fernando)
I flashed the bios of my Asus Maximus VI Formula (Z87) after modding it with UBU v1.24 ILT, no problems so far. The new Intel LAN modules seem to be working just fine, I see no differences with the previous modules. I’m just wondering why did they update them…
Because microcode is read from the file at a GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1 (FIT). And if you push both the microcode it is necessary to recalculate the address in the FIT for the second microcode, otherwise it will not be found. Therefore, user is given the choice of a microcode update.
In this case, the files EFI IRST(e) and LAN UNDI are non-standard GUID’s.
Also 2 files OROM are also in non-standard GUID’s
IRSTe in E8FFA355-BCEA-49B6-B5B5-91CA1A7914F5
Intel Boot Agent iSCSI in 22D01A32-5668-4BC2-80C7-8BDFF1F83EA8
Therefore UBU they are not updated.
I recommend to update the necessary files manually using UEFITool.
Edit:
Also 3 file OROM VBIOS Haswell v2177 in GUID 4C757E60-AAD4-42FE-BDE8-AAB180DB3E61
Have you tried to load the operating system over the network?
These modules will be used on the new platform SkyLake (LAN Chip I219). Himself wondering why such an update.
Thank you for the clarification and I will work on it.
really you make me happy
@ popm:
Welcome at Win-RAID Forum!
This post has been moved to the UBU discussion thread. The other UBU thread has been designed just for the UBU guide and the presentation of a new UBU version.
Regards
Dieter (alias Fernando)
I decided not to upgrade the Lenovo because I moved to FreeBSD and is running AHCI with ZFS soft-RAID, thus upgrading the driver is not going to help me. Also, I am not too confident about doing this manually as there are too many UUID that are not in the usual name and I am afraid I might break something.
If Sonix you can update everything for me with the latest version (RSTe, LAN, VGA etc) and I can try to flash it and report back. This might be beneficial in the long run so that UBU can accommodate the new ThinkServer lines.
Thanks
@ SoniX:
I don’t know if you are collecting any CHV stuff but here is a Cherry Trail capsule image. Manual extraction is needed (Lordkag’s Extractor can detect most of them I guess) since it’s not a normal Intel SPI image.
The source is the only Cherry Trail device available, Microsoft Surface 3 (Intel Atom x7-Z8700).
surfaceuefi.1.50410.78.0.rar (2.64 MB)
Ok. I just need to know what your CPU ID and the version of the OROM VBIOS or GOP displayed. And also, to some version of IRST update 13.1, 13.5 or 14.0?
@lordkag
Put please, that you have at CloverView and CherryView.
I can not find my archives.
Thank you.
I ran dsmeg for CPU:
I can use 14.0 if that’s stable, otherwise I will do one step lower.