Jump to content
  • OSXL Poll (feedback in topic)   112 members have voted

    1. 1. Do you like our site design ?


      • Yes
      • Yes, but still need some improvements
      • No, I hate it
      • Prefer old site template

    Please sign in or register to vote in this poll. View topic
  • Recent Posts

    • Hi @Amoxitine it's jpz4085 here,   After reviewing your debug files I have made the following corrections. Your model’s DSDT is very similar to mine.   I added the “Darwin” check under Method OSID you were missing. (Required for native brightness control.) I removed Device GFX0 and renamed Device VID (and references) to IGPU. That’s the correct one. I renamed Device ECDV to EC (and references) so USB power properties will load. (Not required but good to have.) I removed the XOSI hotpatches and SSDT as it’s unnecessary with the “Darwin” entries in the DSDT. I removed Intel graphics injection and audio layout ID from your config.plist as that’s already taken care of in your DSDT.   Also you can remove the AppleHDA kext patches from your config.plist if you’re only using AppleALC.kext. I’ve included the source files for the native and patched DSDT for you to customize further if needed. Copy the attached files under EFI to the correct locations on your EFI partition and see how it works for you. Dell_E5430.zip
    • Hi Hervé,   Yeah I've already been trying to use Rehabman's ACPIDebug to establish the codes, but I can't get much further than establishing the start point (_Q66) in the chain but it doesn't reach BRT6 so when I saw jpz4085's post about needing to apply the OS Check Fix to the appropriate _OSI checks I was thinking that perhaps that's the reason why I can't establish the key codes in the sys log, but with my limited knowledge that's where I've got stuck.   No worries if you can't advise any further, just thought I'd ask in case you might be able to nudge me in the right direction.
    • Hi Hervé,   Yeah I've already been trying to use Rehabman's ACPIDebug to establish the codes, but I can't get much further than establishing the start point (_Q66) in the chain but it doesn't reach BRT6 so when I saw jpz4085's post about needing to apply the OS Check Fix to the appropriate _OSI checks I was thinking that perhaps that's the reason why I can't establish the key codes in the sys log, but with my limited knowledge that's where I've got stuck.   No worries if you can't advise any further, just thought I'd ask in case you might be able to nudge me in the right direction.
    • Hi Jake Lo,   I tried all the ones in the thread Refined ALPS trackpad and didn't got any success with them after wake ... here are the results:   Test trackpad: VoodooPS2Controller-R6B10fixed 16.16.49 17.29.26: Works fine at boot Trackpad panel = ok Sleep - Wake = present on wake, on click kernel panic   VoodooPS2Controller-R6Bronxteck Touchpad not working on boot; click present, no cursor movement Track pad panel = ok Sleep - Wake = no 2018-09-24 17:34:03.888460-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Found a V8 Flare TouchPad with ID: E7=0x73 0x03 0x28, EC=0x73 0x01 0x13 2018-09-24 17:34:03.925461-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TrackStick detected... (WARNING: V8 TrackStick disabled) 2018-09-24 17:34:03.925464-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TouchPad driver started... 2018-09-24 17:41:11.136132-0400 0xe9       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid or bare packet has been dropped..   VoodooPS2Controller-R6RC2 16.08.24 Works fine on boot Trackpad panel = ok Sleep - Wake = no 2018-09-24 18:09:08.864730-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Found a V8 Flare TouchPad with ID: E7=0x73 0x03 0x28, EC=0x73 0x01 0x13 2018-09-24 18:09:08.898729-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TrackStick detected... (WARNING: V8 TrackStick disabled) 2018-09-24 18:09:08.898732-0400 0xec       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TouchPad driver started... 2018-09-24 18:19:19.888652-0400 0xea       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Found a V8 TouchPad with ID: E7=0x73 0x03 0x28, EC=0x73 0x01 0x13 2018-09-24 18:19:19.922491-0400 0xea       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TouchPad driver started... 2018-09-24 18:20:24.783944-0400 0xe8       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid packet has been dropped... 2018-09-24 18:20:24.785117-0400 0xe8       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid packet has been dropped... Huge lot of drop   VoodooPS2Controller-R6RC2 Works fine on boot Trackpad panel = ok Sleep - Wake = no 2018-09-24 18:34:22.881035-0400 0xea       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Found a V8 TouchPad with ID: E7=0x73 0x03 0x28, EC=0x73 0x01 0x13 2018-09-24 18:34:22.915208-0400 0xea       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TouchPad driver started... 2018-09-24 18:35:30.854929-0400 0xe8       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid packet has been dropped...   VoodooPS2Controllerv8 Works on boot Trackpad panel = ok Sleep - Wake = no 2018-09-24 18:48:39.836350-0400 0xe9       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Found a V8 TouchPad with ID: E7=0x73 0x03 0x28, EC=0x73 0x01 0x13 2018-09-24 18:48:39.873049-0400 0xe9       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: TouchPad driver started... 2018-09-24 18:51:33.096220-0400 0xe7       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid or bare packet has been dropped... 2018-09-24 18:51:33.097228-0400 0xe7       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: an invalid or bare packet has been dropped... 2018-09-24 18:51:33.838749-0400 0xe7       Default     0x0                  0      0    kernel: (VoodooPS2Trackpad) ALPS: Rejected trackstick packet from non DualPoint device   VoodooPS2Controller - latest from rehabman Works on boot Trackpad panel = no Sleep - Wake = yes No log show | grep ALPS      
    • The bluetooth issues got worse, now it is randomly "not available". and only way to fix it is to restart till it is back online again. Any idea what can it be?
    • For those who need an extracted copy of Mojave kernels, here are copies of the various kernels that have come out so far.
       
      I also include copies of the patched AppleIntelCPUPowerManagement kexts that are necessary on SandyBridge/IvyBridge CPUs.
       
      Patches courtesy of Pimentel and his tools as published at IM.
       
      Vanilla kernels for Core2Duo/Core2Quad, Arrandale and Sandy/Ivy Bridge CPUs: Vanilla_kernel_10.14.zip (18.0.0)   Patched kernels for Haswell, Broadwell, Skylake CPUs: N/A (Clover and Enoch can patch the vanilla kernel on the fly)   Patched AppleIntelCPUPowerManagement kexts for Sandy/Ivy Bridge CPUs: Patched_AICPUPM_10.14.zip   NB: kernels go to /System/Library/Kernels as kernel; patched AICPUPM kext goes to /System/Library/Extensions
    • Try version mentioned here No it's not an I2C trackpad, definitely PS2 Alps v8
×