black.dragon74

Where did you verify? Also, You forgot to place VoodooI2CHID in E/C/k/O Why do you have PIN 0x0055 in TPD1 (I had asked you not to do any edits related to I2C controller)

They are specifiers for parent node. We need specifiers for Child nodes (TPD1 or whatever it might be) No. It’s not by manufacturer. YOU HAVE TO LOOK FOR IT IN WINDOWS!

If it is a precision trackpad then it will have the multitouch gestures. If not, you will get basic mouse emulation. Refer to the thread Jake has asked you to and provide the requested stuffs. Haha! It is hell of a machine. Hybrid I2C/PS2 interface along with shared I2C/PS2 interface as if one was not enough to deal with!

No! Need to know if your’s is a precision trackpad or not.

Okay. So I have finished the driver for keyboard. Anyone willing to test may reply (You need to have your keyboard on I2C interface).

You missed the stuffs that I asked you about your machine upon booting Windows. Please provide me with those. EDIT: Furthermore, you have an interesting setup. Your trackpad is on an hybrid interface. So, technically, until a interrupt for I2C is sent, your trackpad will stay on PS2 bus. Hence, you need to boot into windows and tell me the BIOS name of your trackpad as it will be in PTP (precision touchpad) mode under windows. Then, to get interrupt specifiers, you need to boot your machine with VoodooI2C.kext and Windows 10 _OSI patch applied. (No other patch should be applied). I know it's a lot. But it is the only option. Even when you boot without VoodooI2C? EDIT2: Okay. I have some good news. The fact that you mentioned that keyboard stops working once you touch your touchpad helped a lot. You can see (if you have a lil bit of this technical knowledge) that your trackpad and keyboard share a hybrid PS2 and I2C interface. They both have share the same ACPI ID too (PS2K). So, you will need to have an I2C driver for keyboard too. Which doesn't exist. But, the good news is I am already working on it and will try to complete it ASAP. There is one barrier in the way i.e. I don't have any hardware to test it on. So, you will need to be around for the testing. Please PM me and then we can take it on from there. Regards

Well, those files are old and you've already tried with them. See that above mentioned thread and answer the questions I have asked. Then, I need you to remove VoodooI2C and then run my debug script and post the output here.

Also, Jake, is this the user you were assisting?

EDIT: I need you to boot into windows and tell me a couple of things I need to know in order to help you! Is your's a precision touchpad? (Settings > Devices > Touchpad look at the top) BIOS NAME for your touchpad. Also, of the two DSDTs you tried, which one worked (sort of) for you? 0x1b or 0x7b? Regards

Hey! Sorry but your IOREG is corrupt. (weird that your IORegistryExplorer.app passed the check for version 2.1 in gen_debug) I am seeing that quite often. Guess there is some version of IORegExplorer floating around that pretends to be ver2.1 but is actually not. Anyways. Please delete the IORegistryExplorer.app from /Applications folder and then, re-run the script. It will automatically download the correct version for you. Also, have you tried patching yourself? If yes, how far did you manage to go? EDIT: Never mind. I have pushed an update for gen_debug (ver2.4.2) that checks for IORegistryExplorer in a different way. So, just update your copy and it will do everything auto-magically. Regards

Please stay away from using swap file on an SSD as continuous read/write will lead to wearing of the flash memory. Upgrading RAM will be a better choice as using swap file on some other partition will not be that fruitful.

Finally it's here. If there are no ACPI/origin files or if they are older than 1 day. User will have to dump them again. P.S: OSX's "date" is such a headache to work with. GNU date is more simpler. Regards

I am planning on doing something that takes care of it automatically. I and RehabMan are trying to implement a feature that will dump ACPI files automatically if there exists a specific key in config.plist (this may take a while). Until then, I am writing a function which asks user to reboot and press F4 if the origin ACPI files are non existent or older than 1 day. (will finish it today, maybe.) Regards

Hey fellas! I have added experimental support for Chameleon or similar bootloaders. Can someone test it out and confirm it for me (via DM or here)? To test, update gen_debug manually by using: gen_debug -u as I have not pushed the update for everyone yet! Regards

Chrome is a memory hungry app. All macOS version till date tend to work fine with just 4 gigs of RAM until you plan on doing something very intensive (video editing and rendering). Also, in my opinion replacing standard HDD with an SSD should be preferred more over a RAM upgrade. Regards

Yes it will as the system requirements are same (almost) for Sierra and High Sierra.

You created DSDT for USB? I guess not. You need a custom SSDT to use in conjunction with USBInjectAll.kext for proper functioning of USB on macOS 10.11+

A generic log in dumped by gen_debug if the IOREG dump fails after increasing the save times thrice. There could be various reasons for that. Maybe user has some fancy files/folders (files that are not really AML opcode but are in AML format) in CLOVER/ACPI/patched (this is one known issue) However, I can see user saying: FaserF, could you please send me a screenshot of what happens when it (gen_debug) tries to dump an IOREG. Maybe I could then work on fixing it. Cheers!

Hey fellas, I have seen that quite a lot of you are struggling to get your trackpad working while using VoodooI2C kext. That's probably because you are unable to do the GPIO pinning which is needed in 99% of the cases. Although, I am busy due to my exams I will try to help you with the patching in whatever free time I can manage. Here's what you need to do in order to file a request: Press F4 at CLOVER boot screen. Attach output of https://osxlatitude.com/index.php?/topic/10209-how-to-generate-proper-problem-reporting-files/ Info about your processor (generation) Have you tried patching yourself. If yes, how far have you come? Note: DO NOT FORGET TO PRESS F4 AT CLOVER BOOT SCREEN BEFORE RUNNING MY SCRIPT. Regards

That's because not all Dell's support hybrid interface (both PS2 and I2C) for trackpad. From VoodooPS2 log it is quite clear that your trackpad is unsupported via PS2 bus. You can only use VoodooI2C. Regards

Coz, ApplePS2SmartTouchpad expects different EC Query methods to be executed. See https://osxlatitude.com/index.php?/topic/7890-how-to-fix-your-acpi-brightness-keys-using-smart-touchpad-driver/

Attach proper problem reporting files. See How to generate proper problem reporting files

You are expected to ignore this.

You need to create a custom SSDT for proper functioning of USB. Also, AptioMemoryFix is preferred instead of OsxAptioFix* (brings native NVRAM functionality)

If your vendor is ASUS, upload your native DSDT here, untouched. (Press F4 at CLOVER boot screen). P.S: If by newer you mean upto coffeelake(8th gen), it is working in my case (Vivobook S15). Regards