Jump to content

bisk

Members
  • Posts

    73
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by bisk

  1. Yes, it definitely does as 2 finger scrolling works but is not quite sensitive enough. The trackpad.prefPane is active as well. This is a very polite kext and doesn't seem to log anything, at least not while running in release mode. It will probably be pretty tough to debug the glitches if you do not own this trackpad but if you want to go for it anyway, that's awesome ! While the main work right now seems to involve trackpads installed 1+ year ago, this bad boy that I and @bmp152 have is only a few weeks old. So this is much more likely what we'll be seeing on at least the new Dells going forward ! From Info.plist of the working kext ... <string>1.7.5, Copyright Apple Computer, Inc. 2000-2003, David Elliot 2007, RehabMan 2012</string> <key>CFBundleIdentifier</key> <string>org.rehabman.voodoo.driver.PS2Controller</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>Voodoo PS/2 Controller</string> <key>CFBundlePackageType</key> <string>KEXT</string> <key>CFBundleShortVersionString</key> <string>1.7</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>1.7.5</string> <key>DTCompiler</key> <string></string> <key>DTPlatformBuild</key> <string>4F243</string> <key>DTPlatformVersion</key> <string>GM</string> <key>DTSDKBuild</key> <string>12A264</string> <key>DTSDKName</key> <string>macosx10.8</string> <key>DTXcode</key> <string>0440</string> <key>DTXcodeBuild</key> <string>4F243</string>
  2. Thanks for the attempt but your build does not seem to have the code to recognize my new trackpad so it just drops back to the PS/2 mouse controller again. Unfortunately, I'm back to the pre-RehabmanMerge problem. Bummer Dec 11 05:30:01 localhost kernel[0]: VoodooPS2TouchPad Version 1.9.0 loaded... Dec 11 05:30:01 localhost kernel[0]: VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3): 0x00 Dec 11 05:30:01 localhost kernel[0]: VoodooPS2TouchPad Version 1.9.0 loaded... Dec 11 05:30:01 localhost kernel[0]: ApplePS2Controller: Timed out on mouse input stream. Dec 11 05:30:34 --- last message repeated 1 time --- Dec 11 05:30:01 localhost kernel[0]: ApplePS2ALPSGlidePoint::identify: Found ALPS Device with ID E7=0x73 0x03 0x50, EC=0x73 0x02 0x02 Dec 11 05:30:01 localhost kernel[0]: Unknown ALPS touchpad, does not match any known identifiers: E7=0x73 0x03 0x50, EC=0x73 0x02 0x02 Dec 11 05:30:01 localhost kernel[0]: VoodooPS2Mouse Version 1.8.8 loaded...
  3. No bmp152, My trackpad continues to work exactly the same way after waking from sleep. I've tested this fairly extensively so it seems maybe you've got something else going on there. Mine is the Inspiron 3520 which is yours ? I am quite impressed with the progress of this Alps kext but am a bit concerned that we now seem to have at least 2 variations possibly going in different directions. Hope this comes out alright for all involved.
  4. 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
  5. Thank you so much for trying. This what I feared. I dared to hope that the simple inclusion of the new IDs in this Alps kext would be sufficient because the existing Windows 7 driver from December, 2012 continues to work with this new trackpad on the Windows side. Once again, the v7 of this kext was working beautifully with the original trackpad delivered on my Inspiron 3520 last summer but then the buttons failed and Dell replaced the trackpad under warranty just a couple of weeks ago. So this is the latest Alps trackpad that Dell is using these days and it is likely to be popping up quite a bit from here on out. Hopefully, you will have the opportunity to work with on ... nothing much that you can do till then. Thanks again for the attempt. I am glad to see success with the E6420 as that is about to become my next build I'm monitoring this topic and stand ready to test again any time Take care and have a great holiday.
  6. Thanks ! OK, tested the new kext and looking at the log, the new device IDs are recognized but the cursor does not move. So tracking is totally dead I simply left TrackPad.prefPane from the original v7 in place and the PrefPane does sense that a TouchPad exists. In other words, when I click on System Preferences->Trackpad, a configurable panel pops up rather than an empty one. This is on an Inspiron 3520 running 10.8.5. Here's my log ... system.log.zip
  7. Bronxteck, When you say "if in -s exit then exit again should get to desktop ..." Are you saying that it's possible to pop into graphics mode from single user mode w/o rebooting ? That is to say by simply terminating the boot console ?
  8. Yep, I second that. Assuming you have another Mac, use Pacifist to inspect the contents of that PDA net package and then just remove the kext(s) it installed from SLE while in single user mode. Interesting that booting in safe mode doesn't suppress loading of the problematic kext. Hope that your troubles are only being caused by a newly introduced kext !
  9. OK, did that. I didn't really find any relevant vendor/device ID info within the PS2K/M sections of the registry. It appears that, at least, initial device identification is based more upon general ACPI class information rather than specific vendor/device ID designations. Then, given that, the pointing device is queried about it's internals to determine whether it's a mouse, trackpad, touchscreen or whatever. I'm probably just talkin' out my arse here but definitely not seeing VID/DID like I do for the video chip, drive controller, USB controller, etc. Thanks to anybody who can mod the codebase for this. No huge hurry. It's getting into the holidays after all
  10. Ah, that's a fine suggestion and I did do that. But when I go to Device Manager, select the Dell Touchpad and choose Details->Hardware Ids, I get ... ACPI\DLL0555 rather than the usual VendorID/DeviceID/SubSysID entry. Looks like pointing devices are just organized differently internally. I get the feeling that the protocol info from the log is probably all that's really needed anyway. It appears that this kext already knows that we have an Alps trackpad. Let me boot up in Mac again and have a closer gander at IORegistryExplorer.
  11. Hey, Right On npjohnson ! Well, what I get from the log is that I have this Alps -> Found ALPS Device with ID E7=0x73 0x03 0x50, EC=0x73 0x02 0x02. If there is another place where I can find more device info on the trackpad just let me know and I'll happily dig it out for you. I'm running Mountain Lion 10.8.5 on a Dell Inspiron 3520. 3rd Gen i5/6GB PC3-12800/500 GB HDD/HD4000 etc. and dual booting Windows 7 Ultimate x64. Thank you so much for you effort
  12. Yes my friend, You have EXACTLY the same touchpad and EXACTLY the same problem as I. We are now both sporting this new -> "E7=0x73 0x03 0x50, EC=0x73 0x02 0x02" protocol and this kext has no idea what to do with it. Somebody needs to add this set of IDs to the source and recompile. With luck, there won't actually be any new functionality necessary and this trackpad will work OK with existing code for the older model. This is at least a 50/50 possibility since the old Windows 7 driver still works the same with this "new" trackpad. Right now all we get is generic PS/2 mouse functionality with poor tracking, delayed clicking, and horrible cursor jumping when typing fast which results in previously typed text being selected and written over as you go. Basically, our HackPros have been rendered unusable w/o an attached USB mouse. My coding/compiling skills are too outdated for me to do anything about this on my own anytime soon If anybody could step in on this one, I promise that I'll test the h*ll out of it TIA
  13. 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
  14. Fantabulous ! I have an Inspiron 3520 (3rd gen i5) running 10.8.4 on which BOTH the touchpad AND K/B were unusable. Mouse movement was jerky and speed unreliable but, much worse, while typing on the K/B, the cursor would randomly jump, highlight and replace previous text. I had resorted to a USB mouse and keyboard on this notebook ! This is a dual boot and the same K/B issue happened under Win7 as well but the TouchFreeze fixed it over there. Dell support actually uses that free utility as the official tech fix. Sure hope that they are donating I stumbled upon the v7 Alps kext here and now both touchpad and K/B are working great ! Cursor tracking, text selection, window/icon dragging are all smooth and concise AND the terrible K/B behavior has ceased. For 2 finger scrolling, my fingers need to be a little bit apart or it seems that 2 fingers are seen as one but this in not any big deal. Also, the stock Apple Trackpad preference pane just works ! I can't speak to any of the myriad of other possible gesture features that should/maybe working or not 'cuz I don't use 'em but for the basics that I need ... this kext is perfect right now ! AWESOME WORK !!!
  15. Apparently, I spoke a bit too soon. I turned this laptop over to my wife and she deemed immediately the touchpad unusable. She finds it way too sensitive, selecting things randomly upon passing, putting Apps in full screen mode, etc. I have probably become too delicate with it as the months have gone by. I was concerned about that so turned it over to a new user for a fresh perspective. Unfortunately, it failed in a matter of seconds I will look into deactivating "features" to see if this helps. I guess all learn them by trial and error. Not ideal, I know, since you are wanting to develop a full featured kext but for this Acer 5755 series notebook it's just all going crazy ! Thanks again.
  16. OK ! Installed v2.8.0 now and the click and drag is much, much better Before, there was a minimum 2-3 second wait necessary after the left click before a window could be dragged. Now it's a second or perhaps a tad less. Click and drag can still NOT be instantaneous though. Also, text select seems to work more reliably and the touchpad continues working after wake more often as well. I think that it's only failed once so far in about 6 sleep/wake cycles. The touchpad does continue to do a few odd things . For instance, it randomly causes the current window to go full screen just from a single finger swipe during typing, for instance. It also seems to select things w/o a button click at times as well. Perhaps I do not understand all of the possible gestures. Are there single finger swipes that are meant to cause this behavior ? Maybe based on the direction or from crossing into a particular segment of the screen ? I have looked at the Info.plist file contained within the ApplePS2ElanTouchpad.kext and see MANY configurable options but there is no explanation of their functions that I can see and the option names do not help me in most cases. Is there documentation for these parameters anywhere ? Which parameter would help numb single finger swiping sensitivity w/o lengthening the lag between grab and drag ? All that I really want is basic mouse behavior + 2 finger scrolling and touchpad waking from sleep. If these could be made to work 100% by simply dropping all of the other fancy features, I'd be very happy What are the basic parameters that I should I leave on to accomplish this ? What can be switched off ? Perhaps, I should dumb this device down and then gradually add back functionality to see what's messing things up. However, this is quite a nice driver even as it exists right now.
  17. Hi. I've been using your kext for quite some time (since at least 1.8) and have been on 2.7.5 since it was available. My problems have pretty much always been the same. I must wait 2-3 seconds when grabbing a menu bar until the window will recognize that it has been grabbed and can be moved. The same goes for releasing menu bars. I must stop dragging for a couple secs after releasing the button before the window registers that it has been let go. Also, the trackpad only continues to work about 1/3 of the time after waking from sleep. I am running 10.8.4 on an Acer 5755-9401, definitely with ElanTech. Also, I can't seem to find where the binaries are anymore. Is 2.8.0 available ? Should I be removing any stock Apple kexts ? Right now, I simply add your 2 kexts into /E/E. TIA, bisk
  18. OK, I'm trying v2.6 now and, at first, I thought it was the same. However, I am seeing that grab and drag does usually work with a slight delay. Many times, it actually creates a drag lock even though I do not have this option selected on the Prefs Panel. Also, this is the first version that continues to work for me after wake from sleep. It's really coming along. Nice work ! I am running 10.8.3 on an Acer Aspire 5755-9401. bisk
  19. Hey guys, I'm liking this kext alot. The 2.6 version now continues to work after sleep where none of the previous versions did for me. Two finger scrolling works great, the tracking seems quite accurate, etc. But the one problem that has persisted since the beginning still remains. I am UNABLE to drag windows, icons or scroll bars. I can select but never drag. For instance, selecting various windows will make them pop to the top but I can't move or resize them by dragging ! I can advance scroll bars by clicking ahead of them in the well but not grab and move them directly ! I can click into spots in paragraphs of text but not drag to highlight anything but if I click, double click, highlighting will advance that way. It's maddening !!! Is there a plist option to address this behavior ? Please help. I am on an Acer Aspire 5755-9401 running 10.8.3. TIA. bisk
  20. Aloha, Trying all versions on an Acer 5755 and get pretty much the same behavior with each. Basic pointing is fine and 2 finger scrolling works after toucing the Prefs->Scrolling Spped once. However, I am unable to grab and drag anything ! Not scrollbars, not menu bars, not desktop icons, nothing. Yes, I have the Prefs set for Clicking and Dragging but still cannot grab and drag anything most of the time. I can only advance scrollbars by clicking to a different point on the scrollwell. Every once in a great while, a drag lock will happen on a drag attempt and I never have the drag-lock option set ! Anybody else seeing this ? bisk
  21. OMG ! That's it !!! I would have never in a billion years have ever thought to set a system password and then bypass it to make this fly. Verified to do the trick on the E1505 for 10.7.5 for the most part. I don't always get the trackpad back after waking if I sleep right at the login screen but from the desktop, it seems fine. I did KP once. Stack trace started in IONetworkingFamily->IO80211Fammily but I need to simplify my DSDT to remove a bunch of test code so that might improve things. Merci mon ami !
  22. Aloha all, I'm hoping someone can shed some light on a frustrating issue that I have encountered. I have 2 very nice, nearly 100% functional HackBooks that both exhibit the exact same deficiency. They will NOT wake from sleep. I'm fairly sure that they KP on wake. Usually they just stay black screen but every once in a while, I'll get a stack trace screen. Only once was there actually a kext in the stack trace and that was IOSurface.kext. Both notebooks are ICH7 models with the Intel GMA 950 video chip. One is a Toshiba Satellite A105, Core Duo T2500, 1GB RAM, etc. and the other is a Dell Inspiron E1505, Core 2 Duo T5600, 2GB RAM, etc. Again, both have the Intel GMA 950. I have Snow Leo 10.6.8 w/ Chameleon 2-RC5-r752 on the Toshiba and Lion 10.7.5 w/ Chameleon 2.1-r1650 on the Dell. Both systems are entirely vanilla except for the usual AppleACPIPS2Nub/ApplePS2Contoller/FakeSMC in /E/E and an AppleACPIPlatform rollback to Snow Leo + VoodooTSCSync for the Dell running Lion. There are also the usual "legacy" mods to IOPlatformPluginFamily on both to get native SpeedStep as well but other than a few added kexts for audio and LAN, that's about it. Everything else works: QE, ResMan, LAN, WiFi, Audio ins and outs, SpeedStep, Sleep from the menu button and power button menu pop up and clamshell/lid but NO WAKE ! There is one other VERY KEY kext that must be changed, AppleIntelIntegratedFrameBuffer. I have found that only a couple of "patched" versions will get me a display and both seem to be all the way back from Tiger based on the version number -> 1.4.20 ! I have also found one other from Dr. Hurt versioned 1.6.6 that seems more modern but all three still end with the same result, no wake from sleep. Most of this was learned right here on this forum from the Dell Inspiron 6400 thread started by kannan. https://osxlatitude.com/index.php?/topic/2039-dell-inspiron-6400/ If I try the proper Intel FrameBuffer for the exact release of OS X that I'm running, I get a black screen with cursor. I have tried most, if not all, the FrameBuffers from 10.5.8 all the way through 10.7.5. I have tried a couple prescribed DSDT fixes, injecting GMA 950 values from the GFX0 device and removing CRT/DVI/TV devices but this makes no difference. At this point, I'm guessing that this problem is caused by the old FrameBuffer. So these are the details of my testing. Has anyone else out there gotten wake from sleep working on their notebook with GMA 950 under either 10.6.8 or 10.7.5 ? If so, please share.
×
×
  • Create New...