[Bug 1198004] New: Sound card not working - bad firmware?
http://bugzilla.opensuse.org/show_bug.cgi?id=1198004 Bug ID: 1198004 Summary: Sound card not working - bad firmware? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: alanhants@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 857736 --> http://bugzilla.opensuse.org/attachment.cgi?id=857736&action=edit Boot messages relating to the sound device I have a sound device on my motherboard that shows up on Yast as a "100 Series/C230 Series Chipset Family HD Audio Controller" that uses the "snd-hda-intel" kernel driver. After a Tumbleweed update to "20220402" (with kernel 5.17.1-1-default) the card is no longer generating any sound, even when I attempt to manually send a sound file to it (e.g. by playing one of the KDE notification sounds). Examination of the systemd log shows that a firmware file failed to load for the sound device. I've attached an extract of the systemd log relating to the sound card; it shows the error message when loading the firmware and the card being effectively disabled as a direct consequence. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198004 http://bugzilla.opensuse.org/show_bug.cgi?id=1198004#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alanhants@gmail.com Flags| |needinfo?(alanhants@gmail.c | |om) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- (In reply to Alan Hughes from comment #0)
After a Tumbleweed update to "20220402" (with kernel 5.17.1-1-default) the card is no longer generating any sound, even when I attempt to manually send a sound file to it (e.g. by playing one of the KDE notification sounds).
Could you give more detailed description? From which system did you update? If you have been running TW, can you try rollback? If the rollback can't be used, at least, can you try to boot with the older kernel that had worked, and see whether the same problem is seen? In anyway, please give alsa-info.sh outputs from both old and new kernels. Run the script with --no-upload option and attach the outputs to Bugzilla.
Examination of the systemd log shows that a firmware file failed to load for the sound device.
I've attached an extract of the systemd log relating to the sound card; it shows the error message when loading the firmware and the card being effectively disabled as a direct consequence.
Judging from the log, you have two sound cards, at least, one is an onboard audio and another a CA0132-based audio. Maybe both are onboard, but I can't check it. The error about the firmware error is for CA0132, and this must be present in the older kernel, too, unless you mistakenly uninstall the corresponding firmware package (kernel-firmware-sound and alsa-firmware). The onboard audio shows, OTOH, another problem, the codec communication. It went into a fallback mode, which works somehow but imperfectly (e.g. the jack detection won't work in this mode). You need to check with the status with the older kernel to see whether it's a new problem or not, too. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198004 http://bugzilla.opensuse.org/show_bug.cgi?id=1198004#c2 --- Comment #2 from Alan Hughes <alanhants@gmail.com> --- There is a second sound device associated with my graphics card; this device is not being used (it is disabled in YaST). Rollback to an older version of TW (with a 5.16.x kernel) failed to resolve the problem, however a complete power down (with power isolation to ensure that capacitors are discharged) *did* result in the sound functionality being restored. It looks like the kernel reboot I performed after the last TW update left the sound device in an inconsistent state which the kernel did not reset when booted. Based on this I guess you can close the bug report, at least until I can isolate things more comprehensively. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1198004 http://bugzilla.opensuse.org/show_bug.cgi?id=1198004#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID Flags|needinfo?(alanhants@gmail.c | |om) | --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Yeah, that sounds like a symptom that sometimes happens; the system kept the codec chip in a deeply powered down and BIOS couldn't power up properly by some reason. In anyway, it's a BIOS bug :) Let's close now. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com