Contribute
Register

No Audio Devices - AppleHDA Realtek Audio

Hello
I have audio problem since update to Catalina 10.15.1
No sound after update, been using AppleALC on Library/Extensions before and no problems but now I don't get correct input and outputs
My board is ASUS z170a with rx 580 graphics and intel 6700k
I use integrated audio from Asus Z170a
Working on windows so its not connection issue

Here it is my logs and files

looking for some help, thank you
 

Attachments

  • Archive.zip
    1.8 MB · Views: 173
If this is of any help:

Code:
iMac23:~ adrianmihai$ log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "AppleALC" OR eventMessage CONTAINS "Lilu")' --style syslog --source


Filtering the log data using "process == "kernel" AND (composedMessage CONTAINS "AppleALC" OR composedMessage CONTAINS "Lilu")"


Skipping info and debug messages, pass --info and/or --debug to include.


Timestamp                       (process)[PID]   


2019-10-16 12:11:34.659361+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 12:11:34.659364+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 12:11:38.839440+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-16 13:50:46.657167+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 13:50:46.657171+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 13:50:50.829764+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-16 14:07:06.656306+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 14:07:06.656309+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 14:07:10.919892+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-16 14:25:50.657575+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 14:25:50.657578+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 14:25:54.901793+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-16 14:42:29.656669+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 14:42:29.656672+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 14:42:33.851745+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-16 14:45:28.659155+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-16 14:45:28.659158+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-16 14:45:32.809745+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-17 12:40:04.653147+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-17 12:40:04.653150+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-17 12:40:08.925552+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-17 13:12:33.861335+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-17 13:12:33.863221+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-17 13:12:40.098295+0300  localhost kernel[0]: (Lilu) AppleALC:     alc @ failed to obtain device info for analog controller (1)


2019-10-17 13:50:10.863590+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-17 13:50:10.865476+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 10:32:29.661857+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 10:32:29.661860+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 10:58:18.657125+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 10:58:18.657128+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:05:05.863130+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:05:05.865016+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:12:38.864453+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:12:38.866341+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:16:49.861953+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:16:49.863841+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:21:15.863745+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:21:15.865631+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:25:57.860579+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:25:57.862467+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:35:35.862441+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:35:35.864329+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:43:14.866431+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:43:14.868319+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 11:54:05.858839+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 11:54:05.860725+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 12:08:19.863089+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 12:08:19.864975+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 12:10:46.662080+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 12:10:46.662083+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 12:25:26.657118+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 12:25:26.657121+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-18 13:35:01.657375+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-18 13:35:01.657379+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-21 10:28:57.659222+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-21 10:28:57.659225+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-21 11:02:54.658368+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-21 11:02:54.658371+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-21 11:16:17.656398+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-21 11:16:17.656401+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-21 11:28:14.659042+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-21 11:28:14.659046+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-21 11:33:35.659823+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-21 11:33:35.659826+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 09:24:15.654594+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 09:24:15.654597+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:19:37.660703+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:19:37.660706+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:31:06.659425+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:31:06.659429+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:35:04.658588+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:35:04.658592+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:37:32.655089+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:37:32.655092+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:40:33.658176+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:40:33.658179+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)


2019-10-22 11:58:48.654699+0300  localhost kernel[0]: calling mpo_policy_init for Lilu


2019-10-22 11:58:48.654703+0300  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.8 (Lilu)
 
Same here. In my rig it just fails to boot until I remove the AppleALC kext from /Library/Extensions. Tried to install the 1.4.1 which was working before but with the same results. Machine just crashes with the stop sign a second after clover.
Lucky for me I have a Logitech set of speakers with BT and the Apple BT/Wifi adapter which connects to it and sound is back.
I would like to get the Realtek sound working again on my Z390 UD (ALC888). VodooHDA doesn't work, gives me 5 entries for HDMI Audio but I am using DP so no sound.

After reading a bit about it, it looks like AppleALC is not being supported by Clover? Strange as it was working fine before. I dont want to try the opencore boot loader just yet. I prefer the tried and true methods.

Looks like OpenCore is the future though?

Any tips?
 
Ok, went this route also (recommended method, using Hackintool - latest):


The bellow example is for layout 11, I have tested all of them, looked in the ALC887 resource info.plist also, even though Hackintool has all of the layouts.

1. confirmed that in ioreg I can find HDEF (also every single change that the id is changing accordingly), also looked in my DSDT and found HDEF so no need to rename anything in ACPI.
Screenshot 2019-11-12 at 13.36.52.pngScreenshot 2019-11-12 at 13.42.41.png
2. Generated a patch using Hackintool for every layout:
Screenshot 2019-11-12 at 13.35.59.png
3. Converted the layout from Base64 to HEX:
Screenshot 2019-11-12 at 13.36.06.png
4. Add layout to Clover ->Devices->Properties
Screenshot 2019-11-12 at 13.36.20.png
5. Restart the computer after each layout change and verified in Sound Preferences every Output

I have sound in Headphones on most of them, some of them have separate Headphones and Built-in Speaker profiles, some have more Line-outs....
BUT NOT A SINGLE ONE HAS A VALID LAYOUT THAT I CAN USE THE BUILT-IN SPEAKERS of my Asus ET2323 All in one...

6. Looking at this, should I check the different layouts for the ALC888? (EDIT: none are valid)
Screenshot 2019-11-12 at 13.54.45.png

Is there something else that I can do or should I just give up?

EDIT: I made a codec dump, if someone can look through it... card0/codec#0 and card1/codec#0
 

Attachments

  • card0_codec0.txt
    3 KB · Views: 115
  • card1_codec0.txt
    13.5 KB · Views: 122
Last edited:
I'm running High Sierra for 1.5 years. everything worked, but today audio stopped working. didn't update anything, didn't touch my efi partition for over a year. tried reinstalling audio + 100 support with multibeast for HS. nothing. i'm only showing "Apple TV" in my output. USB audio works as well. when booted into windows 10, audio works.

My best guess is maybe an expired certificate somewhere invalidated the audio.

EDIT:
followed this: https://www.tonymacx86.com/threads/applehda-realtek-audio-guide.234732/#post-1606764
installed Lilu method. now everything is working.
 

Attachments

  • attachments.zip
    2.7 MB · Views: 106
Last edited:
Hi !
I had sound on my build, plugged in optical port. Then suddenly, I have only audio to HDMI. I didn’t even restarted, but I’m not sure it can’t have rebooted after a crash, even if it doesn’t looked like it. Seems a bit like previous message, but reinstalling new Lilu & AppleALC didn't solved anything.

OS 10.14.6, MoBo GA-Z170N-Wifi, with i3 4690 processor, built in CG intel HD 530.

I have AppleALC and Lilu installed in EFI/Cover/kexts/other

here are the files, thanks a lot, this is my media center build, so no sound is a bit of a problem :)

[edit] As I've seen in Catalina related topic (even if I'm on Mojave), reinstalling the kexts in L/E instead of Clover solved it ...
 

Attachments

  • el charlot sound problem.zip
    2.4 MB · Views: 128
Last edited:
Having problems. Any help is appreciated.
1) I have no audio. There are no native audio devices, other than airplay and LG 4K monitor HDMI listed in output/input devices. I tried FAKEPCIID method and HDAS to HDEF patches with no luck. First terminal code (ioreg) rendered no output, so attached outputs from codes 2 & 3.
2)10.15.1/ASUS Z370-E/2201/i7 8700K/Radon Rx Vega 64
3) 2 FAKEPCIID kexts, kernel patch (HDAS to HDEF)
 

Attachments

  • Files.zip
    2.5 MB · Views: 135
I cannot get my external speakers (connected via headphone jack) to show up.
I upgraded from 10.13.6 to 10.15.2 after switching from my NVidia 980 Ti to Vega 64. Before the upgrade/graphics card switch, audio worked fine.
I followed the acidanthera/AppleALC guide to get it working again.

I have a Rampage V Extreme (X99) Motherboard with a 5820k and Vega 64.
When I run kextstat | grep 'Lilu\|AppleALC\|AppleHDA', it looks like AppleHDA.kext did not start:
Bash:
> kextstat | grep 'Lilu\|AppleALC\|AppleHDA'
   25    1 0xffffff7f810f4000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (283.15) F266EB6A-29C1-369A-9391-28536E347750 <24 23 22 13 8 7 6 5 3 1>
   28    2 0xffffff7f8186c000 0x23000    0x23000    as.vit9696.Lilu (1.4.0) D90C0A74-6E61-353E-8D57-96C781824E52 <8 6 5 3 2 1>
   30    0 0xffffff7f81b17000 0x125000   0x125000   as.vit9696.AppleALC (1.4.4) 73649D93-8D83-30C0-A5C2-78DCBE7ABCC1 <28 13 8 6 5 3 2 1>

I tried enabling/disabling all the DSDT patches in clover/Acpi and also tried removing all my SSDT*.aml. I was not notice any difference.
I use the system AppleHDA.kext and the renaming from ALZA to HDEF seems to work (as I can find HDEF in IOReg).

EDIT: I removed EAPDFix.kext. Now it works!
[deleted attachment]
 
Last edited:
Problem Reporting

Greetings everyone. I'm here asking for help:
  1. I’m unable to hear anything. Audio ports aren’t recognized, but soundflower is.
  2. My build:
    • Running macOS Catalina (10.15.3). Previously running Mojave and High Sierra, pretty much smoothly.
    • Asus TUF Z370-PLUS GAMING
    • UEFI BIOS version 0430 x64; firmware version: 11.8.50.3399
    • Intel Core i5 8400, 2.8 GHz
    • Intel UHD Graphics 630 1536 MB
  3. I followed Toleda’s AppleHDA Realtek Audio guide.
  4. All files attached as the guide mentions.
 

Attachments

  • Requested Files.zip
    2.5 MB · Views: 129
Problem Reporting

Greetings everyone. I'm here asking for help:
  1. I’m unable to hear anything. Audio ports aren’t recognized, but soundflower is.
  2. My build:
    • Running macOS Catalina (10.15.3). Previously running Mojave and High Sierra, pretty much smoothly.
    • Asus TUF Z370-PLUS GAMING
    • UEFI BIOS version 0430 x64; firmware version: 11.8.50.3399
    • Intel Core i5 8400, 2.8 GHz
    • Intel UHD Graphics 630 1536 MB
  3. I followed Toleda’s AppleHDA Realtek Audio guide.
  4. All files attached as the guide mentions.
According to the IORegistryExplorer it looks like AppleALC is working.

According to the documentation of AppleALC, there are multiple things that should be changed in your config.plist, but I tried on my system and those things doesn't work for me. (this includes getting rid of the rename HDAS to HDEF and also setting the audio inject in the properties box below instead of the usual drop down menu in clover configurator).

What got my system sound working at this point was to test different layout IDs. I have ALC892, and for me 18 was the only one working properly. This is different for different systems, but having the wrong LayoutID could result in no audio devices detected.

You can find all the layoutIDs that match your system at this link:

find your sound system (ALC number) and then find a layout ID matching your motherboard or one that's close. Then try and see what happens. (reboot after each try)

Now, Toleda is a better source than me for help but I thought this could help you a bit faster. :)
 
Back
Top