Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


darkvoid last won the day on June 26 2016

darkvoid had the most liked content!

About darkvoid

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. darkvoid

    FileVault 2

    Yes, the same Clover installation can boot an unencrypted macOS install just fine.
  2. darkvoid

    NVMe native support in 10.13 :)

    Let me rephrase that. Is your main OS disk actually formatted in APFS? Having APFS.efi loading through Clover is independent of that. Users with both Hackintosh as well as real mac's are reporting slow boot times if 512-byte sector SSD's are used with APFS formatting. Samsung SSD's only support 512-byte sectors, some of the other SSD's can be low-level formatted in 4096-byte sectors. The issue of slow boot appears when using: 512 byte sector formatted SSD TRIM enabled Boot drive formatted with APFS Booting can then take well over a minute to complete.
  3. darkvoid

    NVMe native support in 10.13 :)

    And you are using APFS?
  4. darkvoid

    NVMe native support in 10.13 :)

    Does the upgrade to 10.13.2 resolve the speed issue?
  5. darkvoid

    NVMe native support in 10.13 :)

    It would seem that the issue is specifically with 512 byte sector SSDs. Sadly the Samsung Polaris Controller used on the PM96x and Pro96x series only supports 512 byte sector size, 4096 byte sectors are not supported. (Verified with smartctl and nvme format -l 1 /dev/nvme0 on linux) There are a number of complaints of slow boot with Samsing SSD's on Apple's forums, so hopefully it gets resolved with macOs High Sierra 10.13.2.
  6. darkvoid

    NVMe native support in 10.13 :)

    Has anyone thoroughly tested a Samsung PM961, EVO 960 or EVO 960 Pro (all Samsung Polaris controller SSD) with High Sierra 10.13.0 / 10.13.1? Specifically interested in potential problems with APFS, slow boot, trackpad preferences etc.
  7. darkvoid

    Working WiFi in Sierra?

    Its for the Broadcom plugin kext located at: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext You haven't given any details about your third party Airport PCI-E card though, so unsure if this patch will do anything for you.
  8. darkvoid

    Working WiFi in Sierra?

    I wouldn't spring for another card yet. The WiFi drivers in Sierra are still changing, so its possible your card will start working in the future. Even though I posted a patch for the BCM94352Z WiFi card in Sierra, I am hopeful that the patch will not be needed in the final release. Either that, or your PCI-E card could benefit from the same patch.
  9. darkvoid

    [FIX] macOS Sierra DP1 BCM94532Z WiFi

    @Axam, I specifically made the patch for the card you are using. The patch must not be applied correctly in your case. Please double-check that all is in place correctly.
  10. darkvoid

    [FIX] macOS Sierra DP1 BCM94532Z WiFi

    @macq, Its too early to say which patches previously used are still relevant. We are just at DP1, once macOS Sierra reaches release it would be good to consolidate all required patches. @FredWst, I haven't tried booting this in recovery mode. Will see if there is anything to learn from the recovery mode boot scenario. Also the BMC94352Z working in recovery mode might indicate that future release of the developer preview could still support the device properly without additional patches.
  11. darkvoid

    [pre-releases] macOS Sierra

    @notnice, @TheRacerMaster, @mnfesq, Saw your messages with regards to the Broadcom BCM9432Z no longer working in macOS Sierra DP1. I have made available a patch in the post-installation forum: http://www.insanelymac.com/forum/topic/312759-fix-macos-sierra-dp1-bcm94532z-wifi/
  12. On macOS Sierra DP1, when using a BMC94532Z NGFF WiFi card, AirportBrcm4360.kext no longer successfully loads. This problem is caused by the driver not being able to initialize the fvco (frequency voltage controlled oscillator). Apply the following patch in Clover to enable WiFi using the BCM94352Z: Kext: AirPortBrcm4360 Find: 81F952AA00007529 Replace: 81F952AA00006690 Through Clover config.plist: <dict> <key>Comment</key> <string>AirPortBrcm4360 - fcvo</string> <key>Disabled</key> <false/> <key>Find</key> <data>gflSqgAAdSk=</data> <key>Name</key> <string>AirPortBrcm4360</string> <key>Replace</key> <data>gflSqgAAZpA=</data> </dict>
  13. On macOS Sierra DP1, a part of the IOKit functionality dealing with graphics has moved to a new framework kext: CoreDisplay.kext. This affects the existing IOKit maximum pixel clock patch used for previous OS X versions. The new patch to be applied for macOS Sierra DP1 is: sudo perl -i.bak -pe 's|\xB8\x01\x00\x00\x00\xF6\xC1\x01\x0F\x85|\x33\xC0\x90\x90\x90\x90\x90\x90\x90\xE9|sg' /System/Library/Frameworks/CoreDisplay.framework/Versions/Current/CoreDisplay sudo codesign -f -s - /System/Library/Frameworks/CoreDisplay.framework/Versions/Current/CoreDisplay
  14. darkvoid

    Dell XPS 13 9343 Sierra Installation

    @dudenessspa, Ok confirmed this from my side. The CoreDisplay.kext patch correctly re-enables 4K display resolutions (unlocks maximum pixel clock) in macOS Sierra DP1. For those coming across this, the final proper patch is: sudo perl -i.bak -pe 's|\xB8\x01\x00\x00\x00\xF6\xC1\x01\x0F\x85|\x33\xC0\x90\x90\x90\x90\x90\x90\x90\xE9|sg' /System/Library/Frameworks/CoreDisplay.framework/Versions/Current/CoreDisplay sudo codesign -f -s - /System/Library/Frameworks/CoreDisplay.framework/Versions/Current/CoreDisplay
  15. darkvoid

    Dell XPS 13 9343 Sierra Installation

    @dudenessspa, So you are confirming this works for enabling 4K display resolutions for you on the 9343? What frame-buffer and device ID are you using?