UBU tells me, that my ASRock Z87M Extreme4 motherboard with the latest original BIOS 2.00 has “OROM VBIOS Haswell - 2166”. But in the VBIOS package I couldn’t find the appropriate BSF script file for version 2166, so I can’t update the VBIOS to version 2180. How would it be possible to update from 2166 to 2180?
@ hyts:
Welcome at WinRAID Forum!
Only SoniX will be able to answer your question. I hope, that he will see your post and reply.
Regards
Fernando
Take the one closest to 2166
i have some question
i use asrock x79 pro mother board
it have marvell 9172
when i try boot in non CSM setting i did not work
i think there is no EFI sata driver for 9172 in bios
is it possible insert EFI driver for 9172?
@ dygkset:
Welcome at Win-RAID Forum!
If there is no Marvell EFI SATA module for DEV_9172 within the BIOS, it may be possible to insert it, but the UBU tool cannot do it for you, because it is just an "Updater" of modules, which are already present within the BIOS.
Regards
Fernando
thanks a lot…
in side \UBU_v188\Modules\SATA\FFS<br /> there are
marv_ahci_43.ffs
marv_ahci_491.ffs
marv_raid_492.ffs
marv_raid_a2.ffs
is it ok insert it by using MMtool
and i found ‘marv_raid_xx.ffs - 1.1.0.1015 - GUID A28F1CD7-, 4953F720-…2 (compressed)’ this text inside VerDID.txt it mean they are alread compressed??
so i have to insert it whit out check in compressing checkbox?
and what difference between marv_ahci_43.ffs and marv_ahci_491.ffs??
@dygkset
You can try to insert them, I don’t think there is much risk in it. You can use the ones inside UBU, since they are already compressed, so there is less chance of a space warning.
You should use marv_ahci_43.ffs and/or marv_raid_a2.ffs, since those are most likely to be found in Asrock boards. They have different GUID than *491.ffs, *492.ffs, that is all.
i try the insert by mmtool…
but threr is graphic bug… in mmtool like this
do you know how to fix it??
Where did you get the AMI Aptio MMTool resp. what have tried to do with it?
After having run the MMTool.exe file it should look like this:
i use mmtool inside of UBU package…
Ok, then you used the original MMTool version like me.
Did the MMTool GUI look like your pic from scratch or did you try to open a file with it?
yes gui look like pic…
open .bin file is not problem…
but i can see the some butten and test box.
i use windows 8.1 ko-kr
if i change OS it can help me?
I don’t think, that your MMTool problem is OS related, it seems to be just a graphics/display one.
Maybe DPI related? Do you have it set at the default 100%?
yes i set 100%
i install windows 10 preview in vm…
that bug… not appear…
and another vm install windos 8.1 using same image when i was use at main system … appear bug…
i think it is truble whit languge or same thing
Well either way, it’s system specific. And it’s not like you can find other versions of this tool so you need to find a way to make it work. If you do find the issue, share it here so it can help others in the future.
ok
i solved gui problem by using vm…
so first insert ‘marv_ahci_43.ffs’ unchecked -‘for option rom only’ and select ‘insert as is’
-do not work. it also can not find hdd in ‘disableed csm’…
then insert ‘marv_ahci_491.ffs’ unchecked -‘for option rom only’ and select ‘insert as is’
-do not work either
do i have mistake in process?
or in my case not enough to just do that… it need additional process?
Those boards also use an EFI loader, but that is compiled for each board. Can you try with both marv_ahci_43.ffs and marv_raid_a2.ffs ?
Another question: are you sure that everything else is EFI compatible? What about graphic card, RAID drivers if you use RAID?
ok…
i explane situation…
intel x79 sata controller
-samsung 850 pro 256 X 2 raid 0 volume
L windos 8.1 EFI
-WD 1TB 7200rpm
L NTFS for data
-WD 1TB 52000rpm
L exFAT for data
marvel 9172
- sandisk x110 128g
L OSX 10.10 EFI
and VGA is UEFI capable.
so i can boot windows 8.1 in CSM disabled
and i can boot osx in CSM abled
but in CSM disabled… bios can not scan disk connected marvel controller… so bios can not read EFI in sandisk x110…
i want boot CSM… my board is old type… so use CSM boot take so much time…
sounds like he might be using an addon card maybe!?!