Document your code
Every project on GitHub comes with a version-controlled wiki to give your documentation the high level of care it deserves. It’s easy to create well-maintained, Markdown or rich text documentation alongside your code.
Sign up for free See pricing for teams and enterprisesInstallation and usage
How to use AppleALC
The only task you need to accomplish if your codec is supported is to load the kernel extension and see if it works. You can use your bootloader for that but remember to load AppleALC earlier than AppleHDA (see sudo kextstat output for more detail).
Note that Lilu must also be present for AppleALC to work.
Follow an easy-to-use guide to add your codec support if it is not here yet. Please share your successful results afterwards.
Note: It is necessary to set value layout-id in Devices-Properties or boot arguments.
HDEF device locations PciRoot, gfxutil may be used: gfxutil -f HDEF
Do not use renaming HDAS to HDEF, B0D3 to HDAU, etc.
Disable FixHDA, AddHDMI and UseIntelHDMI.
Set Devices → Audio → Inject = NO (Necessarily type string!)
How to control AppleALC
AppleALC accepts different boot arguments to control its behaviour:
-
alcid=layout— to set valuelayout-id; -
-alcoff— to disable itself; -
-alcdbg— to print the debugging information (if the extension was compiled in debug mode); -
-alcbeta- to enable AppleALC on unsupported systems (usually unreleased or old ones); -
-xor-swill also disable AppleALC. - All the Lilu boot arguments affect AppleALC.
How to extract the debug log
After booting with -alcdbg -liludbg run the following commands in Terminal and save the output.
10.12 and newer:
log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "AppleALC" OR eventMessage CONTAINS "Lilu")' --style syslog --source
10.11 and older:
cat /var/log/system.log | egrep '(AppleALC|Lilu)'