[SUCCESS] Ongoing Status of Designare Z390 with i7-9700K

[corint1]

Quick update on the substitute WiFi/BT card by Fosa (BCM94352Z NGFF M.2 Socket-1):

• Unfortunately this card may not be compatible with this motherboard. It does not appear anywhere in IORegistryExplorer or DPCI Manager.
• I wonder if my copy of the card is defective or if this card is just too specific to the Lenovo PC...
• I installed the following kexts by @RehabMan by following the instructions and downloading the files from here.
  • BrcmFirmwareData.kext (CLOVER/kexts/other)
  • BrcmPatchRAM2.kext (CLOVER/kexts/other)
  • BroadcomWiFiInjector.kext (CLOVER/kexts/other)
  • FakePCIID.kext (CLOVER/kexts/other)
• These kexts don't trigger -- again because the DeviceID/VendorID don't seem to be appearing anywhere.

So I'll return this item and just settle on the PCIe x1 card using the more recent BCM94360CS2. (Yes this is just the PCIe adapter; I'll order the WiFi/BT card at the same time.)

Edit: This post by @jaymonkey confirms my suspicions: the CNVi slot on this motherboard is incompatible with standard M.2. CNVi has a slightly different pin layout, which means only CNVi cards will work. Hence, switching to a PCIe x1 card was the right move.

have you BT Apple keyboard and/or trackpad working in bios ?

 

[CaseySJ]

have you BT Apple keyboard and/or trackpad working in bios ?

The CNVi slot on this motherboard is not the same as an NGFF M.2 slot, so I had to return the BCM94352Z. Today I received and installed the BCM94360CS2 on a PCIe x1 slot. Once I disabled USB port HS14 (for the CNVi Bluetooth) and enabled HS11 (for the motherboard USB 2.0 header where the PCIe card is connected), I was able to get both WiFi and Bluetooth working with just Lilu and AirportBrcmFixup.kext.

I connected to my WiFi network at home and also paired my Apple Bluetooth Keyboard.

However, as soon as I rebooted, I immediately ran into the "Couldn't allocate runtime area" error, which aborts the boot process. Because of a full working backup on an external SSD, I booted off the backup, used Carbon Copy Cloner to restore the Mojave disk from the backup, and was able to boot up again.

This problem only occurs when the HS11 USB port for Bluetooth is enabled. With only WiFi enabled, multiple reboots work fine. So I'm currently trying to troubleshoot this problem.

 

[LukeR22]

FYI the T9 Archer worked perfectly for Wi-Fi and Bluetooth. No Broadcom fix kext needed. Worked perfectly for Airdrop, Handoff, Instant Hotspot

 

[LukeR22]

I suspect I'll spend another couple of hours looking into the 630 HD again tonight. I'm at a bit of a loss though. I'm in the same position with headless. I'm using it with an iPad and Parallels Access which appears to be the fastest app of them all.

I can easily work from the iPad now!

Where did you see about there being an upcoming update for WhateverGreen? I couldn't find the hex code you mentioned in any of the source code.

I wonder what would be the cheapest AMD card that would solve the issue.

 

[LukeR22]

Also, FYI.

Intel PTT had to be enabled for me to be able to boot. Unsure why yours needed to be disabled.

 

[LukeR22]

No luck with the 630 tonight :/

 

[CaseySJ]

However, as soon as I rebooted, I immediately ran into the "Couldn't allocate runtime area" error, which aborts the boot process. Because of a full working backup on an external SSD, I booted off the backup, used Carbon Copy Cloner to restore the Mojave disk from the backup, and was able to boot up again.

Problem Fixed!!

Looking through my /Library/Extensions folder, I removed two kexts that were not needed:

• SIPManager.kext (probably got migrated from my MacPro3,1 when I ran Migration Assistant).
• LegacyUSBInjector.kext

Because standard boot was failing, I booted to the Recovery Partition, deleted the above kexts and typed:

cd /
kextcache -i /Volumes/Mojave

This cleared the Couldn't allocate runtime area problem. Subsequently, I did the following:

• Because the BRCM94360CS2 is natively supported, I removed AirportBrcmFixup.kext. Might be okay to leave it (will try later).
• None of these was needed either:
  • BrcmFirmwareData.kext or BrcmFirmwareRepo.kext
  • BrcmPatchRAM2.kext
• The modified USBInjectAll custom SSDT is attached to Post #1. It removes HS14 and adds HS11. The filename is SSDT-UIAC-DESIGNARE-Z390-V3.aml. The DSL file is also uploaded so you can see the comments (all ports are commented).

I'll test Continuity/Handoff later. As of now, WiFi and Bluetooth are working even with repeated reboots.

-----
A Few Hours Later: Multiple reboots are not reliable. This evening I plan to try: (a) OsxAptioFix2Drv-free2000, (b) boot flag -f UseKernelCache=No.

 

[pastrychef]

Subsequently, I did the following:

• Because the BRCM94360CS2 is natively supported, I removed AirportBrcmFixup.kext. Might be okay to leave it (will try later).
• None of these was needed either:
  • BrcmFirmwareData.kext or BrcmFirmwareRepo.kext
  • BrcmPatchRAM2.kext

I'll test Continuity/Handoff later. As of now, WiFi and Bluetooth are working even with repeated reboots.

Don't bother wasting your time trying later. None of these kexts are needed for the natively supported BRCM94360CS2.

 

[CaseySJ]

Also, FYI.

Intel PTT had to be enabled for me to be able to boot. Unsure why yours needed to be disabled.

I just double-checked my PTT setting, and it is Disabled (I'm on BIOS version F4). I think I just blindly disabled anything that had "security" or "trust" in its name!

 

[CaseySJ]

Where did you see about there being an upcoming update for WhateverGreen? I couldn't find the hex code you mentioned in any of the source code.

I'm also unable to find it now; I might have misread 3E9B for 3E98. Just did a strikeout on that sentence in Post #1.