jsl2000
-
Posts
117 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Events
Downloads
Everything posted by jsl2000
-
Yes, I know. Unfortunately I got the same problem as my original EFI. Unable to boot any MacOS from 10.13.6 to 12.1 by Clover 5142 or 5141 now !
-
Thanks and I'll test your EFI in my Ryzen 1700X hackintoshs.
-
Thanks and may I know where is your TRX40 OP located because I can not find it here by search ?
-
Revert to Clover 5141 got the same problem. Revert to old BIOS no vain too. Can you share your working Clover EFI for me ?
-
I can not boot any MacOS from 10.13.6 to 12.1 with Clover 5142 now even after repeated reset Nvram ! Any other possibility for this issue ?
-
Thanks for your prompt reply and advice. preboot.log.zip 2021-12-11_10-23_BOOTX64.EFI.log.zip
-
Before BIOS update I can boot Clover 5141 and OpenCore 0.7.5/0.7.6 successfully without any issue. However after BIOS update I can boot OC only, if booted by Clover 5142 it always got reboot after ++++++++++++++. I have tried to downgrade of BIOS or Clover all in vain. Can anyone check my Clover's config.plist or EFI.zip and give me some help ? config.plist.zip EFI.zip
-
Thanks again ! After addition of Shaneee fix pat patch it works now for both Big Sur and Monterey ! config.plist.zip
-
Thanks for your kind and prompt reply and help. Unfortunately this config.plist can boot both Big Sur and Monterey past +++++++++++++, but unable to login desktop successfully. I need figure out how to fix it or using my old config.plist temporarily because I can boot Ryzen and FX-6300 with old patches by OpenCore and Clover. The only disvantage is ProvideCurrentCpuInfo must be disabled to avoid red screen panic during booting.
-
Hi, fabiosun: I need your help to fix my Ryzen 1700X's Clover 5140.1 config.plist which can boot 10.13.6/10.14.6/10.15.7/12.0beta9, but always got freeze after +++++++++++++ for Big Sur 11.5.2 or 11.6.1. Using old config-working-Ryzen-5138.plist which can boot Big Sur, but always got hang after running for 1~2 minutes. No such an issue by OpenCore 0.7.2 or 0.7.4 with similar kernel patches. config.plist.zip config-working-Ryzen-5138.plist.zip
-
Thanks for your correction and I had similar error for Replace High Sierra to Mojave in Clover's config.plist too.
-
Thanks and I can confirm OC PR 0.7.2 working at Monterey beta3 without these 3 patches in my Ryzen 1700X hackintoshs. The reason I still kept many extra patches because I am a conservative person and try to keep compatibilities between FX-6300 and Ryzen 1700X hackintoshs from High Sierra to Monterey. It seems FX-6300 lost support from OC team since Monterey beta1. I can boot it at FX-6300 because I use previous working patches from High Sierra to Big Sur plus newer one at Ryzen 1700X. Without these experience and basic info I can not boot both now. Special thanks for your help and many excellent explanation and advice from here. In the past I can get support from insanelymac mainly and Shaneee's website sometimes. But recent 2~3 weeks your website provide the newest and excellent info and support as well as prompt reply which I could not find in any other websites. Thanks again and again you are the most wonderful person in this forum !
-
No, in order to boot Monterey beta2 & 3 I apply newer 3 patches in both Clover 5138 and OC 0.7.1 config.plist and it worked well up to now.
-
Thanks and that means if I apply the newer patches my current issue will bother me again by ocvalidate warning or interference. Hope in the near future the developer team of OC or Clover release better solution for FX-6xxx/8xxxx users.
-
Thanks for your explanation which is the great news for all AMD CPU users. In case of FX-6xxx which can not enable ProvideCurrentCpuInfo Quirk do you have any other solution ?
-
Do you mean by OC 0.7.1 or 0.7.2 if ProvideCurrentCpuInfo was enabled I don't need patch 0,1, & 2 ? Or just no need patch 1 & 2 ?
-
I need your help and advice to fix one problem I faced OpenCore 0.7.1 or OC PR 0.7.2: These two versions' ocvalidate always warn me about ReplaceMask of patch 1 & 2 which I need to boot kernel 17.0.0 to 20.x.x unless I changed from FFFFFFFFFF00 to FFFFFFFFFFFF it can not passed. In fact after change it can pass ocvalidate, but always failed to boot High Sierra to Big Sur now. Do you have any solution to fix it ? In Clover I had the same issue too.
-
For Clover you need set CPU parameters as the attached one: For OpenCore you should set DataHub as mine: [Edit] Some errors of patches for Replace in both config.plists were corrected. config-Clover-FX6300.plist.zip config-OC-FX6300.plist.zip
-
Yes, your theory and instruction are correct. Enabled ProvideCurrentCpuInfo Quirk can disable many patches related to core logical string, but my About this Mac issue still bother me up to now. Only Clover booting can fix it from Catalina to Monterey beta3 and the same issue occured at High Sierra and Mojave too! [Edit] No such an issue in FX-6300 hackintoshs from Catalina to Monterey beta3 booted by Clover or OpenCore. Unfortunately if ProvideCurrentCpuInfo was enabled my Fx-6300 hackintoshs will got red screen KP on booting Legacy OC.
-
Thanks for your prompt reply and advice. Set Number from 3841 to 0 did not fix this issue. Disable this unused patch (3) was also in vain to fix it. So I left it over and wait for other solution because it's harmless for this cosmetic issue.
-
Can you check my config.plist of OpenCore 0.7.1 in which related to ProcessorType is correct or not ? Number-->3841 ? This is the last step in which I need to improve now. Enabled ProvideCurrentCpuInfo can not fix this issue. Before OC PR 0.7.2 is it correctly shown in your hackintoshs ? config.plist.zip
-
Can you get correct CPU name in About This Mac by OpenCore PR ? Mine OC 0.7.1 always show Ryzen 1700X 8-Core as 8-Core Intel Xeon W instead.
-
Thanks for your hint which help me to boot Ryzen 1700X smoothly by Clover 5138 now: [Edit] Besides RestrivtEvents.kext add CPU->Type->String->0x0f01 Clover can show correct name of Ryzen 1700X now ! But no such a lucky by OpenCore 0.7.1 even Number -> 3841 (which=0x0f01 hex) was added in PlatformInfo -> Generic ->ProcessorType P
-
Thanks for your help and advice which make my dream come true in FX-6300 hackintoshs now. It can boot and update up to Monterey beta3 with OpenCore and Clover 5137. The next step will be reduction of my patches to minimal working setup from 10.13.6 to 12.0 beta3.
-
Thanks. So even RestrictEvents.kext can be disabled ?
