bpedman

Do you see any messages between "Initilizing touchpad hardware" and "Touchpad initialization complete"?

So, on the debug version you don't even see messages like: "Got pointer event with packet: { xx, xx, xx, xx, xx, xx }" if not then it may still be reporting data but in a PS/2 format which I am ignoring right now because that screws up my touchpad and makes the movement crazy....for some reason it reports PS/2 packets interleaved with the ALPS packets which is kind of annoying, but its weird because the linux driver processes them as well but doesn't cause issues there...not sure why. I made some more changes specifically to the v1/v2 stuff including more logging and error checking, attaching the built kexts, try out the debug version and let me know what you see in the log. ALPS-TouchPad-Driver-v4.1.zip

Also, do you see any messages output when you touch the trackpad or trackstick (I assume you have a trackstick since that model is flagged as dualpoint in the driver).

Just wondering if you see any error messages at all, like "Device initialization failed" or more of those "ApplePS2Controller: Timed out on mouse input stream." messages after the second identification output. FYI, the reason you see multiple lines showing the trackpad identification is because the controller first does a probe and then an initialization...I could probably clean that up but just have it in there both times to ensure the values are all setup correctly since the probe could release some resources...

OK, so it is getting detected as an ALPS device and detecting the correct version which is good. However, I need to see more logging, right at the end of what you pasted is the beginning of the hardware initialization.

V4 is the latest so that should be it. Would you be able to try the debug version and post the system.log from bootup to login and include some touchpad touches? I know that there are some settings I have defaulted that may not work so well with the other versions...like the acceleration multiplier.

Yeah, that would be great to test it on some older hardware. If it works then yeah this should be able to replace all other ALPS drivers...just one driver for all models like the Linux driver.

Just added support for v1/v2 models. Not sure if it works correctly, but hopefully it works somewhat. At least now it is a full port for all models of ALPS touchpads. Adding more support in the future should be easier since it will be minor changes to track the linux driver. I just got a new laptop today so I don't know how much more debugging I will be able to do with this driver anymore on my own. At least the source is all open so anyone can help out and I can still at least try to make changes. My next step right now is to get this merged in with ReHabMan's code so it can share the same fixes he makes for other parts of the driver (keyboard, mouse, and other shared stuff)

Oh yeah... Will update the first post to include that in a little bit... But it is in the install instructions I linked to as well.

Yes it does have the ps2 nub integrated... And yeah, gotta get rid of any other ps2 kext and ps2enabler kext.

OK everybody, I did a major rework of the driver to be as close to the Linux v3.9 driver as possible. It supports a lot more models now, though it is still lacking protocol v1/v2 support. I need to figure out how exactly to process the info from those. olvidalo, it would be great if you could try out this new version and see if it works for you. driedger, try out this new version and see if it works, though I am afraid it may still not work. I did not see your signature listed in the v3.9 driver. However, there is a chance that if your command mode response matches some things it checks for it may work... Let me know what you guys find, it is working for me.

Hmm. Do you happen to have another mouse plugged in...I just remembered that I think the VoodooPS2Daemon will disable the touchpad if another mouse is plugged in. If that does not help, could you attach the whole system.log file from bootup to login?

Yeah, I will definitely see what I can do...hopefully just a few days... Those log lines are exactly what I get with my touchpad...everything looks good there from what I can tell. Even the command mode response (the line with ApplePS2ALPSGlidePoint EC Report) is the same which means it is definitely the exact same model. Could you open up a terminal once you login with the debug version (i.e. use a USB mouse if you have to) and run 'tail -f /var/log/system.log' and then try to make some movements on the touchpad and see if anything shows up there?

Just looked at some things on google and looks like the E5430 actually has a different model. It's identifier is 0x73, 0x03, 0x0a, also the protocol version is v4 instead of v3 like the one I have. So as it stands right now it won't work. However, I am trying to get it working for all the different protocol versions...a complete port of the alps driver in linux. Give me a few days or so and I might have something for you to try out.

Actually, since you are on a E5430, if you are running the debug version check the log for: E7: { 0xXX, 0xXX, 0xXX } E6: { 0xXX, 0xXX, 0xXX } ALPS Device? yes/no Maybe I should include those lines in the regular kext instead of just on debug

If the system.log does not contain a line like 'ApplePS2ALPSGlidePoint: ALPS model 0x73,0x02,0x64' then it isn't loading the correct kext...might be picking up something from the cache still or some other version from another location. See post #7. https://osxlatitude.com/index.php?/topic/2545-new-touchpad-driver-for-e6520-alps/&do=findComment&comment=19195

Hmm, should be working for that version. That is the same model I have, although there are some minor variations in the behavior between the 0x73,0x02,0x64 versions...but since you have an E6520 as well, it should really be the exact same. So, some questions: - What version of OSX are you running? - Run the following 2 commands in a terminal: find /System/Library/Extensions -name '*PS2*' find /Extra/Extensions -name '*PS2*' And paste the output..This is to make sure that no other PS2 kexts are there including the AppleACPIPS2Nub and ApplePS2Controller which should not exist anywhere...sometimes those kexts get left over either in /E/E or in /S/L/E/myHack.kext/PlugIns - Did it not work at all? Or just no side-scrolling or whatever? Also, I have noticed at other times that sometimes the kexts don't get refreshed properly until after a couple reboots...but it may have been my own fault...should be OK as long as you use myHack and run a quick fix or just regenerate the kext cache

Make sure to check /var/log/system.log if it doesn't work and check for "ALPS model x,x,x." And let me know the numbers there. That way I can try and make sure it works for your version.

Just realized I forgot to attach the built driver...haha..attached it now

I know this may be like double posting but I know I don't ever look at the other sections other than this one. I posted a new driver in the Hardware section for the E6520 touchpad. See all the details here https://osxlatitude.com/index.php?/topic/2545-new-touchpad-driver-for-e6520-alps/ and try it out, thanks.

So I took some time to get a working touchpad driver for the touchpad in my Latitude E6520. This driver is based off of the one by ReHabMan. Source: https://github.com/bpedman/OS-X-Voodoo-PS2-Controller The code for the ALPS driver is also heavily based on the Linux driver (3.8 kernel version). See here: http://lxr.free-electrons.com/source/drivers/input/mouse/alps.c?v=3.8 The driver is now ported mainly from the v3.9 kernel which supports a few more models. See here: https://github.com/torvalds/linux/blob/v3.9/drivers/input/mouse/alps.c Installation Instructions: Make sure to follow the installation instructions from rehabman especially the part on removing the other PS2 kexts you have installed like AppleACPIPS2Nub.kext. See https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Install Note that if there is a constant dinging sound after you boot at the login screen, just hit the backspace key to make it stop. What Works: - Side scrolling (hallelujah) - Tap clicking - Trackstick movement - Trackstick buttons, including middle click with the middle trackstick button - Two-finger scrolling - Recognized as built-in trackpad (the trackpad prefpane loads) What Doesn't Work: - 3-finger swiping (I can see it correctly detect 3 fingers but the swiping action doesn't work right now I don't think) - NO IDEA if any of the preferences in the preference panes work...I have not tried changing many things except for enabling tap clicking, I just modified the default values in the driver to acceptable values for me) - ALPS V1/V2 touchpads will not work....other drivers out there already support those versions. I made this just for my touchpad version but I could fairly easily support multiple versions in the future just like the Linux driver does. I updated to support a lot more versions but I still need to figure out how to properly port the v1/v2 packet processing. Got it ported now for V1/V2 models but not sure if it works correctly or not. TODO: - Merge with ReHabMan's official driver to have fairly good support for multiple touchpads (his has good support for Synaptics touchpads, I chose to base off his driver because of the extensive options and his code was very nice and understandable)... - Get 3-finger swiping working - Make 3 finger actions actually do something.... - Test out the preference pane options - Support multiple ALPS device versions - Fix issue where a tap click occurs when lifting finger after doing a side-scroll (I made a change to hopefully help but I still see it happen every once in a while). The driver includes both debug and release versions...debug version includes TONS of log messages to /var/log/system.log Have fun...hopefully I have time to do all the things on the list. ------------------------------------------------------------ EDIT: 13-May-2013 - Got swiping working, but I still don't see anything happening. It is controlled by the VoodooPS2Controller and sends some special keyboard sequences, but I don't see anything happen in the OS...oh well, at least it is firing the 3-finger swipe actions now... EDIT: 18-May-2013 - Ported nearly all the code from the Linux driver over to this. Now supports most models that are not v1/v2...I still need to figure out how exactly to process their packets EDIT: 24-May-2013 - Translated what I could of the v1/v2 protocol...not sure if it is correct or not, but would be nice to have someone test...not even sure what models of laptops use this, but at least now it is a complete port for support for all models. EDIT: 5-June-2013 (v5) - Fixed issues with detecting if a trackstick was present or not - Fixed issue with finger detection on v1/v2 models - Preliminary support for multiple finger detection on v1/v2 models - Potential fix for side scrolling on v1/v2 models EDIT: 9-July-2013 (v6) - Rework the way command mode nibbles are handled, reflecting the Linux driver more closely - Potentially fix an issue that might occur when resetting the mouse EDIT: 12-July-2013 (v7) - Fixed some issues during the refactor of the nibble sending. It should now all work. Tested working on an n5050, thanks bjornw! EDIT: 8-Sept-2013 - Adding merge with rehabman ALPS-TouchPad-Driver-v7.zip RehabmanMerge.zip

Nice, that fixed it. Thanks.

Thanks for this. Went ahead and bought one of these and it is working great! Yeah, this is what threw me off, thought it was half-mini but when I got it, it was actually full size..didn't read close enough. Luckily the E6520 I have at least has an extra spot for a WWAN card which I didn't have installed which is a full height slot. So I took out the original half-height one and put the full height AR9380 in the WWAN spot. I had to move some of the wires around so it would reach the card in the new location but it is all working fine. I am posting this from my e6520 right now all wireless. Also, one thing that is kind of weird that may be related to using the WWAN spot instead of the WLAN spot is that when I am connected, the network settings in system preferences shows that the Bluetooth PAN is connected as well as the Wi-Fi connection. And while the Wi-Fi connection shows it is connected to the network it doesn't list an IP address/DNS settings, etc, but the Bluetooth PAN has all that information on it...kind of weird but whatever...I didn't have to install any special kexts or anything.

I tried but could never get this working...then my laptop died and haven't gotten OSX back on it. I do have all my files I was working with though including a number of different DSDTs I tried out. Attached is a folder I kept everything in. Take a look. I can't remember which DSDTs worked and which ones didn't, so use at your own risk. OSX-Stuff.zip

Looks like the shebang is pointing to /bin/sh but it actually needs to be run using bash. Should probably update the script for that and/or run the script using bash directly, i.e.: bash ssdtPRGen.sh 17 3500