@ Fernando
Some free space can be obtained by removing the modules LAN OROM and EFI. They are not used by home users.

@ SoniX:
Thank you for the file and for explanation.
I was thinking, if i update Intel VGA ROM my problems would be soöved (perhaps).
I did not know, that (if i have UEFI installation of for example Windows 8.1) the ROM is not used.
(Maybe offtopic): so only Intel drivers in the OS (in my case Windows 8.1 drivers) are used?

I have a CPU Microcode in my 2.1 BIOS version, that does not allow overclocking (for example all Cores Turbo).
In older Bios this was allowed, but not anymore. So only thing is: if newer CPU Microcode would have any benefits (except support for newer CPUs).
Is there a changelog of CPU Microcode? I have right now the Microcode version 9.

@Fernando:
Yes in future this will be a problem. Maybe we will have some tool for automatically deleting those unneeded logos etc. from BIOS in the future

I also wroite an emial to ASRock and asking if there is any way they would give us the tools (or at least information we would need) to update the modules easily without the need to wait for a new BIOS version, if it ever comes out.

@ PKOneTwo
You can not just go and update the OROM VBIOS in the BIOS. First you have to configure the VBIOS, otherwise you can get a "blank black screen", that is not the image on the screen.
Then for sure. Version 7 CPU microcode is not blocked from overclocking.

Zitat von SoniX im Beitrag #1350

---

@ PKOneTwo
You can not just go and update the OROM VBIOS in the BIOS. First you have to configure the VBIOS, otherwise you can get a "blank black screen", that is not the image on the screen.
Then for sure. Version 7 CPU microcode is not blocked from overclocking.

---

Zitat von PKOneTwo im Beitrag #1351

---

I know, i read it in the UBU guide.
My problem just was if i would benefit from updating the INTEL VGA. And as you both mentioned: i would not benefit, because i have UEFI installation (so no difference for me), right?

---

Zitat

---

CPU Code: Yes, version 7 was last one. I have now 9. Only question is: wqoul di benefit from updating to newer one? i can't find changelogs from one version to another (like from 9 to newest)

---

Almost no information. We only know that after 7 version is locked overclocking and starting with version 1A - disabled TSX.

I think in future versions UBU, for LGA1150 processors Haswell worth adding 2 CPU microcode update?
07 - êàê do allows CPU overclocking without the index "K" and 19 - where TSX instructions - enabled,

Good news.
Then i'll wait and give it try in the future.
As you said, right now no use for me.

Thank you all for your help.
Maybe future versions of UBU will have a slution built in for BIOSes like Asrock with "insufficient space" error

Zitat von PKOneTwo im Beitrag #1354

---

Maybe future versions of UBU will have a slution built in for BIOSes like Asrock with "insufficient space" error

---

@SoniX

I hope you take this with the same amusement as I did: this time, I see you forgot Broadcom EFI for good; you must be really upset with them.
MMTool5 doesn't see OROMs from 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9. Take X99 WS-E10G for example. Nothing you can do.
Found ASMedia AHCI 3.80 in this Biostar board = GAMING Z97X. Maybe this one works with onboard?

And since this is a short message, other notes from me:
- a few changes to work with new UEFITool releases.
- Added Nvidia GOP detection, since I have found one HP image with Kepler and Maxwell GOPs.
- Detection of all OROMs, compressed or not. Using UEFIFind to get a list of GUIDs, from which I exclude duplicates and already extracted OROMs or known CSM GUIDs. This works pretty well, it even found some OEM-specific OROMs used by HP or Insyde. Every OROM starts with 0x55AA (little indian from AA55), followed by size in paragraphs, then a call to init (jump, jump short or call).
- added info for FIT table.

@plutomaniac
2.59 do as 259, or even remove the numbers.

Zitat von plutomaniac im Beitrag #1359

---

Zitat von SoniX im Beitrag #1358

---

2.59 do as 259, or even remove the numbers.

---

I have removed the numbers temporarily but shouldn't UBU detect only files? That's a folder, that's why I mentioned it.

---

UEFITool 0.20.2 | UEFIExtract 0.4.2 | UEFIPatch 0.3.2 now available !

https://github.com/LongSoft/UEFITool/releases/tag/0.20.2