Jump to content

AppleALC — dynamic AppleHDA patching

vit9696

By vit9696,
in AppleALC

 Share
5,371 posts in this topic

Recommended Posts

Genxster
Genxster
Posted
Posted
 
I suppose mic input is activate...
283318535_Capturedcran2018-07-0810_14_45.png.00b779cdaa740cc25df75a2106742062.png
I mean ,when I talk like whispering ,it recognise some of words not all ,BTW mic is working fine as in Windows with QuickTime recorder and other apps ,just not here.so mic is turned on for Siri too

Sent from my Redmi Note 3 using Tapatalk

  • Like 1
Link to comment
Share on other sites
Genxster
Genxster
Posted
Posted
[mention=1956897]Genxster[/mention]

 

On my system, I've also activate Dictation for Siri work correctly.

 

 

 

1978799650_Capturedcran2018-07-0810_21_58.png.87f49165a5e8480bb00f598f8531ec4f.png

Dictation etc already tried to turn on and off ,thanks for you support

 

Sent from my Redmi Note 3 using Tapatalk

 

 

 

  • Like 1
Link to comment
Share on other sites
kaoskinkae
kaoskinkae
Posted
Posted 
After trying the latest versions of applealc and lilu for my vt2021 sound chip and tested if the kext are loaded correctly it does not work with mojave but with earth. Look at my data about my team.

 

 

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)
16 hours ago, twsps said:

No codeccommander in /L/E

 

Use codeccommander in \L\E and move all the kext into Clover\Kexts\Other except BrcmFirmwareRepo.kext, it will be the best choice.

 

16 hours ago, twsps said:

Update: Without PluginType=True and the right id injection, it will cause kernel panic. Which means, it won't cause kp when its not selecting the correct inject id for ALC295.

 

If you do it and you have KP, maybe other missing thing will cause the KP, normal or if you inject 1.

 

Now for the config.plist, i just managed it to only have the requirements, and removed inject-plugin type because of the new way on the MBP 14,x's and Apple's latest Mac's, so you can use the attached CpuSsdt in the patched folder. For your knowledge, you can go here, download the MacBook Pro 14,1 dump, and check the ACPI files like DSDT for example, find _DSM's method and add them to your DSDT but think that you have to remove the existing one's and drop them again in config.plist, to properly emulate your hack with Apple Hardware, check also the SSDT-10. You can remove XOSI things from config and patched and just add Darwin into \_OSI "simple way" because of DELL use AMI not like HP that use's it's own, you can also merge directly the SSDT's from patched into DSDT except CpuSsdt, use the help of IOREG to locate your devices infos and Apple devices infos, you can add also "compatible" into _DSM for more OS flexibility.

 

16 hours ago, twsps said:

For the reason why others won't have this issue, I believe this is specifically for my codec ALC295

 

I don't believe that sorry, it's not related to the ALC295 IMHO, because sometimes the problems come from the things that we didn't think about

 

So here's the attached files, but you also can create topic here in laptop/dell or in OSXLatitude forums, you'll have @Jake Lo and @Hervé, they solved all the issues that i had with this E7440, now it works on all apple's OS, without even changing something beside Clover it self.

config.plist

CpuSsdt_amd:dsl.zip

Your Clover:Others.zip

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

For anyone wondering how to patch their own codec (or in my case, add a new Layout to an existing one for better compatibility with my board), I'm gonna tell you this: when you start to understand something like this, a tutorial like this suddenly becomes a walk in the park for you. :)) That is definitely not for the faint of heart. And for someone with 0 knowledge of these things, it's hard.

But knowledge is something you get over time. And I was crazy enough to try.

 

Will see how it goes.

Edited by arsradu
  • Like 2
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

@twsps

 

I've found in the MBP 14,1 DSDT file the presence of an _DSM in the (HDEF), this wasn't present in the previous generations, and maybe this will going to make difference, but i'm not 100% sure unless you give it a try:

 

Spoiler 

Device (HDEF)
            {
                Name (_ADR, 0x001F0003)  // _ADR: Address
                OperationRegion (HDAR, PCI_Config, Zero, 0x60)
                Field (HDAR, WordAcc, NoLock, Preserve)
                {
                    VID0,   16, 
                    DID0,   16
                }

                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If (Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b"))
                    {
                        If ((VID0 & 0xFFFF) != 0xFFFF)
                        {
                            Local0 = Package (0x04)
                                {
                                    "hda-gfx", 
                                    Buffer (0x0A)
                                    {
                                        "onboard-1"
                                    }, 

                                    "hda-idle-support", 
                                    Buffer (0x02)
                                    {
                                        "1"
                                    }
                                }
                            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                            Return (Local0)
                        }
                    }

                    Return (0x80000002)
                }
            }

 

 

So that said, this "hda-idle-support"=1 still don't know if it will make difference, but I'm sure here it's meaning is "Enabled idle support", if so, by trying it in your DSDT or just using an external _DSM in SSDT and worked for you, by letting the CPU using the idle, you'll be right by saying:

 

18 hours ago, twsps said:

For the reason why others won't have this issue, I believe this is specifically for my codec ALC295

 

Curiously, i was just looking into the DSDT of that MBP 14,1 to see what's the difference between the old and recent ACPI code, because from time to time i do that, and found it, because i'm sure in the previous generations, HDEF device section are empty!

 

Hope this to make the difference

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

Ok, so first attempt was a no-go. :)) I guess I might be missing something. And the newly added Layout ID 12, doesn't seem to work either. Not sure if it works for anyone. It doesn't work with the official version either.

 

So here's what I managed to get done so far: 

  • I chose Layout ID 30. No particular reason for that. But I couldn't find a pattern for the naming.... Any suggestions?
  • Added Layout30 and Platforms30 xml and zlib files to ALC892 folder.
  • Added Layout ID to ALC892 Info.plist (Item 8)

You can see the actual layout of my ports (and Paths Map). I'm not yet sure how to tell which one will show up as "Internal Speaker" or "Headphone".

Also, I re-attached the linux codec dump, for reference.

 

Also, there are a few things in the Layout ID xml which are not really clear to me... Such as MuteGPIO values. Where are those values taken from? Are they mandatory?

 

Anyway, if someone (preferably a dev) can take a look at what I've done so far and tell me what did I miss (cause I have no inputs/outputs whatsoever in System Preferences -> Sound), that would be awesome.

 

Thank you! :)

 

layout30.xml

Platforms30.xml

ConvertedNodeID

PathMaps

codec_dump_card1(ALC892).txt

PinDefaults & Verbs

Info.plist

Edited by arsradu
  • Like 2
Link to comment
Share on other sites
twsps
twsps
Posted
Posted
4 hours ago, ammoune78 said:

@twsps

 

I've found in the MBP 14,1 DSDT file the presence of an _DSM in the (HDEF), this wasn't present in the previous generations, and maybe this will going to make difference, but i'm not 100% sure unless you give it a try:

 

  Hide contents 


Device (HDEF)
            {
                Name (_ADR, 0x001F0003)  // _ADR: Address
                OperationRegion (HDAR, PCI_Config, Zero, 0x60)
                Field (HDAR, WordAcc, NoLock, Preserve)
                {
                    VID0,   16, 
                    DID0,   16
                }

                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If (Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b"))
                    {
                        If ((VID0 & 0xFFFF) != 0xFFFF)
                        {
                            Local0 = Package (0x04)
                                {
                                    "hda-gfx", 
                                    Buffer (0x0A)
                                    {
                                        "onboard-1"
                                    }, 

                                    "hda-idle-support", 
                                    Buffer (0x02)
                                    {
                                        "1"
                                    }
                                }
                            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                            Return (Local0)
                        }
                    }

                    Return (0x80000002)
                }
            }

 

 

So that said, this "hda-idle-support"=1 still don't know if it will make difference, but I'm sure here it's meaning is "Enabled idle support", if so, by trying it in your DSDT or just using an external _DSM in SSDT and worked for you, by letting the CPU using the idle, you'll be right by saying:

 

 

Curiously, i was just looking into the DSDT of that MBP 14,1 to see what's the difference between the old and recent ACPI code, because from time to time i do that, and found it, because i'm sure in the previous generations, HDEF device section are empty!

 

Hope this to make the difference

Hey,

Thanks for the idea here, how would I add this section of code into DSDT? I tried with patch in MaciASL but I can't apply, or how would I use an external _DSM SSDT?

 

Help is appreciated. Thanks

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
[mention=1581907]twsps[/mention]
 
I've found in the MBP 14,1 DSDT file the presence of an _DSM in the (HDEF), this wasn't present in the previous generations, and maybe this will going to make difference, but i'm not 100% sure unless you give it a try:
 
Spoiler 
Device (HDEF){Name (_ADR, 0x001F0003)  // _ADR: AddressOperationRegion (HDAR, PCI_Config, Zero, 0x60)Field (HDAR, WordAcc, NoLock, Preserve){                   VID0,   16,                    DID0,   16}Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method{If (Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")){If ((VID0 & 0xFFFF) != 0xFFFF){Local0 = Package (0x04){"hda-gfx", Buffer (0x0A){"onboard-1"}, "hda-idle-support", Buffer (0x02){"1"}}                           DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))Return (Local0)}}Return (0x80000002)}}

 
 
So that said, this "hda-idle-support"=1 still don't know if it will make difference, but I'm sure here it's meaning is "Enabled idle support", if so, by trying it in your DSDT or just using an external _DSM in SSDT and worked for you, by letting the CPU using the idle, you'll be right by saying:
 
 
Curiously, i was just looking into the DSDT of that MBP 14,1 to see what's the difference between the old and recent ACPI code, because from time to time i do that, and found it, because i'm sure in the previous generations, HDEF device section are empty!
 
Hope this to make the difference

Although I still don't get how do I put this code into DSDT, I tried with MacBook Pro 11,1, and it turns out it's the same problem. I would still like to try if your method will work out
Thanks

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
9 hours ago, ammoune78 said:

 

Use codeccommander in \L\E and move all the kext into Clover\Kexts\Other except BrcmFirmwareRepo.kext, it will be the best choice.

 

 

If you do it and you have KP, maybe other missing thing will cause the KP, normal or if you inject 1.

 

Now for the config.plist, i just managed it to only have the requirements, and removed inject-plugin type because of the new way on the MBP 14,x's and Apple's latest Mac's, so you can use the attached CpuSsdt in the patched folder. For your knowledge, you can go here, download the MacBook Pro 14,1 dump, and check the ACPI files like DSDT for example, find _DSM's method and add them to your DSDT but think that you have to remove the existing one's and drop them again in config.plist, to properly emulate your hack with Apple Hardware, check also the SSDT-10. You can remove XOSI things from config and patched and just add Darwin into \_OSI "simple way" because of DELL use AMI not like HP that use's it's own, you can also merge directly the SSDT's from patched into DSDT except CpuSsdt, use the help of IOREG to locate your devices infos and Apple devices infos, you can add also "compatible" into _DSM for more OS flexibility.

 

 

I don't believe that sorry, it's not related to the ALC295 IMHO, because sometimes the problems come from the things that we didn't think about

 

So here's the attached files, but you also can create topic here in laptop/dell or in OSXLatitude forums, you'll have @Jake Lo and @Hervé, they solved all the issues that i had with this E7440, now it works on all apple's OS, without even changing something beside Clover it self.

config.plist

CpuSsdt_amd:dsl.zip

Your Clover:Others.zip

Ok, I managed to add that HDEF code into my DSDT with no errors, but it's still having the same issue. Here I attached my edited DSDT.

DSDT.aml

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)

Did you tried the files suggested from the previous post for that config, kexts and CpuSsdt? Because it is from your previously uploaded clover folder, so i patched your CpuSsdt, did some changes into that config and asked you to move the whole kexts from \L\E to Other folder inside clover.

 

2 hours ago, twsps said:

Ok, I managed to add that HDEF code into my DSDT with no errors, but it's still having the same issue. Here I attached my edited DSDT.

DSDT.aml

 

No, you have to know that your Device HDAS is already renamed to HDEF by using clover AcpiPatcher, adding another device that have the same name is not appreciated using the same location address:

Name (_ADR, 0x001F0003) // _ADR: Address. The other thing is that the HDAS device has it's own _DSM, by adding the _DSM into the other HDEF will make confusion. Did you done any patches to that DSDT, because if you're using DSDT you need to apply some fixes the begin patching with _DSM and \_OSI. Also copy paste from other ACPI tables of different hardware into your tables is a bad thing, because it's a code and layout that is different from Bios revision to another one and from manufacturer to another.

 

I'll upload here DSDT with only HDAS>_DSM "Layout-ID 28", BUS0, IMEI, MCHC, Enable GPIO Controller and \_OSI, a complete one need more time, because I have to look into the MBP 14,1 and need also your IOREG.  

DSDT.aml

Edited by ammoune78
  • Like 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
hello,there is a problem when I compiled AppleALC-1.2.8 with Lilu-1.2.4,,the xcode throw a error,
111.thumb.jpg.562f21467b3e3b04b652ef4ead646805.jpg
 
I wonder has anyone encountered this problem?
Lilu 1.2.5 and AppleALC 1.3.0 are available to be built from source. Try them, make sure you have debug Lilu.kext in AppleALC folder before building

Sent from my SM-G930F using Tapatalk

  • Like 2
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted (edited)
28 minutes ago, Master1024 said:

hello,there is a problem when I compiled AppleALC-1.2.8 with Lilu-1.2.4,,the xcode throw a error

 

I wonder has anyone encountered this problem?

 

  • Download BOTH Lilu sources and AppleALC sources.
  • Build Lilu first.
  • Copy the resulting Lilu DEBUG kext into the AppleALC folder.
  • Build AppleALC
Edited by arsradu
  • Like 1
Link to comment
Share on other sites
Master1024
Master1024
Posted
Posted
1 hour ago, SavageAUS said:

Lilu 1.2.5 and AppleALC 1.3.0 are available to be built from source. Try them, make sure you have debug Lilu.kext in AppleALC folder before building 

Sent from my SM-G930F using Tapatalk
 

ok，thanks，it ok

56 minutes ago, arsradu said:

 

  • Download BOTH Lilu sources and AppleALC sources.
  • Build Lilu first.
  • Copy the resulting Lilu DEBUG kext into the AppleALC folder.
  • Build AppleALC

ok，thanks，it ok

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
Did you tried the files suggested from the previous post for that config, kexts and CpuSsdt? Because it is from your previously uploaded clover folder, so i patched your CpuSsdt, did some changes into that config and asked you to move the whole kexts from \L\E to Other folder inside clover.
 
 
No, you have to know that your Device HDAS is already renamed to HDEF by using clover AcpiPatcher, adding another device that have the same name is not appreciated using the same location address:
Name (_ADR, 0x001F0003) // _ADR: Address. The other thing is that the HDAS device has it's own _DSM, by adding the _DSM into the other HDEF will make confusion. Did you done any patches to that DSDT, because if you're using DSDT you need to apply some fixes the begin patching with _DSM and \_OSI. Also copy paste from other ACPI tables of different hardware into your tables is a bad thing, because it's a code and layout that is different from Bios revision to another one and from manufacturer to another.
 
I'll upload here DSDT with only HDAS>_DSM "Layout-ID 28", BUS0, IMEI, MCHC, Enable GPIO Controller and \_OSI, a complete one need more time, because I have to look into the MBP 14,1 and need also your IOREG.  
DSDT.aml
I tried all your files completely, but now clover doesn't recognize any disk. So I can't boot in macOS right now

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
I tried all your files completely, but now clover doesn't recognize any disk. So I can't boot in macOS right now

Sent from my MHA-AL00 using Tapatalk



Have you removed apfs.efi from the drivers folder, or you see the disks but black screen or just stay at Apple logo?


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

But i see now, with the new DSDT you have to remove xsid and xosi from the config plist and also ssdt-xosi from patched
I changed csractiveconfig to 0x67 and injectkexts=yes, added -xcpm to boot-args and change SAT0 to SATA, set apsn and aplf to true.

So maybe injectkexts in that added options don’t let you boot, just set it to detect if you want you can keep csractiveconfig to 3


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

Also set drop OEM DSM in the config to true for all devices, i think you didn’t read my whole posts?


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
Also set drop OEM DSM in the config to true for all devices, i think you didn’t read my whole posts?


Sent from my iPhone using Tapatalk
I use your config plist. So do I still need to change drop OEM DSM on my own?

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
I use your config plist. So do I still need to change drop OEM DSM on my own?

Sent from my MHA-AL00 using Tapatalk


Yes because of new DSDT, from the skylake builds to up, all OEM Manufacturers added in each device it’s own _DSM, so if you delete one of them and replaced it by another, you absolutely have to use drop OEM DSM of that device, otherwise the system will not boot, you’ll have acpi error in verbose


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
twsps
twsps
Posted
Posted

Yes because of new DSDT, from the skylake builds to up, all OEM Manufacturers added in each device it’s own _DSM, so if you delete one of them and replaced it by another, you absolutely have to use drop OEM DSM of that device, otherwise the system will not boot, you’ll have acpi error in verbose


Sent from my iPhone using Tapatalk
If I use your config, no disk will be recognized in clover, which means I can't boot in any OS. If I replace to my own config, clover will recognize my disk. I checked your config plist that you've provided to me, but you have changed a lot, would you mind to tell me what are the necessary ones?
Thanks

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
9 minutes ago, twsps said:

If I use your config, no disk will be recognized in clover, which means I can't boot in any OS. If I replace to my own config, clover will recognize my disk. I checked your config plist that you've provided to me, but you have changed a lot, would you mind to tell me what are the necessary ones?
Thanks

Sent from my MHA-AL00 using Tapatalk
 

 

Ok, let's start with your config, put the CpuSsdt i uploaded in the patched folder, remove plugin-type from the config and under ACPI Drop Tables add the following to the existing one:

 

Spoiler 

		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>

 

 

And see if you can boot, then we will do another steps!

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
6 minutes ago, ammoune78 said:

 

Ok, let's start with your config, put the CpuSsdt i uploaded in the patched folder, remove plugin-type from the config and under ACPI Drop Tables add the following to the existing one:

 

  Hide contents 


		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>

 

 

And see if you can boot, then we will do another steps!

Yes, I can successfully boot in, using id=13. Here I attached files for you to check.

Thanks.

Step 1.zip

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