Jump to content

jsl2000

Members
  • Posts

    123
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by jsl2000

  1. I had a very strange problem in my FX-6300 hackintosh. Unable to update from Monterey 12.0 to 12.1 or from Big Sur 11.6.1 to 11.6.2: It's Macintosh HD always got reboot loop. The only solution is got updated Macintosh HD from other hackintoshs, then it can reboot 3 times successfully to newer version. No such an issue in my Ryzen 1700X hackintosh with both OpenCore 0.7.6 and Clover 5141. [Solved on 2021-11-22] This issue was solved by the following method: (1) OpenCore 0.7.5 (2) SMBIOS=MacPro7,1 (3) SecureBootMode=j160 To get updated Macintosh HD at first (4) SecureBootMode=Disabled To reboot for 3 times and complete update process without reboot loop now ! [Waiting for solution] I don't know why using the similar method of HWTarget in Clover 5142 did not work for me. My Clover's config.plist and EFI are attached here. config.plist.zip EFI 2.zip
  2. Thanks for your prompt reply. I just looking for working FX-8xxx hackintoshs which can provide me reference for comparison between FX-6300 and FX-8xxx.
  3. May I know your another AMD hackintoshs (Asrock Fatal1ty 990fx, Amd FX 8350 4.6 ghz, AMD r9 270x 2gb x2 in CrossfireX) can boot Big Sur & Monterey too ? With OpenCore or Clover ? Can you share its config.plist for reference ?
  4. Thank you very much. Based upon your config.plist with minor modification for my special hardware requirement it can boot Big Sur and Monterey successfully with Clover 5141 again ! config.plist.zip
  5. No, after update BIOS only OpenCore 0.7.6 or 0.7.5 still working perfectly, but failed of Clover 5141 or 5142. For clover 5141 It can past ++++++, then frozen after something. So I guess I need modify something in Clover's config.plist.
  6. Thanks, but I can not find the option for Resize bar in my MB's BIOS settings. Is it present in more modern MB for Intel 9th/10th generation & AMD TRX40 MB ? In my Z490 hackintoshs it's located in Advanced> PCI Subsystem Mine is ASUS Crosshair VI Hero which was produced in 2018. I can disable ResizeAppleGpuBars in Booter & ResizeGpuBars in UEFI with Clover 5141.
  7. 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 !
  8. Thanks and may I know where is your TRX40 OP located because I can not find it here by search ?
  9. Revert to Clover 5141 got the same problem. Revert to old BIOS no vain too. Can you share your working Clover EFI for me ?
  10. 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 ?
  11. Thanks for your prompt reply and advice. preboot.log.zip 2021-12-11_10-23_BOOTX64.EFI.log.zip
  12. 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
  13. Thanks again ! After addition of Shaneee fix pat patch it works now for both Big Sur and Monterey ! config.plist.zip
  14. 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.
  15. 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
  16. Thanks for your correction and I had similar error for Replace High Sierra to Mojave in Clover's config.plist too.
  17. 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 !
  18. 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.
  19. 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.
  20. 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 ?
  21. 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 ?
  22. 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.
  23. 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
  24. 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.
×
×
  • 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.