Jump to content

jsl2000

Members
  • Posts

    117
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by jsl2000

  1. No. Should I enable CurrentCpuInfo and disable patch 0 for re-testing ? Can I apply these 3 patches ? Which one is correct for 6C/6T ?
  2. This OC 0.7.2 debug-Shanee can not boot legacy FX-6300 which always got immediate dead on booting. So I stay at released OC 0.7.1 which worked perfectly in my both FX-6300 and Ryzen 1700X hackintoshs now.
  3. I can confirm that with the released OC 0.7.1 that "algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD" is not needed for Monterey ß3 in my FX-6300 hackintoshs, but I can NOT enable ProvideCurrentCpuInfo which always got dead on red screen !
  4. Thank you very much. This brief version can update Monterey beta2 to beta3 without any issue. The only issue is RestrictEvents.kext can not show Ryzen CPU name correctly with this brief version. I'll try to boot by Clover tomorrow and let you know the result. Great news: My FX-6300 also worked at Monterey beta3 now by OC 0.7.1 and it shows correct AMD CPU name !
  5. Thanks again ! You are my hero ! This brief version can boot Monterey beta2 now ! I'll try to boot beta3 after update it.
  6. Thanks for your prompt reply and help. Mine is Ryzen 1700X (8C/16T). So what's the correct patch for this ? config.plist.zip
  7. Follow your instruction and adapted with your config-patch.plist it still can not boot beta2 or beta3 of Monterey. It can boot 10.13.x~12.0 beta1 only. config.plist.zip
  8. Thanks for this brief version in which I have disabled two Aquantia Ethernet and found that it can boot my Ryzen 1700X hackintoshs and showed correct 6 cores for FX-6300 hackintoshs at Monterey beta1 with OpenCore 0.7.1, but not working at beat 2 yet !
  9. Yes, it's me too in another website of Shaneee, but not here. Because my original name jsl2000 can not login there which forced me to use another name for me. That means I did not use 2 different names in the same forum.
  10. Eventually my Ryzen 1700X can boot Clover 5137 at Monterey without previous issues now. My config.plist attached here: [Edit] Your previous config.plists had some typing error such as 10.5 instead of 10.15 which may cause some trouble to boot smoothly. config.plist.zip
  11. FX-6300 with RX-560 and Ryzen 1700X with RX-580 (the same series of GPU)
  12. I use different patches for FX-6300 (15h_16h) and Ryzen 1700X (17h_19h) respectively. OpenCore can boot both without any issue, but up to now only Clover can boot FX-6300 successfully. The problem maybe related to other kexts/setting besides kernel patches because it hang before complete login desktop with Apple Icon visible. [Edit] It must due to imperfect AMD kernel patching because it can boot fast and smoothly to desktop with working Mouse/keyboard after correction of some kernel patching.
  13. I have tried your minimal patches but it got KP during booting (fault CPU). I think several patches related to CPU cores and packages can NOT be omitted during booting.
  14. The attached is what my FX-6300 hackintoshs booted now: config-Clover-M5A-Monterey.plist.zip
  15. But there is no such an issue in my FX-6300 hackintoshs which can boot Clover 5137 now.
  16. Thanks for your suggestion and attached clover's config.plist. Your Quirks is not compatible with my Ryzen 1700X hackintoshs, but your config.plist can boot to desktop now. The remaining issue is frozen before login or loaded with Finder. I need figure out whether it's due to RX-580 or something else.
  17. Thanks, but it can NOT boot in my Ryzen 1700X hackintosh. It just hanged before +++++++++++++++++++++ appears.
×
×
  • 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.