Contribute
Register

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

Well that was weird...

I tired replacing just (a) OpenCore.efi and (b) BOOTx64.efi with the 0.8.5 versions, but all that got me was

BEP: Invalid revision 2 (!= 3) in loaded driver
Halting on critical error

So I went back to all 0.8.5 drivers, and stuffed in the release version of (a) and (b) above, so an 0.8.5 set of files like I had when it locked up, except now SecureBootModel is disabled, and CFG-Lock is diabled in the BIOS.

That got me to the screen where you pick your region, and I stayed there for quite some time! the keyboard was working (at least the arrow keys were), but now the mouse wasn't, and no amount of pressing Enter or using the Right arrow key would select the region. I could move up and down the list, but I couldn't select anything.

In the past when I've gotten this far the mouse always worked. Not sure what's wrong now, but it's a safe bet it's got something to do with USB.

Also, I apparently do not know what I'm doing with CMD + V. I've got a Windows keyboard, but I think the CMD equivalent is my Alt key (first key to the left of Space). Maybe it's the Windows key (between Ctrl and Alt). In any event I tried pressing a bunch of combos and never got a chance to pick a destination for the verbose logs - was I supposed to get something like that?
 
Updating to OC 0.8.5 caused my Windows 10 boot drive to brake. It's on a separate Sata SSD, macOS is on M.2. It shows up on the OC boot screen, but when I select it, screen goes black and computer immediately freezes. I can tell because holding down the power button makes it shut off within a second.

Picking the Windows drive from the F12 boot menu works fine though.

I haven't changed anything on the Windows EFI disk. Thanks for any help!
 
Last edited:
Got it booted! Just needed to move the mouse to another USB port. No doubt, I'll need to map my USB ports - that will be one of the next things I do along with sorting out why I don't have audio...

Is it safe to simply replace the /EFI folder on the root of my NVMe SSD (the one I just installed Monterey to) with a copy of the /EFI from my OC boot USB? I assume that's the procedure... Take the /EFI that works and got me booted from the USB and replace what's on the /EFI for the Monterey boot drive, right?

Here, hold my beer...
 
Updating to OC 0.8.5 caused my Windows 10 boot drive to brake. It's on a separate Sata SSD, macOS is on M.2. It shows up on the OC boot screen, but when I select it, screen goes black and computer immediately freezes. I can tell because holding down the power button makes it shut off within a second.

Picking the Windows drive from the F12 boot menu works fine though.

I haven't changed anything on the Windows EFI disk. Thanks for any help!
This happens on some Windows systems when we enable AppleVTD. If we disable AppleVTD, it's possible that some devices such as Ethernet ports may not work. Feel free to try without AppleVTD.
 
Got it booted! Just needed to move the mouse to another USB port. No doubt, I'll need to map my USB ports - that will be one of the next things I do along with sorting out why I don't have audio...
Yes this is a USB port map issue. We can use USBToolBox in Windows to map ports. Alas, that procedure is not particularly well documented. We also have a guide here on TonyMac:

Is it safe to simply replace the /EFI folder on the root of my NVMe SSD (the one I just installed Monterey to) with a copy of the /EFI from my OC boot USB? I assume that's the procedure... Take the /EFI that works and got me booted from the USB and replace what's on the /EFI for the Monterey boot drive, right?

Here, hold my beer...
Yes, just replace the EFI folder.
 
Yes this is a USB port map issue. We can use USBToolBox in Windows to map ports. Alas, that procedure is not particularly well documented. We also have a guide here on TonyMac:


Yes, just replace the EFI folder.
Yep, worked! On to the mapping of USBs...
 
@CaseySJ
I'm still having render / audio problems causing a total freeze of the system and even waiting 20+ minutes after log-in doing nothing (no screensaver, no mouse movement, no app involvement) causes this. However, I can work hours and days on web design and Photoshop and never have a freeze.

What I notice with the freeze by audio / video / or doing nothing right after log-in is:
  • My Radeon Vega Frontier's lights display fully (100% load even if no rendering)
  • Fans go 100%
  • System has to be restarted by power button
My research thus far has discovered:
  • People running AMD pro cards face this issue
  • People with multiple displays face this issue
  • People say the same thing about 100% fan and load
  • People are saying AppleGFXHDA.kext causes this problem via audio out the AMD card

I have a total of 3 displays hooked up and a pro AMD card. This may be my culprit!

My problem:
  • I don't know how to properly disable this AppleGFXHDA.kext. People are saying OC doesn't properly disable it either.
Any help is appreciated or sending me to someone you trust. At this point, the machine has been a work horse for 4 years and is almost perfect - except when doing what I love: video editing. It's so frustrating.
 
@mattbatt

I’m going to ask the obvious: ;)
  • Have you tested the multi-monitor hypothesis by disconnecting two of the three monitors, then using the system for an hour or two or three?
 
@CaseySJ, thanks for this amazing guide! I can't believe how well my system is working now. I even have Ethernet from the mobo - something I never had with this system before. Your efforts have saved me so much work, it's ridiculous.

I'm working on USB mapping now, and have found the tools and guide here (https://github.com/corpnewt/USBMap) to be helpful so far. The tool seems to be easy to use and the process, though a bit tedious, isn't hard.

I've run into one thing, though. That tool produced a couple of kexts (USBMap.kext and USBMapLegacy.kext). You're supposed to put the first one in your Kexts folder, then modify config.plist to load it. It starts out as just a dummy kext that this tool's process is supposed to fix.

With USBMap.kext in my Kexts folder, I used propertree to rebuild my config.plist using the Cmd+R command and pointing it at my /EFI/OC folder. Of course, first I saved a copy of the working config.plist in the same folder, and that turned out to be the smartest thing I did since when I booted it hung at the Apple logo without a progress bar.

I was able to reboot and use the shell to move the old config.plist back, I'm not entirely sure what went wrong. One thing propertree did whine about when I did the Cmd+R was that it wanted to disable two kexts with duplicate CFBundleIdentifiers: Airportltlwm-Ventura and USBInjectAll-076. I told it not to, since if there were there before and it was working I didn't want to change that.

Should I have taken propertree up on its offer?

Should I have used OCC instead, and maybe it would have done something differently?

EDIT: So... I tried the first option, taking propertree up on its offer to disable Airportltlwm-Ventura and USBInjectAll-076. That worked, sort of... The system booted, but now I've only got one monitor. Hmmmm, fonts are wacky, too =\

EDIT2: Yep, OCC got it working! Turns out that wasn't so hard to do, just scan the Kexts folder and voila! the USBMap.kext is in the list and enabled. I do get warnigns about using OC 0.8.3 with OCC 2.63, but it seems to be working!

On to mapping USB ports!
 
Last edited:
Back
Top