Jump to content
toleda

El Capitan: Realtek ALC AppleHDA Audio

388 posts in this topic

Recommended Posts

10.11.5 audio_realtekALC-110_v1.0o1.command is the only thing that realtek alc885 audio work perfect on my computer,though it said it can't find clover use ozmosis.seems like c-media usb audio card is bad because it cause my external HDD disappear.

Share this post


Link to post
Share on other sites
Advertisement

10.11.5 audio_realtekALC-110_v1.0o1.command is the only thing that realtek alc885 audio work perfect on my computer,though it said it can't find clover use ozmosis.seems like c-media usb audio card is bad because it cause my external HDD disappear.

it did say "clover/chameleon is not available". so I didn't continue.

 

can you please tell me what audio id did you get?

 

thanks for the help

Share this post


Link to post
Share on other sites

Hello Toledo ... here are my answers


 


True.


I expected 2  answers (green and black) for each time. Confirm:


The results are for the Z97 system only (y/n)? Y


Green and Black perform exactly the same (y/n)? Y


Assume the responses above are for Black only, then


Black: There is no difference with or without codeccommander (y/n)? Y


Black: Sound available before 30 seconds after Desktop appears (y/n)? Y


 


Is the only only problem, the delay for sound to start (y/n)? Y


 


Thans for Your Help


Share this post


Link to post
Share on other sites

I tried 1 to 3 options  (cloverALC to piker) on my setup but it says my audio ID = 0 is not supported. I never touched that DSDT section. 

Native dsdt does not set Audio ID, see Post #1/Audio ID Injection. Use Audio ID: 1.

Additional support, see Problem Reporting, Post #1, attach all requested files.

Is the only only problem, the delay for sound to start (y/n)? Y

No ideas.

Share this post


Link to post
Share on other sites
It's ok Toledo ... I now have the black audio output then selected in operation and have this in Sound settings Lin Out (2) and it is also everything without any error, no sleep.

 

I have just only in Windows operating change anything because since will have standard as are the green output.

 

Only I would be interested in why the o is to the green socket, with this MSI Z97 G43 Board, with this version of ALC892. When MSI Z77 G43 no such problems, just has a different version of the ALC892.

 

Nevertheless big thanks to you for your help try this strange problem ... and if the other users of the same MSI Z97 G43 also? these same problems?

Share this post


Link to post
Share on other sites

why the o is to the green socket, with this MSI Z97 G43 Board, with this version of ALC892. When MSI Z77 G43 no such problems, just has a different version of the ALC892.

"why the o is to the green socket"??

Codec is not the issue; big differences in 9series chipset and 7series chipset and the specific implementation on each motherboard.  In my case, no issues with Maximus VII Impact (Z97), various issues with Z87I.  

Share this post


Link to post
Share on other sites

can you please check this file? https://github.com/toleda/audio_ALCInjection/blob/master/%5BGuide%5D-OSX_ssdt-installation_v4.pdf

 

It's not in github. thank you

 

edit: seems chrome/safari (on both the Hackintosh and on my MBP) are interpreting characters like square brackets, colons and perhaps more into their HTML encoding equivalent (example: open square bracket = %5B) thus it cannot find the file. I have to manually edit the URL.

Share this post


Link to post
Share on other sites

A bit confused here.

 

so I edited my DDST to include the audio ID. According to IOReg, the layout is 1.

 

But when I ran audio_codecdetect.command, it says my Audio ID is not supported but it can also detect it as 1.

 

Can someone clarify?

 

thanks

 

update: I ran the 3rd option anyway and it created a new AppleHDA885.kext for me. My question is, the next time I perform a fresh install of OS X, I can I just copy the KEXT into kext/10.11 folder inside Clover config? Thanks again

 

 


=> ./audio_codecdetect_v1.3.command 

File: audio_codecdetect.command_v1.4

 

HDMI audio codec(s)

 

Onboard audio codec

Realtek: 0x10ec0888

 

OS X/10.11.4 Onboard Audio

Device: HDEF@1B

Audio ID: Not supported

Currrent Audio ID: 1 (set: 1, 2, or 3)

Fix, try:

1. https://github.com/toleda/audio_ALCInjection/tree/master/ssdt_hdef/

ssdt_hdef-1-with_ioreg/hdef.zip (or -2 or -3, select View Raw)

2. CLOVER/config.plist/Devices/Audio/Inject/1 (or 2 or 3)

 

No system files were changed

To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...

Share this post


Link to post
Share on other sites

Github problem, no longer displays pdf. Investigating.

Work around: select the repo, click Download Zip.

so I edited my DDST to include the audio ID. According to IOReg, the layout is 1.

 

update: I ran the 3rd option anyway and it created a new AppleHDA885.kext for me. My question is, the next time I perform a fresh install of OS X, I can I just copy the KEXT into kext/10.11 folder inside Clover config? Thanks again

Script error, fixed

Codec is 888.   Script installs AppleHDA888 to L/E, no need to copy anything to EFI

Share this post


Link to post
Share on other sites

Github problem, no longer displays pdf. Investigating.

Work around: select the repo, click Download Zip.

Script error, fixed

Codec is 888.   Script installs AppleHDA888 to L/E, no need to copy anything to EFI

my DFI DK P45 T2RS PLUS codec is 885,his Z97-G43 codec is 888,I don't have a problem when I using your Realtek ALC AppleHDA Audio.His codec doesn't work like native like instant work after boot right?So what's the best codec for Realtek ALC AppleHDA Audio except 1150,what about MSI H81M-E33 codec 887?

Share this post


Link to post
Share on other sites

 "why the o is to the green socket"??

Codec is not the issue; big differences in 9series chipset and 7series chipset and the specific implementation on each motherboard.  In my case, no issues with Maximus VII Impact (Z97), various issues with Z87I. 

 

 Thank you for this Tips.

Share this post


Link to post
Share on other sites

His codec doesn't work like native right?So what's the best codec for Realtek ALC AppleHDA Audio except 1150,what about MSI H81M-E33 codec 887?

Post #1:

Supported codecs: Realtek Codecs and Applications

Exceptions: Unsupported/Non-working Realtek ALC AppleHDA

 

Have not found any audio problems with the supported codecs.  Specific motherboards have issues with audio not working after wake, external amplifiers, etc. If audio works after a restart, the codec is working properly. Dual boot requires Windows/Sound driver.

Share this post


Link to post
Share on other sites

Post #1:

Supported codecs: Realtek Codecs and Applications

Exceptions: Unsupported/Non-working Realtek ALC AppleHDA

 

Have not found any audio problems with the supported codecs.  Specific motherboards have issues with audio not working after wake, external amplifiers, etc. If audio works after a restart, the codec is working properly. Dual boot requires Windows/Sound driver.

I find a replacement for Realtek ALC AppleHDA Audio,AppleALC http://www.insanelymac.com/forum/topic/311293-applealc-—-dynamic-applehda-patching/

which keep SLE vanilla

Share this post


Link to post
Share on other sites

Same files, your choice.

Why this is possible?Because some Mac model has Realtek ALC?Which model?

Share this post


Link to post
Share on other sites

v2.5 - 4/8/16 - x99/AppleHDA.kext/10.11 support, see Post #1

Unsupported/Non-working Realtek ALC AppleHDA

2. X99/Intel High Definition Audio

Credit: bOLEMO

No idea if it will work; try.  Likely both audio devices will be labeled the same.

 

Thank you for the credit toleda.

 

Also, after reconstructing the kext cache for something else, it took several restarts to have the device recognized again (I used method I.2). I though that this is what happened when I tried method I.3 (pikeralphaALC), so I tried again, and I confirm that it works (and the problem was not related to the method itself). So I.1, I.2 and I.3 are working.  :)

Share this post


Link to post
Share on other sites

Why this is possible?Because some Mac model has Realtek ALC?Which model?

OS X configures the codec with files, many ways to present OS X with codec specific files.

All codecs comply with Intel High Definition Audio spec, codec dump specifies the configuration of installed codec.

Native codec, sole source Cirrus Logic 4206+

macpro5,1 uses ALC885; vintage Macs used 269, 662, 883, etc.

if the new kext is installed in /Library/Extensions, do I still need to delete the original AppleHDA.kext in SLE? thanks

No

What is a difference between Realtek Alc269 and Realtek Alc269 BRIX? 

Google/BRIX: GIGABYTE BRIX Ultra Compact PC Kit

Headphones and Optical only.

I.1, I.2 and I.3 are working. 

Confirmation, thanks.

Share this post


Link to post
Share on other sites

Hi toleda,

 

Quick question: have you ever encountered the following sound issue or heard of it: ascending sound (for like half a second, maybe less, it's barely noticeable, but it's definitely there) when starting playing something like a video on youtube (only at the beginning of the video) or when getting sound notifications for new mails, sent mails and things like that?

 

Is this related to the codec (ALC892) or...something related to El Capitan like maybe sound is not properly initialized right from the very beginning at full volume (or wherever you left the volume slider)...? I didn't find any setting for "ascending sound" in El Capitan 10.11.4 that I'm using now. So..I don't know if it's an OS X issue/feature or...maybe something related to the motherboard/codec.

 

Recently I updated my motherboard. And, although the sound is working fine, I'm having this little issue.

 

Any thoughts on it?

Share this post


Link to post
Share on other sites

Here is HDEF DSDT injection MaciASL Patch credit Clover,but I don't know what's HDEF abbreviation for and what's this patch mean,toleda HDEF DSDT injection doesn't work.

# Insert device HDEF into device with _HID PNP0A08 (PCI0)
#
into device name_adr 0x001B0000 parent_hid PNP0A08 remove_entry;
into device name_hid PNP0A08 insert
begin
Device (HDEF)\n
{\n
Name (_ADR, 0x001B0000)\n
Method (_PRW, 0, NotSerialized)\n
{\n
Return (Package (0x02)\n
{\n
0x0D,\n
0x05\n
})\n
}\n
\n
Method (_DSM, 4, NotSerialized)\n
{\n
Store (Package (0x06)\n
{\n
"layout-id", \n
Buffer (0x04)\n
{\n
0x01, 0x00, 0x00, 0x00\n
}, \n
\n
"MaximumBootBeepVolume",\n
Buffer (One)\n
{\n
0x01\n
},\n
\n
"PinConfigurations", \n
Buffer (Zero) {}\n
}, Local0)\n
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
Return (Local0)\n
}\n
}
end

Share this post


Link to post
Share on other sites

ascending sound (for like half a second, maybe less, it's barely noticeable, but it's definitely there) when starting playing something like a video on youtube (only at the beginning of the video) or when getting sound notifications for new mails, sent mails and things like that?

No.  No suggestions at this time.

 

HDEF DSDT injection doesn't work.

Not helpful.  Available to solve problems, no files attached.

Support Post #1 solutions only.  

Share this post


Link to post
Share on other sites

Oh well I bought a Optical Splitter instead.  Maybe that will work for what I'm trying to achieve.  

Share this post


Link to post
Share on other sites

No.  No suggestions at this time.

 

Understood. Thank you. :)

 

Just in case it might trigger an idea, I just timed it. How long it takes for the sound to "fall asleep". Around 30-40 seconds.

 

So if I start a video, for example, pause it, then let it cool down for around 30 seconds, when I hit Play again, this issue will occur. It's like the sound disengages for some reason, instead of being always on, so it can resume at any point. Maybe not the sound, but the volume.

 

As I said, in my case, it's not that annoying, since it re-initializes quickly. So it's like a very short ascending volume till it reaches the previously defined volume. It is a bit annoying on short notifications/sound effects. Cause they are too short for the sound to actually initialize completely. So more often then not, you won't hear the notification if the sound has been idle for more than 30-40 seconds. I still wonder, is this intended? Could this be a bug in OS X's AppleHDA kext for 10.11.4? This is really weird.

 

Toleda, if I can help with log files or anything you need to take a closer look at this, or try to debug the situation, you know you can count on me. Just tell me what you need, and I'll try to provide it.

Share this post


Link to post
Share on other sites

it's like I wrote you in my PN .. it need not be puzzled here what and why it is. The solution is yet in my sent to you mail !!

 

let especially this Command to run and evaluate the info.plist and then adjust the AppleALC then and it all goes WITHOUT asleep after 30 seconds.

 

One should look at the hitherto functioning AppldHDA.kext then to adjust the new AppleALC.kext it!

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 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!
       
×