New TouchPad driver for E6520 / ALPS

[bjornw]

Give it a shot, the new version is on the original post marked as v5, once I get some verification it works OK I will remove the v4 download.

 

The V5 version looks to be doing more or less the same for me. The only difference I see is here:

Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x64 }
Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint ERROR: read wrong registry value, expected: 8
Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x14 }
Jun  5 10:57:36 localhost kernel[0]: ApplePS2ALPSGlidePoint ERROR: read wrong registry value, expected: 4

Used to be in the V4 version:

Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x64 }
Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint ERROR: read wrong registry value, expected: 8
Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x64 }
Jun  3 09:32:00 localhost kernel[0]: ApplePS2ALPSGlidePoint ERROR: read wrong registry value, expected: 8 

So " 0x14 " is now " 0x64 "  and " expected: 8 "  is now " expected: 4 " Not sure this is significant. I also Noticed that the VoodooPS2synapticsPane.prefPane Doesn't save settings after reboot, maybe this has to do with not propperly loading the kext. After reboot, it goes back to default settings.

 

Like miguelme777 my n5050 has no stick. basically n5050 (mine) is the same as his n5040 (miguelme777) Different cpu, hdd and RAM, but the rest is the same

 

Here's complete log output with the v5 version (filtered the system.log on "PS2") of anything trackpad related. (attached it to the post to keep the thread better readable). Would like to contribute more than just testing, is there anything I can do? Look at the source code maybe? Any advice on where to start?

 

V5 log.txt

 

SMALL UPDATE:

 

Did a clean install on a other HDD, just to make sure that my current installation wasn't the source of the error. It didn't change anything though, same log entries as mentioned above. 

[bpedman]

OK, I will look again. I know where this is happening, something is being handled wrong when it probes for the trackstick.

 

Also, can't remember if it was you or someone else that asked, but yes the code is up on github, the link is is the first post...but here is the link too so you don't have to go look at the first post as well: https://github.com/bpedman/OS-X-Voodoo-PS2-Controller

The file you would want to look at is https://github.com/bpedman/OS-X-Voodoo-PS2-Controller/blob/master/VoodooPS2Trackpad/VoodooPS2ALPSGlidePoint.cpp

[bjornw]

it was me, I already saw that you posted the code location on github in your first post, I oversaw it at first. when I found it, I edited my post, no reason for asking something that's already clear

 

I already had a look at the file you mentioned, but it's a bit above my programming skills 

 

Really appreciate your efforts though!

 

cheers

[bpedman]

Weird, so it is getting past the trackstick probe now but it is still having issues with the result from reading a register.

 

In the linux driver it states that the first and second bytes should come back representing the address that was read from. However, in your case it is always coming back as 0x50 0x00. I stuck a little workaround in for this so that if the version is v3 and the first and second bytes come back as 0x50 0x00 then I will treat it as acceptable.

 

Give it a shot, attached to this post

ALPS-TouchPad-Driver-v5.1.zip

[bjornw]

Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint::identify: Found ALPS Device with ID E7=0x73 0x02 0x64, EC=0x88 0x07 0x9d
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x64 }
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x14 }
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x40, 0x02, 0x3c }
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint ERROR: read wrong registry value, expected: 6
Jun  6 11:39:44 localhost kernel[0]: ApplePS2ALPSGlidePoint: Device initialization failed. Touchpad probably won't work

this what happens now, so it does read another reg value, but that doesn't change the outcome.

[bpedman]

Sheesh...well, OK, so I removed all error checking here for this model then. Dunno what is going on. You will have to see what happens after all the initialization is complete.

 

Thanks a bunch for testing this out so much, hopefully we can get a good driver working for everybody.

 

New version attached

ALPS-TouchPad-Driver-v5.2.zip

[bjornw]

Well different result, but worse than it was  . Now the trackpad isn't functioning at all... (keyboard is fine though) No debug messages anymore when I touch it. 

 

I've attached a complete system.log of a boot cycle filtered on "PS2".

 

V5-2 ps2 system.log.txt

 

A bunch of reg entries are loaded now (what do they refer to?) 

Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint::identify: Found ALPS Device with ID E7=0x73 0x02 0x64, EC=0x88 0x07 0x9d
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x64 }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x50, 0x00, 0x14 }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x40, 0x02, 0x3c }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x40, 0x02, 0x50 }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x00, 0x02, 0x14 }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x00, 0x02, 0xc8 }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x00, 0x02, 0x0a }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2ALPSGlidePoint read reg result: { 0x10, 0x02, 0x3c }
Jun  6 17:34:21 localhost kernel[0]: ApplePS2Controller: setCommandByte for mouse interrupt install
Jun  6 17:34:21 localhost kernel[0]: ApplePS2Controller: oldCommandByte = 45
Jun  6 17:34:21 localhost kernel[0]: ApplePS2Controller: newCommandByte = 47

How would a log of a successful kext load look like? can someone post an example?  

[miguelme777]

Okay, so I just tested this myself to be sure, and I am getting the exact same results as bjornw.  Our hardware is mostly the same, so if it works for one of us, it'll probably work for both of us. [:

[bpedman]

Thanks for the log...some of my log messages don't have PS2 in them though unfortunately...I should probably fix that...any way I could get the whole log?

[bjornw]

Thanks for the log...some of my log messages don't have PS2 in them though unfortunately...I should probably fix that...any way I could get the whole log?

 

I send you a pm with a full boot cycle log, I saw there were a few debug messages i missed before. I sent it by PM because there probably will be private information in there I don't want spread publicly. I trust you'll treat it with respect

 

Small Update:

 

I thuoght I could test Ububtu and see how it would detect my touchpad. So I installed 13.04 on an extrernal HDD and did some testing. in Ubuntu the touchpad works just fine, single and multi touch. I've attached a file with the output of the tests I did. Maybe it helps if you know what output my ALPS trackpad gives when it is working propperly.

 

If it helps I can do additional tests. Let me know what tests on Ubuntu i should run, to help you make the propper adjustments to the kext so it will detect my trackpad in OS X.

 

Cheers

 

Log file ubuntu touchpad.txt