[Offer] Intel Sandy/Ivy Bridge and Haswell VBIOS modules

Fernando · August 22, 2013, 5:01pm

also for H67 pls…

AFAIK the latest VGA ROM module for Sandy/Ivy Bridge IGPs is v2158 dated 11/23/2012, for Haswell IGPs the latest is v2177 dated 07/25/2013. You can find them within the start post of >this< thread.
Regarding the GOP "Driver" modules for Intel IGPs I don’t know the latest version.

EDIT: SoniX just has answered your question while I was writing my post. Thanks!

SoniX · August 22, 2013, 5:56pm

@Fernando
EFI GOP Driver iGPU
SanIvyGOP.rar 2.0.1024/3.0.1023 For Sandy/Ivy proc
HaswellGOP.rar 5.0.1034 (Thanx Pacman) For Haswell proc
I think may add to the first post?

PS More new not yet found.

HaswellGOP.rar (25 KB)

SanIvyGOP.rar (29.7 KB)

Fernando · August 22, 2013, 6:33pm

@ SoniX:
Thanks for the attached EFI iGPU GOP Drivers.
Yes, I agree with your idea to present them at a better visible place.
Question:
Into the first post of which already existing or new thread shall we add them?
These are the options:

Pacman changes the title of this thread to “Intel iGPU GOP Drivers” and modifies the content of the first post.
You start a new thread titled “Intel iGPU GOP Drivers” (or similar) and put the links and some instructions regarding the replacement/insertion of these modules into the start post.
I rename >this< thread to "Actual BIOS modules (not AHCI/RAID related) and add the Intel iGPU GOP Driver files you have posted.

I would prefer the second option. What do you think?

Pacman · August 22, 2013, 7:31pm

Just wanted to say, i agree with Fernando, probably better to start a new thread.

SoniX · August 22, 2013, 9:34pm

Make a new one. This leave for the tests.

Fernando · August 22, 2013, 10:55pm

Will you do it?

SoniX · August 22, 2013, 11:36pm

Will you do it?

Oh. … No. Thank you.

I have not enough time for that. Make a better place for all.

Fernando · August 23, 2013, 12:04am

Oh. … No. Thank you.
I have not enough time for that.

Ok, then I will do it within the next days.

How do you mean that? One single thread with all BIOS modules (AHCI/RAID ROM, other PCI ROM modules, SataDriver, GOP Driver, CPU MicroCode etc.)?

SoniX · August 23, 2013, 1:02am

It is necessary to think a…

Update
Until we leave as is. This thread rename as "Intel Sandy bridge and Haswell/Ivy VBIOS differences. Testing.", to check for new versions. And audited (working) modules into this thread "Actual PCI ROM modules (not AHCI/RAID related)".

Fernando · August 23, 2013, 3:20pm

@ SoniX:

Meanwhile I have renamed and customized the start post of >this< thread and added the Intel GopDriver modules you had linked.
This evening I will add some infos regarding the replacement and insertion of the GopDriver modules. AFAIK the procedure will be the sae as with the SataDriver modules. Am I right?
Please check, if everything is ok (inclusive the download links). If not, please send me a PM.
By the way: I have renamed the original SandyBridge GopDriver module and hope, that it is correct what I have done.
Thanks again for your support.

Regards
Fernando

mindwarper · September 10, 2013, 6:10pm

MMTool crash because he meets 2 empty modules.
1) Open MMTool and Load Image
2) Delete Vol 01 Ind 00 and Vol 02:01:02 Ind 02 modules (GUID 17088572-)
3) "CPU Patch"

@Sonix or @Fernando or anyone else that may help

This is interesting

Thanks for the heads up on this, but I have additional questions…

I’ve found the GUID mentioned in the Volume 00 Index 01 and another in Volume 02:01-02 Index 02 just as like in the mentioned information for the BIOS of ASRock’s Z87 Extreme9/ac for example…

Now I am curious…
I can delete them safely and then update the microcode patch?

Or do I do these steps?
1. extract them one by one starting the way down from GUID 17088572- in as-is mode or uncompressed mode?
2. delete them one by one
3. do the microcode patch update (Haswell rev 12)
4. then re-insert the previously deleted with the extracted modules

Or can I just go on after I deleted the empty modules with the GUID and leave them out subsequently?
Does it harm the UEFI BIOS in any way if you leave them out…?

In other words how can I re-insert the previously deleted empty gaps (GUID 17088572-) at the same location again, without any trouble/huge work?
Please elaborate, if you can…

You know it is a lot of work to extract them (especially in the main Volume 02:01-02 in my case) first, as you have to do them in order to get them back later in same order.
Thanks again on your help on this…

Fernando · September 10, 2013, 9:34pm

@ mindwarper:
Welcome at Win-RAID Forum!

Since I am not an expert regarding your topic, I hope, that you will get an answer from SoniX or Pacman.

Regards
Fernando

Pacman · September 10, 2013, 10:03pm

@mindwarper
My Maximus VI Gene, only has one instance of the 17088572 module, Vol. 04 ind. 02, i just delete it, then insert the new microcode and delete the old revision.
I don’t Think there is any need to re-insert those modules.

There is also a new microcode, rev. 16. For Haswell Only.

Here is the bin file, if you want.
http://www.mediafire.com/download/06ickj…306c3_Rev16.zip

mindwarper · September 11, 2013, 2:21pm

@Pacman

Thanks for the update and the information about that you actually leave the empty gap module out after updating the microcode

But I feel to re-insert them would be a good idea, but then in deed they get re-inserted at the bottom of the Volume…as you cannot specify the Index
Better yet is to get them re-inserted at their original location… But again I would like that to be not as much work as I think it is now… There has to be a solution that does not imply that much tedious work…
But nevertheless thanks for your info!

Remco · September 12, 2013, 4:27pm

I successfully replaced the microcode update (16) in a Sabertooth Z87 bios (1405).

MMTool didn’t show the microcode patches in the cpu patch tab, until I removed said module (17088572).

Flashed and all working now.

Pacman · September 13, 2013, 4:33am

@mindwarper
Deleting and re-inserting the modules at the index they were Before i think would be a bit complicated, but here is Another way, if you are still interested.

First, if you feel unclear about any of this, ask Before trying.

This way will the BIOS exactly as it was, but with new microcode, quite simple way but i tried it on my Maximus and it worked.
Load your BIOS file in MMTool
Extract the 17088572 modules, Vol. 01 ind. 00, Vol 02 ind. 02, even though i Think they are identical, extract the first to file “1.ffs” and the other to "2.ffs"
Then replace both 17088572 mod with one of the “.ffs” files i have attached, and click “CPU Patch” delete old MC rev. insert the new, go back to "Replace"
and replace the two files you inserted with the 17088572 modules you extracted before, then save image.

This way works because the two problematic MC modules are not there anymore when you go to “CPU Patch”, it is like they were deleted, but then they can be “re-inserted” at their original location.
The attached files are just some random FFS files i have that are about the same size as the 17088572 modules.

Of course, even though i have tried this on my motherboard, and it worked, i can not give you any guarantee that it will work for you, but i don’t see why it shouldn’t.

ffs.zip (79.3 KB)

error-id10t · September 14, 2013, 1:55am

Thanks for the hint above.

The 1st time I updated to v12, I didn’t put the 2 files back and all appeared ok. The 2nd time I updated to v16, I put them both back to the right Volume but of course there’s no way to define Index, again all appeared to run normally.

Anyway; for my board (Z87-Pro) just deleting 04:02 is enough (GUID 17088572-) to allow CPU Patch tab to work, no need to delete/change 01:00. To retain the position and pretty much following what you said but changing 1 file only: export say both 01:00 and 04:02 and then replace 04:02 with 01:00 - change microcode - then put back the original 04:02, and you’re good to go with what you had there before with updated microcode.

Fernando · September 14, 2013, 9:15am

@ error-id10t:

Welcome at Win-RAID Forum and thanks for your report!

Regards
Fernando

mindwarper · September 16, 2013, 11:48am

Pacman:

@mindwarper
Deleting and re-inserting the modules at the index they were Before i think would be a bit complicated, but here is Another way, if you are still interested.

First, if you feel unclear about any of this, ask Before trying.

This way will the BIOS exactly as it was, but with new microcode, quite simple way but i tried it on my Maximus and it worked.
Load your BIOS file in MMTool
Extract the 17088572 modules, Vol. 01 ind. 00, Vol 02 ind. 02, even though i Think they are identical, extract the first to file "1.ffs" and the other to "2.ffs"
Then replace both 17088572 mod with one of the ".ffs" files i have attached, and click "CPU Patch" delete old MC rev. insert the new, go back to "Replace"
and replace the two files you inserted with the 17088572 modules you extracted before, then save image.

This way works because the two problematic MC modules are not there anymore when you go to "CPU Patch", it is like they were deleted, but then they can be "re-inserted" at their original location.
The attached files are just some random FFS files i have that are about the same size as the 17088572 modules.

Of course, even though i have tried this on my motherboard, and it worked, i can not give you any guarantee that it will work for you, but i don’t see why it shouldn’t.

@Pacman
Will try that thanks!
Thanks for thinking along and coming with a good working solution

Now when extracting the 17088572 modules, I suppose you have to extract them as-is I suppose? That is what I would find most logical to do… Or am I wrong?
I see you have in that ZIP-file four ffs files to use… I can use any one of them?

Pacman · September 16, 2013, 12:06pm

Hi
Yes, i extracted the 17088572 modules "As is", i included the four different .ffs files because some BIOSes i have tried give the error, GUID alredy exists, but otherwise any of them will work.