Contribute
Register

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

Status
Not open for further replies.
I highly doubt it. You need your wifi to be en0 and builtin (use DPCI Manager). I'm not even sure you'll be able to log into iTunes...
It is en0. I don't know how to check the built-in box. No, I cannot log into iTunes - it says that my computer cannot be verified.
 
It is en0. I don't know how to check the built-in box. No, I cannot log into iTunes - it says that my computer cannot be verified.

https://github.com/RehabMan/OS-X-Null-Ethernet

This is what you need. As long as the system has something that's en0 and builtin, it doesn't care where you get internet from. This will make a fake device that's builtin and en0, so you can use an external WiFi adapter or whatever to get online.
 
https://github.com/RehabMan/OS-X-Null-Ethernet

This is what you need. As long as the system has something that's en0 and builtin, it doesn't care where you get internet from. This will make a fake device that's builtin and en0, so you can use an external WiFi adapter or whatever to get online.

Thanks. It works! I have iMessage now activated.
 
Is it safe to upgrade to 10.12.3?
 
Quick update - booting Clover in Legacy (EFI) mode instead of UEFI does not freeze for charger plug/unplug.

I'll shortly be posting Problem Reporting files for both EFI and UEFI, but for now it looks to be related to Clover, or this BIOS's UEFI implementation.

Since UEFI vs. legacy mainly affects the memory map, and memory map is affected by OsxAptioFix...
You should try OsxAptioFixDrv-64.efi instead of OsxAptioFix2Drv-64.efi....

Also:
- FixRegions_10000000 is a bad idea (remove or set false)
- remove darkwake=0
- the ioreg shows Dell SMBIOS truncation (fix available in new Clover)
- ACPI/patched should not have dynamic SSDTs
- SSDTs are being loaded in the wrong order (below is from your Clover bootlog)
Code:
2:126  0:000  Inserting SSDT-14.aml from EFI\CLOVER\ACPI\patched ... Success
2:126  0:000  Inserting SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success
2:127  0:000  Inserting SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
2:128  0:000  Inserting SSDT-11x.aml from EFI\CLOVER\ACPI\patched ... Success
2:128  0:000  Inserting SSDT-10x.aml from EFI\CLOVER\ACPI\patched ... Success
2:129  0:000  Inserting SSDT-9x.aml from EFI\CLOVER\ACPI\patched ... Success
2:130  0:000  Inserting SSDT-8x.aml from EFI\CLOVER\ACPI\patched ... Success
2:130  0:000  Inserting SSDT-7x.aml from EFI\CLOVER\ACPI\patched ... Success
2:131  0:000  Inserting SSDT-6x.aml from EFI\CLOVER\ACPI\patched ... Success
2:132  0:000  Inserting SSDT-5x.aml from EFI\CLOVER\ACPI\patched ... Success
2:132  0:000  Inserting SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
2:133  0:000  Inserting SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
2:133  0:000  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
2:134  0:000  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
2:135  0:000  Inserting SSDT-pr.aml from EFI\CLOVER\ACPI\patched ... Success
2:135  0:000  Inserting SSDT-TB.aml from EFI\CLOVER\ACPI\patched ... Success
2:136  0:000  Inserting SSDT-NVMe-Pcc.aml from EFI\CLOVER\ACPI\patched ... Success
2:137  0:000  Inserting SSDT-ALC256.aml from EFI\CLOVER\ACPI\patched ... Success
2:138  0:000  Inserting SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
(as per ACPI patching guide, you must use SortedOrder to load SSDTs in the correct order)
- also, as per ACPI patching guide, DropOem must be true when you have patched SSDTs in ACPI/patched. You have it set false.
- better to install all kexts to the system volume and reserve kext injection only for recovery and the installer
- Chrome is hooking your USB ports (read FAQ for how to disable)
- avoid 3rd party system software (such as LittleSnitch) until you have the bugs worked out...
- USB is not implemented correctly (wrong UsbConnector values)
- Clover HWPEnable not needed with correct SMBIOS choice and XCPM idle patch (it is native)
 
Hi iannn,

Are there some special steps you had to do with your specific model? Mine(i7, 16gb, 512gb, qhd) will arrive tomorrow.

Hi Pspracers,

Sorry - took me a minute to get back to you, there. Been working like a madman all week.

I could not get the LiteOn nvme mine shipped with to work no matter what I tried, so I bought a Samsung 950 on eBay. Not an ideal solution, but it got the job done.
 
Please let us know:
1- why did you update tb firmware? Was it not working before fw update?
2- did you use my ssdt-tb or did you take other steps to make it work? In the latter case, please describe them.

1. It was not working before I updated the firmware. After the firmware update, it started working. This has been a common practice on Gigabyte boards, so I just applied it here.
2. No, I did not. No other special steps.
 
Since UEFI vs. legacy mainly affects the memory map, and memory map is affected by OsxAptioFix...
You should try OsxAptioFixDrv-64.efi instead of OsxAptioFix2Drv-64.efi....

Also:
- FixRegions_10000000 is a bad idea (remove or set false)
- remove darkwake=0
- the ioreg shows Dell SMBIOS truncation (fix available in new Clover)
- ACPI/patched should not have dynamic SSDTs
- SSDTs are being loaded in the wrong order (below is from your Clover bootlog)
Code:
2:126  0:000  Inserting SSDT-14.aml from EFI\CLOVER\ACPI\patched ... Success
2:126  0:000  Inserting SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success
2:127  0:000  Inserting SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
2:128  0:000  Inserting SSDT-11x.aml from EFI\CLOVER\ACPI\patched ... Success
2:128  0:000  Inserting SSDT-10x.aml from EFI\CLOVER\ACPI\patched ... Success
2:129  0:000  Inserting SSDT-9x.aml from EFI\CLOVER\ACPI\patched ... Success
2:130  0:000  Inserting SSDT-8x.aml from EFI\CLOVER\ACPI\patched ... Success
2:130  0:000  Inserting SSDT-7x.aml from EFI\CLOVER\ACPI\patched ... Success
2:131  0:000  Inserting SSDT-6x.aml from EFI\CLOVER\ACPI\patched ... Success
2:132  0:000  Inserting SSDT-5x.aml from EFI\CLOVER\ACPI\patched ... Success
2:132  0:000  Inserting SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
2:133  0:000  Inserting SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
2:133  0:000  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
2:134  0:000  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
2:135  0:000  Inserting SSDT-pr.aml from EFI\CLOVER\ACPI\patched ... Success
2:135  0:000  Inserting SSDT-TB.aml from EFI\CLOVER\ACPI\patched ... Success
2:136  0:000  Inserting SSDT-NVMe-Pcc.aml from EFI\CLOVER\ACPI\patched ... Success
2:137  0:000  Inserting SSDT-ALC256.aml from EFI\CLOVER\ACPI\patched ... Success
2:138  0:000  Inserting SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
(as per ACPI patching guide, you must use SortedOrder to load SSDTs in the correct order)
- also, as per ACPI patching guide, DropOem must be true when you have patched SSDTs in ACPI/patched. You have it set false.
- better to install all kexts to the system volume and reserve kext injection only for recovery and the installer
- Chrome is hooking your USB ports (read FAQ for how to disable)
- avoid 3rd party system software (such as LittleSnitch) until you have the bugs worked out...
- USB is not implemented correctly (wrong UsbConnector values)
- Clover HWPEnable not needed with correct SMBIOS choice and XCPM idle patch (it is native)

BAM! This is why you are the @RehabMan Freaking genius! Thanks I'll try this ASAP.
 
Last edited:
Since UEFI vs. legacy mainly affects the memory map, and memory map is affected by OsxAptioFix...
You should try OsxAptioFixDrv-64.efi instead of OsxAptioFix2Drv-64.efi....

Thanks for the detailed help, it is much appreciated. However after having applied all options the charger freeze issue still persists, so we're back to square one. I suspect it's an EC register now, especially seeing that in non-UEFI modes the charger works fine.

I also have a further couple of questions based on your feedback...

- the ioreg shows Dell SMBIOS truncation (fix available in new Clover)
I'm using the latest Clover svn (4035) - is there something i need to additionally apply?

- Chrome is hooking your USB ports (read FAQ for how to disable)
I'm not sure I understand this - which FAQ should I look at?

- USB is not implemented correctly (wrong UsbConnector values)
I had a feeling this was the case, however both USB ports do work so far. I haven't yet tried the USB-C, so maybe that's why. Does this also mean that any 9360 users who have followed this post have the wrong UsbConnector values as well, or is this specific to my config?

Thanks again
 
Status
Not open for further replies.
Back
Top