Jump to content

Mojave on X99 E5-2696v4. Need help!


kingkong89

Recommended Posts

  • Supervisor

Hi KingKong nice to see you here

 

:)

 

post your actual efi

 

 

 

Ha scritto dopo 5 minuti 50 secondi:

 

remember also

 

you have to change some kernel patches if you are using some ;)

 

 

 

Ha scritto dopo 7 minuti 34 secondi:

 

@sherloks posted a summary in other forum :

 

 

 

here is xcpm patch for 10.14

 

B9A00100 000F32

 

B9A00100 0031C0

 

cpuid_set_info_rdmsr © vit9696

 

 

 

B9E20000 000F30

 

B9E20000 009090

 

xcpm_idle_wrmsr © Pike R. Alpha

 

 

 

B9980100 000F32

 

B9980100 0031C0

 

xcpm_assert_rdmsr © Sherlocks

 

 

 

BE0B0000 005DE908 000000

 

BE0B0000 005DC390 909090

 

xcpm_SMT_scope_msrs © Pike R. Alpha

 

 

 

04723CD0

 

04XX3CD0 XX

 

cpuid_set_info © Pike R. Alpha

 

 

 

89D804C4 3C22

 

89D804XX 3C22 XX

 

xcpm_bootstrap © Pike R. Alpha

 

 

 

B9990100 000F30

 

B9990100 009090

 

xcpm_assert_wrmsr © Sherlocks

 

 

 

BE030000 0031D2E8 91FCFFFF

 

BE030000 0031D290 90909090

 

xcpm_core_scope_msrs © Pike R. Alpha

 

 

 

554889E5 41574156 41554154 53504189 D64889FB 4189F54C 8D3D6257

 

C39089E5 41574156 41554154 53504189 D64889FB 4189F54C 8D3D6257

 

xcpm_program_msrs © Pike R. Alpha

 

 

 

BE070000 0031D2E8 AEFCFFFF

 

BE070000 0031D290 90909090

 

xcpm_pkg_scope_msrs © Pike R. Alpha

 

 

 

BE0B0000 0031D2E8 7EFCFFFF

 

BE0B0000 0031D290 90909090

 

xcpm_SMT_scope_msrs © Pike R. Alpha

 

 

 

C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF05938D 76004883 C4085B5D C30F1F40 00

 

B800FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 938D7600 4883C408 5B5DC390 90

 

xcpm_assert_perf_max © PMheart

 

 

 

8A0284C0 7442

 

8A0284C0 EB42

 

Disable panic kext logging on 10.14 Release kernel © vit9696

  • Like 1
Link to comment
Share on other sites

Do you happen to know the XX value for E5-2696V4?

 

 

 

The XX value in cpuid_set_info © Pike R. Alpha & xcpm_bootstrap © Pike R. Alpha....

 

 

 

Sorry for the trouble...

 

 

 

Added in 10 minutes 44 seconds:

 

here is the EFI after I incorporated the kernel patch. but without my cpu XX value...

EFI.zip

Link to comment
Share on other sites

  • Supervisor

Far away from my pc by now

 

I will check later

 

For now take a look here

 

https://pikeralpha.wordpress.com/2016/07/26/xcpm-for-unsupported-processor/">https://pikeralpha.wordpress.com/2016/0 ... processor/">https://pikeralpha.wordpress.com/2016/07/26/xcpm-for-unsupported-processor/

 

Also you can find xx in your old patches

  • Like 1
Link to comment
Share on other sites

  • Supervisor

Ciao Kingkong89

 

 

 

your efi is using too many kernel patches and in kext you are using many old kext

 

I will try to give you a simple config.plist for it but you should also use latest kext and maybe also new drivers64 uefi I think

 

 

 

Ha scritto dopo 8 minuti 30 secondi:

 

I see also many unusefull ssdt for Nvme and old method to map correctly USB ports

 

If I don't mind you have an Asus x99 deluxe 2

 

You can use this guide to map it in new and fast way

 

https://www.macos86.it/viewtopic.php?f=68&t=702">viewtopic.php?f=68&t=702">https://www.macos86.it/viewtopic.php?f=68&t=702

 

 

 

Ps

 

if you can put in your signature your hardware :)

 

Thank you

Archive.zip

  • Like 1
Link to comment
Share on other sites

  • Supervisor

Have you used also kext in others and driver64uefi I insert in it?

 

could you post only clover folder (working one in your system with High Sierra)?

 

also you should post where system hangs in verbose (take a photo of it)

 

Thanks

 

 

 

Ha scritto dopo 11 minuti 14 secondi:

 

I see also now you have in signature a Vega 64 (Nitro+), I think is not there your hang ;)

  • Like 1
Link to comment
Share on other sites

  • Supervisor

If you want you can delete all ssdt for nvme and study to create a ssdt for usb

 

it is pretty simple

 

now I have activated automatic kernel XCPM in clover but you can achieve it also in other ways. with right kernel patches

 

 

 

I have no more your kind of cpu so I am limited in helping (no chance to test) :9

 

Have a nice Hack :)

 

 

 

Ha scritto dopo 3 minuti 21 secondi:

 

for vectorfrequency

 

try to use ImacPro 1.1 smbios

 

It is working well and it has FV injected by default

 

Very usefull also for Nvidia Policy problem we have with MacPro 6.1 smbios

  • Like 1
Link to comment
Share on other sites

kernelXCPM must be checked in my config.plist to run Mojave..

 

 

 

My Bios is patched with MSR 0xE2 register unlock, the xcpm is working without patches in kernel patch, only need the performance patch. I'm happy with the system. Only thing is it does not perform as well in mojave as in HS. about 10% slow, check using geekbench.

Link to comment
Share on other sites

  • Supervisor
"kingkong89" post_id="15707" time="1538607337" user_id="612">

kernelXCPM must be checked in my config.plist to run Mojave..

 

 

 

My Bios is patched with MSR 0xE2 register unlock, the xcpm is working without patches in kernel patch, only need the performance patch. I'm happy with the system. Only thing is it does not perform as well in mojave as in HS. about 10% slow, check using geekbench.

 

Yes till you will find exact patches for you

 

XCPM kernel patches is an automatic way to patch kernel for unsupported Cpu as your XEON

 

If you remember till High Sierra I have had an identical system to yours

 

For our system was mandatory to have

 

1) fakecpuid

 

2) Brumbaer IOCPIFamily kext patch

 

3) only reboot fix (piker alpha) (also with/without patched bios

 

then if you have EIST enabled in bios to have performance you have to use oarksit performance fix

 

 

 

Said this

 

KernleXCPM allow to boot without fakecpuid and reboot fix (brumbaer instead should be mandatory)

 

if you have time, searching on clover code in clover repo, you will find exact patch with KernelXCPM flag uses for your cpu and you can decide to use it without that flag in usual way

 

 

 

About 10% is too much maybe you have to refine better your settings cleaning unuseful things but only you can know :)

 

 

 

or ... :)

 

update @ x299 system

 

your old Xeon is today a great value and in same case you can also use your ECC unsupported DIMM as I do (they are working well with designare EX and with X299 Sage (not latest bios)

  • Like 1
Link to comment
Share on other sites

thank Fabio!

 

 

 

I' actually a mechanical engineer... I don't know much bait IT and I really a noop with programming. I'm actually struggling to understand get the Hackintosh work in a perfect way... but I really appreciate your help and others who are willing to share how to make a hack work.

 

 

 

BTW do you happen to know the _cpuid_set_info for E52696V4? I think that will help a lot....

Link to comment
Share on other sites

  • Supervisor

Ciao KK89

 

 

 

take a look here

 

 

comment = "_cpuid_set_info_rdmsr";

 

// PMheart: attempt to add 10.14 compatibility

 

if (os_version >= AsciiOSVersionToUint64("10.12") && os_version

 

- // 10.12 - 10.13

 

+ // 10.12 - 10.14

 

STATIC UINT8 find[] = { 0xB9, 0xA0, 0x01, 0x00, 0x00, 0x0F, 0x32 };

 

STATIC UINT8 repl[] = { 0xB9, 0xA0, 0x01, 0x00, 0x00, 0x31, 0xC0 };

 

applyKernPatch(kern, find, sizeof(find), repl, comment);

 

@@ -1065,9 +1066,10 @@

 

DBG("KernelIvyBridgeXCPM()

 

return TRUE;

 

}

 

-

 

+

 

DBG("Searching _xcpm_pkg_scope_msr ...\n");

 

if (os_version >= AsciiOSVersionToUint64("10.12")) {

 

+ // 10.12+

 

patchLocation = 0; // clean out the value just in case

 

for (i = 0; i

 

if (kern[i+0] == 0xBE && kern[i+1] == 0x07 && kern[i+2] == 0x00 && kern[i+3] == 0x00 &&

 

@@ -1096,14 +1098,14 @@

 

STATIC UINT8 find[] = { 0x83, 0xC3, 0xC4, 0x83, 0xFB, 0x22 };

 

STATIC UINT8 repl[] = { 0x83, 0xC3, 0xC6, 0x83, 0xFB, 0x22 };

 

applyKernPatch(kern, find, sizeof(find), repl, comment);

 

- } else if (os_version >= AsciiOSVersionToUint64("10.12.6") && os_version

 

- // 10.12.6 - 10.12.x

 

+ } else if (os_version

 

+ // 10.12.6

 

STATIC UINT8 find[] = { 0x8D, 0x43, 0xC4, 0x83, 0xF8, 0x22 };

 

STATIC UINT8 repl[] = { 0x8D, 0x43, 0xC6, 0x83, 0xF8, 0x22 };

 

applyKernPatch(kern, find, sizeof(find), repl, comment);

 

+ // PMheart: attempt to add 10.14 compatibility

 

} else if (os_version

 

- // PMheart: attempt to add 10.14 compatibility

 

- // 10.13.x/10.14.x

 

+ // 10.13/10.14

 

STATIC UINT8 find[] = { 0x89, 0xD8, 0x04, 0xC4, 0x3C, 0x22 };

 

STATIC UINT8 repl[] = { 0x89, 0xD8, 0x04, 0xC6, 0x3C, 0x22 };

 

applyKernPatch(kern, find, sizeof(find), repl, comment);

 

and focalize this line :

 

comment = "_cpuid_set_info_rdmsr";

 

// PMheart: attempt to add 10.14 compatibility

 

if (os_version >= AsciiOSVersionToUint64("10.12") && os_version

 

- // 10.12 - 10.13

 

+ // 10.12 - 10.14

 

STATIC UINT8 find[] = { 0xB9, 0xA0, 0x01, 0x00, 0x00, 0x0F, 0x32 };

 

STATIC UINT8 repl[] = { 0xB9, 0xA0, 0x01, 0x00, 0x00, 0x31, 0xC0 };

 

applyKernPatch(kern, find, sizeof(find), repl, comment);

 

 

 

this code is from /rEFIt_UEFI/Platform/kernel_patcher.c inside clover

 

so if you check KERNELXCPM flag it uses all patches it thinks useful for detected cpu

 

 

 

Cupid_set_info_rdmsr will be :

 

 

 

find

 

B9A00100000F32

 

Repl

 

B9A001000031C0

 

 

 

I hope this can help to understand ;)

 

 

 

Ha scritto dopo 19 minuti 24 secondi:

 

attached c files where you can locate all patches used for Broadwell and other cpu

  • Like 1
Link to comment
Share on other sites

  • Supervisor

When I have had your same system I have optimized it using only 3 mandatory patches or KernelXCPM flag (I preferred 3 patches state)

 

 

 

1)fakecpuid

 

2)Brumbaer IOCPIfamily kext patch

 

3) Pikeralpha reboot fix kernel patches

 

 

 

And this should be valid also for you

 

 

 

Obviously with my I9 7980Xe now I have eliminated all of this and system starts pretty vanilla

 

So it is up to you the choice :)

 

Remember all it is possible also to use your actual DDR4 ECC in new X299 (official specific is not true for Asus X299 Sage (not latest bios) and for Gigabyte Designare EX (bios F2 and F3)

 

I have talked with gigabyte technical service and they say with latest bios is not possible to use anymore Rdimm etc DDR4

 

In these days DDR4 is a pain to buy..and there are no advantages in performance if you use ddr4 @2133 or @4000...

 

Due High TDP you will need of a liquid cooling system to have a nice OC if you want

  • Like 1
Link to comment
Share on other sites

Hi Fabio,

 

 

 

Thanks for the information!!

 

 

 

I have finally able to boot with just three patches, without the KernelXCPM. It was some kext in my old 10.13.6 kext folder. I had help from KGP on the PCI implementation, also his kext on a X99 board, and the hack is working very well now. I want to thank you for giving my the lead on the XCPM, I did learn something about patches and fundamental of computer stuffs. Being a person totally an alien to IT and computer programming, your input really helps a lot!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.