ufdlim

Doesn't look like my /EFI has a nvram.plist? Turned on hidden files as well. Tried clearing nvram with Terminal "sudo nvram -c" from single user mode. Also rebuilt cache. I think I'll probably be resigned to having this at full brightness! Ha... Thanks for your help Jake!

Gave that a try without success - kept all kexts from the bootpack in E/C/k/Other and only those 4 along with the normal macOS kexts in L/E. Still stuck on full brightness. Its interesting because during the boot process I'd say the brightness is around 50% - it is not until loading the UI does it max and stay at 100%.

No idea why that was the case - seemed to be missing entire clover folder too. See updated attached. Yes, using Karabiner. Used to using F11 and F12 for Show Desktop and Dashboard, respectively. Using F5 and F6 instead. However, same effect using Karabiner and slider, 100% then blackout around 10 or 15% brightness. Thanks for your help Jake! debug_16936.zip

@Hervé Yep - you're right. After replacing with a DW1830, Wi-fi worked out of the box. The only other noticeable issue I seem to have is that the backlight control doesn't really work it. The brightness is basically 100% until you get to around the 15% mark, in which case anything less results in flickering until fully dark at around 5%. I have SSDT-PNLF.aml in EFI/ACIP/patched, the AppleBacklight patch for "change F%uT%04x to F%uTxxxx for AppleBacklightInjector.kext (credit RehabMan)", and AppleBacklightInjector.kext in L/E. I don't have IntelBacklight or ACPIBacklight anywhere. Kextcache has already been updated. Looks like the fix might involve modifying PWMMax or EDID patching? EDIT: Clover detected EDID so I tried injecting product-id 0x9c7c without success.

Doubled checked, definitely DW1830. I'm thinking the sticker is wrong because it is a Atheros vendor ID and not Broadcom at all. Ordered a real DW1830.

@Jake Lo Worked beautifully! Booted, installed, and installed locally perfectly. System sleeps and wakes from sleep just fine. Sound works great. Able to get a working dual boot with Windows 10 as well.Thanks so much! Still need to do the post-install Karabiner. Wi-Fi doesn't work but I'm not surprised because its 168C:003E, which is an Atheros card I've not seen compatible anywhere. Weird because the sticker on the actual card says its a DW1830.

@Allan Noted the config was using "detect", which I then updated to "Yes" without any apparent success. Thanks for the suggestion! @Jake Lo Sorry about that, that must have been me mashing F4 in Clover because it doesn't give a status. Attached updated origin. Hopefully this one is a bit better... origin-updated.zip

Hey Bronxteck - thanks for the suggestion. I noticed they were already in my e/c/k/o folder but went ahead and updated them to their latest releases. However, I am still stuck - seemingly randomly at this point. Also, I apologize - realized i put this topic in the Guides forum. Please move or I can delete and re-post.

I've tried all night reading through the forums and the guide to try to boot the High Sierra installer without luck. I've followed the guides at Dell Latitude E7x70 - Clover UEFI Only and Dell Latitude / Inspiron / Precision / Vostro / XPS - Clover Guide for creating the install media, installing Clover, and replacing (not merging) the generic EFI and high sierra bootpack. Things to note: I did not do not set DVMT to 96MB (0x3) - according to FireWolf's guide DVMT needs to be 96MB or more and I see it is 128MB in Windows. Or am I misinterpreting the need to do this? Specs: Core i5-6300U, 8GB DDR4, Intel 520 graphics, 1080P matte non-touch, 256GB Hynix SC308 M.2 SSD (non NVMe), Broadcom Atheros QCA61x4A WLAN (although when I opened up the laptop, it says this is a DW1820 chip; its okay if I don't have wifi, ethernet is fine), Intel I219-LM ethernet, fingerprint sensor, and NFC device BIOS: 1.19.4 BIOS settings: BIOS defaults, then TPM = Disabled, Secure Boot = Disabled, UEFI = Enabled, SATA = AHCI, = Wake on LAN = Disabled, and Legacy ROM = tried both Enabled and Disabled Clover settings: UEFI booting only, Clover in the ESP, add AptioMemoryFix Step considered: Clover R4586, replace generic EFI, add E7270 bootpack - stuck at "creating RAM disk for /var/log" (consistent) Reset /EFI, Clover R4558, replace generic EFI, add E7270 bootpack - random freeze at various points Replaced AptioMemoryFix with AptioMemoryFix-64 at some plint - didn't work Reset /EFI, Clover R4586, replace generic EFI, add E7270 bootpack, replace patched ACPI from various forum posts: 1, 2, 3 - random freeze at various points Was reading that the bootpack might have some outdated files, so - Reset /EFI, Clover R4558, generic EFI, E7270 bootpack, upgrade to Clover R4586 - stuck at "restore environment starting" (see image below) What am I missing? The DVMT fix? Attached is my origin dump from Clover. Thanks for any help! Origin ACPI files: origin.zip CLOVER folder: CLOVER.zip