Contribute
Register

[Guide] Dell XPS13-9360 (2016) Sierra-10.12.2

Status
Not open for further replies.
I use the invalid ig-platform-id (0x12345678), so I can get into Sierra and rebuild cache, after that I restart with (0x19168086)

Make sure you're setting an invalid ig-platform-id and not an invalid FakeID.
FakeID and ig-platform-id are two different things.
Must use correct FakeID all the time, and invalid ig-platform-id when trying to get the kext in cache.
You seem to be mixing the two interchangeably.
 
Make sure you're setting an invalid ig-platform-id and not an invalid FakeID.
FakeID and ig-platform-id are two different things.
Must use correct FakeID all the time, and invalid ig-platform-id when trying to get the kext in cache.
You seem to be mixing the two interchangeably.

*Face palm*

I mixed those things... Now its working! Thank you so much Rehabman! I really appreciate your effort.
 

Attachments

  • Working.png
    Working.png
    96.8 KB · Views: 215
Did anyone get the resolution with the QHD, higher then 2048 x 1152?
 
64MB should work fine and is likely the default (most Kaby Lake laptops have so far had it set 64mb as default).
Yes, it works well when I set the value to 0x2(64M).
Thanks very much.
but what puzzles me is the defaut value of the 'DVMT Pre-Allocated' is 0x0(0M) on my Laptop
 
It is likely the HackrNVMeFamily you have installed to the system partition was not generated with --spoof (impossible for me to verify here).
Since you're injecting one that is from EFI/Clover/kexts, remove the one that you installed to the system partition and use the injected one only.
Thanks again for helping!
According to the info.plist in HackrNVMeFamily,I think the creation of HackrNVMeFamily.kext with --spoof option is all right,as info.plist have follow strings:

<key>IOPCIClassMatch</key>
<string>0x0108ff00&amp;0xFFFFFF00</string>

And I'll attach it in this post.

Secondly,I followed your instruction,removed HackrNVMeFamily.kext from /L/E, then rebooted.And with no luck,still I cannot see the nvme disk.kextstat can see the HackrNVMeFamily.kext had been loaded.

I think there maybe two reasons for this issue:
1. The kext driver is not suitable for my nvme disk,but as so many people have installed mac os 10.12.X in it.This reason seems no possibility to be right.
2. There is sth. wrong with my precedure of using SSDT-NVMe-Pcc.aml and rename _DSM to XDSM to change the device id.I want to have another try to load all aml files use "SortedOrder" array after _DSM rename.This is done by sachaaaz ,he 's done it wrong at first for not adding the SSDT-NVMe-Pcc.aml to the array.

May there be some method to confirm what excatly the device id of nvme disk,was it changed already?

Thanks in advance!
 

Attachments

  • HackrNVMeFamily-10_12_2.kext.zip
    88.7 KB · Views: 101
Last edited:
  • Battery life is definitely worse than Windows

Disabling the SD-reader in the BIOS does improve the battery life, almost for 1 hour. (on 3200x1800, so maybe the 1920x1080, will have more then 1 hour extra battery)

Here you can see the results...

Left one is showing the SD-OFF results
Right one is showing the SD-ON results
 

Attachments

  • SD OFF.png
    SD OFF.png
    54.1 KB · Views: 172
  • SD ON.png
    SD ON.png
    50.3 KB · Views: 170
Last edited:
Yes, it works well when I set the value to 0x2(64M).
Thanks very much.
but what puzzles me is the defaut value of the 'DVMT Pre-Allocated' is 0x0(0M) on my Laptop

The zero value may mean BIOS default (which still may be 64mb).
Does it work at default too?
 
Thanks again for helping!
According to the info.plist in HackrNVMeFamily,I think the creation of HackrNVMeFamily.kext with --spoof option is all right,as info.plist have follow strings:

<key>IOPCIClassMatch</key>
<string>0x0108ff00&amp;0xFFFFFF00</string>

And I'll attach it in this post.

Secondly,I followed your instruction,removed HackrNVMeFamily.kext from /L/E, then rebooted.And with no luck,still I cannot see the nvme disk.kextstat can see the HackrNVMeFamily.kext had been loaded.

I think there maybe two reasons for this issue:
1. The kext driver is not suitable for my nvme disk,but as so many people have installed mac os 10.12.X in it.This reason seems no possibility to be right.
2. There is sth. wrong with my precedure of using SSDT-NVMe-Pcc.aml and rename _DSM to XDSM to change the device id.I want to have another try to load all aml files use "SortedOrder" array after _DSM rename.This is done by sachaaaz ,he 's done it wrong at first for not adding the SSDT-NVMe-Pcc.aml to the array.

May there be some method to confirm what excatly the device id of nvme disk,was it changed already?

Thanks in advance!

In the files you provided previously, SortedOrder was not specified in config.plist, so the SSDT will definitely load just by being in ACPI/patched.
You should try without the hotpatch setup (eg. without all the extra SSDTs)
Did you set SATA mode to AHCI?
 
Disabling the SD-reader in the BIOS does improve the battery life, almost for 1 hour. (on 3200x1800, so maybe the 1920x1080, will have more then 1 hour extra battery)

Here you can see the results...

Left one is showing the SD-OFF results
Right one is showing the SD-ON results

Yes it does indeed improve battery life on the FHD version as well. I've been experimenting with many different setups and I've managed to get the battery life up to 10-11 hours with light usage (web browsing, some youtube, couple movies, etc.) with brightness at around 40%. Will definitely update the guide as soon as I feel confident in the numbers.

One issue I've been having though is that the power-savings do not survive sleep. My usual idle is at around 0.55-0.65W (with SD turned off in BIOS), but after waking from sleep it kicks back up to around 1.5W, and the extra battery life is gone. I am not currently using ssdtPRGen.sh though, and instead using HWPEnabler.kext with custom values for min-max, etc. (this helps with heat as well.) Do your power savings survive sleep?
 
Status
Not open for further replies.
Back
Top