yapan4 Posted April 10, 2019 Share Posted April 10, 2019 I think it will be difficult for developers to help without the hardware in their hands Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 (edited) So to solve the problem we have to buy @apianti a complete Hackintosh rig with Xeon W and C422 mobo. It will be expensive Edited April 11, 2019 by obus Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 Just now at home I switch from boot with xcpm_bootstrap (used last 10.14.5b1 and 10.14.5b2) back to FakeCPUID+_xcpm_pkg_scope_msrs (used since macOS 10.14.1) and .... don't work!!!! FakeCPUID + _xcpm_pkg_scope_msrs don't work at all on 10.14.5b2 probably on 10.14.5b1 also don't work. So, _xcpm_pkg_scope_msrs_PMhart don't useful since 10.14.5b1 (Darwin 18.6)!!! xcpm_bootstrap (c) Pike R. Alpha still useful, xcpm don't work in this case. Such an additional unpleasant news Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 (edited) 7 minutes ago, yapan4 said: Just now at home I switch from boot with xcpm_bootstrap (used last 10.14.5b1 and 10.14.5b2) back to FakeCPUID+_xcpm_pkg_scope_msrs (used since macOS 10.14.1) and .... don't work!!!! FakeCPUID + _xcpm_pkg_scope_msrs don't work at all on 10.14.5b2 probably on 10.14.5b1 also don't work. So, _xcpm_pkg_scope_msrs_PMhart don't useful since 10.14.5b1 (Darwin 18.6)!!! xcpm_bootstrap (c) Pike R. Alpha still useful, xcpm don't work in this case. Such an additional unpleasant news Thats really bad because with XCPM_bootstrap I have full throttle on my processor. I will test now with 10.14.5 beta 2. I will give PMhart a call. I have an sms conversation with him. I will keep in touch. Edited April 10, 2019 by obus Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 (edited) 32 minutes ago, obus said: I will test now with 10.14.5 beta 2. I will give PMhart a call. I have an sms conversation with him. I will keep in touch. Good 32 minutes ago, obus said: Thats really bad because with XCPM_bootstrap I have full throttle on my processor. My too. Disabling AppleIntelCPUPowerManagement.kext somewhat corrects the situation... also I do some sysctl dumps as is - with enabled bootstrap path, disabled AppleIntelCPUPowerManagement.kext, enabled "PluginType" yapan4 sysctl dumps.zip Edited April 10, 2019 by yapan4 Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 (edited) I don't have the bootstrap patch anymore so could you please send it to me? I'm stuck +++++++++++ Edited April 10, 2019 by obus Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 config.plist.zip Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 With bootstrap patch you don't need FakeCPUID or kernel patch Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 Only bootstrap patch, any FakeCPUID and disabled _xcpm_pkg_scope_msrs_PMhart, that all. Then AppleIntelCPUPowerManagement.kext in /S/L/E renamed to AppleIntelCPUPowerManagement.kext.bak Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 You can delete the FakeCPUID. You don't need it with bootstrap. Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 Yes, deleted... 5 minutes ago, obus said: You can delete the FakeCPUID. You don't need it with bootstrap. Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 (edited) Bump Edited April 10, 2019 by obus Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 Sorry! I mean this thread: Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 (edited) Well, it's not KernelAndKextPatches 10.13x,10.14.x C422 Edited April 10, 2019 by yapan4 Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 No but I was using them for booting High Sierra and some of this patches worked. Are you following the Clover thread now? https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?page=747I Link to comment Share on other sites More sharing options...
apianti Posted April 10, 2019 Share Posted April 10, 2019 (edited) Yeah, send me the hardware and I'll figure it out. No, actually, I think that the problem is because of the specialization of the mac-only CPU models, it has an MSR that is not present in other CPUs. So why you guys need to disable call to _xcpm_pkg_scope_msrs. Then you have full throttle because that is the state the processor started in and there is no frequency vector information available, so you must either fakeid to a model that does have them, or add them to the plist. There is a script available to do this. The xcpm_bootstrap forces unsupported cpus to use the information for some specific model, no idea which so it may be a incorrect model to switch. EDIT: As for the patches not working, get a hex editor, look for the patch in the kernel it did work in and look at what is around it and the general position, then look around in the newer kernels in that place for the same sort of stuff. It would be even easier if you can disassemble the kernel and look at the source, then you'll be able to find where to patch even easier. Edited April 10, 2019 by apianti 1 Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 I thought that I too was caught by demential when I saw that you suddenly was posting here when I was posting on the other site. Anyway where can we find this script? And is there a manual? Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 (edited) 27 minutes ago, apianti said: Yeah, send me the hardware and I'll figure it out. No, actually, I think that the problem is because of the specialization of the mac-only CPU models, it has an MSR that is not present in other CPUs. So why you guys need to disable call to _xcpm_pkg_scope_msrs. Then you have full throttle because that is the state the processor started in and there is no frequency vector information available, so you must either fakeid to a model that does have them, or add them to the plist. There is a script available to do this. The xcpm_bootstrap forces unsupported cpus to use the information for some specific model, no idea which so it may be a incorrect model to switch. Bravo, @apianti ...but how about apple-native Xeon Hackintosh build??? ...and Apple iMacPro1,1 with x86(non-Apple) Xeon? Edited April 10, 2019 by yapan4 Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 Ok. New working _xcpm_pkg_scope_msrs_PMhart 31d2e8b4fcffff -> 31D29090909090 1 Link to comment Share on other sites More sharing options...
yapan4 Posted April 10, 2019 Share Posted April 10, 2019 14 minutes ago, obus said: Ok. New working _xcpm_pkg_scope_msrs_PMhart 31d2e8b4fcffff -> 31D29090909090 I confirm it works on 10.14.5b2 Link to comment Share on other sites More sharing options...
obus Posted April 10, 2019 Author Share Posted April 10, 2019 1 hour ago, apianti said: There is a script available to do this. The xcpm_bootstrap forces unsupported cpus to use the information for some specific model, no idea which so it may be a incorrect model to switch. Hi @apianti do you mean PikerAlphas freqVectorsEdit script? Link to comment Share on other sites More sharing options...
apianti Posted April 10, 2019 Share Posted April 10, 2019 Yeah that's the one. 1 hour ago, yapan4 said: Bravo, @apianti ...but how about apple-native Xeon Hackintosh build??? ...and Apple iMacPro1,1 with x86(non-Apple) Xeon? I don't understand what you mean, you can't get the mac-only model for purchase as a regular customer and imacpros only have those models.... Link to comment Share on other sites More sharing options...
yapan4 Posted April 11, 2019 Share Posted April 11, 2019 (edited) 10 hours ago, apianti said: Yeah that's the one. I don't understand what you mean, you can't get the mac-only model for purchase as a regular customer and imacpros only have those models.... Apple CPUs sometimes appear on sale. Probably removed from native iMacPro after upgrade. There are reports from owners of such hackintosh machines (s2066 C422 motherboard + Apple-Xeon). Not successful, just like ours - it's impossible to boot without FakeCPUID and _xcpm_pkg_scope_msrs. Native iMacPro1,1 Mac does not have this problem and can work equally well with any Xeon Edited April 11, 2019 by yapan4 Link to comment Share on other sites More sharing options...
yapan4 Posted April 11, 2019 Share Posted April 11, 2019 (edited) @obus The situation is more or less cleared up for me but let's wait for the answer @apianti P.S. Sorry, there was an error(Apple -Non Apple) in my previous message, please review Edited April 11, 2019 by yapan4 Link to comment Share on other sites More sharing options...
apianti Posted April 11, 2019 Share Posted April 11, 2019 (edited) Yes the difference is the firmware. EDIT: I realize that you CAN buy those CPUs outside the supply chain, but I was trying to say that they are most likely not similar enough for the firmware to know what to do with extra stuff I'm assuming is there or why did they have special mac-only models made when it would have been cheaper to source already made CPUs? Edited April 11, 2019 by apianti Link to comment Share on other sites More sharing options...
Recommended Posts