Contribute
Register

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

Status
Not open for further replies.
DW1560 WiFi + BT. I'm experiencing BT Lag when using with 2.4Ghz WiFi. Anyone else?
 
Hi guys, I've seen a lot of activity in my thread recently. Very happy about this.
I'm on holidays and I don't have access to my laptop for two weeks. I'll try to help anyone as soon as I come back.
Meanwhile, thanks to all of you for answering and helping the newbies.
For newbies: remember to post your most updated problem reporting files any time you ask for help. No answers without problem reporting files attached!
Any deviation from the files attached in post #1 will be difficult to troubleshoot.
With these files I have a 100% stable system and 10+h of battery life (on SATA drive).
 
@RehabMan - Since 10.12.6 has been released I haven't succeeded in getting the native KBL framebuffer driver to work properly with my UHD display. My DVMT in BIOS is set to pre-allocate 64MB. The display boots up fine (it's in 1600x900 in Retina mode) but when the screen turns off or laptop goes to sleep the display either does not come back or comes back garbled. It works fine with the SKL framebuffer driver though.

Windows reports the device as having an ID of 59168086.

Here's what I've tried to do:
1) Change ig-platform-id to 591b0000 & FakeID to 59168086 With the 19MB framebuffer patch the display fails to initialise; I subsequently amended the kext patch to 64MB, the display starts up correctly but then fails to come back on sleep or screen-off.

2) Change ig-platform-id to 59160000 & FakeID to 59168086. Display starts up fine but fails to come back on sleep or screen-off.

3) Change ig-platform-id to 19160000 & FakeID to 19168086. Display works correctly and resumes properly.

4) Increase DVMT in BIOS to 96MB or 128MB. No effect.

I've attached my problem reporting files.
 

Attachments

  • EFI_KBL.zip
    4.8 MB · Views: 88
@RehabMan - Since 10.12.6 has been released I haven't succeeded in getting the native KBL framebuffer driver to work properly with my UHD display. My DVMT in BIOS is set to pre-allocate 64MB. The display boots up fine (it's in 1600x900 in Retina mode) but when the screen turns off or laptop goes to sleep the display either does not come back or comes back garbled. It works fine with the SKL framebuffer driver though.

Windows reports the device as having an ID of 59168086.

Here's what I've tried to do:
1) Change ig-platform-id to 591b0000 & FakeID to 59168086 With the 19MB framebuffer patch the display fails to initialise; I subsequently amended the kext patch to 64MB, the display starts up correctly but then fails to come back on sleep or screen-off.

2) Change ig-platform-id to 59160000 & FakeID to 59168086. Display starts up fine but fails to come back on sleep or screen-off.

3) Change ig-platform-id to 19160000 & FakeID to 19168086. Display works correctly and resumes properly.

4) Increase DVMT in BIOS to 96MB or 128MB. No effect.

I've attached my problem reporting files.

Try other ig-platform-ids. Suggest you extract all of them from the binary and try each.
For some of them, you may need to increase DVMT-prealloc.

Also, an ioreg from a retina KabyLake MacBookPro might be useful. Perhaps there is some property we should be injecting. And it would tell us which ig-platform-id is being used.
 
Try other ig-platform-ids. Suggest you extract all of them from the binary and try each.
For some of them, you may need to increase DVMT-prealloc.

Also, an ioreg from a retina KabyLake MacBookPro might be useful. Perhaps there is some property we should be injecting. And it would tell us which ig-platform-id is being used.

Will do.
Would you suggest a different SMBIOS to Macbook9,1?
 
Will do.
Would you suggest a different SMBIOS to Macbook9,1?

Macbook9,1 is Skylake...
So, there are potentially better choices for KabyLake hardware such as yours.
Refer to everymac.com.

I think it is likely this is DVMT-prealloc related and related to the framebuffer memory settings (framebuffer size/cursor bytes size). 128mb prealloc with larger memory buffers likely to be helpful.
 
After some testing, MacbookPro14,3 solves the issue on my i7-7500U with UHD. ig-platform-id is set to 591b0000, and the system works with HWP set on or off.

In so doing I've extracted a number of other ig-platform-id from the binary. Haven't tested them but here they are:

59120000
591B0000
591B0006
591D0000
591E0000
591E0001
59230000
59260000
59260002
59270000
59270004
59270009
 
After some testing, MacbookPro14,3 solves the issue on my i7-7500U with UHD. ig-platform-id is set to 591b0000, and the system works with HWP set on or off.

In so doing I've extracted a number of other ig-platform-id from the binary. Haven't tested them but here they are:

59120000
591B0000
591B0006
591D0000
591E0000
591E0001
59230000
59260000
59260002
59270000
59270004
59270009

MacBookPro14,3 might have issues as it has discrete graphics.
MacBookPro14,1 might be a better choice.
 
The MBP14,1 definitely looks better. It has the i7-7660U CPU which is on the latest XPS models.
Do you know if/where I can find the Mac- plist to test?
Scratch that. Found it. MBP14,1 is Mac-B4831CEBD52A0C4C.plist
 
Ok so the screen issues on battery power are solved with a combo of board id and dvmt patching.

The one final issue is that the screen issues still happen whilst the screen turns off and on when power is plugged in. What is the difference here?
 
Status
Not open for further replies.
Back
Top