Jump to content

AppleALC — dynamic AppleHDA patching

vit9696

By vit9696,
in AppleALC

 Share
5,390 posts in this topic

Recommended Posts

polyzargone
polyzargone
Posted
Posted

Hello.

 

1. Clean (untouched, vanilla) AppleHDA.kext. (Toleda's script modifies it). Replace it.

2. Delete ALL sound patches you mentioned from your config.plist.

3. Delete RealtekALC.kext from EFI/Clover/Kexts

4. Rebuild caches.

5. Put AppleALC.kext into EFI/Clover/Kexts/Other

6. Reboot.

 

Thanks but I already tried that… No way. Still no sound :(.

 

Maybe it wasn't clear in my first post but AppleALC.kext does not work on El Cap/Yos either… But with Clover's patch, it's fine.

Link to comment
Share on other sites
vandroiy2012
vandroiy2012
Posted
Posted

Thanks but I already tried that… No way. Still no sound :(.

 

Maybe it wasn't clear in my first post but AppleALC.kext does not work on El Cap/Yos either… But with Clover's patch, it's fine.

 

Add in bootargs -alcdbg. Boot OS with Debug version of AppleALC.kext. Provide terminal output with command 

cat /var/log/system.log | grep AppleALC

Also verify AppleHDA.kext with this command

codesign --verify --no-strict /System/Library/Extensions/AppleHDA.kext/
Link to comment
Share on other sites
sebinouse
sebinouse
Posted
Posted

Hi guys.

 

There's something I don't get . I have a working ALC888 on Yos/El Cap using Toleda's patch :

Comment : t1-AppleHDA/Resources/xml>zml
Find : 786D6C2E7A6C
Replace : 7A6D6C2E7A6C
Name : AppleHDA

Comment : t1-10.9-10.11-AppleHDA/Realtek ALC888
Find : 8B19D411
Replace : 8808EC10
Name : AppleHDA

Comment : t1-10.11-AppleHDA/Realtek ALC...
Find : 8319D411
Replace : 00000000

Name : AppleHDA

HDEF Layout ID = 1

 

From my understanding, it should work with AppleALC.kext using the patch toleda ALC888 in PinConfig.kexts/Contents/info.plist ?

 

Still, I have no sound even if audio outputs shows in SysPrefs. Isn't the patch supposed to work the same as the one with Clover ?

 

I've attached codec dumps from Linux if it can help :

 

Vendor Id: 0x10ec0888

Revision Id: 0x100202

 

OS X : 10.12 Sierra/EC/Yos

According to the Github Toleda's files are used on Layout 1, 2 and 3 on desktop. Did you tried all three of them ?

 

If not you have to dig inside your working kext and extract the necessary files to create your own codec ...

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

Add in bootargs -alcdbg. Boot OS with Debug version of AppleALC.kext.

Debug version cause boot to hang at this point :

 

 

 

akn1W1e.jpg

 

 

So I used standard 10.11 RELEASE and it worked. But as expected, I can't provide result of cat /var/log/system.log | grep AppleALC

 

Also verify AppleHDA.kext with this command

codesign --verify --no-strict /System/Library/Extensions/AppleHDA.kext/

 

Gives nothing :

 

Core-i5:~ polyzargone$ codesign --verify --no-strict /System/Library/Extensions/AppleHDA.kext
Core-i5:~ polyzargone$
AppleALC.kext is loaded though :

 

Core-i5:~ polyzargone$ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   22    2 0xffffff7f82b88000 0x19000    0x19000    org.netkas.driver.FakeSMC (1410) 5536724F-16D4-33C2-AA7A-F592EACA7DD5 <11 7 5 4 3 1>
   23    0 0xffffff7f82ba1000 0x96000    0x96000    as.vit9696.AppleALC (1.0.11) 99D48FE6-E7DE-3E6B-8FB2-4AD440A8B84E <7 5 4 3 2 1>
   24    0 0xffffff7f82c44000 0x5000     0x5000     org.hwsensors.driver.CPUSensors (1410) 89AB8FDB-1A2C-30A8-B6CE-CB85C92F4B7D <22 7 5 4 3>
   45    0 0xffffff7f82c4c000 0x13000    0x13000    org.hwsensors.driver.LPCSensors (1410) 4A526B40-A4F0-369C-A67C-2DD8FEE6640D <22 12 11 7 5 4 3>
   50    0 0xffffff7f82c84000 0x3a000    0x3a000    com.insanelymac.RealtekRTL8111 (2.0.0) 54A33BAE-C115-361F-A956-7FFE91E04329 <49 12 5 4 3 1>
  112    2 0xffffff7f80f9b000 0x327000   0x327000   com.nvidia.web.NVDAResmanWeb (10.1.3) 6270A38C-42A6-3ECD-B890-39D090AD5970 <111 103 86 12 7 5 4 3 1>
  113    0 0xffffff7f812d5000 0x1bd000   0x1bd000   com.nvidia.web.NVDAGK100HalWeb (10.1.3) 7CD4ED06-226E-3485-9718-057240871F75 <112 12 4 3>
  117    0 0xffffff7f81fba000 0x9a000    0x9a000    com.nvidia.web.GeForceWeb (10.1.3) 2F9A2E0A-FAC6-3644-B070-B7AE811402E9 <116 112 103 86 12 7 5 4 3 1>
  131    0 0xffffff7f82cbe000 0x29000    0x29000    org.pqrs.driver.Karabiner (10.20.0) 56226F4F-1BF5-3173-901E-F4DCF85059B5 <35 5 4 3 1>
  135    0 0xffffff7f820a9000 0x2000     0x2000     com.nvidia.CUDA (1.1.0) 5AFE550D-6361-3897-912D-897C13FF6983 <4 1>
@Sebinouse

 

I tried all 3 layouts. No difference, still no sound.

 

As for building my own codec, well I think I'll wait for an updated Clover patch from Toleda… If any :).

Link to comment
Share on other sites
vit9696
vit9696
Posted
  • Author
Posted (edited)

polyzargone,  AppleALC works just fine with ALC1150 in 10.11. I have this codec.

macOS 10.12 is currently for gurus and developers, therefore has a lot of bugs.

ALC1150 issues in 10.12 might be due to the unnecessary null patches, see the one with MinKernel 16. Revert the file to the previous revision and give it a try.

Edited by fantomas1
  • Like 3
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

polyzargone,  AppleALC works just fine with ALC1150 in 10.11. I have this codec.

macOS 10.12 is currently for gurus and developers, therefore has a lot of bugs.

ALC1150 issues in 10.12 might be due to the unnecessary null patches, see the one with MinKernel 16. Revert the file to the previous revision and give it a try.

 

I can confirm AppleALC works with ALC892 in both Sierra and El Capitan. Which was a really nice surprise, from my point of view. So thank you for that. Having the AppleHDA.kext untouched does bring a few advantages. So yeah, nice job, in my opinion.

 

Vit9696, I'm gonna need your support to debug my work PC (using ALC1150) in El Capitan, especially since you're using the same codec. It's been driving me crazy ever since I replaced my work PC. So if you're ok with that, let's focus on the positive and, most importantly, useful things. :)

Edited by fantomas1
  • Like 1
Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted (edited)

polyzargone, AppleALC works just fine with ALC1150 in 10.11. I have this codec.

macOS 10.12 is currently for gurus and developers, therefore has a lot of bugs.

ALC1150 issues in 10.12 might be due to the unnecessary null patches, see the one with MinKernel 16. Revert the file to the previous revision and give it a try.

 

I'm NOT talking about ALC1150 but ALC888 !

 

And whatever you think about people installing beta software and testing them, the fact is the Clover patch works where your kext does not. Also, I mentioned that it does not in El Cap and Yos either so it's not a matter of beta software or not.

 

Lastly, keep in mind that macOS Sierra Public beta will be available to everyone starting next July and I'm curious to know what you'll answer to those who'll have the same issue at this moment.

Guys, this is no place to fight. :) Come on.

 

I want to say that I have no problem with AppleALC.kext on other rigs so I'm just trying to figure out why it does not work on this particular system.

 

I also think that AppleALC.kext is a wonderful piece of work and I'm just hoping it will work flawlessly for everyone :).

Edited by fantomas1
  • Like 1
Link to comment
Share on other sites
vit9696
vit9696
Posted
  • Author
Posted (edited)
Vit9696, I'm gonna need your support to debug my work ALC1150 in El Capitan, especially since you're using the same codec. It's driving me crazy ever since I replaced my work PC. So if you're ok with that, let's focus on the positive and, most importantly, useful things.  :)

 

Check #587 please, I think https://github.com/vit9696/AppleALC/blob/29baac6e88139ad5c66e81f3fd8a5f30f063db8c/Resources/ALC1150/Info.plistmight work for you.

Edited by fantomas1
  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)

One thing I had to make double sure I got right, is to have the native AppleHDA kext. I extracted mine from the installer, using Pacifist. :D Pretty cool method. I didn't know about it. :) After that, I just cleared my KextsToPatch section from config, and let the Inject Layout ID = 1 in Devices. I also unchecked the Reset HDA checkbox, just in case.

 

Now, in your case, I would say...but I could be very well wrong, that it might be either something particular to your system (hardware-wise) or...maybe just a messed up config. Happened to me before. :)) So yeah... one messed up config can cause a lot of frustration. Also, when you've got hardware that no one else has, that can be also a big pain in the butt.

Edited by fantomas1
  • Like 2
Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted (edited)

One thing I had to make double sure I got right, is to have the native AppleHDA kext. I extracted mine from the installer, using Pacifist. :D Pretty cool method. I didn't know about it. :) After that, I just clearedn my KextToPatch section from config, and let the Inject Layout ID = 1 in Devices. I also unchecked the Reset HDA checkbox, just in case.

 

Now, in your case, I would say...but I could be very well wrong, that it might be either something particular to your system or...maybe just a messed up config.

I'm 100% sure the AppleHDA.kext is untouched. Never applied any script on it.

 

Also, that's the command codesign --verify --no-strict /System/Library/Extensions/AppleHDA.kext tends to confirm (correct me if I'm wrong).

 

Edited by fantomas1
  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

One thing I had to make double sure I got right, is to have the native AppleHDA kext. I extracted mine from the installer, using Pacifist. :D Pretty cool method. I didn't know about it. :) After that, I just cleared my KextsToPatch section from config, and let the Inject Layout ID = 1 in Devices. I also unchecked the Reset HDA checkbox, just in case.

 

Now, in your case, I would say...but I could be very well wrong, that it might be either something particular to your system (hardware-wise) or...maybe just a messed up config. Happened to me before. :)) So yeah... one messed up config can cause a lot of frustration. Also, when you've got hardware that no one else has, that can be also a big pain in the butt.

Still not work? El capitan work and sierra not work right?

 

If your in case above, first you use flytopatch + layoutid+dummyfile. Then all check in el and sie. If Both are work, you make applealc for your codec. Edit info, xml.zlib etc follow instruction applealc by youself. Then report AppleALC. I'm using AppleALC builded by myself after Dummyfile is tested.

 

나의 LG-F410S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
insanelyDeepak
insanelyDeepak
Posted
Posted

@InsanelyDeepak --  re: ALC891  --  Let's continue conversation here so mailbox doesn't fill up :)

 

THANK YOU!! :)   & Let me know what you want me to test next.

 

Summary: my testing finds speakers work with both V1 and V2 of your AppleHDA kexts.

 

hello 

this will be kinda off topic , this thread is only related to AppleALC which only supports working Patches for now ALC891 don't have it , my first proves in couple of testing version you will get your working AppleHDA then we can request @vt9696 or @vandroiy2012 to add your codec to list , untill we have to clean the thread so PM will sufficient for you 

  • Like 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

@All

I do believe that the new patch may not be needed for all the codecs in Sierra. Everybody having issues is supposed to report it here or (better) on github so that it does not get lost.

 

Audio not working in macOS Sierra DP for ALC283 with latest 8A19D411 nulling patch

 

 

        <dict>

            <key>Count</key>

            <integer>2</integer>

            <key>Find</key>

            <data>ihnUEQ==</data>

            <key>MinKernel</key>

            <integer>16</integer>

            <key>Name</key>

            <string>AppleHDA</string>

            <key>Replace</key>

            <data>AAAAAA==</data>

        </dict>

 

 

1. Laptop model/Motherboard model: Intel NUC6i5SYH

2. Codec name: Realtek ALC283

3. Layout used with the info what works for you (ideally if you try them all): 3

4. OS X versions you tried: 10.11.4, 10.11.5, 10.12DP

5. Working with nulling patch removed

     Info.plist attached

Info.zip

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

@Vit9696, for ALC1150, I think I've got everything set up properly. The AppleHDA kext is the native one now. Also, I removed all the patches from config and added layout id =1. So..in theory, it should work. Still, it kinda doesn't...

 

Can I help you with some information to debug this case? Maybe the hardware is slightly different from what you have. Just saying.

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

@Vit9696

 

AppleALC works with ALC888 with Sierra/EC/Yos… :thumbsup_anim:

 

Well, sort of (at least with my setup) because the strange thing is that in order to have sound, I have to enter sleep mode first then it's fine. Otherwise, I have no sound at all after boot.

 

That's why I was thinking there was a problem with the patch but it appears that's something else.

 

Any hint on this ?

 

Thanks.

  • Like 1
Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

I know applying broad strokes isn't a good idea, but it seems that the laptop Realtek chipsets (ALC2xx) don't require the 8A19D411 null patch, while the desktop (ALC8xx) ones do.

 

Maybe removing it from all of the ALC2xx patch lists would work? Has anyone needed it to get an ALC2xx working yet?

Link to comment
Share on other sites
insanelyDeepak
insanelyDeepak
Posted
Posted

@vt9696 in every couple of restart I receive KP due AppleALC 

 

Here are log files KernelPanic_Log.zip

 

Can you tell why this happens ??? 


I know applying broad strokes isn't a good idea, but it seems that the laptop Realtek chipsets (ALC2xx) don't require the 8A19D411 null patch, while the desktop (ALC8xx) ones do.

 

Maybe removing it from all of the ALC2xx patch lists would work? Has anyone needed it to get an ALC2xx working yet?

Reported to Dev at post #590

Link to comment
Share on other sites
vit9696
vit9696
Posted
  • Author
Posted

@insanelydeepak, even though I cannot be sure without keepsyms=1 in boot-args to get a proper panic log, the issue looks very similar to the one Riley Freeman has. I think the best way is to wait for new DPs. As a workaround you could use -v -alcdbg arguments which reduce the chance of a panic.

Link to comment
Share on other sites
sebinouse
sebinouse
Posted
Posted

I know applying broad strokes isn't a good idea, but it seems that the laptop Realtek chipsets (ALC2xx) don't require the 8A19D411 null patch, while the desktop (ALC8xx) ones do.

 

Maybe removing it from all of the ALC2xx patch lists would work? Has anyone needed it to get an ALC2xx working yet?

I own a i5-4250u Intel NUC with ALC283.

 

I didn't manage to get AppleALC.kext to work properly with Audio IN and OUT on macOS12.

 

I'm using  an injector with zero patch for 8A19D411 and both work.

Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted

Salut sebinouse, I also have the same NUC you have (followed your excellent guide) with Intel Core i5-4250U and ALC283, still not working.

Can you share the 8A19D411 null patch, or what you refer to as injector with zero patch for 8A19D411?

Any other solutions and ideas are welcome, guys... Many thanks.

Link to comment
Share on other sites
Micky1979
Micky1979
Posted
Posted

Salut sebinouse, I also have the same NUC you have (followed your excellent guide) with Intel Core i5-4250U and ALC283, still not working.

 

Can you share the 8A19D411 null patch, or what you refer to as injector with zero patch for 8A19D411?

 

Any other solutions and ideas are welcome, guys... Many thanks.

is not in the range comparisons so no null patch for 8A19D411 is needed. (at least can work because does nothing, but it's useless)

 

You have to zeroing <8508ec10> and then replace <8419d411> with <8302ec10> .

this for Sierra.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...