Jump to content
toleda

Mavericks Realtek ALC AppleHDA Audio

470 posts in this topic

Recommended Posts

Move Desktop/audio_ALC889-master file back to Downloads. Delete Desktop/audio_ALC889. Double click audio_alc889-90_patch.command from Downloads/audio_ALC889-master.

 

Hello toleda

all ok thanks

 

@Fabio1971

Try this Kext:

Hello mirone

all ok thanks

 

Fabio

Share this post


Link to post
Share on other sites
Advertisement

Hello, i'm not able to get my ALC1150 working as intended.

 

I have a front panel with Headphones, Mic-in, Line-In jack's.

 

But they do not work, i tried to use all Out Line in the Audio manager.

 

I don't really care at the line-in or mic, but i need headphones to work.

 

The jack's on the motherboard are working, but i also need the output at the front panel.

 

 

My Motherboard is AsRock H87 Fatal1ty Performance, and i have a fresh install of Mountain Lion 10.8.5 and i don't use a dsdt.

 

EDIT: I just saw that i posted in the Mavericks thread, sorry for that, but anyway i used all istructions for Mountain Lion.

 

I just did install HDAEnabler1.kext and then i used your command script to patch AppleHDA.kext

All worked fine since at least i have the audio on the motherboard jack's.

 

Then i tried with HDAEnabler2.kext, but nothing changed.

 

I don't know if there are other steps to enable them, or if i did something wrong.

 

I got some difficulties to follow your instructions, and i am not an hackintosh expert.

 

Can you assist me to get it working?

 

Thank you very much and sorry if my english is not perfect, i'm italian.

Share this post


Link to post
Share on other sites

The jack's on the motherboard are working, but i also need the output at the front panel.

You have a front panel problem.  If System Preferences/Sound/Output/Internal Speakers does not change to Headphones when plugged into the front panel, OS X does not see the front panel electrically.  OS X only supports HD Audio, no AC 97 support.  Verify correct font panel connector is plugged into the correct port on the motherboard.

Share this post


Link to post
Share on other sites

You have a front panel problem.  If System Preferences/Sound/Output/Internal Speakers does not change to Headphones when plugged into the front panel, OS X does not see the front panel electrically.  OS X only supports HD Audio, no AC 97 support.  Verify correct font panel connector is plugged into the correct port on the motherboard.

 

 

Hi, thanks for your reply.

 

It is connected correctly, because on Windows 7 is working. Also it was working in Snow Leopard using generic Voodoo before installed ML (the sound was distorted but it was working).

 

On the Motherboard i only have one Port for the audio panel and it is HD Audio.

But i don't know if the panel matter, maybe it is not compatible with HD Audio and it is only Ac'97?

 

In red is where is connected to:

 

 

EDIT 1: I found out that my front panel is AC 97 and not HD Audio, so it is incompatible.

 

LAST EDIT: I got it Working! I've manually patched the Platforms.xml  to manually select between Headphones and Internal Speaker and the front panel is working.

Ill do the same for Mic, and hope it will work.

 

Thank you for your help and your work!

 

 

 

Share this post


Link to post
Share on other sites

HP dc7700. 

Had perfect sound alc262 . updated to 10.9.1 now nothing.

no audio listed in system report

 help needed . reloaded > kext, codec > nothing

Share this post


Link to post
Share on other sites

ALC 262 sound working now . re-installed hda injector kext from extensions with Cameleonlist.

didn't work with kext utility.

thanks toleda

All is well !!!

Share this post


Link to post
Share on other sites

v1.1 - 12/22/13 - Mavericks 10.9.1 AppleHDA Patches available, see Post #1

hi Toleda,

 

do you see a way for us AMD users to get the internal sound card ALC8xx to run  or is this just a dream of mine or some such made ​​possible to implement in the near future?

 

Share this post


Link to post
Share on other sites

do you see a way for us AMD users to get the internal sound card ALC8xx to run  

I have no knowledge of AMD audio.  OS X requires Intel High Definition Audio spec compliance and checks for valid device_ids.

Share this post


Link to post
Share on other sites

hello toleda. this is great guide. i've followed everything in the op (and the github). but no sound coming from my speaker (nor my headphone port). sound comes from 1st line out and 2nd line out though.

 

here my hackintosh's details:

1. Maverick 10.9.1/HM55 (Acer 4740)/InsydeH20 v1.10/i3 330M/Intel HD 1st gen (i dont use the hdmi, so dont really care bout it)

2. dsdt patch (layout-id 2, (no sound whatsoever in layout-id 1 or 3))/AppleHDA Mavericks 10.9.1 patched using 888_v100202 patch

3-7, http://www78.zippyshare.com/v/13506264/file.html

 

the sound from applehda is far better than from voodoohda (it even sound nicer than in win8.1 using foobar2000+wasapi), it will be nice if the sound coming from the internal speaker and the headphone port. thanks

Share this post


Link to post
Share on other sites

hello toleda. this is great guide. i've followed everything in the op (and the github). but no sound coming from my speaker (nor my headphone port). sound comes from 1st line out and 2nd line out though.

Audio is working, however, your laptop uses different pin assignments from desktops.  Attach a codec dump to see which pins are assigned to Internal speaker and microphone.

Share this post


Link to post
Share on other sites

codec_dump.txt

 

i've changed the pathmap in platforms.xml, internal mic is working. but no sound from internal speaker (the path is correct according to codec_dump_dec.txt.svg), nor the headphone (ive changed this too). tried change the pinconfig in the plist with the modified verbs.. no sound :D im really confuse.

 

it might be bothering, but thanks for your help. i appreciate it (and the guide too)

Share this post


Link to post
Share on other sites

I have no knowledge of AMD audio.  OS X requires Intel High Definition Audio spec compliance and checks for valid device_ids.

 

hi toledo, thanks carlo_67, we have new drivers get without boot npci=0x.....

but sound with AppleHDA without functional. I hope you can help me

I add here a link as I have created my systeminfo imaging

Please can you look at the data to you, perhaps you can create something. should you require any information to be famous, then please contact me.

If you succeed, then the user would be a huge success for all amd

 

here is the new drivers package for mavericks 10.9.2

Edited by spakk

Share this post


Link to post
Share on other sites

we have new drivers get without boot npci=0x.....

but sound with AppleHDA without functional. 

Doesn't do anything for audio.  Attach an IOReg.

i've changed the pathmap in platforms.xml, internal mic is working. but no sound from internal speaker (the path is correct according to codec_dump_dec.txt.svg), nor the headphone (ive changed this too). tried change the pinconfig in the plist with the modified verbs.. no sound )

Out of town, attach codec_dump_dec.txt.svg  and verbit.txt.

Share this post


Link to post
Share on other sites

Doesn't do anything for audio.  Attach an IOReg.

Hi toleda,
 
with VoodooHDA sound output is OK, but with AppleHDA no sound output but  AppleHDAController is active
 
you can see the differences based good on the two visually results

 

 

with VoodooHDA 2.8.4:
#63 icon_share.png

 

and with AppleHDA:

#65 icon_share.png

Ioreg_txt.zip

AMD_IMac14,2_ioreg.zip

Edited by spakk

Share this post


Link to post
Share on other sites

 

Hi toleda,
 
with VoodooHDA sound output is OK, but with AppleHDA no sound output but  AppleHDAController is active
 
you can see the differences based good on the two visually results

 

 

with VoodooHDA 2.8.4:
#63 icon_share.png

 

and with AppleHDA:

#65 icon_share.png

 

 

:)

 

spakk , your HDMI works with voodooHDA ? 

Share this post


Link to post
Share on other sites

 with AppleHDA no sound output but  AppleHDAController is active

AMD_iMac14,2 IOReg does show AppleHDAController loading for the Nvidia HDMI audio codec. HDMI audio works with the native Mavericks AppleHDA.  See Mavericks AppleHDA HDMI Audio - OSx86 10.9 (Mavericks) - InsanelyMac Forum

For onboard audio, try this AppleHDAController binary edit:

Find: 86 80 20 1C

Repl: 10 02 43 83

 

Reply with IOReg (.ioreg not .txt)

Share this post


Link to post
Share on other sites

Thanks toledo. I'll try it and will report :)

Share this post


Link to post
Share on other sites

this is the result but no sound

 

 

 

Edit:

 

toledo, please watch my iioreg to that : (vendor-id and device-id) will now be displayed 0x10de0ac0 but it must be 0x10de0bee

 

but change after the Hex has done something :w00t: :drool:

AppleHDA with Hex-patch.png

CodecDump.zip

AppleHDAController_after Hex_patch.png

Edited by spakk

Share this post


Link to post
Share on other sites

please watch my iioreg to that : (vendor-id and device-id) will now be displayed 0x10de0ac0 but it must be 0x10de0bee

 

but change after the Hex has done something

Those device_ids are in a plist and  support legacy native products.; not relevant.

AppleHDAController patch did not work.

What AppleHDA.kext is installed; native, 889 or something else?  Attach.

Share this post


Link to post
Share on other sites

from Combo Update10.9.2

Those device_ids are in a plist and support legacy native products.; not relevant.

AppleHDAController patch did not work.

What AppleHDA.kext is installed; native, 889 or something else? Attach./quote]

 

please create a link to the version that you think should work with my system. I have tested so many sound driver in the last hours and now I have lost the overview. thanks for your help.

Share this post


Link to post
Share on other sites
So ALC275 is unsupported by this topic. :( If anyone knows how, HELP! I don't want to stay w/ Voodoo Quality Sound :(

 

open IoregExplorer, Save the IOREG and upload it here,

better you post a code_dump create code_dump under Linux from your sound card and upload the code here

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      Some users claim that using VoodooHDA they hear loud bump at system start and sound in system comes with noise.
      Although this can be repaired with existing drivers I propose a version that do this automatically.
      It started silently and have very clear output. The file is compiled as 32/64 and works from 10.6 up to 10.12.
      VoodooHDA.kext-289.zip
      The sources is in my signature.
       
      There is a VoodooHDA,prefPane compatible with Sierra
      VoodooHDA.prefPane-289.zip

       
      Now there is a version 2.9.0 by Zenith432.
      It can work with multichannel sound and play it on 5.1 analog system.

      VoodooHDA.kext-2.9.0d8.zip
      27.04.2017 
      d10 - Fix issues involving AudioControls
      VoodooHDA.kext-2.9.0d10.zip
       
      20.11.2018
      Fix issue with scratch on slow CPU
      VoodooHDA.kext-291SSE.zip
       
      04.05.2019
      More checks for memory allocation. More clear sound anyway. 
      VoodooHDA.kext-292.zip
      IOAudioFamily.kext.zip
       
       
    • By Mieze
      Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy.
       
      As of now the driver supports the following members the RTL810X Fast Ethernet family:
      RTL8101E RTL8102E RTL8103E RTL8401E RTL8105E RTL8402 RTL8106E RTL8106EUS RTL8107E   Here is a list of the driver's basic features:
      Supports Sierra (maybe El Capitan). 64 bit architecture only. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2. Built using Xcode 4.6.3.  
      Changelog Version 2.0.1 (2018-05-10): Fixes a problem with retrieval of the permanent MAC address on some chips. Version 2.0.0 (2017-04-04): Uses Apple's private driver interface introduced with 10.8. Adds support for the RTL8107E. Supports packet scheduling with QFQ. Adds support for flow control and EEE. Version 1.0.0 (2014-05-24): First offical release.     Installation   Before you install the driver you have to remove any installed driver for RTL810X. Goto /S/L/E and delete the old driver. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Install the new driver and recreate the kernel cache. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.   Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      Getting the driver
      There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/ The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100   Mieze
    • By Mieze
      A New Driver for Realtek RTL8111
       
      Due to the lack of an OS X driver that makes use of the advanced features of the Realtek RTL81111/8168 series I started a new project with the aim to create a state of the art driver that gets the most out of those NICs which can be found on virtually any cheap board on the market today. Based on Realtek's Linux driver (version 8.035.0) I have written a driver that is optimized for performance while making efficient use of system resources and keeping the CPU usage down under heavy load.

      Key Features of the Driver
      Supports Realtek RTL8111/8168 B/C/D/E/F/G found on recent boards. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Fully optimized for Mountain Lion (64bit architecture) but should work with Lion too. As of now there is no support for Snow Leopard but it can be added if someone will create the necessary patches. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2.  
      Limitations
      As checksum offload doesn't work with jumbo frames they are currently unsupported and will definitely never be. No support for 32bit kernels.  
      Installation
      Before you install the driver you have to remove any installed driver for RTL8111/8168.
      Goto /S/L/E and delete the old driver (Lnx2mac, AppleRealtekRTL8169, etc.). Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be found in /var/log/system.log. For Sierra and above use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable.  
      FAQ
      How can I retrieve the kernel logs? In Terminal type "grep kernel /var/log/system.log". I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Take a look at the driver's Info.plist file. There you will find an option named <key>enableEEE</key>. Change its value from <true/> to <false/>. Don't forget to recreate the kernel cache after changing the value. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Current status
      The driver has been successfully tested under 10.8.x and 10.9 with the B, C, D, E, F and G versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.2.2 (2018-01-21) Force ASPM state to disabled/enabled according to the config parameter setting. Requires 10.12 or newer. Version 2.2.1 (2016-03-12): Updated underlying linux sources from Realtek to 8.041.00. Added support for RTL8111H. Implemented Apple’s polled receive driver model (RXPOLL). Requires 10.11 or newer. Support for older versions of OS X has been dropped. Version 2.0.0 (2015-06-21): Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Please note that 2.0.0 is identical to 2.0.0d2. Only the version number has changed. Version 1.2.3 (2014-08-23): Reworked TSO4 and added support for TSO6. Version 1.2.2 (2014-08-44): Added an option to disable Active State Power Management (ASPM, default disabled) as ASPM seems to result in unstable operation of some chipsets. Resolved a problem with Link Aggregation after reboot. Added a workaround for the multicast filter bug of chipset 17 (RTL8111F) which prevented Bonjour from working properly Version 1.2.0 (2014-04-24): Updated underlying linux sources from Realtek to 8.037.00. Improved interrupt mitigate to use a less aggressive value for 10/100 MBit connections. Version 1.1.3 (2013-11-29): Improved transmit queue handling made it possible to reduce CPU load during packet transmission. Improved deadlock detection logic in order to avoid false positives due to lost interrupts. Version 1.1.2 (2013-08-03): Improved SMB performance in certain configurations. Faster browsing of large shares. Version 1.1.0 (2013-06-08): Support for TCP/IPv6 and UDP/IPv6 checksum offload added (can be disabled in Info.plist). Maximum size of the scatter-gather-list has been increased from 24 to 40 segments to resolve performance issues with TSO4 when offloading large packets which are highly fragmented. TSO4 can be disabled in Info.plist without rebuild. Statistics gathering has been improved to deliver more detailed information (resource shortages, transmitter resets, transmitter interrupt count). The interrupt mitigate settings has been changed to improve performance with SMB and to reduce CPU load. Configuration option added to allow for user defined interrupt mitigate settings without rebuild. Version 1.0.4 (2013-05-04): Moved setLinkStatus(kIONetworkLinkValid) from start() to enable(). Cleaned up getDescCommand(). Version 1.0.3 (2013-04-25): The issue after a reboot from Windows has been eliminated. Version 1.0.2 (2013-04-22): Added support for rx checksum offload of TCP and UDP over IPv6. Version 1.0.1 (2013-03-31): Improved behavior when rx checksum offload isn't working properly. Adds the chipset's model name to IORegistry so that it will show up in System Profiler.  
      Known Issues
      There are still performance problems with regard to SMB in certain configurations. My tests indicate that Apple's Broadcom driver shows the same behavior with those configurations. Obviously it's a more general problem that is not limited to my driver. WoL does not work in certain configurations. Old systems with 3 and 4 series chipsets exhibit performance issues in recent versions of macOS because there is no optimized power management for these systems in macOS anymore as Apple dropped support for the underlying hardware a long time ago. In case you are affected, please upgrade your hardware or find an alternative solution because I have no plans for a workaround. Sorry, but I don't think that it's worth the effort.  
      Getting the driver
      The source code can be found here: https://github.com/M...driver_for_OS_X There is also a pre-build binary for Mavericks and Yosemite: http://www.insanelym...n-and-wireless/  
      Building from Source
      I'm using XCode 4.6.3 for development. You can get a free copy of XCode after becoming a member of the Apple developer program. The free membership is sufficient in order to get access to development tools and documentation.
    • By tom666
      osx10.14
      i5-4250u
      i have added "irq hdef hdau  mutex osys10" patch
      and install acpibettery on clover ,but the battery management still donot work

      my audio card is alc269vc ,i try to use applealc,and tried all the layoutid, all of those colud not work.
      2019-03-31 20:18:23.389590+0800  localhost kernel[0]: (kernel) AppleALC:     alc @ failed to find IOHDACodecVendorID, retrying 0
      i have also use linux to find the codec
      i uploaded the clover , dsdt,codec.
      This problem has been bothering me for two days.
      thanks
       
       
      all.zip
      2019-03-31 20:18:17.997435+0800  localhost kernel[0]: calling mpo_policy_init for Lilu
      2019-03-31 20:18:18.003796+0800  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.3.5 (Lilu)
      2019-03-31 20:18:23.389590+0800  localhost kernel[0]: (kernel) AppleALC:     alc @ failed to find IOHDACodecVendorID, retrying 0
      2019-03-31 20:18:23.398483+0800  localhost kernel[0]: (kernel) Lilu: patcher @ lookup patching applied only 0 patches out of 1
    • By noisegate
      Hi,
       
      I use AppleALC v1.3.5, I can see the device in system info but no sound. Any idea?
       
      Thanks!
       
×