[Guide] Dell XPS 9560 Mojave VirtualSMC, I2C Trackpad, Clover UEFI Hotpatch

[Twerterus]

@blazinsmokey I just wanted to say thank you for the guide. For my work, we required mac OS, and since I already owned an XPS, I used several other guides until I finally landed on yours. Your guide has been working for me for months without any issues, and I can triple boot macOS, linux and Windows on the same machine - which is amazing. There are some small hiccups like sleep (which I just disabled - I just lock my laptop when I'm on my break), and TB3 (which I am not really using - I'm only using a usbC to HDMI adapter to get 2 external displays). Other than that, the experience has been really rock solid - even more so than my ubuntu installation. So I just wanted to pitch in and say thanks for the good work. I still haven't updated my mojave since I'm afraid gestures and keyboard functionality will break, but I don't really feel inclined to do so.

 

[blazinsmokey]

Blazinsmokey
Instruction in OP about VoltageShift is incomplete
./voltageshift offset -125 -90 -125 vil only work after cold/reboot.But after sleep/wake these values return to -0.
You can check with this
./voltageshift info
To solve it you should use -125 -90 -125 0 0 0 1
the last digit "1" will scheduled check the settings every 1 min. and amend if needed. (after wake from sleep)
More details here:

[Guide] Dell XPS 9350 Mojave VirtualSMC, I2C Trackpad, Clover UEFI Hotpatch

As there´s no updated Mojave guides here on tonymacx86 for my laptop i decided to make one. (Bear with me as this is first time i try to make a new thread and my native language is not English) My laptop specs. Dell XPS 9350 QHD+ I7 6560U Intel Iris 540 (3200x1800) 16GB 1867 Mhz DDR3 Ram 512GB...

www.tonymacx86.com

That's for when you are building the launch daemon. I only referred to the settings I was manually setting myself, you can read the voltageshift's github repo to fully understand the difference between the offset command versus the buildlaunchd command.

Edit: Also if you want your battery life to decrease significantly then sure have it check every minute. You're much better off checking every 30 minutes or an hour.

 

[blazinsmokey]

Heres the new generated CPUFriendDataProviders I made. I was thinking during my holiday break maybe it's because my BIOS is hacked up by changing values via EFI hacks when I was trying to figure out USB-C and TB. I'll have to reset it completely by removing the CMOS battery. Eventually I will but I think in the meantime some of you could give it a try.

Laptop for me would only enter deep idle and not sleep but would have low wattage usage from waking from deep idle.

 

[arehep]

That's for when you are building the launch daemon. I only referred to the settings I was manually setting myself, you can read the voltageshift's github repo to fully understand the difference between the offset command versus the buildlaunchd command.

Edit: Also if you want your battery life to decrease significantly then sure have it check every minute. You're much better off checking every 30 minutes or an hour.

Setting it to check every 30 or 60 minutes won't increase battery life.
It means that you don't have VoltageShift working for 30 or 60 minutes after wake from sleep.
That will for sure decrease battery life.
Setting it to one minute will not have any noticeable impact on increased battery life.
Believe me. I've done a lot of research.
In IntelPowerGadget you se that checking will show a very very very short raise in ghz (0,5)

 

[blazinsmokey]

Setting it to check every 30 or 60 minutes won't increase battery life.
It means that you don't have VoltageShift working for 30 or 60 minutes after wake from sleep.
That will for sure decrease battery life.
Setting it to one minute will not have any noticeable impact on increased battery life.
Believe me. I've done a lot of research.
In IntelPowerGadget you se that checking will show a very very very short raise in ghz (0,5)

It doesn't reset when the laptop goes to sleep, only when it hibernates and on cold boots. I don't use hibernation at all so I only have to run at boot. I run a couple bash alias commands every time I boot up anyways that sets this for me. I don't believe in needing a daemon for this. To each their own tho.

The developer actually sets the default interval to 160 minutes. It's in the instructions of the github. Take it how you want but I highly doubt the developers would pick 160 minutes as default if they thought every minute was a good idea. I still stand by my reasoning that it's not a good idea to poll it every minute, especially if you don't use hibernate then you should just have the offsets set at boot and not have it check at all.

 

[arehep]

"The developer actually sets the default interval to 160 minutes"
You are right.But VoltageShift was not made intended for Hackintosh.It was made for real macs
Hackintosh´s do not support hibernate.
Next time you put your Hack to sleep and wake it then check with ./voltageshift info
Values returns to -0

 

[mazakiss]

Heres the new generated CPUFriendDataProviders I made. I was thinking during my holiday break maybe it's because my BIOS is hacked up by changing values via EFI hacks when I was trying to figure out USB-C and TB. I'll have to reset it completely by removing the CMOS battery. Eventually I will but I think in the meantime some of you could give it a try.

Laptop for me would only enter deep idle and not sleep but would have low wattage usage from waking from deep idle.

Hi @blazinsmokey .

Using the new CPUFriend kext does the same thing as the one I generated with this handy script:

GitHub - stevezhengshiqi/one-key-cpufriend: Generate customized CPUFriendDataProvider.kext for dynamic macOS CPU power management

Generate customized CPUFriendDataProvider.kext for dynamic macOS CPU power management - stevezhengshiqi/one-key-cpufriend

github.com

Seems less power hungry and battery decreases much slower, but for an unknown reason sleep wake from lid open doesn't work anymore, I have to do it manually via power button. (like you apparently).

Last, I'm sad to hear for your Bios trouble (a bit guilty here)... Maybe try to install new bios 1.15.0 upon it to reset to factory setting https://www.dell.com/support/home/u...N&oscode=WT64A&productcode=xps-15-9560-laptop (after waiting a few days, because even if published apparently dell support aren't even aware it exist " lol We do not have any new BIOS firmware released for your system. We suggest that you do not proceed with the new update.

Hope it'll be ok.

Cheers.

EDIT: removing DeepIdleSSDT seems to fix sleep wake from lid but I have not tested sleep state yet (like in previous posts, will do).

 

[blazinsmokey]

"The developer actually sets the default interval to 160 minutes"
You are right.But VoltageShift was not made intended for Hackintosh.It was made for real macs
Hackintosh´s do not support hibernate.
Next time you put your Hack to sleep and wake it then check with ./voltageshift info
Values returns to -0

VoltageShift is literally a modified version of AnVMSR which was created for the hackintosh community.

hackintosh does support hibernate, rehabman even said so in this thread a while ago.

I think you want to research how writing to MSR registers work to understand why it doesn't matter if it's a real Mac or a hackintosh. The settings stick even after sleep, thats if your laptop sleeps correctly and doesn't hibernate.

 

[ferchizzle]

Btw, I can see you're still having BrcmFirmwareRepo.kext in your clover folder.
This is wrong, I could NOT pair XPS with my iPhone until I replaced it with BrcmFirmwareData.kext
BrcmFirmwareRepo.kext is for L/E or S/L/E ONLY

@blazinsmokey @dmitry_matora is it still necessary to use BrcmFirmwareRepo.kext? I didn’t see that kext in the latest Clover folder that was uploaded. What WiFi/BT cards are you both using?

 

[arehep]

The settings stick even after sleep

False
I just checked it on my HP Elitebook 840 G5 to and its the same.
If i use 30 instead of 1 the values return to -0 after wake from sleep.
From my XPS 9350
Before sleep

After wake from sleep