Forum - RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions

Win-Raid Forum (Drivers - Firmware - Modding) � BIOS Modding � BIOS Modding Guides and Problems � [ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

Page 35 of 335 � Page 1 ... 30 31 32 33 34 35 36 37 38 39 ... 335 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#511 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Tue Jun 24, 2014 10:37 pm

@SoniX

Many thanks for the version and the files. Meanwhile, I had a look at Fischer's file. It is not a bug, it is a feature. And I'm not joking. In this post is the explanation. Fischer has one OROM linked to 3 IDs. While the normal anchor is 20 00 VID DID, the linked one looks like 0[x] A0 VID DID - where x is number of OROMs from base 0.

The solution is this:

The same goes for Intel RSTe SCU:

A workaround would be to strip the first 00, but then you will run into this case.

This thread has been closed.

#512 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Wed Jun 25, 2014 2:13 am

Hi Fernando,

I did it that way, using the flashback routine...however, UBU did already renamed it automatically into the CAP...so far BIOS works OK, will report back with overall experience. The issue with standard BIOS is, well...something isn't right...the machine doesn't works well, and I am unable to boot any flavor of Linux...which is a must for me!!!
Thanks

Asrock Z87 Fatal1ty Professional * Intel i7 4790k * G.Skill TridentX 16gb 2400MHz * RAID 0 [2XOCZ Vector 128GB] * RAID 5 [3XToshiba DT01ACA300]
Asus Z97-Pro WiFi[ac] * Intel i7 4790k * G.Skill TridentX 16gb 2400MHz * RAID 0 [2XOCZ Vector 128GB]

This thread has been closed.

#513 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Wed Jun 25, 2014 2:19 am

Zitat von lordkag im Beitrag #558

The solution is this:

The same goes for Intel RSTe SCU:

A workaround would be to strip the first 00, but then you will run into this case.

Oh, yes! It really works. I'll have to add in the following versions of UBU. Many thanks for the tip. :)

This thread has been closed.

#514 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Wed Jun 25, 2014 9:50 pm

Hi all!

I have a problem with all versions of UBU Tool. My MB is ASRock B75M R2.0, and when I flash the original BIOS, I could check for BIOS update from within BIOS itself, but, when I try to do the same with UBU modified BIOS, I get just frozen BIOS, and only thing that I can do is to hard reset the PC.
These are the modules in original BIOS:

This thread has been closed.

#515 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Thu Jun 26, 2014 3:18 am (Last edited: Fri Jun 27, 2014 10:27 am)

Linux* Processor Microcode Data File 20140624

https://downloadcenter.intel.com/Detail_...8&DwnldID=23984

New microcode for Ivy Brigde,Ivy Brigde-E, (Haswell..as posted earlier).

Edit:
New microcode for Ivy Brigde:
Date: 2014/05/29
MC ID: 0306A91B
CPU Id: 06A9
Revision: 1B

New microcode for Ivy Brigde-E:
Date: 2014/05/29
MC ID: 0306E4428
CPU Id: 06E4
Revision: 428

New microcode for Ivy Brigde-E:
Date: 2014/05/29
MC ID: 0306E770D
CPU Id: 06E7
Revision: 70D

ex58 has attached files to this post

Z590/490/390 AORUS Master
Z370 AORUS Gaming 7,
GA-Z170X-SOC Force ,
GA-Z97X-SOC Force ,Core i7-4790K ,G.Skill F3-2933C12D-8GTXDG
2xSSD Corsair Force GS 128 (RAID 0), WD Caviar Black 1TB
Win 7 SP1 x64;Win 8.1 x64 ;Win 10 x64

This thread has been closed.

#516 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 6:27 am

Zitat von ex58 im Beitrag #562
Linux* Processor Microcode Data File 20140624

https://downloadcenter.intel.com/Detail_...8&DwnldID=23984

New microcode for Ivy Brigde,Ivy Brigde-E, (Haswell..as posted earlier).

Edit:
New microcode for Ivy Brigde:
Date: 2014/05/29
MC ID: 0306A91B
CPU Id: 06A9
Revision: 1B

New microcode for Ivy Brigde-E:
Date: 2014/05/29
MC ID: 0306E4428
CPU Id: 06E4
Revision: 428

New microcode for Ivy Brigde-E:
Date: 2014/05/29
MC ID: 0306E770D
CPU Id: 06E7
Revision: 70D

The microcode for MC ID: 0306A91B you posted is incorrect! It does not get recognized by AMI Tools.
If you check with hex editor you will see that the last 16 bytes are duplicated.
Delete data from offset 0x3000 - 0x300f and mc gets recognized - file size exactly 0x3000h.

This thread has been closed.

#517 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 9:09 am (Last edited: Sat Jun 28, 2014 9:14 am)

@Sonix:
While modding bios for Zotac ZBOX ID18 I got the following message (see attached).
Bios can be downloaded from here: http://www.zotac.com/products/mini-pcs/z.../downloads.html

Should be this module:
|160|RTLLanx64 |5E53CBEB-C4E1-4393-B8FB-7267A118CB1E|0051FBA7|01550D|DRVR|

mictlan has attached images to this post

sonix.png

This thread has been closed.

#518 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 11:14 am (Last edited: Mon Jun 30, 2014 9:57 pm)

Zitat von mictlan im Beitrag #564
@Sonix:
While modding bios for Zotac ZBOX ID18 I got the following message (see attached).
Bios can be downloaded from here: http://www.zotac.com/products/mini-pcs/z.../downloads.html

Should be this module:
|160|RTLLanx64 |5E53CBEB-C4E1-4393-B8FB-7267A118CB1E|0051FBA7|01550D|DRVR|

Verify.
Update MC IB and IB-E
Update GUID 5E53CBEB for EFI LAN Realtek
Rename files MC.
Added support video ASPEED type and version (OROM only)
Work continues. :)

Unpack the top of version 1.6.1.

@ Fernando
This is not the official version, it does not need to be declared.

This thread has been closed.

#519 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 11:48 am (Last edited: Sat Jun 28, 2014 11:49 am)

Zitat von SoniX im Beitrag #565
Zitat von mictlan im Beitrag #564
@Sonix:
While modding bios for Zotac ZBOX ID18 I got the following message (see attached).
Bios can be downloaded from here: http://www.zotac.com/products/mini-pcs/z.../downloads.html

Should be this module:
|160|RTLLanx64 |5E53CBEB-C4E1-4393-B8FB-7267A118CB1E|0051FBA7|01550D|DRVR|

Verify.
Update MC IB and IB-E
Update GUID 5E53CBEB for EFI LAN Realtek
Rename files MC.
Added support video ASPEED type and version (OROM only)
Work continues. :)

Unpack the top of version 1.6.1.

@ Fernando
This is not the official version, it does not need to be declared.

Wow, that was fast

Added RTLUndi with AMITool manually and ran UBU after it (Test on hardware can be done next week)

mictlan has attached images to this post

sonix2.png

This thread has been closed.

#520 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 2:29 pm

Zitat von mictlan im Beitrag #563

The microcode for MC ID: 0306A91B you posted is incorrect! It does not get recognized by AMI Tools.
If you check with hex editor you will see that the last 16 bytes are duplicated.
Delete data from offset 0x3000 - 0x300f and mc gets recognized - file size exactly 0x3000h.

You can try yourself.....download original file from Intel page and extract with microdecode.exe.
Will be interesting to see what you will get.

This thread has been closed.

#521 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 5:51 pm (Last edited: Sat Jun 28, 2014 5:52 pm)

@Sonix: There is some verify needed in order to check the Rev 1B of the Ivy Bridge

Guys don't integrate Rev. 1B for Ivy Bridge because there are some problems...I've done it with the latest UBU 1.65 Beta on the F12J of the Gigabyte Z77X-UP5 TH and it has bricked my main BIOS.
The MoBo made and endless mini-boot and suddenly shut down until i stopped it manually.
Thankfully Gigabyte has a solid routine that detect the corruption of the main BIOS and overwrite it with the backup-BIOS and now everything is fine.

This thread has been closed.

#522 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 7:20 pm (Last edited: Sat Jun 28, 2014 7:41 pm)

Zitat von killkernel im Beitrag #568
@Sonix: There is some verify needed in order to check the Rev 1B of the Ivy Bridge

Guys don't integrate Rev. 1B for Ivy Bridge because there are some problems...I've done it with the latest UBU 1.65 Beta on the F12J of the Gigabyte Z77X-UP5 TH and it has bricked my main BIOS.
The MoBo made and endless mini-boot and suddenly shut down until i stopped it manually.
Thankfully Gigabyte has a solid routine that detect the corruption of the main BIOS and overwrite it with the backup-BIOS and now everything is fine.

I insert it (manually) to my ASRock Z68Ext3 and no problems.
Manually (using AMITool) integrated ucode from UBU 1.65 - looks ok.

Edit: I see why it bricked: Checksum in module not correct.
Attached module with correct checksum. Should work ok.
Look up file name in ubu, rename attached file to it and let ubu insert it.
https://www.sendspace.com/file/7gx48k

This thread has been closed.

#523 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 11:11 pm

Zitat von mictlan im Beitrag #569

Edit: I see why it bricked: Checksum in module not correct.

These checksums MMTool forms and never had problems.

This thread has been closed.

#524 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Jun 28, 2014 11:20 pm

@SoniX

It is possible that the new Asmedia OROM is for 1062 or 1062R. I see here that they should have 4 controllers, but here it seems that they share the same ID, even though it should be 1B21:0611 for 1061, 1B21:0612 for 1062. From a quick look for asm1062, it would seem that there are a few boards with 1062/1062R controller: Crosshair V Formula, Z77 Pro4, Z87 Extreme6, Z97-A with 1062R, Asus Hyper Express with 1062R. If you can get a user with any of these boards to test this new OROM/firmware, maybe we would know for sure. In fact, any user with Asmedia controller should visually check his board: if he sees a Asmedia ASM1062/ASM1062R, he can test it.

@mictlan

Your changes don't make any sense. You first changed the EFI_FFS_FILE_ATTRIBUTES, but in a wrong way. Usually 0x08 is for dummy microcodes and 0x48 for full microcodes (but they can also be found reversed). Then you calculate a bad module checksum - it should be 00 for entire module, yours is 03.

Sonix has done everything right. If there is a problem, it is either in the microcode itself or in the process of replacing. If one user reports a fail, while other(s) report a success, I would say it is the later case.

This thread has been closed.

#525 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Jun 29, 2014 12:10 am (Last edited: Sun Jun 29, 2014 3:28 pm)

@lordkag
Ok. Made a request to the specified motherboard is, I hope that someone will respond. Honestly, this version is already intriguing 3.xx. :)

Add
@lordkag
Chip: asmedia/ASM1061/BG644101A2/1143
OROM v3.070 not working.
Waiting for someone on board ASM1062(-R).

This thread has been closed.

BIOS Company �

Page 35 of 335 � Page 1 ... 30 31 32 33 34 35 36 37 38 39 ... 335 Page �

Please enter a reason for warning.