[OFFER] Var. ASUS Sabertooth X79 BIOSes (NVMe/Bifurc./uCode/OpROM)

@gdfath3r - Time to RMA, anything could mess it up, power surge, general failure, bad FW update, bad write possibly etc

BIOS tested, works fine.
VCCSA : It wanted to set 1,25V on it (which aparently isn’t a good idea :D).
I had to manually decrease it to 0,975V (stock), after I choose XMP profile on my memory.
After that, I saved and PC booted (voltage control works, memory frequency stayed where it should be).

Here’s how it looks :



@Lost_N_BIOS Q: How ME update works vs. what’s in BIOS image ?
I updated my ME to latest 8.1.70.1590 (using FWUpdLcl64), and it didn’t switch itself to lower version from this BIOS. However in HWInfo64, it detects older version under "Intel ME FITC Version" ?

ME.png

@agentx007 - So, please clarify, there is an issue with use of XMP and voltages then, correct? If yes, I’ll have to redo BIOS in manner that I did for Ntrako - I’ll have to look back and see what we found as the cause of this and redo your mod, it’s been so long now I don’t remember.
But, this is why I waited and didn’t do both at once for you there, because I knew this issue may happen if mod not done certain way, but wanted to see if that version would be OK without that dance required (whatever it was)
So, in summary, sounds like this BIOS does not work fine

@Ntrako - can you please confirm, the above mentioned XMP/Voltage issue at #242 is similar/same/part of what we had to work around for you, correct?

FITc is software version, whatever is used to create the ME FW you flashed in, that has nothing to do with actual ME FW version (your now on latest)

@Lost_N_BIOS There was an issue with not working on set frequency/voltages (regardless if done manually or via XMP [?]). It works fine with that last BIOS though.
Just to reiterate : When VCCSA is set in Profile to 1,25V, XMP it will set that (such setting only needs to be there).
Problem Ntraco had wasn’t with value itself (since it depends on Profile), but with not applying said value after a Save & Restart.

I checked with no manual adjustments to settings :
1,25V for VCCSA and proper timings/frequency were set, when XMP was selected.

Is there a way to update ME FW to latest, with just BIOS Flashback update ?
Or (if not), can this be an issue down the line (when software version doesn’t match up with the one I use) ?

OK, that sounds normal/expected then, correct? Since that is what is set in your XMP profile.
I don’t think this is the issue Ntrako found on previous edit, I believe that was with the use of XMP some crazy high voltage was applied (Maybe that was just what he thought, and it’s like you’re seeing, and that’s what’s in his XMP profile?)
I also think speed choice was affected too, but not sure. We’ll have to wait for him to stop back in and clarify again, I don’t have time to dig backwards through this thread to try and find where he outlined the problem (OK, I found, page 11-12 and before maybe, he said ram freq and VCCSA voltage issue)
But, I don’t think it’s what was in his XMP, because once we sorted out the cause and I did it differently, then his memory and XMP use was back to normal.

On MW FW, not sure if flashback will write ME FW or not, but you could try the ERALL.CAP (or the AMIBOOT.CAP) method with a BIOS that has updated ME FW in it, and see if that works, unsure if this works now on CAP
If your ME FW is healthy now, you can update ME FW easily with ME FW update tool. I suggest this method, I hate messing with ME FW updating manually using FITc tool, it’s a pain in my rear and I never trust the file once done (We don’t have 100% compatible/bug free tool for this)
ME Drivers rarely ever match the ME FW version, just read the ME driver thread and it will explain to you what driver to use based on your chipset series.

So, where are we now with your set of four requested BIOS, I’m lost?

So… I can’t just swap ME regions inside EFI BIOS with UEFITool (using .bin file from ME thread) ?

As for BIOS’es, I need a bifurcation enabled version of 4801 from post #189 :slight_smile:

PS. Why switch from 6.6.04/1.5.62 to 0.0.23/0.1.14 on Intel GbE ROMs, when stock one is for i210/i211/i350 (5.5.23/1.3.72) ?

No, you can NEVER do that, when using files from that thread you must use BIOS or ME From your board and run through the ME Clean up and settings transfer guide using Intel FITc tool, and then that can be inserted into BIOS or that BIOS used if you edit the whole BIOS at once.
That may or may not get flashed with a reflash of the same BIOS version when using USB Flashback, sometimes it’s never flashed via USB Flashback. << this is why I mentioned all I did above, it’s easiest and safest way for you to update this using the ME FW update tool, especially on X79 chipset

On GbE roms, those are the newest latest versions, due to version name changes by Intel.

Thanks, I’ll follow up soon with bifurcation BIOS from #189

@Lost_N_BIOS
sorry for the late answer.
the problem i had was that i had stock values on vccsa and ram frequence,and generally all options that will change with xmp, either i enable xmp or not…
stock values are:
vccsa:0.975v
ram freq: 1333mhz

expected xmp values:
vccsa: 1.220v
ram freq: it depends on ram freq(in my case was 1866mhz)

EDIT1: so i dont understand why @agentx007 says that in xmp 1.250v for vccsa is high?
The original value that should get in xmp profile is 1.220v and it plays between(1.210v - 1.240v), so @agentx007 dont worry about that, it is not higher voltage, its expected one when you enable xmp :wink:
it depends also on cpu and ram type by the way…vccsa, and other voltage values may varie from different hardware(cpu and ram, as mobo is the same…)

So @Lost_N_BIOS to answer your question i believe that your mod hasn’t any issue about the above you mentioned,
vccsa value is as expected

@Ntrako - Thanks. All XMP Profiles are set differently, by the manufacturer per memory model, so yours would be different than his unless you both had exact same memory kits with same manufacture dates.
I think we’re all sorted on his BIOS now too, I just need to make that final one for him with the bifurcation edits (Will do tonight so I don’t keep forgetting )

* Edit - @agentx007 - here is 4801 Updated + Bifurcation
http://s000.tinyupload.com/index.php?fil…951496884673017

@Ntrako I don’t like going above Intel recommended IMC voltage when CPUs aren’t cheap to get.
Since, in my case, I can get away with it on lower voltage (system is stable), I prefer to NOT use higher VCCSA.
@Lost_N_BIOS Sorry about late request, but I would like to ask for 6.6.04/1.5.62 OpROM to be used for Intel LAN instead of latest one. Thank you.

- for what BIOS? Those would not be latest versions, so you know. And is that the stock versions, so I don’t have to look it up? Can’t UBU do that for you, or does that break the BIOS too?

@Lost_N_BIOS I know it won’t be latest.
It’s in UBU already. Simply pick “2” instead of “1” when asked about Intel OpROM update.
I tried picking it after 0.0.x.x was put in there, but it doesn’t allow it to be replaced :frowning:

I only would like it to change for my 4801 version.

I don’t use UBU, I asked that meaning can’t you update it with UBU, are you saying it wont let you? If it wont let you then it’s not for your board or you need to use the force option I think
Let me look. You never answered me, is that the stock version that was in 4801 BIOS to begin with?

You do know that is ONLY used if you boot from LAN or use Wake On LAN, don’t you? * Edit - do you want that in both 4801’s?
I only see 8.7/1.5 as option, but that is in older 1.75.1 UBU. And again, those are not for the chip on your board, so probably will not work (unless you are referring to what older versions were in there originally)

Never mind about stock question, I checked and see these are stock ones (At least in the BIOS you sent me anyway)
EFI Intel PRO/1000 UNDI - 5.5.23
OROM Intel Boot Agent GE - 1.3.72

I checked UBU files folder, and those 6.6 etc are definitely not for your LAN Chip, only what is shown as offered is compatible and really only the ones for 82579
Even old 1.69 UBU only offers those as a forced option, but it will complete successfully

@agentx007 - Here, both these done with UBU 1.69_17_4 for simplicity - if you can’t wake from LAN or boot from LAN, then you know these are not compatible.
http://s000.tinyupload.com/index.php?fil…704042384123932

So, to test if those LAN roms actually work, I have to try Wake-on LAN ?

In that case, maybe let’s stick with what UBU recommends.

Just FYI : Those 8.7/1.5 versions shown on UBU will get downgraded during update to 6.6.04/1.5.62 (when older device gets detected).

I’m at work at the moment, I will check this BIOS when I get back.

Yes, as I mentioned, that is the ONLY time those LAN roms are loaded/used, if you boot from LAN or wake on LAN, other than that they just take up space in the BIOS and are never used (Like RAID Roms, if you don’t use RAID they are never used)
I don’t usually use UBU for BIOS mods, but I can tell you the ones I put in there initially are the ones UBU would have updated the BIOS to (1.75 version anyway) because I used it to see which were suggested.
Only old 1.69 UBU even offers those for your BIOS, the new 1.75+ UBU does not offer those, but offers the 0.xx ones instead (the 8.7/1.5 are FORCE only, and not for your LAN Chip)

This is what new 1.75 UBU would offer, suggests for your correct chip ID (May be slightly newer versions with latest UBU)
EFI Intel PRO/1000 UNDI - 5.5.23 >> 0.0.23 (new version/name formatting)
OROM Intel Boot Agent GE - 1.3.72 >> 0.1.14 (Same as above)

Not sure what you mean about any “New version” will get downgraded to 6.xx etc. UBU only puts in what you select or force, and LAN/BIOS itself cannot change this, so what you put in there is the only thing that would ever be in there (No auto-downgrades, unless you do it yourself)
New 1.7x UBU does not even offer the module versions you asked for, and old 1.69 ONLY offers them as a forced option

I meant that, if you try update stock BIOS with UBU, and check second option on LAN update side (instead of recommended one), it will back track to 6.6.04/1.5.62 instead of forcing 8.5 version.

I did not test that, seems odd it would do that, maybe some bug? I tested with 1.75 and I see what you mean now! Odd that happens, when not offered initially. Probably due to those are not meant for this LAN Chip anyway, neither 8.7.10/1.5.88 or 6.6.04/1.5.62
I checked when initially doing all these mods for you, and your board has the 82579 chip per the specs -https://www.asus.com/us/Motherboards/SAB…specifications/
And those that I used are the updates shown as first/suggested non-force option in old and new UBU

New UBU >>
EFI Intel PRO/1000 UNDI - 5.5.23 >> 0.0.23
OROM Intel Boot Agent GE - 1.3.72 >> 0.1.14

1.69 UBU
EFI Intel PRO/1000 UNDI - 5.5.23 >> 0.1.13
OROM Intel Boot Agent GE - 1.3.72 >> 0.0.19

Those versions look odd due to Intel version formatting name changes, they are not “older” modules.

If you want 100% clarification on what’s new, what’s old, why this is offered instead of that, why you have to force this or that, why forcing this or that doesn’t actually stick in versions is appears to be offering you to force in etc
You’ll have to talk to SoniX about this, I only know how to mod BIOS, I don’t keep up with what modules are best or latest etc.

Sounds like you don’t boot from LAN or use wake on LAN Anyway, so all this discussion and mod, re-mod, test to see etc all for nothing as you’ll never use any module for LAN that’s in there anyway no matter what version it is

You got me there (I don’t use Wake-on LAN ;)).
Still, since SoniX said everything worked for his friend, I went with first BIOS you created for me (4801).

So far, works fine :slight_smile:
Bifurcation and other options are also there.
Thank you.

I thought you didn’t use WOL or Boot from LAN, when you first asked if that was only way to test Most people do not use those at all ever, that’s why I kept saying that.

So you were already talking with SoniX about these BIOS, and one was for his friend? He could have told you all about those weird version numbers and how/why etc. Why didn’t he?
And, since he was involved, why didn’t he update BIOS, very strange

Thanks for report back about bifurcation and functioning all OK! So, do you want me to put you together some final package A-D now, so it’s all together, or do you have it all sorted on your end?

I didn’t talked with him before you mentioned it.
Here’s my first post in UBU topic (no earlier PMs with him as well, just FYI) : LINK
I just wrote here what he answered.

I want to make things clear, before I create A-D and redo my first post.