So I received " This version of Mac Os is not supported on this platform" followed by MAC-AA95BIDDAB27BB95
I used Imac 19,1 system definition. It shows the i9 9900k being the processor. I'm running an i7 8086k which is a binned 8700k , would the system definition that I chose be incorrect? should I use the i7 8700 ~ Non K def instead?
IIRC, 19,1 is turn key for Designare z390 Catalina upgrade. I could be wrong of course.
@CaseySJ When trying to copy, then rename, there was already another config.plist already present and thus did not allow me to rename. Did this occur being that I needed to copy and rename with a plist editor ? Can't you just rename or delete the old version and then copy the new one and...
www.tonymacx86.com
Thanks Casey! I had a few questions regarding the above linked Radeon guide:
1. As this is a new SSDT is this likely to break sleep? The reason I ask is because the only way for me to get 100% fully working sleep (with the machine not awakening randomly and going to sleep after 3 mins) was to apply your power management fix straight after a fresh install. The fix was in the first page of this thread:
Code:
cd /Library/Preferences
ls -l com.apple.PowerManagement.*
I've just now updated the Radeon Boost guide and included my GeekBench 4 and GeekBench 5 before/after chart, which is quite amazing. However, I found that using the SSDT prevented the system from switching on the AMD frame buffer at the end of the boot process so I've removed the SSDT. This is all quite new so please experiment and report findings.
2. I’m guessing as a worst case, if I apply the aforementioned Radeon SSDT in the Radeon mini guide, as well as the new kext, I can just run the above power management command again?
Probably best to avoid the SSDT for now. Try first with only the RadeonBoost kext and disable WhateverGreen with the -wegoff argument.
3. As we’re already on version 1.4 of this fix, assuming some time down the line there’s V1.x, if we find that has broken sleep, or something else, is there a simple procedure to roll back to the previous SSDT/kext, or do we have to restore from our Casey mandated backups?
Rolling back a kext is simply a matter of removing the bad one and copying a good one regardless of version.
4. Lastly, I haven’t got Netflix working on safari yet and am going to run the fixes. Should I do that after or before I apply the new Radeon mini guide changes?
The Radeon Boost procedure is completely optional. It might be better to fix Netflix first.
P.S. I’ll also run some Geekbench 4, cinebench and brute tests before and after so we can get some metrics going! I’ve also seen reference to OpenCL, Metal an GFXbenchmark tests that can be carried out. Is there any other tests yourself or anyone else would like me to try? I’m dual booting windows so don’t mind doing them there too to compare
So I received " This version of Mac Os is not supported on this platform" followed by MAC-AA95BIDDAB27BB95
I used Imac 19,1 system definition. It shows the i9 9900k being the processor. I'm running an i7 8086k which is a binned 8700k , would the system definition that I chose be incorrect? should I use the i7 8700 ~ Non K def instead?
IIRC, 19,1 is turn key for Designare z390 Catalina upgrade. I could be wrong of course.
Trying to go from Mojave 10.14.3 to Catalina 10.15.4 as per micro upgrade guide via post#1 then build my Catalina USB as shown in the Mini Catalina 10.15.4 guide
Which SMBIOS name are you using currently on Mojave 10.14.3? MacMini8,1 or iMac18,3 or ?? It may be necessary to keep the same SMBIOS name when upgrading to Catalina.
I've just now updated the Radeon Boost guide and included my GeekBench 4 and GeekBench 5 before/after chart, which is quite amazing. However, I found that using the SSDT prevented the system from switching on the AMD frame buffer at the end of the boot process so I've removed the SSDT. This is all quite new so please experiment and report findings.
Probably best to avoid the SSDT for now. Try first with only the RadeonBoost kext and disable WhateverGreen with the -wegoff argument.
Rolling back a kext is simply a matter of removing the bad one and copying a good one regardless of version.
The Radeon Boost procedure is completely optional. It might be better to fix Netflix first.
That would be helpful! When you say "brute" tests do you mean "Bruce X"?
Thanks Casey. I’ll fix Netflix, and then I'll install the Radeonboost kext and disable Whatevergreen. However, I’m guessing, if things appear to be broken then as this kext is not replacing anything, I can simply remove it and re-enable Whatevergreen? I.E., no need to hopefully restore from backup?
Sorry to hear that. After Step 1 in which flashrom said "VERIFIED", the chip was correctly programmed. In Step 2, the missing SSP1 and SSP2 ports were probably due to Thunderbolt SSDT. It would have been best to stop and report the problem here because we would troubleshoot that by examining the system log as follows:
Code:
log show --last boot | grep ACPI
We would also have looked at the complete IOReg file to determine if flashing itself was okay.
Suggestions:
Run IORegistryExplorer and capture a screenshot of RP05. I suspect there won't be much there, but let's have a look.
In the worse case it is possible to desolder and replace the Thunderbolt chip. But we should ask an experienced technician to do this. A local PC repair shop might have everything on-hand, including replacement W25Q80DVIS chips and the ability to flash them. They will just need the Thunderbolt firmware you captured from the chip.
Because you created 3 backup files of the firmware, please type the following in Terminal: strings Backup1.bin and post just the last 25 or so lines of the output.
P.S. That is probably the best example of problem-reporting I've seen so far. Exceptionally detailed and organized.
I'm very happy to say that I was able to re-flash my TB3 chip successfully with the patched firmware!
(For those reading this without earlier context, see my previous post here.)
Successful re-flash of the Winbond chip
Steps that led to a successful re-flash:
CMOS reset of the board before anything else.
Used the wiring of SOIC8-clip with breadboard/capacitor/resistor to GPIO.
ROM read with VCC disconnected and PSU off, giving succesful reads but random checksums. I decided to try flashing anyway, as the chip seemed already dead.
ROM write with VCC connected and PSU off would fail (No EEPROM/flash device found.).
ROM write with VCC disconnected and PSU off would fail (Uh oh. Erase/write failed! Flash chip is in unknown state).
ROM write with VCC disconnected and PSU off, and connecting VCC as soon as flashrom reports "Found Winbond Flashchip ...".
Looking back at my logs, I just noticed that I changed spispeed to 4096 for the succesfull write, where I used 1024 in all unsuccesful reads and write attempts before that.
This resulted in "Verifying flash ... VERIFIED". After re-flashing I left VCC connected and did 3 flashrom reads (again with spispeed=4096). Then verified checksums, and to my big surprise all checksums were identical, and matched the checksum of the patched firmware ROM file exactly. Whoohoo!
macOS boot issue fixed. Problems with Thunderbolt and USB in macOS still persist
I'm also happy to report that I'm writing this from my hackintosh again!
After reassembling my system, I managed to boot into macOS after using my USB Install Drive, and replaced the customized UID in "ThunderboltDROM" section of SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml with the default one.
With that being said, the issues regarding Thunderbolt and USB in my previous post still persist.
In short, it seems the Thunderbolt XHC is dead and SSP1 and SSP2 ports are gone.
In System Report > Thunderbolt, my Thunderbolt Bus and both Ports are listed instead of "No drivers loaded". However, several properties (UID, Firmware Version, ...) have a value of 0.
In Settings > Network, I see a new Thunderbolt Bridge interface.
IOReg shows a populated ThunderboltLocalNode (only Domain UUID property) and ThunderboltPort@7 (several properties) under RP05, but USB ports SSP1 and SSP2 and Thunderbolt XHC5 are missing.
In Hackintool > USB, the Thunderbolt XHC5 controller is no longer listed, and SSP1 and SSP2 are no longer present in the list of USB ports.
I connected my Apple Thunderbolt Display (using an Apple TB3-to-TB2 USB-C adapter), but the screen stayed off. None of the display's internal interfaces (USB-ports, FaceTime camera, Network Port, Firewire port, Display Audio) were visible in System Report nor IOReg.
I connected my MacBook Pro /w touchbar (late 2016) with TB-cable to each of Designare's two TB3 ports. Nothing happened on either system.
I connected a USB3 Thumbdrive to both TB3 ports on the backplate of the Designare, and it would not mount.
Some things I already tried to remedy:
CMOS reset
Reflashing Designare's UEFI BIOS with version F9b (and unlocking MSR 0xE2 Register again)
Verifying BIOS settings exactly as outlined in post #1
Clearing NVRAM
Copying SSDT's from Catalina 10.15.4 Fresh install over existing ones in EFI/CLOVER/ACPI/patched
Attached you find a zip-file with all the relevant information I could think of:
A collection of screenshots from System Information, IORegistryExplorer, and Hackintool.
A full IORegistryExplorer dump.
I also ran log show --last boot | grep ACPI like you suggested, and included the output.
Screenshots showing my EFI contents (SSDT's, UEFI drivers, kexts)
My config.plist with serial numbers removed.
Right now I'm still over the moon that my system has been revived. The Thunderbolt ports I can live without.
I'm hoping you can have a look after enjoying your weekend, and hopefully find something that's causing the issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
