[Guide] Dell XPS 13 9360 on MacOS Sierra 10.12.x - LTS (Long-Term Support) Guide

[ZombieBest]

Bluetooth is still an issue I see, sorry. Still my xps 9360 does recognize BT I have the
Broadcom BCM94352Z

Please try this. Put you laptop at sleep. Then disconnect AC Power. Wake up you laptop and tell me which is the BT device name. See what I wrote some posts above

Thank you

 

[RehabMan]

Is it possible to modify the VoodooPS2Controller? @RehabMan

Full source code is available on my github, if you'd like to tweak it.
Also, there are many settings in the Info.plist files all of which can be overridden with ACPI.

Note: Your real goal should be to get an I2C-based driver working for the trackpad (PS2 does not have the bandwidth for good trackpad response).

 

[Vygr10565]

Please try this. Put you laptop at sleep. Then disconnect AC Power. Wake up you laptop and tell me which is the BT device name. See what I wrote some posts above

Thank you

So i connected my XPS to my iPhone X it connects. And when I return in HS from sleep BT is still available.

I don't have bluetooth headphones, so can't test audio.

 

[Vygr10565]

Full source code is available on my github, if you'd like to tweak it.
Also, there are many settings in the Info.plist files all of which can be overridden with ACPI.

Note: Your real goal should be to get an I2C-based driver working for the trackpad (PS2 does not have the bandwidth for good trackpad response).

I see, do you have any experience with http://forum.osxlatitude.com/index....and-synaptics-smart-touchpad-driver-mac-os-x/ aka ApplePS2Smarttouchpad? I notice some improvements instead of VoodooPS2Controller or is it just me?

 

[RehabMan]

I see, do you have any experience with http://forum.osxlatitude.com/index....and-synaptics-smart-touchpad-driver-mac-os-x/ aka ApplePS2Smarttouchpad? I notice some improvements instead of VoodooPS2Controller or is it just me?

That kext is closed-source, in violation of the APSL. I have nothing to do with it.

 

[nos1609]

Has anyone tinkered with this? Worth a try, if you have time (I unfortunately do not).
https://www.tonymacx86.com/threads/voodooi2c-help-and-support.243378

Already tried and tested, even found the right pin value, but I have no experience nor nowledge in DSDT editing, only patching following explicit guides here and on some other forums. So I failed to get it working, but the trackpad is recognized in ioreg, and be ready to use an external usb mouse during testing, as you'll have no mouse input once i2c kext loaded.

 

[ZombieBest]

So i connected my XPS to my iPhone X it connects. And when I return in HS from sleep BT is still available.

I don't have bluetooth headphones, so can't test audio.

And device name remains BCM94352Z after you return from sleep while on battery?

 

[hackintose]

Does anyone know if there are any IFR variables to change when the fans kick in or allow OS level fan control? I went through the IFR.txt and couldn't find anything that clear.

edit: i've extracted the ROM and IFR from the 2.5.1 firmware on the XPS13 i5 8520u

It confirms the following variables are the same from 2.2.1

Spoiler: IFR variables

Intel(R) SpeedStep(tm)
2.3.1: 0x4AB --> 1 (Enabled, Default: Enabled)

Intel(R) Speed Shift Technology
2.3.1: 0x4AD --> 1 (Enabled, Default: Disabled)

CFG Lock
2.3.1: 0x4DE --> 0 (Disabled, Default: Enabled)

DVMT Pre-Allocated
2.3.1: 0x785 --> 0x6 (192MB, Default: 32MB)

DVMT Total Gfx Mem
2.3.1: 0x786 --> 0x03 (MAX, Default: 128MB)


----------------
Thunderbolt(TM) Support
2.3.1: 0x443 --> 1 (Enabled, Default: Enabled)

Thunderbolt(TM) PCIe Support
2.3.1: 0x44A --> 1 (Enabled, Default: Disabled)

Thunderbolt Usb Support
2.3.1: 0x44C --> 1 (Enabled, Default: Disabled)

Windows 10 Thunderbolt support
2.3.1: 0x13C5 --> 1 (Enabled, Default: Disabled)

This is all I can find in relation to fan control in the IFR file

Spoiler: fan control

Numeric: Active Trip Point 0 Fan Speed (4294928424-4294928424) , Variable: 0x2B0 {07 91 4E 11 4F 11 D2 02 01 00 B0 02 00 10 00 64 01}
0x39D23 Default: 8 Bit, Value: 0x64 {5B 06 00 00 00 64}
0x39D29 End {29 02}
0x39D2B Setting: Active Trip Point 1, Variable: 0x2AD {05 91 2B 11 2C 11 D3 02 01 00 AD 02 10 10 0F 7F 00}
0x39D3C Option: Disabled, Value: 0x7F {09 07 04 00 00 00 7F}
0x39D43 Option: 15 C, Value: 0xF {09 07 33 11 00 00 0F}
0x39D4A Option: 23 C, Value: 0x17 {09 07 34 11 00 00 17}
0x39D51 Option: 31 C, Value: 0x1F {09 07 35 11 00 00 1F}
0x39D58 Option: 39 C, Value: 0x27 {09 07 36 11 00 00 27}
0x39D5F Option: 47 C, Value: 0x2F {09 07 37 11 00 00 2F}
0x39D66 Option: 55 C, Value: 0x37 {09 07 38 11 30 00 37}
0x39D6D Option: 63 C, Value: 0x3F {09 07 39 11 00 00 3F}
0x39D74 Option: 71 C, Value: 0x47 {09 07 3A 11 00 00 47}
0x39D7B Option: 79 C, Value: 0x4F {09 07 3B 11 00 00 4F}
0x39D82 Option: 87 C, Value: 0x57 {09 07 3C 11 00 00 57}
0x39D89 Option: 95 C, Value: 0x5F {09 07 3D 11 00 00 5F}
0x39D90 Option: 103 C, Value: 0x67 {09 07 3F 11 00 00 67}
0x39D97 Option: 111 C, Value: 0x6F {09 07 40 11 00 00 6F}
0x39D9E Option: 119 C (POR), Value: 0x77 {09 07 41 11 00 00 77}
0x39DA5 End of Options {29 02}

0x39DA7 Numeric: Active Trip Point 1 Fan Speed (4294928424-4294928424) , Variable: 0x2AF {07 91 50 11 51 11 D4 02 01 00 AF 02 00 10 00 64 01}
0x39DB8 Default: 8 Bit, Value: 0x4B {5B 06 00 00 00 4B}
0x39DBE End {29 02}
0x39DC0 Suppress If: {0A 82}
0x39DC2 Variable 0x2CF equals 0x1 {12 06 CF 02 01 00}
0x39DC8 Setting: Passive Trip Point, Variable: 0x2B1 {05 91 2F 11 30 11 D5 02 01 00 B1 02 10 10 0F 7F 00}

0x39FF3 Numeric: CPU Fan Speed (4294928424-4294928424) , Variable: 0x2C4 {07 91 70 11 71 11 E4 02 01 00 C4 02 00 10 01 64 01}
0x3A004 Default: 8 Bit, Value: 0x41 {5B 06 00 00 00 41}
0x3A00A End {29 02}
0x3A00C End Form {29 02}

0x3A3BE Setting: FAN1 Device, Variable: 0x2EA {05 91 00 12 01 12 FC 02 01 00 EA 02 10 10 00 01 00}
0x3A3CF Option: Disabled, Value: 0x0 {09 07 04 00 00 00 00}
0x3A3D6 Option: Enabled, Value: 0x1 {09 07 03 00 30 00 01}
0x3A3DD End of Options {29 02}
0x3A3DF Setting: FAN2 Device, Variable: 0x2EB {05 91 02 12 03 12 FD 02 01 00 EB 02 10 10 00 01 00}
0x3A3F0 Option: Enabled, Value: 0x1 {09 07 03 00 30 00 01}
0x3A3F7 Option: Disabled, Value: 0x0 {09 07 04 00 00 00 00}
0x3A3FE End of Options {29 02}


Form: Fan Control Override, Form ID: 0x2844 {01 86 44 28 8C 19}
0x30A01 Subtitle: Fan Control Override {02 87 8C 19 00 00 00}
0x30A08 End {29 02}
0x30A0A Subtitle: {02 87 02 00 00 00 00}
0x30A11 End {29 02}
0x30A13 Grayout If: {19 82}
0x30A15 Variable 0xDFC equals 0x0 {12 06 FC 0D 00 00}
0x30A1B Checkbox: Fan Control Override, Variable: 0x10C9 {06 8E 8E 19 8F 19 E7 00 01 00 C9 10 10 00}
0x30A29 Default: Other {5B 85 00 00 08}
0x30A2E Value {5A 82}
0x30A30 64 Bit Unsigned Int: 0x0 {45 0A 00 00 00 00 00 00 00 00}
0x30A3A End {29 02}
0x30A3C End {29 02}

curiously checking if FAN2 is enabled in uefi shell shows it is despite the xps13 having a single fan

If i check the
Fan Control Override, Variable: 0x10C9
it reports as 0x00, is it too risky to try changing it? I have several of these laptops and to be honest im open to bricking one

 

[hackintose]

Update

So I was messing with some IFR variables, I managed to brick the bios.

Recovery was interesting, I made a FAT (not fat32) drive with the 2.5.1 exe, the 2.1.0 bios exe renamed BIOS_IMG.rcv as well as the setup rom file from 2.2.1.


following the standard procedure, unplug batt- cmos batt- hold power to clear nvram- replug - plug in usb then hold escape/ctrl and plug AC did not work.

However on second attempt I placed placed the flash drive in (left plug) BEFORE reconnecting the battery (i connected rtc battery first followed by main battery)

As soon as the battery connector went in it booted right up to an error about defaulting BIOS. (no keys pressed or held, no AC plugged in)

I attempted to flash bios from the F12 boot menu, however it did not work with the slightly unbricked bios.

Then I powered off, held escape/control, plugged in power cable (with usb in left slot) and loaded the BIOS recovery mode.

This allowed me to downgrade all the way back to the factory shipped 2.1.0 from 2.5.1

One tidbit which may or may not mattered was the battery connector only went in about half way the second time, so when it finally booted the front LED was flashing orange/white, and the laptop did not recognize the battery (even though it booted without power plug) so it refused to do a BIOS recovery, I shut down pushed the battery connector in the rest of the way and rebooted into BIOS recovery.

Perhaps the battery giving power but not info was what jogged it to boot. Regardless it took a good hour of mucking about to get it to boot.

To be clear I had 3 bios revisions on the recovery drive, stock 2.5.1.exe, the 2.1.0 exe renamed BIOS_IMG.rcv and the 2.2.1 ROM file. BIOS recovery console did not let me select a file, it chose 2.1.0 which means the proper fix must entail having the BIOS executable renamed to BIOS_IMG.rcv for the ctrl/esc recovery to work. It may also allow others to downgrade.

Im now going to update to 2.2.1 (same bios as my other device I dont want to brick) and start playing with IFR again.

Any input would be appreciated

 

[hackintose]

I plan to change the cpu and gpu undervolt to 0x4B (-.075v) do you think this is unsafe? Should I test with XTU in windows first?

What is the purpose of the thunderbolt variables?
Thunderbolt(TM) Support
2.3.1: 0x443 --> 1 (Enabled, Default: Enabled)

Thunderbolt(TM) PCIe Support
2.3.1: 0x44A --> 1 (Enabled, Default: Disabled)

Thunderbolt Usb Support
2.3.1: 0x44C --> 1 (Enabled, Default: Disabled)

Windows 10 Thunderbolt support
2.3.1: 0x13C5 --> 1 (Enabled, Default: Disabled)

Will they have any effect in OSX? I'm not sure if it was those or changing the active trip point temperatures that bricked it last time.

I want to test the active trip point temps again. They should just change when the fan kicks in, 71 degrees is too hot for fan response.
The default variable for active trip point 1 is 71 degrees Celsius, but according to intel power gadget, its not until nearly 90 degrees that the fan really kicks in. The ifr text points show it can be set it much lower. If it would start cranking when the bottom gets hot (~55degrees) the hardware will live longer (my end goal)

I also saw the XMP variables in the IFR. Should they be left untouched?

Once again I'm prepared to brick one of my machines but obviously I am not trying to.