Hervé

Mojave patcher tool is for unsupported platforms. The X1 Carbon 3rd gen meets all the technical requirements for Mojave, so, afaik, no need for the patcher.

No, not all E6230 are fitted with the same card.... As written on the labels; it's a Dell DW1540, based on Broadcom BCM43228. It's listed in our inventory (link provided above) and you're out of luck, sorry.

Sigh... This "original wifi/bluetooth combo card", what is it ? Make and model? Intel cards not supported. If you have one, it will need to be replaced. Consult our inventory.

Is your installation full vanilla or a distro? Post a zipped copy of your Clover EFI folder.

I don't know what more you expect... I ask you something, you reply something unrelated... All in all, it seems you do not have any mini-PCIe wireless card but are running on the built-in DW380 BT 4.0 module and a TP-Link TL-WN821N v5 USB dongle for wifi. Nothing further to add, I guess your done.

New Latitude 7490 now available in Guides section: Only the Realtek RTS525A microSD card reader and the buttons of the Alps Touchpad aren't working. External mouse recommended...

AR5BXB63 carries PCI id 168c:001c. This is an old card that is only supported up to Lion 10.7.5, not in any subsequent OS X/macOS versions as stated here: It would be most helpful if you could say what card you have in your E6230 at the moment. Is there a problem giving out this info???

Framebuffer patching is mandatory for gaining those desired VGA/DP/DVI output. From memory HDMI output should work OOB but patching still is required to gain HDMI audio output.

As specified here, Bluetooth module carrying PCI id 413c:8197 is Dell's built-in BT 4.0 DW380. That's supported under OS X/macOS but limited to very basic usage (no AirDrop, no Handoff). You must untick Bluetooth in BIOS->Wireless to disable that module and hope to use the BT module of any Wireless/BT combo card fitted in one of the mini-PCIe slot. Failing that, the built-in module takes precedence over the combo card. I've experienced this. You need to post the make and model of your Wireless (or combo Wireless/BT) card and/or its PCI id.

Lenovo 00JT494 is indeed the same as the DW1820A: https://wikidevi.com/wiki/Foxconn_T77H649.00 Do not go for those Qualcomm Atheros-based devices you mentioned above, they're poorly supported under macOS. Stick to Broadcom-based cards.

Arf! No, I don't own any E7250 and I guess you didn't check the adapter/card size before buying! But what's that other slot, next to the M.2 WLAN one? It seems larger. If you have to look for another card and still exclude the DW1830, I very recently (yesterday) got my M.2 2230 DW1820A card fully working under High Sierra/Mojave. That will definitely fit into your slot and may be a more suitable alternative... It sells from $10€ to $20.

By NFC sticker, do you mean the NFC/RFID logo that is engraved on the laptop's casing when it is fitted with an optional finger scanner and Contactless SmartCard Reader? That would indeed be the Broadcom BCM5880 chip but that's not supported under OS X/macOS. You can read more about that chip here: https://ridrix.wordpress.com/2009/06/30/dell-embedded-contactless-smartcard-reader/ Those chips and associated security devices are normally directly supported by applications, not through OS drivers. For example, this was the case for the finger scanners of fitted to old Latitude D4x0 or other models of that generation. There were Mac applications that could use those to provide authentication under Snow Leopard, Lion or Mountain Lion. Subsequent chips/scanners/readers were dropped and I'm not sure the apps were updated over time. If, by NFC sticker, you meant an actual NFC tag, I don't think that can unlock your computer, no. Unless you have a NFC reader of some sort installed in the laptop that can read/scan that tag and decode it. But it would not make any sense... By definition, an NFC sticker/tag's purpose is to be approached by an NFC-enabled device in order to trigger an action/execute a task on that device through a specifically NFC-tuned application. Most common NFC-enabled devices would be SmartPhones... Or does your 7480 actually have an NFC radio/reader that, when presented with an NFC tag or an NFC card could then automatically enter the password that will unlock it? This would require an NFC-tuned app on the PC too. But as far as I know, it's just another Contactless Smart Card Reader that Delll handle through their ControlVault2 security driver/package. https://lifehacker.com/use-nfc-tags-to-unlock-your-computer-1561695242 The two (NFC tag and NFC reader) are not the same at all... If your 7480 is NFC-enabled, it'll carry a logo on the case (not a sticker/tag): https://www.dell.com/support/article/fr/fr/frbsdt1/sln292603/how-do-i-use-near-field-communication-nfc-on-dell-systems?lang=en You can read here about Apple's own NFC adoption (for Payment through iPhone or Apple Watch); and that's about it! If you have an NFC reader, I expect support to be a matter for NFC applications. Eg: https://itunes.apple.com/us/app/nfc-tools-for-desktop/id1392471092?mt=12

For displays, you can refer to the E6220 and HD3000 threads I linked to on p1. Remember that HD3000 only supports 2 x concurrent displays, not 3. So it'll be internal LCD + 1 external display or 2 x external displays only.

Please refer to my previous post; I just finished updating it.

You're not using the adequate kext for TouchPad and Keyboard. Use this one, I can vouch for it. You'll have to activate Tap to Click through the PrefPane. VoodooPS2Controller.kext.zip Your Clover config is a little incorrect; use this revised version instead. config.plist.zip Your Clover config makes reference to "SSDT.aml" for obvious CPU power management purposes (mandatory on your 2nd gen Sandy Bridge platform) but you're missing the file. Use Pike R Alpha's SSDT generator script to generate your own file anyplace it in Clover's EFI/CLOVER/ACPI/patched folder. You'll then gain full CPU SpeedStep + Turbo boost. As for the WebCam, look here for the supported and unsupported models. Then lookup your camera's own PCI ids in SysProfiler/System Information. You must have the unsupported model...

EFI folder available in post #2 on p1...

Thread moved. Please don't post in the Guides section which is clearly labelled "Guides only, no support" ! Coming back to your predicament: your disk reports IO errors. You need to look into that, say with Disk Utility having booted your macOS USB installer. kernelcache/PrelinkedKernel is reported as needing rebuild right before your system hangs. If your disk LED is showing activity, wait several minutes for this rebuild to complete. Failing that, try and boot your USB installer and deletes the cache + PrelinkedKernel folders from Terminal.

@jean512, there you are: DW1820A fully functional under High Sierra and Mojave... By the way, you don't have a Dell DW1820A but the Lenovo / Foxconn T77H649.00 equivalent (different subsystem id 17aa:075a)

Last update: 17 Jun 2020 Target macOS release: Mojave 10.14.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on Intel UHD620 iGPU, including brightness control (with Lilu v1.3.5 + WEG v1.2.7) multi-display with HDMI OOB, including HDMI-to-DVI adaptation (HDMI-to-VGA not successful) and VGA/DP over USB Type-C audio, including HDMI, microphone input and headset output (with AppleALC v1.3.6 & layout 11 + CodecCommander v2.7.1) GigEthernet LAN connection (with IntelMausiEthernet 2.4.0 kext) wireless and bluetooth with any compatible card (a DW1820A in my case) left and right USB ports (with Hackintool-generated USBPorts), including USB Type-C integrated webcam (OOB) CPU power management sleep (Lid, Energy Saver settings, Apple menu, Fn-Insert, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) keyboard (with VoodooPS2Controller v1.9.2) touchpad (with VoodooI2C v2.1.4 + VoodooI2CHID v1.0), including tap-to-click (mandatory in PrefPane settings), scroll & zoom, rotate or other multi-finger gestures. On occasions, won't work until system is rebooted one or several times. Not working: Touchpad buttons TrackPoint Not tested: RTS525a microSD card reader with Cholonam's revised sinetek-rtsx kext GeekBench v2.4.3 (32bit) gives a 14200+ rating: 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave 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: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers AudioDxe-64 DataHubDxe-64 FSInject-64 SMCHelper-64 ApfsDriverLoader-64 AppleImageLoader-64 AptioMemoryFix-64 Fat-64 HFSPlus NvmExpressDxe-64 PartitionDxe-64 Ps2MouseDxe-64 UsbKbDxe-64 UsbMouseDxe-64 Themes (optional) Install Clover Preference Pane (optional) you may use version r4919 attached below: Clover_v2.4k_r4919.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/copy the files & folders from the Latitude 7490 Mojave Clover pack below to the EFI/Clover folder: Clover_Pack_7490.zip Clover_Pack_7490_#2.zip Clover_Pack_7490_#3.zip Clover_Pack_7490_#4.zip Clover_Pack_7490_#5.zip Clover_Pack_7490_#6.zip Clover_Pack_7490_#7.zip Clover_Pack_7490_#8.zip 7490_Mojave_Clover_Pack_#9.zip 2) 10.14 installation boot the Mojave USB installer at the Clover main menu, select the "Install macOS Mojave" 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 Mojave installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Mojave partition>" repeat this until this partition is no longer offered and only the target Mojave partition is left to boot Reboot the target Mojave partition via your USB installer 3) Post-installation tuning Once the target Mojave partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Mojave 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 Mojave partition/disk Open this EFI partition and transfer the files & folders from the above Latitude 7490 Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots off your disk through Clover Edit: 16 Apr 2019 - - - - - - - - - - - - Tuned-up Clover pack #2: removed unnecessary SSDTs removed unnecessary patches removed unnecessary settings added NoTouchID kext to fix authentication lag when making changes to /LE and/or /S/L/E replaced I2C kexts to fix TouchPad laggy/jumpy movement Edit: 31 Jul 2019: - - - - - - - - - - - - Revised Clover pack #4: patched DSDT added to inject support for Fn-F11/Fn-F12 brightness keys. Edit: 09 Aug 2019: - - - - - - - - - - - - - Revised Clover pack #5: fixed mistake in patched DSDT affecting _PWR resources which killed Sleep when laptop running on mains. Edit: 15 aug 2019: - - - - - - - - - - - - - Revised Clover pack #6: Adjusted Clover config to add "DellSMBIOSPatch" in order to avoid truncated Mac model name in "About This Mac". Edit: 08 Sep 2019: - - - - - - - - - - - - - Revised Clover pack #7: Patched DSDT of pack #6 was causing system reset. Re-patched raw DSDT from BIOS 1.11.0 to inject support for Fn-F11/Fn-F12 brightness keys (no other patch) and all seems Ok. Edit: 05 Oct 2019: - - - - - - - - - - - - - Revised Clover pack #8: Injected HDMI connector type to iGPU FB@1 to recover from a picture issue (like yellow veil) with HDMI output + loss of HDMI audio, all due to default DP connector type on the framebuffer. This worked OOB initially (certainly did with my initial 10.14.4 build) but clearly not any more with subsequent Mojave versions, at least 10.14.6. Edit: 20 Apr 2020: - - - - - - - - - - - - - Added a note about Realtek RTS525a SD card reader. Edit: 17 Jun 2020: - - - - - - - - - - - - - Revised Clover pack #9: Moved patched DSDT out of ACPI/patched folder since it's causing KP for most people. It was only patched to support brightness control through Fn-F11/Fn-F12. Jake Lo has provided SSDT alternatives in other guides/threads so it's best to use that. I'll try them asap on the 7490 and update accordingly.

With a text editor or other tools such as PlistEdit Pro.

Last update: 28th Jan 2020 Dell DW1820A: Ok Ok Ok DW1820A is a pretty good combo card providing 2.4/5GHz 802.11ac wireless at 867Mbps + Bluetooth 4.1. As stated at Wikidevi, there appears to be a few different models of the card. Whilst they all carry the same Broadcom id 14e4:43a3, they each carry a different subsystem id/part #: 1028:0021 (part # CN-0VW3T3) -> 100% Ok with ASPM disabled (originally tested 100% Ok on my Latitude 7490 without ASPM tuning) 1028:0021 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0022 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0023 (part # CN-0VW3T3) -> 100% Ok with APSM disabled 1028:0023 (part # CN-08PKF4) -> 100% Ok with APSM disabled I acquired a Dell DW1820A a few months ago and was able to play with that card on a Latitude 7490 laptop (fitted with an M.2 2230 Key A+E WLAN slot) that I targeted for Mojave. The model I received was CN-0VW3T3. Before it was later established that not all DW1820A were equal, I purchased a 2nd one and, as it turned out to be, was lucky to receive another 0VW3T3 model. /!\ The 1st thing I want to report is that I encountered difficulties booting my Mojave USB installer and installing macOS with the card plugged in. I had to disable wireless in BIOS to be able to install Mojave. Once it was installed, booting Mojave with wireless enabled in BIOS would cause quite severe lag and performance degradation once at the desktop, as if the card just clogged up CPU ressources. This was because I had not applied any particular tuning for the card and, of course, this was resolved once I implemented the necessary fix detailed below. /!\ Searching through the Web for that DW1820A/BCM4350, I came accross a few forum posts/threads that mentionned: rolling back the Yosemite IO80211Family kext to get the card to work, although with instability and regular KPs removing AirPortBrcmNIC plugin kext from IO80211Family kext, patching AirPortBrcm4360 plugin kext with the id of the DW1820A and installing AirportBrcmFixup kext with a couple of parameters (Credits to Hugotai, cf. his post @Voldemort's place, 2nd Dec 2018) Whilst I did not really contemplate doing the 1st thing, I did envisage the 2nd one and started to look at the differences between Yosemite's version of IO80211Family kext and Mojave's. The main difference I had already noticed was that device id 14e4:43a3 was handled by AirPortBrcm4360 up to Sierra 10.12 and by AirPortBrcmNIC since High Sierra 10.13. Further reading and experimenting showed me that AirPortBrcmNIC kext was the root cause of the problem. Building on Hugotai's success, I seeked to work out an easier solution to bypassing AirPortBrcmNIC kext that would not require kext removal and Info.plist patching but, instead, something that could be implemented through hardware properties injection, either through DSDT/SSDT patching or bootloader (Clover or OpenCore) configuration. Once Hugotai's solution was verified and confirmed, I worked out the following Clover-based solution (because that's what I was using) for HighSierra/Mojave: identify the IOReg/ACPI device to which the DW1820A card is attached (use IORegistryExplorer app to that effect). Eg: RP0n@xx,yy->PXSX@0. in the absence of individual ACPI device entry under the PCI bridge for the card, select "FixAirport" ACPI Fix in Clover. That'll create a device "ARPT" @0 under the bridge and that's what you'll inject properties to. This may also require to select "AddDTGP" ACPI Clover fix if your DSDT does not possess any DTGP method. If running with Clover, use Clover Configurator app to that effect. inject the following properties either in DSDT or through bootloader config (latter recommended): compatibility of the card with Broadcom chips 14e4:4353 or 14e4:4331 that are handled by IO80211Family's PlugIn kext AirPortBrcm4360 ASPM disabling (required for most cards to avoid CPU clogging and system freeze) optionally, add SysProfiler's cosmetic info such as PCIe Slot, card's make and model, etc. and that's it ! Nothing to do to IO80211Family kext or its PlugIns which all remain untouched/unmodified/full vanilla in /S/L/E. It really could not be simpler... NB: if your card's country code absolutely requires to be changed, say for full 5GHz/80MHz operations, add the following steps: install AirportBrcmFixup kext in /L/E + repair permissions + rebuild your cache or inject it through Clover's EFI/CLOVER/kexts/Other add boot argument brcmfx-country=XX (where XX is the target value, eg: US, FR, #a, etc.) to the Boot section of your Clover config but, beware, I found that using AirportBrcmFixup (v1.1.9 at time of writing) with country code other than default's US setting of the card impacted my wireless performance (fluctuating and reduced RX/TX rate). For instance, with country code set to FR (for France), I would not connect at 80MHz on my 5GHz Wireless network, only at 40MHz which resulted in a local wireless connection limited to 400Mbps (vs. 867Mbps) and reduced my overall Internet RX rate by about 60% and TX rate by about 10%: with country code set to #a (to get full 80MHz connection), I could not obtain DFS channel mode to my local router and I noticed fluctuating/unstable RX/TX rates: without AirportBrmfixup, my wireless connection runs solid at 867Mbps and SpeedTest returns a solid TX and RX rates at 300Mbps (i.e. the maximum speed of my Internet connection). Properties injection through DSDT: On my laptop, the DW1820A was found attached to device RP03.PXSX located at IO address 0x001C0002, i.e. 1C,2. The DSDT patch required to inject properties could look like this (devices names will differ from one computer to another of course!): Device (RP03) // PCIe Root Bridge { name (_ADR, 0x001C0002) [...] [...] [...] Device (PXSX) // DW1820A card attached to this device (FixAirport Clover ACPI fix required if such device is missing) { Name (_ADR, Zero) [...] [...] [...] Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "AAPL,slot-name", // Optional Buffer () { "WLAN" }, "device_type", // Optional Buffer () { "Airport Extreme" }, "name", // Optional Buffer () { "Airport" }, "model", // Optional Buffer () { "Dell DW1820A 802.11ac wireless" }, "compatible", // Mandatory Buffer () { "pci14e4,4353" // Declares compatibility with BCM43224; "pci14e4:4331" for BCM94331 may also be used }, "pci-aspm-default", // Mandatory for most cards Buffer (One) { 0x00 // Disables ASPM for PCIe device } }) } } } Properties injection through bootloader config: An easier alternative is to inject those properties in bootloader config (for Clover via Clover Configurator app for instance). This can be done within the Devices properties section by injecting the desired properties in the Properties sub-section: In the left part, add the PCIe address of the targeted device in the form PciRoot(0x0)/Pci(<root device address>)/Pci(<actual device address>) In the right part, add the above properties in single lines and with the right types (String, Data, Number) For instance, in the case of my laptop booting with Clover, the target device will be PciRoot (0x0)/Pci(0x1C,0x02)/Pci(0x0,0x0) for PCI0@0->RP03@1C,2->PXSX@0. Then, properties will be injected as lines of keys of 3 x possible types: strings, hex data blocks or numbers. For instance, to declare compatibility with 14e4:4353, the line will consist of Property Key set to compatible, Key Value set to pci14e4,4353 and Key Type set to STRING. The complete properties injection will be: Device = PciRoot(0x0)/Pci(0x1c,0x02)/Pci(0x0,0x0) Key = compatible | Value = pci14e4,4353 | Type = STRING Key = pci-aspm-default | Value = 0 | Type = NUMBER Key = AAPL,slot-name | Value = WLAN | Type = STRING (optional) Key = device_type | Value = Airport Extreme | Type = STRING (optional) Key = name | Value = Airport | Type = STRING (optional) Key = model | Value = Dell DW1820 (BCM4350) 802.11ac wireless | Type = STRING (optional) Once the device properties are injected in bootloader config or DSDT, there's nothing left to do but reboot the computer. The DW1820A card will then be fully active and able to connect to 2.4/5GHz networks at full speed. Results: On the Bluetooth side, once the usual Broadcom firmware patching kexts are installed (eg: Rehabman's BrcmFirmwareRepo + BrcmPatchRAM2 for instance), the BT4.1 module will be fully operational and capable of supporting AirDrop and Handoff! Links: Clover Configurator app Rehabman's Broadcom Firmware patching kexts Acidanthera AirportBrcmFixup kext - - - - - - - - - - Edit: 06 Jan 2020 Updated with freshly found ASPM disabling property injection that fixes all outstanding stability issues. DW1820A #096JNT and Foxconn T77H649 now tested 100% Ok. DW1820A #08PKF4 should be just the same. - - - - - - - - - - Edit: 28 Jan 2020 Finally got to test a DW1820A #08PKF4 and it's also 100% Ok with ASPM disabled.

If you use the VoodooPS2Controller posted in my E6220 Sierra guide, your TouchPad should fully work. It's the kext available in DrHurt's VoodooPS2Controller thread in our R&D->Kexts section. Version R6, compiled by Bronxteck. For Bluetooth and Webcam, please post details (PCI ids) of the hardware. There are 2 x models of Webcam on these laptops and one of them is not supported whilst the other works OOB... Built-in Bluetooth of these laptops usually is BT3.0 DW375 and this is supported natively with some obvious limitations (no support for Handoff for instance). If you want to be able to turn it on and off, you need to patch the Bluetooth Transport PlugIn to inject the DW375 properties in a existing or a new profile. Very common requirements for BT modules.

I had not noticed BIOS A20 had come out. I'm still running on A19 for which I repatched the DSDT to fix graphics corruption rather than stick to version A11 or A12. You'll have to specify your Bluetooth and wifi card(s) model before anything else.

You could, knowing that I never posted High Sierra/Mojave guides for these models because I still use Chameleon but it does not support installations of HS/Mojave. As such, I use Clover to install and update the OS but I still boot with Chameleon. The method used to build the USB installer remains the same but: you install Clover rather than Chameleon at the end files of the /Extra folder go to Clover's EFI folder as follows: DSDT + SSDT into ACPI/patched folder Kexts in /Extra/Extensions go to kexts/Other folder Or you can also follow Jake's guides available here:

Stick to High Sierra on this HD3000 laptop. In addition, 8GB RAM is highly recommended to maximize VRAM and minimize the graphics glitches that I expect you'll inevitably experience over time (eg: lines across the screen, pixel corruption), especially after multiple and extended Sleep/Wake. But apart from that, you'll find that everything works on those laptops. Install a SSD in place of a mechanical HDD and you'll find these ageing E6x20 are great and nippy little things. You may of course use the docking station, knowing that not everything works out of it. You'll find details of patches required for video output ports in various places: