Jump to content


  • Content Count

  • Joined

  • Last visited

About hvolkoff

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey man, I completely understand your point (even though I disagree with some of what you said about the license and the iOS Jailbreak community, but that is off-topic...). However I do want to clarify that when I released the binary of the native branch my only intention was to bring awareness of the future capabilities of VoodooI2C. Even though I have to agree that it was wrong of me to put a beta label on it when it was not even close to a minimum stable version. Anyway thank you for all the work you have done on it and I hope it get's event better in the future.
  2. Hun? That is weird. I don't think neither SSDT-XOSI nor voodooPS2daemon should cause any incompatibilities with I2C. Could you plz provide you system IOReg and logs?
  3. Done, already removed it from the attachment. Sorry if it caused any troubles, wasn't my intention. However, I do have to point out that you actually gave permission to your software distribution when you released it under GNU GPL3, as per section 6.d. Maybe you want to revise the license?
  4. Damn, thanks man. I totally forgot about adding that to the post... I too did have to make changes in SSDT-XOSI, but I only had to add the newer "windows" identifiers to it. Do you mind explaining what the CNT1 bit is about?
  5. Hi, I don't know cause I don't have a 9560 and also don't have access to one's DSDT. But it may work, considering that some of my config is derived from @KNNSpeed's files, and I made very few changes to make them compatible with 9550. Well... I got say that I don't understand much of how that works as well, hahaha. But, from our device DSDT you can see that in the _SB.PCI0.I2C1 bus there are two devices declared: Scope (_SB.PCI0.I2C1) { Device (TPD1) { Name (HID2, Zero) Name (SBFB, ResourceTemplate () { I2cSerialBusV2 (0x002C, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PCI0.I2C1", 0x00, ResourceConsumer, , Exclusive, ) }) ... } Device (TPL1) { Name (HID2, Zero) Name (SBFB, ResourceTemplate () { I2cSerialBusV2 (0x004C, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.PCI0.I2C1", 0x00, ResourceConsumer, _Y29, Exclusive, ) }) ... } ... } TPD1 is the touchpad TPL1 should be the touchscreen However if you check IOReg with VoodooI2C enabled: You can see that under I2C1 there is only TPD1 (touchpad), and on the USB controller there are some I2C nodes for the Touchscreen. So, maybe, the TPL1 device is acting as some kind of bridge between the two interfaces or something. But that is just me guessing based on my currently limited knowledge of I2C. Yeah physical clicks are acting weird for me too on Native and I am experience some random crashes on startup.
  6. So, my post was deleted due to the forum's recent changes... Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen) More info about VoodooI2C here (thanks @alexandred for the great work) Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`: <dict> <key>Comment</key> <string>change GPI0 device _STA to XSTA</string> <key>Disabled</key> <false/> <key>Find</key> <data>X1NUQQCgCZNTQlJHAA==</data> <key>Replace</key> <data>WFNUQQCgCZNTQlJHAA==</data> </dict> <dict> <key>Comment</key> <string>change I2C devices _CRS to XCRS</string> <key>Disabled</key> <false/> <key>Find</key> <data>X0NSUwCgDg==</data> <key>Replace</key> <data>WENSUwCgDg==</data> </dict> Copy the SSDT-I2CX.aml and SSDT-XOSI.aml(thanks @goodwin_c) files inside the attached zip to `CLOVER > ACPI > patched` Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here) Reboot and that's it. Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus. P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C. P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. (Removed per author's request, if you want to know more about this version go here) I2C.zip
  7. New bios 1.2.29: http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=F7M6G&fileId=3696502830&osCode=WT64A&productCode=xps-15-9550-laptop&languageCode=en&categoryId=BI
  8. Yeah, that is probably right, simpler problem than I thought... @the_voicer u can use CoreDisplayPatcher if u don't want to patch it at every update
  9. Currently no, our laptop use Optimus, and there is no built-in support for it on macOS, we would need something like FakeSMC.kext, but for the Optimus, which is reasonably hard to make, and probably a custom driver to enable it, and as far as I know no one is working on this.
  10. You probably need IntelGraphicsFixup.kext. there were some Intel graphics changes on the recently sierra updates. Just add this two kexts to your /kext/Other clover folder: https://github.com/vit9696/Lilu/releases/download/1.1.5/1.1.5.RELEASE.zip https://sourceforge.net/projects/intelgraphicsfixup/files/Release/IntelGraphicsFixup_1.1.5.kext.zip/download And see if this solve the boot problem.
  11. Hello, Just to let anyone having problems with their audio know, @KNNSpeed just released a new solution for it on the XPS15 9560 thread. I test it on my XPS15 9550 and it is fully compatible (Both the 9560 and 9550 share the same codec), it replaces the CodecCommander kext and the ALCPlugFix, with his VerbStub kext, which solve all sound related problems our machines were facing (Sleep and Line-in for me). If anyone else want to test link is here: http://www.insanelymac.com/forum/topic/324366-dell-xps-15-9560-4k-touch-1tb-ssd-32gb-ram-100-adobergb​/page-6#entry2458025 P.S: His solution works alongside AppleALC and Lilu, and, although, his post says it needs a modded version of it, @vit9696 already merged his changed on the official AppleALC repo, so you can grab the latest version from there: (https://github.com/vit9696/AppleALC), you will need to compiled it thought.
  12. Hi, I recently noticed an ACPI error in my logs that pops up everytime I plug/unplug my charger. 2017-06-22 15:05:21.843678-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843697-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843718-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.H_EC.CHRG] 2017-06-22 15:05:21.843721-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.PCI0.LPCB.H_EC.CHRG] 2017-06-22 15:05:21.843726-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-22 15:05:21.843729-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Namespace lookup failure, AE_NOT_FOUND 2017-06-22 15:05:21.843735-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-22 15:05:21.843738-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psargs-1d1) 2017-06-22 15:05:21.843759-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843761-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843766-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-22 15:05:21.843770-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-22 15:05:21.843775-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\PNOT] (Node ffffff80419a9050) 2017-06-22 15:05:21.843778-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\PNOT] (Node ffffff80419a9050) 2017-06-22 15:05:21.843781-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-22 15:05:21.843784-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-22 15:05:21.843802-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-22 15:05:21.843805-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-22 15:05:21.843811-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843814-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error: 2017-06-22 15:05:21.843818-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-22 15:05:21.843821-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> Method parse/execution failed 2017-06-22 15:05:21.843826-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.ADP1._PSR] (Node ffffff80419be890) 2017-06-22 15:05:21.843843-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> [\_SB_.ADP1._PSR] (Node ffffff80419be890) 2017-06-22 15:05:21.843847-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-22 15:05:21.843849-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> , AE_NOT_FOUND 2017-06-22 15:05:21.843854-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-22 15:05:21.843857-0300 localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> (20140828/psparse-270) 2017-06-22 15:05:21.843886-0300 localhost kernel[0]: (ACPIBatteryManager) ACPIBatteryManager: ACPIACAdapter: ACPI method _PSR failed It seems some guy filed a bug report for ubuntu (XPS 9350) for something similar, although the error happened when he unplugged his monitor through USB type-c. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574044/ I also found some people complaining about this error on other Dell computers in the Arch and Dell forums. https://bbs.archlinux.org/viewtopic.php?id=205147&p=5 (XPS 9350) http://en.community.dell.com/techcenter/os-applications/f/4457/t/20006889 (Precision 5510) Wanted to know if anyone knows something about it.
  13. The only config.plist you should ever need to modify, as far as I know, is the EFI/EFI/CLOVER/config.plist.
  14. I recommend following this guide: https://www.reddit.com/r/hackintosh/comments/525dsb/getting_imessage_working_on_el_capitan_and_sierra/ Even if you are not going to use iMessage or Face Time. I had an account blocked with this laptop only using App Store, because i didn't have the correct info set up.