[ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

[mjgr33n]

@SoniX

Do it again mod, but using only original UBU.bat v1.29.
Flash and the last time check. We must make sure that it does not fail to assemble FFS-file.

Yes, I can confirm that using the original UBU.bat for v1.29 does not work, it fails to load the EFI network stack at bootup.

It does not fail to assemble the FFS-file as far as I can tell.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 

Enter number:3
 
        LAN OROM PXE and EFI UNDI  Intel, Realtek, BCM, QCA
 
1 - Update ALL LAN OROM and EFI:
    Intel LAN OROM 1.5.70 EFI version select
0 - Exit Main Menu
 
Enter number:1
 
1 - Update EFI Intel Gigabit UNDI v0.0.07 (Support 82579/i217/i218, test i210/i211)
2 - Update EFI Intel PRO/1000 UNDI v6.6.04 (Support all GbE chips)
0 - Skip update EFI Intel UNDI
 
Enter number:2
* Generate FFS Intel LAN UNDI GUID 4953F720-006D-41F5-990D-0AC7742ABB60 ... Ok!
* Update EFI Intel LAN UNDI GUID 4953F720-006D-41F5-990D-0AC7742ABB60 ... Ok!
* Generate Intel LAN PXE OROM Device ID 1502 ... Ok!
* Update OROM Intel LAN PXE Device ID 1502 ... Ok!
 
     OROM Intel Boot Agent GE   - 1.5.70
     EFI Intel PRO/1000 UNDI    - 6.6.04
Press any key to continue . . .
 

Thanks.

[plutomaniac]

@kevindd992002

And just curious, why isn’t MEI updating included in UBU? No pun intended here.

Because of OEM settings that need to be transferred via FITC manually. Also, UBU works with SPI regions such as BIOS but the ME one is most of the times locked via the Flash Descriptor so in the end it wouldn’t get updated on such systems. Too much work for too few results. Manual checking is way faster.

[SoniX]

@mjgr33n
Fine! Thank you very much.
I will put you within a single file, if you will not be difficult, then take the last test?

[mjgr33n]

@SoniX

@mjgr33n
Fine! Thank you very much.
I will put you within a single file, if you will not be difficult, then take the last test?

Sure, but I will test tomorrow morning, thanks ))

[SoniX]

@mjgr33n

Sure, but I will test tomorrow morning, thanks ))

No problem.

GA-Z87X-OC Force BIOS F10b - mod only EFI LAN Intel PRO/1000 v6.6.04 and OROM v1.70
Updates made in UBU v1.29.1
The result is only "works" or "does not work".

[Jest]

There seems to be something wrong with updating procedure EFI AMD GOP Driver in UBU1.29 for ASRock QC5000M.
With 1.27 works fine.

[SoniX]

@Jest

There seems to be something wrong with updating procedure EFI AMD GOP Driver in UBU1.29 for ASRock QC5000M.
With 1.27 works fine.

Yes, there is a problem. I corrected in the near future.

Edit:
@Jest
Fixed in UBU v1.29.1

[javanse]

Hi SoniX, after updating the ROMs of my Asus P8Z68-V Pro 3603 Bios with latest UBU 1.29, there’s an error message when loading the PXE ROM while booting.

Instead of loading the Intel PXE 1.5.70, i get the error message “PXE-E01: PCI Vendor and Device IDs do not match!” and then the board continues to boot.

Full Device ID of the Intel 82579V according to windows device manager is “PCI\VEN_8086&DEV_1503&SUBSYS_00008086&REV_05”.

I also noticed a strange behaviour when updating the CPU microcode for the same bios: when i skip updating any microcode, it actually gets deleted from the bios file instead of being skipped.

Thanks for this great program, and keep up the great work.

[Fernando]

@ javanse:

Welcomeat Win-RAID Forum!
Just for your inforation: I have moved your post into the correct UBU discussion thread. The other one is just for the UBU guide and the announcement of a new UBU version.

Regards
Dieter (alias Fernando)

[mjgr33n]

@SoniX

GA-Z87X-OC Force BIOS F10b - mod only EFI LAN Intel PRO/1000 v6.6.04 and OROM v1.70
Updates made in UBU v1.29.1
The result is only "works" or "does not work".

Works.

Please use F10 final for further tests though not F10 beta, thanks ))
http://www.mediafire.com/download/289ilz…/Z87XOCF.10.zip

[SoniX]

@mjgr33n

Works.

Fine! Thanx.

Please use F10 final for further tests though not F10 beta, thanks ))

So far, with tests completed.

[mjgr33n]

@SoniX

So far, with tests completed.

Great

[SoniX]

@javanse

Hi SoniX, after updating the ROMs of my Asus P8Z68-V Pro 3603 Bios with latest UBU 1.29, there’s an error message when loading the PXE ROM while booting.
Instead of loading the Intel PXE 1.5.70, i get the error message "PXE-E01: PCI Vendor and Device IDs do not match!" and then the board continues to boot.
Full Device ID of the Intel 82579V according to windows device manager is "PCI\VEN_8086&DEV_1503&SUBSYS_00008086&REV_05".

Before modification v1.3.72:

After modification v1.5.70:

As you can see from the screenshots, assembly Vendor ID and Device ID going right.
I do not know why you have such a problem. I only assumptions. Fault time modifications or flashing BIOS or version 1.5.70 are not compatible, which is very strange and unlikely.

I also noticed a strange behaviour when updating the CPU microcode for the same bios: when i skip updating any microcode, it actually gets deleted from the bios file instead of being skipped.

All microcode stored in a single file GUID 17088572-377F-…
Replacement made the entire file rather than individual microcode.

[SoniX]

@mjgr33n

Zitat von SoniX im Beitrag #1773

---

So far, with tests completed.

Great

---

Check out our the results in UBU v1.29.1

[mjgr33n]

@SoniX

Check out our the results in UBU v1.29.1

YAY, worked great thanks )))

[asrlab]

Hi Sonix,
In the version 1.29 and 1.29.1 is present an bug for replace module AMD AHCI 4391

[SoniX]

@asrlab

Hi Sonix,
In the version 1.29 and 1.29.1 is present an bug for replace module AMD AHCI 4391

Fixed in UBU v1.30

[asrlab]

ok changed, now works!

Thank you

[gtishtar]

for the amd orom vbios and efi gop driver, i got file can’t be opened message. not sure if it’s normal. the bios i try to update is gigabyte f2a78m-d3h. bios version “FB”

[SoniX]

@gtishtar

for the amd orom vbios and efi gop driver, i got file can’t be opened message.

Fixed in UBU v1.30