Contribute
Register

[Guide] Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB

Status
Not open for further replies.
KNNSpeed said:
NEW!

After several weeks of toiling (it's July already?!), here's a new audio solution for perfect working audio. I basically ported the linux driver and created a GUI popup menu to configure the combo jack (see screenshot).

Features:
  • Fully working Combo Jack! (Heaphones, headset, AND line-in!)
  • New verb sending kext (no more need for CodecCommander on systems without EAPD troubles; VerbStub is simply a direct port of hda-verb for Linux)
  • Launchdaemon with Windows-like pop-up menu monitors the jack for insertion
  • Automatic OMTP (Nokia)/CTIA (iPhone) detection for headsets!
  • Fully commented sources
Notes:
  • Line-in mode disables audio output. I haven't been able to re-enable the speakers when the jack is purely an input, but that's the only "issue"
  • Zero "no audio after sleep" issues so far
  • Make sure to turn off "Use ambient noise reduction" when using an input that isn't the internal Mic (unless you find that it helps)
How does it work?

Simple! Due to the way the Realtek codec is set up on this machine, the ComboJack program watches the jack and switches the codec selector (node 0x22) to the correct input after applying all the requisite processing coefficients and pin widgets. This means that Mac OS only sees a built-in mic, but behind the scenes it actually is connecting to the headset and line-in ports. This works because all input paths lead through selector node 0x22 and into capture node 0x09, and the OS only acknowledges the capture node.

How to install (uses modded AppleALC):
  1. Disable SIP (I use 0x67 for CSRActiveConfig and 0xEE for booterconfig)
  2. Remove ALCPlugFix from /usr/bin (may need to kill with Activity Monitor first)
  3. Remove good.win.ALCPlugFix.plist from /Library/LaunchAgents (may need to launchctl unload first)
  4. Remove CodecCommander from Clover/kexts/Other (unless you need it, but it looks like the 9560 doesn't)
  5. Copy VerbStub.kext to EFI/Clover/kexts/Other
  6. Copy AppleALC to EFI/Clover/kexts/Other
  7. Change layout-id to 72 (in SSDT-Config -- 0x48 is hex)
  8. Run install.sh and read what it says
  9. Reboot (and enable SIP if you want)!
Download "ComboJack Installer.zip" and "AppleALC.kext.zip" for everything. The other zips are sources.
(Also included in "ComboJack Installer" is a folder containing the platform, layout, and pinconfigs used.)
Click to expand...

hey KNN do you think this will work on High Sierra?
 
lebish said:
On an unrelated note, I thought I should point out in this thread that it's possible to use builtin NVRAM on the XPS 15 9560. Remove "EmuVariableUefi-64.efi" and replace your "OsxAptioFix*.efi" driver with "OsxAptioFix2Drv-WTH.efi" (attached to this post). Reboot and you should now be using native NVRAM instead of emulated!

To test this:
  1. Swap out the Clover drivers as described above.
  2. Reboot.
  3. Open iTerm/Terminal and run "sudo nvram my-awesome-test=my-awesome-value", which will write the value "my-awesome-value" under the key "my-awesome-test" into the physical NVRAM.
    1. If you installed "RC Scripts" with Clover -- which this guide tells you to do -- you need to remove the shutdown script that persists emulated NVRAM to file: "sudo rm /etc/rc.shutdown.d/80.save_nvram_plist.local".
  4. Reboot.
  5. Back in your terminal run "sudo nvram my-awesome-test" -- which should print "my-awesome-test=my-awesome-value". If this works then the variables are persisting correctly in your physical NVRAM.
  6. Profit!
If you're using FileVault2, you may need additional drivers (i.e.: AsAmiShim.efi) to get the keyboard working at the Preboot screen. (I didn't write this driver, just found it on GitHub while researching other issues.)
Click to expand...
Thank you for sharing this. Haven't been on this for a while. Because you are running builtin NVRAM on the XPS 15 9560 were you able to turn the hibernate function back on?
 
tgmac said:
Bios update 1.9.1 is out and seems to be working fine. Should be safe to update.

I've also taken the liberty to attach an up-to-date CLOVER (works with 10.13.4 and all latest macOS updates) and KEXTS folder.

CLOVER.zip - Can be used and replace EFI/COLVER (note that only the essential kexts are located in Clover/kexts/Others as intended)
Kexts LE.zip - all kexts files are the latest ones available up until April 17th, 2018.
These KEXTS should be placed in /L/E (As intended) using something like KextBeast

sudo kextcache -i / afterwards and restart

As always, open up config.plist and generate your own serial & UUID. You can use Clover Configurator to do so.
Click to expand...

This doesn't work for me... :(

Coming from a working 10.12.6 installation, when I follow the instructions to update directly to 10.13 by maintaining HFS+, Terminal will do its thing, then upon reboot and selecting "Install macOS" in the bootloader, my system will hang indefinitely (see pic) and I'll need to force shutdown. I'm attaching my config.plist.
 

Attachments

  • IMG_0164.JPG
    IMG_0164.JPG
    982.8 KB · Views: 119
  • IMG_0165.JPG
    IMG_0165.JPG
    648.2 KB · Views: 93
  • config.plist
    15.3 KB · Views: 182
TheBeev said:
This doesn't work for me... :(

Coming from a working 10.12.6 installation, when I follow the instructions to update directly to 10.13 by maintaining HFS+, Terminal will do its thing, then upon reboot and selecting "Install macOS" in the bootloader, my system will hang indefinitely (see pic) and I'll need to force shutdown. I'm attaching my config.plist.
Click to expand...


"Problem Reporting" files are incomplete.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 

Attachments

  • debug_5094.zip
    5.8 MB · Views: 101
RehabMan said:
Your drivers64UEFI is not correct.
See notes in guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

And you should do some cleanup on Clover/kexts/Other as well.
(see guide)
Click to expand...

I cleaned up my kexts/other folder. I adjusted the drivers64UEFI folder to match how it was following KNNSpeed's guide (first post). If you believe there is something inherently wrong with his drivers64uefi folder, maybe that would be good for us all to know. The one thing I'm unsure of is which version of OsxAptioFixDrv to use. I read that AptioMemoryFix might be the best solution, so I tried that instead.

In any case, I still have the same problem. I cannot proceed to macOS install from the bootloader.
 

Attachments

  • drivers64UEFI.zip
    82.2 KB · Views: 119
  • IMG_0166.JPG
    IMG_0166.JPG
    951 KB · Views: 145
TheBeev said:
I cleaned up my kexts/other folder. I adjusted the drivers64UEFI folder to match how it was following KNNSpeed's guide (first post). If you believe there is something inherently wrong with his drivers64uefi folder, maybe that would be good for us all to know. The one thing I'm unsure of is which version of OsxAptioFixDrv to use. I read that AptioMemoryFix might be the best solution, so I tried that instead.

In any case, I still have the same problem. I cannot proceed to macOS install from the bootloader.
Click to expand...


"Problem Reporting" files are incomplete.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top