This is not UBU business, but what Cesco81 needs to change is this:

There are tree false positives. The above search was done with the help of UEFIFind

Processor Microcode Data File 20150107

http://downloadmirror.intel.com/24616/en...de-20150107.tgz

What are all the command line arguments needed to use UEFIFind?

Zitat von lordkag im Beitrag #1279

---

This is not UBU business, but what Cesco81 needs to change is this:

to this:

Which will look strange with that background around icons. There are at least 78 images in Z77 E6 and 91 in Z77 OCF.

Even if he fixes that, he has a long way to go, since Asrock, unlike Asus, is using a separation between images.

There are tree false positives. The above search was done with the help of UEFIFind

---

Tried to update another Supermicro BIOS
Xeon-Mainboard: X10SLM+-LN4F
x10slmp4_424.zip

Replacing of Modules works fine,
but when trying to insert newest CPU-Microcode, I get into a loop (allways have to enter "1").

Zitat von Wishbringer im Beitrag #1285

---

Tried to update another Supermicro BIOS
Xeon-Mainboard: X10SLM+-LN4F
x10slmp4_424.zip

Replacing of Modules works fine,
but when trying to insert newest CPU-Microcode, I get into a loop (allways have to enter "1").

---

Realtek PXE and RPL ROM 2.61

Realtek PCIe GBE Family Controller Series v2.61 (01/07/15)

Zitat von lordkag im Beitrag #1274

---

I hope you recovered to a working state. This is a good report on NOT to change OEM compiled files. It shouldn't be too hard for Asrock to add them in the UEFI firmware, the Marvell EFI drivers are already out there. Please report back if they do it, I'm curious to see if their support is really up to it.

---

PCH is Peripheral Controller Hub aka chipset, they are saying that you should use chipset SATA ports for non-CSM UEFI-bootable drives.

Found Broadcom UNDI 16.4.6 in sp70087. Also, it turns out ValleyView also has a long version, like VBIOS 7.1.1007, GOP 7.1.1003, GOP 7.2.1008.

[[File:X79PFS_3.zip]]@lordkag

few day's ago asrock gave me new bios. 3.10A
thay say 3.10A bios surpport marvall cantroller EFI boot
but it is not work to me...


in my system i can see driver loaded and EFI Shell scan file System..
but strangely only UEFI mode EFI shell can not read contents of file system..
you can see the fs2: in 'update3.jpg' the same file system 'EFI for windows'
in legacy mode... EFI SHELL can read all file and bootloader and file

i report it asrock.. and asrock said
'We tested the BIOS P3.10A in our side before release to you.
It can install the Windows in UEFI mode(AHCI) and boot normally.'

do you know why this bug occured?

edit:
i attached asrock 3.10 bios
it centain marvell RAID driver and ahci driver..
it is almost same you gave me few days ago but guid is diffrent
AMITSE and marvel 9172 DXE replaced new one..

@dygkset

What is the problem exactly? Is UEFI booting not working at all for Marvell controller, no HDD/SSD detection, or just the UEFI Shell has problems? Either way, it is Asrock business to fix their problems. The only thing I recommend is to run this beta file in UBU and update the Marvell EFI AHCI driver to 1.1.0.1015. Other than that, nothing can be done from our side, without sources and EFI development knowledge.

the problem is can not boot target disk cennceted marvel sata..
becouse uefi driver can detect HDD/SSD and scan file system well but can not read in it include boot loader..

the reason i ask to you not asrock that asrock said thay also test it... and they can boot and there is no such a bug exist.

do you think the test of asrock incorrent?

edit:
forget it
i found why diffrent resert ocured betwen asrock's test nad my test...
m1 m0 port do not work..
m2 m3 port works..fine..