onemanosx

That error has nothing to do with graphics. Choose a different aptiodriver

Boot with -v and take picture

add -v in boot arg to see what is causing the problem. I am also not a fan of installing kexts in S/L/E or L/E. Use only clover/kexts/other folder for its purpose. Download a generic clover folder here and use it as well https://Olarila.com/files/Clover.Folder/CLOVER.NOTEBOOKS.100.200.300.zip. Upon reboot, generate a new RunMe file.

Maybe read post #1?

see mald0n's post https://Olarila.com/forum/viewtopic.php?p=79832#p79832

[ref]niteman1969[/ref], boot only with these files. see if works. Archive.zip

Similarly, we need to know touchscreen hardware details. I think [ref]erroruser[/ref]'s touchscreen is a USB device? And thats easy to configure.

if its there, though. Best to google from manufacturer's spec. Not many card readers are supported in hackintosh.

[ref]FCU4ever[/ref], a new post, I see Anyway, a post like this without details of your card reader chipset will be of no help.

[ref]FCU4ever[/ref], maybe you need to mod the AsusFN kext plist. I cant help with that. Never used it. On a good note, the slider and brightness keys are working though it didnt change the brightness

[ref]FCU4ever[/ref], similar patch as in your dsdt Add this patch to the latest DSDT that I had uploaded and remove AsusFN kext from your S/L/E or L/E or Clover/Kexts/Other. Rebuild permissions and reboot. (might also need to rebuild permissions again and reboot 2nd time) into method label _Q0E replace_content begin // Brightness Down\n Notify(\_SB.PCI0.SBRG.PS2K, 0x0205)\n Notify(\_SB.PCI0.SBRG.PS2K, 0x0285)\n end; into method label _Q0F replace_content begin // Brightness Up\n Notify(\_SB.PCI0.SBRG.PS2K, 0x0206)\n Notify(\_SB.PCI0.SBRG.PS2K, 0x0286)\n end; In some cases, slider wont adjust brightness. But working FNkeys will adjust the brightness accordingly. If this doesnt work, then I dont know.

[ref]FCU4ever[/ref], no idea since i never used asusFN kext. I had a working slider and Fn keys just by using voodoops2controller and dsdt patch for my old laptop with nvidia graphics http://Olarila.com/forum/viewtopic.php?f=28&t=8768

DSDT.aml.zip

[ref]FCU4ever[/ref], can you also attach your runme files?

https://github.com/RehabMan/OS-X-BrcmPatchRAM

Need to check your osi patch or ssdt has windows patch. I also took a look at your clover config and found there are multiple hot patches for battery status. Remove all hot patches concerning battery and try again. Can you generate fresh ACPI tables by pressing F4 at clover bootloader and upload clover/acpi/origin folder?

[ref]niteman1969[/ref], 1. Place DSDT.aml in Clover/ACPI/Patched 2. Remove SSDT-BAT and SSDT-BATC 3. Reboot and see if battery works. DSDT.aml.zip

So, what just happened here? What does new ioreg shows for i2c device?

if your debug patch are done correctly, you can also use these codes in terminal log show | grep -i acpidebug

[ref]FCU4ever[/ref], if you are using RH brightness kext and ssdt, you are able to adjust the intensity of brightness. But I have not looked into that.

[ref]FCU4ever[/ref], unlikely.

for the sake of interest. Remove all trackpad related kexts or ssdts and use only voodooi2c and voodooi2chid kexts. Reboot. Rebuild permissions and reboot again. Run and Upload runme folder. Thx.

[ref]Wizzard[/ref], read edited reply above your last post.

Actually, the infos are all there for you to read. You can check in Windows or follow the procedure to check in ioreg. https://voodooi2c.github.io/#GPIO%20Pinning/GPIO%20Pinning