[Help needed] Great success, but then... insanity

reyr

New member
AMD OS X Member
May 19, 2025
5
1
1
1
CPU:
5600x
So, after years, I've decided to build a Hack again.

I followed Dortania's guide down to the letter, build my own USB map, used as litte generic SSDT's as possible, etc... so after only like 6 hours:

It boots, my CPU is nicely integrated and even iServices worked flawlessly OOTB!

I was very pleased with it.

Here`s the insanity factor: I've spent the last 4 day trying to get sleep, shutdown and reboot to work.

As I've found out, they're very much linked to each other.

Here's the issue: whenever I either wake the Hack from sleep, restart or turn on after shutdown (from macOS), it locks up hard, aka firmware crash (?). Also with sleep, it sometimes Instant-Wakes.

Means: Fans spinning violently, complete hanging until fully power-cycled.

I tried everything applicable in these guides:

As you can see in my config.plist in the attached EFI folder (kexts removed, but theyre all in the plist anyway), there are a lot of sleep / usb 'fix' kexts (configured acording to their respective guides).
GPRW and PTSWAKTTS are SSDTs allegedly fixin sleep issued too.

These are almost all I tried.

Everything mentioned above also works perfectly fine without those sleep kexts and SSDTs.

BIOS Settings:
  • WOL off
  • WOPS2 off
  • S3 Sleep to Auto
  • Peripheral Wake from S4/S5 Sleep off
  • TPM off
  • other BIOS settings mentioned in Guides

Hack Specs:
  • Ryzen 5600X, no OC
  • Radeon RX6800, no OC
  • 32GB 3200Mhz DDR4 RAM
  • ASROCK B550M PRO4 w/
  • REALTEK 8811H NIC
  • Compatible NVMEs
  • No Wireless
  • MacPro7,1 SMBIOS
  • OS 15.5

It may be one of my USB controllers, as my cheap chinese wireless keyboard stays on when the Hack is put to sleep. I can't figure out the f*cker's issue tho, I've injected USBX devices and mapped my own USBmap, which seemd to be working perfectly.

I've avoided manual System-SSDT editing for now as I'm multi-booting with Win11 and Fedora (on a different drive, if that matters) and don't want to break anything.

This is the first time asking for help on the Internet, but I'm just at a loss right now.

So, if anyone finds the time and kindness to give advice / look into my EFI, I'd be very grateful.

Thanks a lot,

rey

1000013935.jpg
(success tax)
 
Last edited:
  • Like
Reactions: turko35408
Solution
First of all: thanks a lot man.

Your EFI did not fix it,

However:
Getting off of my high horse, admitting my limited competence and building a USBMap with USBToolbox did.

I'm pretty sure the issue was that my Case USB 3.1Gen2 Type C is on a MoBo adapter (A-Header to C-Case Connector).

Again, many thanks for helping, you got me on the idea of building another Map.

One more thing, changing SMBIOS properties (not Type) shouldnt cause any issues, right?
Not that I dont trust you, just that its on here now.

Im very sorry for wasting your time.
Best from AT,
rey
Sorry, just saw I shouldve posted in Post-Install. Hope its no big Problem.
Edit: Thanks for changing, mods!
 
Last edited:
Try this revised and cleaned up EFI folder, see if this helps.

I have removed a couple of unnecessary SSDTs, cleaned up the config.plist and made a few other changes, including:
  1. Disabled XhciPortLimit Quirk, as you have a custom USBMap kext.
  2. Added a missing USBConnector to one of the ports in your USBMap kext.
  3. Removed any unnecessary entries from the config.plist.
Test the EFI on a spare USB pen drive, don't overwrite or erase your current EFI until you are sure the one attached works.
 
  • Like
Reactions: reyr
Try this revised and cleaned up EFI folder, see if this helps.

I have removed a couple of unnecessary SSDTs, cleaned up the config.plist and made a few other changes, including:
  1. Disabled XhciPortLimit Quirk, as you have a custom USBMap kext.
  2. Added a missing USBConnector to one of the ports in your USBMap kext.
  3. Removed any unnecessary entries from the config.plist.
Test the EFI on a spare USB pen drive, don't overwrite or erase your current EFI until you are sure the one attached works.
Oh wow thanks man, youre awesome!
Got some job hunting todo now, so Ill it try later and report back!
Many thanks again!!
 
Best of luck with the job hunting!
 
Best of luck with the job hunting!
Thanks a lot, Ill need it.
Hey stupid Question, Ive just looked through the plist, have you generated a new SMBIOS or did I really forget to anonymize it?
 
You forgot to anonymise it.
 
  • Like
Reactions: reyr
First of all: thanks a lot man.

Your EFI did not fix it,

However:
Getting off of my high horse, admitting my limited competence and building a USBMap with USBToolbox did.

I'm pretty sure the issue was that my Case USB 3.1Gen2 Type C is on a MoBo adapter (A-Header to C-Case Connector).

Again, many thanks for helping, you got me on the idea of building another Map.

One more thing, changing SMBIOS properties (not Type) shouldnt cause any issues, right?
Not that I dont trust you, just that its on here now.

Im very sorry for wasting your time.
Best from AT,
rey
 
Last edited:
Solution
  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.