Yes.
I've Win/Lin too: Win is "linked" to UEFI, Ubuntu isn't. Efi-driver is loaded from win-efi partition.
Just use EFI-driver with microcode update or disable microcode setting as in lin as in win if you prefer _no_microcode version.
Same problem. On the load: CPU has about 136W during 56 sec...
Did you disable C3/C6 states in BIOS ?
My PC (EP2C612WS 2x2686v3) works fine in Win/Lin with v3x2_cp39.efi only when C6 disabled.
But when uncore is forced ("cup" version of efi driver) C3 must be disabled too.
Wow, amazing! I've got ~4700 in R15 with that (mc39 version).
(Before: ~4500 w/o microcode and 4200 with mc39)
Can you provide source code? I'm interested how did you make it.
Alas unfortunately I had BSOD during LinX-0.7.1 testing. (v3x2_50_39_vcc.efi) :(
V3x2 isn't blocked to double socket only.
It just does modification on each found CPU in system.
It must work well with single Xeon too.
But I've got only double socket system so I haven't checked on another one.
Use original V3.efi (V3_1.efi) for PC with single CPU and V3x2_cup.efi (from attached link) for multi CPU PC. And remove microcode update from OS.
V3x2 with variuos configurations: https://ufile.io/b7d061
cup - with uncore max (max perfomance, but high power drain on idle)
cp - without uncore...
Hmm... other hacks work per package. I've checked MSR registers on several cores with RU.efi
(Cores which didn't execute boost hack themselves but they have neighbors in package which did it).
With microcode...
I thought per package was right, but actually I have got a similar mess too.
4 core...
Yep, С6 doesn't work properly yet. I've cought couple of freezes too.
But C3 state works well.
About MSR register list - I'm newbie here. That question to @Dufus and @The Stilt.
I just have disassembled their V3.efi to find how to change boost multipliers and have searched some info in google...
Source code: https://ufile.io/e548b
In Windows, you will need:
1) UDK2015: http://www.tianocore.org/udk/udk2015/
2) Any C-compiler that is supported by UDK2015. I've used VisualStudio2013.
3) In file [UDK2015]\BaseTools\Conf\target.txt change next parameters to:
ACTIVE_PLATFORM =...
Yap, that method of measuring is better. I think I need such device too. ;)
Anyway I just checked C3/C6.
C3 can be enabled now and C6 can be partial enabled (I've 2x option C6 in BIOS setup, second one for memory/PCI-e etc. still doesn't work).
Windows didn't freeze at loading - good sign. I'm...
Hmm.
I didn't check C3/C6 yet. W/o Cx it looks stable, I've been using it for a couple of hours.
And I've got less than 50W per CPU... closer to 30W in balanced mode. And about 30-40W in Idle with "High performance".
How much power do you have in "DRAM Power" ?
Changing from windows - It's...
Try this one: https://ufile.io/e664a1
It changes cores boost + has some power limit experiments + updates microcode to 0x39, but doesn't touch uncore.
Looks like it works. But it may have several penalty to performance somewhere in comparision with V3.efi where uncore on FULLMAX everytime.
Hmm. It may be uncore CPU block. V3.efi changes multipliers for boost on cores (0x1AD..1AF registers) and also as I guess multiplier for uncore (register 0x620 - I've no description). As I remember uncore multiplier changes to lower value on idle but now it is fixed at max value (3GHz in my case).
I've insert microcode update into efi driver. (V3x2_mc39.efi). So I've the boost unlock and 0x39 microcode in BIOS setup stage.
But this is useless for C3/C6 on my PC (EP2C612 WS, 2686v3) it still freezes during OS loading. With 0x27 microcode - same result.
However one man has write to me that...
V3x2_mc39.efi:
https://ufile.io/1b08f
It does this:
1) update boost multipliers on each found CPU (as V3x2).
2) update CPU(s) microcode with revision 39. (which integraded into efi file, so it's ~40KB now)
Profit: OS independed microcode update.
You don't have to remove...
I've about 100W from 2x CPUs with only C1 state on idle.
http://s018.radikal.ru/i519/1703/cd/255cdc3b6a31.png
With C6 state it's about 40W on idle.
"load" - just check that all ok. For loading at boot: copy from usb flash to local hdd and "bcfg driver add..." from local.
No, this is source code. I shared compiled one a little earlier than source.
----------------------------------------------------------------------------------------------------------------
I'm trying to return C3/C6 states now.
I've added microcode update into V3x2.efi after multipliers...
Did you disable using C3/C6 states in BIOS ?
My EP2C612 WS stops in same way unless I do it.
(It is on V3.efi. I forgot to test it on v3x2 when both CPU "unlocked", I'll test it in some hours later.)
Yes. I've written it on C so it larger than original that was made on ASM (I think so, I don't have source).
Also my current code contains really ugly (unoptimized) translation ASM to C, where several simple ASM operations with registers become several function calls.
Source code...
I've made my own V3x2.efi
https://ufile.io/541182
( Unlock boost for E5-26xx-v3 multiprocessor systems, based on original V3.efi ).
PS: It is my first experience with uefi programming... it works, on my PC at least... but why I have got x28 on the first and x30 on the second CPU... I'll check...
Did you rename file in EFI/BOOT into BOOTx64.efi ?
Files on my flash drive (GPT table), that works:
│ autorun.inf
│ Shellx64.efi
│ V3.EFI
└───EFI
....│ Shellx64.efi
....└───BOOT
.........BOOTx64.efi
Shellx64.efi and BOOTx64.efi --- the same file with different names. .
Patched: https://ufile.io/b0092
Original: https://ufile.io/522e31
This is "Firmware v2.13B" for ASRockRack EP2C612 WS.
(It isn't avaible from ASRockRack site yet. I've got that one from ASRock support service. Difference from 2.1 - ClusterOnDie supporting)
PS: "Unlocking" works on v2.1 too. I...
I've used that method on PC with two CPU: BIOS modificaton + V3.EFI + win + microcode_27
Config: ASRock EP2C612 WS + 2xE5-2686v3.
And have got an interesting result: the first CPU is unlocked and the second one is not.
(That "asymmetrical" system works stable after C3/C6 states were disabled in...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.