Jake Lo

It's Jake...by the way. Anyway, please post an IOReg file while the HDMI display is connected. Use IORegistryExplorer.app v2.1 not 3.0+

Who is Jack? Open the Config file under DeviceProperties/Add/PciRoot(0x0)/Pci(0x2,0x0) Change all framebuffer-con1-* to framebuffer-con2-* Save and test after reboot

Is it that hard to find?

Try switching VoodooPS2Controller with Dr. Hurts' version compiled by Bronxteck. I'm assuming you mean Intel Wifi since I don't have this issue on my DW1820A. Probably a good idea to switch it with a more supported card since Intel is still in it's developement stage.

@ONRA You haven't confirm what touchpad you have, is it indeed an I2C Alps? Most new Dell Latitude I worked on has I2C Alps but never heard such strange behavior. Perhaps it's a new variant of the I2C Alps and it's not quite supported yet. You can try contacting the developer for help. @KeinOhrHasen I guess you'll have to swap out with a spare SSD to test. Others in this thread didn't have such issue but I don't know what disk model they have. They will have to chime in.

Try adding SSDT-TPDX.aml. Should be in my attached file

Yes, and can be deleted from the Config file as well. VoodooPS2Controller has VoodooInput as a plug and so does VoodooI2C. Haven't boot enabled will cause boot issue, hence one is disabled. You may enable VoodooPS2mouse and trackpad, see if it'll make a difference. The other VoodooI2C satellites are not needed since your system has an Alps I2C touchpad so only need one satellite kext - VoodooI2CHID.kext. I might be wrong, so you'll have to check your system what touchpad it has. If it's a synaptics, you should use VoodooI2CHID as well, for Elan, use VoodooI2CElan...etc etc etc.

@ONRA Did you remove / disable the DSDT-Patched.aml and test again? According to your IOReg file, I2C kext is loading and working. @KeinOhrHasen Try removing the drive 1st and see if it'll boot all the way with the USB Installer just to confirm. All Sata SSD are supported. If you want NVMe, most Samsung are supported aside from PM981, PM981a, PM998, Micron 2200s. See here Before ordering it, do the research. See if others have issue with it on Hackintosh.

did you test disabling the WD drive? I believe the issue with with the NVMe drive.

Yes, run ProperTree and do a snapshot to add the new kext. I don't use it personally, I just Plistedit pro to manually add it.

Try adding NVMEFix.kext, if it still hang, I would consider replacing it. You can also try disabling the drive to see if the installer will boot all the way.

@KeinOhrHasen What model is your internal drive? Some NVMe drive like Samsung PM981 and PM991 are known to be incompatible with MacOS.

Remove the DSDT-Patched.aml. It's for Murkie's 5410 and I don't know what patches are applied on it but could cause havoc on your 5510.

@ONRA Please post your most recent files + IOReg file Remove the SSDT-DGPU.aml if necessary for screen to come on

check the BIOS to see if BT has been enabled if it exist Try resetting NVRam from OC Picker

@vjiethoang Are you sure the SSDT-TYPC is correct for your system? Please post IOReg file using IORegistryExplorer.app v2.1 not 3.0+

I'm not sure if the Intel Wireless supports SideCar. You'll need to do the research.

@ONRA Is there an option in the BIOS to enable Optimus under Display?

Did you try the file I attached here ? or maybe try to integrate or adapt some of the stuff from it? I should include touchpad, sdcard reader, HDMI, sleep / Wake You'll need to add an SSDT-DGPU.aml to disable the DGPU, since it's not supported and will cause extra battery draining.

For graphics, try Add deviceID = 9B3E0000 For keyboard, add VoodooPS2Controller.kext For Touchpad, remove VoodooI2CElan, doubt your Dell's touchpad is Elan, most likely it's Alps. Replace it with VoodooI2CHID.kext

IOReg file is corrupted, can't open it. Try using IORegistryExplorer v2.1, not 3.0 Audio should work with layoutid=3, try adding CodecCommander.kext. AppleBacklightFixup.kext is integrated into WEG, so you can eliminate that. Wifi, make sure you have the correct version for your version of MacOS. BT, make sure it's detected under USB, if not, fix your USB ports.

Ok, you mean verbose mode. Yes Resetting NVRam would do the trick if you don't have it set in the current Config.

What is "Boot Scroll"?

You'll need to post your system's full specs before we could help you.

add to boot arg -igfxvesa -v