thanks mate.
i tried the patched AmdProcessorInitPeim

Still shows µcode version 06000629.


For the efi raid.
i looked at some newer bioses from gigabyte and msi.
they have no HiiDatabase module.
Maybe the problem is there?

lordkag

My motherboard is ASRock 990FX Extreme4 with latest bios 2.70 and agesa version 1.2.9.0
http://www.asrock.com/mb/AMD/990FX%20Extreme4/?cat=Download

My CPU is AMD FX 6300 Vishera with ìcode 06000817
newest Vishera µcode is 06000822

Can you patch the AmdProcessorInitPeim module?

Thanks for any help you can provide

@shm0

Even though I had that link bookmarked for a while, it seemed that I had forgotten about it when writing my script. These are the microcodes in your BIOS:



Here is another AmdProcessorInitPeim.ffs with the following updates:
- cpu10A0_ver010000DC_date#24-10-2011
- cpu6012_ver0600063D_date#06-03-2013
- cpu6020_ver06000822_date#03-01-2013

Replace the module with the same name using either MMTool or UEFITool. I will upload the EFI RAID files in a few days, just let me recheck my files and find all 4 modules.

@kgbab

Will look into your BIOS soon.

Zitat von lordkag im Beitrag #786

---

Here is another AmdProcessorInitPeim.ffs with the following updates:
- cpu10A0_ver010000DC_date#24-10-2011
- cpu6012_ver0600063D_date#06-03-2013
- cpu6020_ver06000822_date#03-01-2013
Replace the module with the same name using either MMTool or UEFITool. I will upload the EFI RAID files in a few days, just let me recheck my files and find all 4 modules.

---

@kgbab

This is is your BIOS:



This is your file, it has the same 3 updates.

Sonix

I found a Marvell 9120 module in my motherboard(asrock990fxextreme4) bios with name Marvell9120_DXE
Does the problem exist here?(Marvell 9120-a0 1.0.01038 - cursor blink)

Thanks anyway

@lordkag
Ok. As you said, this is really AGESA not so simple. Overall I thought it over and decided to exclude AGESA update. Leave only the display version.
And I have another questions.
For 7802/7803 also need variant 7803 -> FC / 7802 -> FD?
AND GOP driver may be updated or the same problems as with AGESA?

@kgbab
This driver is used in UEFI mode and does not affect the OROM. Unfortunately, I can not say why you do not work OROM starting with version 1.0.0.1030. I can only assume that it is necessary to update the firmware of the controller itself.

@SoniX

I don't think 7802/7803 needs the same reversed treatment for Asus. By looking at the BIOS from these boards, it seems that either they don't have a MISC at all, or they have only 7802 + MISC in FC. Others like MSI A88XM-E45 v25.3 have the full package.

You are good to go with updating GOP + VBIOS. I have always have found the same file for the same version. Latest versions updated below.

@kgbab

Based on user feedback, I would say the same as Sonix, that you need to update your whole firmware (AUTOLOAD + OROM + Firmware) for the Marvell controller to work properly. But this kind of updating is more like flash&pray than flash&play, so be careful. Download the package attached, add it on the root of a DOS flash, boot and type "go -r -y". Again, only "go -r" and "y" to read back the chip. Upload the IMAG_RB.bin that is read, I'll see if it is safe to build an updated image.

@lordkag
It's just awful! On the AMD platform, though that you can upgrade without incident for the fifth point??
Even the GOP, like Intel, only one can not be updated? Where is the guarantee that the modules VBIOS not configured for a specific model of motherboard is? %-(

@SoniX

I'm having trouble understanding your message. I presume you used Google Translate, which did a lousy job.

I assume you are asking if the update of AMD VBIOS and AMD GOP can be done without risks? If so, my answer is yes. I always compare the module from a BIOS with the ones from my collection and they were always the same, no variations. But it is better to trust your own research, so here is what I have. Pick any FM2+ AMD board and you will see that they are always the same.

Once again, you can update without worries. Just watch out that the VBIOS can be found either in CSMCORE or in separate ffs.

lordkag

The result is, I beleive, that we can't do anything because the marvell controller is on the board and there is not access to the chip.

Look at this:

MARVELL FLASH TOOL
----------------------------

MVF_MAG v1.0.0.2461
Turn off CPU Access
No supported flash found!!

Thanks for your try.

@lordkag
VBIOS from Intel must now configure, or you may get a black screen. VBIOS from AMD does not need to configure?

I tried RC4 with a M5A78L-M LX/BR and running it the first message that came up was CSMCORE not present? What did go wrong?

@SoniX

I haven't seen any customized VBIOS from AMD. Maybe they are used as original, or the settings are stored in other module. From my point a view, it is safe to update AMD VBIOS + AMD GOP.

@kgbab

First of all, you haven't replied back after the patched AmdProcessorInitPeim.ffs I provided you a couple of messages back. Why ask for something if you don't plan on using it?

The error message from the Marvell flasher is not uncommon and it means that the chip is not registered. I have successfully patched this flasher for some U3S6 cards, but I had the ID of the chip. So inspect your board and locate the Marvell controller, then check the chips around it. It must be 512KB in size.