I'm going to try and make this readable - and hopefully add/update/change info as I get it, but no promises :)
Click the "[Return]" links to return to the Index.
- OSX Boot Issues
- Missing Bluetooth Controller Transport
- Enable Legacy Matching
- Prohibited Sign
- OsxAptioFix Errors
- Row Of Plus Signs
- Kernel Panics
- AppleIntelCPUPowerManagement
- BluetoothHostControllerUARTTransport
- Audio
- Skylake
- AppleALC
- HDMI Audio
- USB
- _OSI to XOSI
- Hardware Exceptions
- Asus Z170-A
- GA-X79-UP4
- Tools
- Mounting the EFI Partition
- Repairing Permissions and Rebuilding Kext Cache
This seems like a Bluetooth error - but it's actually just the last line before the GPU initialization starts. It usually means the GPU isn't initializing.
- Maxwell - 900 Series (also includes 745, 750, 750ti)
- Ensure you have NVIDIA Injection disabled in Clover
- If you have already installed the NVIDIA Web Drivers - boot with
nvda_drv=1 - If not - boot with
nv_disable=1 - Kepler - GTX 600 & 700 Series (excludes 745, 750, 750ti)
- Ensure you have NVIDIA Injection disabled in Clover
- Remove
nv_disable=1andnvda_drv=1from boot arguments if present - If you still can't get in - try using
nv_disable=1, installing Web Drivers, then usingnvda_drv=1 - Some of the Kepler cards work better with the Web Drivers
- Fermi
- Ensure you have NVIDIA Injection disabled in Clover
- I believe most of these work OOB - but may suffer from stuttering
- If yours stutters, try using
nv_disable=1, installing Web Drivers, then usingnvda_drv=1
- HD 4600 - Haswell
- Ensure Intel Injection is enabled in Clover
- Remove any ig-platform-id
- Set primary display output to IGPU in BIOS
- HD 530 - Skylake
- Ensure Intel Injection is enabled in Clover
- Set ig-platform-id to 0x19120000
- Set primary display output to IGPU in BIOS
This is something I've seen on some Skylake builds. It's related to USB ownership.
To fix it - enable FixOwnership in config.plist (you may also need to enable Inject):
<key>USB</key>
<dict>
<key>FixOwnership</key>
<true/>
<key>Inject</key>
<false/>
</dict>
Shows up usually when booting the USB drive - the text gets garbled, a cirlce with a slash through it shows up, and the line Still waiting for root device... can be seen at the end.
This usually means that the USB drive got "lost" as the OS is booting. The most commonly accepted solution is to try all USB ports on your board.
USB 2.0 typically work better (and even better still when combined with a USB 2.0 flash drive).
You may need to inject all your USB ports via RehabMan's USBInjectAll.kext, and add the following to your config.plist -> KextsToPatch:
<dict>
<key>Comment</key>
<string>change 15 port limit to 30 in AppleUSBXHCIPCI</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>
g72M/v//EA==
</data>
<key>Name</key>
<string>AppleUSBXHCIPCI</string>
<key>Replace</key>
<data>
g72M/v//Hw==
</data>
</dict>
Memory mapping errors are tricky - if you're on an X99 system, you may be out of luck, although I do believe there are some custom OsxAptioFix drivers out there - reports on their success are hit and miss.
For everyone else - this usually means that you need to swap OsxAptioFixDrv-64.efi for OsxAptioFix2Drv-64.efi (or vise versa) in your EFI partition at /EFI/CLOVER/drivers64UEFI/ (do not have both fixes in that folder - that's like Russian Roulette with memory mapping).
Usually attributed to the VBoxHfs-64.efi file in your EFI partition at /EFI/CLOVER/drivers64UEFI/. Replace that file with HFSPlus.efi (it does not have to be renamed) and you should have some better success.
This section will go over some of the common kernel panics and how to avoid them.
This KP is caused by either locked MSR attempted access or a CPU without supported C & P-States.
To fix it temporarily, you can use NullCPUPowerManagement.kext.
You can alternatively enabled AsusAICPUPM in Clover.
For Ivy Bridge and newer CPUs, you can use Pike R. Alpha's ssdtPRGen.sh script to generate an SSDT for your CPU. The resulting SSDT is named "ssdt.aml" and located at ~/Library/ssdtPRGEN/ - rename this file to "SSDT.aml" and place it in /Volumes/EFI/EFI/CLOVER/ACPI/patched/. You may also ened to drop the CpuPm and Cpu0Ist SSDT tables in your config.plist -> ACPI -> DropTables:
<key>DropTables</key>
<array>
<dict>
<key>Signature</key>
<string>SSDT</string>
<key>TableId</key>
<string>CpuPm</string>
</dict>
<dict>
<key>Signature</key>
<string>SSDT</string>
<key>TableId</key>
<string>Cpu0Ist</string>
</dict>
</array>
Also make sure to enable the following in your config.plist -> KernelAndKextPatches:
<key>KernelAndKextPatches</key>
<dict>
<key>AppleRTC</key>
<true/>
<key>AsusAICPUPM</key>
<true/>
<key>KernelPm</key>
<true/>
For Ivy Bridge CPUs (not necessary on Haswell, but doesn't hurt either way), you'll also need to add -xcpm to your boot arguments to force the use of the new power management method.
For Sandy Bridge and older, do not use Pike's script, and instead enable Generate CStates and PStates in config.plist -> ACPI -> SSDT:
<key>SSDT</key>
<dict>
<key>DropOem</key>
<false/>
<key>Generate</key>
<true/>
</dict>
This KP is seen on Skylake boards - and is related to the serial port. Disable the serial port in BIOS (Peripherals -> Super IO -> Serial Port; or similar) and you should be able to boot. Note: some boards have a serial port header (not a port on the back), and in those cases - you will still want to disable it.
If you have an Asus Z170-A board, you may also need the following in your config.plist -> ACPI -> DSDT -> Patches:
<key>ACPI</key>
<dict>
<key>DSDT</key>
<dict>
<key>Patches</key>
<array>
<dict>
<key>Comment</key>
<string>Z170-A UART Patch</string>
<key>Find</key>
<data>
QdAFAQ==
</data>
<key>Replace</key>
<data>
AQIDBA==
</data>
</dict>
To allow many Skylake boards (if not all of them) to work with some of the more elegant audio solutions (see AppleALC), you need to rename HDAS to HDEF in DSDT via the following edit to your config.plist -> ACPI -> DSDT -> Patches:
<dict>
<key>Comment</key>
<string>Rename HDAS to HDEF for Realtek Audio</string>
<key>Find</key>
<data>
SERBUw==
</data>
<key>Replace</key>
<data>
SERFRg==
</data>
</dict>
AppleALC is a kernel extension developed by Vit9696 that allows for dynamic patching of AppleHDA.kext in kext cache (non-destructive, works with SIP) and supports a large range of codecs.
It gets installed to your EFI partition (if using Clover) at /Volumes/EFI/EFI/CLOVER/kexts/Other/ (or the 10.xx folders - but I prefer Other). I did an audio-related writeup about it here. /u/TheRacerMaster wrote a tutorial for installation here.
Toleda is still the resident expert for HDMI audio - I don't have the capacity to figure out how he does it - but I'll link some of his repos here:
From his HDMI Audio AppleHDA [Guides]
- HD6000+/Desktop/BRIX/NUC
- HD4600+/Desktop/BRIX/NUC
- HD4000/Desktop/BRIX/NUC
- HD3000/Desktop
- AMD HDMI audio
- Nvidia HDMI audio
- ALC/HDEF audio
- Intel 100 Series (HD 515, 530, and 540 at the time of this writing)
His guides can be tough to figure out - but he knows his stuff. Read through them carefully (IIRC, the AMD and NVIDIA guides require using IORegistryExplorer to get the address of your card per this guide) and place the correct SSDT for your GPU in /Volumes/EFI/EFI/CLOVER/ACPI/patched/.
The following was quoted from this post:
If you notice that whenever you plug a USB3 device into a USB3 port and it shows up either in IOReg or About This Mac being loaded under EHCI (USB2) or "USB2.0 Hub", then this patch is for you. For a full explanation on how it works, refer to RehabMan's guide: "_OSI and Windows Version Checks"
To apply that patch, add the following to your config.plist -> ACPI -> DSDT -> Patches:
<dict>
<key>Comment</key>
<string>change _OSI to XOSI</string>
<key>Find</key>
<data>X09TSQ==</data>
<key>Replace</key>
<data>WE9TSQ==</data>
</dict>
For all Skylake boards, you'll want to make sure that you disable your serial port via BIOS - but this board still seems to have some serial port issues (referenced here as well). You'll want to make sure you have the following in your config.plist -> ACPI -> DSDT -> Patches:
<key>ACPI</key>
<dict>
<key>DSDT</key>
<dict>
<key>Patches</key>
<array>
<dict>
<key>Comment</key>
<string>Z170-A UART Patch</string>
<key>Find</key>
<data>
QdAFAQ==
</data>
<key>Replace</key>
<data>
AQIDBA==
</data>
</dict>
This board worked fine for me from 10.9.3-10.10.x - but with the rewrite of the way OSX handles USB implemented in El Capitan, it had some trouble. I would pretty consistently get a IOUSBFamily.kext kernel panic. I was finally able to get it to boot into the installer by using the following SSDT patch:
DefinitionBlock ("iASLwAigOV.aml", "SSDT", 1, "APPLE", "Fix_USB2", 0x00001000)
{
Name (_SB.PCI0.EUSB._STA, Zero)
Name (_SB.PCI0.USBE._STA, Zero)
}
To make it work, save the above code into a plain text file (called SSDT.dsl) - then hen compile it on MaciASL to get the SSDT.aml. After that - place it in your /Volumes/EFI/EFI/CLOVER/ACPI/patched/ folder.
The second required step was to disable all USB3 ports in BIOS (there were 2 USB3.0 controller IIRC). After doing this - I was able to boot. I haven't gone through and actually installed the OS as I'm a bit pressed for spare hard drives - but I don't know if there's a way to enable USB3.0 on this board in 10.11+.
To mount an EFI partition (in case you reboot, or eject one when you need it again), do the following in the Terminal:
diskutil list
Take note of the drive number that you want, and also the partition number of the EFI partition. It will look like diskDsP where D is the drive number and P is the partition number.
Then type the following in the Terminal to mount it:
diskutil mount diskDsP
Replacing D and P with the respective drive and partition numbers.
These are good maintenance tools - they ensure permissions are correct on the boot drive, and that the kext cache is not populated with old, or unused kexts. They are all entered into the Terminal.
For repairing permissions:
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /
For rebuilding kext cache:
sudo rm -r /System/Library/Caches/com.apple.kext.caches
sudo touch /System/Library/Extensions
sudo kextcache -update-volume /
Just make sure that you have the correct kexts in place - I've seen people mess up their builds because they swapped out correct kexts for incorrect ones, and were just coasting on the previous kext cache. When they rebuilt the kext cache, it pulled their feet out from under them and they had issues.