HorstBrack75

Please tell me, if you need something else from SysProfiler!

THX

IORegistryExplorer.zip SP.zip

On 8/31/2019 at 7:20 PM, Hervé said:

Ok, it's perfectly clear. You must be the 1st person for whom the DW1820A actually works nearly OOB!

I am 2nd.

08PKF4 OOB, no property injection, no masked pins on 10.14.6 (18G95)

Loaded kext: com.apple.driver.AirPort.BrcmNIC (1400.1.1)

Software Versions:

  CoreWLAN: 13.0 (1375.2)

  CoreWLANKit: 13.0 (1375.2)

  Menu Extra: 13.0 (1380.2)

  System Information: 12.0 (1300.2)

  IO80211 Family: 12.0 (1200.12.2)

  Diagnostics: 1.0 (805)

  AirPort Utility: 6.3.9 (639.9)

  Interfaces:

en6:

  Card Type: Third-Party Wireless Card

  MAC Address: xx:xx:xx:xx:xx:xx

  Supported PHY Modes: 802.11 a/b/g/n/ac

  Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165

  Wake On Wireless: Supported

  AirDrop: Supported

  AirDrop Channel: 149

  Auto Unlock: Supported

Card does not show up under PCI devices.

I am sure, it did not work before!

I only checked now after I read the post and I installed both Supplemental updates since I last tried.

Is it possible, that something changed with one of the last two 10.14.6 supplemental updates here?

Card: DW1820A, #CN08PKF4, 0x106b:0023

Hackintosh: Intel NUC8I7HVK

macOS versions: Mojave OK
Patch: "compatible pci14e4,4353" property injection in Clover

Kexts: AirportBrcmFixup, BrcmBluetoothInjector, BrcmFirmwareRepo, BrcmPatchRAM2, USBInjectAll

Boot parameter: brcmfx-driver=1

Tricks: Correct SSDT for USBInjectAll setting Bluetooth USB to internal. Disable VT-d in BIOS (AirportBRCMFixup), Disable Wake on LAN and PCIE ASPM in BIOS. Matching Bluetooth Firmware in Windows and MacOS (4689), Clover WIFI Fake ID 0x0

I thought everything was fine since WiFi and Bluetooth work great now including Handoff and without freeze. (Even though it is a CN-08PKF4).

I just noticed, that something must be still shady since running Wireless Diagnostics hard crashes the computer.

Did anybody try to run Wireless Diagnostics yet? 

Got it working now including Handoff using v7 4096. C/K/O only! 

- Configured USB correctly with USBInjectAll to get bluetooth USB on internal USB

- Added Device Property

- Added brcmfx-driver=1 brcmfx-country=#a

And VERY, VERY, VERY important, disabled Wake on LAN and PCIE ASPM in BIOS.

On 8/13/2019 at 12:04 PM, Hervé said:

The firmware only applies to the Bluetooth module of the card, not the wifi part.

 

On p10 (2nd post from the top), @astray provided a link to the Windows driver that updates BT firmware to v4689. You can use this safely to update the card. Then, you may use the following patching kexts in macOS. All this works for me but the card already worked well when showing firmware version v5799 or v5803 (see posts on p5 to p7).

Thanks that fixed it in Windows at least. Just as a side note and maybe the reason why there are 12 pages on this. None of the mentioned solutions seems to work for this card.  As I found out from other threads now, it seems to depend even on the subversion etc.

PCI\VEN_14E4&DEV_43A3&SUBSYS_00231028&REV_08\4&1A9424EB&0&00E2

PCIROOT(0)#PCI(1C02)#PCI(0000)

ACPI(_SB_)#ACPI(PCI0)#ACPI(RP03)#ACPI(PXSX)

It is possible to activate it but it will slow down the system and make it unusable.

Applying the workaround proposed in another thread to use AirportBrcmFixup and brcmfx-driver=1 for some reason does not work. It will not boot. 

Either I get AirPort_Brcm43xx start failed, Memory leak of bytes 116, Failed 'startGated()' or kext stall or an underrun or a kernel panic.

I read about masking pins but I really don´t like the idea.

THX anyway!

23 hours ago, tqbinh said:

Fortunately, I found a post on tonycrap (member midi1996) describing some kexts to patch to disable all (or most of?) native broadcom kexts, except for AirPort.Brcm4360.kext (see below), then the system boots normally. Wifi and bluetooth work as expected. However, the second and subsequent shutdowns give a waitq error, but it is acceptable for me at this moment. 

Note that I currently use all native 10.13.6 kext, only add  @nickhx kexts in C/K/O, add PCI Device Properties as @Hervé and kexts to patch as bellow. I attached my config.plist file for reference.

 

I got a CN-08PKF4 and I got it to work somehow work in MacOS using:

BrcmPatchRAM2.kext, BrcmFirmwareData.kext in EFI/CLOVER/Kext/Other.

"Somehow" means that I get KP booting MacOs two times before it actually boots.

The strange thing now is that WiFi stopped working in Win10 now. When I click on update driver in Windows 10, I get a Windows bluescreen now.

Did I maybe alter the firmware and break the card now?