kgp
Retired
- Joined
- May 30, 2014
- Messages
- 6,743
- Motherboard
- ASUS WS X299 Sage 10G
- CPU
- i9-7980XE
- Graphics
- Vega 64
- Mac
- Mobile Phone
Ugh, so I got the MatchOS format incorrect? Why do you advocate not using it? I need to be developing under both OS releases throughout the day, and I thought that this is what MatchOS is for.
The matchOS entries just introduce confusion to OSX and might be also applied to all other patches without MatchOS entries. Use different EFI-Folders for each macOS build. Each macOS should have it's system disk and it's EFI-Folder. In this case all macOS entries in the kext patches should be totally obsolete.
Sadly, no - there's still nothing under _SB/PC03@0/BR3X@10000/UPSB@0/DSB2@20000 save for a lonely IOPP entry.
I did not check yet whether or not your SSDTs and your particular ACPI path are properly implemented..
Which variable you get after nulling BR3B.SL0A? Maybe you have to null another variable after nulling BR3B.SL0A? Something is totally wrong. DSB2 should never be empty (even no XHC USB device is connected), in case SSDT-TB3-_L69-BR1X.aml also properly applies. It is also empty, after connecting a XHC USB device directly to your TB-Adaptor? Why do you have all XHC USB ports under DSB1 instead of DSB2? Are these USB ports part of your monitor? Maybe that's why the implementation of DSB2 fails straight away? Can you disable the USB ports on your monitor for testing? I am not familiar with such TB configuration.
I use an LG 5K UltraFine display as my only display - it's a TB3 display, so there is always a TB device connected. The KP happens every time I try to wake the machine, sadly.
That's weird.. I never faced any KP issue when using TB.
Edit:
BTW.. you know that against all instructions you did not rename and order ALL CPs! Thus, currently you are running a strange mixture of PRs and CPs. No idea what would be the consequence of such CPU core implementation .
Last edited: