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

[ferchizzle]

Thanks! Also thanks for sharing that 9570 guide, I think there's some great info in there I'll have to check it out thoroughly when I have time. Unfortunately I have no idea on the 1830 as I have the 1560. I wonder if people using it have a windows installation to update the firmware on the BT chip. Also in what Airport kext is loading up for you guys after sleep? Try this boot arg "brcmfx-driver=2" to only load AirPort_BrcmNIC.

USB-C should work with KNN's method in the TB folder I included.

@blazinsmokey great to hear from you and thank you for writing back! The only command I know to check which kexts are loaded is "kextstat". The output I get is:
"18 0 0xffffff7f80fcc000 0x8000 0x8000 as.lvs1974.AirportBrcmFixup (2.0.2) C0286DB4-56CC-391C-B846-CB059AB02CBB <17 16 13 8 6 5 3 2 1>"
"129 1 0xffffff7f80c34000 0x6000 0x6000 com.no-one.BrcmFirmwareStore (2.2.10) 5DD4CFA3-AB5A-3AB4-BBA2-8ACE9BCD72D8 <6 5 3>"
"130 0 0xffffff7f80d4f000 0x6000 0x6000 com.no-one.BrcmPatchRAM2 (2.2.10) EA8FADAF-E7F3-3CDF-8440-49C15C0E25F8 <129 25 6 5 3 1>"

@blazinsmokey can you please what else I should do to get you the info you need?

And for the benefit for all DW1830 users, this is what one persistent person went thru to try to get DW1830 working on a 9350:https://www.tonymacx86.com/threads/dw1830-bluetooth-not-available-power-saving-issue.246350/

 

[blazinsmokey]

@blazinsmokey great to hear from you and thank you for writing back! The only command I know to check which kexts are loaded is "kextstat". The output I get is:
"18 0 0xffffff7f80fcc000 0x8000 0x8000 as.lvs1974.AirportBrcmFixup (2.0.2) C0286DB4-56CC-391C-B846-CB059AB02CBB <17 16 13 8 6 5 3 2 1>"
"129 1 0xffffff7f80c34000 0x6000 0x6000 com.no-one.BrcmFirmwareStore (2.2.10) 5DD4CFA3-AB5A-3AB4-BBA2-8ACE9BCD72D8 <6 5 3>"
"130 0 0xffffff7f80d4f000 0x6000 0x6000 com.no-one.BrcmPatchRAM2 (2.2.10) EA8FADAF-E7F3-3CDF-8440-49C15C0E25F8 <129 25 6 5 3 1>"

@blazinsmokey can you please what else I should do to get you the info you need?

And for the benefit for all DW1830 users, this is what one persistent person went thru to try to get DW1830 working on a 9350:https://www.tonymacx86.com/threads/dw1830-bluetooth-not-available-power-saving-issue.246350/

load IOReg and check ARPT@0 and you'll see what kext is loaded against the hardware

here's mine, check when it works and when it doesn't to see if any significant changes happen when your laptop wakes

 

[jmayniac]

@blazinsmokey
If you need a tester for anything, let me know. In addition to the 9560 I have several TB3 docks at my disposal as well as other hardware that I could potentially test with.

 

[blazinsmokey]

Got some good news, at least for me

When you change the variable bits using EFI-shell like the one for enabling HWP/Speedshift you can actually restore them all to defaults by just using the Restore Settings function built into the bios. I initially thought it wouldn't work b/c these settings persist through BIOS upgrades. However, I used the Manufacturing Settings option and it worked. I confirmed by checking before and after using the EFI-shell and Windows (Throttle Stop app and HWINFO64). I then ofcourse went back and reenabled HWP but only that.

Here's info on the restore options if people are interested.

The difference between this action and the Restore Default System Settings option is that Restore Default Manufacturing Settings erases all UEFI variables. An OS can write UEFI variables that store such things as entries in the boot order and key database information for Secure Boot. When you Restore Default Manufacturing Settings, this information is cleared, whereas it is retained when you Restore Default System Settings.

Saved me from taking the whole thing apart to get to the CMOS battery which is underneath the board. Meaning you have to take out the battery, fans, nvme, wifi, etc and then the main board and flip it around. I hope all our CMOS batteries lasts forever.

I can now resume tinkering around knowing we all have the same settings. Hopefully I can sort somethings out today and this week.

Happy hacking everyone!

Also thanks to the mod who cleaned up the thread, much appreciated.

 

[ferchizzle]

load IOReg and check ARPT@0 and you'll see what kext is loaded against the hardware

here's mine, check when it works and when it doesn't to see if any significant changes happen when your laptop wakes

View attachment 415621

@blazinsmokey thanks for the primer! The good news is I have to try harder to make Bluetooth to be "N/A" as opposed to just leaving it unplugged, as I have in the past. What I did to make it "N/A", last night, was to go on battery power, turn it off, use it for a few hours, and then turn bluetooth and connect my BT keyboard and trackpad. I checked the "CFBundler" Property before and after and they were both "com.apple.driver.Airport.BrcmNIC" before the crash (and plugged in) and after the crash (on battery power).

 

[ferchizzle]

@blazinsmokey was looking at your SMBIOS and am wondering why you used "MacBook Pro 14,1" vs "MacBook Pro 15,1". Was this a legacy setting from the KNNSpeed/HighSierra days?

 

[blazinsmokey]

@blazinsmokey was looking at your SMBIOS and am wondering why you used "MacBook Pro 14,1" vs "MacBook Pro 15,1". Was this a legacy setting from the KNNSpeed/HighSierra days?

iirc knn actually used 13,3 to begin with because when we were on sierra and hs we were spoofing Skylake for a while. Now we don't b/c macOS natively supports it now.

I chose 14,1 due to rehabman's advice and just looking at the hardware it made sense. Same gen CPU KabyLake, no dgpu, no touchid(T2 chip), you can compare the hardware yourself and see. In my opinion 15,1 wouldn't match up as well. Maybe a change is necessary.... I dunno. If you want to test it out for us, that'd be great.

14,3 would have been my second choice b/c it actually has a 7700HQ but it has dGPU, touchID...

 

[blazinsmokey]

@blazinsmokey thanks for the primer! The good news is I have to try harder to make Bluetooth to be "N/A" as opposed to just leaving it unplugged, as I have in the past. What I did to make it "N/A", last night, was to go on battery power, turn it off, use it for a few hours, and then turn bluetooth and connect my BT keyboard and trackpad. I checked the "CFBundler" Property before and after and they were both "com.apple.driver.Airport.BrcmNIC" before the crash (and plugged in) and after the crash (on battery power).

I'm not sure I understand what you saying here.

I thought the problem was bluetooth doesn't work on wake sometimes? Or is it any times?
Take a look at the configuration section here

GitHub - RehabMan/OS-X-BrcmPatchRAM: Broadcom PatchRAM driver for OS X

Broadcom PatchRAM driver for OS X. Contribute to RehabMan/OS-X-BrcmPatchRAM development by creating an account on GitHub.

github.com

Sepcifically

Note: Some with the typical "wake from sleep" problems are reporting success with: bpr_probedelay=100 bpr_initialdelay=300 bpr_postresetdelay=300. Or slightly longer delays: bpr_probedelay=200 bpr_initialdelay=400 bpr_postresetdelay=400.

 

[blazinsmokey]

Ladies and gentlemen, we are fixed up! I think....
After 7 hours of sleep, 1% battery usage. Idle CPU freq hovers much closer to 800Mhz than before. Temps are lower as well. I got as low as 33C which is lowest I ever seen at idle. No more extra power consumption on wake, power usage at idle returns to 9W-11W.

I cleaned up a bunch of stuff that is no longer necessary.
Fixed not going to sleep by removing, deep idle. Better to sleep than deep idle for battery savings. The deepidle SSDT patches were actually created by PikerAlpha to help sleep but here we are.
Fixed higher power consumption after waking from sleep.
CPUFriendDataProvider uses power savings.
Below is a pretty good overview but I may have forgot to mention some changes.

Enjoy! Happy hack! Let me know what I screwed up on, bc I'm sure something doesn't work, lol.
Edit: Folder posted to guide

7/11 Release Clover v3.4, Updated Guide
All kexts updated as of 7/11
New generated CPUFriendDataProviders
Edited SSDT-config.aml
Clover updated to 4988

• IMPORTANT NOTE, recent update changed drivers64UEFI to drivers/UEFI
• Due to different folder format make sure you have what's needed or you better have you USB backup

Removed from config

• No longer need to set plugin type to 1, the generate plugin section will do
• ACPI / UseSystemIO=YES
• ACPI / Drop SSDT Tables, xh_rvp11 and PtidDevc
• KernelandKextpatch / Apple RTC
• KernelandKextpatch / Apple IntelCPUPM

Added to config

• Added AutoMerge=YES

SSDT Removed

• Deep Idle, still included in misc folder, read the readme

@ars0n how's open core going for you? Only bluetooth not working? I'm about to join in on the fun soon. Maybe open a thread for this? And are you trying open core on Mojave or Catalina?

 

[blazinsmokey]

For anybody that wants to try, i have OpenCore 0.0.3 working for Dell XPS 9560 to boot MacOS. I can't get BrcmpatchRAM2 to load for bluetooth to work. If anyone can look into that and help with that, it'll be a good thing. Any modifications or fixes is welcomed also.

So I started a config.plist for OC and I looked at yours to see how far you got. Did you just steal this config from some random system? Bc there's no way these device properties make any sense.