Hervé

Your immediate hibernation/sleep issue is quite typical when you do not have the correct CPU power management settings in place. If you use a generated SSDT, make sure it's one made for your particular CPU, not a different model.

Having moved the HDD from a SandyBridge/HD3000 E6420 to an IvyBridge/HD4000 E6530, you'd need to adjust your Clover config and set up the following: Graphics section: Inject Intel layout-id 0x01660003 SMBIOS section: MacBookPro9,2

Last updated: 15 Jun 2024 We occasionally get questions about compatible graphics cards, so these articles should be useful for Hackintoshing purposes: 1) Best budget (under $50) graphics cards in 2024 Some of those cards are compatible with macOS up to High Sierra. Only a handful support Metal and Mojave/Catalina/Big Sur, i.e. Kepler architecture for nVidia (e.g.: GeForce GT 710) and GCN1.0 architecture for AMD (e.g.: AMD R5 240). And remember that, since Monterey, macOS dropped all support for nVida cards. 2) Best low-profile single-slot graphics cards for Small Form Factor (SFF) PCs in 2024 All those cards are compatible with late versions of OS X/recent versions of macOS. Afaik, all meet the minimum requirements for Metal but caution with nVidia cards since Mojave/Catalina/Big Sur only support Kepler models and, since Monterey, macOS dropped all support for nVida cards. 3) Best 1080p gaming graphics cards under $150 Those are good and reasonably priced cards, compatible with late versions of OS X/recent versions of macOS. Some do not need dedicated power supplies and will draw power from the PCIe bus. Afaik, all meet the minimum requirements for Metal but, again, caution with nVidia cards in Mojave/Catalina/Big Sur since those only support Kepler models and, since Monterey, macOS dropped all support for nVida cards. The site offers other "best graphics cards..." articles like "under $100", "under $200", etc. All available through a basic search.

I actually got one on order; 'should get it next week and then confirm whether it works or not. On paper, it's supported since based on BCM4350 chip which was fitted to 2015 MacBook8,1.

Your SKL layout 191b0000 (inside AppleIntelSKLGraphicsFramebuffer.kext) probably requires patching to support all the video outputs you desire: 00001B19 00000000 E1810800 00000000 // layout 0x191b0000 01030303 00002002 00005001 00000060 // 3 x display ports 6C050000 6C050000 00000000 00000000 00000800 02000000 98000000 // port #0, FB@0, LVDS 01050900 00040000 87010000 // port #5, FB@1, DP 02040A00 00040000 87010000 // port #6, FB@2, DP FF000000 01000000 20000000 0F110000 i.e. this layout defines 3 x output ports connector 0000, type 0200 0000 -> LVDS connector 0105, type 0004 0000 -> DP connector 0204, type 0004 0000 -> DP You need to identify through IOReg what port/connector each of those DP ports attach to, knowing that the layout may not support/include the necessary connector. Indeed, as detailed here, there's another potential connector 0306 (port #7, FB@4). So, using apps such as IORegistryExplorer, 1st check things in IOReg under your iGPU device located @2, it should show several framebuffer @0, @1, @2. FB@0 will be your built-in LCD and your DP ports should register under one of the other FBs. You should see things similar to what I posted here. If you only see a DP screen under FB@1 and not under FB@2, then you may have to patch that specific port to connector 0306. You may save your IOReg output, zip it and post it for us to look at it.

Erm... what error? As usual please post your system's specs + zipped copy of your Clover folder (less the Themes subfolder) if you want support.

You have multiple routers and presumably multiple wireless clients. 40MHz increases channel overlapping and likelihood of interference and packet loss, so clearly, 20MHz channels is the optimum choice. You'll find lots of info on this on the Web. If you want to improve your current performance using 40MHz bandwidth, you should modify your routers channels settings and set them apart to avoid overlapping.

A bootloader is a special piece of software that allow a non-Apple PC computer to boot OS X. It's not possible without it. Such software includes Chameleon, Enoch (a more recent version/branch of Chameleon), Clover (today's de-facto "standard" bootloader) and a (very) few others. Since their inception in the early days of Hackintosh, those tools evolved from simple bootloaders to sophisticated configuration packages. You're going to have to do some serious reading but to install macOS on a PC, the general process is to: 1) create a USB key with the OS installation package, aka a "USB installer" 2) install the bootloader on the key to make it bootable 3) install all the necessary drivers required to support your own specific hardware 4) tune your bootloader configuration You'll encounter barbaric terms like DSDT, SSDT, ACPI, tables, patches and patching. These refer to low-level tables that form part of a PC's BIOS and provide description of the computer hardware to the OS and how some of this hardware may behave. It's nearly always required to fine tune these tables (i.e. patch them) to be able to install and then run OS X. It's all very technical and requires some computing skills; it's quite different from inserting a CD or a DVD and booting it to install the desired OS...

Ok, took the DW1520 out of my D630 that runs Mojave 10.14.1 and replaced it by the AR5B93 card + installed 10.13.6's Atheros40 kext posted here. The results are more or less identical to what I obtained with the D430: Whilst your network are listed as 802.11n, I can see that the card only achieves a connection at a transmit rate of 11Mbps when my card achieves 117 to 130Mbps. This is clearly where your issue is. AR5B93 is 2.4GHz only and my router only offers 20MHz channels, not 40MHz. Maybe you should stick to 20MHz... Could also be linked to eventual limitation with Country Code...

You could have specified that subtlety from the onset... Atheros cards are no longer officially supported in Mojave so feel free to test Atheros40 kext from other versions if you're game. You can always extract the kext with Pacifist app from past Combo Update packages available for download off Apple's web site. Failing that, opt for a better card like DW1510; AR5B93 is getting a little long in the tooth today... I took out my old little Latitude D430 out of its cupboard and replaced the DW1510 fitted into it by the AR5B93 card I have lying around. It's this exact Foxconn T77H047 card. 'booted ML and ran Ookla legacy tests. Results are as good as I expected at around 70-80Mbps: Try and adjust your local connection settings. Good luck.

AR5B93 is supported OOB, i.e. with the vanilla Atheros kext installed by default in OS X. Your speed issue is not kext related per sé but connection related (channel settings, negotiation of connection between card and router). If your router supports 2.4GHz and 5GHz networks, try and split the SSIDs; Sharing the same SSID on both types of network can interfere.

Last update: 20 Jan 2019 Target macOS release: High Sierra 10.13.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration GT730: with macOS native/default drivers (or with nVidia Web Driver) GT1030: with nVidia Web Driver only multi-display, including VGA (with Lilu + WEG) GT730: DVI + HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 GT1030: DVI + HDMI OOB audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) CPU power management (works better with MacPro3,1 SMBIOS than iMac10,1) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) AppleALC supports the following layouts for ALC888: Audio found to work with all such layouts which individually support various inputs and outputs as shown below: I went with layout #1: VoodooHDA lists I/O that are more PC oriented Not working: N/A Not tested: N/A GeekBench v2.4.3 (32bit) gives a 4500+/4700+ rating: 1) 10.13 USB installer creation Using a USB key of 8GB minimum, create a High Sierra USB installer through the following Terminal command: sudo <path>/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of High Sierra installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> FSInject-64 / ApfsDriverLoader-64 / AppleImageLoader-64 BIOS Drivers, 64 bit -> GrubEXFAT-64 / GrubNTFS-64 (both optional only) Themes (optional only) Install Clover PrefPane (optional only) you may use version r4689 attached below or any subsequent version available at Dids' Github repo Clover_v2.4k_r4689.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the Vostro200 High Sierra Clover pack below to the EFI/Clover folder of the EFI partition Vostro200_10.13_Clover_Pack.zip 2) 10.13 installation boot the High Sierra USB installer and wait until you get to the language menu; it'll get there. at the Clover main menu, select the "Install macOS High Sierra" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target High Sierra installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target High Sierra partition>" repeat this until this partition is no longer offered and only the target High Sierra partition is left to boot 3) Post-Installation tuning Once the target High Sierra partition has booted, complete the 1st boot configuration finalisation Once at the desktop, install Clover bootloader on the High Sierra partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the High Sierra partition/disk Open this EFI partition and transfer the files & folders from the above Vostro200 High Sierra Clover pack to the EFI/Clover folder of the EFI partition You may then reboot and verify that High Sierra boots off your disk through Clover After that reboot, finalise post-installation tuning actions such as disabling hibernation, allowing all apps download from anywhere, changing all serial numbers, etc. Edit #1: 20 Jan 2019 New pack with updated DSDT re-patched for proper Sleep & Wake

'took the old girl out of retirement! Specifications: Modded/unlocked BIOS 1.0.16 (from www.bios-mods.com) with HDD set to AHCI mode (standard BIOS 1.0.16 with HDD set to RAID mode should be Ok too) G33M02 motherboard (dual-core CPUs only; G33M03 mobo required for quad-core CPUs) Intel G33 chipset (ICH9R, PCIe 1.1, PCI 2.3, SATA-II and USB 2.0) CPU: Intel Wolfdale Core2Duo E8600 @3.33GHz Intel Wolfdale-DP Xeon X5270 @3.5GHz (with LGA771-to-LGA775 mod) Integrated Intel GMA 3100 graphics (unsupported in Mac OS X/OS X/macOS and disabled in BIOS) Graphics card: Asus PCIe x16@x8 GeForce GT730 (Kepler) 2GB-DDR5 (10de:1287) single-slot low-profile, 1 x VGA + 1 x DVI + 1 x HDMI output + HDMI audio (10de:0e0f) Gigabyte PCIe x16@x4 GeForce GT1030 (Pascal) 2GB-DDR5 (10de:1d01) single-slot low-profile, 1 x DVI + 1 x HDMI output + HDMI audio (10de:0fb8) Yeston PCIe x16@x8 Radeon RX560 (Polaris 21/Baffin) 4GB-DDR5 (1002:67ef) single-slot low-profile, 1 x VGA + 1 x DVI + DVI, 1 x HDMI output + HDMI audio (1002:aae0) AMD PCIe x16@8 Radeon Pro WX4100 (Polaris 21/Baffin) 4GB-DDR5 (1002:67e3) single-slot low-profile, 4 x mini-DP outputs + HDMI audio (1002:aae0) 6Go 8GB DDR2-800 RAM Intel 82562V-2 10/100Mb FastEthernet (8086:10c0) ALC888 7:1 High Definition Audio (10ec:0888) TEAC CA-200 internal-USB 19-in-1 card reader (0644:0200) SATA CD/DVD RW drive Dell wireless keyboard and mouse (Bluetooth devices with dedicated USB dongle in HID proxy mode) 6 x USB 2.0 ports 2 x front jack ports (microphone + headset) 6 x rear jack ports (various audio I/O) Wireless/Bluetooth: any compatible PCI/PCIe card or USB dongle compatible with target macOS version With GT730: vostro200:lspci admin$ lspci -nn pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:00:1b.0 64-bit device address ignored. pcilib: 0000:00:1f.3 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1) With GT1030 (High Sierra only): vostro200:~ admin$ lspci -nn pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:00:1b.0 64-bit device address ignored. pcilib: 0000:00:1f.3 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1) For recommended BIOS settings, see here. These guides are for Vostro200 desktop computers fitted with a Wolfdale Core2Duo CPU (or Wolfdale-DP dual core Xeon CPU) that includes SSE4.1 instructions set. Conroe CPUs do not include these and are therefore unsuitable for macOS, they can only run OS X up to El Capitan. From Mojave to Big Sur, macOS natively supports nVidia Kepler cards only. As such, High Sierra 10.13 is the end of the road for Pascal cards such as the GT1030, knowing that these (like Maxwell cards) are only supported with the nVidia Web Driver due to lack of native drivers. From Monterey, macOS drops all native support for nVidia cards, marking the official end for Kepler cards. Support can however be recovered/provided by applying patches with tools such as OCLP. The only alternative is to use supported AMD cards (HD7000/HD8000 series minimum, Polaris minimum being favoured), hence why I opted for a Polaris21/Baffin RX560. AMD Radeon Pro WX4100 (LP card) is suitable too (tested 100% successfully). Both those AMD cards are natively fully supported. NB: Wolfdale-DP CPUs may require adjusting CPU clock rate parameter to highest multiplier in BIOS for proper CPU SpeedStep to work. Running on a Wolfdale-DP Xeon dual core CPU may also require the use of additional boot arg npci=0x2000 or npci=0x3000 to avoid boot freeze and system hard reset. It certainly did on my Vostro200 (but then again my X5270 was an ES model...).

Atheros/Qualcomm QCA6174 is unsupported. Consult out non-exhaustive inventory of supported cards/USB adapters available in R&D->Wireless section.

Consult the Wireless & Bluetooth section of the forum.

I don't mean to teach your granny to suck eggs but your battery life clearly depends on system usage as well as size + current age and health of your battery. Knowing that you've already disabled the dGPU and you've got proper CPU power management in place, you may slightly extend battery life by installing the kext that disables CPU Turbo boost when running on battery; that would of course be to the detriment of performance. Replacing a mechanical HDD by an SSD would also increase battery life. Generally speaking, battery drains quicker under OS X/macOS than under Windows due to heavier graphics demand. See how it compares between macOS and, say, Windows.

Again, you do not appear to have a discrete nVidia GPU and you run on HD5500 iGPU. MBP12,1 SMBIOS is perfectly Ok. Alternatives Broadwell profiles would be MBA7,x. Consult the list available in Clover Configurator app. If you do not call on generated CPU PM SSDT, you must set your Clover config for PluginType 1. You can Google for it or search the forum to find explanations. Fn-Insert/Fn-F3 should control brightness. If you seek to control brightness through Fn-UP/Fn-DOWN, you'd have to identify the ACPI code returned by those keys and program your DSDT accordingly. This is also something you can Google for but but know that it's very advanced stuff.

@roniez, nope, you're mistaken. Your IOReg clearly shows you run on HD5500 iGPU with no signs of an nVidia dGPU. It's fair to say it's either disabled or not present at all. --> Check your CPU power management settings.

No, that's definitely a no: kexts that are not related to any fitted hardware will not load! If that RTL8100 kext relates to the fitted LAN card, keep it!

If you have no related hardware, obviously there is no need for useless drivers...

Is there something you're specifically after? Change OSID to XSID (to avoid match against _OSI XOSI patch) Change _OSI to XOSI, use with SSDT-XOSI.aml Change _DSM to XDSM (needed for _DSM injections, e.g. for HDEF, IGPU) Change ECDV to EC (so Mac OS knows about the Embedded Controller) Change HDAS to HDEF (needed for audio) Change HECI to IMEI (so Mac OS can natively use the Management Engine) Change GFX0 to IGPU (needed for graphics) Rename method UPRW to XPRW and use with SSDT-UPRW.aml to fix USB "instant wake" on sleep Rename method GPRW to YPRW and use with SSDT-UPRW.aml to fix USB "instant wake" on sleep change GPI0 device _STA to XSTA change I2C devices _CRS to XCRS I'm not really in a position to make much comment... I saw nothing out of the norm or that was not applicable to your raw DSDT.

If you're unable to connect all 3 x antenna connectors, the card will still work on 2 x antennas but at a reduced rate. In the case of the DW1830, instead of peaking at 1.3Gbps (3 x 433Mbps), you'd be limited to 867Mbps (2 x 433Mbps) max. Signal quality and reliability would also be somehow impacted but not necessarily to the point where it would become an issue...

I confirm that DW810 is not supported (and never will be). DW1830 is based on Broadcom BCM4360 and does indeed work OOB, so nothing to do.

Last update: 13 Nov 2023 This 2nd inventory comes to complement our original one created back in 2013 which is now restricted to cover wireless cards under Snow Leopard 10.6 to El Capitan 10.11. This new list will provide the equivalent for macOS versions (Sierra 10.12 and later) given that it's getting complicated to keep everything under a single text table and Apple has been increasingly dropping support for wireless cards since the introduction of macOS Sierra in 2016. I invite everyone to bring his/her own contribution and it'll be added to the list. This post will be updated as contributions come along in order to keep the list under control. Hardware specifications can be verified here: https://wikidevi.wi-cat.ru. A few OS X/macOS-related wireless cards buying guides also exist where summarised chipset support is available. Please use your preferred search engine to look these up, we won't provide links since this would infringe our own posted rules. Note: OOB = Out of the Box /!\ Sierra 10.12 dropped support for old Broadcom BCM431x and BCM4321 cards. There is no workaround, they have to be replaced. /!\ /!\ Mojave 10.14 dropped support for Atheros cards. The workaround is to install the Atheros40 kext from an earlier release like High Sierra 10.13.6, i.e. copy to /L/E + repair permissions + rebuild cache. /!\ 10.13.6_AirPortAtheros40.kext.zip /!\ Catalina 10.15 no longer supports injection or caching of High Sierra's AirPortAtheros40 kext. Instead, install High Sierra's IO80211Family kext, i.e. copy to /L/E + repair permissions + rebuild cache (leaving /S/L/E untouched) or, if that does not work, replace Catalina's IO80211Family kext in /S/L/E by High Sierra's. /!\ 10.13.6_IO80211Family.kext.zip /!\ Catalina 10.15 dropped support for BCM4322 (14e4:432b). AirPortBrcm4331 plugin kext of IO80211Family kext was abandoned. This affects cards such as DW1510. Workaround is to simply install Mojave's (or High Sierra's) IO80211Family kext, i.e. copy to /L/E + repair permissions + rebuild cache (leaving /S/L/E untouched) or, if that does not work, replace Catalina's IO80211Family kext in /S/L/E by Mojave's (or High Sierra's) but this will need to be done again after each update because vanilla kexts will be re-installed. /!\ 10.14.6_IO80211Family.kext.zip /!\ Intel wireless: some recent models may now enjoy support thanks to development detailed on OpenIntelWireless Github repo. /!\ Big Sur dropped support for BCM4331 (14e4:4331) and BCM43224 (14e4:4353). A patched version of Catalina's IO80211Family kext may be used as workaround (only AirPort4360 PlugIn is retained). Kext can then be called from OC config by setting minimum kernel to version 20. See here for details. /!\ /!\ Atheros cards previously supported in High Sierra and earlier (eg: AR928x, AR9380) can be supported under Big Sur with a patched version of High Sierra's IO80211Family kext . Kext can then be called from OC config by setting minimum kernel to version 18. See here for details. /!\ /!\ Monterey 12.x does not support patches/workarounds for dropped cards such as Atheros or Broadcom BCM4322. Same for Broadcom BCM4331 or BCM43324. Such cards have to be replaced by models supported in Monterey. /!\ Sonoma drops all official support for Broadcom "legacy" cards that were natively supported up to Ventura (chipsets BCM4350, BCM4360, BCM43602). OCLP patcher is now required for all non-Intel wireless cards that were previously supported. Unsupported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca BS Mt Vt OOB Kext/comment Intel - - - - - - - - - - - - N See here Atheros AR5BXB6 Mini PCIe 168c-001c AR5424 A/B/G N N N N N N N - - AzureWave AW-CB161H ½Min PCIe 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB209NF NGFF/M.2 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB210NF NGFF/M.2 14e4-43ec BCM4356 A/B/G/N/AC N N N N N N N - - AzureWave AW-NB155NF NGFF/M.2 14e4-4365 BCM43142 B/G/N N N N N N N N - - Dell DW1390 Mini PCIe 14e4-4311 BCM4311 B/G N N N N N N N - - Dell DW1395 Mini PCIe 14e4-4315 BCM4312 B/G N N N N N N N - - Dell DW1490 Mini PCIe 14e4-4312 BCM4311 A/B/G N N N N N N N - - Dell DW1505 Mini PCIe 14e4-4328 BCM4321 A/B/G/N N N N N N N N - - Dell DW1397 ½Min PCIe 14e4-4315 BCM4312 B/G N N N N N N N - (=DW1395) Dell DW1501 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N N N N - - Dell DW1503 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N N N N - - Dell DW1504 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N N N N - - Dell DW1530 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N N N N - - Dell DW1540 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N N N N - - Dell DW1701 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N N N N - - Dell DW1704 ½Min PCIe 14e4-4365 BCM43142 B/G/N N N N N N N N - - Dell DW1810 NGFF/M.2 168c:0042 QCA9377 A/B/G/N/AC N N N N N N N - (=QCNFA435) Dell DW1820 NGFF/M.2 168c:003e QCA6174A A/B/G/N/AC N N N N N N N - (=QCNFA344A) Qualcomm QCNFA435 NGFF/M.2 168c-0042 QCA9377 A/B/G/N/AC N N N N N N N - - Qualcomm QCNFA344A NGFF/M.2 168c-003e QCA6174A A/B/G/N/AC N N N N N N N - - Ralink RT5390 ½Min PCIe 1814-539b RT5390 B/G/N N N N N N N N - - Supported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca BS Mt Vt OOB Kext/comment Intel - - - - - - - - - - - - N See here Atheros AR5B91 Mini PCIe 168c-002a AR9281 B/G/N Y Y * * * N N Y * See above for Mojave Atheros AR5BXB72 Mini PCIe 168c-0024 AR5418/5133 A/B/G/N Y Y * * * N N N patch Atheros40 Atheros AR5BXB92 Mini PCIe 168c-002a AR9280 A/B/G/N Y Y * * * N N Y - Atheros AR5BXB112 Mini PCIe 168c-0030 AR9380 A/B/G/N Y Y * * * N N Y - Atheros AR5B22 Mini PCIe 168c-0034 AR94621 A/B/G/N Y ? * * ? N N N FW + Atheros40 patch Atheros AR5B93 ½Min PCIe 168c-002a AR9283 B/G/N Y Y * * * N N Y - Atheros AR5B95 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N DSDT/Atheros40 patch Atheros AR5B97 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * * N N N DSDT/Atheros40 patch Atheros AR5B195 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B95+BT3.0) Atheros AR5B197 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * * N N N (=AR5B97+BT3.0) Atheros AR5BHB92 ½Min PCIe 168c-002a AR9280 A/B/G/N Y Y * * * N N Y - Atheros AR5BHB112 ½Min PCIe 168c-0030 AR9380 A/B/G/N Y Y * * * N N Y - Atheros AR5B125 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N FW + Atheros40 patch Atheros AR5B225 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N FW + Atheros40 patch AzureWave AW-NB037H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) AzureWave AW-NB048H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) AzureWave AW-NB290H ½Min PCIe 14e4-4357 BCM43225 B/G/N Y Y Y Y Y Y Y N DSDT/kext patch AzureWave AW-CE123H ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y Y N DSDT/kext patch AzureWave AW-CB160H ½Min PCIe 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Dell DW1502 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B95) Dell DW1506 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N (=AR5B125) Dell DW1510 ½Min PCIe 14e4-432b BCM4322 A/B/G/N Y Y Y * * N N Y - Dell DW1515 ½Min PCIe 168C-002a AR9280 A/B/G/N Y Y * * * N N Y (=Atheros xB92) Dell DW15202 ½Min PCIe 14e4-4353 BCM43224 A/B/G/N Y Y Y Y * * * Y/N MBA5,2/Brcm4360 patch Dell DW1550 ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y ? N DSDT/kext patch Dell DW1601 ½Min PCIe 168c-0034 AR94621 A/B/G/N/AD Y Y * * ? N N N (=AR5B22) Dell DW1702 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) Dell DW1703 ½Min PCIe 168c-0032 AR94851 B/G/N Y Y * * ? N N N (=AR5B225) Dell DW1705 ½Min PCIe 168c-0036 AR95651 B/G/N Y Y * * ? N N N FW + Atheros40 patch Dell DW1560 NGFF/M.2 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y ? N DSDT/kext patch Dell DW1707 NGFF/M.2 168c:0036 AR95651 B/G/N Y Y * * ? N N N FW + Atheros40 patch Dell DW1802 NGFF/M.2 168c-0034 AR94621 A/B/G/N Y Y * * ? N N N (=AR5B22) Dell DW1820A3 NGFF/M.2 14e4-43a3 BCM43503 A/B/G/N/AC Y Y Y Y * * * N DSDT patch/injection Dell DW1830 NGFF/M.2 14e4-43ba BCM43602 A/B/G/N/AC Y Y Y Y Y Y Y Y - Fenvi BCM94360NG NGFF/M.2 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Asus USB-N10 USB 2.0 0b05-1786 RTL8188SU B/G/N ? ? ? ? ? ? ? N RealTek's v2.0.1 Asus USB-AC51 USB 2.0 0b05-17d1 MT7610U A/B/G/N/AC ? ? ? ? ? ? ? N Asus's driver CSL Nano V.2 USB 2.0 0bda-8176 RTL8188CUS B/G/N Y Y Y Y Y Y ? N ? D-Link DWA-121 A1 USB 2.0 2001-3308 RTL8188CUS B/G/N Y Y Y Y Y Y ? N ? Lafalink LF-D10 Nano USB 2.0 148f-7601 MT7601 B/G/N Y Y Y Y ? ? ? N Ralink's v4.2.9.10/RT2870 Driver Lafalink LF-D12 Nano USB 2.0 148f-5370 RT5370 B/G/N ? ? ? ? ? ? ? N Ralink's v4.2.9.2 NetGear WNA3100M USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? ? ? ? N Realtek's v2.0.1 On-Nwrks N300 USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? ? ? ? N Realtek's v2.0.1 Tenda W522U USB 2.0 148f-3572 RT3572 A/B/G/N Y Y ? ? ? ? ? N TP-Link/Ralink TP-Link TL-WN725N v2 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN723N v3 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v1 USB 2.0 0bda-8178 RTL8192CU B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v2 USB 2.0 2357-0109 RTL8192EU B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v3 USB 2.0 ????-???? ???? B/G/N Y Y Y Y ? ? ? N TP-Link's driver Asus USB-AC56 USB 3.0 0b05-17d2 RTL8812AU A/B/G/N/AC ? ? ? ? ? ? ? N Asus's driver Asus PCE-AC66 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Asus PCE-AC68 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - TP-Link TL-WN781ND v1 PCIe x1 168c-002b AR9285 B/G/N Y Y * * * * * N DSDT/Atheros40 patch TP-Link TL-WDN4800 PCIe x1 168c-0030 AR9380 A/B/G/N Y Y * * * * * Y - TP-Link Archer T9E PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - NB: Patching means adding the PCI ids of the listed card to the Info.plist file found inside the listed kext. In rare cases, binary patching may also be necessary. For some cards, DSDT Patching can be a suitable and permanent alternative to kext patching (no need to repatch a kext after OS X updates and upgrades or new installations). For instance, in the case of the Atheros AR5B95 card (chip AR9285 168c,2b), adding compatibility with a chip known to be supported OOB such as AR9380 168c,30 or AR9280 168,2a (as found in the vanilla Atheros40 kext) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x1E) { "Atheros AR5B95 b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci168c,30" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ` In the same respect, in the case of the Broadcom BCM4322x cards (e.g.: chip BCM43225 14e4,4357) or BCM4352 cards (14e4,43b1), adding compatibility with a chip known to be supported OOB such as BCM94360 14e4,43ba or 14e4,43a0 (as found in the vanilla AirPortBrcm4360 kext or AirPortBrcmNIC) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x23) { "AzureWare AW-NB290H b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci14e4,43a0" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ` Broadcom BCM43224-based cards with id 14e4:4353 (e.g.: DW1520) are subject to whitelisting in AirPortBrcm4360 kext. Wireless will only work if using the SMBIOS of a supported Mac model or after binary patching the kext to inject the Mac board-id of the desired SMBIOS. See our patching guide on the matter. ________________ 1 AR946x (168c,34), AR9485 (168c,32) and AR9565 (168c,36) work to some degree (i.e. not 100%) with alternative (re-written) Atheros40 driver as posted at InsanelyMac by Chunnann. Further patching facility posted here. These cards appear very poorly supported to plain unsupported from High Sierra. They are NOT recommended. 2 DW1520 (14e4,4353) is known to suffer from frequent and repeated wireless disconnections when plugged into mini PCIe-only slot and built-in Bluetooth is enabled. This may even lead to wireless turning off. This has been noticed on Dell Latitude E6x20 and E6x30. Wireless works Ok once built-in Bluetooth is disabled in BIOS or, as stated by wl_michael, if the card is fitted into combo PCIe/USB slot such as WWAN. 3 DW1820A and other BCM4350-based cards are supported. See our BCM4350 guide for these cards. * See top of post for Mojave, Catalina, Big Sur, Monterey and Ventura.

It does indeed sound like the laptop is entering hibernation. If that's what you want, you have to apply special Clover settings to support hibernation (and you can Google for that). Failing that, disable hibernation and revert to plain old sleep as described in our FAQ forum section.