Jump to content

blazinsmokey

Members
  • Content Count

    90
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    blazinsmokey got a reaction from surfinchina in Corsair iCUE (MacOS) Now Available as Open Beta!   
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this.
     
    Link below and the post it refers to.
    http://forum.corsair.com/v3/showthread.php?p=982647#post982647
     
     
    Hi everyone,
    It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! 
    Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg
     
    Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks:
    1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.
    2.) Complete iCUE for Windows and then port it over to macOS.
    3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
     
    The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update:
    K68 RGB
    K70 RGB MK.2 SE
    K70 RGB MK.2/RAPIDFIRE
    K70 RGB MK.2 LP
    Strafe RGB MK.2 
    M65 RGB Elite
    M65 PRO RGB
    K70 RGB LUX
    K70 RGB RAPIDFIRE
    SCIMITAR PRO
    STRAFE RGB
    HARPOON RGB
    All VOID headsets (except Stereo)
    All HS headsets (except Stereo)
    ST100
    MM800 (All versions)
     
    To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already:
    K95 RGB PLATINUM
    K55 RGB
    K63 WIRELESS/SE
    DARK CORE RGB/SE
     
    Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. 
    I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products!
     
    Regards,
    James
     
    FAQ:
    1.) What products are supported in iCUE for macOS?
    iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads).
    2.) Why does iCUE for macOS not support DIY products?
    We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support.
    3.) Is it possible to update firmware on iCUE macOS in the future?
    Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta.
    4.) Is there anything missing from iCUE macOS from Windows besides device support?
    We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now.
    5.) Will we be able to update iCUE versions on macOS?
    Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows.
    6.) Is there anything special I need to do in macOS?
    If you want key repeat enabled in macOS, you will need to enable this through the terminal.
    This is the command to enable press and hold:
    Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return>
    Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return>
    (Thanks Manofclay)
    After you enable this, you will need to restart your system.
    7.) Is this an official release for macOS?
    No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire.
    8.) What version of macOS does this support?
    We are supporting High Sierra and newer but we recommend using the latest if possible.
     
  2. Like
    blazinsmokey got a reaction from surfinchina in Corsair iCUE (MacOS) Now Available as Open Beta!   
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this.
     
    Link below and the post it refers to.
    http://forum.corsair.com/v3/showthread.php?p=982647#post982647
     
     
    Hi everyone,
    It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! 
    Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg
     
    Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks:
    1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.
    2.) Complete iCUE for Windows and then port it over to macOS.
    3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
     
    The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update:
    K68 RGB
    K70 RGB MK.2 SE
    K70 RGB MK.2/RAPIDFIRE
    K70 RGB MK.2 LP
    Strafe RGB MK.2 
    M65 RGB Elite
    M65 PRO RGB
    K70 RGB LUX
    K70 RGB RAPIDFIRE
    SCIMITAR PRO
    STRAFE RGB
    HARPOON RGB
    All VOID headsets (except Stereo)
    All HS headsets (except Stereo)
    ST100
    MM800 (All versions)
     
    To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already:
    K95 RGB PLATINUM
    K55 RGB
    K63 WIRELESS/SE
    DARK CORE RGB/SE
     
    Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. 
    I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products!
     
    Regards,
    James
     
    FAQ:
    1.) What products are supported in iCUE for macOS?
    iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads).
    2.) Why does iCUE for macOS not support DIY products?
    We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support.
    3.) Is it possible to update firmware on iCUE macOS in the future?
    Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta.
    4.) Is there anything missing from iCUE macOS from Windows besides device support?
    We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now.
    5.) Will we be able to update iCUE versions on macOS?
    Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows.
    6.) Is there anything special I need to do in macOS?
    If you want key repeat enabled in macOS, you will need to enable this through the terminal.
    This is the command to enable press and hold:
    Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return>
    Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return>
    (Thanks Manofclay)
    After you enable this, you will need to restart your system.
    7.) Is this an official release for macOS?
    No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire.
    8.) What version of macOS does this support?
    We are supporting High Sierra and newer but we recommend using the latest if possible.
     
  3. Like
    blazinsmokey got a reaction from surfinchina in Corsair iCUE (MacOS) Now Available as Open Beta!   
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this.
     
    Link below and the post it refers to.
    http://forum.corsair.com/v3/showthread.php?p=982647#post982647
     
     
    Hi everyone,
    It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! 
    Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg
     
    Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks:
    1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.
    2.) Complete iCUE for Windows and then port it over to macOS.
    3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
     
    The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update:
    K68 RGB
    K70 RGB MK.2 SE
    K70 RGB MK.2/RAPIDFIRE
    K70 RGB MK.2 LP
    Strafe RGB MK.2 
    M65 RGB Elite
    M65 PRO RGB
    K70 RGB LUX
    K70 RGB RAPIDFIRE
    SCIMITAR PRO
    STRAFE RGB
    HARPOON RGB
    All VOID headsets (except Stereo)
    All HS headsets (except Stereo)
    ST100
    MM800 (All versions)
     
    To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already:
    K95 RGB PLATINUM
    K55 RGB
    K63 WIRELESS/SE
    DARK CORE RGB/SE
     
    Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. 
    I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products!
     
    Regards,
    James
     
    FAQ:
    1.) What products are supported in iCUE for macOS?
    iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads).
    2.) Why does iCUE for macOS not support DIY products?
    We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support.
    3.) Is it possible to update firmware on iCUE macOS in the future?
    Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta.
    4.) Is there anything missing from iCUE macOS from Windows besides device support?
    We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now.
    5.) Will we be able to update iCUE versions on macOS?
    Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows.
    6.) Is there anything special I need to do in macOS?
    If you want key repeat enabled in macOS, you will need to enable this through the terminal.
    This is the command to enable press and hold:
    Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return>
    Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return>
    (Thanks Manofclay)
    After you enable this, you will need to restart your system.
    7.) Is this an official release for macOS?
    No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire.
    8.) What version of macOS does this support?
    We are supporting High Sierra and newer but we recommend using the latest if possible.
     
  4. Like
    blazinsmokey got a reaction from surfinchina in Corsair iCUE (MacOS) Now Available as Open Beta!   
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this.
     
    Link below and the post it refers to.
    http://forum.corsair.com/v3/showthread.php?p=982647#post982647
     
     
    Hi everyone,
    It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! 
    Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg
     
    Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks:
    1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.
    2.) Complete iCUE for Windows and then port it over to macOS.
    3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
     
    The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update:
    K68 RGB
    K70 RGB MK.2 SE
    K70 RGB MK.2/RAPIDFIRE
    K70 RGB MK.2 LP
    Strafe RGB MK.2 
    M65 RGB Elite
    M65 PRO RGB
    K70 RGB LUX
    K70 RGB RAPIDFIRE
    SCIMITAR PRO
    STRAFE RGB
    HARPOON RGB
    All VOID headsets (except Stereo)
    All HS headsets (except Stereo)
    ST100
    MM800 (All versions)
     
    To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already:
    K95 RGB PLATINUM
    K55 RGB
    K63 WIRELESS/SE
    DARK CORE RGB/SE
     
    Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. 
    I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products!
     
    Regards,
    James
     
    FAQ:
    1.) What products are supported in iCUE for macOS?
    iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads).
    2.) Why does iCUE for macOS not support DIY products?
    We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support.
    3.) Is it possible to update firmware on iCUE macOS in the future?
    Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta.
    4.) Is there anything missing from iCUE macOS from Windows besides device support?
    We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now.
    5.) Will we be able to update iCUE versions on macOS?
    Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows.
    6.) Is there anything special I need to do in macOS?
    If you want key repeat enabled in macOS, you will need to enable this through the terminal.
    This is the command to enable press and hold:
    Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return>
    Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return>
    (Thanks Manofclay)
    After you enable this, you will need to restart your system.
    7.) Is this an official release for macOS?
    No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire.
    8.) What version of macOS does this support?
    We are supporting High Sierra and newer but we recommend using the latest if possible.
     
  5. Like
    blazinsmokey reacted to vit9696 in VirtualSMC — SMC Emulator   
    SMC emulator with 2nd generation SMC support. Includes some monitoring plugins as API usage examples. New plugin additions are very welcome, given that they are well-written.   Source code: repository. FAQ and documentation: link. Features and configuration: link.   I wish to express my deep gratitude to all the people who worked on this project with me.
  6. Like
    blazinsmokey reacted to vit9696 in AptioMemoryFix   
    I thought it was worth making a separate thread for our AptioFix discussions.

    Some links to relevant posts (suggest us gather stuff here):
    1. Information about APTIO V nvram bugs
    2. Z97 NvramSmi code & boot.efi memory move code
    3. KASLR slide calculation & usage
    4. Slide calculation formula
    5. Debug printing mess in boot.efi
  7. Like
    blazinsmokey reacted to Andrey1970 in VirtualSMC — SMC Emulator   
    support fans reading
    https://github.com/acidanthera/VirtualSMC/releases
  8. Thanks
    blazinsmokey got a reaction from waysgim in XPS 9560 Mojave Guide   
    Disclaimer: I am no expert or claim to be an expert in this field. I learn new things every time I dwell in the world of Hackintosh. All constructive criticism is welcomed. Lets get these laptops to be one of the best hackbooks.   My hardware Dell XPS 9560 1080p i7-7700HQ Intel HD 630 PM961 Samsung NVME 512 Dell DW1560 (Broadcom BCM94352Z) 97whr Battery Overview I've been using and working on this laptop since its launch. My model was one of the first batches released, so I don't even have the fingerprint reader most people have. There was minor success until KNNSpeed came along with his guide. Seems he has since abandon it but a lot of the work he provided is still in effect today. Many advancements have been made since Sierra and KNNSpeed's guide. Lilu, Whatevergreen and now VirtualSMC. So I've taken some time to move our laptop to these new developments and will try to keep things to date. I also used wmchris' work he did on the 9550 to understand some of these new changes so thanks for his work as well. I have tried to make it as clean as possible but again I'm as noob as most of you. For now I am very happy with how it is working, especially with VoodooI2C.   What's Included clover folder disable hibernate script combo jack installer What Works CPU Power Management Native NVRAM Battery Support Sleep and Wake with Lid Open and Close (10 hours = ~2% battery loss) Intel HD 620 HDMI out w/ Audio (1080p) Audio ALC298 Headphone Jack/Combo Jack (headphone / headset(w/mic) support) Brightness Keys Brightness saved after restart Keyboard Trackpad with Gestures Webcam WiFi and Bluetooth iCloud Services Continuity and Hand-off USB-C / Thunderbolt Hot plug (Updated 11/12/18, check Understanding SSDT Hot Patching for more info) What Doesn't Work Finger Print Sensor NVIDIA GTX 1050 SD CARD Reader Keyboard, sort of. Clover Kext Injection of VoodooPS2Controller.kext doesn't work on cold boots, system must be restarted and it'll work. I believe this is fixed by installing into /Library/Extensions. Not Tested File Vault 2 Currently being tested, link found here #20 Hibernation I disabled it, the possibility of data corruption out weighs the minimal benefits, plus the writes to our NVME or even SATA SSD will shorten its life. Some have been using it with no reports of corruption yet but you have been warned. What Needs Improvement Second stage boot glitch. About halfway through Apple logo and loading screen there's a horizontal glitch across the screen for as a second. I tried some things without success but it's really just an OCD thing. When waking from sleep by opening the lid, the screen takes a second or two to come on and there's a black flash but then functions normally. Battery percentage while mostly accurate is weird sometimes. For example sometimes it's 97% and I plug it in and it shoots to 100%. Nothing serious but I think improvements will come with newer version of VirtualSMC and SMCBatteryManager. VoodooPS2Controller injected by Clover doesn't work on cold boots, does work after a restart. Current fix is to install in /Library/Extensions. BIOS Configuration Will fill this out later but it's the usual. You can use KNNSpeed's BIOS Settings found here https://www.tonymacx86.com/threads/guide-dell-xps-15-9560-4k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/. Currently using BIOS 1.12.1 (11/9) If you are not using a Windows dual boot you can easily update the BIOS from within the BIOS by using a flash drive and placing the .exe file directly on it. Has to be a FAT32 partition I believe. I placed it in my Clover EFI partition for the update. Smooth sailing. Install Work in progress, I'll fill out better details when I have time. You should be able to create a macOS Mojave Clover USB installer and replace EFI with mine, with little adjustments. SMBIOS info included is pre generated but generate your own SMBIOS info if you want working and secure iCloud services. My Samsung PM961 is not 4Kn sector, seems there is native support for it and matches a native device ID. There are plenty of guides to get your NVME to be usable if this is not the case but here's one that may help. KextsToPatch Name: com.apple.iokit.IONVMeFamily Find: F6C1100F 85410100 00 Replace: F6C1010F 85410100 00 Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01, credit RehabMan based on 10.12 patch (c) Pike R. Alpha Note for 4K screen users you may or may not need to add -cdfon to boot-arg but I have already added enable-hdmi20 IGPU entry in Devices/Properties which should be suitable as well. Please report. Clover Boot Loader Settings We are working with native nvram here on our laptops. You should not have nvram.plist, EmuVariableUEFI or RC scripts. If you have installed these on your boot drive you need to remove them and clear nvram from from Clover boot loader using F11. Clover for UEFI booting only Install Clover in the ESP UEFI Drivers DataHubDxe-64 FSInject-64 ApfsDriverLoader-64 AptioMemoryFix (installed from https://github.com/acidanthera/AptioFixPkg) HFSPlus FileVault 2 Files Still testing Post Install Disable hibernate. A script is included, cd to directory of script and run. Every update or any major changes in your config, please do your self a favor unless you like corrupt data. RUN THIS SCRIPT AGAIN! Install VoodooPS2Controller.kext to L/E so keyboard works on cold boots. If you find yourself without keyboard after a cold boot, restart for it to pickup. This is weird but Rehabman has specified in his install instructions to to install to L/E so maybe this is the reason. I will look further into this as Clover injection has worked for me up until now but this one kext install isn't the end of the world. You may also do as Rehabman suggests in his guides and install all other non-essential kexts if you want but I have not. Headphone/Headset/Combo Jack, thank KNNSpeed for his work on this. His work and instructions is linked here https://www.tonymacx86.com/threads/guide-dell-xps-15-9560-4k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/page-9#post-1539760. Verbstub.kext is already included in EFI/Clover/Kexts/Other and the layout is also set to 72 via SSDT. You no longer need a modded AppleALC as that modification is now included. So we just need to run his install script. Now when you insert anything into the jack, the ComboJack pop up will ask you what type of device you connected. Bluetooth two methods (Updated 11/1) Sorry, my mistake, I had BrcmFirmwareRepo being injected where it should not be the case. Pairing did not work although AirDrop worked fine. Credit to [USER=368095]@dmitry_matora[/USER] for spotting this The Clover/kexts/Other folder now replaces that with BrcmFirmwareData.kext. This injections does work but needs dart=0 in clover config. Credit to [USER=6160]@fabiofabio[/USER] for commenting about the need for dart=0 If you are not comfortable with above injection method, remove the files and properly install BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext to L/E Trackpad Settings Optional Sensors In my experience sensor kexts can cause problems in the long run when dealing with updates. I don't monitor my system like this and feel that Intel Power Gadget is enough for me when necessary. I have however tested this functionality, but do not expect me to keep up with this. How To (https://github.com/acidanthera/VirtualSMC)Download the release from link above. Install HWMonitor but do not install FakeSMC or it's sensors. Only the software. You can download the package here https://github.com/kozlekek/HWSensors/releases Install SMCProcessor.kext from VirtualSMC in EFI/CLOVER/kexts/Others Restart your system Other sensors from VirtualSMC could be tested as well, I however will not be doing so. Please report with your findings.   Geekbench 4.3   Cinebench R15.038 CPU   Persistence and Upgrading Updating Kexts I use a nice little tool called Kext Updater to check for updates and then manually install where needed. https://bitbucket.org/profdrluigi/kextupdater/overview Mojave 10.14 to 10.14.1 Make sure your kexts are up to date or use the latest clover.zip attachment Rebuild kext cache for our trackpad to come back to life. https://github.com/alexandred/VoodooI2C/issues/128 Troubleshooting You're a lot less likely to get help with out a detailed explanation of the problem and what you've tried as well as including problem reporting files. Problem Reporting files can easily be generated by a script https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/   Understanding config.plist ACPI Section DSDT patches section is self explanatory. Standard changes and Method renames for the SSDT hot patches. SSDT includes Use SystemIO, PluginType 1 and PluginType=Yes. Drop SSDT Tables, xh_rvp11 and PtidDevc. Fix Headers, Reset Address 0x0CF9 and Reset Value 0x06. SortedOrder is not necessary for this setup. Boot Section Arguments, darkwake=no, necessary to sleep properly. dart=0 while eliminates problems with VT-D also helps load BrcmFirmwareData.kext. Without this flag, timeouts will occur causing very long boot and shutdown times plus Bluetooth doesn't work. Custom Flags, brcmfx-country=#a to ignore country code for WiFi, helpful for 5GHz. XMPDetection=Yes, better ram speed detection but can be set to NO as well. Boot Graphics Section Empty CPU Section HWPEnabled=YES, this is needed since we are not using SSDT-XCPM. In combo with CPUFriend.kext and CPUFriendDataProvider.kext we get idle at 800MHz vs native 1.3GHz. So a bit of battery life savings here. CPU will still hit 3.8GHz turbo boost. Devices Section USB Inject, Add ClockID, and FixOwnership = YES. AddProperties, IntelGFX the key and value help HDMI audio out. Properties, the device listed PciRoot(0x0)/Pci(0x2,0x0) is the graphics location. The included Properties Key and Property Values took KNNSpeeds old frame buffer patch to recognize the XPS15 ports in macOS and converted for use via WhateverGreen through this method. Disable Drivers Section VBoxHfs GUI Section Put in your screen resolution but the rest is really up to you. Graphics Section Empty. Isn't that great?! Kernel and Kext Patches Section Apple RTC, AppleIntelCPUPM, KernelPM, DellSMBIOSPatch = YES KextsToPatch, nothing! KerneToPatch include patch for MSR 0xE2 _xcpm_idle prevent instant reboot (c) Pike R. Alpha and Disable panic kext logging on 10.14 release kernel (credit Vandroiy) RT Variable Section BooterConfig = 0xEE and CsrActiveConfig = 0x67 Generate a Rom SMBIOS Section MacBookPro 14,1 There are guides for using a proper serial and setting up these values for iCloud, you will need SmUUID and Board Serial Number. System Parameters Section Inject Kexts=Yes   Understanding drivers64UEFI ApfsDriverLoader-64.efi - loads APFS drivers AptioMemoryFix.efi - installed separately from https://github.com/acidanthera/AptioFixPkg DataHubDxe-64.efi - honestly don't know, but every source I found says it's always safe and no conflicts so... FSInject-64.efi - injects kexts HFSPlus.efi -  hfs support, optional can be removed   Understanding SSDT Hot Patching SSDT-ALC298.aml - audio SSDT-ALS0.aml - ambient light sensor, we don't have one this helps fakes it for saving brightness SSDT-BRT6.aml - brightness keys SSDT-Config.aml - rehabmans rmcf configuration SSDT-DeepIdle.aml - enables deep idle support, power saving SSDT-DMAC.aml - DMA controller SSDT-HDEF.aml - audio properties SSDT-I2C.aml - voodooi2c trackpad SSDT-LPC.aml - LPC bus SSDT-MCHC.aml - memory controller SSDT-MEM2.aml - via KNNSpeed's explanation "Defines a fixed memory region that gets used for something (hardly any information on it, but PNP0C01 is “System Board” in Windows so it has to do with motherboard resource allocation). Presumably, it’s related to the Integrated Graphics, as that’s the section in which Apple defines the MEM2 device." SSDT-PMCR.aml - via KNNSpeed's explanation "Complements the PPMC (Platform Power Management Controller) with the seemingly useless PMCR device that exists in Mac DSDTs. It doesn’t hurt anything to have this, and it can really only help, so it’s here." SSDT-PNLF.aml - backlight SSDT-PTSWAK.aml - powers on dGPU before sleep and power is off after wake for tracking purposes SSDT-RMDGPU.aml - powers off dGPU SSDT-SMBUS.aml - SMBus SSDT-TB3-V1.aml - allows thunderbolt and USB-C hot plug https://www.tonymacx86.com/threads/in-progress-ssdt-for-thunderbolt-3-hotplug.248784/ Info #46 and final implementation #118 After comparing KNNSpeed's methods in SSDT-TYPC with SSDT-TB3-V1 I came to the conclusion KNNSpeed's version was not only conflicting but also not complete so the swap here makes things work wonderfully.  SSDT-UIAC.aml - USB ports defined, use with USBInjectALL.kext SSDT-UPRW.aml - Stops instant wake from USB and Lan SSDT-USBX.aml - USB Power properties SSDT-XOSI.aml - system exposed as if Windows 10 SSDT-YTBT.aml - USB Type-C hot plug   Understanding Kexts Injected AirportBrcmFixup.kext - Wifi, DW1560 used with Lilu AppleALC.kext - Audio used with Lilu AppleBacklightFixup.kext - Backlight, Brightness. Used with Lilu BrcmFirmwareData.kext - Bluetooth used with BrcmPatchRAM2 BrcmPatchRAM2.kext - Bluetooth used with FakePCIID https://github.com/RehabMan/OS-X-BrcmPatchRAM BT4LEContiunityFixup.kext - Bluetooth Continuity used with Lilu CPUFriend.kext - allows for idling at 800MHz used with Lilu CPUFriendDataProvider.kext - used with  CPUFriend and with Lilu FakePCIID_Intel_HDMI_Audio.kext - HDMI audio used with FakePCIID FakePCIID.kext - Rehabman's powerful PCI ID provider https://github.com/RehabMan/OS-X-Fake-PCI-ID HibernationFixup.kext - Used for hibernation, not recommended but just incase this helps if you accidentally forget to to disable. Used with Lilu. Lilu.kext - kext that provides platform for arbitrary kext, library, and program patching https://github.com/acidanthera/Lilu SATA-unsupported.kext - SATA100 unsupported, even if you're only using NVME, keep this to avoid errors https://github.com/RehabMan/hack-tools SMCBatteryManager.kext - battery support used with VirtualSMC USBInjectAll.kext - USB support https://github.com/RehabMan/OS-X-USB-Inject-All VerbStub.kext - audio support from KNNSpeed VirtualSMC.kext - FakeSMC replacement https://github.com/acidanthera/VirtualSMC VoodooI2C.kext - Trackpad with gestures support https://github.com/alexandred/VoodooI2C VoodooI2CHID.kext - Trackpad supports VoodooI2C VoodooPS2Controller.kext - Enables Keyboard https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller WhateverGreen.kext - Graphics used with Lilu https://github.com/acidanthera/WhateverGreen   Updates 10/28 Added trackpad options to Post Install Section, Geekbench 4.3 scores   10/29 Added SMCProcessor.zip and info on using with HWMonitor, added more links and some formatting   11/1 Added new Clover folder XPS9560-Clover v2.zip with updated kexts and drivers. Added Bluetooth pairing fix plus install options and extra trackpad option. FileVault 2 currently being tested by [USER=6160]@fabiofabio[/USER] his post here #20. Adjusted Optional sensors with link and removed attached SMCProcessor from post.   11/5 Clover updated v2.1 brightness save fixed by editing config.plist #70. Cinebench CPU benchmarks posted. TB3 testing in progress look here #53 please test if you have the hardware and report.   11/8 Updated with Clover Boot Loader Settings, other minor fixes   11/12 Clover updated v3.0 Thunderbolt 3 and USB-C hot plug working, removed SSDT-TYPC.aml and replaced with SSDT-TB3-V1.aml from https://www.tonymacx86.com/threads/in-progress-ssdt-for-thunderbolt-3-hotplug.248784/. Updated clover config dsdt hot patch comments to reflect this change. Clover and Kexts are latest versions. disablehibernate.zip
    ComboJack Installer.zip
    XPS9560-CLOVER v3.0.zip
  9. Thanks
    blazinsmokey got a reaction from waysgim in XPS 9560 Mojave Guide   
    Disclaimer: I am no expert or claim to be an expert in this field. I learn new things every time I dwell in the world of Hackintosh. All constructive criticism is welcomed. Lets get these laptops to be one of the best hackbooks.   My hardware Dell XPS 9560 1080p i7-7700HQ Intel HD 630 PM961 Samsung NVME 512 Dell DW1560 (Broadcom BCM94352Z) 97whr Battery Overview I've been using and working on this laptop since its launch. My model was one of the first batches released, so I don't even have the fingerprint reader most people have. There was minor success until KNNSpeed came along with his guide. Seems he has since abandon it but a lot of the work he provided is still in effect today. Many advancements have been made since Sierra and KNNSpeed's guide. Lilu, Whatevergreen and now VirtualSMC. So I've taken some time to move our laptop to these new developments and will try to keep things to date. I also used wmchris' work he did on the 9550 to understand some of these new changes so thanks for his work as well. I have tried to make it as clean as possible but again I'm as noob as most of you. For now I am very happy with how it is working, especially with VoodooI2C.   What's Included clover folder disable hibernate script combo jack installer What Works CPU Power Management Native NVRAM Battery Support Sleep and Wake with Lid Open and Close (10 hours = ~2% battery loss) Intel HD 620 HDMI out w/ Audio (1080p) Audio ALC298 Headphone Jack/Combo Jack (headphone / headset(w/mic) support) Brightness Keys Brightness saved after restart Keyboard Trackpad with Gestures Webcam WiFi and Bluetooth iCloud Services Continuity and Hand-off USB-C / Thunderbolt Hot plug (Updated 11/12/18, check Understanding SSDT Hot Patching for more info) What Doesn't Work Finger Print Sensor NVIDIA GTX 1050 SD CARD Reader Keyboard, sort of. Clover Kext Injection of VoodooPS2Controller.kext doesn't work on cold boots, system must be restarted and it'll work. I believe this is fixed by installing into /Library/Extensions. Not Tested File Vault 2 Currently being tested, link found here #20 Hibernation I disabled it, the possibility of data corruption out weighs the minimal benefits, plus the writes to our NVME or even SATA SSD will shorten its life. Some have been using it with no reports of corruption yet but you have been warned. What Needs Improvement Second stage boot glitch. About halfway through Apple logo and loading screen there's a horizontal glitch across the screen for as a second. I tried some things without success but it's really just an OCD thing. When waking from sleep by opening the lid, the screen takes a second or two to come on and there's a black flash but then functions normally. Battery percentage while mostly accurate is weird sometimes. For example sometimes it's 97% and I plug it in and it shoots to 100%. Nothing serious but I think improvements will come with newer version of VirtualSMC and SMCBatteryManager. VoodooPS2Controller injected by Clover doesn't work on cold boots, does work after a restart. Current fix is to install in /Library/Extensions. BIOS Configuration Will fill this out later but it's the usual. You can use KNNSpeed's BIOS Settings found here https://www.tonymacx86.com/threads/guide-dell-xps-15-9560-4k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/. Currently using BIOS 1.12.1 (11/9) If you are not using a Windows dual boot you can easily update the BIOS from within the BIOS by using a flash drive and placing the .exe file directly on it. Has to be a FAT32 partition I believe. I placed it in my Clover EFI partition for the update. Smooth sailing. Install Work in progress, I'll fill out better details when I have time. You should be able to create a macOS Mojave Clover USB installer and replace EFI with mine, with little adjustments. SMBIOS info included is pre generated but generate your own SMBIOS info if you want working and secure iCloud services. My Samsung PM961 is not 4Kn sector, seems there is native support for it and matches a native device ID. There are plenty of guides to get your NVME to be usable if this is not the case but here's one that may help. KextsToPatch Name: com.apple.iokit.IONVMeFamily Find: F6C1100F 85410100 00 Replace: F6C1010F 85410100 00 Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01, credit RehabMan based on 10.12 patch (c) Pike R. Alpha Note for 4K screen users you may or may not need to add -cdfon to boot-arg but I have already added enable-hdmi20 IGPU entry in Devices/Properties which should be suitable as well. Please report. Clover Boot Loader Settings We are working with native nvram here on our laptops. You should not have nvram.plist, EmuVariableUEFI or RC scripts. If you have installed these on your boot drive you need to remove them and clear nvram from from Clover boot loader using F11. Clover for UEFI booting only Install Clover in the ESP UEFI Drivers DataHubDxe-64 FSInject-64 ApfsDriverLoader-64 AptioMemoryFix (installed from https://github.com/acidanthera/AptioFixPkg) HFSPlus FileVault 2 Files Still testing Post Install Disable hibernate. A script is included, cd to directory of script and run. Every update or any major changes in your config, please do your self a favor unless you like corrupt data. RUN THIS SCRIPT AGAIN! Install VoodooPS2Controller.kext to L/E so keyboard works on cold boots. If you find yourself without keyboard after a cold boot, restart for it to pickup. This is weird but Rehabman has specified in his install instructions to to install to L/E so maybe this is the reason. I will look further into this as Clover injection has worked for me up until now but this one kext install isn't the end of the world. You may also do as Rehabman suggests in his guides and install all other non-essential kexts if you want but I have not. Headphone/Headset/Combo Jack, thank KNNSpeed for his work on this. His work and instructions is linked here https://www.tonymacx86.com/threads/guide-dell-xps-15-9560-4k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/page-9#post-1539760. Verbstub.kext is already included in EFI/Clover/Kexts/Other and the layout is also set to 72 via SSDT. You no longer need a modded AppleALC as that modification is now included. So we just need to run his install script. Now when you insert anything into the jack, the ComboJack pop up will ask you what type of device you connected. Bluetooth two methods (Updated 11/1) Sorry, my mistake, I had BrcmFirmwareRepo being injected where it should not be the case. Pairing did not work although AirDrop worked fine. Credit to [USER=368095]@dmitry_matora[/USER] for spotting this The Clover/kexts/Other folder now replaces that with BrcmFirmwareData.kext. This injections does work but needs dart=0 in clover config. Credit to [USER=6160]@fabiofabio[/USER] for commenting about the need for dart=0 If you are not comfortable with above injection method, remove the files and properly install BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext to L/E Trackpad Settings Optional Sensors In my experience sensor kexts can cause problems in the long run when dealing with updates. I don't monitor my system like this and feel that Intel Power Gadget is enough for me when necessary. I have however tested this functionality, but do not expect me to keep up with this. How To (https://github.com/acidanthera/VirtualSMC)Download the release from link above. Install HWMonitor but do not install FakeSMC or it's sensors. Only the software. You can download the package here https://github.com/kozlekek/HWSensors/releases Install SMCProcessor.kext from VirtualSMC in EFI/CLOVER/kexts/Others Restart your system Other sensors from VirtualSMC could be tested as well, I however will not be doing so. Please report with your findings.   Geekbench 4.3   Cinebench R15.038 CPU   Persistence and Upgrading Updating Kexts I use a nice little tool called Kext Updater to check for updates and then manually install where needed. https://bitbucket.org/profdrluigi/kextupdater/overview Mojave 10.14 to 10.14.1 Make sure your kexts are up to date or use the latest clover.zip attachment Rebuild kext cache for our trackpad to come back to life. https://github.com/alexandred/VoodooI2C/issues/128 Troubleshooting You're a lot less likely to get help with out a detailed explanation of the problem and what you've tried as well as including problem reporting files. Problem Reporting files can easily be generated by a script https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/   Understanding config.plist ACPI Section DSDT patches section is self explanatory. Standard changes and Method renames for the SSDT hot patches. SSDT includes Use SystemIO, PluginType 1 and PluginType=Yes. Drop SSDT Tables, xh_rvp11 and PtidDevc. Fix Headers, Reset Address 0x0CF9 and Reset Value 0x06. SortedOrder is not necessary for this setup. Boot Section Arguments, darkwake=no, necessary to sleep properly. dart=0 while eliminates problems with VT-D also helps load BrcmFirmwareData.kext. Without this flag, timeouts will occur causing very long boot and shutdown times plus Bluetooth doesn't work. Custom Flags, brcmfx-country=#a to ignore country code for WiFi, helpful for 5GHz. XMPDetection=Yes, better ram speed detection but can be set to NO as well. Boot Graphics Section Empty CPU Section HWPEnabled=YES, this is needed since we are not using SSDT-XCPM. In combo with CPUFriend.kext and CPUFriendDataProvider.kext we get idle at 800MHz vs native 1.3GHz. So a bit of battery life savings here. CPU will still hit 3.8GHz turbo boost. Devices Section USB Inject, Add ClockID, and FixOwnership = YES. AddProperties, IntelGFX the key and value help HDMI audio out. Properties, the device listed PciRoot(0x0)/Pci(0x2,0x0) is the graphics location. The included Properties Key and Property Values took KNNSpeeds old frame buffer patch to recognize the XPS15 ports in macOS and converted for use via WhateverGreen through this method. Disable Drivers Section VBoxHfs GUI Section Put in your screen resolution but the rest is really up to you. Graphics Section Empty. Isn't that great?! Kernel and Kext Patches Section Apple RTC, AppleIntelCPUPM, KernelPM, DellSMBIOSPatch = YES KextsToPatch, nothing! KerneToPatch include patch for MSR 0xE2 _xcpm_idle prevent instant reboot (c) Pike R. Alpha and Disable panic kext logging on 10.14 release kernel (credit Vandroiy) RT Variable Section BooterConfig = 0xEE and CsrActiveConfig = 0x67 Generate a Rom SMBIOS Section MacBookPro 14,1 There are guides for using a proper serial and setting up these values for iCloud, you will need SmUUID and Board Serial Number. System Parameters Section Inject Kexts=Yes   Understanding drivers64UEFI ApfsDriverLoader-64.efi - loads APFS drivers AptioMemoryFix.efi - installed separately from https://github.com/acidanthera/AptioFixPkg DataHubDxe-64.efi - honestly don't know, but every source I found says it's always safe and no conflicts so... FSInject-64.efi - injects kexts HFSPlus.efi -  hfs support, optional can be removed   Understanding SSDT Hot Patching SSDT-ALC298.aml - audio SSDT-ALS0.aml - ambient light sensor, we don't have one this helps fakes it for saving brightness SSDT-BRT6.aml - brightness keys SSDT-Config.aml - rehabmans rmcf configuration SSDT-DeepIdle.aml - enables deep idle support, power saving SSDT-DMAC.aml - DMA controller SSDT-HDEF.aml - audio properties SSDT-I2C.aml - voodooi2c trackpad SSDT-LPC.aml - LPC bus SSDT-MCHC.aml - memory controller SSDT-MEM2.aml - via KNNSpeed's explanation "Defines a fixed memory region that gets used for something (hardly any information on it, but PNP0C01 is “System Board” in Windows so it has to do with motherboard resource allocation). Presumably, it’s related to the Integrated Graphics, as that’s the section in which Apple defines the MEM2 device." SSDT-PMCR.aml - via KNNSpeed's explanation "Complements the PPMC (Platform Power Management Controller) with the seemingly useless PMCR device that exists in Mac DSDTs. It doesn’t hurt anything to have this, and it can really only help, so it’s here." SSDT-PNLF.aml - backlight SSDT-PTSWAK.aml - powers on dGPU before sleep and power is off after wake for tracking purposes SSDT-RMDGPU.aml - powers off dGPU SSDT-SMBUS.aml - SMBus SSDT-TB3-V1.aml - allows thunderbolt and USB-C hot plug https://www.tonymacx86.com/threads/in-progress-ssdt-for-thunderbolt-3-hotplug.248784/ Info #46 and final implementation #118 After comparing KNNSpeed's methods in SSDT-TYPC with SSDT-TB3-V1 I came to the conclusion KNNSpeed's version was not only conflicting but also not complete so the swap here makes things work wonderfully.  SSDT-UIAC.aml - USB ports defined, use with USBInjectALL.kext SSDT-UPRW.aml - Stops instant wake from USB and Lan SSDT-USBX.aml - USB Power properties SSDT-XOSI.aml - system exposed as if Windows 10 SSDT-YTBT.aml - USB Type-C hot plug   Understanding Kexts Injected AirportBrcmFixup.kext - Wifi, DW1560 used with Lilu AppleALC.kext - Audio used with Lilu AppleBacklightFixup.kext - Backlight, Brightness. Used with Lilu BrcmFirmwareData.kext - Bluetooth used with BrcmPatchRAM2 BrcmPatchRAM2.kext - Bluetooth used with FakePCIID https://github.com/RehabMan/OS-X-BrcmPatchRAM BT4LEContiunityFixup.kext - Bluetooth Continuity used with Lilu CPUFriend.kext - allows for idling at 800MHz used with Lilu CPUFriendDataProvider.kext - used with  CPUFriend and with Lilu FakePCIID_Intel_HDMI_Audio.kext - HDMI audio used with FakePCIID FakePCIID.kext - Rehabman's powerful PCI ID provider https://github.com/RehabMan/OS-X-Fake-PCI-ID HibernationFixup.kext - Used for hibernation, not recommended but just incase this helps if you accidentally forget to to disable. Used with Lilu. Lilu.kext - kext that provides platform for arbitrary kext, library, and program patching https://github.com/acidanthera/Lilu SATA-unsupported.kext - SATA100 unsupported, even if you're only using NVME, keep this to avoid errors https://github.com/RehabMan/hack-tools SMCBatteryManager.kext - battery support used with VirtualSMC USBInjectAll.kext - USB support https://github.com/RehabMan/OS-X-USB-Inject-All VerbStub.kext - audio support from KNNSpeed VirtualSMC.kext - FakeSMC replacement https://github.com/acidanthera/VirtualSMC VoodooI2C.kext - Trackpad with gestures support https://github.com/alexandred/VoodooI2C VoodooI2CHID.kext - Trackpad supports VoodooI2C VoodooPS2Controller.kext - Enables Keyboard https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller WhateverGreen.kext - Graphics used with Lilu https://github.com/acidanthera/WhateverGreen   Updates 10/28 Added trackpad options to Post Install Section, Geekbench 4.3 scores   10/29 Added SMCProcessor.zip and info on using with HWMonitor, added more links and some formatting   11/1 Added new Clover folder XPS9560-Clover v2.zip with updated kexts and drivers. Added Bluetooth pairing fix plus install options and extra trackpad option. FileVault 2 currently being tested by [USER=6160]@fabiofabio[/USER] his post here #20. Adjusted Optional sensors with link and removed attached SMCProcessor from post.   11/5 Clover updated v2.1 brightness save fixed by editing config.plist #70. Cinebench CPU benchmarks posted. TB3 testing in progress look here #53 please test if you have the hardware and report.   11/8 Updated with Clover Boot Loader Settings, other minor fixes   11/12 Clover updated v3.0 Thunderbolt 3 and USB-C hot plug working, removed SSDT-TYPC.aml and replaced with SSDT-TB3-V1.aml from https://www.tonymacx86.com/threads/in-progress-ssdt-for-thunderbolt-3-hotplug.248784/. Updated clover config dsdt hot patch comments to reflect this change. Clover and Kexts are latest versions. disablehibernate.zip
    ComboJack Installer.zip
    XPS9560-CLOVER v3.0.zip
  10. Like
    blazinsmokey reacted to Sascha_77 in Kext Updater: Keep your Kexts fresh with only one Click   
    Hmm. If you switched off the chime the user wouldn´t notified. Good suggestion. Will include it in the next update.
     
    EDIT:
    Released yesterday and included it.
  11. Like
    blazinsmokey reacted to Sascha_77 in Kext Updater: Keep your Kexts fresh with only one Click   
    You are tired searching Updates for your Kexts? With my little Tool its totally easy to have up-to-date Kexts. Simply Click "Start" and it will look if a new Version of your used Kexts is available. If there is a new Version available it will downloaded it to your Desktop and you can decide if you want to install it or not. It checks APFS and Clover too. The Database with the latest Versions available is updating every 6 Hours. Never it was more easy to be up to date.  
     
    I started developing this Tool since 04/2017. You can Download it on Github. 
     
    https://github.com/ProfDrLuigi/kextupdater/releases/latest
    Because M$ bought GitHub I closed my acc there immediatley. The Repo is now on Bitbucket.
    https://bitbucket.org/profdrluigi/kextupdater/downloads/
     
    There are some extra Options too. Loading Webdriver, Clover or Clover Nightly Build. And now have fun.
     
    Minimum OS for running the Updater is 10.10
     

     
     
  12. Like
    blazinsmokey got a reaction from Zsparrow0 in [Guide] Dell XPS 15 9560 - High Sierra 10.13.2   
    NvidiaGraphicsFixup is not just for NVIDIA. There's actually multiple uses for it besides making a NVIDIA card work.
    The reason for our laptops using this is stated clearly in the original guide created by KNNSpeed. Quoted below.
     
     
    Just like how a desktop can use this kext it to avoid black screen on boot by using a ConfigMap of "none" our laptops can use this method so that our HDMI out will function properly.
     
     
    Don't be sorry for wanting to help. If he removes that kext, how would you get the HDMI working the "optimized" way? I'm fascinated by your tremendous knowledge on how our hack's components are setup to function. Please enlighten us.
  13. Like
    blazinsmokey got a reaction from Zsparrow0 in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Hey man you PM'd me about my 9560 and sleep and also installation error which I told you to come here. I just noticed now, reading your post here that you're following the guide for the 9550, can I ask why? You have a 9560 don't you? You can follow this awesome guide KNNSpeed setup for us and in the past few pages or so you can find out the changes for high sierra. I believe one of my posts a few pages back even includes a EFI. Also listing your detailed hardware in your signature would a great benefit to you and the people trying to help you.
  14. Like
    blazinsmokey reacted to TheRacerMaster in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    It's caused by APFS+TRIM boot delays. You can fix that by specifying a longer FirstPollDelay (I use 16 seconds).
  15. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    BIOS 1.7.0 is safe (breaks nothing) over 1.6.2.
  16. Like
    blazinsmokey reacted to wmchris in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    usb-pd works. tested with an apple macbook pro usb-c pd charger.
  17. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Never tried; don't have a USD-PD charger that is powerful enough for my XPS.
     
     
    About BIOS 1.6.2:
    It does not break any patches or anything. If you update and something breaks (not the ACPIFamily kernel panic--just reboot and it's fine), then your install was not set up right to begin with. No issues with brightness keys, no issues with TB patches as far as I can tell. Dell added a new method  in the DSDT that runs when a thunderbolt device gets plugged in, though I am not sure what it does. It might have helped alleviate a massive memory management issue I have been encountering on Windows lately.
     
    Note: I'm still on Sierra.
  18. Like
    blazinsmokey reacted to Badruzeus in Clover Themes   
    Square shaped icons version of Lover, Material & One themes...
     
    "MaterialBox"
     

     
     
     
     
    ...and;
     
     
     
    Happy hackintosh. 
  19. Like
    blazinsmokey got a reaction from Akrobs in Dell XPS 15 (9560, Version 2017) compatibility information   
    KNNSpeed, I saw your guide and it's great, thanks. I noticed people stopped having to use a hacked voodoops2 (thanks freejack) to fix the trackpad going out. Haven't touched macOS since probably my last post here or at the other place. I'm assuming the BIOS updates eventually fixed something there. I had time yesterday and gave it go again. Posting here to not clog your thread up with different hardware and this thread seems more appropriate.
     
    I didn't do a clean install with your method but I used your files for reference and as the core after upgrading Clover and macOS to 10.12.5. My hardware is a bit different as seen in my signature. No fingerprint sensor either. Your guide was tremendously informative. I added/changed some things to work with my system. And everything is working for the most part. No real complaints, iMessage and iCloud services are working as well. 
     
    A real guide for this set of hardware may come later from me or hopefully someone else as I'm not that great at this stuff but consider this a mini guide. Looking forward to what High Sierra can do for us. I've only been playing with the laptop for hardly a day so bugs or other things may arise and I will update my post with findings or fixes. Feedback is more than welcomed.
     
    This is based off of what KNNSpeed has put together very nicely. I take no credit for this info really, credits to him and credits to the people he credited   
     
    My Hardware
    XPS 15 9560 1080p (FHD)  i7-7700HQ 16GB-2400 Intel HD 630 GTX 1050 Samsung PM961 512GB NVMe Dell DW1560 (WiFi Swap) No fingerprint sensor Warnings
    I do not have a 4k sector drive like in the KNNSpeed's guide. I highly recommend you follow the appropriate guide accordingly. HWmonitor will not work but you can easily added the needed files with KNNSpeed's guide. Not a fan of hwmonitor (personal opinion).  ACPI/patched differences
    SSDT-NVMe-Pcc.aml (added for Samsung PM961) SSDT-Fans.aml (removed, personal choice after KNNSpeeds suggestion) Kexts Removed
        I'm wondering if SATA-100-series-unsupported.kext could be implemented by a hot SSDT fix instead of injecting. I did test without it and it works fine, just the system report shows as generic SATA device. This could be an SSDT but KNNSpeed and now me are hoping for native support with High Sierra, fingers crossed.
    CoreDisplayFixup.kext (not necessary for 1080p models) CPUSensors.kext (hwmonitor) GPUSensors.kext (hwmonitor) LPCSensors.kext (hwmonitor) Kexts Added
    FakePCIID_Broadcom_WiFi.kext (added, for Dell DW1560) HackrNVMeFamily-10_12_3.kext (added, for Samsung PM960) BrcmFirmwareData.kext, BrcmPatchRAM2.kext are for the bluetooth. I'm pretty sure I used the ones I had working before but I'm not 100% as I did it really late at night. Sorry. I don't believe it matters though. config.plist
    Acpi - Not using sorted order SSDT (I'm a lazy {censored}) Kexts to patch - I removed the existing AirPortBrcm patch and replaced accordingly <dict> <key>Comment</key> <string>AirPortBrcm4360 - fcvo - enable WiFi oscillator (10.12)</string> <key>Disabled</key> <false/> <key>Find</key> <data> gflSqgAAdSk= </data> <key>MatchOS</key> <string>10.12.x</string> <key>Name</key> <string>AirPortBrcm4360</string> <key>Replace</key> <data> gflSqgAAZpA= </data> </dict> <dict> <key>Comment</key> <string>10.11-BT4LE-Handoff-Hotspot-lisai9093</string> <key>Disabled</key> <false/> <key>Find</key> <data> 4885ff7447488b07 </data> <key>Name</key> <string>IOBluetoothFamily</string> <key>Replace</key> <data> 41be0f000000eb44 </data> </dict> RT Variables - Changed BooterConfig to 0x28, CsrActiveConfig to 0x67 SMBIOS 13,3 generate or find your own System Parameters - nothing checked and Inject Kexts set to Detect. Miscellaneous
    Using OsxAptioFixDrv-64.efi instead of the fix2 version. I am on the latest BIOS 1.3.3 but I couldn't boot with the fix 2. I'm not sure if there are repercussions but this is something to note. Clover 4091 Removed all themes, installed CrispyOSX. Issues
    The trackpad, lol. Works well for the most part though, at least it's usable. Seems when you change settings in accessibility > trackpad option it gets reset when you change things in trackpad options. The gestures seems to not match up all the time. Have the dragging enabled with drag lock, initially wanted three finger drag but then mission control stopped working and there was a noticeable lag or something after dragging, almost like a slight freeze.  
    Trackpad
        After KNNSpeed's explanation it seems this is the best we have so far. It works, but could be better. In his guide in the optional step 8 I didn't understand at first but the gestures are actually inputting to the system keyboard strokes. Makes much more sense and you can read his explanation below. I will be tinkering with this and trying to find solutions. The hackbook pro is damn near flawless once the trackpad is more like a real MBP.
     
    Edit: How could I forget a geek bench, lol. 
    Geekbench 4.1.0 (400460) 

     
    6/18 After KNNSpeeds Suggestions CLOVER.zip
     
  20. Like
    blazinsmokey got a reaction from NOTNlCE in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Took the plunge to 10.12.6 just now. Do yourself a favor don't change anything in your SMBIOS or config,plist until after you finish the update b/c when it reboots for the update you won't have support yet, lol. I had my install USB so no big deal here. Also sign out of all iCloud, iMessage accounts before changing SMBIOS, so it doesn't get all jacked up. 
     
    You can now safely remove all the faking of Skylake CPU and GPU from clover config, no need to inject anything either. Under Devices section you no longer need the IntelGFX Fake ID, Graphics section can be completely empty, and remove FakeCPUID entry in Kernel and Kext Patches. All while using the new clover configurator generated MBP 14,3 SMBIOS. 
     
    You will still need the kexts FakePCIID_Intel_HD_Graphics and FakePCIID_Intel_HDMI_Audio.
     
    Took another few Geekbench of CPU and no improvements, all within 1% of each other.
    Unfortunately I did not bench the graphics before this update so that is a lost on my part.
     
    Faking Skylake     Native Kaby Lake 
     
    My config.plist config.zip as with all config.plist, don't be stupid and get your own serial.
  21. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Significantly improved the touchpad experience. It's very similar to the Apple Wireless Trackpad (v1) with this kext (I tweaked it as best I could), which in turn is pretty similar to the MBP's built-in trackpad.
     
    Remove VoodooPS2Controller to use it (also remove the two voodoops2 scripts that had to be installed if using RehabMan's fork instead of the version in post #1). Also need to "unflip" Command and Alt if they were flipped, and restore all keyboard shortcuts to defaults. With this kext, only 3-finger swipe down, 4-finger swipe down, and "show notification center" via two-finger edge swipe (both from the right and left work) need to be configured as keyboard shortcuts, otherwise everything else works just like a real trackpad with the default shortcuts. I even got the dictionary feature to work with 3-finger click. No tapping is enabled at all, just FYI, since tapping was behaving rather weirdly.
     
    Supposedly 4-finger and 5-finger pinch work, too, but I have them set to copy whatever 4-finger swipe down does (I'm using that for launchpad).
     
    Tracking speed is changed by the Trackpad prefpane setting, not the mouse prefpane settings. Most of the trackpad settings don't work, or don't do what you'd think they would--just about all of the touchpad configuration is done in the kext's main info.plist (keyboard config is in the keyboard kext's info.plist in the plugin folder).
     
    Credit EMlyDinEsH, especially for the awesome documentation of about 95% of the options. Highly recommend checking out the documentation at that link, e.g. to learn about the custom F13-F24 mapping.
     
    EDIT: Some more differences: PrtScr is a shortcut for CMD+Shift+4 (screenshot), and no longer disables the touchpad. The search on F9 seems to be a second mute button for some reason, and I'm not totally sure what F7's and F8's special keys do, if anything.
    ApplePS2SmartTouchPad.kext.zip
  22. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    ACPI tables would most likely be the same if the replacement board were exactly the same and on the same BIOS version as mine. If anything changed there then there's nothing I can do except put a warning that this setup will only work on specific motherboard revisions. That said, if you have to use the same BIOS file as the rest of us, you're probably still using the same tables. The only thing I can suggest is that maybe there's a kext that isn't playing nice with your system, but I can't really do too much more troubleshooting (no more time). A good place to start is looking at 
    log show --last "10m" or however many minutes  since your last shutdown and see if there's anything obvious in either the shutdown or boot sequence. Good luck!
     
     
    Will do. 
    I won't be trying to get Optimus switching to work, haha. Not tackling that one--for a single person like me that would basically be a small job or a very long hobby project. Trying to port the entirety of Linux's Bumblebee project might seem like one way to do it, but making an entirely new driver and sidestepping Apple's gmux altogether would probably be the better way to do it. Bumblebee still isn't 100% perfect.
     
    Ergo, it remains quite the undertaking no matter how you slice it (and too big for me for the forseeable future). The "state of the Optimus" is summed up quite nicely by this reddit thread. 
     
    TL;DR: if QuickSync on MacOS can't get the job done, dual-boot. Don't bother waiting for Optimus support!
  23. Like
    blazinsmokey got a reaction from KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Thanks for the help. Got HDMI audio working now, glad I understood this time you meant to go back to original hdmi audio kext.
    Went through your config and did the same injections for intelGFX. Now I'm back to HD 630 and "unspoofed".
     
    Really appreciate your patience!! All set for now I guess.
     
    My new files attached for other people if needed.
     
    config.zip
    Other.zip
  24. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    It's the same FakePCIID HDMI Audio kext from the very first post in this thread.
    You should also use the config I just posted, and follow the directions I posted (sorry I can't be more detailed atm).
     
    That you see KBL CRB means Kaby lake graphics are now native, so the next step is to properly configure things (which will cause the graphics to say HD 630 again, but it will be "unspoofed" ).
  25. Like
    blazinsmokey reacted to KNNSpeed in Dell XPS 15 9560: 4K Touch, 1TB SSD, 32GB RAM, 100% AdobeRGB​   
    Your understanding is correct, however it appears you may have "unspoofed" incorrectly.
    Instead of "unspoofing" it looks like you "reverse spoofed."
×