New XPS 15 (9560) compatibility?

[RehabMan]

I tried enabling that but it locked up all input probably because it tried to call initTouchPad() too many times like you mentioned.

Yes...the code is disabled for good reason... As I mentioned, it is not done.

I included patchmatic files from today in the previous zip but here's one containing the Clover f4 extracted files.

I wanted to compare native ACPI with patched ACPI.
Your patched ACPI files are out-of-sync with native.
Different SystemMemory addresses in the SSDT package in SSDT-4.

 

[freejack]

I wanted to compare native ACPI with patched ACPI.
Your patched ACPI files are out-of-sync with native.
Different SystemMemory addresses in the SSDT package in SSDT-4.

I extracted them again. Do they look ok now? Only origin and patchmatic ACPI files in the attachment. Thanks.

 

[RehabMan]

I extracted them again and the SSDT-4 addresses are still different after patching. Is that not supposed to happen? See attachment. Only origin and patchmatic ACPI files in the zip.

They will not be the different if you patch based on a recent extract (eg. ACPI/patched content based on ACPI/origin).

 

[freejack]

They will not be the different if you patch based on a recent extract (eg. ACPI/patched content based on ACPI/origin).

Can you look at the files I attached in the previous message? The origin files were just collected and patchmatic extracted right after booting.

@RehabMan are you talking about these differences? I've extracted from clover and immediately used patchmatic after booting to pull the post-patch ACPI files. There's always this difference. Regardless, I don't think this is what's causing the trackpad issues could it?

J-MacBook-Pro:troubleshooting j$ diff patchmatic_extract/SSDT-4.dsl CLOVER/ACPI/origin/SSDT-4.dsl
8c8
< * Disassembly of iASLfeiE2k.aml, Sun Feb 19 19:48:17 2017
---
> * Disassembly of iASLgoOL8B.aml, Sun Feb 19 19:48:24 2017
14c14
< * Checksum 0xD0
---
> * Checksum 0x2C
48c48
< 0x785D5E18,
---
> 0x785D3E18,
51c51
< 0x773D0198,
---
> 0x78635C18,
54c54
< 0x76725A18,
---
> 0x785D3C18,
57c57
< 0x76725818,
---
> 0x785D5E18,

 

[freejack]

Here's a version of voodoops2controller where you can press the prtscr button to get the trackpad back again. Based on suggested edits by rehabman. I've tested it and it is able to restore trackpad functionality every time.

 

[RehabMan]

Can you look at the files I attached in the previous message? The origin files were just collected and patchmatic extracted right after booting.

@RehabMan are you talking about these differences? I've extracted from clover and immediately used patchmatic after booting to pull the post-patch ACPI files. There's always this difference. Regardless, I don't think this is what's causing the trackpad issues could it?

J-MacBook-Pro:troubleshooting j$ diff patchmatic_extract/SSDT-4.dsl CLOVER/ACPI/origin/SSDT-4.dsl
8c8
< * Disassembly of iASLfeiE2k.aml, Sun Feb 19 19:48:17 2017
---
> * Disassembly of iASLgoOL8B.aml, Sun Feb 19 19:48:24 2017
14c14
< * Checksum 0xD0
---
> * Checksum 0x2C
48c48
< 0x785D5E18,
---
> 0x785D3E18,
51c51
< 0x773D0198,
---
> 0x78635C18,
54c54
< 0x76725A18,
---
> 0x785D3C18,
57c57
< 0x76725818,
---
> 0x785D5E18,

Yes, those are the differences. It is because your content in ACPI/patched is not in sync with recent extract via Clover F4 in ACPI/origin.

 

[freejack]

@blazinsmokey Alright, if you want to be a guinea pig, I've got a modified driver here that auto inits when a bad byte is detected. I've been testing it myself and it can confirm that it's doing what it's supposed to. Just two lines of code changed.
The cursor will pause for a fraction of a second as the driver reinits but I believe it's still better than manually pressing prtscr.

Good luck.

Edit: Updated with release version and a minor timing change that makes the reinit almost unnoticeable.

 

[blazinsmokey]

@blazinsmokey
Edit: Updated with release version and a minor timing change that makes the reinit almost unnoticeable.

Wow appreciate the effort in trying to find a solution. Just tried it for the past 5 minutes and I think my trackpad dies so frequently and fast that while it does work, it's giving me a hard time to navigate. It skips around a bit on me, better than nothing though.

What files does rehabman need to look elsewhere or is alter the drivers are only hope?

 

[RehabMan]

Wow appreciate the effort in trying to find a solution. Just tried it for the past 5 minutes and I think my trackpad dies so frequently and fast that while it does work, it's giving me a hard time to navigate. It skips around a bit on me, better than nothing though.

That was my fear with that fix.
Seems that the spontaneous reset points to a root problem that is not being addressed...

 

[blazinsmokey]

That was my fear with that fix.
Seems that the spontaneous reset points to a root problem that is not being addressed...

RehabMan, I was thinking maybe the fixes we are using in the DSDT, can you take a look if I upload all the typical files you have listed in the problem reporting of your laptop faq thread? Or have you already taken a look at freejacks?