Frequently Asked Questions

####Frequently Asked Questions

• What do I need to do with my previous sound modifications?
  You must remove any of them except the DSDT edits in any form (be that done via your bootloader or by manually written SSDT files) and CodecCommander.kext if you use it. All the other changes including modified AppleHDA.kext, VoodooHDA.kext, HDAEnabler.kext, AppleHDADisabler.kext, realtekALC.kext, bootloader kext patches if any, etc. are to removed.

• How do I add the prerequired DSDT modifications and what are they?
  This may be specific to the bootloader you use, however, there are guides for that on the net. In brief you must be sure you have a HDEF section for analog audio, and a HDAU section(s) for HDMI audio. The first one must contain a layout-id.

• The provided codec modification does not work for me, what can I do?
  AppleALC was originally designed to be configured and built specifically for each user. However, a number of codecs were added by various people for their own needs. Consider these additions to be usage examples, because in no way they guarantee that the changes are meant to work on your configuration.

• Why does not AppleALC inject DSDT properties (e. g. layout-id, hda-gfx)?
  This kind of functionality is available in a flexible form in all major bootloaders via SSDT editing, plist configuration, etc. AppleALC is not meant to configure your hardware but only fix the incompatibilities in-between. Therefore no feature duplication is available.

• Why do I get a number of warnings when compiling AppleALC in Xcode?
  Ask Apple why Mac policy is still not considered KPI, and why the linkage issue is unfixed after a long while. These two can be safely ignored.

• Why do I have no sound in Recovery HD?
  There is a hotplug bug on certain codecs, which allows only (front panel) phones work after booting to Recovery. One could try CodecCommander.kext to fix this issue.