piker-alpha / applehda8series.sh Goto Github PK

Below is the output of script
--I am using fresh install of Yosemite updated to DP3 untouched with Chameleon r2380

The supported Realtek ALC codecs for AppleHDA8Series.sh are:

[1] Realtek ALC  885 (0x10EC0885 / 283904133)
[2] Realtek ALC  887 (0x10EC0887 / 283904135)
[3] Realtek ALC  888 (0x10EC0888 / 283904136)
[4] Realtek ALC  889 (0x10EC0889 / 283904137)
[5] Realtek ALC  892 (0x10EC0892 / 283904146)
[6] Realtek ALC  898 (0x10EC0899 / 283904153)
[7] Realtek ALC 1150 (0x10EC0900 / 283904256)

Please choose the desired codec for the hardware: 4
Error: ACPI Device (HDEF) {} NOT found!
ACPI tables appear to be broken and require (manual) patching!
Aborting ...
Done.

1. OS X version/motherboard model/BIOS version/processor/graphics
2. Procedure/Guide Used/AppleHDA.kext version
3. AppleHDA(codec).kext (i.e., AppleHDA1150.kext)
4. Copy of IOReg - IOReg_v2.1/File/Save a Copy As…, verify file (not
       ioreg.txt)
5. Extra/dsdt.aml (if installed)
6. Console/All Messages/kernel Sound assertions selected/Save
       Selection As…..
7. Screenshot of System Information/Hardware/Audio/Intel High
       Definition Audio (not Devices)

1. 10.10.3 / Gigabyte GA-X99M-Gaming 5 / BIOS version f4a / i7 5930K / PNY Nvidia GTX980
2. tried with
   http://www.tonymacx86.com/yosemite-desktop-guides/143849-haswell-e-x99-motherboard-temporary-guide-os-x-10-10-a-23.html#post909616 (SSDT-1.aml taken from)
   audio_cloverALC-100.command.zip
   last one https://github.com/toleda/audio_pikeralphaALC

AppleHDA version 272.18
3) included
4) Mac Pro included
5) SSDT-1.aml included
6) sound assertion messages.log included
7) screen shot included

no match found for: __ZN18AppleHDAController18setupHostInterfaceEv

Hi i got this problem, my ALC892 notebook did worked perfectly with you're patch on 10.10, now i updated to 10.10.1 and i cannot boot OS X anymore... But when i put the applehda.kext from OS X 10.10 back the audio works fine again. I have more details and reports in this post.
http://www.tonymacx86.com/hp-probook-mavericks/118877-patch-applehda-kext-fly-clover-bootloader-21.html#post929552

Seems like apple changes something in their code and the binary patch broke

First of all, I really like your solution, bc in conjunction with a Clover kext patch it allows for a completely untouched AppleHDA.kext. However, it seems the kext still needs to be placed in S/L/E.

When I put this kext in /EFI/CLOVER/kexts/10.10 it does not seem to load.

Question: is this a bug, a missing feature or more a kind of technical limitation? Of course it would be really nice if that would be possible, bc then you can have a completely untouched vanilla OS X installation, with everything hackintosh specific completely contained in your EFI partition. Right now, your patched kext is the only one which does not allow this, so of course it would be great if this could be made possible.

Otherwise, thanks and keep up the good work!

Hi Pike,
Thanks for your awesome work you're doing.
One thing that I found is that after DP3 or 4, the Output names for sound are being showed in Russian.
There is a folder created in AppleHDA>Contents>Resources>ru.lproj
After deleting it, the names are showed in English again. But after an update the ru.lproj folder is back again. I'm using V3.1 script.

Again, thanks for sharing your work.

Hi don't know really if I'm using the right HDAEnabler or not but downloaded HDAEnabler1 from http://www.insanelymac.com/forum/topic/293001-mavericks-realtek-alc-applehda-audio/ and used your AppleHDA8Series v3 and got these 2 errors with fresh 10.9.4 install..

Warning: 'MaximumBootBeepVolume' property NOT found (will show a Sound assertion in: system.log)
Error: 'PinConfigurations property NOT found (may result in unexpected behavior)!

is there different HDAEnabler i could use with my alc892 or should i just ignore the error and proceed with the patch..

I have problems with sound installations in EI capitan 10.11. Can not install sound in all cases.
Please help.

https://www.dropbox.com/s/2pn4kh8yyqlcomb/%E0%B8%9C%E0%B8%A5%E0%B8%AD%E0%B8%AD%E0%B8%81%E0%B8%97%E0%B8%B5%E0%B9%88%E0%B8%9A%E0%B8%B1%E0%B8%99%E0%B8%97%E0%B8%B6%E0%B8%81%E0%B8%82%E0%B8%AD%E0%B8%87%E0%B9%80%E0%B8%97%E0%B8%AD%E0%B8%A3%E0%B9%8C%E0%B8%A1%E0%B8%B4%E0%B8%99%E0%B8%B1%E0%B8%A5?dl=0
Thank you pike

curl -o AppleHDA8Series.sh https://raw.githubusercontent.com/Piker-Alpha/AppleHDA8Series.sh/master/AppleHDA8Series.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 61558  100 61558    0     0  27682      0  0:00:02  0:00:02 --:--:-- 27691

chmod +x AppleHDA8Series.sh
sudo ./AppleHDA8Series.sh -b AppleHDA -b AppleHDAController

Output:

AppleHDA8Series.sh v3.1 Copyright (c) 2013-2015 by Pike R. Alpha 
patched XML files by Toleda and contributors
----------------------------------------------------------------
The supported Realtek ALC codecs for AppleHDA8Series.sh are:

    [1] Realtek ALC  885 (0x10EC0885 / 283904133)
    [2] Realtek ALC  887 (0x10EC0887 / 283904135)
    [3] Realtek ALC  888 (0x10EC0888 / 283904136)
    [4] Realtek ALC  889 (0x10EC0889 / 283904137)
    [5] Realtek ALC  892 (0x10EC0892 / 283904146)
    [6] Realtek ALC  898 (0x10EC0899 / 283904153)
    [7] Realtek ALC 1150 (0x10EC0900 / 283904256)

Please choose the desired codec for the hardware: 6
Do you want to use [1] as the layout-id (y/n)? y
Warning: AppleHDA898.kext already exists. Do you want to overwrite it (y/n)? y
Removing directory ...
Looking in: /System/Library/Extensions/AppleHDA.kext for ConfigData
ConfigData for Realtek ALC 898 found!
------------------------------------------------------------
IUccECFHHUAhRx4RIUcfkCFHDAIhVxwgIVcdECFXHgEhVx8BIWccMCFnHWAhZx4BIWcfASF3HPAhdx0AIXceACF3H0AhhxxAIYcdkCGHHqAhhx+QIZccYCGXHZAhlx6BIZcfAiGnHFAhpx0wIacegSGnHwEhtxxwIbcdQCG3HiEhtx8CIbcMAiHnHJAh5x1hIeceSyHnHwEh9xzwIfcdACH3HgAh9x9AIRcc8CEXHQAhFx4AIRcfQA==
------------------------------------------------------------
Creating AppleHDA898.kext in: /Users/naiclub
Copying AppleHDA ...
Bin-patching AppleHDA ... Done.
Copying AppleHDAController ...
Bin-patching AppleHDAController ...Warning: no match found for: __ZN18AppleHDAController17gfxMatchedHandlerEPvP9IOServiceP10IONotifier
Error: no match found for: __ZN18AppleHDAController18setupHostInterfaceEv
Done.
Done.

Hi,
I tried using your script on a Gigabyte GA-X99-UD4 board with a ALC1150, but it won't install. The output is as follows:

AppleHDA8Series.sh v3.1 Copyright (c) 2013-2015 by Pike R. Alpha
                    patched XML files by Toleda and contributors
----------------------------------------------------------------
The supported Realtek ALC codecs for AppleHDA8Series.sh are:

    [1] Realtek ALC  885 (0x10EC0885 / 283904133)
    [2] Realtek ALC  887 (0x10EC0887 / 283904135)
    [3] Realtek ALC  888 (0x10EC0888 / 283904136)
    [4] Realtek ALC  889 (0x10EC0889 / 283904137)
    [5] Realtek ALC  892 (0x10EC0892 / 283904146)
    [6] Realtek ALC  898 (0x10EC0899 / 283904153)
    [7] Realtek ALC 1150 (0x10EC0900 / 283904256)

Please choose the desired codec for the hardware: 7
Error: ACPI Device (HDEF) {} NOT found!
       ACPI tables appear to be broken and require (manual) patching! 
Aborting ...
Done.

I found a thread where you said to Rename the ALC audio device in your ACPI tables (read DSDT) to HDEF. Could you please help me on how to do that? I never worked with a DSDT, and can't find where to change this field.
Thanks.

This script is always useful for user without bootloader helps to patching kexts. Please take a look my fork, hope you found something useful to merge.

I seen on your blog someone asked about this chipset.
Is this in anyway supported or easily added?

Codec: VIA VT1828S
CodecID: 285 623 361

If you need me to do anything like get info from the device i can as i have one

Kind Regards
Martell

I can see all audio output and input devices, but no sound output.

-deleted-

Sorry Pike

Encountered error when running the script

./AppleHDA8Series.sh: line 270: syntax error near unexpected token (' ./AppleHDA8Series.sh: line 270: printf "AppleHDA8Series.sh v${gScriptVersion} Copyright (c) 2013-$(date "+%Y") by Pike R. Alpha\n"'

I have Realtek ALC 1150 that come with my mother board ASRock Z97 extreme6,
I'm running Yosemite public beta 2
I've tried the 2 method Piker-Alpha AppleHDA8series

1. the script complaining that the kext-dev-mode=1 is not set event though I put it in the boot argument.
2. The AppleHDA1150 kext was installed into S/L/E but it never loaded may be because it never signed. Boot with either kext-dev-mode=1 set or not have no effect.
3. My monitor is connected to ASUS R9 270 graphic card via HDMI and there is no sound from it

It's not a big deal. As always done in the past, in less than 2 minutes I created a new AppleHDA892.kext. But I thought this kext would survive to system update! Did I miss anything? Or maybe not all updates work in the same way.
Zotac Z77 ITX
Intel 3770T
Mavericks 10.9.2
Chameleon v.2377

./AppleHDA8Series.sh -b AppleHDA -b AppleHDAController
layout id 3

Pike,

10.12 testing of v3.6 showed -t replaced -d. Suggestion; if -t set, no need to prompt "Do you want to copy AppleHDA1150.kext to: /System/Library/Extensions? (y/n)" Answer is always no.

Clover patching of AppleHDAController is not working for HD4600 HDMI audio in v3.6. Did something change in recent versions regarding AppleHDAController binary?

Thanks for all your contributions.

If there is any space in the script path, patching fails and ambiguous redirect errors happen as the plist gets generated. Removing spaces in the parent directories solves the problem.

The errors:

Creating symbolic link to AppleHDA ...
./AppleHDA8Series.sh: line 1263: $gInfoPlist: ambiguous redirect
./AppleHDA8Series.sh: line 1264: $gInfoPlist: ambiguous redirect
...(snipped)...
./AppleHDA8Series.sh: line 1317: $gInfoPlist: ambiguous redirect
Done.

Thank you.

Hello,

After sleep there is no sound output anymore.
Normaly i used an EAPD fix for such things on other devices (CodecCommander.kext, EAPDFix.kex) but it seems they are not working if AppleHDA ist not loaded directly.
So would it be possible to implement the EAPD fix directly into your loader?

I'm trying to understand how to properly use your script, and everything seem very clear apart from the example where you're asked about:

Do you want to use [3] as the layout-id (y/n)?

What doe this mean? Can you say a few lines about how to know what to answer there.

Since I'm already here, I'll give you my background to the real issue. I'm trying to understand if your script is the right one to use for enabling audio on 10.9.4 when running as a VirtualBox VM guest on a i7-4710HQ Win8.1 machine. The info I get from OSX is obscure, but since the drivers providing this info via VirtualBox, once we determine the correct codecs/kexts/drivers to use, you will solve an issue that is affecting a huge bunch of VM people, in one go.

The Problem: Windows show this:

Audio Controller Hardware ID: PCI\VEN_8086&DEV_8C20&SUBSYS_11CD1043&REV_05
Audio Codec Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_00000000
DeviceInstanceId: HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_104311CD&REV_1000\4&6BFDCFC&0&0001

Googling around on this, it claims I have a Realtek ALC 1150, however in OSX I get:

# sudo lspci -m -v
Device:   00.05.0
Device:   82801FB (ICH6) High Definition Audio Controller
SVendor:  SigmaTel
SDevice:  Device 7680

# sudo lspci -m -n -vvv
Class:    0403
Vendor:   8086
Device:   2668
SVendor:  8384
SDevice:  7680

which is claiming to be a: STAC9221 HD Audio Codec, from this site. So if they are the same and we can successfully use your script with 1150, we would solve a huge sound issue for VM people on Haswells.

In your script you include usage information for what looks to be all previous versions of your script. It's not really a huge deal but it does cause a little confusion.

if you think about it, there's no reason to include information on how to run old versions of the script because as a user, I'm only retrieving the latest version of your script and therefore I shouldn't see information on how to run anything other than what is currently functional. If users should be able to retrieve and run old versions of your script, you should tag your releases.

Your "Changes" section should be sufficient for documenting changes between new versions of your code. However I'd recommend annotating the bullet points by the version they were added in instead of by the month and year.

Keep up the good work!