AMD Hackintosh Tahoe Beta2 Works Great...Can't get to Beta3 or 4

CaliMark

New member
AMD OS X Member
Oct 23, 2024
7
0
1
CPU:
AMD
I have Mac OS Tahoe DP2 Running Great on my AMD A320M Ryzen 3 2200G 8GB (2GB VRAM), In fact it was able to get DP2 installed using OC-Simplify!

So, my question is for whatever reason using the same EFI that works for DP2 i can't get into DP3 or 4, everything seems to go fine until i get a lockup / freeze at some point after setting the REGION. Also if i do an upgrade from inside a working DP2 everything goes fine, i get to the login screen, but after getting to desktop i also lockup / freeze? So, what do i have to change between beta 2 or 3 that i just can't think of? Looking for any ideas, pretty sure i am all current on OC, KEXTS, AMD (beta) Kernel Patches....Help...Thanks...

CaliMark
 
The issue you are reporting doesn't sound like an OpenCore issue. i.e. one caused by the bootloader being set incorrectly. If it was an issue related to OpenCore the system would most likely kernel panic prior to starting the installation of Tahoe.

It sounds more like an issue with your installer files.

All I can think to suggest is to try reinstalling the latest beta of Tahoe using a newly downloaded copy of the Tahoe Beta 3 or 4 installer.
 
The issue you are reporting doesn't sound like an OpenCore issue. i.e. one caused by the bootloader being set incorrectly. If it was an issue related to OpenCore the system would most likely kernel panic prior to starting the installation of Tahoe.

It sounds more like an issue with your installer files.

All I can think to suggest is to try reinstalling the latest beta of Tahoe using a newly downloaded copy of the Tahoe Beta 3 or 4 installer.
Yea I've grabbed them multiple times and the SHA all match, and it would be weird that both the installer for Beta3 and 4 to both be corrupt or act the same way etc...Imagine if i spared another drive and set up a working beta2 (or any mac) and then i could access the other drive and maybe access some logs....I am only running 8gb only thought is that maybe beta3 needs more then 8gb, but again that seems weird since i can get decent performance from tahoe even w/ only 8gb...who knows...this one has me stumped....Again thanks for the ideas or suggestion!

CaliMark
 
Can you post a screenshot of your config.plist’s Kernel section in “OpenCore Configurator”?

That will tell us whether there are any kexts that should be disabled or replaced with something else.

Which GPU are you using? Or are you using iGPU with NootRx?
 
Can you post a screenshot of your config.plist’s Kernel section in “OpenCore Configurator”?

That will tell us whether there are any kexts that should be disabled or replaced with something else.

Which GPU are you using? Or are you using iGPU with NootRx?
Hopefully this is what you were hoping for as far as screenshots? I am using the iGPU in the Ryzen 3 2200G via NootedRed.
Again this EFI seems to make a very stable beta2! So again no idea why it locks up right before I can set up a new account on beta3/4

Thanks for taking the time to look at this.

CaliMark
 

Attachments

  • Screenshot 2025-07-23 at 11.26.39 PM.png
    Screenshot 2025-07-23 at 11.26.39 PM.png
    416.2 KB · Views: 21
  • Screenshot 2025-07-23 at 11.26.54 PM.png
    Screenshot 2025-07-23 at 11.26.54 PM.png
    329.1 KB · Views: 20
Is NootedRed compatible with Tahoe? Have others experienced similar crashes in latest Tahoe beta?

I would also suspect the RTL driver. Try disabling RealtekRTL8111 to see if stability improves.
 
Is NootedRed compatible with Tahoe? Have others experienced similar crashes in latest Tahoe beta?

I would also suspect the RTL driver. Try disabling RealtekRTL8111 to see if stability improves.
As far as i am aware a commit to nootedred gave it tahoe support not long ago. I haven't heard of others.

I did get excited the RTL Driver wasn't the most current, i had 2.4.2 and there was a 2.5.0 so i added that to my efi and beta2 the internet was still fine and everything seems good. Beta3/4 i had same results of a lockup or crash w/ 2.4.2 or 2.5.0 installed or not installed same end result of lockup, either right after login, or during setup right before setting your password. So still no luck for me getting beta 3/4 working, its installed just locks up....thanks for the suggestions and help.

CaliMark
 
A bit of an update....I was finally able to get Beta 3/4 to boot in using the boot-arg -liluoff so i didn't haven't much graphics or acceleration and it was slow but it did run w/o lockup and about mac id's as running at the time beta4! So, not sure what this tells me, does my system have issue w/ lilu itself or one of the plugin's. I do still have video, just no liquid glass or accel, i believe if i disable nootedred i don't see a desktop any longer. So, hopefully some of the smarter minds here have some more good ideas...Im closer...

CaliMark
 
Check which version of Lilu.kext you are using, if you haven’t done so already.

Make sure you are using the latest versions of all the kexts in your OC setup.
 
Check which version of Lilu.kext you are using, if you haven’t done so already.

Make sure you are using the latest versions of all the kexts in your OC setup.
Yes, i am current on all the kext etc...etc...and as i mentioned this efi runs a very stable beta2 its just has issue with 3/4....

I haven't seen any other success stories for beta 3-4 on similar hardware, seems like something has an issue w/ beta 3+ on older chipsets? Still trying to solve this! Thanks for any suggestions....trying to nail down where i need to reach out to one of the dev's....but for which....anybody have a nice quide for how to use the debug version maybe it will help me with a clue.

CaliMark
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.