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

[WhosMac]

At the top of the 10.15.4 mini-guide I've posted a link to a MacRumors article that describes a system crash problem that many real Mac owners are experiencing. It might be a good idea to wait for a 10.15.4 hot fix.

Must have missed the addition when I read it thru the first time, appreciate the heads up @CaseySJ guess that means ill be holding off until a fix is generated or 10.15.5 is released.

 

[Tea-Bone]

I installed the new Lilu/WhateverGreen/AppleALC/VirtualSMC that were released yesterday. I was unable to fully boot until I reverted the VirtualSMC to the previous version.

The message in verbose was busy timeout for AppleACPICPU

Any clue as to what I need to do to keep up with VirtualSMC?

Running 10.14.6

Thankfully it had booted far enough to SSH in, but black screen locally.

Thanks!

 

[CaseySJ]

"Have you already tried bringing the mice close to the antenna/USB-transceiver?":
My hackintosh is about 60cm away from my mouse, so it's right next to me

I just disabled and restarted "IOAPIC 24-119 Entries" in the BIOS, then immediately enabled it again in the BIOS. After that I restarted again and started up with macOS. The problem occurs only very rarely now.

I don't know if it was useful or not, but it definitely did something.

I have one more question: does a "new installation" do anything if I don't format the SSD, but just install it over it, or is it a duty to format the SSD before?

If we apply Piker Alpha's patch, we may not need to modify the BIOS setting. I have not tested this so buyer beware!

<key>KextsToPatch</key>        
<array>
            <dict>
                <key>Comment</key>
                <string>Skylake AppleAPIC Patch (c) Pike R. Alpha</string>
                <key>Find</key>
                <data>
                wegQD7bw
                </data>
                <key>Name</key>
                <string>AppleAPIC</string>
                <key>Replace</key>
                <data>
                vhcAAACQ
                </data>
</dict>
</array>

 

[CaseySJ]

That’s what I did.

Apparently, the OS will also adjust depending on this setting. It affects how the PCH lanes are managed, and also supposedly the timings and latencies of the graphics and other PCI-E devices. I’m no expert on that though.

The RW/O registers (Read/Write Once) are those that can be read any time, but written (modified) only once after each reboot. As soon as firmware (BIOS) writes to that register, it cannot be written-to again until the next reboot. So if you change IOAPIC 24-119 to Disabled, then changing it back to Enabled will undo the modification after each reboot.

MSR 0xE2 (CFG-LOCK) behaves the same way. It's also a write-once register, which is why BIOS has to either write a "1" or a "0" to it every time the system boots (i.e. the setting does not persist between reboots).

 

[bugsyraz]

The IORegistryExplorer screenshot does not look correct. Under RP05 you should see the following (in the absence of any connected Thunderbolt device):

View attachment 460305

Suggestions:

1. Do not use the "search" field in IORegistryExplorer. Just scroll the device tree on left side until you see RP05. Do you still see a reduced list of devices compared with screenshot above?
2. Confirm that CLOVER/ACPI/patched no longer contains the file: SSDT-Z390-DESIGNARE-TB3HP-V4.aml
3. Re-read the Winbond chip with Raspberry Pi three times, compute checksums three times, and see if they match the checksum of DESIGNARE-Z390-NVM33-Elias64Fr.bin (shown below)

% shasum DESIGNARE-Z390-NVM33-Elias64Fr.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  DESIGNARE-Z390-NVM33-Elias64Fr.bin

Hi Casey,

I've managed to reflash the chip after a bunch of tries.

Initially reflashed it back to the backed up original firmware. Then went ahead to check functionality in Windows and it won't see the ports at all. Curiously enough, USB-C devices worked while with Elias's firmware, USB-C wasn't working.
Thunderbolt didn't work though. I can see it in Device Manager but ports are not seen.

Went back and reflashed it to NVM33, checksum was good.

Booted back to OSX and Thunderbolt BUS shows the same thing.

Also worth mentioning, USB-C doesn't work on OSX either, with NVM33 installed.

Here's a picture of IOREG.

 

[CaseySJ]

Hi Casey,

I've managed to reflash the chip after a bunch of tries.

Initially reflashed it back to the backed up original firmware. Then went ahead to check functionality in Windows and it won't see the ports at all. Curiously enough, USB-C devices worked while with Elias's firmware, USB-C wasn't working.
Thunderbolt didn't work though. I can see it in Device Manager but ports are not seen.

Went back and reflashed it to NVM33, checksum was good.

Booted back to OSX and Thunderbolt BUS shows the same thing.

Also worth mentioning, USB-C doesn't work on OSX either, with NVM33 installed.

Here's a picture of IOREG.View attachment 460366

Please post the following:

• IORegistryExplorer --> File --> Save As... (post this file)
• Compressed CLOVER folder (but remove serial numbers from config.plist)

 

[bugsyraz]

Please post the following:

• IORegistryExplorer --> File --> Save As... (post this file)
• Compressed CLOVER folder (but remove serial numbers from config.plist)

Here you go, Casey!

Thanks!

 

[CaseySJ]

Here you go, Casey!

Thanks!

That folder must be deleted.

 

[bugsyraz]

That folder must be deleted.

View attachment 460373

Sure, tis done.

 

[CaseySJ]

Sure, tis done.

Is the Thunderbolt tree still truncated in IORegistryExplorer? Please try a cold boot:

• MacOS --> Shutdown
• Then flip power switch on PSU to OFF for 10 seconds
• Restart