CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 20,491
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
-
- Classic Mac
-
- Mobile Phone
-
Perfect thanks! Would my USB map get messed up by the migration to the newer OC and Monterey?
The USB SSDT has not changed in a long time. If, however, you're using a customized USB port map, just check whether it is still configured properly in config.plist after the update.Perfect thanks! Would my USB map get messed up by the migration to the newer OC and Monterey?
How do I check if it is properly configured?The USB SSDT has not changed in a long time. If, however, you're using a customized USB port map, just check whether it is still configured properly in config.plist after the update.
It is also strongly recommended to make a full bootable backup before upgrading to a newer version of macOS.
Key |
Type |
Value |
Comment |
String |
change Method(GPRW,2,N) to XPRW, pair with SSDT-GPRW.aml |
Disabled |
Bool |
False |
Find |
Data |
4750525702 |
Replace |
Data |
5850525702 |
@CaseySJ I keep getting this error as well, and now only one Thunderbolt port works.How do I check if it is properly configured?
If you go through the 0.7.7 Mini-Guide, this problem will not occur. Please give that guide a try (read all the warnings and notes) and see if the problem gets resolved.@CaseySJ I keep getting this error as well, and now only one Thunderbolt port works.
Correct.Hey @CaseySJ couple of quick questions: The BIOS experiment has been put on halt, until further notice (resp. @Elias64Fr is still experimenting), did I get that right?
It has not happened on any of my Intel-based Macs so I'm still puzzled why it happens to others. Haven't identified the cause.From what I understood enabling Apple VT-d yields a Blackscreen under Windows. Does that happen to everyone? Any workarounds in the works aside from disabling it?
Latest versions of macOS still need patches for iGPU to operate over HDMI port, but not for operating over Thunderbolt (DisplayPort). For output only through Thunderbolt (DisplayPort) we need to set Platform ID to 0x3E9B0007 without using any frame buffer patches.With the newer Operating Systems on the market are the framebuffer patches for UHD still necessary? Is the RadeonBoost still necessary?
It's always good to glance at the Quick Reference to Mini-Guides and Micro-Guides for any new entries to the table of contents. For instance, we're now on OpenCore 0.7.7 and there's a reference to the 0.7.7 mini-guide that contains important information.Anything else I've missed, while biding my time with my beloved X58?![]()
Cool. Any Updates any time soon? First I heard of it I got giddy as a child, but after the VT-d discovery I didn't hear anything since.Correct.
Ok, then I have to make my own discovery through trial and errorIt has not happened on any of my Intel-based Macs so I'm still puzzled why it happens to others. Haven't identified the cause.
Damn! I hoped I could get past as many property injections as possible. I'm still doing it the hard way over ACPI and (to be honest I haven't started debugging yet, but I'm 99.9% sure it's got to do something with property injection, had it already on my X58) Windows gives me BSOD with ACPI_BIOS_ERROR.Latest versions of macOS still need patches for iGPU to operate over HDMI port, but not for operating over Thunderbolt (DisplayPort). For output only through Thunderbolt (DisplayPort) we need to set Platform ID to 0x3E9B0007 without using any frame buffer patches.
RadeonBoost was not shown to provide meaningful acceleration in real-world apps, but only in synthetic benchmarks. Hence I stopped recommending it a long time ago.
It's always good to glance at the Quick Reference to Mini-Guides and Micro-Guides for any new entries to the table of contents. For instance, we're now on OpenCore 0.7.7 and there's a reference to the 0.7.7 mini-guide that contains important information.