- Joined
- Sep 10, 2012
- Messages
- 113
- Motherboard
- Gigabyte Z390 Designare
- CPU
- i9-9900KS
- Graphics
- RX Vega 64
Where can you find these logs?Yes exactly! I saw this over 20 times this morning during Thunderbolt testing.
Where can you find these logs?Yes exactly! I saw this over 20 times this morning during Thunderbolt testing.
These are messages that come on screen right after a hard boot and are cleared after the next successful boot.Where can you find these logs?
@CaseySJ ,@Elias64Fr,
I'll create a summary and test plan here before continuing with testing this evening (about 9 hours from now).
ThunderboltConfig
Fixing SSP1 and SSP2 with Companion Port
- Based on this post, I tested with:
- ThunderboltConfig =
- 00021c00 02000503 01000400 05030200 03000503 01000000 03030200 01000200.
- Let's call this one TCONFIG-2
- Did not seem to make any progress with this string, but I haven't given up on it yet.
- Nearly all of the good or hopeful results posted previously are with...
- ThunderboltConfig =
- 0002FFFF 04000301 01000400 05010200 03000301 01000000 03010200 02000100.
- Let's call this one TCONFIG-1
Booting with USB 3.1 Gen 1 Flash Drive
- Modifications Made:
- This fixes SSP1 and SSP2 to USB Type C (0x09).
- Adds XHC companion ports 0x08 (HS08) and 0x0D (HS13).
- Adds USB Power Properties.
- Defines FS, LS, HS devices (USB Full Speed, USB Low Speed, USB High Speed) -- these are USB 1.x and 2.x.
- All of the results from this morning are with these changes.
- TNODE/TBUS appeared two times this morning, but each time the system hanged about 10 seconds after login was complete.
- This was with TCONFIG-1.
- This means, after I enter Catalina login password, then 10 seconds later system hangs.
- But the fact that TNODE/TBUS even appeared with these settings is a good sign.
Booting with Apple TB-to-GbE Adapter (w/Apple TB3-to-TB2 adapter)
- During this test, GPE _E17 was in use. This means any attempt to hot-plug or hot-unplug causes immediate GUI hang.
- So this test was done with USB drive already connected before boot.
- When system booted up, the USB disk mounted automatically after a few seconds.
- USB flash disk was 100% usable. Good sign!
Empty GPE E_17 Method
- On 2 out of 20-30 boot attempts this morning, the Apple TB-to-GbE device tree under RP05 was fully materialized.
- Shows randomness / inconsistent device state from boot to boot.
- System Information --> PCI showed that drivers were loaded.
- But the Ethernet port did not respond when Ethernet cable was plugged in.
- So partial progress!
Obtaining XHC2 Power State Properties with No Device Connected
- Because hot-plug and hot-unplug were causing immediate GUI hangs, we decided to empty the method by simply removing the following instructions from the method:
- Removed call to UPSB.AMPE() -- this normally invokes a Notify on NHI0
- Removed call to UPSB.UMPE() -- this normally invokes a Notify on XHC2 and XHC
- But Gigabyte's default handler (XE17) was not called. Maybe we should call it?? Will try this in the evening.
- With this change, the system no longer hangs with either hot-plug or hot-unplug, but Thunderbolt devices do not actually hot-plug or hot-unplug. Their state remains the same as it was at boot.
- As mentioned, I will invoke the default XE17 handler and see what happens.
_INI / PINI Methods
- Because SSP1/SSP2 devices do not always appear in IOReg, it takes several reboots/hot-unplugs/cold-starts to make them appear (almost sounds like a timing / randomness issue??).
- Next time SSP1/SSP2 appear, I will capture their Power State Properties with no devices connected.
- But with USB 3.1 Gen 1 Flash drive connected:
- kPowerStateOff was 0ms (0%)
- kPowerStateSleep was 0ms (0%)
- kPowerStateOn was 2xx or 3xx ms
- kPowerStateSuspended was some large number (in ms)
- Comparing the _INI/PINI methods between our SSDT, Apple's original iMac19,1 SSDT, and Osy86's compiled version, we see that Apple and Osy86 are initializing the device only if !OSDW() (OS not equal to Darwin), but we are initializing the device unconditionally.
- Will see what happens if this section is commented-out.
View attachment 447145
Comments on Current Status
- Because TNODE/TBUS have never appeared when no device is connected, what does this imply?
- Because TNODE/TBUS appear inconsistently, almost randomly, during warm boots, what does this imply? Timing issue? Random events? Some device state that we're not setting properly?
- The Apple TB-to-GbE device (with Apple TB3-to-TB2 adapter) got fully materialized two times this morning, and System Information --> PCI indicated that driver was loaded. But the device could not actually connect to Ethernet cable.
- This "full materialization" also happened randomly, 2 times out of 20-30 boot attempts this morning. So it is not consistent/reliable.
- Also need to determine why XHC2.PCED is never called. We have no ACPIDebug logs of this. We do not see the following logs:
View attachment 447147
[This post will continue to update during the day as the test plan evolves.]
Here is my config and EFI folder. Everything looks in order. All files were the latest from the Catalina mini guide for the 5700 XT.@pitt1717
This is the oldest and most frequently discussed boot problem in this thread!
- Check your drivers/UEFI folder in Clover.
- Ensure that there is only 1 memory fix driver:
- OcQuirks.efi + FwRuntimeServices.efi together constitute one driver. This is the preferred driver.
- OsxAptioFix2Drv-free2000.efi is the alternative driver.
- Remove any other memory driver such as:
- AptioMemoryFix.efi
- OsxAptioFix3Drv.efi
- OsxAptioFix2Drv.efi
- Also ensure that config.plist --> Boot Arguments contains slide=0.
Clover version is 5103. BIOS is F8.What version of Clover are you running?
The must both be enabled.Or both must be enabled?
If you’re still getting the allocation error, please try a CMOS Reset first (shorting 2 pins on motherboard). This will retrain the memory map.Here is my config and EFI folder. Everything looks in order. All files were the latest from the Catalina mini guide for the 5700 XT.
View attachment 447221
View attachment 447222
No good. Same thing. Maybe I missed something else, or maybe it just didn't like the BIOS change for whatever reason. I'm going to try another clean install and see what happens.If you’re still getting the allocation error, please try a CMOS Reset first (shorting 2 pins on motherboard). This will retrain the memory map.
If this fails, you may have to switch to OsxAptioFix2Drv-free2000
After doing the CMOS Reset, all BIOS parameters revert back to factory defaults. I forgot to mention that BIOS must be reconfigured starting with "Load Optimized Default". Are BIOS parameters still at their factory default settings?No good. Same thing. Maybe I missed something else, or maybe it just didn't like the BIOS change for whatever reason. I'm going to try another clean install and see what happens.
Are you seeing the same error as before, namely Couldn't allocate runtime area? Please enable Verbose mode as before.So I did another install. I booted up with just the fresh Catalina folder and 5700 config, and it works. I followed the NVRAM guide, reboot and stop sign again. I'm not sure what is going on. But looking at the config, is this correct
shiki-id=Mac-7BA5B2D9E42DDD94? I don't recall that setting before.
You're okay there as well. OcQuirks-4 is an older version, but it's still okay to use. The newer version consists of (a) OcQuirks.efi, (b) OcQuirks.plist, and (c) FwRuntimeServices.efi. Again, the version you have is okay.also you said to have OcQuirks.efi and FwRuntimeServices.efi. but I have OcQuirks-4.efi, do I need to rename it and remove the -4?