Jake Lo

ok, can I assume you got it figured out or you need help with it? Are you installing Sierra?

it depends on the system where the location is, not the drive brand. did you find something similar as the user, please post screenshot. Use the "More Reply Option" on the lower right to attach rather than using external link

try looking through all the option in detail..should be there. Looks similar to this _SB_.PCI0.RP09.PXSX

You need to copy the patched kext + ssdt-nvme-pcc.aml to the installed drive EFI partition. Make sure to add the ssdt-nvme-pcc.aml to the ssdt sortedorder of the Config file.

??? What happened after reboot?

the newest is 1.5.3 not 1.4.3. Can you confirm? http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=F29XW&fileId=1962738623&osCode=WT64A&productCode=latitude-14-5480-laptop&languageCode=en&categoryId=BI

Are you having problem booting the USB installer or the USB installer is not seeing your NVMe drive? If the latter, then yes. Once you have created the patch kexts for the version of OS X you're installing + the SSDT-NVME-Pcc.aml added to the installer, NVMe drive should be visible.

if Bronxteck's advice doesn't work, then try this config file Config.plist.zip

Ok, we have established that you want to install to an m.2 Samsung NVMe 960 EVO. The youtube video is old and incomplete. If you have follow the guide correctly, you'll need the patched kext and SSDT-NVMe-Pcc.aml. You'll need to determine the path to which your NVMe drive is installed. You'll need windows for that part with the NVMe drive installed. From Windows, go to Device Manager, go down to Storage Controller and expand. You should see Standard NVM Express Controller, right click and select Properties. Then click on Details tab, look for "BIOS device name" under Property. You'll see the path found under "Value".

There are 2 duplicate tables in the folder, might be corrupted. Can you clear the Origin folder... Reboot and re-extract the files and attach it here again. You can use the More Reply Options on the lower right to attach the folder here instead of using external storage site

What version of BIOS are you running? I'm reviewing your Config file and noticed you don't have kext-dev-mode=1 enabled. You usually need that to run un-signed kexts.

Which bootpack did you use? If you're using any of the bootpack E6430 or E6530_HD4000_Only, there's a boot arg to disable the Nvidia card (nv_disable=1), hence you're able to get to the desktop but without QE/CI because Nvidia kexts are not loaded. If you remove that arg from boot, you won't be able to get to the desktop and hang at loading the nvstartup. If you follow the guide I linked, FrostytheSnowman mentioned he got both graphics working but I have not confirmed it.

Which card are you seeing having the artifacts? HD 4000 or NVS5200m? Do you have Optimus enabled or disabled? I think the artifacts you're having is due to BIOS version. For this model, if you're using the HD4000, you need to be on A13. If you have anything over, you'll need to downgrade to A03 and then upgrade to A13. With A13, the BIOS setting won't reset if you have Optimus enable/ on restart, it'll stick. With other BIOS version, A11 or A12, I believe it'll automatically switch to Discrete after each reboot.

File structure looks fine. This is from the AMD guide you linked? Post # 9 is for M.2 NVMe drive, you mentioned your drive is M.2 SATA SSD right?

Audio should work if you follow the post installation part. Did you copy the kexts in /EFI/Clover/kexts/Other/LE to /Library/Extensions, repair permission and rebuild cache? Make cache building is successful. As for the Nvidia, I don't have a bootpack for that. See this guide instead.

Here patched for A12 3446_A12.zip

Compress and attach /EFI/Clover/ACPI/Origin folder here

Can you try using the kexts from E7x70 but replace the DSDT/SSDT and Config file?

does the Fn+F5 and Fn+F6 Brightness key work ?

what version of BIOS? Specs same as OP?

the attach ioreg and sysREport is from without patch DSDT/SSDT Try new bootpack then send me new sysReport and IOREG R510VX-3.zip

Can you use an USB keyboard/mouse during boot, and select F4 from the USB keyboard? Then check to see if there's file in the /EFI/Clover/ACPI/Origin folder after you boot up to MacOS. It probably just need a patch to get them working.

Hmm, strange. Let me check the patching again. Update: Try replacing with this DSDT. The rest stays the same DSDT.aml.zip

You can boot to Clover right? At the Clover GUI, hit F4. Then go to Options, use the right arrow to navigate Select ACPI patching-> Tables Dropping-> Go all the way down and deselect Drop all OEM SSDT Check all the Drop "SSDT-xx" below that Select Return Change DSDT name: BIOS.aml or anything other than DSDT.aml Select Return, Return Hit spacebar to select Verbose mode Select boot with selected Options What the above does is to not use the patched DSDT/SSDT

You could follow my Clover guide and use the bootpack from this post