Contribute
Register

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

Quick question around the Wi/Fi-BT adapter, can I still use Ethernet instead of Wi-Fi, but still use the BT functionality of the card?

Don't see, why not.

Furthermore, will the Bluetooth work in Windows as far as you're aware?

Depends on the card you're using. 94331CD to 94360CD is alright. My 943602CDPs BT doesn't work (driver conflict, Windows claims that the Apple drivers are not signed and thus doesn't 'trust' them), unless you start with driver signature check disabled, or put the machine in permanent dev mode. Didn't try the first version of 943602CDP, though (first versions had BT 4.1, mine has BT 4.2, can be identified through P/N on the card).
 
Thanks Casey. I've added the 300-series RTC patch fix and will report back. I'll also expedite the PCI-e internal wifi/bluetooth card so I can stop using the USB bluetooth adapter.

Quick question around the Wi/Fi-BT adapter, can I still use Ethernet instead of Wi-Fi, but still use the BT functionality of the card? Furthermore, will the Bluetooth work in Windows as far as you're aware?

You can still use the Ethernet, and wifi at the same time if you want. The current wifi/bluetooth card already installed works fine in Windows so when you add the Fendi don't install any Windows drivers for it.
 
None at all. Directly edited the DSDT.aml provided by the system and put it into ACPI/patched (without KP this time, the reason, why I believe it is a bootloader thing, that it didn't work, back then, on our first attempts). Nonetheless, I reuploaded my EFI folder, you can put it use however you see fit :)

Did try, but it didn't work. In my DSDT.aml there is an If-clause that creates/initialises the device GLAN, so the SSDT won't get used/parsed, because during the time clover tries to put it to use, the device doesn't 'exist'.

It may being set to GLAN by IntelMausi (or IntelMausiEthernet). Maybe not: I looked inside with HexFiend and I see no references to GLAN.
 
It may being set to GLAN by IntelMausi (or IntelMausiEthernet).

Tried without the kext, as well. The kext hooks up at any supported Intel Ethernet adapter, no matter the device name. I'm 100% positive, that it's absolutely required to eliminate/circumvent the If() clause provided by the DSDT (which I already did and got working results). Now the question that remains is, whether it can be done using just an SSDT, without manipulating the system DSDT.aml
 
It's always advisable to focus on one main issue at a time. So for now let's forget about Windows and focus on getting macOS bootable and stable.
  • Which version of macOS are you running?
  • Does the Clover Boot Menu appear and does it contain an option to boot macOS?
  • Does macOS boot up?
It's also a good idea to:
  • Check the coin battery on the motherboard. Replace that battery just to be extra safe.
  • Perform a CMOS Reset and configure BIOS parameters starting with Load Optimized Defaults.
  • If you had unlocked MSR 0xE2, check it again via the Grub shell. If you did not unlock MSR 0xE2, skip this step.
Then try the suggestions in my previous post.
I'm running Mojave 10.14.5
The Boot menu does appear and it contains the usual option to boot macOS
The OS won't boot that is where it crash...
Theres a way to remove the WhateverGreen.kext without getting into the system?
I went out to buy a new battery (The only difference is that the system is keeping the time right)... Did the CMOS reset and loaded the Load Optimized Defaults.
Never changed this MSR 0xE2.
Sorry about the misinformation... I'm not an expert on this, but I'm trying to follow the steps the best I can!
Would be a bad idea to update the motherboard firmware? I'm running the F6.
 
Theres a way to remove the WhateverGreen.kext without getting into the system?

Several, actually. Most popular and easiest would be a an ubuntu stick (did it myself couple times, when I made system-screwing-edits).
 
Hi!
CaseySJ!!! What a work you have done here!
I am trying to build my 2nd Hackintosh, but did not practice for a while...
I Have the same Motherboard.
I am starting the process to install Mojave on Z390 Designware...
BUT, with latest Clover the Kernel and Kext patches section in the Config.plist is different (the "External icons Patch does not appear on mine), and the EFI created with Unibeast (9.3.0) does not show drivers64 or Drivers64UEFI...only "Drivers" and a subfolder named UEFI (and not UEFI64).
Should I make the changes to that folder?
why the Drivers64 and Drivers64UEFI do not show?
Sorry
Hello @RuiNeves,

We can manually enter the External Icons Patch as follows:
  • Name: AppleAHCIPort
  • Find* [HEX]: 45787465 726E616C
  • Replace* [HEX]: 496E7465 726E616C
  • Comment: External Icons Patch
The current version of UniBeast installs Clover 5107, which puts all EFI drivers in CLOVER/drivers/UEFI folder. So wherever you see:
  • drivers64UEFI
... you may replace that with:
  • drivers/UEFI
Good luck with the rest of the install.
 
Thanks Casey. I've added the 300-series RTC patch fix and will report back. I'll also expedite the PCI-e internal wifi/bluetooth card so I can stop using the USB bluetooth adapter.

Quick question around the Wi/Fi-BT adapter, can I still use Ethernet instead of Wi-Fi, but still use the BT functionality of the card? Furthermore, will the Bluetooth work in Windows as far as you're aware?
Yes you may disable WiFi from the Fenvi quite easily and still use Bluetooth. Windows may need to download special drivers for this card, so I recommend not doing that. Let the Fenvi card be an "unknown" device in Windows. This allows Windows to use the much better Intel CNVi module that comes preinstalled on the motherboard. But be sure to connect the outboard antenna (that comes in the Designare box) to the two antenna ports on the rear IO panel.
 
Tried without the kext, as well. The kext hooks up at any supported Intel Ethernet adapter, no matter the device name. I'm 100% positive, that it's absolutely required to eliminate/circumvent the If() clause provided by the DSDT (which I already did and got working results). Now the question that remains is, whether it can be done using just an SSDT, without manipulating the system DSDT.aml
Why don't you try the FIND/REPLACE options in my earlier post? No DSDT or SSDT changes needed. This removes the IF clause. Then use Clover --> Devices --> Properties to inject System Information properties. This keeps everything confined to the config.plist. (Assuming the FIND/REPLACE works.)
 
I'm running Mojave 10.14.5
The Boot menu does appear and it contains the usual option to boot macOS
The OS won't boot that is where it crash...
Theres a way to remove the WhateverGreen.kext without getting into the system?
I went out to buy a new battery (The only difference is that the system is keeping the time right)... Did the CMOS reset and loaded the Load Optimized Defaults.
Never changed this MSR 0xE2.
Sorry about the misinformation... I'm not an expert on this, but I'm trying to follow the steps the best I can!
Would be a bad idea to update the motherboard firmware? I'm running the F6.
  • Firmware F6 is perfectly okay. You may upgrade to F7 or F8 or even F9b if you like. It will be necessary to reconfigure BIOS parameters afterwards.
  • How long ago was Mojave installed? Recently? Weeks ago? Months ago?
  • Was it running properly for some time and then suddenly the crashes started?
  • Do you have a full bootable backup of Mojave? We usually do this right after installing macOS. It gives us a known working baseline that we can go back to.
  • Do the crashes occur:
    • When running a web browser?
    • When running one of your applications?
    • When running one of the built-in Apple applications?
    • When copying large files?
    • Completely randomly?
    • Other?
 
Back
Top