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

[Coletz]

Yeah true, I should've added the troubleshooting items. I did a temporary workaround, though reverted to my old configs, and updated to the latest kexts. I guess it was something to do with the clover config. Gotta look at it carefully



Yes, I did compile the dsdt from that specific commit. So let me get this straight, after I updated the SSDT-TYPC.aml in my config, I should expect a drop on the PKG under Power, right? Something under 1.00, when type-C port isn't in use? Thanks @Coletz

My values are nearly identical to Richylitschy 's values in the screenshot attached in the GitHub issue I've linked in the past days... I haven't compiled anything anyway. Just took the aml file and putted in the EFI/CLOVER folder replacing the old one, invalidated kext cache (don't think it's needed though) and rebooted. I am using the clover folder which Richylitschy uploaded some weeks ago + the modified SSDT + maybe I've updated some kext, but can't remember

 

[ToyoRob]

Has anyone managed to get a Thunderbolt Display to work with this? I tried using the overpriced Apple Thunderbolt 3 to 2 adapter and got no sound or video.
Thanks

 

[Richylitschy]

Does anybody have a working battery cycle count btw? Mine is showing 0. Is the Dell battery even tracking its cycles?

 

[jkbuha]

@the-darkvoid , CLOVER r5018 breaks sleep and crashes/reboots on my rig. Most of my config (apart from CPUFriend, audio and bluetooth) is similar to your setup so not sure if you've seen it as well. This is not the /drivers/UEFI/ issue, it's likely an incompatibility with the efi drivers and one of the more recent build versions of Clover (4961 and above)

Had to revert to v4934 where it works fine. Not sure why this is the case, as a quick search doesn't seem to show anyone having the same issue...

 

[the-darkvoid]

@the-darkvoid , CLOVER r5018 breaks sleep and crashes/reboots on my rig. Most of my config (apart from CPUFriend, audio and bluetooth) is similar to your setup so not sure if you've seen it as well.

Definitely haven't had the same issue. Migrated all EFI drivers to the new structure and all seems fine.
Also OpenCore with v0.3 seems more stable now and might soon be a production ready alternative.

 

[Killuminati91]

The new files specify the frame-buffer controller through device property injection, as opposed to SSDT-CONFIG and SSDT-IGPU. So the existing AML's need to be removed first and the following properties should be in config.plist at least:

    <key>Devices</key>
    <dict>
        <key>Properties</key>
        <dict>
            <!-- IMEI Controller -->
            <key>PciRoot(0x0)/Pci(0x1f,0x0)</key>
            <dict>
                <key>compatible</key>
                <string>pci8086,9cc1</string>
                <key>device-id</key>
                <data>
                wZwAAA==
                </data>
            </dict>
            <!-- AppleALC HDAS Layout -->
            <key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>layout-id</key>
                <data>
                DQAAAA==
                </data>
            </dict>
            <!-- GFX0 platform-id and framebuffer configuration (QHD) -->
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                AAAWWQ==
                </data>
                <key>device-id</key>
                <data>
                FlkAAA==
                </data>
                <key>enable-hdmi20</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-fbmem</key>
                <data>
                AADAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-stolenmem</key>
                <data>
                AAAABQ==
                </data>
            </dict>
        </dict>
    </dict>

If you have non-QHD you need to place your values here instead (if different). You should be able to derive them from the pre-existing SSDT-IGPU.dsl logic.

Managed to get it to boot with the following settings (taken from RehabMans Laptop Config), however my HD620 is now displayed as 7MB and monitor brightness is not working. What am I missing? Cant attach problem reporting files, as I still use my external USB to start the new clover files.

<key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1f,0x0)</key>
            <dict>
                <key>compatible</key>
                <string>pci8086,9cc1</string>
                <key>device-id</key>
                <data>
                DwCqAA==
                </data>
            </dict>
            <key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>layout-id</key>
                <data>
                DQAAAA==
                </data>
            </dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                qqsAAA==
                </data>
                <key>device-id</key>
                <data>
                DwCqAA==
                </data>
                <key>enable-hdmi20</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-fbmem</key>
                <data>
                qgyqAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-stolenmem</key>
                <data>
                qgoKAA==
                </data>
            </dict>
        </dict>

 

[mashny]

This fixed the bluetooth breaking after sleep issue for me!

[FIX] BCM94352z DW1560 BT lost after sleep

Hello pals using BCM94352z: I'm here to share the final solution I've found to the DUPLICATE DEVICE problem of BCM94352z, in the hope that it would help you. This problem has been bothering me for a long time. I searched the whole Internet but got no clue. The most common advice is to adjust...

www.tonymacx86.com

 

[Mrgeque]

Surely you need to enable overclocking first, as per my settings. Otherwise the settings may appear to be passed to the MSR register but will be blocked. I've pasted the relevant excerpts here:

*Overclock, CFG, WDT & XTU enable
(0x4DE) -> 00
(0x64D) -> 01
(0x64E) -> 01

been watching this thread for a while, wanted to ask how you overclock the 8550u? and set frequency for each core? 800mhz idle? I've undervalued the cpu already but can't seem to find where and how to overclock it exactly. thanks

 

[jkbuha]

Definitely haven't had the same issue. Migrated all EFI drivers to the new structure and all seems fine.
Also OpenCore with v0.3 seems more stable now and might soon be a production ready alternative.

Finally got some free time to troubleshoot this, and the issue is with the boot argument. Changing to darkwake=4 solved it.

 

[jkbuha]

been watching this thread for a while, wanted to ask how you overclock the 8550u? and set frequency for each core? 800mhz idle? I've undervalued the cpu already but can't seem to find where and how to overclock it exactly. thanks

Just to be clear. The 'U' series of chipsets cannot be overclocked; the multiplier is locked.