I missed these completely and focused solely on your guide. Thank you.
The only thing bothering me right now is figuring out a way to update LAN ROMs properly. Older UBU versions fail to install the proper version, and the latest one, which seems to resolve this issue, generates a BIOS that is not updatable. I already reported it.
You are right: We need a completely new guide about how to update an AMI Aptio V BIOS.
I am still hoping, that CodeRush will write it within the next weeks.
Fernando I am a new forum member but I have been following your guides for years, I wanted to thank you for all your work. UBU is an amazing piece of software relieving many of us from some of the most complex tasks, and I can only hope to see it working across all different BIOSes in the future, including ones like my R5E. I wish I had the knowledge to help with what you are doing here.
Alright, here we go:
Microcode updated to the latest version (2015/08/10)
RAID updated to the latest version (14.8.0.2377)
LAN updated to the latest version (6.6.04 & 2.035)
Unlike Unb0rn’s version, the Realtek Gigabit UNDI EFI module is not removed, and thanks to the latest UBU tool it has the correct Intel module.
R5E.CAP
Great work
Intel EFI LAN 6.6.0.4 seems to be really old(July?) and it seems like they switched our NIC to 0.0.x versioning. At least, it looks like this.
Well, according to UBU 1.43, v6.9.07 is for "Intel NIC 210/211/350" while v6.6.0.4 is for "Intel NIC 82579/217/218/219+210/211/350".
Rampage V has "Intel I218V" controller so, according to UBU, the correct version is v6.6.0.4 and not v6.9.07. This does not mean the latest version will not work - but I trust the UBU creators with my eyes closed.
Regarding UNDI v0.0.09 there is this:
And UNDI v0.0.09 does in fact work. However, mind that Rampage V’s BIOS reports "EFI Intel PRO/1000 UNDI - 6.0.24" in UBU, making the 6.x.x.x versions the more likely compatible ones, but this is something only SoniX / Fernado can clarify, not me.
If SoniX / Fernado say UNDI v.0.0.09 is better I will update accordingly and it will be very useful information, but until then I will go according to the original BIOS, which reports "EFI Intel PRO/1000 UNDI - 6.0.24".
1801 is out if anyone fancies tackling all the modules
If the motherboard is installed only one network controller 82579, 217, 218 or 219 - uses the new version of the files 0.x.xx.
It does have one controller physically, but UBU reports this:
LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel Boot Agent GE - 1.5.47
EFI Intel PRO/1000 UNDI - 6.0.24
EFI Realtek UNDI - 2.026
Should we go for the one UBU defaults to (0.0.09)?
EDIT: Updated to the latest ASUS BIOS version (1801):
Microcode updated to the latest version (2015/08/10)
RAID updated to the latest version (14.8.0.2377)
Intel LAN updated to SoniX’s suggested version of (0.0.09) - you can switch versions by forcing them via UBU v1.43, according to your needs or in case something changes regarding the NIC matter.
Note for overclockers:
The latest CPU Microcode has helped me achieve the same O.C. with 0.05 less voltage in both cache and frequency on a 5960X.
R5E.CAP
Yes.
EFI LAN Realek UNDI can be removed.
It does have one controller physically, but UBU reports this:
LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel Boot Agent GE - 1.5.47
EFI Intel PRO/1000 UNDI - 6.0.24
EFI Realtek UNDI - 2.026
Should we go for the one UBU defaults to (0.0.09)?
EDIT: Updated to the latest ASUS BIOS version (1801):
Microcode updated to the latest version (2015/08/10)
RAID updated to the latest version (14.8.0.2377)
Intel LAN updated to SoniX’s suggested version of (0.0.09) - you can switch versions by forcing them via UBU v1.43, according to your needs or in case something changes regarding the NIC matter.
Note for overclockers:
The latest CPU Microcode has helped me achieve the same O.C. with 0.05 less voltage in both cache and frequency on a 5960X.
R5E.CAP
Thanks for this, I will have a crack at installing this and filling in all the settings when I get chance to sit down for an hour!
are you planning to remove the realtek module as I will post this on the Asus forums once you give me the nod
FYI one boards been bricked so I do advise resetting the BIOS before using flashback so we have done as much as possible to stop it bricking. Last time mine bricked it took a lot of messing about swapping BIOS and resetting (with mains pulled) to get it to boot again.
(mine bricked on stock 1701 using normal flash methods not flashback and the guy who bricked his today also didn’t use flashback))
@ GoNz0:
Off-topic:
The fully quoting procedure may be easier for you, but not for the viewers of a thread, whose size has been blown up and nearly doubled by fully quoted posts.
The best way to address a reply to a specific Forum member is to use the “@ Someone” option.
[Solved] How to mod an ASUS Rampage V Extreme BIOS? (5)
+
Changed to the latest ASUS BIOS version (1801):
- update OROM LAN Intel Boot Agent CL v0.1.06
- remove EFI LAN Realtek UNDI
R5E_1801_mod.rar (5.68 MB)
Does this have both raid modules updated?
Thanks.
Yes it is completely updated and the absolutely best right now since it comes from SoniX - I will be pulling mine down.
Thank you for this SoniX, I hope you find the time to tell us how you removed and updated the modules so we can do it ourselves next time instead of bother you.
Thanks again!
Great stuff, I have linked this to the Asus forums
Thanks for your effort, guys.
1801 MOD working here rock solid…
Best regards.
Updated bios using bios flashback. If I set storage configuration to Raid mode sata drives are displayed - says not installed. Is the Intel rom 14.8.0.2377 used in the mod compatible?
@ catch36:
Welcome at Win-RAID Forum!
When the drives are shown, they have been detected and should be usable.
Why should it not?
By the way: The Intel RAID ROM will only be used, if you are running your system in LEGACY mode. Otherwise the Intel EFI RaidDriver will be loaded while booting in RAID mode.
Regards
Dieter (alias Fernando)
It is a little strange on this board as you can turn on the raid module via the ez-tuning menu or by the option in storage configuration, the module is installed twice in the BIOS to account for this as we found out when I initially modded the BIOS.