Lol well if it's hiding it on you then I dunno but at least you saw it before it ran and hid under the bed 
That's whack if you left blacklist snd_hda_codec_hdmi in the blacklist the hdmi should be gone...something screwy going on.
Now,
aplay -lL | grep HDA :
HDA Intel PCH
HDA ATI HDMI, HDMI 0
HDA ATI HDMI, HDMI 1
HDA ATI HDMI, HDMI 2
HDA ATI HDMI, HDMI 3
HDA ATI HDMI, HDMI 4
HDA ATI HDMI, HDMI 5
HDA ATI HDMI, HDMI 6
HDA ATI HDMI
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
card 1: HDMI [HDA ATI HDMI], device 12: HDMI 6 [HDMI 6]
I kinda think this is a failed approach. In theory to nuke the HDMI
blacklist snd_hda_codec_hdmi
blacklist snd_hda_codec
blacklist snd_hda_intel
Which in theory will also nuke the actual HDA.
OK well back to the drawing board. If you remove all the blacklist stuff and just do (aplay -lL | grep HDA) what does it give you. So long as the 100/C230 shows will try to go from there.
Okay, just so I follow you, should I try blacklisting again with those three lines first?
Or just go ahead and don't have anything blacklisted, then do aplay -IL | grep HDA ?
No I'm saying remove all the blacklist stuff. I was trying to be reductionist where if we can remove the HDMI from things it will clean stuff up and be easier to parse outputs and or perhaps make things default to the "only remaining interface" which should have been the normal HDA. However the reductionist approach has el flopped heh.
So if you remove the blacklist stuff just see if aplay can see the normal HDA and try to work around the fact everything wants to grab the HDMI first.
1 Like
Gotcha
aplay -IL | grep HDA
HDA Intel PCH
HDA ATI HDMI, HDMI 0
HDA ATI HDMI, HDMI 1
HDA ATI HDMI, HDMI 2
HDA ATI HDMI, HDMI 3
HDA ATI HDMI, HDMI 4
HDA ATI HDMI, HDMI 5
HDA ATI HDMI, HDMI 6
HDA ATI HDMI
OK well it sees it...kinda.
OK just a note here but I'm getting my a$5 kicked via some allergy crap lately, the brain fog, the feeling of my eyes being sucked outta my head heh. Not an excuse at all but my lord it's making some stuff hard to focus on.
I went back to check your initial sys dump and yeah FFS the HDMI is using snd_hda_intel same as the HDA so we absolutely can't separate them in that respect but I completely missed that.
Gimmie a few to play around with a few things.
I hear that! 
Okay, just want to check to see if I should leave this as it is:
Leave it for now but run this and see what it says
cat /proc/asound/cards
cat /proc/asound/cards
File: /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x92720000 irq 59
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0x92660000 irq 60
OK well that sees the damn thing...(back to digging for a few)
I think I saw something on another post somewhere about changing frequencies, is that related in some way?
No it won't be. The issue isn't the bit rate of freq but rather pulse refuses to see the normal audio. Alsa sees it (going back to why alsa is the gatekeeper) but I want to just be able to shoot some audio to the device via alsa first and see if we get some sound. Then if that works we'll need to get pulse/pipe to pull their heads out of their ar$e5 so you can use it via the "top end" controls.
Given alsa sees it as 0 maybe try
vi/kate/mousepad/whichever /etc/asound.conf
and add
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
I had been able to mess around with inputs and the config settings just with the volume control/audio sys settings, to where it would show the volume meter thing fluctuating when I played a video, but there just wasn't any actual sound
...fallin trees, or anythane eltse... 
Yeah it will show the volume levels but it's sending to a dead output so no sound
peek /var/lib/alsa/asound.state and see what it says. I'm just curious.
Also this might be a tad cheese but do you have audacious installed? Was wondering if you set it to strictly alsa output and played something...
In theory you should be able to do (based on your initial aplay -L)
aplay -Dfront:CARD=PCH /path/to/random/wav/file
aplay -Dsurround21:CARD=PCH /path/to/random/wav/file
Those are the two interfaces most likely to be right for that interface
Okay, there is a ton of stuff in that file, I only know how to look at it by typing sudo nano (then whatever trying to get into).
I'm sure it's about time I learned a better way, lol
Or was there a specific thing therein you wanted me to check?
No to Audacious
No, I was more curious if it had been populated.
Aight to audcaious heh and try those aplay lines if you've got a wav file kicking around or an mp3 if you don't mind horrible static...IF it works.
Okay, I had just done a fresh install of Garuda not long ago, so don't have any real content outside of what it fires up with
Is there a good place to quickly download one just for this purpose?
I dare say if you want to go the noise route you can just call any file. A text file from your .config folder or even /etc/fstab if you want a fast blip of noise heh.
1 Like
Wondering if it might be a kernel issue? Had seen something about that on the Arch forums. And I can't join those because they're strictly for Arch.
[Le sigh]...
Just don't know what to try 
