I think your PC has a Tiger Lake processor. hence sof-firmware, which you installed is necessary.
However IMHO it is mistake to apply the snd_hda_intel force-probe fix, and that could break your sound while that is in place. Also, the thread where you reference blacklisting ALC1220 appears to be for entirely different hardware than what you have … ?? Do I have that correct ? If so, you should not do that.
Randomly applying such fixes, while they are in place, could break your sound and invalidate any other fixes to audio that you may have attempted already, leading total confusion as to the issue (at least that is the case for me when I look at this thread).
OK - thanks. Don’t forget to also remove the ‘blacklist’ command you applied - or can you confirm you found that recommendation by a user with identical hardware?
Can you now run the diagnostic script again, and paste the link here on this forum?
/usr/sbin/alsa-info.sh
My hope is that running it now will provide diagnostic information that is not ‘tainted’ by those settings.
When pipewire is properly installed, the pulseaudio package is removed. It is replaced by a wrapper (pipewire-pulseaudio) for applications that may depend on it. openSUSE_Pipewire
I also note the simple mixer control ‘loop back mixing’ is enabled. I don’t know if that a correct setting. It exceeds my knowledge.
Using alsamixer, I can’t see the loop back or any way to change it.
However under F2 System Information
.in /proc/asound/timers I do see “Client Sequence Queue 0: stopped”
. in /proc/sound/pcm I see:
… 00-00 ALC1220 Analog : playback 1 : capture 1
… 00-01 ALC1220 Digital : playback 1
speaker-test -c2 -l5 -twav
This test ran, the speaker sound gauge moved up and down but there is no sound at the speaker
as a regular user, both these commands ran but neither moved the sound gauge nor yielded sound at the speaker
as root, both commands ran but neither yielded sound at the speaker … the 0,0 command moved the speaker gauge but the 0,1 didn’t move the gauge
I am surprised to see no mention of pulse audio, and the ‘no sound servers’ in the script. Did you remove pulse audio at some point in time ?
sudo alsactl restore\CODE]
which produced the possibly interesting result:
alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0x6203178000 irq 174)
alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Just a tip: When posting output, please enclose it within CODE tags as you have been when posting commands that led to the output.
The output is significant. Searching online for similar errors turns up reports of other users having issues with alsa version 1.2.5, so a bug report is likely required here.
Actually … I thought there might be near term patches but this doesn’t seem to be the case … so might be facing having no sound for a long time if I wait for bug fix
Likely the quickest way to get the fix, is to write a bug report yourself on the openSUSE kernel in Tumbleweed. That will get the immediate attention of the SuSE-GmBH packager for sound in the kernel, who is also an alsa sound driver developer. There is a good possibility he will likely want to immediately work with you, giving you some tests to try to get the sound working. He is possibly the best person on this planet to solve this issue (IMHO) … We are very fortunate in the openSUSE distro to have him as a packager.
I believe you can use your openSUSE forum user name and password when logging on to the bugzilla site.
Don’t bother referencing this thread, as the openSUSE packager will not read a forum thread, so your bug report needs to have all the salient information. Run the diagnostic script
/usr/sbin/alsa-info.sh --no-upload
and attach the resultant text file (that will be saved in /tmp) to your bug report.
As long as the openSUSE packager is not on vacation or working on some urgent task, you are likely to get a reasonably quick response.
Thanks everyone for your help … our developers have advised that my hardware is supported in kernel 5.15, which was released on 7 Nov 2021 … and we need to wait for the kernel to be released in Tumbleweed
