Jump to content

agrafuese

Members
  • Content Count

    245
  • Joined

  • Last visited


Reputation Activity

  1. Thanks
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Yes, it seems 2.3 has issues on our machines. There is also an issue thread open on alexandred's github, but I didn't report it because I'm not sure how to provide debug info in a hotpatch situation. It seems they want DSDT files to accompany error reports. If you are more knowledgeable about this kind of stuff, maybe you can add to the issue thread, here: https://github.com/alexandred/VoodooI2C/issues/231
     
     
    Very possible. At least I will believe this so that I don't feel so crazy
  2. Thanks
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Actually, it looks like I found a solution after all! 
     
    Long story short: VoodooPS2Controller was the reason behind my trackpad cursor instability, not VoodooInput. I found this out by tinkering with the plugin inside of VoodooPS2Controller, called VoodooPS2Trackpad. I used an old version of the plugin located inside my original VoodooPS2Controller to replace the newest version that was causing problems. This plugin has been removed entirely as of update #3. Read below for more info.
     
    This helped me in two ways: It stabilized my trackpad cursor movement (it is perfect now!) and now that I can use the newest version of VoodooPS2Controller (with old VoodooPS2Trackpad plugin), I have a working caps-lock LED!
     
    As long as I don’t experience any KPs, this is a big improvement all around. See update #3.
     
    For reference, here are all of the changes I've made to my kexts folder, versus the current repo for 10.14.6:
     
    • VoodooI2C.kext (using version 2.2) 
    • VoodooI2CHID.kext (satellite for I2C above)
    • VoodooInput.kext version 1.0.3 removed as of update #3 below
    • VoodooPS2Controller.kext version 2.1.2 using VoodooPS2Trackpad plugin from version 2.0.4 <--- IMPORTANT (See update #3)
     
    End Results:
     
    • Keyboard working!
    • Caps-lock LED working!
    • "~" key for ANSI layout working!
    • Trackpad working!
    • Multi-touch gestures working!
    • 4K Touchscreen (single finger) working!
    • 4k Touchscreen Multi-touch ***not working  (see update below) (working as of update #3)
    • No KPs as of this writing. Will update if this changes. Still testing for KPs.
     
    UPDATE: I later realized that VoodooInput does not enable multi-touch support for the 4k touchscreen. This is somewhat disappointing, but expected. I attempted a few workarounds for this, but no success to speak of as of yet.
     
    UPDATE 2: As I was tinkering with workarounds for the touchscreen issue, I got a startup KP from VoodooPS2Controller. It could have been triggered by what I was doing, but it is likely that I am still getting random KPs from the newest version of the kext. Time will tell...
     
    UPDATE 3: It appears VoodooPS2Controller was still causing startup KPs, specifically from the VoodooPS2Trackpad plugin. So, as a test, I have removed the plugin from inside of it entirely, and have stopped using VoodooInput as well (since it is dependent upon that plugin to work). Instead, I am now back to using VoodooI2C and VoodooI2CHID, but version 2.2 instead of 2.3 (due to KPs after wake from sleep). I have implemented some ACPI patches as recommended by the xxxzc repo to compliment VoodooI2C 2.2. The startup KPs have stopped, and VoodooI2C 2.2 does not give me KPs after wake from sleep. This is the most stable configuration so far. Will update if I experience anymore KPs.
  3. Thanks
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Actually, it looks like I found a solution after all! 
     
    Long story short: VoodooPS2Controller was the reason behind my trackpad cursor instability, not VoodooInput. I found this out by tinkering with the plugin inside of VoodooPS2Controller, called VoodooPS2Trackpad. I used an old version of the plugin located inside my original VoodooPS2Controller to replace the newest version that was causing problems. This plugin has been removed entirely as of update #3. Read below for more info.
     
    This helped me in two ways: It stabilized my trackpad cursor movement (it is perfect now!) and now that I can use the newest version of VoodooPS2Controller (with old VoodooPS2Trackpad plugin), I have a working caps-lock LED!
     
    As long as I don’t experience any KPs, this is a big improvement all around. See update #3.
     
    For reference, here are all of the changes I've made to my kexts folder, versus the current repo for 10.14.6:
     
    • VoodooI2C.kext (using version 2.2) 
    • VoodooI2CHID.kext (satellite for I2C above)
    • VoodooInput.kext version 1.0.3 removed as of update #3 below
    • VoodooPS2Controller.kext version 2.1.2 using VoodooPS2Trackpad plugin from version 2.0.4 <--- IMPORTANT (See update #3)
     
    End Results:
     
    • Keyboard working!
    • Caps-lock LED working!
    • "~" key for ANSI layout working!
    • Trackpad working!
    • Multi-touch gestures working!
    • 4K Touchscreen (single finger) working!
    • 4k Touchscreen Multi-touch ***not working  (see update below) (working as of update #3)
    • No KPs as of this writing. Will update if this changes. Still testing for KPs.
     
    UPDATE: I later realized that VoodooInput does not enable multi-touch support for the 4k touchscreen. This is somewhat disappointing, but expected. I attempted a few workarounds for this, but no success to speak of as of yet.
     
    UPDATE 2: As I was tinkering with workarounds for the touchscreen issue, I got a startup KP from VoodooPS2Controller. It could have been triggered by what I was doing, but it is likely that I am still getting random KPs from the newest version of the kext. Time will tell...
     
    UPDATE 3: It appears VoodooPS2Controller was still causing startup KPs, specifically from the VoodooPS2Trackpad plugin. So, as a test, I have removed the plugin from inside of it entirely, and have stopped using VoodooInput as well (since it is dependent upon that plugin to work). Instead, I am now back to using VoodooI2C and VoodooI2CHID, but version 2.2 instead of 2.3 (due to KPs after wake from sleep). I have implemented some ACPI patches as recommended by the xxxzc repo to compliment VoodooI2C 2.2. The startup KPs have stopped, and VoodooI2C 2.2 does not give me KPs after wake from sleep. This is the most stable configuration so far. Will update if I experience anymore KPs.
  4. Thanks
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Thanks. I just really wish I knew how to modify these kexts myself to make for a better experience on the trackpad. I don't even really know where to begin with that, but considering I2C works well (except for me) and VoodooInput doesn't cause (me) panics (and reduces number of kexts used, since I2C needs two), surely there must be a way to make a kext that is the best of both worlds. :/
  5. Like
    agrafuese got a reaction from tikizondo94 in VoodooInput performance issues   
    Well, in any case, I think I solved the problem (in testing so far), so I'll just report the solution in case anyone else comes here with the same issue (doubtful, but anyway...)
     
    It turned out that VoodooPS2Controller was the culprit, NOT VoodooInput. I had recently installed the newest versions of both, and I had assumed VoodooInput was causing the issues, because it is what makes my trackpad work (ultimately). However, I overlooked the fact that VoodooPS2Controller ALSO contributes to trackpad functionality as well. So, I fixed the problem by taking the VoodooPS2Trackpad plugin from inside VoodooPS2Controller version 2.0.4 (which was working fine), and put it inside the new VoodooPS2Controller version 2.1.2, overwriting the current one. 
     
    For anyone still reading this (unlikely!), I needed the newest VoodooPS2Controller because it fixed a capslock LED problem I was having. So, that's why I needed the best of both worlds
  6. Like
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Thanks for pointing this out. I did a text search in the tutorial for things like hda-verb, combojack, etc before I posted, but nothing came up - now I realize it was because I didn't see that the additional fixes section was on its own page. My bad. Just glad to see I'm taking all the proper steps
  7. Like
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Update for anyone reading this who may also be curious about the combo jack and headphone distortion fixes:
     
    The fix included in this tutorial/repo is great, but the install script that comes with it needs updating/re-writing. The scripting/wording in install.sh should be as follows:
     
    #!/bin/bash echo "This installer requires admin rights. Also make sure you don’t have Time Machine running or any usb stick inserted!" echo "IMPORTANT: Please remove any previous jack fixes manually before continuing. Also, remove CodecCommander.kext from your EFI kexts folder, and replace with the included VerbStub.kext." echo "Do you want to continue?" select yn in "Yes" "No"; do case $yn in Yes ) break;; No ) exit;; esac done echo "Installing local configuration" sudo cp ComboJack /usr/bin sudo chmod 755 /usr/bin/ComboJack sudo chown root:wheel /usr/bin/ComboJack sudo cp hda-verb /usr/bin sudo chmod 755 /usr/bin/hda-verb sudo chown root:wheel /usr/bin/hda-verb sudo cp com.XPS.ComboJack.plist /Library/LaunchAgents/ sudo chmod 644 /Library/LaunchAgents/com.XPS.ComboJack.plist sudo chown root:wheel /Library/LaunchAgents/com.XPS.ComboJack.plist sudo launchctl load /Library/LaunchAgents/com.XPS.ComboJack.plist sudo mkdir /usr/local/share/ sudo chmod 755 /usr/local/share/ sudo mkdir /usr/local/share/ComboJack/ sudo chmod 755 /usr/local/share/ComboJack/ sudo cp Headphone.icns /usr/local/share/ComboJack/ sudo chmod 644 /usr/local/share/ComboJack/Headphone.icns sudo cp l10n.json /usr/local/share/ComboJack/ sudo chmod 644 /usr/local/share/ComboJack/l10n.json echo echo "Please reboot! Also, it may be a good idea to turn off \"Use" echo "ambient noise reduction\" when using an input method other than" echo "the internal mic (meaning line-in, headset mic). As always: YMMV." echo echo "You can check to see if the watcher is working in the IORegistry:" echo "there should be a device named \"VerbStubUserClient\" attached to" echo "\"com_XPS_SetVerb\" somewhere within the \"HDEF\" entry's hierarchy." echo echo "Enjoy!" echo exit Essentially, I have removed any scripting that involved files or caches related to /S/L/E, since we don't generally use that type of configuration in this repo. I also added lines to create the /usr/local/share/ and /usr/local/share/ComboJack folders, as these lines were missing previously, resulting in some of the files not copying to their proper locations, and therefore the listener script was not working properly.
     
    *NOTE: I have not included scripting to automatically remove CodecCommander.kext or copy VerbStub.kext in the EFI kexts folder, because it is much safer for the user to do that manually themselves, and it is easy enough to do so. So, I added notes to remind the user to do so instead. Also, I realize that the bit about "remove previous jack fixes" is vague, but hopefully users can figure that out themselves. There are just too many variables to write a script that would satisfy all possible use case scenarios and configurations.
     
     
    *ALSO NOTE: I am not "officially" requesting that these changes be made to the repo, out of respect for any possible reasons why someone would argue against them. I am simply suggesting that these changes be reviewed in order to bring the install.sh script up to date with the way that the repo is structured. The old script was confusing and didn't work properly OOTB.
  8. Thanks
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Is it possible that your time machine is USB 2.0 and everything else is 3.0?
     
    I happened to notice in the original post of this thread that there was a change log mentioning that USBInjectAll.kext was taken out of the repo a few years ago. When looking up general hackintosh fixes for USB issues, many sources pointed at doing custom injection of hardware values into USBInjectAll. So, I wonder if there is any hope of fixing some of these problems that way by going back to USBInjectAll. I see that this repo currently uses a different USB related kext, so I wonder if the two would conflict...
     
    Anyway, golimpio, if you want stability for now, I recommend getting a simple usb hub (this is the one I use). It should fix your problems, as like I mentioned, I believe it "converts" the 3.0 to 2.0 as it passes through the hub, making connections more reliable. Not a "proper" fix, and it will likely slow transfer speeds, but it is a bandaid at least.
  9. Like
    agrafuese got a reaction from golimpio in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    That is very odd, indeed. Do you have the ability to try a different mouse and see if you still have these problems? My initial thought is maybe it has something to do with the usb dongle (especially being MS). I doubt this story is related, but I noticed that one of my usb external hard drives loses connectivity after it has been plugged in for a bit, but all of my other external hard drives are fine. It's almost as if there is something in the hardware that is less effective than the others (they are all the same version of USB) - like something in the electrical components/power management (I have no idea what I'm talking about, lol). So, maybe there is something similar happening with the usb dongle for your mouse?
×