Audio Codec: 0X10EC1168 / Realtek ALCS1200A

[unecc]

Hi i can't ear audio. can someone help me what i can do??

I'm using AppleALC.kext v.1.9.5

alcid=15 (i don't know if it's right)

0X10EC1168 is not in this list https://github.com/acidanthera/AppleALC/wiki/Supported-codecs

 

[Edhawk]

Your motherboard uses the Realtek S1220A audio codec, which is supported by AppleALC.kext, since release 1.9.3, using layout-id = 15.

Which speakers are you using?
How are you connecting the speakers?
Are they connected via the ‘Green’ coloured audio port?

 

[unecc]

Thanks edhawk, I answer to all questions:

- yes, i know, in my config.plist AppleALC.kext 1.9.5 is on, layout-id = 15 is configurated in boot arg. When i boot i can see in/out in audio settings but can't increase/decrease. line is gray. I've to add the pci address?

- i'm using rear port (green). it's the main stereo out.

- speaker works in windows and debian too. it works!


in SMBIOS i've used "iMacPro1,1" i read that's better for my cpu.

 

[Edhawk]

If you have the correct layout-id used in the alcid boot argument you do not want a conflicting/incorrect entry for the same device in the DeviceProperties section of your config.plist.

I would recommend that you delete the audio DeviceProperties entry from your config.

Why aren’t you enabling WhateverGreen.kext? The agdpmod=pikera boot agreement is reliant upon WhateverGreen to work with your Navi GPU.

If you are not using a Broadcom Bluetooth device you should remove the unused kexts from your /EFI/OC/Kexts folder and config.plist, same goes for any other unused kexts.

 

[unecc]

-No i don't use Broadcom BT devices i've inside a intel Dual Band Wireless-AC 7265 that i read that doesn't works. i will buy a fv-T919.

- This is EFI of @ccphuc. DP/PCIlist, ACPI and USBMAP are his! I've change smbios (to imac1,1 he use 7,1).


update1:
activated whateverGreen.kext also if 5700XT works ootb 4K, Metal3 and dual monitor.
This shot is before activate whateverGreene.kext

This is after activated whatevergreen, is identical i think that less kext is better (?)


------------

update2: removed not used kext


update3: 2 address for audio device that i has insert inside are removed

in original ccphuc file there is also this for audio in UEFI, i've to remove?






Problems

• audio still not works;
• when i try shutdown, it reboots! I'm sure that before i can do it, i don't know before what :'(
• USB works fine but the keyboard for waking up at boot i've to digit some button for wake up, need some secondo for doing it.
• USBC of motherbord not works

 

[Edhawk]

Post a copy of your current EFI folder so we can see exactly what you are using. Just delete the serial number from the config.plist before posting the copy here.

Also post a screenshot of the Hackintool > PCIe tab, with all the info shown within the PCIe window, ie expand the Hackintool app to fill the screen so the IOReg Name and Device Path columns can be clearly seen in the screenshot.

 

[Edhawk]

If you tried any other audio ‘fixes’ such as using VoodooHDA.kext, did you make sure to remove them, once you knew they hadn’t worked?

 

[unecc]

Thanks for your answer.
- Yes, in past i've installed Vodoohda.pkg (so VoodoHDA.kext+pref.panel), but not works for me. For ccphuc i read that for him works.

 

[unecc]

i think that PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4) i can delete because i've no devices with that path.
I repeat: these are path of an other user that has mainboard (i think) the same of mine.
I've ASUS X570 PRIME PRO

PRIME X570-PRO - Specifiche Generali｜Schede Madri｜ASUS Italia

Specifiche dettagliate di PRIME X570-PRO Specifiche Generali，CPU:AMD AM4 Socket 3rd and 2nd AMD Ryzen™/2nd and 1st Gen AMD Ryzen™ with Radeon™ Vega Graphics Processors,* Refer to <a href="http://www.asus.com">www.asus.com</a> for CPU support list,* Due to CPU limitation, CPU cores supported...

www.asus.com

He's ASUS X570 PRO/CSM

https://www.asus.com/motherboards-components/motherboards/prime/prime-x570-pro-csm/

Problems

• audio still not works;
• when i try shutdown, it reboots! I'm sure that before i can do it, i don't know before what :'(
• USB works fine but the keyboard for waking up at boot i've to digit some button for wake up, need some secondo for doing it.
• USBC of motherbord not works

 

[ccphuc]

you can not take my EFI to use for your system. did not read carefully then start building EFI following youtube video

Buid EFI on Windows:

GitHub - lzhoang2801/OpCore-Simplify: A tool designed to simplify the creation of OpenCore EFI

A tool designed to simplify the creation of OpenCore EFI - lzhoang2801/OpCore-Simplify

github.com

Sound RealTek ALC S1220A boot arg alcid=15 + AppleALC.kext 1.9.6 dev :

https://olarila.com/topic/43035-how-to-enable-audio-in-macos-tahoe-with-mykextinstaller/

Realtek

ALCS1220A

0x100101, 0x100003, bố cục 1, 2, 3, 5, 7, 8, 11, 13, 15, 20, 21, 99

SMBios MacPro 7.1 for Tahoe beta 3.

How to Fix Intel WiFi and Bluetooth on macOS Sequoia, Tahoe Beta | Hackintosh | Step By Step Guide​

Did you follow all the instructions and videos?

 

[unecc]

Sound RealTek ALC S1220A boot arg alcid=15 + AppleALC.kext 1.9.6 dev : according to the instructions Olarila
https://olarila.com/topic/43035-how-to-enable-audio-in-macos-tahoe-with-mykextinstaller/

SMBios MacPro 7,1 for Tahoe beta 3.

You are the one who does not research carefully and then asks ???!!!

dear @ccphuc this is my 3th day with this problems. I'm a newbie girl ;-) and all tutorials i watch are in English, that's not my motherlanguage. Now i'm not using TAHOE because was too difficult for me. I'm in SEQUOIA now.

Be patient, because you've been a rookie in the past too. Don't offend me, because I didn't do anything to you.
I'm struggling with my strength to understand.

 

[ccphuc]

video, there is a tutorial for those who are not good at English, use google translate, language is not the problem

 

[unecc]

it's all new as you would. I reboot

 

[Edhawk]

Try this cleaned up EFI folder based on OC 1.0.5 (Release) with the latest AMD Vanilla Patches for Tahoe.

I have made a few changes to your EFI when creating this new one.

1. Edited the SSDT-USB-Reset.aml table to correct the IOReg Names shown in the SSDT, so they match those shown in the screenshot you posted.
2. Removed NVMeFix.kext - it as disabled anyway.
3. Edited the USBMap.kext/Contents/Info.plist so it uses the iMacPro1,1 SMBIOS to match the SMBIOS data in your config.plist.
4. Replaced the AMD Kernel Patches to the latest version, as your current config doesn't use the newest set.
5. Removed the DeviceProperties entries from the config.plist, as I don't believe they are correct.
6. Made sure all the Drivers, Tools etc, in the EFI folder are from the same OC release.
7. Made a few other edits in the config.plist to keep in line with the Dortania OC Ryzen guide.

Try this revised EFI on a spare USB pen Drive and let me know how it works or if you ran in to issues using the EFI.

Other issues:
From the Hackintool Screenshot you posted I can see that you have 7 x devices with 'pci-bridge@x' entries in the IOReg Name. This will prevent these devices from being correctly identified by macOS. See edited entries in the screenshot below.

7 x Devices with 'pci-bridge' entries that need fixing.

To fix these issues you need to generate one or more (possibly 3) SSDT's using Corpnewt's SSDTTime script and your system DSDT.aml. I can help with this if you are not sure what is required, as I have had to do the same for a few of my AMD systems.

Post a copy of your system DSDT.aml and a fully expanded screenshot showing the FULL Device Patch Entry. Shrink the others as required to show the full Device Path column.

 

[unecc]

Try this cleaned up EFI folder based on OC 1.0.5 (Release) with the latest AMD Vanilla Patches for Tahoe.

I have made a few changes to your EFI when creating this new one.

1. Edited the SSDT-USB-Reset.aml table to correct the IOReg Names shown in the SSDT, so they match those shown in the screenshot you posted.
2. Removed NVMeFix.kext - it as disabled anyway.
3. Edited the USBMap.kext/Contents/Info.plist so it uses the iMacPro1,1 SMBIOS to match the SMBIOS data in your config.plist.
4. Replaced the AMD Kernel Patches to the latest version, as your current config doesn't use the newest set.
5. Removed the DeviceProperties entries from the config.plist, as I don't believe they are correct.
6. Made sure all the Drivers, Tools etc, in the EFI folder are from the same OC release.
7. Made a few other edits in the config.plist to keep in line with the Dortania OC Ryzen guide.

Try this revised EFI on a spare USB pen Drive and let me know how it works or if you ran in to issues using the EFI.

Other issues:
From the Hackintool Screenshot you posted I can see that you have 7 x devices with 'pci-bridge@x' entries in the IOReg Name. This will prevent these devices from being correctly identified by macOS. See edited entries in the screenshot below.

View attachment 17571 7 x Devices with 'pci-bridge' entries that need fixing.

To fix these issues you need to generate one or more (possibly 3) SSDT's using Corpnewt's SSDTTime script and your system DSDT.aml. I can help with this if you are not sure what is required, as I have had to do the same for a few of my AMD systems.

Post a copy of your system DSDT.aml and a fully expanded screenshot showing the FULL Device Patch Entry. Shrink the others as required to show the full Device Path column.

:'( Ed the other user, rightly, suggest me to create a new and cleaned EFI and not use his. Can we do the same for this, i think that's better and ready with alla your edits.

 

[Edhawk]

The EFI I created and attached to post #14, is 'New & Cleaned'.

Try it and see where it gets you.

 

[unecc]

I've insert that efi : Panic in -v boot
I've try try to reboot and it reboot automatically. Then the ssd of macos disappear from boot.
I've insert old EFI, with disk genius in windows and ...nothing SSD disappear from boot device
I'm a stupid girl. Solved


Update1: i'm trying an other time OACA say this of your EFI, i go on , i think it's a problem of compatibility.



Update 2:
Panic

 

[Edhawk]

No my EFI is not borked. You are using an old version of ocvalidate so it won’t work correctly with my EFI, which is from Release 1.0.5. If you use the ocvalidate from OC 1.0.5 then there will be no errors.