ASUS ProArt X670E-CREATOR WIFI peripheral issues

[Reproach1481]

Hi everyone! Glad to be a part of the community.

I've been Hackintoshing for 10, but you know how it goes – you get one machine to work flawlessly (my trusty old Dell XPS 13 9350), occasionally update it and fix the issues, but your proficiency goes through a window because of the amazing advancements the community is making.
Here I am needing a second pair of eyes myself on a new build I tried to run macOS Sonoma 14.7.4 on.

Spoiler: Specs

• CPU: AMD Ryzen 9 7900X
• MOBO: ASUS ProArt X670E-CREATOR WIFI
  • Since it has a AMD RZ616/Mediatek MT7922A22M, which I'm fairly certain won't be supported, I've decided to swap it for a DellDW1820A I had lying around from my old Dell
• RAM: G.Skill Trident Z5 RGB DDR5 96GB (2x48GB) 6400MHz CL32 XMP3 F5-6400J3239F48GX2-TZ5RW
• M.2 1: Lexar NM790 1TB PCIe Gen 4 NVMe SSD – macOS system
• M.2 2: Lexar NM790 2TB PCIe Gen 4 NVMe SSD – data
• M.2 3: (empty not to mess with the PCIe 3 slot as they share bandwidth)
• M.2 4: Samsung 970 EVO Plus 1TB PCIe Gen 3 SSD – data/probably Windows/Linux dual-boot if needed in the future
• SATA 1: LG BH16NS40 Blu-Ray Optical Drive
• SATA 2: Crucial MX500 2TB SATA SSD
• SATA 3: Seagate Exos 7E8 8TB SATA HDD
• SATA 4: Old shucked Seagate 5TB SATA HDD
• PCIe 1: MSI Armor OC RX580 8GB
• PCIe 2: (empty)
• PCIe 3: StarTech PEX1394A2V2 FireWire card (need it to drive my trusty old RME FireFace 400; works flawlessly out of the box!)
• PSU: be quiet! Dark Power 13 850W fully modular power supply

I have used the EFI kindly posted by the ovenlite1 here as a base and adjusted it to my build somewhat (CPU cores number, got rid of agdpmod=pikera because RX580 is natively supported and various little tweaks here and there).

And so, here are the issues I encountered:

---

1. Boot drive (as the only one from the NVMe drives) shows as external - purely cosmetic but should be easy to fix, right?
2. Boot sequence takes a while, after which none of the SATA devices show up. In System Information, they all show as Unknown:
   
   Spoiler: Screenshot

   
3. Can't get Dell DW1820A to work – I mostly use the 10Gbps connection anyway, but I'd like to have all those native Wi-Fi + BT features like Continuity, Handoff, Airdrop etc., and from my understanding, it should be pretty straightforward with the Broadcom chip in the DW1820A. I have tried using OCLP with the kext replacement as per OSXlatitude guide, and weirdly enough, I couldn't get it work. In the process, it would also mess up my Ethernet ports, so I was left with no connectivity, and after injecting Broadcom kexts and patching the kernel, the card would stop showing up in devices altogether. Exported PCIe device list from Hackintool attached to this post below.
   
   Spoiler: Screenshots

   
4. There is something weird going on when I try to reset NVRAM and try to boot. What happens after OC boot selection: Boot progresses for a 2-3s and then reboots the machine, after which the system boots fine (although it is the slow boot with many errors regarding SATA devices). There must be something going on in that first boot that shouldn't be happening…
   Here are both kernel-boot.txt and system-boot.txt from Hackintool that cover only the "second" boot (successful), but I'm also including a bigger chunk in system-boot-1.txtthat hopefully covers the "first" (unsuccessful) boot as well:
   • kernel-boot.txt
   • system-boot.txt
   • system-boot-1.txt (careful, it's big)

Current EFI and export from IORegistryExplorer v2.1 attached. Also attaching the SysReport generated by OC during one of the previous boots and 2 OC boot logs from the current boot sequence (similar to the ones above - first "unsuccessful" boot and then the second "successful" one).

Thanks in advance - hopefully we can figure all of this out!

 

[Edhawk]

1. To fix internal PCIe drives showing as External, add Innie.kext to your OC setup.

GitHub - cdf/Innie: Make PCIe drives appear internal

Make PCIe drives appear internal. Contribute to cdf/Innie development by creating an account on GitHub.

github.com

2. The SATA drives do they work as expected?

Is the Generic Controller and 'Unknown' drive names cosmetic, or does it prevent the SATA drives working?​

Which SATA drives are you using, ie, make and model?​

You may need to create a custom SSDT, Kext or add DeviceProperties to your config.plist, to set the SATA drive Devices with the correct names and AMD SATA controller.​

​

What does the Hackintool > PCIe tab show regarding your SATA drives?​

​

3. Dell 1820A WiFi/BT card, have you used/added the Device Properties entry shown below to your config.plist, to get the DW1820A Power Management to work correctly in macOS?

​

​

A DW1560 might be a better WiFi/BT card for your Hack, if this DeviceProperties entry doesn't help.​

​

Hackintool showing BCM_4325C as the Bluetooth module name usually means the Bluetooth device has not been configured correctly.​

​

​

​

Look to make sure the USB port serving the BT device is set with connector type Internal (255).​

​

4. Needs more time to investigate than I have available at present. I will come back to this when I have the time, later today or tomorrow, if someone else doesn't offer any suggestions on how to fix this issue.

 

[Reproach1481]

Hi @Edhawk – hugely appreciate your help!

1. Solved, thank you! Instead of going with a kext, I tracked down the NVMe in IORegistryExplorer and injected the bulit-in property in OpenCore – all good now and it shows up where it should.
2. This was super weird… I noticed that due to some property injection/ACPI patching weirdness, they would sometimes show up, while sometimes they would be completely missing. When they are showing as Unknown, they are completely non-functional; do not appear in Disk Utility/diskutil at all. Other times they work fine and show up as expected. Hard to track it down right now, so I'll be back to this when the rest of the issues are solved.
3. Yes – or at least, I tried to! Here's what I tried today:
   

   State	Wi-Fi	Bluetooth
   Completely clean slate (no Broadcom kexts, no AirportBrcmFixup kext, no property injection)​	Card not listed up in Network devices in Hackintool, not showing in PCI devices nor in gfxutil; Not working	Not listed in Hackintool; Not working
   AirportBrcmFixup + AirportBrcmNIC_Injector​	Card not listed in Network devices in Hackintool, but shows up in PCI devices and in gfxutil: 7d:00.0 14e4:43a3 /PCI0@0/GPP7@2,1/UP00@0/DP40@8/UP00@0/DP00@0/ARPT@0 = PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) Not working	Listed in Hackintool as 004c:6000 Apple BCM_4350C2; Not working
   Above + BrcmFirmwareData + BrcmPatchRAM3 + BlueToolFixup​	Same as above; it is shown in the PCI devices and gfxutil; Not working	Same as above; Not working
   Above + pci-aspm-default injection​	Same as above, it is shown but still not working; even more interesting, there are two entries in the IORegistry explorer: One is under ARPT@0 which is probably from the kexts, and the injected properties show up under WIFI@0 which is a completely separate entry. They both have a different acpi-path and that is really confusing for me: Spoiler: ARPT@0 Spoiler: WIFI@0 Not working	Same as above; Not working

I have also redone USB mapping using the USBToolBox on WinPE but it didn't change a thing – curiously, none of the ports showing up in e.g. Hackintool are labeled as Internal despite setting up some of them in the UTBMap.kext.
Checked if the WiFi/BT works at all – and it does work out of the box under Manjaro LiveCD environments (it's what I had handy); it is able to connect, sustain the connection, pair with BT devices etc. Attaching both lspci and lsusb dump from Manjaro.

Please, do not spend much time figuring the last one out for now – I've noticed that this happens when I boot another system and then try to boot macOS afterwards through OC, might be an intermittent thing or maybe something ACPI related. I'd like to figure this one out but it's not worth your time at this point, I think!

I might do a fresh install of Ventura instead, if getting the DW1820A working would be easier there. I don't really have a need for the newest macOS version at the moment, so let me know if that's viable