Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Lockzi

  1. I have upgraded one of my location to Google WiFi. I now notice that the WiFi compatibility seem to not be as expected... It's a two story location with concreet walls with 3 Access Points. It simply refuses to connect to the closes network, and insists on 5Ghz AC connection rather then 2.4Ghz even though it gives poor connection. I remember reading before about someone else having problems with the WiFi on this configuration. Has there been any updates on that specific issue and maybe someone is interested in troubleshooting?
  2. I was able to fix the teleporting by the assistant of Alexandred at: https://github.com/alexandred/VoodooI2C/issues/113 Really awesome trackpad now!
  3. What Mac OS version are you running? I'm still on 10.13.3 due to DisplayLink driver issues.
  4. Hello Alex, I can confirm that I was using APCIBatteryManager. After disabling it I still have the same issue, so it's not even after sleep. Should I go through with the troubleshoot procedure you've listed on Github?
  5. So then I am guessing it is something with our implementation. I have not realized nor confirmed that it occurs after sleep. Interesting, will check it out. It seems like it has something to do with the GPIO pins for trackpad interrupts? Maybe I should try rolling back the GPIO patches and use VoodooI2Cs polling method instead...
  6. Hey Guys, just wanted to quickly check here before I report a bug and troubleshoot with the developer. I've switched to VoodooI2C v 2.1.4 today, and if I draw a circle with the mousepointer using the trackpad continuously I can see how it teleports in the last known direction of the circle - exactly every second, which makes it impossible to do a circle. Same thing can be observed if you slowly scroll on this page. The scroll will be jumpy at every second. I have added the DSDT files as per hvolkoff's initial discussion Is anyone else seeing this on our machines? Are everyone else still using the SSDT-I2CX.aml and SSDT-XOSI.aml from the linked post or has the development of the kext changed so it's no longer needed?
  7. I updated, but I am still on 10.13.3 No other changes for me.
  8. Same for me. Even though removing the I2C kexts it does not work. It may be due to the SSDT-XOSI or voodooPS2daemon? I have only tried the SSDT-XOSI as @goodwin_c suggested, not using the previous one with enabling later windows as @hvolkoff stated. I have tried both I2C 2.0.1 and the "10.13 beta" as included in zip file of original post by @hvolkoff . The ControllerInterrupt first two hex are "10" looking at IOReg. I've noticed that in some cases the mouse works just fine during the login screen, but shortly after logging in it stops moving, hard to do mouse clicks, essentially unusable except for scrolling. The touchscreen, however, works perfectly.
  9. Has anyone else started to experience problems with Bluetooth after sleep since High Sierra? The problem is that after wake up: It's on - but can't connect to any devices and can't be turned off (no error message or anything, just nothing happens when pushing the button). The only fix is to restart the computer. I remember that while installing I had some bcrmpatch2 errors while trying to install.
  10. Exact wording: macOS could not be installed on your computer An error occured while verifying firmware. Quit the installer to restart your computer and try again. If I recall right I opned the console and there it was a message about securityd killed all processes through sigterm due to "Firmware unsuported", but the wording above is what the installer wizard says.
  11. I had to disable (rename/remove) the EmuVariableUefi-64.efi, it apparently has to do with our NVIDIA GPUs (source: http://hackintosher.com/guides/high-sierra-fix-macos-not-installed-computer/) /dev/disk0 (internal): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme 1.0 TB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_APFS Container disk1 980.1 GB disk0s2 3: Apple_HFS Win10 43.6 GB disk0s3 I'll go along with installing win10 now through bootable USB - hoping for the best! UPDATE: There's no problem dual booting High Sierra APFS with Win10!
  12. I can not confirm by facts, exactly that is my experience based on the two re-installations I've done. Another thing I would like to add was that once the first installation failed (firmware unsupported error), I had to reformat the whole disk to HFS (from APFS) in order to get it working again. I created another partition as place holder for Windows 10 at the end of the drive. Has anyone installed Windows 10 (dual boot, not bootcamp) after High Sierra with APFS? Worried about it overwriting the partition scheme and screwing something up...
  13. Yes, i7 Got it working by removing the emuvariable driver as well as downloading the latest cover instead of the one Pandora uses. Apparently it seems like it's because of our integrated GPU.
  14. I have the exact same problem as well. Changing from Cloverx64.efi to bootx64.efi does unfortunately not work either. Doing a clean install. 4k sector, extended journal, GUID, with prepared empty partition for bootcamp. Any more ideas?
  15. So, I've figured out some more things. Slide 170 works for me when I am portable, with no cables or anything attached. Slide 196-198 works for me when I am docked with HDMI cable inserted. How should I go about finding a slide value that works for both conditions?
  16. Did not work for me, had to use a slide value of either 196 or 198 My computer has 32gb RAM, if that has anything to do with it I have however noticed that it now stays longer on the +++++++++++++++ signs than before. I am guessing that slide with as low value as possible is preferred?
  17. Suddenly my computer has stopped sleeping. When I open the lid it reboots. How would I troubleshoot this?
  18. I wonder if it's possible to have a small bash script run before graphics drivers load. I've put the sudo pmset -a hibernatemode 0 into a script that loads on boot, but if we could have a script running before graphics loads we would have solved 4K patching on upgrade as well.
  19. A word of caution! If you do the native CPU power management (not through HWPEnable), if you have an NVMe drive you will have to re-do sudo pmset -a hibernatemode 0 As in my case it was reset to hibernatemode 3 after doing this which we all know the risks of.
  20. Success!!! So here are my steps. run the install.sh from the AppleHDA syscls directory. sudo sed -i.vanilla 's/Mac-FC02E91DDD3FA6A4/Mac-A5C67F76ED83108C/g' /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist What it does is stealing Board-ID Mac-FC02E91DDD3FA6A4 and replacing it with the MBP13,3 Mac-A5C67F76ED83108C. <key>Mac-A5C67F76ED83108C</key> <string>none</string> Reload caches. Reboot I have changed the install.sh script and created a pull request. I do have a KextToPatch fix as well (NOT WORKING!) <dict><key>Comment</key> <string>Fix HDMI output MBP133 Lockzi</string> <key>Disabled</key> <true/> <key>Find</key> <string>3e4d61632d464330324539314444443346413641343c2f6b65793e</string> <key>InfoPlistPatch</key> <true/> <key>Name</key> <string>AppleGraphicsDevicePolicy</string> <key>Replace</key> <string>3e4d61632d413543363746373645443833313038433c2f6b65793e</string> </dict> 0:228 0:000 - [13]: AppleGraphicsDevicePolicy (Fix HDMI output MBP133 Lockzi) :: PlistPatch :: data len: 27 It is being applied according to boot log but it does not seem to have the same effect as manually editing the Info.plist Maybe someone could see what's wrong and help out?
  21. Do you have HDMI out working (not with USB-C adapter)?
  22. You could try to add: <key>ForceKextsToLoad</key> <array> <string>/System/Library/Extensions/AppleGraphicsControl.kext</string> <string>/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext</string> <string>\System\Library\Extensions\IONetworkingFamily.kext</string> </array> I never have understood what this actually does, yet basically every config.plist has the IONetworkingFamily.kext loaded, and it is not necissary for the kext to be loaded to do the KextsToPatch patches. However I have broken my audio completely now. I've tried both wmchris (which I had working before I went on to this whole HDMI output venture) and the syscl AppleHDA, neither work... I've also noticed that my USB Video Card (DisplayLink) is not recognized anymore... I feel like weird stuff are happening since I changed SMBIOS to MBP13,3 Even though I got HDMI out to work on MBP13,3 I am considering as well to switch back to iMac17 Update: So I spent some time in order to fix my audio trying to revert to where I was before. Guess what Deniryer, now my HDMI patch doesn't work anymore! Clearly, they are related. Further more, when I restored my audio - suddenly my USB Video card was recognized again! My best guess is that you're set up like wmchris guide: L/E> aDummyHDA.kext CodecCommander.kext S/L/E> AppleHDA.kext (vanilla) ACPI/patched/ssdt-ALC298 Correct? Then let's try to find a fix together as we're at the same startingpoint!
  23. Oh no, the patch I copied in is the same patch as wmchris linked to. As I wrote, there is no entry/configuration for our MacBookPro13,3 board-id. I have however changed the patch to add our board-ID with the configuration none (Destroys iMac13,2 configuration) Find: >Mac-B809C3757DA9BB8D</key> <string>none</string> Replace: >Mac-A5C67F76ED83108C</key> <string>none</string> <dict> <key>Comment</key> <string>Fix HDMI output MBP133 Lockzi</string> <key>Disabled</key> <false/> <key>Find</key> <string>3e4d61632d423830394333373537444139424238443c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string> <key>InfoPlistPatch</key> <true/> <key>Name</key> <string>AppleGraphicsDevicePolicy</string> <key>Replace</key> <string>3e4d61632d413543363746373645443833313038433c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string> </dict> Unfortunately this does not work for me anyhow. I have also tried with adding the "PublishHDMI_DP" to aDummyHDA (http://www.insanelymac.com/forum/topic/319211-guide-fix-skylake-hdmidp-output/?p=2333909) yet it doesn't work and breaks audio. I am on BIOS v 1.2.19 which has the change log: "1.Fixed Pre-OS has no display on external monitor with Lid Close issue" Maybe it also broke something? UPDATE: --Read from here -- Allright got it working! The fix is to simply use the patch I provided. <dict> <key>Comment</key> <string>Fix HDMI output MBP133 Lockzi</string> <key>Disabled</key> <false/> <key>Find</key> <string>3e4d61632d423830394333373537444139424238443c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string> <key>InfoPlistPatch</key> <true/> <key>Name</key> <string>AppleGraphicsDevicePolicy</string> <key>Replace</key> <string>3e4d61632d413543363746373645443833313038433c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string> </dict> Do NOT add the PublishHDMI_DP to aDummyHDA.kext. I now have MBP13,3 SMBIOS with HDMI out working.
  24. So, I had 15 minutes over and had another look. The KextPatch: <dict> <key>Comment</key> <string>Fix HDMI output</string> <key>Find</key> <string>3e4d61632d423830394333373537444139424238443c2f6b65793e0a090909093c737472696e673e436f6e666967323c2f737472696e673e0a09</string> <key>InfoPlistPatch</key> <true/> <key>Name</key> <string>AppleGraphicsDevicePolicy</string> <key>Replace</key> <string>3e4d61632d423830394333373537444139424238443c2f6b65793e0a090909093c737472696e673e6e6f6e653c2f737472696e673e0a09090909</string> </dict> Is not useful at all and I can't believe I didn't cach that before. What it does is the same as going manually into the kext and changing Config2 to none. Search: >Mac-B809C3757DA9BB8D</key> <string>Config2</string> Replace: >Mac-B809C3757DA9BB8D</key> <string>none</string> As the board-ID with SMBIOS MacBookPro13,3 is: Mac-A5C67F76ED83108C it has no effect. Also as I stated initially there is no setup for Mac-A5C67F76ED83108C in the AppleGraphicsPolicies kext. What I haven't tested yet is to actually add: <key>Mac-A5C67F76ED83108C</key> <string>none</string> Since MBP13,3 does not have HDMI output, that just might be the right fix! I'll check that out later.