bmp152

Let me revise my previous post.  I tried some more 3 finger gestures and the vast majority of the time it either does absolutely nothing or causes scrolling (probably a finger slips a bit ?).  However, every once in a great while I do hear a little error funk tone.  It's kinda rare tho'.

 

Maybe this helps ?

Hi bisk. Just to clarify, are you using yeahoon's most recent kext or are you using the RehabmanMerge Alps_Multitouch kext that I posted a few days ago? I tried to install yeahoon's most recent kext and I have no tracking. I just wanted to clarify so that if npjohnson does more work on the kext for our trackpad model, he's looking at the right code. Also, I wanted to make sure that my system is not behaving differently than yours with yeahoon's kext...

Hey npjohnson,

 

My system does not beep.  I'm not sure what you mean by "does 3 finger fire off".  I am a very simple user and do nothing unusual other than 2 finger scrolling.  Basically, If I can click, grab, drag and 2 finger scroll reliably, I'm happy.

Hi npjohnson. My system does not beep either when performing a 3-finger swipe. Like bisk, I don't use these features very often and would also be pretty happy with click, drag, and 2-finger scrolling.

Thanks again for all of your hard work! Looking forward to the new kext!

Also I might add that this worked very well on my E6420, though it should work on all ALPS models, @bisk & @bmp152 try this kext and see if your models work, I would be surprised if they didn't...

 

Thanks for the support everyone!!!

Hi npjohnson! Thanks for the continued work on this driver. I installed the kext and it appears to load but does not find my alps trackpad device id:

Yep, I think I remember this one as the RehabMan Merge.  I did try it right before the superior v7 on this forum came out.  I had forgotten completely about it.  I do have it installed and it seems the best alternative out there for us right now.  Interesting how our new IDs don't affect it's loading.  I assume that it hasn't been tuned for our trackpad yet.

 

You are right, the 2 finger scrolling comes and goes but the most bazaar thing is that the tracking acceleration seems backwards.  In other words, moving a finger across the trackpad quickly makes the cursor move like a snail while sliding a finger very slowly causes the cursor to fly across the screen.  That's what I remember about this kext last time !

 

Very strange, huh ?

 

Thanks again bmp152 for bringing this one in

Yep, the tracking with this kext is exactly as you describe. Slowly brushing the touchpad causes the pointer to accelerate rapidly, while swift movement causes the pointer to crawl. Also, I've noticed that the intermittent scrolling seems to be somewhat improved when you press down harder on the trackpad. Although, this may be related to the inverse tracking issue, i.e. harder pressure/slower movement leads to faster scrolling. I'm not sure if adjusting the Z-finger setting may fix these issues (if that's even possible with this kext)? Unfortunately, I'm not sure where this setting is located. 

Also, today I noticed that after reviving my hackintosh from sleep, the trackpad was totally unresponsive. I plugged in a USB mouse, removed it, and the trackpad then worked again. So there's some kind of sleep-related issue as well. Is this reproducible on your system bisk?

Thanks again guys for all of your hard work.

Thanks again yeahoon for all of your contributions.

@bisk: I was poking around google and found somebody with the same device ID (0x73 0x30 0x50) as ours on the InsanelyMac forum. In that same massive thread I found that someone (Florin9doi?) was working on an ALPS multitouch hackintosh driver. I downloaded the latest version (v beta 5, specifically with alps v6 support). I then uninstalled the recent VoodooPS2Controller.kext provided by yeahoon but left all other files in place. I installed the newly downloaded VoodooPS2Controller.kext from InsanelyMac to S/L/E, rebuilt cache and permissions.

http://www.insanelymac.com/forum/topic/271573-guide-dell-inspiron-n5110/?p=1897980

To my surprise, the trackpad actually had movement. I could also click/drag! 2-finger scrolling and 3-finger gestures work as well! Since installing, my enthusiasm has waned a bit. The tracking seems very fast, even when adjusting to the lowest value in the PrefPane. 2-finger scrolling is "jumpy" and doesn't seem highly sensitive. Perhaps these are values that can be adjusted in the kext files?

I've attached the file for you to try out.

@yeahoon and @npjohnson: Please check out this kext for any potential ways to improve upon it. Many thanks for all of your continued help and contributions.

ALPS_Multitouch_VoodooPS2Controller.kext.zip

Hi yeahoon. Thanks very much for working on this!

I appear to be having the same problems as bisk. After installing your kext, I lost mouse tracking. Looking in the system log, it does appear that the device is recognized properly. I too also have a configurable trackpad in the Prefpane, whereas before it simply said "Trackpad not detected".

I am running ML 10.8.5 on a Dell Inspiron 13z.

Thanks again to both you and npjohnson for your hard work!

I've attached by system.log

system.log.zip

@npjohnson and @yeahoon: I just wanted to express my thanks for your continued efforts on revising the drivers and adding support for the ID E7=0x73 0x03 0x50, EC=0x73 0x02 0x02 Alps trackpad. Looking forward to testing out the final products!

Awesome! Thanks for all of your hard work...looking forward to testing the finished product once its compiled.

@bisk. Thanks for attempting to look up those DevIds. I can't seem to find much on my system either.

I was googling around a bit for the DevIds and found a link to another alps.c source code:  http://www.emmestech.com/linux/downloads/alps.c

static const struct alps_model_info alps_model_data[] = {
    { { 0x32, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* Toshiba Salellite Pro M10 */
    { { 0x33, 0x02, 0x0a },    0x00, ALPS_PROTO_V1, 0x88, 0xf8, 0 },                /* UMAX-530T */
    { { 0x53, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x53, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x60, 0x03, 0xc8 }, 0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },                /* HP ze1115 */
    { { 0x63, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x02, 0x28 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_FW_BK_2 },        /* Fujitsu Siemens S6010 */
    { { 0x63, 0x02, 0x3c },    0x00, ALPS_PROTO_V2, 0x8f, 0x8f, ALPS_WHEEL },            /* Toshiba Satellite S2400-103 */
    { { 0x63, 0x02, 0x50 },    0x00, ALPS_PROTO_V2, 0xef, 0xef, ALPS_FW_BK_1 },        /* NEC Versa L320 */
    { { 0x63, 0x02, 0x64 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x03, 0xc8 }, 0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* Dell Latitude D800 */
    { { 0x73, 0x00, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_DUALPOINT },        /* ThinkPad R61 8918-5QG */
    { { 0x73, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x73, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_FW_BK_2 },        /* Ahtec Laptop */
    { { 0x20, 0x02, 0x0e },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* XXX */
    { { 0x22, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },
    { { 0x22, 0x02, 0x14 }, 0x00, ALPS_PROTO_V2, 0xff, 0xff, ALPS_PASS | ALPS_DUALPOINT },    /* Dell Latitude D600 */
    /* Dell Latitude E5500, E6400, E6500, Precision M4400 */
    { { 0x62, 0x02, 0x14 }, 0x00, ALPS_PROTO_V2, 0xcf, 0xcf,
        ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED },
    { { 0x73, 0x02, 0x50 }, 0x00, ALPS_PROTO_V2, 0xcf, 0xcf, ALPS_FOUR_BUTTONS },        /* Dell Vostro 1400 */
    { { 0x52, 0x01, 0x14 }, 0x00, ALPS_PROTO_V2, 0xff, 0xff,
        ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED },                /* Toshiba Tecra A11-11L */
    { { 0x73, 0x02, 0x64 },    0x9b, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
    { { 0x73, 0x02, 0x64 },    0x9d, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
    { { 0x73, 0x02, 0x64 },    0x8a, ALPS_PROTO_V4, 0x8f, 0x8f, 0 },
    { { 0x73, 0x03, 0x0a },    0x1d, ALPS_PROTO_V5, 0x8f, 0x8f, ALPS_DUALPOINT },        /* Dell Latitude E6430 */
    { { 0x73, 0x03, 0x50 },    0x0d, ALPS_PROTO_V6, 0xc8, 0xc8, 0 },                /* Dell Inspiron N5110 */
    { { 0x73, 0x03, 0x50 },    0x02, ALPS_PROTO_V6, 0xc8, 0xc8, 0 },                /* Dell Inspiron 17R 7720 */
};

The last 2 lines seem to provide a definition for 1 of the device codes we see during boot: 0x73, 0x03, 0x50. However, there appears to be no reference for the 0x73, 0x02, 0x02 device id. Perhaps that second 0x02 in the "Dell Inspiron 17R 7720" line indicates such?

I'm not sure if any of this helps to compile the new alps code, but I thought I'd pass it along to somebody smarter than me! Thanks again for your interest and hard work, whenever you get the chance. Enjoy the holiday.

@npjohnson - you are the man! Many thanks for your efforts in recompiling the alps source.

Unfortunately, I couldn't find the device or vendor ID for the alps touchpad in my Dell 13z-5323. Much like bisk, the only reference to the device id that I could find was listed as above. I am running Mountain Lion 10.8.5.

@bisk - since you have a dual-boot environment, perhaps you could boot into Windows 7 and attempt to find the device ID, as per npjohnson's suggestion. It's been a long time since I've used Windows, but I believe if you open device manager, right click on the device, go to properties, and look for device details, you should find something that looks like PCI\VEN_xxx&DEV_xxxx&SUBSYS_xxxxxxx&REV_xx. Thanks in advance!

Hi all,

 

I have an Inspiron 3520 where this kext had previously worked perfectly, a true piece of art.  Then the touchpad buttons failed and I sent the notebook in to Dell for a warranty repair. 

 

I just received my unit back and it appears that Dell has both updated my BIOS from A04 to A09 AND replaced the trackpad with a slightly different hardware model.

 

So now the kext fails to recognize it and doesn't load.

 

This is a dual boot syatem and on the Windows 7 side it's still the same Windows driver installed.

 

Here are the relevant log entries from BEFORE with the original trackpad before the buttons failed and AFTER with the new trackpad which I received back fro DELL just today ...

 

--------

Before:

--------

 

Oct 30 10:03:56 haxmax78 kernel[0]: ApplePS2ALPSGlidePoint::identify: Found ALPS Device with ID E7=0x73 0x02 0x64, EC=0x88 0x07 0x9d

Oct 30 10:03:56 haxmax78 kernel[0]: Initializing TouchPad hardware...this may take a second.

Oct 30 10:03:56 haxmax78 kernel[0]: ApplePS2ALPSGlidePoint EC Report: { 0x88, 0x07, 0x9d }

Oct 30 10:03:58 --- last message repeated 1 time ---

Oct 30 10:03:56 haxmax78 kernel[0]: IOHIDSystem cursor update overdue. Resending.

Oct 30 10:03:56 haxmax78 kernel[0]: Touchpad initialization complete.

 

-----

After:

-----

 

Nov 22 09:14:31 localhost kernel[0]: ApplePS2ALPSGlidePoint::identify: Found ALPS Device with ID E7=0x73 0x03 0x50, EC=0x73 0x02 0x02

Nov 22 09:14:31 localhost kernel[0]: Unknown ALPS touchpad, does not match any known identifiers: E7=0x73 0x03 0x50, EC=0x73 0x02 0x02

Nov 22 09:14:31 localhost kernel[0]: VoodooPS2Mouse Version 1.8.3 loaded...

 

So, one step forward and then two back

 

Can the kext be modified to handle this trackpad ?  Looks to still be an Alps.

 

This new Alps trackpad is likely to be seen more often going forward, so accommodating it is definitely worthwhile.  I am happy to be a beta tester.

 

Just let me know

I seem to be having the same problem as bisk, using a Dell Inspiron 13z-5323. It was a recent refurb and may have likely had the same trackpad model replaced. The driver appears to be loading properly upon boot but cannot find the specific model. I've attached the system.log output: