[HELP] Wake Failure issue on AMD Ryzen 5600H while installing Hackintosh.

shivamsnaik

New member
AMD OS X Member
Jul 25, 2023
7
1
3
CPU:
Ryzen 5 5600H
I have been trying to install Hackintosh on my laptop for a few days. I have tried building the whole EFI from scratch using the Dortania guide, and tried replicating EFIs from different users who succeeded in installing Hackintosh with similar configs.

Yet, I am always seeing the same error: AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82

I have done the following changes to my BIOS:
  1. Disabling XHC1 using UniversalAMDFormBrowser.
  2. Select the Discrete Graphics Only option.
  3. Disabled Virtualization.
  4. Disabled Secure Boot.
I have attached two versions of the EFI folder configured for the information. "EFI.zip" is the latest version which I adapted from Here. I have also attached the full opencore-log, incase it helps describe my problem better. If anyone could help me figure out the problem, I would be really grateful. As I feel I have tried everything that I have come across.

System Specifications:

OpenCore Version -
OpenCore-0.9.3-DEBUG
Laptop Model - Lenovo Legion 5 Pro - 16ACH
Motherboard Model - LENOVO 82JQ
Motherboard Details - LENOVO LNVNB161216
CPU - AMD Ryzen 5 5600H with Radeon Graphics
Dedicated GPU - Nvidia RTX 3060 Laptop
Integrated GPU - AMD Cezanne
Ethernet - Realtek RTL8168/8111 PCI-E Gigabit Ethernet Adapter
Wifi and Bluetooth - Intel Wifi 6 AX200 160MHz Wireless Network Adapter
Audio Codec - Realtek ALC287 @ AMD K19.5 - Audio Processor - High Definition Audio Controller (Standalone AZ)
Storage - Samsung SSD 970 EVO Plus 1TB and SKHynix_HFS512GDE9X084N
CPU Architecture - 64bit
 

Attachments

Last edited:
Hi there,

Thanks for your post. I believe your system could boot macOS but you’re going to have to disable your Nvidia discrete GPU because it is unsupported under macOS.
Instead what you are going to have to do is disable your Nvidia discrete GPU in BIOS, delete Whatevergreen.kext from your EFI/OC/Kexts and replace it with the latest
NootedRed.kext from this link which enables AMD Vega IGPUs. You have an AMD Cezanne IGPU so it may work. > https://github.com/NootInc/NootedRed/

At the Github site you'll first have to login to the site (create an account if you don't have one), go to the special Nootedred page I've directed here >
https://github.com/NootInc/NootedRed/actions/runs/5656539327 and click on the Artifacts button below the page. This will give you the latest compiled package for NootedRed.
You just need use the version of this kext in the Release folder, and place it into your EFI/OC/Kexts (not forgetting to add and enable it in the config.plist under Kernel > Add).

You may also need to add in PCI device properties for your AMD IGPU if just adding it doesn't work. You can check how the AMD IGPU settings in config.plist should look like here (under the Device Properties section). > https://forum.amd-osx.com/threads/r...ta-—-radeon-graphics-8-gb-renoir-—-nred.4566/
It may require you to also check what your IGPU properties are under Windows Device Manager > Hardware IDs (so that you can add it into the Device Properties in the config.plist).
 
  • Like
Reactions: shivamsnaik
Hi there,

Thanks for your post. I believe your system could boot macOS but you’re going to have to disable your Nvidia discrete GPU because it is unsupported under macOS.
Instead what you are going to have to do is disable your Nvidia discrete GPU in BIOS, delete Whatevergreen.kext from your EFI/OC/Kexts and replace it with the latest
NootedRed.kext from this link which enables AMD Vega IGPUs. You have an AMD Cezanne IGPU so it may work. > https://github.com/NootInc/NootedRed/

At the Github site you'll first have to login to the site (create an account if you don't have one), go to the special Nootedred page I've directed here >
https://github.com/NootInc/NootedRed/actions/runs/5656539327 and click on the Artifacts button below the page. This will give you the latest compiled package for NootedRed.
You just need use the version of this kext in the Release folder, and place it into your EFI/OC/Kexts (not forgetting to add and enable it in the config.plist under Kernel > Add).

You may also need to add in PCI device properties for your AMD IGPU if just adding it doesn't work. You can check how the AMD IGPU settings in config.plist should look like here (under the Device Properties section). > https://forum.amd-osx.com/threads/ryzen-5-4600g-—-ventura-13-5-sonoma-public-beta-—-radeon-graphics-8-gb-renoir-—-nred.4566/
It may require you to also check what your IGPU properties are under Windows Device Manager > Hardware IDs (so that you can add it into the Device Properties in the config.plist).
Hi @Middleman. Thanks a lot for guiding me with the iGPU properties. I suppose it helped the OC identify my iGPU without any issue. However, I am getting a new error now. It gets stuck at a different point. I have attached a photo of the error along with the new EFI partition. In the debugging log, it gets stuck at EB|LOG:EXITBS:START.

I tried all the modifications given in Dortania Troubleshooting page for EB|LOG:EXITBS:START, but none of the corrections are helping me get past this point. Is there anything I missed out?
 

Attachments

Last edited:
Hi @shivamsnaik,

Okay. I see you are missing a few other kexts such as USBPort.kext and the npci=0x3000 boot-arg for the AMD IGPU. Did you create any custom USB maps at all? You will need them going forward.

As for other things I’d suggest you take a look at this here for another Lenovo laptop. It is similar to your build but is using a 5800H instead. If you change the AMD kernel patch values to match yours and add in the NootedRed instead of Whatevergreen it could work for your setup.

 
  • Like
Reactions: shivamsnaik
Hi @shivamsnaik,

Okay. I see you are missing a few other kexts such as USBPort.kext and the npci=0x3000 boot-arg for the AMD IGPU. Did you create any custom USB maps at all? You will need them going forward.

As for other things I’d suggest you take a look at this here for another Lenovo laptop. It is similar to your build but is using a 5800H instead. If you change the AMD kernel patch values to match yours and add in the NootedRed instead of Whatevergreen it could work for your setup.

Thanks for taking out the time to give me those references. I included the boot-arg mentioned by you, completed the USB mapping, and also had a look at the link provided. For USBPort.kext, is it required for my laptop with an AMD system?. Please let me know. Also, I followed everything given in the link, and updated by EFI file. I have attached the updated files.

I am still stuck with the same error. At this point, I am unable to figure out how people figured out to get past the OS selector with similar configuration as mine. I have been trying multiple links since a week, with no luck.

I must be committing some major mistake, but unable to pinpoint that. If you could please have a look at my EFI in your free time, It would be really big help.
 

Attachments

Okay @shivamsnaik,

I've looked at your EFI and made a number of adjustments, please check below. To help simplify things I have based it on this EFI profile but using 6 cores.

One of the very first issues you should be aware of with EFIs is the SMBIOS settings. As yours is a laptop it's not recommended you use any other such as iMac or MacPro.
Granted, you are now also using NootedRed, and that currently has only a handful of working compatible SMBIOS setups such as iMac19,1 and iMacPro1,1.

Secondly you had quite a number of kexts enabled, and some weren't required (such as SMCProcessor.kext which is for Intel CPUs or IntelBluetoothInjector which is not needed for Monterey onwards). For the time being I've not enabled any Bluetooth kexts (for testing purposes) but should you need it just enable Bluetoolfixup, IntelBluetoothFirmware and IntelBTPatcher.

As for everything else I've enabled the Airportitlwm wifi and added default alcid=1 for the audio.

Also USBToolbox must be loaded alongside UTBMap.kext for it to work. The arrangement is different for USBMap or USBPorts.kext, both of which doesn't need an accompanying kext.
 

Attachments

  • Like
Reactions: shivamsnaik
Okay @shivamsnaik,

I've looked at your EFI and made a number of adjustments, please check below. To help simplify things I have based it on this EFI profile but using 6 cores.


One of the very first issues you should be aware of with EFIs is the SMBIOS settings. As yours is a laptop it's not recommended you use any other such as iMac or MacPro.
Granted, you are now also using NootedRed, and that currently has only a handful of working compatible SMBIOS setups such as iMac19,1 and iMacPro1,1.

Secondly you had quite a number of kexts enabled, and some weren't required (such as SMCProcessor.kext which is for Intel CPUs or IntelBluetoothInjector which is not needed for Monterey onwards). For the time being I've not enabled any Bluetooth kexts (for testing purposes) but should you need it just enable Bluetoolfixup, IntelBluetoothFirmware and IntelBTPatcher.

As for everything else I've enabled the Airportitlwm wifi and added default alcid=1 for the audio.

Also USBToolbox must be loaded alongside UTBMap.kext for it to work. The arrangement is different for USBMap or USBPorts.kext, both of which doesn't need an accompanying kext.
Hi, thanks a lot for modifying the EFI partition and correcting few of the mistakes I had made.

I tried out the EFI paritition and modified the SMBIOS as you mentioned. The result was the same. It is still throwing the same error.

I feel now if something unknown about this particular system has something to do with these problems. I have pretty much tried everything from Dortania, but the issues persist. I'll probably keep trying if something comes up on this forum related to my configurations.

Anyways, thanks alot for your help :)
 
  • Like
Reactions: Middleman
You’re welcome. One more thing you could do before you go is to run ResetNVRAM. Run it first then reboot with the new EFI. That sometimes helps clear whatever settings that remains in memory which stops the system from booting up with the new configuration.
 
  • Like
Reactions: shivamsnaik
Hello. I have almost the same config as you, except, mine is ryzen 5 5600H, with GTX 1650 hp pailion.
I am also stuck. Do post here if there is some development from your end.
 
  • Like
Reactions: shivamsnaik
Okay guys,

I guess you all probably familiar with the general Opencore build so I won't say anything about the EFI. I had a brainstorm the other day and think what you are all missing from your setup is likely a SSDT-GPU-DISABLE. > https://dortania.github.io/Getting-Started-With-ACPI/Laptops/laptop-disable.html

I would highly suggest you look at the above and see what you get. You will need access to Windows with your dGPU enabled, and then disable it once you've got the PCI values for the SSDT put them into OC/ACPI and then in your build use NootedRed instead of Whatevergreen.
 
  • Like
Reactions: shivamsnaik
You’re welcome. One more thing you could do before you go is to run ResetNVRAM. Run it first then reboot with the new EFI. That sometimes helps clear whatever settings that remains in memory which stops the system from booting up with the new configuration.
Thanks for the suggestion. I tried clearing NVRAM, but the result remains the same. I'll post here incase anything works beyond the current stage.
 
Hello. I have almost the same config as you, except, mine is ryzen 5 5600H, with GTX 1650 hp pailion.
I am also stuck. Do post here if there is some development from your end.
Hey. I can totally understand the frustration :(. I'll surely post here incase I proceed further.

Please give me suggestions if incase the same happens with you. :)
 
Okay guys,

I guess you all probably familiar with the general Opencore build so I won't say anything about the EFI. I had a brainstorm the other day and think what you are all missing from your setup is likely a SSDT-GPU-DISABLE. > https://dortania.github.io/Getting-Started-With-ACPI/Laptops/laptop-disable.html

I would highly suggest you look at the above and see what you get. You will need access to Windows with your dGPU enabled, and then disable it once you've got the PCI values for the SSDT put them into OC/ACPI and then in your build use NootedRed instead of Whatevergreen.
I have actually included the GPU disable kext as well in my EFI after a discussion with you. The result remains the same.

I am wondering if there are any additional changes to the config.plist that can be done (other than the instructions given in Dortania Troubleshooting page) to solve the following problem?
[EB|LOG:EXITBS:START]
 

Attachments

Good news Boys!! I have somehow gotten Big Sur Installer booted up. Not Installed yet, will test. For the folder I included, try replacing my SSDTs and Serial Number values with yours and try booting.

EDIT: Monetary Installer booted up!! No Ventura though
 

Attachments

Last edited:
@jansir

Just letting you know that I've updated your EFI to latest OC 0.9.3 which also includes the latest AMD kernel patch. This was the main reason why you couldn't install Ventura.
Also because you had an older version of OC that still had the Bootstrap folder.

Also, I saw you had put the Heliport.dmg into the kext folder. That is NOT how you install it!
You need to first have itlwm.kext enabled in the Kexts folder and after getting into macOS run and open the Heliport.dmg in desktop mode. Then from there install it as an app into your Applications folder. It will then appear as an extra Wifi icon on your upper menu taskbar from which you then select your wifi network.
 

Attachments

  • Wow
Reactions: shivamsnaik
  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.