Bronxteck

try pointing the boot path to the oc binary not the bootx64 also make sure you dont have an efi folder within the efi folder.

https://www.insanelymac.com/forum/topic/339830-dell-monitoring-by-smm-and-fan-control/ there is also https://github.com/acidanthera/VirtualSMC/tree/master/Sensors/SMCDellSensors

glad it worked.

if it is IDT92HD91BXX try id's 12,13,33 or 84. if that is not good enough do as Herve says and just use voodoohda.

have you tried agdpmod=pikera instead of agdpmod=vit9696

you need to clear nvram.

try different values of finger z and see if it gets better or worse so if 10 is harder and 99 is faster or not if nothing changes then issue may lay in some of the other values.

try Dr.Hurts suggestion "Try editing the plist of R2RC with fingerz=30, scrollresolution & resolution=400, divisorx, divisory=2"

try modifying the finger z value in the trackpad kext plist file.

what happens if you close the screen and open it again after it blacks out on the main screen? if you shine light on the screen do you still have images showing but with no backlight?

nope nothing i could do off hand. most likely a BT firmware compatibility issue.

sometimes the installer reboots 3 to 4 times before installing. have you waited that long? no i did not watch the video.

you can run the config validator to see what needs to be fixed in your config. should tell you the errors. then you look in the sample config to see how it is now implemented as things change in OC on a monthly basis. make sure all acidanthera kexts are also updated with the same version of OC that is installed. simpler to update to newest stuff since it gets hard tracking what goes with what version.

have you checked the manufacturer to see if it has apple compatible software? usually in the past many csr devices where natively supported.

try resetting nvram in case there are some rough values from the old EFI

it might be trying to update the non existent apple mac firmware. if using OC there is option to not allow it as we do not need that on a hack. i don't recall what it is off the top of my head but it's in the OC documentation.

glad to see your up and around. hope your better after your last scare.

welcome.

you can try layout id 13 and 29 they seem to be for a asus x55 system

reset nvram.

it is not that it is impossible. it is just that none of the devs that would have the skills to code for it have the machine. necessity is the mother of invention.

most likely has to do with filevault. or BT see if you can disable any new vault related features can try with man pmset or pmset -g log to see what is going on

try id 66

panic shutdown info is stored in nvram that's how it knows your previous shutdown was not successful.

clear nvram.