Jump to content


  • Content Count

  • Joined

  • Last visited

About sailor25462

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

2,556 profile views
  1. Version 1.0.0


    RTL8811AU USB WiFi ac dongle drivers packed, including 10.4 to 10.12. Confirmed to work under Mojave 10.14.5.
  2. sailor25462

    strange issue

    I have the same issue with z68, i7-3770 / HD4000 / NVIDIA Titan (natively supported). Just reboots after.... a while... Not a solution for you, but it seems not to limited to your board/setup, only. Gesendet von iPad mit Tapatalk
  3. sailor25462

    Postinstall advice for 10.14.4 on Ga-Z68AP-D3

    Today, I managed once again to split my fusion drive for unknown reason. So, over night I’ll need to play back my 900GB backup, before I can go back to more „adventurous“ attempts. [emoji16] When booting from usb installer, using iGFX and -v, I believe to have seen the last lines of unknown CPU and unknown PCH (?)... Not sure if this makes sense, though. Gesendet von iPhone mit Tapatalk
  4. EFI folder contains Hackintosher.txt, showing "Installer version: v2.4k r4586 EFI bootloader". If that is the current clover release installed, the first thing to do would be to update to the most current one (today r4920). Just as a starter....
  5. sailor25462

    Postinstall advice for 10.14.4 on Ga-Z68AP-D3

    Tried to install, but appears to work not. Even tried to extract with Pacifist, but the kext will not even copy. Strange... Can you post the kext? edit: sorry... something was wrong with my system. worked after a restart. Well, to me it doesn't seem to do the trick. The kext installs and it will recognize a USB3 device (64GB Intenso stick in this case). Interestingly, system report under USB section will not give the usual information on the inserted stick anymore with this kext. Putting in a USB2 device will not work at all, same as using stock drivers. No advantage using the NEC driver.
  6. sailor25462

    Postinstall advice for 10.14.4 on Ga-Z68AP-D3

    You need to update your clover to the most present one (today it's r4920). To work with an outdated clover versions is not helpful at all. As far as proper power management is concerned, you will have noticed that your CPU does only either full speed or idle, but nothing "in between". The SSDT automator script is a nice piece of cake and will create an ssd.aml file for you, which you can place in your CLOVER/ACPI/patched folder. You must also de-select the generation of the p- and c-states in the config: <key>ACPI</key> <dict> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>CStates</key> <false/> <key>PStates</key> <false/> </dict> </dict> </dict> I do have the same board as you do, but with the i7-3770, not the unlocked "k". So, I'm naturally excited to follow your thread here, although I'm using an Nvidia TitanX (Kepler), which is natively supported. So can't prove anything on AMD GPU's. In any case, what I can confirm is that headless activation of the iGPU (which I have done, too) does definitely make the boot slower. This is to be expected and a small price you need to pay for airplay mirroring support. What I see from your screen shot is an error report regarding iTunes playback. I had the same issue after updating to 10.14.4 with an "outdated" clover version. Movies would just result in a black screen and not play all. After I updated clover to 4920, everything works again! Now for the USB3 support: This is exciting for me, because I do use stock drivers only, plus USBInjectAll.kext. Before using this kext, only one USB2 port from the front panel worked. Now all ports work fine. USB3 ports work, too, but handoff for USB2 devices in the USB3 port does not seems to work at all. This is not a big issue for me now, but would be the ultimate cherry on the pie to get this running as well. Therefore, I should be trying your NEC kext and see what it does for me. Will report back! <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP</key> <true/> <key>FixDarwin</key> <true/> <key>FixDisplay</key> <false/> <key>FixS3D</key> <true/> <key>FixSBUS</key> <true/> <key>FixUSB</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> <key>ReuseFFFF</key> <false/> <key>SlpSmiAtWake</key> <true/> </dict> <key>HaltEnabler</key> <true/> <key>SSDT</key> <dict> <key>DropOem</key> <true/> <key>EnableC6</key> <true/> <key>Generate</key> <dict> <key>CStates</key> <false/> <key>PStates</key> <false/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>darkwake=8 kext-dev-mode=1</string> <key>Debug</key> <false/> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Legacy</key> <string>PBR</string> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <false/> </dict> <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>12</integer> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IMEI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> <key>ForceHPET</key> <false/> <key>USB</key> <dict> <key>AddClockID</key> <false/> <key>FixOwnership</key> <false/> <key>Inject</key> <false/> <key>NameEH00</key> <false/> </dict> </dict> <key>GUI</key> <dict> <key>Hide</key> <array> <string>\EFI\BOOT\BOOTX64.EFI</string> </array> <key>Language</key> <string>de:0</string> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <false/> <key>Linux</key> <false/> <key>Tool</key> <false/> </dict> <key>ScreenResolution</key> <string>1680x1050</string> <key>Theme</key> <string>bootcamp</string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>NvidiaGeneric</key> <false/> <key>NvidiaNoEFI</key> <false/> <key>NvidiaSingle</key> <false/> <key>ig-platform-id</key> <string>01620007</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleIntelCPUPM</key> <false/> <key>AppleRTC</key> <true/> <key>Debug</key> <false/> <key>ForceKextsToLoad</key> <array> <string>RealtekRTL8111</string> <string>BrcmFirmwareRepo</string> <string>BrcmPatchRAM2</string> <string>Lilu</string> <string>AppleALC</string> </array> <key>KernelCpu</key> <false/> <key>KernelLapic</key> <false/> <key>KernelPm</key> <false/> <key>KernelXCPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>External icons patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> <dict> <key>Comment</key> <string>USB Port Limit Patch 1</string> <key>Disabled</key> <false/> <key>Find</key> <data> g/sPD4cLBAAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.4</string> <key>Name</key> <string>com.apple.iokit.IOUSBHostFamily</string> <key>Replace</key> <data> g/s/D4cLBAAA </data> </dict> <dict> <key>Comment</key> <string>USB Port Limit Patch 2</string> <key>Disabled</key> <false/> <key>Find</key> <data> QYP/Dw+DlAQAAA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.4</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> QYP/Pw+DlAQAAA== </data> </dict> <dict> <key>Comment</key> <string>USB Port Limit Patch 3</string> <key>Disabled</key> <false/> <key>Find</key> <data> g+MP0+NBCd8= </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.4</string> <key>Name</key> <string>com.apple.iokit.IOUSBHostFamily</string> <key>Replace</key> <data> g+M/0+NBCd8= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>#########################</string> <key>ROM</key> <data> UOVJ5q8a </data> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>09/11/2015</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>IM131.88Z.010A.B09.1509111558</string> <key>Board-ID</key> <string>Mac-00BE6ED71E35EB86</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardSerialNumber</key> <string>########################</string> <key>BoardType</key> <integer>10</integer> <key>ChassisAssetTag</key> <string>iMac-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>13</string> <key>Family</key> <string>iMac</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Memory</key> <dict> <key>Channels</key> <integer>0</integer> </dict> <key>ProductName</key> <string>iMac13,1</string> <key>SerialNumber</key> <string>######################</string> <key>Trust</key> <false/> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>CustomUUID</key> <string>#####################################</string> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> So far, I'm not using any DSDT.aml file, only the patches for power management and headless IGPU. I've also tried to minimize the number of "activated" teaches over the time. No sure if I'm missing some of them now (at least I did not recognize any negative consequences so far) or if my set is making sense in all details. But it works for me to 99,9%, so I guess I did not mess it all completely. Of course, I'm always open for improvement suggestions!
  7. sailor25462

    APFS fusion drive crashed / split

    Thanks xtraa for your feedback and glad to see someone replying who's living quite near to my place, too Indeed, I have come across this and can confirm that it creates a new fusion drive (automatically), but does not merge back in any way that it could preserve any "old" data. The bottom line is: I had to use my time machine backup after I did the resetFusion command with diskutil, it does delete all content on both hdd's. By the way: resetFusion does work only when there are exact 2 drives, i.e. one ssd and one spinning drive, present. So you need to deactivate other hdd's first in BIOS or resetFusion will quit. It also appears that the fusion drive split happened just again yesterday. I'm not so keen on testing this any further for obvious reasons, but I think it breaks when the boot process (last stage before login) hangs for some reason. In this particular case, I had changed my CPU and graphics settings and switched from external GPU to internal HD4000 (for testing). Boot froze at let's say 90% (no -v) and I had to make a cold restart after all. With this, fusion drive was gone (again). Lesson learned To me it seems that the fusion drive is quite vulnerable when it comes to cold restarts during boot process. Better to avoid this during testing conditions and use a single drive installation instead.
  8. Folks, I‘m afraid I need your support, please. I had successfully finished a clean install of Mojave with fusion drive and after this I retrieved my personal data back from my time machine backup. So far, so good. Today, however, within just some usual work, my machine completly freezed. Something which I had never really had in the past. Pushed reset button, but now - holy f... - my fusion drives appears split as two separate apfs drives. Since I haven‘t made a new time machine backup yet, I can still easily go back to high Sierra, but actually this is a scary incident and I‘m wondering if anyone else did have such a crash before, too? Is there any non-destructive way to get the fusion drive back „fused“ or do I have to re-create it and make a new clean install? (Which would just costs me another 6 hours or so, since my backup is nearly 1 TB in size.... Any advise is highly appreciated!
  9. sailor25462

    Updating BIOS to UEFI on z68ap-d3 (rev. 1)

    By the way, here is the original source I found my files in: http://forum.gigabyte.ru/viewtopic.php?t=47933 Use google translate to read in English.
  10. sailor25462

    Updating BIOS to UEFI on z68ap-d3 (rev. 1)

    Frankly speaking, I do not know what to say. I have not come across such problems. Don't really dare to ask, but are you sure you have a rev.1 board? Except from that, I've no clue what to do. As I said, I have sold the rig a while ago, so I have no chance to test anything myself. sorry.
  11. sailor25462

    Updating BIOS to UEFI on z68ap-d3 (rev. 1)

    It’s long time ago, I barely remember. But I don’t think I ever used any extra tools.
  12. sailor25462

    Updating BIOS to UEFI on z68ap-d3 (rev. 1)

    Wasn’t there a built-in flash update Option in the bios of the mobo?
  13. sailor25462

    Updating BIOS to UEFI on z68ap-d3 (rev. 1)

    Frankly speaking I don’t know. It’s because I sold the rack a while ago. I would believe i updated from F8, but it’s not guaranteed. Also you should be aware that many seem to have issues with this uefi (fan), so you should be aware of the risk it could also happen to you. I don’t want to encourage you, but neither want to say: don’t do it. All i can say is that it worked for me, as shown on the screen captures. I have no clue why it worked for me and for others not. Could be language settings or something we don’t even dream of. So from my side: if you feel safe and are ready to go through an unsupported downgrade path in case it doesn’t work, then fine. Its obviously not for the faint at heart.... Oh, maybe one more advice: make sure you really “flush” all settings to default after the upgrade (should you decide to do it) I would believe that removing power and the backup battery from the board should ensure you start from blank.
  14. I have had the same, actually on two machines, but already earlier, before this latest 13.4 update. On one of the machines, all of a sudden, we couldn't open Photos.app anymore, on the second it involved mail.app up to FaceTime and iMessage. I was looking at the permissions within the user folder, but couldn't identify anything specific. However, what I noticed was that some sym-links seemed to go to nowhere, their corresponding counter part was simply missing. Maybe this is something you may want to check also, if this is also happening in your case? I ended up moving everything into a new profile, but would would be interested to solve (or at least understand) this after all.