Contribute
Register

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

Status
Not open for further replies.
imEgo said:
DVMT settings:
setup_var 0x785 0x2 works for my device on [email protected]
Click to expand...

Here's what I have extracted from BIOS 2.2.1
Code: 
0x40CCC         Suppress If: {0A 82}
0x40CCE             Variable 0xD62 equals 0x20 {12 06 62 0D 20 00}
0x40CD4             Setting: DVMT Pre-Allocated, Variable: 0x785 {05 91 1C 05 2F 05 35 27 01 00 85 07 14 10 00 FE 00}
0x40CE5                 Option: 0M, Value: 0x0 {09 07 1D 05 00 00 00}
0x40CEC                 Option: 32M, Value: 0x1 {09 07 1E 05 30 00 01}
0x40CF3                 Option: 64M, Value: 0x2 {09 07 1F 05 00 00 02}
0x40CFA                 Option: 4M, Value: 0xF0 {09 07 20 05 00 00 F0}
0x40D01                 Option: 8M, Value: 0xF1 {09 07 21 05 00 00 F1}
0x40D08                 Option: 12M, Value: 0xF2 {09 07 22 05 00 00 F2}
0x40D0F                 Option: 16M, Value: 0xF3 {09 07 23 05 00 00 F3}
0x40D16                 Option: 20M, Value: 0xF4 {09 07 24 05 00 00 F4}
0x40D1D                 Option: 24M, Value: 0xF5 {09 07 25 05 00 00 F5}
0x40D24                 Option: 28M, Value: 0xF6 {09 07 26 05 00 00 F6}
0x40D2B                 Option: 32M/F7, Value: 0xF7 {09 07 27 05 00 00 F7}
0x40D32                 Option: 36M, Value: 0xF8 {09 07 28 05 00 00 F8}
0x40D39                 Option: 40M, Value: 0xF9 {09 07 29 05 00 00 F9}
0x40D40                 Option: 44M, Value: 0xFA {09 07 2A 05 00 00 FA}
0x40D47                 Option: 48M, Value: 0xFB {09 07 2B 05 00 00 FB}
0x40D4E                 Option: 52M, Value: 0xFC {09 07 2C 05 00 00 FC}
0x40D55                 Option: 56M, Value: 0xFD {09 07 2D 05 00 00 FD}
0x40D5C                 Option: 60M, Value: 0xFE {09 07 2E 05 00 00 FE}
0x40D63             End of Options {29 02}
0x40D65         End If {29 02}
0x40D67         Setting: DVMT Total Gfx Mem, Variable: 0x786 {05 91 30 05 31 05 18 05 01 00 86 07 10 10 01 03 00}
0x40D78             Option: 256M, Value: 0x2 {09 07 33 05 30 00 02}
0x40D7F             Option: 128M, Value: 0x1 {09 07 32 05 00 00 01}
0x40D86             Option: MAX, Value: 0x3 {09 07 34 05 00 00 03}
0x40D8D         End of Options {29 02}
0x4
Should I use "setup_var 0x786 0x1" or "setup_var 0x786 0x2" for HD 620 + QHD screen
I thought that 256M was too much ?
 
oli.mathieu said:
I have extracted the BIOS 2.2.1
Code: 
0x40CCC         Suppress If: {0A 82}
0x40CCE             Variable 0xD62 equals 0x20 {12 06 62 0D 20 00}
0x40CD4             Setting: DVMT Pre-Allocated, Variable: 0x785 {05 91 1C 05 2F 05 35 27 01 00 85 07 14 10 00 FE 00}
0x40CE5                 Option: 0M, Value: 0x0 {09 07 1D 05 00 00 00}
0x40CEC                 Option: 32M, Value: 0x1 {09 07 1E 05 30 00 01}
0x40CF3                 Option: 64M, Value: 0x2 {09 07 1F 05 00 00 02}
0x40CFA                 Option: 4M, Value: 0xF0 {09 07 20 05 00 00 F0}
0x40D01                 Option: 8M, Value: 0xF1 {09 07 21 05 00 00 F1}
0x40D08                 Option: 12M, Value: 0xF2 {09 07 22 05 00 00 F2}
0x40D0F                 Option: 16M, Value: 0xF3 {09 07 23 05 00 00 F3}
0x40D16                 Option: 20M, Value: 0xF4 {09 07 24 05 00 00 F4}
0x40D1D                 Option: 24M, Value: 0xF5 {09 07 25 05 00 00 F5}
0x40D24                 Option: 28M, Value: 0xF6 {09 07 26 05 00 00 F6}
0x40D2B                 Option: 32M/F7, Value: 0xF7 {09 07 27 05 00 00 F7}
0x40D32                 Option: 36M, Value: 0xF8 {09 07 28 05 00 00 F8}
0x40D39                 Option: 40M, Value: 0xF9 {09 07 29 05 00 00 F9}
0x40D40                 Option: 44M, Value: 0xFA {09 07 2A 05 00 00 FA}
0x40D47                 Option: 48M, Value: 0xFB {09 07 2B 05 00 00 FB}
0x40D4E                 Option: 52M, Value: 0xFC {09 07 2C 05 00 00 FC}
0x40D55                 Option: 56M, Value: 0xFD {09 07 2D 05 00 00 FD}
0x40D5C                 Option: 60M, Value: 0xFE {09 07 2E 05 00 00 FE}
0x40D63             End of Options {29 02}
0x40D65         End If {29 02}
0x40D67         Setting: DVMT Total Gfx Mem, Variable: 0x786 {05 91 30 05 31 05 18 05 01 00 86 07 10 10 01 03 00}
0x40D78             Option: 256M, Value: 0x2 {09 07 33 05 30 00 02}
0x40D7F             Option: 128M, Value: 0x1 {09 07 32 05 00 00 01}
0x40D86             Option: MAX, Value: 0x3 {09 07 34 05 00 00 03}
0x40D8D         End of Options {29 02}
0x4
Should I use "setup_var 0x786 0x1" or "setup_var 0x786 0x2" for HD 620 + QHD screen
I thought that 256M was too much ?
Click to expand...

Maybe @jkbuha is kind enough to give us a recap of EFI tuning to make QHD screens work without issues.
I'll put this recap in the main thread. TY
 
The following settings worked for me on the QHD and MBP14,1:

0x785 -> 0x06 (=192MB most likely, can't properly measure this unless someone knows how to measure DVMT in macOS)
0x786 -> 0x03 (=MAX possible gfx allocation for DVMT)
 
Hello, guys! Could you please provide dvmt values for full hd 9360 model with bios 2.2.1?
 
hello
jkbuha said:
0x785 -> 0x06 (=192MB most likely, can't properly measure this unless someone knows how to measure DVMT in macOS)
Click to expand...
I dont see this value in my extracted file ! is it risky to use it ?
Thanks
 
No one has the text values above 02, but it's safe to assume the DVMT increases in 32MB increments.

This variable is only risky if you set 0x785 to 00. Then you *will* brick the laptop and you will only be able to recover by fully resetting the laptop through SPI flash.
 
jkbuha said:
All screen glitches are now fixed on Sierra 10.12.6 with native Kaby Lake drivers on the i7-7500U with UHD. Thanks @RehabMan for helping me find a solution.

The solution involves a number of fixes, namely:

1) BIOS DVMT pre-alloc patching from 32MB to 128MB (setup_var 0x785 0x04)
2) BIOS DVMT max-alloc patching from 256MB to MAX (setup_var 0x786 0x03)
3) DVMT Framebuffer kext patch for ig-platform-id 59160000 - increase to 80MB and Cursor buffer to 12MB Cursor
4) Change SMBIOS to MacBookPro14,1

I've attached my Clover file for anyone with the QHD screen experiencing the same issues (in theory you should all see this at some point if you're using the native KBL drivers on Dell's QHD display). Note that I've disabled HWP and PluginType as I'm seeing approx 10-15% higher scores on Geekbench. Also I've discovered you can tweak your GT overclocking settings using UEFI variables, yielding another 5-10% increase, but that's for another post.
Click to expand...

@jkbuha I thought these were the correct DVMT settings you had mentioned in your previous post.
 
Killuminati91 said:
0x785 is still the value for the Full-HD i7-7500u version on bios 2.2.1.
Changed to 0x2 (which should be 64mb) and everything working fine.

Gave up on high sierra, waiting for the full release. Running 10.12.6 flawlessly. Thanks for the guide!
Click to expand...

My advice is to wait 1-2 months for High Sierra.
There are no revolutionary features that make the switch compulsory.
I will publish a guide, but don't expect it soon.
I'm working 10 hours a day on this hackintosh on 10.12.x and it's the most stable and fastest laptop I ever had (Windows ones included).
In the spirit of LTS, we'll switch to 10.13 after a while and only when stability, battery life, upgrade resilience, data integrity is not compromised.

Thanks to all of you for contributing to this guide, we did a great job, I've never seen a Hackintosh guide so well followed and with this amount of feedback (and system stability). To all of you, Thank you!
 
Added info regarding QHD screen BIOS fixes, re-paste photos and undervolting procedures in the main post.
Let me know if I missed something.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top