Contribute
Register

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

Updates.

So I’ve been in a situation recently where a wired connection just isn’t possible at all. So, I’ve been forced to mess around to make this MQUPIN Fenvi T919 wifi/bt card work. Getting any other cards seems to be impossible in Canada right now.

In addition to plugging in the BT header to the F_USB on the motherboard, I ended up having to do the following combination of things to get it working fully and reliably.

1) I put the card in the 2nd PCIE long slot (between the 2 nvme slots) in order to get the Bluetooth working in bios and boot and after boot. No other slots would do this for me.

2) To get my wifi working without stalling and becoming unusable after booting, I added the latest AirportBrcmFixup kext and then removed the plugin, AirPortBrcm4360_Injector.kext inside the package (you can disable it instead) and added the country code and used brcmfx-driver=2 in my boot arguments (not sure if these were needed or not but I added them anyway).

To be safe, I also cleared NVRAM after moving the card and adding the modified kext and boot arguments for opencore.

Handoff, Airdrop, Sidecar, wifi and bt all work fine now for me.
More updates. Mind boggling stuff. After a week of things working perfectly, this wifi/bt combo card has gone back to the wifi connection just hanging after being booted for a while, and now the bt is randomly disconnecting. Still works in bios/boot at least! Haha.

Just when I think progress is made it just reverts to being flakey again. Very frustrating. The pleasures of hackintosh. Not sure this issue will ever be sorted out unfortunately.
 
More updates. Mind boggling stuff. After a week of things working perfectly, this wifi/bt combo card has gone back to the wifi connection just hanging after being booted for a while, and now the bt is randomly disconnecting. Still works in bios/boot at least! Haha.

Just when I think progress is made it just reverts to being flakey again. Very frustrating. The pleasures of hackintosh. Not sure this issue will ever be sorted out unfortunately.
There's a way to fix the onboard Intel Ethernet and Bluetooth on this build's forum. I had an issue with an inability to turn off the Fenvi's Bluetooth with Monterey, but I don't recall exactly how I fixed it. There's a lot to all of this, but also a lot of success in 3443 pages. So far in Monterey, En0 (Intel) works, but not En1 (SmallTree) –IDK if it will get fixed.
 
It was surpringly hard to upgrade to Big Sur because of the extra safety measures that blocked some of my kexts(UAD especially).
A developer mentioned that there are bugs in Big Sur that make this a miss and hit affair. These will probably never be fixed in a Big Sur update.
I solved this issue by using the "Reset-UAD-Access-Control" command. Run it, then get ready to click all the stuff in System Preferences<Security to re-allow all of that UAD stuff to run before the mandatory restart.
 

Attachments

  • Reset-UAD-Access-Control.zip
    5.8 KB · Views: 30
I looked at your USB port map (USBMap.kext), but it does not seem correct. All USB ports are set to Type 3 (USB 3.x) whereas Z390 Aorus Pro has:
  • 4 USB 2.0 ports on rear (Type 0)
  • 5 USB 3.0 ports on rear (Type 3)
  • 1 USB-C port on rear (Type 9)
  • 2 USB 2.0 headers on motherboard (Type 255)
  • 1 USB 3.1 front panel header (Type 3)
I found a USBPort map from this build guide, that I'm attaching here.

Instructions:
  • Download both files (config.plist attached here does not have serial numbers)
  • Mount EFI partition containing OpenCore
First, copy the entire working EFI folder to the EFI partition of a USB flash disk -- this will be your emergency boot disk. Then eject the USB flash disk.
  • Copy USBPorts.kext to EFI/OC/Kexts folder
  • Rename the existing config.plist to something like config-backup.plist
  • Before proceeding to next step, ensure that only one EFI partition is mounted
  • Open both the old and new config.plist files in OpenCore Configurator and click to the PlatformInfo --> DataHub section in each of the two windows
  • Copy and paste these values to the new config.plist:
    • System Serial Number
    • Hardware UUID
    • MLB
View attachment 535934
  • Save the file.
  • Reboot and log back in.
  • Check Bluetooth.
  • If it still does not work, download and run Hackintool.zip from here.
  • Select the USB tab at the top of Hackintool.
  • Resize the window so that all ports are visible.
  • Capture screenshot with CMD-Shift-5 and post.
Hopefully it's a simple issue...
Hi! Contribution done for your help ;-)

So this morning I did all what you said, but Bluethooth still doesn't work, and had some trouble using USB ports at the back after rebooting (see attached).

So I opened Hackintool, seems like almost all USB connectors are still recognised as USB 3...:roll2:
Any idea what's wrong with the new USBPorts.kext you send me ?

Again, thanks a lot!
Frank
 

Attachments

  • Hackintool capture.png
    Hackintool capture.png
    267 KB · Views: 37
  • USBMap.kext issue.png
    USBMap.kext issue.png
    529.5 KB · Views: 37
  • USBPorts.kext in Kexts folder.png
    USBPorts.kext in Kexts folder.png
    470.3 KB · Views: 33
I solved this issue by using the "Reset-UAD-Access-Control" command. Run it, then get ready to click all the stuff in System Preferences<Security to re-allow all of that UAD stuff to run before the mandatory restart.
Didn't work for me. I had to wipe everything UAD/disable SIP via the recovery partition/install with SIP off/test/reboot in recovery/switch SIP on again. This worked for several kexts, BTW.
 
How to change OpenCore Picker volume name?

My Aorus Pro Monterey install became unstable. (I had performed an in-place upgrade from Big Sur.) So I decided to do a clean install. I did a clean install of Monterey on a spare HD, then used Carbon Copy Cloner to clone the "old" Monterey data volume to the backup HD. I then used the CCC legacy restore procedure, which assigned the destination disk the same name as the source (backup) disk. I gave the destination disk a new name using Disk Utility, but the CCC-assigned name shows up on the OC picker. I think there is a procedure here somewhere to change it but my searching didn't turn it up.
Thanks,
Ken
 
Hi! Contribution done for your help ;-)

So this morning I did all what you said, but Bluethooth still doesn't work, and had some trouble using USB ports at the back after rebooting (see attached).

So I opened Hackintool, seems like almost all USB connectors are still recognised as USB 3...:roll2:
Any idea what's wrong with the new USBPorts.kext you send me ?

Again, thanks a lot!
Frank
Some comments and suggestions:
  • Only one USB port map is allowed. System will not boot with two USB port maps!
  • In Hackintool we can click the "clear" button followed by "refresh" button in order to see the updated USB map:
Screen Shot 2021-12-01 at 8.38.11 AM.png

  • It's actually better to download IORegistryExplorer from here.
Please note that the new USB port map defines exactly 15 ports, which is the technical maximum without a kernel patch. A side-effect of limiting the number of ports is that USB 2.0 devices will not work on some USB 3.0 (blue or red) ports. It's best to attach USB 2.0 devices to black USB ports, which are USB 2.0.


Instructions:
  • Download IORegistryExplorer from link above.
  • Mount EFI partition and make the changes shown below to OpenCore's config.plist:
Screen Shot 2021-12-01 at 9.15.33 AM.png

  • Reboot and log back in. Now all USB ports should be enabled.
  • Run IORegistryExplorer and select File --> Save As... and save the IOReg file; then post that file.
This will give us a clear look at all USB ports and help us determine where Bluetooth is located.
 
Last edited:
How to change OpenCore Picker volume name?

My Aorus Pro Monterey install became unstable. (I had performed an in-place upgrade from Big Sur.) So I decided to do a clean install. I did a clean install of Monterey on a spare HD, then used Carbon Copy Cloner to clone the "old" Monterey data volume to the backup HD. I then used the CCC legacy restore procedure, which assigned the destination disk the same name as the source (backup) disk. I gave the destination disk a new name using Disk Utility, but the CCC-assigned name shows up on the OC picker. I think there is a procedure here somewhere to change it but my searching didn't turn it up.
Thanks,
Ken
Please see the post below, which applies to both Big Sur and Monterey:
 
Back
Top