Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

@Elias64Fr & @CaseySJ :

Been following your TB developments with passion and secrete hope !! ;-)

Also, in parallel I've been trying understand & adapt your findings to my Gigabyte Z390 Aorus Xtreme, where the TB ACPI is actually on RP01 (not RP05 as on Designare).

So, placed RehabMan's ACPIDebug.kext in /Library/Extensions/ (sudo chown -R root:wheel ACPIDebug.kext) and created a SSDT-RMDT.aml (attached), but I only get a single system log line displayed (via Hackintool), no more ACPI debugging information:
Code:
Timestamp                       (process)[PID]   
2020-01-22 07:13:45.052852+0000  localhost kernel[0]: (ACPIDebug) <ACPIDebug`org_rehabman_ACPIDebug::start(IOService*)> ACPIDebug: Version 0.1.4 starting on OS X Darwin 19.2.

Can you (both) please share your configuration for this TB testing ?

Thanks.
 

Attachments

  • SSDT-RMDT.aml
    600 bytes · Views: 105
FWIW. I never sleep the Hack. I'm not convinced that in the long run "Jettison" will protect (the iLok, the eLicenser, and the USB stick that holds the Waves licenses) from damage. So, for my use, the machine is only on or off. Mostly it's on. If I want to save electricity, I quit the app or unload the VSL session. I also don't sleep my real Macs that run Pro Tools. It just causes more problems than it saves for me.

Yeah. Sleep and DAW's, just don't do it.
 
@Elias64Fr & @CaseySJ :

Been following your TB developments with passion and secrete hope !! ;-)

Also, in parallel I've been trying understand & adapt your findings to my Gigabyte Z390 Aorus Xtreme, where the TB ACPI is actually on RP01 (not RP05 as on Designare).

So, placed RehabMan's ACPIDebug.kext in /Library/Extensions/ (sudo chown -R root:wheel ACPIDebug.kext) and created a SSDT-RMDT.aml (attached), but I only get a single system log line displayed (via Hackintool), no more ACPI debugging information:
Code:
Timestamp                       (process)[PID]
2020-01-22 07:13:45.052852+0000  localhost kernel[0]: (ACPIDebug) <ACPIDebug`org_rehabman_ACPIDebug::start(IOService*)> ACPIDebug: Version 0.1.4 starting on OS X Darwin 19.2.

Can you (both) please share your configuration for this TB testing ?

Thanks.
Hello @augustopaulo

SSDT-RMDT contains logging functions that can be used by any other SSDT. The log messages themselves are placed on a queue that is read by ACPIDebug.kext and copied into the macOS system log.

The line you quoted is just a confirmation that ACPIDebug.kext has started up.

In order to see actual logs we have to use a modified SSDT that invokes the various logging functions in SSDT-RMDT. These logging functions are:
  • RMDT.P1 --> for a log message with one argument such as: log ("Hello")
  • RMDT.P2 --> for a log message with two arguments such as: log ("this", "that")
Similarly, RMDT.P3 through RMDT.P7 handle log messages with up to 7 arguments.

The Thunderbolt SSDT modified by @Elias64Fr contains numerous calls to RMDT.P1, which is why we see those messages in the system log.
 
I'm also reading that the AppleALC kext reconnecting the HDMI audio after sleep is a thing contributing to crashes. Since I don't use it, maybe I'll just delete and disable the onboard audio since I don't want it anyway.

update...
seems to be AppleALC. If I manually inhibit sleep or remove the kext and allow sleep then everything works fine. Since I don’t need on-board sound I’m removing the Kext from clover to keep things simple. I have 3 monitors. 2 are DP to DP and the other is DP to DVI. Audio midi setup shows the 2 DP to DP monitors as available audio destinations. Not sure if my monitor setup is part of the issue or not.
Interesting. I'll add this to the Sleep/Wake Troubleshooting Mini-Guide ("Sleep Aids").
 
Hi tried installing the extra scripts but clover bootloader doesn’t work and I get an error ocabc: found legacy aptioMemoryFix driver any recourse here ? I assume I can boot off the usb disk and change the efi on the ssd? Thanks
When installing Clover we just have to make sure to uncheck all UEFI drivers. It may have installed AptioMemoryFix. So you should be able to boot from USB flash disk, mount EFI partition of macOS SSD, then manually delete AptioMemoryFix.
 
I updated my OpenCore installation and still get a kernel panic, in the same place as before (see my screen shots posted previously). I did have to add -v to the boot arguments to see the panic this time though.

There's nothing terribly special about my build. I did install the RX580 in slot 2 and the Fenvi in the top (short slot)... but that's never given me any trouble, in Mojave or Catalina.
The fourth screenshot from that post (now 157 pages back!) suggests that the kernel panic occurred after 2 ACPI tables failed to load. One of those tables is SSDT-DTPG. However, when an ACPI table fails, it should not cause a kernel panic. We should remove SSDT-DTPG and update config.plist.

The kernel panic backtrace suggests the crash occurred while starting to load kexts. Please double-check all kext-related settings in config.plist -- make sure kext paths are correct and the files themselves are valid. Feel free to post your OpenCore config.plist (you may remove serial numbers from PlatformInfo).
 
Hi guys, all was going well with my Hack until Logic Pro started crashing immediately after start up.

I am on Mojave 10.4.6 and Logic Pro X 10.4.8 and after installing last week, and working fine - Logic is now crashing immediately after starting, not even getting to the project window.

I have tried starting Logic with these options - holding Option, holding Shift and holding Control. Nothing seems to work. I have also tried deleting all Logic preferences and databases.

I have attached the first part fo the Logic crash log as a text file, and it is seems it is Thread 0 reporting a crash.

Any help would be hugely appreciated :)
 

Attachments

  • Screenshot 2020-01-22 at 12.35.47.png
    Screenshot 2020-01-22 at 12.35.47.png
    228.3 KB · Views: 85
Hi guys, all was going well with my Hack until Logic Pro started crashing immediately after start up.

I am on Mojave 10.4.6 and Logic Pro X 10.4.8 and after installing last week, and working fine - Logic is now crashing immediately after starting, not even getting to the project window.

I have tried starting Logic with these options - holding Option, holding Shift and holding Control. Nothing seems to work. I have also tried deleting all Logic preferences and databases.

I have attached the first part fo the Logic crash log as a text file, and it is seems it is Thread 0 reporting a crash.

Any help would be hugely appreciated :)
Some A/V apps will crash if iGPU is set to non-headless mode (platform ID 0x3E9B0007). I would check this first. Platform ID is specified in reverse byte order and can be found here:
Screen Shot 2020-01-22 at 3.39.59 AM.png
This example shows 0300983E, is the correct headless platform ID (3E980003 backwards).
 
Have you also tried reducing RAM speed to 2666MHz or 2933MHz?

I don't know if this question is directed to me, but yes, I've lowered my RAM speed to 2666. Externals disk are properly unmounted/remounted on sleep/wake, but sleep will often not work properly(screensaver will kick in but PC will still be on) if I am actively using DAW software(looking at you, Cubase), and even after quitting.
I need to restart to get sleep to work properly.
Lowering the RAM speed gave me 3% lower geekbench results, so that's not a big deal.

Hm. I will try 2933 next. Thanks for the reminder.
 
Back
Top