Hah ... the Prime Z270A MB >IS< the one I ordered from Amazon. They shipped me a Tuf MB (the cheaper one) after delays made me wait 2 weeks. I found out when received 2 days before I was going to install it that it was incorrect AND they "sold out" again of the Z270A. After I brought up the delays, Prime-ness, customer history and how this messes up my install window for at min a week more... the supervisor OKed them giving me a credit for the difference to the next MB up from that one. I immediately ordered one that looked really good with great reviews and was hurray. Then laying in bed I read the order and realized in my hurry to find an ASUS match sold BY Amazon that my search on "Z270" returned "Z170s" also and since my chip was newer it likely would not even post. So I quickly recalled and went through it again, this time selecting the Z270E Strix moments before the other one was shipping it seems. I didn't even read about it... had no time. Ironically that "great one" Z170 was +$80 so that's the credit. This one was only +$50 so ended up getting it cheaper than my intended Prime Z270A.

Prime: Realtek® ALC S1220A 8-Channel High Definition Audio CODEC featuring Crystal Sound 3
Stix: ROG SupremeFX 8-Channel High Definition Audio CODEC S1220A

Yup... good catch... BAH! That's probably why folks say they got S1220A working (and I didn't)

Tried these:

#options snd-hda-intel model=asus-mode5
#options snd-hda-intel model=ALC1220
#options snd-hda-intel model=alc1220_fixup_gb_dual_codecs

I know only the first was mentioned but I searched on "1220" and tried these even though names were not in same "format", figured what the hey.


So, unless some person sniffs a new fix and remembers this thread - I figure we are up to whether or not I should downgrade 4.11 to the one supplied in Mint 18.1 in order to leverage the Mint Updater tool for security updates etc? Figure if I need to install a custom kernel to solve this like e.g., 4.12 I can always re-manually install it again later.

If you don't plan to file a bug report (which you should), then just run the stock Mint kernel if it works with everything else.

Despite all of the marketing buzz terms and the different "value-added" Windows DSP software the boards come with, it looks like the same codec to me. I don't think the differences should affect getting basic sound working under Linux.

It's probably an identifier mismatch or whatever (said with no real working knowledge but hey... why stop now)
I will write a report with the lspci, aplay, dmesg, etc info from this thread.
Will be first time for me with an unanswered bug - what's the best place to do this so I enter it correctly? I'll sign up on whatever the right site is.

If they do fix it, I can always go back to the 4.11+ but this way I get "free notification" of updates without having to remember to poll the kernel site for new releases since I am poor with followups.

https://bugzilla.kernel.org/enter_bu...ent=Sound(ALSA)

Just give them the link to your alsa info. It has all of that.

Right, forgot that.


Below is my first bug ever after registering on the site:
https://bugzilla.kernel.org/show_bug.cgi?id=195795