Forum - RE: [Discussion] 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 204 of 335 � Page 1 ... 199 200 201 202 203 204 205 206 207 208 ... 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

#3046 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Jun 27, 2017 2:31 pm (Last edited: Tue Jun 27, 2017 2:37 pm)

@ampere
Why not give a try? I cross-flashed my DS3H to D3H and succeeded before, even if the 2 boards have different audio chip.
Also, with Gigabyte's DualBIOS, the risk of BIOS flash is minimized.

My current System(s):
Laptop: CLEVO P655SA, CPU: Intel Core i7-4720HQ, Disk Drives: Crucial MX200 250GB SSD + HGST 1TB 7200RPM, RAM: Kingston DDR3L 1600MHz 8GB*2, Graphics: NVIDIA GeForce GTX965M 2GB, OS: Win10 Education x64 + Ubuntu 16.04.5 LTS x64 + macOS High Sierra 10.13
Desktop: MB: GIGABYTE GA-Z77-DS3H, CPU: Intel Core i7-3770K, Disk Drives: Plextor M5S 128GB SSD + Western Digital 1TB 7200RPM, RAM: Kingston HyperX DDR3 1600MHz 4GB*2 at 1866MHz, Graphics: AMD Radeon R9 390 8GB, OS: Win10 Pro x64

This thread has been closed.

#3047 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Jun 27, 2017 3:23 pm

I've been looking around for a modded bios for my ga-x79-ud3 rev 1.0, but every mod bios i found does not mention if it is for rev 1.0 or rev 1.1.
If these are cross-flashable that would make sense. Latest i found is F21e beta mod rev3.

This thread has been closed.

#3048 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Jun 27, 2017 4:10 pm

rev1.0 and 1.1 share the same BIOS up to F16.

This thread has been closed.

#3049 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Tue Jun 27, 2017 6:34 pm

Yup that is sandy bridge,
Ivy Bridge-EP support starts from bios F20 for rev1.1
I'l pick up a e5-2660v2 somewhere and give it a try

This thread has been closed.

#3050 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Wed Jun 28, 2017 12:09 pm

UBU is featured in Germanys biggest IT News mag: https://www.heise.de/newsticker/meldung/...de-3755660.html :)

aka Velocet | Xeon E3-1230v3 @ ASUS Z87 Gryphon (mBIOS 3301)|
Samsung 960 Pro NVMe via kryoM.2 evo|ASUS GTX 650 Ti Boost OC

This thread has been closed.

#3051 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 3:43 pm (Last edited: Fri Jun 30, 2017 3:50 pm)

UBU 1.69 Update 1 Bug report.

When updating EFI RaidDriver on my Asrock Z270 Taichi, UBU adds a GUID EE4E5898- inside 91B4D9C1- after flashing RST is not available in the UEFI and can not boot either, had to boot using legacy ROM.
I saw this a while back, but forgot to report it, but also bobypf had the problem, so i'm reporting it now.

As it should be.

After UBU.

EDIT: the problem is that UBU removes the DXE Dependency Section.

This thread has been closed.

#3052 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 4:15 pm

@ Pacman

Give me a link to BIOS. I'll add Depex. :))

This thread has been closed.

#3053 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 4:28 pm

Well, this is the BIOS, but i have re-added the dependency section with UEFITool, so now it works.
But it would be great if UBU could re-add this section when updating, is it possible?

This thread has been closed.

#3054 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 5:13 pm (Last edited: Fri Jun 30, 2017 6:37 pm)

Oops! Error in UBU. I'll fix it now.

Added:
@Pacman
Please check 1.69.2. :)

This thread has been closed.

#3055 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 7:52 pm

Thank you, but there is still some problem, more testing needed, if i manually replace the PE32 image with UEFITool, it works, but not with UBU.
Maybe it has something to do with the original BIOS having a compressed section under GUID 91B4, but after mod with UBU it has a GUID defined section,
i don't know, but that seems to be the only difference.

I will do some more testing.

This thread has been closed.

#3056 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 8:03 pm

So I have a newer board, And I noticed this new option under NIC section

1 - Update Automatic Mode
- EFI LAN Intel Gigabit UNDI v0.0.17
- EFI LAN Intel PRO/1000 UNDI v7.4.36
C - Create file with Device ID
- OROM LAN Intel BootAgent CL 0.1.12
- OROM LAN Intel BootAgent GE 1.5.62/1.5.84
0 - Exit Main Menu

Now I updated one of my two NICs. but I am wonder how to use tyhe second option, as I see it creates two files
in the UBU directory. Do I need to rename these and put then in the NIC folder and rerun UBU?
How do I use the files created to update the remaining NIC?

This is my setup, as you can see one is updated already, And created two files named _BootAgentCL_156F.lom, and _BootAgentGE_15A0.lom.

3 - LAN OROM PXE and EFI UNDI - Intel, RTK, BCM, QCA
OROM Intel Boot Agent GE - 1.5.50
OROM Intel Boot Agent CL - 0.1.10
EFI Intel PRO/1000 UNDI - 7.4.36
EFI Intel Gigabit UNDI - 0.0.17

This thread has been closed.

#3057 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 8:15 pm (Last edited: Fri Jun 30, 2017 9:13 pm)

@ Pacman
Are you testing already modified or original?

Zitat
i don't know, but that seems to be the only difference.

If you use the original BIOS file, then the difference in the compression method. UBU uses LZMA compression. This is not critical. All the rest is obtained as in the original file.

@ f3bandit
[Discussion] UBU Tool related Questions, Reports and Suggestions (200)

This thread has been closed.

#3058 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 9:45 pm (Last edited: Fri Jun 30, 2017 9:53 pm)

Zitat von SoniX im Beitrag #3058
Are you testing already modified or original?

Already modified

EDIT by Fernando: The first one of the identical double posts and unneeded parts of the fully quoted post removed (to save space)

This thread has been closed.

#3059 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 9:53 pm

@ SoniX

Both, first i tested with a already modded BIOS dump, it didn't work, then the BIOS file downloaded from Asrock, modded it with UBU, updated to 15.7.0.2925, didn't work either.
It does work if i replace the body of the pe32 image in UEFITool.

In that case it does seem like the compression format is the reason, everything else is identical.

This thread has been closed.

#3060 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Fri Jun 30, 2017 10:46 pm

@ Pacman
It's strange that no one complained...

Ok. I will make changes to the EFI compression method. Will you test later?

This thread has been closed.

BIOS Company �

Page 204 of 335 � Page 1 ... 199 200 201 202 203 204 205 206 207 208 ... 335 Page �

Please enter a reason for warning.