New XPS 15 (9560) compatibility?

[freejack]

No effect. Just moved it to my desktop restarted, checked to make sure it wasn't loaded and it wasn't. Frustration intensifies.

Sorry. I feel like I'm giving you the runaround but I'm really trying to help. Don't know how I missed this before but a user was having a similar issue here with his XPS 9530: https://www.tonymacx86.com/threads/guide-dell-xps-9530-using-clover-uefi.172859/page-49#post-1221900

Turned out to be a faulty trackpad. I'm hoping this is not the case but I have another 9560 on order (due to an unrelated issue) and will see if that one exhibits the same problem.

FYI, the trackpad still stops working for me also but not as frequently as you seem to be experiencing. There's a potential workaround. A utility can be written to parse the log contents constantly and immediately reload the trackpad driver when bad data is logged by the driver. Should be barely noticeable if reload instantly but I'll need to figure out how this is done.

 

[blazinsmokey]

Sorry... https://www.tonymacx86.com/threads/guide-dell-xps-9530-using-clover-uefi.172859/page-49#post-1221900.

Hey man, do not be sorry for anything. I'm just thankful someone else is working on this laptop with me. Seems like you and me are the only people trying to get this laptop working for now. I've seen you entered a thread I was in on another forum as well seems no one is trying much other than us, or more like you, lol.

I have been using my laptop in Windows almost everyday since I got it with zero glitches or issues with the touchpad. I read that thread you linked going back some pages to see what the issues are. He said he eventually had a glitch with the left click in Windows but after he sprayed and "cleaned" his trackpad connections. Wouldn't be surprised he made non issue into an issue. Mine literally goes for 15 seconds and dies after boot. If I move it around crazy fast it dies even quicker. I find it hard to believe that you and I both have faulty trackpads.

I just got my wifi card!! No more thumbdrive back and forth!! Will be installing it later and will do a clean install. I'm also going to try and compare our DSDTs, I think I our problem lay in there somewhere for the trackpad.

I have however enabled Speed Shift from the BIOS and confirmed in Windows using this link, super easy and set at the BIOS level. You may have already done it but worth noting here for future owners. Nice and knowledgeable thread too.
http://forum.notebookreview.com/threads/xps-15-9560-owners-thread.800611/

 

[freejack]

I have however enabled Speed Shift from the BIOS and confirmed in Windows using this link, super easy and set at the BIOS level. You may have already done it but worth noting here for future owners. Nice and knowledgeable thread too.
http://forum.notebookreview.com/threads/xps-15-9560-owners-thread.800611/

Thanks. I've enabled it although I haven't confirmed if it does anything in Sierra.

Edit: Deleted my theory on the battery shielding. Losing trackpad even with the battery removed now.

 

[freejack]

Thanks. I've enabled it although I haven't confirmed if it does anything in Sierra.

Edit: Deleted my theory on the battery shielding. Losing trackpad even with the battery removed now.

@RehabMan I think we may need your assistance with this one. All of us 9560 users are experiencing the same trackpad instability. If it's a hardware issue then it must be widespread but the trackpad has not exhibited any issues in windows 10. Here are logs from the debug version of voodoops2controller that I collected from two different instances right when the trackpad stopped working. Note that the "Unexpected byte" message is sometimes truncated suggesting some kind of memory issue although it may very well be unrelated. I've bolded these lines.

There is one strong correlation I observed that may be useful. The trackpad never stops working when the fans are spinning.

Instance 1:
2017-02-19 11:21:59.988790-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: (1,0,1) secondary finger dx=0, dy=0 (3425,3344) z=64 (3428,3393,0,0)
2017-02-19 11:22:00.000543-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (4365,3654) z=60 w=0 mode=(9,9,9) buttons=0 wasdouble=1
2017-02-19 11:22:00.013516-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: secondary finger pkt (3416, 3220) (0d58, 0c94) = { 84, ac, 4a, e0, 66, 10 }
2017-02-19 11:22:00.013539-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: (1,0,1) secondary finger dx=0, dy=0 (3421,3281) z=64 (3425,3344,0,0)
2017-02-19 11:22:00.026473-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (4356,3606) z=60 w=0 mode=(9,9,9) buttons=0 wasdouble=1
2017-02-19 11:22:00.590398-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: now_ns=139489375621, touchtime=0, diff=139489375621 cpct=300000000 (false) w=3 (0,0)
2017-02-19 11:22:00.590402-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2p: setting clickbuttons to indicate left

2017-02-19 11:22:00.590433-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (6184,4864) z=250 w=3 mode=(9,9,9) buttons=2 wasdouble=1
2017-02-19 11:22:02.789888-0500 0x11a3 Activity 0x8000000000001c32 469 Google Chrome: (Security) SecTrustEvaluateIfNecessary
2017-02-19 11:22:02.790640-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.atomicfile] 0x7ffec3232300 opened /System/Library/Keychains/SystemRootCertificates.keychain: 385940 bytes
2017-02-19 11:22:02.790729-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.atomicfile] 0x7ffec3232300 closed /System/Library/Keychains/SystemRootCertificates.keychain
2017-02-19 11:22:02.792368-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.integrity] loading /System/Library/Keychains/SystemRootCertificates.keychain
2017-02-19 11:22:03.946634-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:22:03.946635-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (06) from PS/2 controller
2017-02-19 11:22:03.946636-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (01) from PS/2 controller
2017-02-19 11:22:03.946638-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
…lots of these messages…
2017-02-19 11:22:03.946645-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (04) from PS/2 controller
2017-02-19 11:22:03.946646-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (fb) from PS/2 controller
2017-02-19 11:22:03.946648-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (28) from PS/2 controller
2017-02-19 11:22:03.946649-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (03) from PS/2 controller
2017-02-19 11:22:03.946650-0500 0x106 Default 0x0 0 kernel: App
2017-02-19 11:22:03.946656-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 38=37 down
2017-02-19 11:22:04.011921-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: genADB = 3
2017-02-19 11:22:04.011926-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 4=0, 0=80 down
2017-02-19 11:22:04.124632-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 38=37 up
2017-02-19 11:22:04.124757-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending typed ADB code 0x3
2017-02-19 11:22:04.132097-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 4=14 up


Instance 2:

2017-02-19 11:43:20.439230-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(1,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.452481-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.464136-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.476616-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.489514-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:21.050349-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:25.652841-0500 0x21a Default 0x0 70 coreduetd: [com.apple.coreduet.admissionCheck.] CDDBatteryMonitor: received batterycallback, currentPercentage:0.000000!
2017-02-19 11:43:26.841745-0500 0x104 Default 0x0 0 kernel: Unexpected byte0 data (14) from PS/2 controller
2017-02-19 11:43:26.841747-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (07) from PS/2 controller
2017-02-19 11:43:26.841748-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:43:26.841750-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (15) from PS/2 controller
2017-02-19 11:43:26.841751-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (05) from PS/2 controller
2017-02-19 11:43:26.841752-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:43:26.841753-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (05) from PS/2 controller
2017-02-19 11:43:26.841754-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (03) from PS/2 controller

 

[RehabMan]

@RehabMan I think we may need your assistance with this one. All of us 9560 users are experiencing the same trackpad instability. If it's a hardware issue then it must be widespread but the trackpad has not exhibited any issues in windows 10. Here are logs from the debug version of voodoops2controller that I collected from two different instances right when the trackpad stopped working. Note that the "Unexpected byte" message is sometimes truncated suggesting some kind of memory issue although it may very well be unrelated. I've bolded these lines.

There is one strong correlation I observed that may be useful. The trackpad never stops working when the fans are spinning.

Instance 1:
2017-02-19 11:21:59.988790-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: (1,0,1) secondary finger dx=0, dy=0 (3425,3344) z=64 (3428,3393,0,0)
2017-02-19 11:22:00.000543-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (4365,3654) z=60 w=0 mode=(9,9,9) buttons=0 wasdouble=1
2017-02-19 11:22:00.013516-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: secondary finger pkt (3416, 3220) (0d58, 0c94) = { 84, ac, 4a, e0, 66, 10 }
2017-02-19 11:22:00.013539-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: (1,0,1) secondary finger dx=0, dy=0 (3421,3281) z=64 (3425,3344,0,0)
2017-02-19 11:22:00.026473-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (4356,3606) z=60 w=0 mode=(9,9,9) buttons=0 wasdouble=1
2017-02-19 11:22:00.590398-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: now_ns=139489375621, touchtime=0, diff=139489375621 cpct=300000000 (false) w=3 (0,0)
2017-02-19 11:22:00.590402-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2p: setting clickbuttons to indicate left

2017-02-19 11:22:00.590433-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (6184,4864) z=250 w=3 mode=(9,9,9) buttons=2 wasdouble=1
2017-02-19 11:22:02.789888-0500 0x11a3 Activity 0x8000000000001c32 469 Google Chrome: (Security) SecTrustEvaluateIfNecessary
2017-02-19 11:22:02.790640-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.atomicfile] 0x7ffec3232300 opened /System/Library/Keychains/SystemRootCertificates.keychain: 385940 bytes
2017-02-19 11:22:02.790729-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.atomicfile] 0x7ffec3232300 closed /System/Library/Keychains/SystemRootCertificates.keychain
2017-02-19 11:22:02.792368-0500 0x1558 Default 0x8000000000001c32 294 trustd: (Security) [com.apple.securityd.integrity] loading /System/Library/Keychains/SystemRootCertificates.keychain
2017-02-19 11:22:03.946634-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:22:03.946635-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (06) from PS/2 controller
2017-02-19 11:22:03.946636-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (01) from PS/2 controller
2017-02-19 11:22:03.946638-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
…lots of these messages…
2017-02-19 11:22:03.946645-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (04) from PS/2 controller
2017-02-19 11:22:03.946646-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (fb) from PS/2 controller
2017-02-19 11:22:03.946648-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (28) from PS/2 controller
2017-02-19 11:22:03.946649-0500 0x106 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (03) from PS/2 controller
2017-02-19 11:22:03.946650-0500 0x106 Default 0x0 0 kernel: App
2017-02-19 11:22:03.946656-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 38=37 down
2017-02-19 11:22:04.011921-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: genADB = 3
2017-02-19 11:22:04.011926-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 4=0, 0=80 down
2017-02-19 11:22:04.124632-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 38=37 up
2017-02-19 11:22:04.124757-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending typed ADB code 0x3
2017-02-19 11:22:04.132097-0500 0x106 Default 0x0 0 kernel: (VoodooPS2Keyboard) ApplePS2Keyboard: sending key 4=14 up


Instance 2:

2017-02-19 11:43:20.439230-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(1,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.452481-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.464136-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.476616-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:20.489514-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:21.050349-0500 0x104 Default 0x0 0 kernel: (VoodooPS2Trackpad) ps2: dx=0, dy=0 (0,0) z=0 w=0 mode=(0,0,0) buttons=0 wasdouble=0
2017-02-19 11:43:25.652841-0500 0x21a Default 0x0 70 coreduetd: [com.apple.coreduet.admissionCheck.] CDDBatteryMonitor: received batterycallback, currentPercentage:0.000000!
2017-02-19 11:43:26.841745-0500 0x104 Default 0x0 0 kernel: Unexpected byte0 data (14) from PS/2 controller
2017-02-19 11:43:26.841747-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (07) from PS/2 controller
2017-02-19 11:43:26.841748-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:43:26.841750-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (15) from PS/2 controller
2017-02-19 11:43:26.841751-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (05) from PS/2 controller
2017-02-19 11:43:26.841752-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (08) from PS/2 controller
2017-02-19 11:43:26.841753-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (05) from PS/2 controller
2017-02-19 11:43:26.841754-0500 0x104 Default 0x0 0 kernel: ApplePS2SynapticsTouchPad: Unexpected byte0 data (03) from PS/2 controller

Does a sleep/wake cycle fix it?
Might be spontaneous reset (see related issue at github).
Or could be ACPI problem.
Read FAQ, "Problem Reporting".

 

[freejack]

Does a sleep/wake cycle fix it?
Might be spontaneous reset (see related issue at github).
Or could be ACPI problem.
Read FAQ, "Problem Reporting".

Wouldn't the message say "Unexpected reset..." if that was the case?
Btw, I also made the changes you suggested in another post to bind the print screen key to reinitialize the driver which works.

Sleep/wake restores functionality of the trackpad.

I've attached the relevant files. Thanks!

EDIT: forgot to attach files.

 

[RehabMan]

Wouldn't the message say "Unexpected reset..." if that was the case?

There is code in the kext to detect a reset and notify (0xaa 0x00). But some trackpads have been known to reset without an announcement.

Btw, I also made the changes you suggested in another post to bind the print screen key to reinitialize the driver which works.
Sleep/wake restores functionality of the trackpad.

Then it is spontaneous reset (without notification).

I've attached the relevant files. Thanks!
EDIT: forgot to attach files.

Too large (you must have included files that weren't requested).

 

[freejack]

There is code in the kext to detect a reset and notify (0xaa 0x00). But some trackpads have been known to reset without an announcement.

How would that be handled then? In windows I assume the driver knows how to handle these issues?

Too large (you must have included files that weren't requested).

Removed some large files from EFI/Apple/ and deleted the previous zip file. Thanks.

 

[RehabMan]

How would that be handled then? In windows I assume the driver knows how to handle these issues?

There is some code (currently disabled), in the kext to attempt to deal with it.
It doesn't work (which is why it is disabled).
Problem is that when a reset is detected, we need to re-initialize the trackpad, but it continues to send garbage shortly after the reset, which causes another reset, which completely breaks everything. The code should probably not send a follow up reset until after some time has passed, and should probably give up after a certain number of tries. Since I could never repro the problem, I never implemented the required code.

Removed some large files from EFI/Apple/ and deleted the previous zip file. Thanks.

Actually, EFI is not even requested... the request is only for EFI/Clover (very clear in the FAQ request).
And the files in ACPI/origin are not from today.
Remove all files from ACPI/origin and re-submit the requested files...

 

[freejack]

There is some code (currently disabled), in the kext to attempt to deal with it.
It doesn't work (which is why it is disabled).
Problem is that when a reset is detected, we need to re-initialize the trackpad, but it continues to send garbage shortly after the reset, which causes another reset, which completely breaks everything. The code should probably not send a follow up reset until after some time has passed, and should probably give up after a certain number of tries. Since I could never repro the problem, I never implemented the required code.

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

If the trackpad is reset, why would there still be garbage sent or is that the data left over in the buffer?

Actually, EFI is not even requested... the request is only for EFI/Clover (very clear in the FAQ request).
And the files in ACPI/origin are not from today.
Remove all files from ACPI/origin and re-submit the requested files...

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