-
Notifications
You must be signed in to change notification settings - Fork 132
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
kernel 5.7: No sound. sof-audio-pci ASoC: can't set iDisp3 Pin hw params: -22 #2065
Comments
Can confirm having the same issues on 5.7rc3 and earlier versions of Linux 5.7. Microphone appears to be working, but audio playback yields no sound and error -22 in dmesg. |
I'm closing this issue, because:
SolutionI spent more than 12 hours to get a working sound on Linux (because 2020 is the year of the Linux desktop;)), so here's a solution for people with the same problem as I have:
Related issues |
The recommentation is to take the binaries from the sof-bin repository and use the go.sh script to update the symlinks for all platforms. |
In-progress (hit submit accidentally) :/
Kernel: 5.7.0-050700rc3.202004262131
Short version
Long version
Machine
Kernel 5.4
snd-intel-dspcfg
withdsp_driver=1
changes driver in use to snd_hda_intel and i have sound but my internal microphone does not workoptions snd-hda-intel model=laptop-dmic
and none seems workKernel 5.7
So checked fix for #1658
dmesg
lspci
/proc/asound
No sound:
alsamixer
sees (correctly or not - I don't know) my card:aplay - no sound:
pactl list cards
- only sees nvidia sound card. On kernel 5.4 withdsp_driver=1
pulse audio sees my intel sound card.Let me know if you need more information. I can also patch/recompile my kernel if you want:)
BTW assuming that SOF driver detects correct topology of my setup on 5.7 kernel, is it possible to use this information somehow (I don't know: creating devices manually, writing things to procfs/sysfs, hda, hdajackretask, patching
patch_realtek.c
) on 5.4 kernel withsnd_hda_intel
to get my mic working?The text was updated successfully, but these errors were encountered: