Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALC1220 / ALC1220A #120

Open
BoostFX opened this issue Oct 5, 2017 · 6 comments
Open

ALC1220 / ALC1220A #120

BoostFX opened this issue Oct 5, 2017 · 6 comments

Comments

@BoostFX
Copy link

BoostFX commented Oct 5, 2017

Hi, I've had some trouble getting my GA Z270-UD5 audio working with the 130 command script.

I found that it patched the 1220 thus only displayed the devices without working them.

I reworked the 124 script to work with 10.13 rerun that and now got working sound.

Thus there is probably some mixup in the 130 script with applying the normal and A version or I did something wrong and took a very long detour.

But looking at the kext to patch plist section they find the same hex but patch to 6811ec10 for the A and 2012ec10 for the non A

Have a great day
ciao

@toleda
Copy link
Owner

toleda commented Oct 5, 2017

"But looking at the kext to patch plist section they find the same hex but patch to 6811ec10 for the A and 2012ec10 for the non A"
Say more.

@vadimvitvickiy
Copy link

same here, can't get it work, but patch installed
asus z270g

@toleda
Copy link
Owner

toleda commented Oct 5, 2017

Which is wrong, 6811ec10 or 2012ec10?

@vadimvitvickiy
Copy link

I was try latest version

@BoostFX
Copy link
Author

BoostFX commented Oct 5, 2017

That’s right but
at least on my clean installed system the patch was applied for the non a version

6811ec10 for the A and 2012ec10 for the non A

And A was needed.

Only found that by mistakenly opening the plist and browsing the patches. Comparing to my config list patches and found that the non a version patch was applied.

I really don’t know the background mechanics. Just found that it applied the wrong patch. And in earlier versions (124) the right one was applied. And I believe in one version it was asked for the correct codec.

Despite that all.
Thank you so much for that great tool.
I started with tiger and things got so easy at this point for most hardware.

@toleda
Copy link
Owner

toleda commented Oct 5, 2017

@BoostFX: 6811ec10 for the A and 2012ec10 for the non A
That is correct.
Asus/STRIX uses 1220A/1168. Everyone else, including Gigabyte, use 1220/1220.
No change to 1220 from 124 to 130.
Wrong patch was not applied, something else is wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants