[Guide] Dell XPS 13 9350 macOS 10.12.1

[RehabMan]

I apologize upfront for the noobie question, but I'm trying to build a kext using Rehabman's Github for Voodoo PS2. I have Xcode and opening the folder and simply building it, but it doesn't seem to be working correctly. Any suggestions on how to successfully build it with the most recent changes that were committed?

No need to build it as there are pre-built kexts provided. See README.
If you're building it for some other reason (wish to make changes), your post is rather off-topic and you should open a separate thread.

 

[Silence720]

VoodooPS2 1.8.25 works really great now.
Sharing my own tweaks for Dell XPS9350.

* added momentum horizontal scroll
* detect 4 fingers, instead of three fingers for swipes
* 3 finger drag (from tluck's fork)
* jittery pointer hack for my laptop (or maybe for all XPS13)

https://github.com/icedman/OS-X-Voodoo-PS2-Controller

Edit: removed kext.zip, bugs. just build from source if you wish to use

Hi - Can you include kext? I can't seem to build it properly and would appreciate your help! Thanks.

 

[Silence720]

Thanks. I will give it a try.

That worked. I have been stable with your suggested changes. Let me know when you have v3 and I will give it a try.

 

[Silence720]

Th


That worked. I have been stable with your suggested changes. Let me know when you have v3 and I will give it a try.

Same issue just occurred. I have an hitachi drive running i7-6560 hd540 using your clover v2. Any suggestions on what could be causing the hard drive corruption? I have hwp enabled and the kext installed. In addition, I have your clover folder excluding fakesmc kexts.

Hopefully someone can help me!!!!

 

[ic3dm4n]

Hi - Can you include kext? I can't seem to build it properly and would appreciate your help! Thanks.

here's the kext.
http://kludgets.com/VoodooPS2Controller.kext.zip

I've since added these features:
1. four fingers spread / pinch
2. two finger zoom in / zoom out
3. two fingers swipe from edge (for notification)
use in combination with keyboard shortcuts

this has some of quirks and only for testing - though I'm using it for myself.

on a side note:
-- I think it is unfair that the ApplePS2 guy copies from Voodoo and other open source projects, yet doesn't share his own improvements and fixes

 

[itzmedavid89]

Without the class-code spoof, you cannot use HackrNVMeFamily on 10.12.x.
Instead you must add the IONVMeFamily patches (appropriate to your macOS version) to your own config.plist.

Thanks for the reply, but Maxexcloo already added those IONVMEFamily patches to his config.plist that he attached in his first post. I verified that it was in the <key>KernelAndKextPatches</key> section

Any other ideas how why i cant see my Nvme in disk utility when i try to install macOS for the very first time?

 

[RehabMan]

Thanks for the reply, but Maxexcloo already added those IONVMEFamily patches to his config.plist that he attached in his first post. I verified that it was in the <key>KernelAndKextPatches</key> section

Any other ideas how why i cant see my Nvme in disk utility when i try to install macOS for the very first time?

CLOVER.zip has a lot of problems:
"PCI Error" patches for AirPortBrcm4360 are wrong/not needed.
Port limit patch is only for short term use (port discovery)
There should not be two 5ghz BCM94352 patches (only one applicable to each 10.11.x/10.12.x). And really there is no 5ghz patch for 10.12, only the 'fcvo' patch.
AirPortExtreme patch is not needed with FakePCIID kexts.
No kexts in EFI/Clover/kexts/Other

And... because Clover cannot patch a kext that is not in kernel cache, you must include IONVMeFamily in EFI/Clover/kexts/Other, along with FakeSMC.kext, etc.

You should really use the class-code spoof + HackrNVMeFamily*.kext instead of KextsToPatch.

 

[Sevinkroff]

I used smbios MacBook9,1. I set this from before installation.
Then generated SSDT with Piker's script.
[[ I think ]] changing smbios after installation matters and affects the script.

I'm now using HWPEnabler.kext., setting the default value at 64001C01.

The difference:
Using HWPEnabler.
1. Idle frequency drop to 0.5 .. The graph looks ugly- erratic.
2. operating temperature is around 5 degree C lower
3. most probably better battery life

Using SSDT
1. Idle at 1.0 .. the graph when idle looks like a flat line - like the laptop is sleeping
2. no CPU state lower than 1.0
3. higher GeekBench 4 results than with

You can play with HWPEnabler's default values for performance or for efficiency.

Note:
I did not remove SSDT.aml;
HWPEnabler sometimes gets lost after sleep. You need to do some sleepwatcher stuff to reload it.

Dude, I heard some horror stories about the file system corrupting with HWP enabled. If I install HWPEnabler kext could that still happen? How long have you been using HWPEnabler and have you had those issues? I think I had it in the past when I used HWP without SSDT

 

[ic3dm4n]

I have HWPEnabler for just about a couple of weeks.
I've been running Xcode, compiling, building.
I have my kids play Minecraft, watch youtube.
No problems so far.

The default values or frequencies of HWPEnabler is maxed at 4.4 while my cpu is only at 2.8.
Using HWPEnabler as is could be the source your horror stories.
I also also keep watch with Intel Power Gadget and AppleIntelInfo

In any case, the guy to ask is Goodwin who made the enabler available.

 

[Sevinkroff]

I have HWPEnabler for just about a couple of weeks.
I've been running Xcode, compiling, building.
I have my kids play Minecraft, watch youtube.
No problems so far.

The default values or frequencies of HWPEnabler is maxed at 4.4 while my cpu is only at 2.8.
Using HWPEnabler as is could be the source your horror stories.
I also also keep watch with Intel Power Gadget and AppleIntelInfo

In any case, the guy to ask is Goodwin who made the enabler available.

I changed the default values for HWP to match 2.8 as well. Booted back into Windows and have some corruption issues. Luckily I can still copy off my important files but for now I'm keeping HWP off. With it on, I didn't notice a dramatic difference with it on in tangible battery life. It definitely hit lower frequencies more often, around the 500mhz rather than hovering at 1ghz, however battery life is the same (around 4 HRS) compared to Windows' 8 hours.