- Joined
- Dec 15, 2010
- Messages
- 681
- Motherboard
- Asus ProArt Z690 Creator WiF
- CPU
- i9-12900K
- Graphics
- RX 6900 XT
- Mac
Can I use existing DROM, or does it need to be altered?It's worth trying. I've added the patched NVM 50 to that post...
Can I use existing DROM, or does it need to be altered?It's worth trying. I've added the patched NVM 50 to that post...
We can use any USB-C to DisplayPort cable that is rated for 4K60 such as this one. It connects directly from the rear IO panel (use any of the two TB3 ports) to the monitor. To the the HDMI port, simply follow this guide from Post #1:Great, so i have options at least.
For monitors, i have a single Asus 27" 1440p 144hz Gaming screen with both Displayport and HDMI inputs (switchable), and a 4k TV with HDMI 2.1.
When you say "USB-C to DisplayPort cable", would that be the USB-C connection from the internal Thunderbolt 3 port, ran out to displayport of monitor? You'll have to excuse my lack of knowledge on Thunderbolt connections. And otherwise a regular HDMI > HDMI from iGPU to monitor/tv? (but with some extra work patching?)
To disable or hide the Nvidia GPU in Slot 1, just copy this SSDT to CLOVER/ACPI/patched (located at the end of Post #1):Finally, is information regarding how to disable the 2080 via SSDT/Frame Buffer Patching posted in the first page of this thread, or should i be looking elsewhere for info on this? Again, sorry if i sound silly, this is my first Hackintosh since about 2008 or so when i first attempted it!
No need to alter the DROM for GC-Titan Ridge.Can I use existing DROM, or does it need to be altered?
is your GC-AR unflashed?@faithie999 Totally understand you!
Since last summer I'm using attached SSDT-Z390-TB3HP.aml (kindly made by @CaseySJ for all of us, link should be also available in post #1 of this thread). No problems at all with my Apple Thunderbolt Display. Very consistent and stable experience.
The only benefit of activating Thunderbolt Local Node and Thunderbolt Bus (with all those steps you mentioned) I recently noticed was finally being able to control brightness via F1/F2 keys without display glitching or blinking. Seems like macOS uses this Local Node / TB Bus structure to obtain / send additional control information to Apple Thunderbolt Display.
In all other aspects, Apple Thunderbolt Display working really good with GC-Alpine Ridge and SSDT-Z390-TB3HP.aml without any special modifications.
I get kernel panics and cant boot if I boot from the Catalina drive (Samsung SSD 970 EVO 2TB) . But if I boot from USB then have clover boot from Catalina it is smooth as silk. When I mount the Catalina EFI it says EFI on APFS Container (Catalina - Data, Preboot, Recovery, VM, Catalina). Am I missing something here?
- We'll make this really simple.
- Run Clover Configurator which was copied to the USB flash disk in Step 1.
- Click Mount EFI on left sidebar of Clover Configurator
- Mount EFI partitions of (a) USB flash disk and (b) Catalina SSD.
- Copy the entire EFI Folder from EFI partition of USB disk to EFI partition of Catalina SSD.
Although they should be the same, I'm using EFI Agent instead of Clover Configurator to mount EFI. If an EFI folder exists there, it should be deleted first and trash should be emptied before copying the entire EFI folder from USB.Well. I thought I was there lol.
I get kernel panics and cant boot if I boot from the Catalina drive (Samsung SSD 970 EVO 2TB) . But if I boot from USB then have clover boot from Catalina it is smooth as silk. When I mount the Catalina EFI it says EFI on APFS Container (Catalina - Data, Preboot, Recovery, VM, Catalina). Am I missing something here?
THanks!
Jules