@Dufus @The Stilt @Welsper @randir @RamRock @fromax
Finally got this darn thing to work, thanks to you lot
For me, I had to manually to manually change the mCode headers in my BIOS using HxD. For some reason, only one header showed up in UBU after editing, but apparently that's not a problem.
Afterwards, I had to disable all C-states C3/C6 to boot successfully into Windows. This was stopping all my previous attempts.
Once that was through, I applied Welsper's v3x2_cp39.efi and voila, things finally worked out. For those with dual-socket boards, it is imperative you do not use v3.efi. Enabling C6 reporting was not a problem with my board (for now anyway).
Now all I need to do is figure out how to load this EFI driver automatically on startup.
When running CB r15
With 8 cores enabled, I'm getting 3.2 GHz across all cores.
With 18 cores, I'm getting 2.4 Ghz.
Not much of an improvement with all cores running, but the going from 2.8 - 3.2 GHz with 8 cores is nice.
Finally got this darn thing to work, thanks to you lot
For me, I had to manually to manually change the mCode headers in my BIOS using HxD. For some reason, only one header showed up in UBU after editing, but apparently that's not a problem.
Afterwards, I had to disable all C-states C3/C6 to boot successfully into Windows. This was stopping all my previous attempts.
Once that was through, I applied Welsper's v3x2_cp39.efi and voila, things finally worked out. For those with dual-socket boards, it is imperative you do not use v3.efi. Enabling C6 reporting was not a problem with my board (for now anyway).
Now all I need to do is figure out how to load this EFI driver automatically on startup.
When running CB r15
With 8 cores enabled, I'm getting 3.2 GHz across all cores.
With 18 cores, I'm getting 2.4 Ghz.
Not much of an improvement with all cores running, but the going from 2.8 - 3.2 GHz with 8 cores is nice.