[GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation

[agrafuese]

...and of course the good came with the bad...

 

Just got my first kernel panic a moment ago while booting up, and I think it was from voodoops2controller (see below for output from Crash Reporter). 

 

This is the first time it has happened in about 5-10 reboots since installing the newest kexts from repo and the latest Apple security update. I've rebooted twice so far since the panic, and that has been fine. So, this could be a random occurrence. I will report back if it worsens.

 

*** Panic Report ***
panic(cpu 0 caller 0xffffff800aedc9bd): Kernel trap at 0xffffff7f8e73aca8, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000023ba1000, CR4: 0x00000000003626e0
RAX: 0xfa424d5d87c8003d, RBX: 0xffffff8040e84000, RCX: 0x0000000000000008, RDX: 0xffffff7f8e742470
RSP: 0xffffff81ff7b3d60, RBP: 0xffffff81ff7b3d70, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8:  0xffffff81be441200, R9:  0xffffff81be4411fc, R10: 0xffffff81be441000, R11: 0x0000000000000000
R12: 0xffffff8042292d50, R13: 0xffffff8042292d58, R14: 0xffffff80420db800, R15: 0xffffff8042292d00
RFL: 0x0000000000010286, RIP: 0xffffff7f8e73aca8, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff81ff7b3830 : 0xffffff800adaf57d 
0xffffff81ff7b3880 : 0xffffff800aeeb065 
0xffffff81ff7b38c0 : 0xffffff800aedc79a 
0xffffff81ff7b3930 : 0xffffff800ad5c9d0 
0xffffff81ff7b3950 : 0xffffff800adaef97 
0xffffff81ff7b3a70 : 0xffffff800adaede3 
0xffffff81ff7b3ae0 : 0xffffff800aedc9bd 
0xffffff81ff7b3c50 : 0xffffff800ad5c9d0 
0xffffff81ff7b3c70 : 0xffffff7f8e73aca8 
0xffffff81ff7b3d70 : 0xffffff800b42baaa 
0xffffff81ff7b3dc0 : 0xffffff800b4374bb 
0xffffff81ff7b3df0 : 0xffffff7f8e73a531 
0xffffff81ff7b3e20 : 0xffffff7f8e741d5d 
0xffffff81ff7b3e40 : 0xffffff800b42f6cb 
0xffffff81ff7b3e80 : 0xffffff800b42f385 
0xffffff81ff7b3f00 : 0xffffff800b42e947 
0xffffff81ff7b3f50 : 0xffffff800b430436 
0xffffff81ff7b3fa0 : 0xffffff800ad5c0ce 
      Kernel Extensions in backtrace:
         as.acidanthera.voodoo.driver.PS2Trackpad(2.0.4)[CFDA888E-E3F7-3220-BE69-F6C46E719297]@0xffffff7f8e739000->0xffffff7f8e748fff
            dependency: as.acidanthera.voodoo.driver.PS2Controller(2.0.4)[E2927F57-AEFE-372E-ACAD-19C77D1D69E9]@0xffffff7f8e6d0000
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[CCEA17E9-B816-3148-AFF1-E43E46E1C37B]@0xffffff7f8bc0e000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 nv_disable=1 agdpmod=vit9696 -v brcmfx-country=#a darkwake=no -lilubetaall kext-dev-mode=1 

Mac OS version:
18G1012

Kernel version:
Darwin Kernel Version 18.7.0: Sat Oct 12 00:02:19 PDT 2019; root:xnu-4903.278.12~1/RELEASE_X86_64
Kernel UUID: DFB5D0E2-3B41-3647-A48B-D704AFCC06B4
Kernel slide:     0x000000000aa00000
Kernel text base: 0xffffff800ac00000
__HIB  text base: 0xffffff800ab00000
System model name: MacBookPro13,3 (Mac-A5C67F76ED83108C)

System uptime in nanoseconds: 6834762454
last loaded kext at 3353261784: com.apple.driver.AppleActuatorDriver	2450.1 (addr 0xffffff7f8df64000, size 61440)
loaded kexts:
com.alexandred.VoodooI2CHID	1
com.no-one.BrcmPatchRAM2	2.2.10
com.no-one.BrcmFirmwareStore	2.2.10
com.metakine.handsoff.driver	4.2.1
as.acidanthera.voodoo.driver.PS2Mouse	2.0.4
as.acidanthera.voodoo.driver.PS2Trackpad	2.0.4
as.acidanthera.voodoo.driver.PS2Keyboard	2.0.4
org.rehabman.driver.FakePCIID	1.3.15
ru.joedm.SMCSuperIO	1.0.2
com.alexandred.VoodooI2C	2.2
org.coolstar.VoodooGPIO	1.1
as.acidanthera.voodoo.driver.PS2Controller	2.0.4
as.vit9696.SMCProcessor	1.0.2
xyz.racermaster.NoTouchID	1.0.1
as.lvs1974.AirportBrcmFixup	1.1.9
as.vit9696.AppleALC	1.3.6
org.tw.CodecCommander	2.7.1
as.vit9696.WhateverGreen	1.2.7
ru.usrsse2.SMCBatteryManager	1
org.vanilla.driver.CPUFriend	1.1.6
ru.usrsse2.SMCLightSensor	1
as.vit9696.VirtualSMC	1.0.2
as.vit9696.Lilu	1.3.5
com.alexandred.VoodooI2CServices	1
com.apple.driver.AppleTopCaseHIDEventDriver	138.4
com.apple.driver.AppleFileSystemDriver	3.0.1
com.apple.driver.AppleVirtIO	2.1.3
com.apple.filesystems.hfs.kext	407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
com.apple.BootCache	40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
com.apple.AppleSystemPolicy	1.0
com.apple.driver.AppleSmartBatteryManager	161.0.0
com.apple.filesystems.apfs	945.275.8
com.apple.driver.AirPort.BrcmNIC	1400.1.1
com.apple.driver.AppleAHCIPort	329.260.5
com.apple.driver.AppleACPIEC	6.1
com.apple.driver.AppleRTC	2.0
com.apple.driver.AppleACPIButtons	6.1
com.apple.driver.AppleHPET	1.8
com.apple.driver.AppleBacklight	170.12.12
com.apple.driver.AppleSMBIOS	2.1
com.apple.driver.AppleAPIC	1.7
com.apple.nke.applicationfirewall	202
com.apple.security.TMSafetyNet	8
com.apple.driver.AppleActuatorDriver	2450.1
com.apple.driver.AppleHSBluetoothDriver	138.4
com.apple.driver.IOBluetoothHIDDriver	6.0.14d3
com.apple.iokit.IOBluetoothFamily	6.0.14d3
com.apple.driver.AppleMultitouchDriver	2450.1
com.apple.driver.AppleInputDeviceSupport	2440.2
com.apple.driver.AppleUSBAudio	315.6
com.apple.driver.usb.IOUSBHostHIDDevice	1.2
com.apple.driver.usb.cdc	5.0.0
com.apple.driver.usb.networking	5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
com.apple.iokit.IOSerialFamily	11
com.apple.filesystems.hfs.encodings.kext	1
com.apple.driver.AppleUSBMergeNub	900.4.2
com.apple.driver.AppleUSBHostMergeProperties	1.2
com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
com.apple.iokit.IOUSBFamily	900.4.2
com.apple.driver.AppleXsanScheme	3
com.apple.iokit.IOAHCIBlockStorage	301.270.1
com.apple.driver.AppleEFINVRAM	2.1
com.apple.iokit.IO80211Family	1200.12.2
com.apple.driver.mDNSOffloadUserClient	1.0.1b8
com.apple.driver.corecapture	1.0.4
com.apple.driver.AppleEFIRuntime	2.1
com.apple.driver.AppleIntelLpssI2C	3.0.60
com.apple.driver.AppleIntelLpssGspi	3.0.60
com.apple.iokit.IOAHCIFamily	288
com.apple.driver.usb.AppleUSBXHCIPCI	1.2
com.apple.driver.usb.AppleUSBXHCI	1.2
com.apple.iokit.IOHIDFamily	2.0.0
com.apple.driver.AppleBacklightExpert	1.1.0
com.apple.iokit.IONDRVSupport	530.51
com.apple.iokit.IOGraphicsFamily	530.67
com.apple.security.quarantine	3
com.apple.security.sandbox	300.0
com.apple.kext.AppleMatch	1.0.0d1
com.apple.iokit.IOAudioFamily	206.5
com.apple.vecLib.kext	1.2.0
com.apple.iokit.IOSMBusFamily	1.1
com.apple.driver.DiskImages	493.0.0
com.apple.driver.AppleFDEKeyStore	28.30
com.apple.driver.AppleEffaceableStorage	1.0
com.apple.driver.AppleKeyStore	2
com.apple.driver.AppleUSBTDM	456.260.3
com.apple.driver.AppleMobileFileIntegrity	1.0.5
com.apple.iokit.IOUSBMassStorageDriver	145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice	408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily	408.250.3
com.apple.iokit.IOStorageFamily	2.1
com.apple.kext.CoreTrust	1
com.apple.driver.AppleCredentialManager	1.0
com.apple.driver.KernelRelayHost	1
com.apple.iokit.IOUSBHostFamily	1.2
com.apple.driver.usb.AppleUSBCommon	1.0
com.apple.driver.AppleBusPowerController	1.0
com.apple.driver.AppleSEPManager	1.0.1
com.apple.driver.IOSlaveProcessor	1
com.apple.iokit.IOReportFamily	47
com.apple.iokit.IOTimeSyncFamily	740.2
com.apple.iokit.IONetworkingFamily	3.4
com.apple.driver.AppleACPIPlatform	6.1
com.apple.driver.AppleSMC	3.1.9
com.apple.iokit.IOPCIFamily	2.9
com.apple.iokit.IOACPIFamily	1.4
com.apple.kec.pthread	1
com.apple.kec.Libm	1
com.apple.kec.corecrypto	1.0

EOF

 

[Krim404]

kernel panics with voodoops2 are rare, but they happen.

Hopefully the new version will not result in more KPs than before. @agrafuese please keep us updated

 

[dmeister]

On 10/31/2019 at 8:16 PM, golimpio said:

FIY: Updated to 10.15.1 without any issues so far. Also updated to the latest BIOS (1.11.2), but it doesn't make any difference for this specific MacOS update, I've done it just to keep the system updated and also for testing it.

Hi, I have no issues installing 10.14.6 on my 9550.  I followed the guide for installing 1015.1 using the files provided here but never get to the 10.15.1 installer.  It just freezes on the console screen. I even tried creating another partition and trying to install to from my 10.14.6 install.  Same result.  'What did you do to get 10.15.1 installed?  Thanks.

[golimpio]

22 hours ago, dmeister said:

Hi, I have no issues installing 10.14.6 on my 9550.  I followed the guide for installing 1015.1 using the files provided here but never get to the 10.15.1 installer.  It just freezes on the console screen. I even tried creating another partition and trying to install to from my 10.14.6 install.  Same result.  'What did you do to get 10.15.1 installed?  Thanks.

I had 10.15 installed before and just did the normal macOS upgrade to 10.15.1. Same for 10.15, I had 10.14.? installed, and did an upgrade to 10.15 via the macOS Software Update.

[Rajveer86]

I upgraded to MacOS 10.15.1 without any issues, and just wanted to say thanks to everybody who keeps this post and the github archive updated. I've had this Hackintosh working perfectly for the last 1.5 years with upgrades being ridiculously easy to perform because of your efforts, and I am very thankful

[agrafuese]

On 11/15/2019 at 4:02 AM, wmchris said:

kernel panics with voodoops2 are rare, but they happen.

Hopefully the new version will not result in more KPs than before. @agrafuese please keep us updated

 

@wmchris Came back to report 2 more KPs from voodoops2controller - one last night and one this morning, same exact error report as previously posted. It happens on boot up, and I can't figure out any reason for it. I should also reiterate that before I installed this version of the repo, my keyboard (and very rarely trackpad) would not work sometimes upon boot up, forcing me to reboot and try again. So, it's almost as if I traded that problem for the KPs. Could it be that I have slightly different hardware? My 9550 is the 4k touchscreen version, if that matters? Let me know if I can assist with anymore info.

 

@wmchris ...and two more today.

Edited November 19, 2019 by agrafuese

[golimpio]

*EDITED:* original message deleted (the issue reported didn't exist).

Edited November 22, 2019 by golimpio

[Krim404]

On 11/18/2019 at 7:53 PM, agrafuese said:

@wmchris Came back to report 2 more KPs from voodoops2controller - one last night and one this morning, same exact error report as previously posted. It happens on boot up, and I can't figure out any reason for it. I should also reiterate that before I installed this version of the repo, my keyboard (and very rarely trackpad) would not work sometimes upon boot up, forcing me to reboot and try again. So, it's almost as if I traded that problem for the KPs. Could it be that I have slightly different hardware? My 9550 is the 4k touchscreen version, if that matters? Let me know if I can assist with anymore info.

 

@wmchris ...and two more today.

Damn. Sadly I can’t reproduce this. Take a look at the voodoops2 drivers and maybe install older versions or from different forks. Maybe you can find a Version with less bugs. Please keep us updated.

 

The other reported issues (had to reboot because keyboard was not responding) were an issue which was so rare, it didn’t require a fix, just a quick reboot

[golimpio]

On 11/19/2019 at 9:03 AM, golimpio said:

There was one issue on 10.15.1 that I haven't noticed before:

• Connecting to bluetooth devices was not working, even though the devices were showing up on the list.

I've just upgrade: BrcmFirmwareData.kext and BrcmBluetoothInjector.kext to the latest version (2.5.0) and it's working now (BrcmPatchRAM3.kext was already updated).

There was nothing wrong with the files in the repository, they were all updated to the correct version already. It was my mistake, I did something wrong while copying these files. I apologise for not having double checked it before posting here.

Edited November 22, 2019 by golimpio

[agrafuese]

On 11/22/2019 at 1:27 PM, wmchris said:

Damn. Sadly I can’t reproduce this. Take a look at the voodoops2 drivers and maybe install older versions or from different forks. Maybe you can find a Version with less bugs. Please keep us updated.

 

The other reported issues (had to reboot because keyboard was not responding) were an issue which was so rare, it didn’t require a fix, just a quick reboot

 

Thanks for trying. On a possibly unrelated note, I'm finally going to try to fix the "couldn't allocate" error that I've also been having (needs the slide fix, I think), and I'm hoping that it somehow magically fixes the problems I'm having with the voodoo2controller kext. In my case, the previous problem of the keyboard not working was just as recurring as this KP is now, so reverting back to that older kext would only get me so far. I'll report back if the slide fix gets me anywhere. Slide fix did not work.

Edited December 2, 2019 by agrafuese

[Mr.C]

New System BIOS released 18 Nov 2019:
Fixes:
- Fixed the issue where the mouse lags when the Dell TB16 dock is unplugged or plugged in.
- Fixed the issue where the screen does not display content when the lid is opened and closed repeatedly.
- Firmware updates to address security advisory INTEL-SA-00213 (CVE-2019-0086, CVE-2019-0091, CVE-2019-0092, CVE-2019-0093, CVE-2019-0094 and CVE-2019-0096)
- Firmware updates to address security advisories INTEL-SA-00233(CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 and CVE-2019-11091)
- Removed the preboot Intel RST Manager Optimized Defaults option.
- Fixed the issue where the BitLocker prompts for recovery. It occurs when Auto Power On option in BIOS setup is set to wake up the system at a specific time.

Enhancements:
- Modified battery algorithm to prolong lifespan and minimize risk of swelling.

 

-----

Didn't try yet

[golimpio]

11 hours ago, Mr.C said:

New System BIOS released 18 Nov 2019:
Fixes:
- Fixed the issue where the mouse lags when the Dell TB16 dock is unplugged or plugged in.
- Fixed the issue where the screen does not display content when the lid is opened and closed repeatedly.
- Firmware updates to address security advisory INTEL-SA-00213 (CVE-2019-0086, CVE-2019-0091, CVE-2019-0092, CVE-2019-0093, CVE-2019-0094 and CVE-2019-0096)
- Firmware updates to address security advisories INTEL-SA-00233(CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 and CVE-2019-11091)
- Removed the preboot Intel RST Manager Optimized Defaults option.
- Fixed the issue where the BitLocker prompts for recovery. It occurs when Auto Power On option in BIOS setup is set to wake up the system at a specific time.

Enhancements:
- Modified battery algorithm to prolong lifespan and minimize risk of swelling.

 

-----

Didn't try yet

I've updated to this BIOS about a week ago and it's stable in my laptop. I don't have a dock though, so I can't comment on the mouse lags issue.

[tev66]

So I just did a fresh install of MacOs 10.15.1 and had previously had 10.14 working on my system for the last year. After following the 10.15 tutorial I have my MacOs bootable on clover but not my windows. I am able to see my windows efi in clover. When I select and try to boot into windows, I get a blue screen error saying device is not available (error 0xc0000001). I am able to use older clovers and boot fine into my windows, but then I am unable to boot my Catalina MacOs. I am also able to manually boot windows via my bios. So I'm pretty sure it is something on clover's end... would anyone know what I need to change/do?

[sangra4l]

Hi,
I followed the guide before to install on my xps 15 osx 10.13.3.
Now i'm trying to do a fresh install of catalina but when i try to boot from usb my drive loads the new clover but it doesn't list the osx installer, only the boot from my ssd and the recovery.

Can anyone guide me to fix this issue?
Thanks

[chilmeat]

hai 

I have catalina installed on my 9550(4K、I7、32GB RAM)

I found the touchscreen Only one finger operation can be realized,other finger operation not work

but the Touch pad work well

the kext(VoodooI2C、VoodooI2CHID) in Clover

please give me  some suggestions ?

[sangra4l]

On 12/3/2019 at 2:13 PM, sangra4l said:

Hi,
I followed the guide before to install on my xps 15 osx 10.13.3.
Now i'm trying to do a fresh install of catalina but when i try to boot from usb my drive loads the new clover but it doesn't list the osx installer, only the boot from my ssd and the recovery.

Can anyone guide me to fix this issue?
Thanks

Hi,

I've done some tests to try and overcome this problem.
The version of macos that i downloaded from the appstore is the 10.15.1.
I've tried installing different versions of clover (the one included in this repository 4972, and the latest version 5099).
What i've found is that for me there is no way to make the clover in my thumbdrive list the install partition in the thumbdrive itself.
I've tried installing the clover versions and not overwrite the files in the EFI partition with the ones provided in this repository, and i've tried overwriting them with no success.
The strange thing is that i've tried to perform the whole process using the latest Mojave install file (10.14.6) and with both versions of clover they show the install partition only if i don't overwrite any file from the EFI partition.

[Krim404]

On 12/3/2019 at 7:09 AM, tev66 said:

So I just did a fresh install of MacOs 10.15.1 and had previously had 10.14 working on my system for the last year. After following the 10.15 tutorial I have my MacOs bootable on clover but not my windows.

 

wrong forum. This is a general problem using clover. Read the topics there or/and use google.

https://www.insanelymac.com/forum/327-clover/

 

On 12/3/2019 at 2:13 PM, sangra4l said:

Hi,
I followed the guide before to install on my xps 15 osx 10.13.3.
Now i'm trying to do a fresh install of catalina but when i try to boot from usb my drive loads the new clover but it doesn't list the osx installer, only the boot from my ssd and the recovery.

you created the usb installer the wrong way. No support for this issue, as this can be interpreted as piracy. Use google. Hint: many times the app store doesnt download a full installation image. If you use this as the base image, then it's not bootable. Use a different approach.

 

12 hours ago, chilmeat said:

hai 

I have catalina installed on my 9550(4K、I7、32GB RAM)

I found the touchscreen Only one finger operation can be realized,other finger operation not work

but the Touch pad work well

the kext(VoodooI2C、VoodooI2CHID) in Clover

please give me  some suggestions ? 

> https://github.com/alexandred/VoodooI2C

Edited December 5, 2019 by wmchris

[sangra4l]

3 hours ago, wmchris said:

you created the usb installer the wrong way. No support for this issue, as this can be interpreted as piracy. Use google. Hint: many times the app store doesnt download a full installation image. If you use this as the base image, then it's not bootable. Use a different approach.

 

Hi,

thanks for the reply.

I've created the usb installer the way that is written in the repository that is linked in the first page of this thread.

As I said in the previous post, using the Mojave installer I can create a working boot drive, but if I overwrite the files in the EFI partition of the drive with the ones in the repository (./10.15/CLOVER) the boot drive is not listed anymore in clover, I see only my ssd and the recovery.

 

I've read multiple guides and multiple fixes but nothing seems to work.

I'm already grateful for your work because I have a working hackintosh and I'm sorry but I can't understand the piracy argument.

 

[Krim404]

22 hours ago, sangra4l said:

 

Hi,

thanks for the reply.

I've created the usb installer the way that is written in the repository that is linked in the first page of this thread.

As I said in the previous post, using the Mojave installer I can create a working boot drive, but if I overwrite the files in the EFI partition of the drive with the ones in the repository (./10.15/CLOVER) the boot drive is not listed anymore in clover, I see only my ssd and the recovery.

 

I've read multiple guides and multiple fixes but nothing seems to work.

I'm already grateful for your work because I have a working hackintosh and I'm sorry but I can't understand the piracy argument.

 

 

10.15 sometimes needs a different approach to download the OS Base Image. The images from the app store look like normal images, but are not bootable on its own. You can identify this by looking at the size of the image. Just take a look in this thread, this happened a few people here before.

 

Helping you there could be interpreted as illegal download of copyrighted content.

Edited December 6, 2019 by wmchris

[sangra4l]

24 minutes ago, wmchris said:

 

10.15 sometimes needs a different approach to download the OS Base Image. The images from the app store look like normal images, but are not bootable on its own. You can identify this by looking at the size of the image. Just take a look in this thread, this happened a few people here before.

 

Helping you there could be interpreted as illegal download of copyrighted content.

 

Ok thanks,

 

but what about the fact that when i change the files in clover the bootable installer of Mojave disappears?

Seems to me that i can't understand what to do with those.

 

[sangra4l]

21 hours ago, sangra4l said:

 

Ok thanks,

 

but what about the fact that when i change the files in clover the bootable installer of Mojave disappears?

Seems to me that i can't understand what to do with those.

 

 

I've done some more testing.

I have created a bootable Catalina usb drive that is listed in clover correctly until I switch the config.plist in the stock clover with the one found in the GitHub repository.

I don't know what can be causing the problem but I'm sure is in that file.

 

[Krim404]

On 12/7/2019 at 4:04 PM, sangra4l said:

 

I've done some more testing.

I have created a bootable Catalina usb drive that is listed in clover correctly until I switch the config.plist in the stock clover with the one found in the GitHub repository.

I don't know what can be causing the problem but I'm sure is in that file.

 

then please take a deeper look into it. merge it line by line till it's not booting anymore.

[golimpio]

I've updated to macOS 10.15.2. The only issue I had so far was the trackpad that wasn't working.

This wasn't the first time that it happened, and usually after a couple of reboots the trackpad would start working again. This time it took more than a few boots, I've updated a few kexts just in case, but I can't confirm if the trackpad started working again because I've updated the kexts or it was "magic" like in the other times. I can confirm that updating VoodooPS2Controller.kext had no effect in the mouse issue though.

[golimpio]

For some reason insanelymac search is not working for me, so forgive me if I'm asking something that was discussed before. Why do we use VoodooI2C + VoodooI2CHID?

For trackpad, VoodooPS2Controller + VoodooInput seem to work well. I'm just wondering if we need VoodooI2C for something else than the trackpad. Thanks!

[Krim404]

12 hours ago, golimpio said:

For some reason insanelymac search is not working for me, so forgive me if I'm asking something that was discussed before. Why do we use VoodooI2C + VoodooI2CHID?

For trackpad, VoodooPS2Controller + VoodooInput seem to work well. I'm just wondering if we need VoodooI2C for something else than the trackpad. Thanks!

1st: the reboot is required to make the trackpad work, because the required files are patched after the first run and they need a reboot to get loaded. not the best solution, but it's working. Strange that you need more than one restart this time. I think i should add this information in the tutorial. :-)

2nd: The touchscreen of the 4K model is also part of I2C.

Edited December 11, 2019 by wmchris