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
Audio only working after stopping PulseAudio and setting the UCM - kblda7219max on the ChromeOS Kernel, 5.10.70 #142
Comments
I ended up removing the |
On further inspection directly from ChromeOS, audio is working but it appears that PA blew my left speaker’s membrane. Is there any way to sense these issues ahead of time? |
Strangely, OEM didn't integrate the hardware-level protection from such things. |
Google can’t integrate hardware level protection from very loud noises. They probably put in protection from over-voltage. |
Stale. Re-open, if UCM configuration can be improved for this device. |
On my
kblda7219max
Chromebook (baseboard: NAMI), internal audio works properly when the following conditions are met:However, whenever I start PulseAudio (
pulseaudio -vvvv
), audio is disabled, going to a dummy output.PulseAudio passes through probing for the UCM files but errors out in this particular spot:
which causes it to say:
My
dmesg
gets filled with:However, once I kill PulseAudio and run
alsaucm -c kblda7219max set _verb HiFi set _enadev Speaker
, audio begins working again (but this is in pure ALSA and PA apps are not compatible) and theno backend DAIs enabled for Kbl Audio Port
is no longer logged todmesg
.I think this is a UCM issue because the audio is working fine kernel-level and with ALSA, but PulseAudio seems to mess something up with the UCM and the UCM needs to be set again.
Huge thanks for any help!
alsa-info.txt
(My PulseAudio log is slightly different from the time I ran PulseAudio and got the PCM_IOCTL_PREPARE error)
pulseaudio-log.txt
HiFi.conf.txt
kblda7219max.conf.txt
The text was updated successfully, but these errors were encountered: