Jump to content
toleda

El Capitan: Realtek ALC AppleHDA Audio

388 posts in this topic

Recommended Posts

Advertisement

Works here too, ALC1150, Z87, El Cap, Chameleon.

 

It complains on startup about extra characters at line 177 but still works ok.

Share this post


Link to post
Share on other sites

The thing you must do - before running the GREAT  audio_realtekALC-110.command, is to check if you already have set the layout-id to Audio-ID  1,2 or 3.

Mostly it was set before to other layout-id , like 12  (x0C) or 885. (in dsdt HDA part or by injection chameleon other injectors like bootloaders or kexts)

If you set the rigtht AUDIO ID (= layout-id) all other things (the patch, backup old unpatched kext) will be made by the patch script.

 

Look this part above about the many ways (1. to 5., below listed)  to set the AUDIO-ID (= layout-id) - you only have use ONE of that:

Audio ID Injectionaudio_ALCInjection : 01,02 or 03

  1. HDEF/kext/no dsdt/HDAEnabler_.kext = Audio_ID
  2. HDEF/dsdt/layout-id = Audio_ID,
  3. HDEF/ssdt/layout-id = Audio_ID
  4. HDEF/Clover/config.plist/Devices/Audio/Inject = Audio_ID
  5. HDEF/Chameleon/Extra/org.chameleon.Boot.plist
    1. HDAEnabler = Yes
    2. HDEFLayoutID = 01000000 or 02000000 or 03000000
    3.  

 

If  you use dsdt way - in list above 2. , it  looks like:

  Device (HDEF)

         .....
 
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x04)
                        {
                            "layout-id", 
                            Buffer (0x04)
                            {
                                0x01, 0x00, 0x00, 0x00    // in the past often was set to x0C or others
                            }, 
 
                            "PinConfigurations", 
                            Buffer (Zero) {}
                        }, Local0)
          ....
                }
            }

Share this post


Link to post
Share on other sites

I have ACL892 but cant make it work, can you please help me step by step?

first of all what method u wanna use ?

Clover way or AppleHDA.kext way?

Share this post


Link to post
Share on other sites

first of all what method u wanna use ?

Clover way or AppleHDA.kext way?

 

 

"Piker-Alpha/patch alias" but it's not important, please help me with your method. I use MSI H77GMA45 with ACL892. 

Thanks

Share this post


Link to post
Share on other sites

Hi! your post helps is very cool. The only "but" that I have is the method to obtain the native AppleHDA not work for El Capitan. The installation package of El Capitan has changed. I got looking at the search box but it had not been for that I would not have found. Thank you. :thumbsup_anim:

Share this post


Link to post
Share on other sites

I have a Realtek ALC889

I'm still using an AppleHDA patched kext (i'm using it since Osx Lion) and it works very well also with El Capitan .

 

BTW i will give a try ....

Share this post


Link to post
Share on other sites

the method to obtain the native AppleHDA not work for El Capitan.

Run the El Capitan Installer over the current EL Capitan install to restore native AppleHDA.kext.

Share this post


Link to post
Share on other sites

Hello,

 

I have a P5Q motherboard with a ALC 888S-VD sound card. This model is excluded from the above tuto. It makes days that I'm looking for a solution to get it working on el Capitan. Has someone any clue for this issue ?

 

Thank you 

Share this post


Link to post
Share on other sites

Hello Toleda

 

Thank you for the very quick answer. Here is below my sound card détails:

 

Audio device: 0x80863A3E

Sub device: 0x104382FE

Code ID: 0x10EC0888

Revision: 0x0101

Codec name: Realtek ALC888S-VD

 

Your support is very ap​preciated

Share this post


Link to post
Share on other sites

Code ID: 0x10EC0888

Revision: 0x0101

Codec is 888/00101

Legacy is 888/00201

Run either Post #1/Realtek ALC AppleHDA Scripts

Answers:

Legacy: y

Continue: y

Reply with script/Terminal/Export Text As...

Share this post


Link to post
Share on other sites

Thanks Toleda. The sound panel is ok now.

However, I have a strange behavior from my computer. The first time after applied your patch and restarted, the sound was bad. I shut down the computer and after 1 night, I started it again. then the sound was very good and thought the problem was definitely resolved. After restarted again, the issue rise again : bad sound. It comes again with an issue with the time clock which is not accurate (too slow).

Don't you have any idea on the reason of such behavior ?

Share this post


Link to post
Share on other sites

It comes again with an issue with the time clock which is not accurate (too slow).

Don't you have any idea on the reason of such behavior ?

No.

Share this post


Link to post
Share on other sites

Hello everyone,

 

Can someone please tell me what I`m doing wrong?

 don't have sound yet and, I tried all Three Methods that you suggested in the first post of this topic.

 

1. method: realtekALC/patch kext in place

audio_realtekALC-110.command.zip  - didn`t help

You can see the log in "audio_realtekALC-110_v1.0h.command.txt.zip"

 

2. method: cloverALC/patch kernel cache  - didn't help

 

3. method: Piker-Alpha/patch alias  - didn't help

When i tried ./AppleHDA8Series.sh -a 887 -l 3 -d /System/Library/Extensions

in terminal, I got message "/System/Library/Extensions/FakeSMC.kext was installed improperly and cannot be used."

Do I need to reinstall it somehow or just delete from Extensions and change with other FakeSMC?

 

Then, I tried to manually select model of my Realtek with:

./AppleHDA8Series.sh -b AppleHDA

then i choose the second option (Realtek ALC  887 (0x10EC0887 / 283904135)) and with layout-id : 0 -

I got message "Looking in: /System/Library/Extensions/FakeSMC.kext for ConfigData

Error: ConfigData NOT found!"

You can see the log in "terminal-layout 0.txt"

 

When I tried to change layout-id from 0 to 1, I got a message that everything is OK and "ConfigData for Realtek ALC 887 found!",  but after restart I still don't have a sound card installed. I got the same message also for layout-id=2 and 3

You can see the log in "terminal-layout 1.txtterminal-layout 2.txt and terminal-layout 3.txt"

 

I will also upload a log file from IOReg, DPCIManager and Console file from last boot.

 

My configuration is:

System Version: OS X 10.11 (15A284) / Kernel Version: Darwin 15.0.0 / 

MSI H61M-P31 (audio by Realtek ALC887, network by Realtek 8111E) / Intel i5-2500k / 8GB DDR3 / Saphire HD5870 / HDD1: 64GB SSD / HDD2: 2TB 3.5" 

 

 

Thank you all guys in advance for all your time and effort.

iMac.spx.zip

DSDT.aml.zip

nOOb’s iMac.ioreg.zip

system.log.zip

terminal-layout 0.txt

Terminal-layout 1.txt

Terminal-layout 2.txt

Terminal-layout 3.txt

Share this post


Link to post
Share on other sites

No.

 

I finally found the solution.

I have analyzed both logs when the computer had good and bad sound. With Excel, I have compared each lines and found some différences. On the first log, the CPU was loaded with a certain speed and on the other log, the CPU speed was different. See below:

 

Log1                                                                                                 Log2

 

FSBFrequency=422MHz DMIvalue=333330kHz FSBFrequency=633MHz DMIvalue=333330kHz

Finally: Bus=333295kHz CPU=3000MHz Finally: Bus=499937kHz CPU=3000MHz

 

 

 

 I have then fixed the correct speed by copying the data of the Log1 into Clover (CPU part / Frequency MHz and Bus Speed kHZ).

 

I have restarted my computer and everything is going fine now.

 

CONCLUSION: Check your CPU speed in Clover !

 

Share this post


Link to post
Share on other sites

Can someone please tell me what I`m doing wrong?

Audio ID injection not set,;see Post #1, Audio ID Injection (required)

You can see the log in  "audio_realtekALC-110_v1.0h.command.txt.zip"; not attached

Pike's script /10.11 not supported; see Piker-Alpha AppleHDA8sries Script, Step 7

For addition support; see Post #1, Problem Reporting

restarted my computer and everything is going fine now.

Thanks.

Share this post


Link to post
Share on other sites

Hey, Toleda!
Can you help me?
I have
MB: ASUS P6TSE with ALC1200

Video: GTX 770(4gb, GIGABYTE)
Proc: intel core i7 920 @2.67
Is there any way to enable HDMI audio?
OSX 10.10

Share this post


Link to post
Share on other sites

I have a strange bug behavior.

System: Asus X99 Deluxe, Yosemite OS X 10.10.5 (14F1021), as well as on El Capitan 10.11.1

Using AppleHDA 2.6.3-toledaALC1150

Using Clover Audio Inject (layout 1), SSDT to fix ALZA to HDEF and Clover kextpatch for AppleHDAController 208C to 208D (X99 ALC Onboard Audio).

 

This worked fine for a long time, and I realized today that the front left and right speakers are not working (when they were in the past), more exactly the volume is very very low. I check audio configuration, and it is not from there.

I switched speakers to be sure it was not from the speakers themselves, and it is not.

For some reasons, now, the volume for the integrated output is way way lower than the others (so low that it is not usable).

The volume for the 2 other integrated line outputs are fine.

 

Any idea on what is happening?

Share this post


Link to post
Share on other sites

Not strange; external amp, expected

See X99-DELUXE | Motherboards | ASUS USA/Flawless audio. . . /Audio Amplifier. . .

Install 1150 edited Dolnor/EAPD-Codec-Commander

Ha!

 

I was using codec commander (for sleep problems), and when I moved from Chameleon to Clover, I put it in Clover kexts… I still had sound on the 5.1 system, so I did not pay attention, but it stopped loading as it has to be in S/L/E to work properly apparently… I just moved it back in S/L/E and miracle it works again.

 

Thank you toleda!

 

Any chance to see the 10.11 AppleHDA working on the X99 (patched of course)? 10.9.4 one is still working fine, but for how long…

Share this post


Link to post
Share on other sites

Audio through my analog ports is working after audio_cloverALC-110.command, but I am struggling to customize the install to get the S/PDIF output working. I really prefer to use the digital outputs for sound quality, so I bought this small addition to go with my board:

 

http://www.amazon.com/gp/product/B0035J9Z7W?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00

 

It connects the S/PDIF header from the board to ports on the back of the case. It definitely has power, as the laser for the optical output is working. I have tried both the optical and coaxial S/PDIF outputs from the attached board. Seeing that neither was working, I tried to follow the instructions here:

 

https://github.com/toleda/audio_ALC_guides/blob/master/Customization%20-%20Realtek%20ALC%20AppleHDA_v2%20%5BGuide%5D.pdf

 

The relevant section says:

 

7. Substitute SPDIF-2 Wire Output: Replaces SPDIFOut Optical with motherboard SPDIF 2 wire SPDIF audio output device

Credit: intamara: Lion HDMI Audio - Part 2a: DSDT Edits/Discrete - AMD/Nvidia - Page 29, Post 289
A. Edit Platforms.xml/zml
1. Open Item/PathMapID
2. Open the current SPDIFOut (last item)
3. Edit this path map as follows:
4. Current:
⁃ Item 0/NodeID/Number/30
⁃ Item 1/NodeID/Number/6
5. New:
⁃ Item 0/NodeID/Number/17
⁃ Item 1/NodeID/Number/16
B. Edit HDAHardwareConfigDriver/info.plist or realtekALC/Info.plist
1. Open Item/CodecID
2. Verify CodecID/LayoutID
3. Edit ConfigData (1150 only, edit each entry, 21 to 01)
⁃ Find: 21171cf0 21171d00 21171e00 21171f40
⁃ Replace: 21171ca0 21171d01 21171e43 21171f99
⁃ Find: 21e71c90 21e71d61 21e71e4b 21e71f01
⁃ Replace: 21e71cf0 21e71d00 21e71e00 21e71f40
C. Save, install and restart
 
It appears that I can edit Platforms.zml as described, but I can't find the same items in the Platforms.xml to edit. Also, the structure of the HDAHardwareConfigDriver/info.plist seems to be different than is described, and I cannot figure out how to achieve the edits listed. I must say that I am a bit confused about the item numbers, as everything in the plists is an item. According to the guide, Realtek 887 is item 1. Specs for the motherboard say Realtek 887, and so did the audio_cloverALC-110.command install script. DPCIManager lists the audio codec as Realtek 888B, but apparently this is the same as 887.
 
ASUS H97M-PLUS — BIOS v2404, i3-4370, ASUS GeForce GTX 750 Ti STRIX
 
Had to do some workarounds to attach files as some formats are not allowed for posts on this board. Hopefully this will be enough information for someone with more knowledge to assist me.
 
One last thought. In the tools listed for inflating and deflating the zlib files here:
 
 
The instructions for the perl script leave a .xml file that Xcode reads as xml. To get it to read as a plist, I just appended .plist to the file, which worked great. Then I thought, why not just add this when inflating the .xml. This also worked. Here are the commands:
 
Last login: Sat Oct 24 16:41:19 on ttys000
Anachronauts-iMac:~ anachronaut$ cd /Users/anachronaut/Desktop/New\ Folder 
Anachronauts-iMac:New Folder anachronaut$ perl zlib.pl inflate Platforms.xml.zlib>Platforms.xml.plist
Anachronauts-iMac:New Folder anachronaut$ perl zlib.pl inflate Platforms.zml.zlib>Platforms.zml.plist
Anachronauts-iMac:New Folder anachronaut$

Run the El Capitan Installer over the current EL Capitan install to restore native AppleHDA.kext.

 

I extracted the AppleHDA.kext from the El Capitan installer. It was only in one place, and seems to be complete. It is working on my computer after the audio_CloverALC110.command script.

Clover_config_plist.txt

DPCIManager_Misc_Boot_Log.txt

DPCIManager_Status.tiff

info_plist.tiff

Platforms_xml.tiff

Platforms_zml.tiff

System_Report_Audio1.tiff

System_Report_Audio2.tiff

Anachronaut’s iMac IOReg.tiff

platforms_xml_plist.txt

Platforms_zml_plist.txt

AppleHDAHardwareConfigDriver_Info.txt

Audio Clover 110 audio script.txt

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