Yo, EliteMacx86!
I would like to thank you for your help and support of this wonderful forum ❤️
After some time, I managed to get both MacOS Big Sur and Monterey to work on these components (MacOS 13 Ventura should also work with this EFI, but I already managed to sell this PC and buy a MacBook...
Ops, DSDT file disappeared because his extension isn't allowed at this forum.
I'll attach my DSDT from SSDTTime now and ll attach origin tables from Clover some later(now 01:20 AM, at 5:30 I have to go to work, sry
Yoo, here is my dumped via SSDTTime DSDT.aml
I understand it.
I played a lot with the BIOS settings, but it did not lead to any effect.
Now I will set the settings according to one of your guides and update my post.
P.S. Thanks for ur answer, guys!!!
UPD:
Current results:
without cpus = 1...
Good morning.
I collected detailed statistics with logs (which, as I understand it, do not make much sense) and a description of the behavior of the system at boot.
Here is the results:
• Without any TscSync kexts - Monterey unsuccess (panic and reboot), Big Sur unsuccess(panic and stuck)
•...
Tried to use CpuTscSync by wy414012 and catch another panic and immediate reboot, when loading Monterey installer. With Big Sur I'm loading successfully.
I made changes to my EFI:
• Indeed, I shouldn't have generated an SSDT-PLUG for my Ivy Bridge E since it's need for Haswell and newer. I generated SDST-PM via ssdtPRGen and everything works great.
• Should I enable DisableIoMapper if I disabled VT-d in the BIOS?
• Put kexts in the right order...
Thanks for ur reply, bro.
I did all what u said, and deleted some more SSDT's from my EFI, not only PLUG.
And creater new PM SSDT with ssdtPRGen.
All's good, all USB ports work without USBTool, but now my PC have a lot of lags and long boot time.
I ll fix it and after this will post results...
Yoo ;)
After many attempts to install Big Sur on X79G motherboard, I finally managed to do it!
However, when running the Monterey 12.3 installer, I ran into a problem that I can’t solve for more than a day, namely, writing on the lines:
• Kernel trap at 0xffffff8007484f3b
• panic(cpu 0 caller...
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.