Hervé

Readable details of specs are missing so here they are: Intel dual-core Kaby Lake-U/Y i7-7500U @2.70GHz (Turbo boost up to @3.5GHz) Intel HD Graphics 620 (PCI id 8086:5916) 15.6 built-in LCD Full HD @1920x1080 or HD @1366x768 ? 4GB DDR4-2400 Realtek RTL8101/2/6E Gigabit Ethernet (PCI id 10ec:8136) Qualcomm QCA9377 802.11ac Wireless LAN (PCI id 168c:0042) Audio ? USB ports ? Video outputs ? Card reader ? Webcam ? Note that the Qualcomm WLAN card is unsupported and will have to be replaced by a supported model or USB dongle. See our FAQ section. I recommend you lookup the other Inspiron 5570 threads in this section, many contains useful info + copies of Clover setups. You can use the forum Search facility if required.

No, if only if were just that! There are many many mistakes and missing items with your Clover setup (config + kexts). Try the attached instead: CLOVER.zip

Last update: 29 Mar 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 HD4000 graphics (with Lilu v1.3.7 + WEG v1.3.0) multi-display with HDMI OOB audio, including jack microphone input and headset output (with AppleALC v1.3.9 & layout 12 + CodecCommander v2.7.1) HDMI audio (with Capri Framebuffer patch) built-in GigEthernet LAN connection (with AppleIntelE1000e v3.1.0 or latest IntelMausiEthernet kext) wireless and bluetooth with any compatible card integrated webcam (OOB) full CPU power management, including Turbo boost (with CPU-specific generated ssdt) sleep (Lid, Energy Saver settings, Apple menu, Fn-F1, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) SD card reader (with DSDT patch for compatibility with Apple's default reader) keyboard (with Dr Hurt's VoodooPS2Controller R6 + DSDT patch for brightness control) touchpad including tap-to-click (with Dr Hurt's VoodooPS2Controller R6) left combo eSATA/USB2.0 + right USB3.0 ports (with Hackintool's generated USBPorts + Rehabman's FakePCIID kexts for multiplexing) ExpressCard slot OOB Not working: VGA output unsupported Not tested: SmartCard reader fingerprint scanner GeekBench v2.4.4 (32bit) gives a slightly improved 8100+ rating: 1) 10.14 USB installer creation Using a USB key of 16GB 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_16GB) The process will take several minutes. Once completed: Setup your BIOS for UEFI mode 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 DataHubDxe FSInject SMCHelper ApfsDriverLoader AptioMemoryFix Fat PartitionDxe Ps2MouseDxe UsbMouse.Dxe VBoxHfs Themes (optional) Install Clover Preference Pane (optional) you may use version r5035 attached below: Clover_v2.5k_r5035.pkg.zip once Clover is installed, run 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 Latitude E6230 Mojave Clover pack below to the EFI/Clover folder: E6230_Mojave_pack.zip E6230_Mojave_pack_#2.zip E6230_Mojave_pack#3.zip E6230_Mojave_pack_#4.zip if your E6230 is fitted with a different CPU than those cared for in the bootpack (i5-3340M/i7-3540M), remove the SSDT.aml table from Clover's EFI/Clover/ACPI/patched folder (default table is for i7-3540M); you'll generate you own CPU-specific power management table in post-installation phase. 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 E6230 Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots off your disk through Clover If your E6230 is fitted with a different CPU than the models stated above, download Pike R Alpha's SSDT generator tool and generate your own CPU-specific SSDT. Copy the resulting SSDT.aml file to Clover's EFI/Clover/ACPI/patched folder. - - - - - - - - - - Edit #1: 16 Aug 2019 Updated pack #2: revised patched (A19) DSDT to fix to a small coding error causing issues with battery monitoring. - - - - - - - - - - Edit #2: 20 Aug 2019 Updated pack #3: added the USBPorts kext I had forgotten in pack #2. - - - - - - - - - - Edit #3: 29 Mar 2020 Updated pack #4: fixed a small copy/paste mistake in HDMI audio patch in pack #3.

Reserved High Sierra

RP05.PEGP is initialised in table SSDT-9-SgPch.aml: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (Zero, \_SB.PCI0.RP05.PEGP._ADR) } This is where you would normally add the _OFF () command: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (Zero, \_SB.PCI0.RP05.PEGP._ADR) External (\_SB.PCI0.RP05.PEGP._OFF, MethodObj) _OFF () } And in DSDT, you could adjust Method _REG as follows: Method (_REG, 2, NotSerialized) // _REG: Region Availability { If (LEqual (Arg0, 0x03)) { Store (Arg1, ECFL) } If (LAnd (LEqual (Arg0, 0x03), LEqual (Arg1, One))) { ^^^PEG0.PEGP._OFF () } If (LAnd (LEqual (Arg0, 0x03), LEqual (Arg1, One))) // Added test to disable dGPU device RP05.PEGP { ^^^RP05.PEGP._OFF () } } If you want, give those revised tables a go: DSDT.aml.zip SSDT-RP05.aml.zip

Ok, perfect. This confirms that the nVidia GeForce 920M is attached to RP05.PEGP (or RP05.GFX0 once device is renamed by Clover) located @1C,4. I also see that, in SysInfo->Software->Extensions, the Nvidia drivers loaded for this Kepler dGPU: We can now try and disable the dGPU properly.

@ftrela, could you please: remove that SSDT-Disable-DGPU table reboot the laptop save an output of SysProfiler/SysInfo + IORegistryExplorer and post a zipped copy of them dGPU definition and controls will be in the following tables: DSDT.Aml SSDT-8-SaSsdt.aml SSDT-9-SgPch.aml SSDT-10-OptTabl.aml It's important to identify the correct device used for the dGPU in order to try and disable it properly.

To me, there is something weird on your system... You obviously aim to disable your GeForce 920M (Kepler) dGPU through that SSDT-Disable-dGPU table. You quite rightly rename PEGP device to GFX0 in your Clover config. Looking at your extracted tables, the dGPU could be believed connected to root device PEG0.PEGP @1. But then, in IOReg, I see that dGPU active under root device RP05 @1C,4. We would need to confirm what is what through an IOReg extract taken without any DSDT/SSDT patches affecting or aiming to affect dGPU. I also derive from your IOReg that you're using Clover config called "config.plist" which sets SMBIOS to MBP12,1. The only other SMBIOS you could use for your Broadwell platform would normally be MBA7,1 or MBA7,2, not MBA6,2 which is Haswell... Can you please explain what you patched in your DSDT?

What about those "GraphicsPolicy" patches you've got configured in Clover? Tried to see how wake behaves when you remove them?

Try and wait something like 5mins after you wake the laptop. I had a similar issue on my E6440 and it was due to the number of ports in the Azul framebuffer and their re-initialisation on wake or something like that. Initially, the laptop would wait to a black screen which would only lit after several (long) minutes.

Try a low level format with HDDGuru's tool from Windows (or a PC with Windows) to completely wipe out all the partitions and be able to start 100% afresh with it.

Installed DP #1 on the E6230 and updated straight to beta #5 through Software Update (did not have to go through all intermediary versions! ) All that was required for beta #5 was to add the ACPI renaming required for embedded controller, i.e. rename ECDV to EC. This is a straight hexadecimal ASCII definition in Clover config ("ECDV" -> "EC__"). All the rest is identical to Mojave, just with the latest versions of add-on kexts (Lilu, WEG, etc.).

Probably results from one (or several) of those ACPI renaming/fixes you implement. Try without the renaming _DSM to XDSM. Bur keep a backup of your current Clover config that you could manually recall from Clover main menu of course (use a name like config_bak.plist for instance or call the test config config_test.plist)! NB: IOGraphicsFamily patches should no longer be necessary with WEG. The 1st one (75 25 to EB 25) is obsolete for sure.

Sure does; do you actually have anything reported under SysProfiler->PCI ? Post a zipped copy of your Clover config.

The card can only get listed in the SysProfiler if the specs/info are injected properly (eg: DSDT patch or Clover device properties injection).

WWAN modules are USB-based. Until you get all your ports working, including the internal ones, nothing you could try to get the WWAN working will succeed. Once you see the module listed under SysProfiler->USB, you'll know it's detected and available for tuning. Consult the existing E7470 guides/threads/posts to get all your USB ports working.

It was all explained here:

If you experience KP, there's a high chance that you've reverted to an older wireless kext from Yosemite. It's actually a bad idea and, given the impact, it is simply not sustainable. If you cannot get your DW1820A to work, demand to return it to the seller especially as the MAC@ does not match the label... It's a fake OVW3T3.

It would seem you still haven't installed CodecCommander, so... once you add it, things may begin to work properly...

Why don't you remove the BrcmAirportFix kext + Clover associated options ? You could also try to declare compatibility with 14e4,4353 instead of 14e4,4331 though it really does the same. Post your debug package.

You're confusing things and are mistaken re: PCI ids. You need to read my guides with more attention (especially the 1st post). In a nutshell, the intel audio device is the controller and Realtek is the audio codec. When I said "add-on kexts", I meant all the kexts you use for your Hackintosh, those provided in the bootpack.

Check that the Wifi card is listed in Network PrefPane. If it's not, try and add it manually.

If you've not done it, install the add-on kexts in /L/E, repair permissions and rebuild your cache.

None whatsoever; if you've installed the kexts + config I provided, all should work. The only thing to note with audio is that, sometimes, after waking the laptop, audio is corrupted. It takes a new sleep/wake to recover.

'means you need to adjust the USB port definitions and/or settings. You can use the patcher tool to create the appropriate USBPort kext. Did you try rehabman's USBInjectAll at all?