New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
machdep.tsc.frequency on AMD CPU System - (maybe related to the miss of ProvideCurrentCPUInfo quirk) #487
Comments
+1 for this issue as well. Really needs to be looked at deeper. |
ProvideCurrentCpuInfo has no relation to AMD CPU. |
No @SergeySlice sorry to contradict you
And with Clover Bootloader we have wrong TSC data from many time...in Monterey 12.2 it produces bad animation and many others problem Thank you for your time |
Grazie @SergeySlice your latest R5144 solve almost all problem AMD users add with Clover and TSC:
|
This problem is present also in old Clover Release (tested till R5139)
In OSX greater than 12.01 it produces many disasters as instability, double speed animation in dock o in YouTube , bad GPU performances, WIFi disconnection and so on)
Attached here a pic:
left is Clover terminal output and right is about Opencore boot loader output
Attached also 2 logs, first one is about a "working" OSX like Monterey 12.01:
2021-12-26_09-19_BOOTX64.EFI.log
I say "working" because in Monterey 12.01 system works pretty fine and the only problem I see is a GPU performance loss of about 12% if compared with OpenCore boot loader
Second one log is about 12.2 (it is similar or the same in 12.1 OS):
2021-12-26_09-23_BOOTX64.EFI.log
12.1 is a disaster, with all problem said above
I attach here also the patches (old) we have to use in Clover Bootloader:
patches.plist.zip
These above patches are included in a newer release in OpenCore Bootloader Kernel quirk
We can't use this new three patches because Clover manages in a different way masking parameters, and C3/ret does not work as it does in OpenCore
If you need others things to debug in a more proper way ask and I will try to answer as soon I can
Thank you
The text was updated successfully, but these errors were encountered: