Proposal: new section
- I disagree, this is a static workaround around broken automatic detection, likely brought about by having an incorrect utility starting too early and blocking a device, or having an incorrect session set up. It would be better to fix the root issue, than suggesting workarounds that are likely to lead to more issues. Ideally on a proper working pulse setup, your entire ALSA config should be the one provided by alsa-pulseaudio--V1del (talk) 23:08, 11 January 2019 (UTC)
- OK, where do I start to find out what's messing up the automatic detection? Should I put this in a forum post instead of here in the wiki talk ? --E-type (talk) 23:42, 11 January 2019 (UTC)
Pulseaudio server bound to wrong card and no other cards detected
Pulseaudio can be bound to the first card found and not detect the second. As a result you may have no audio from speakers though headphone jack might give good output.
Check available cards. Example from HP Pavilion Laptop 15-cw0xxx:
$ aplay -L null Discard all samples (playback) or generate zero samples (capture) hdmi:CARD=Generic,DEV=0 HD-Audio Generic, HDMI 0 HDMI Audio Output default:CARD=Generic_1 HD-Audio Generic, ALC295 Analog Default Audio Device sysdefault:CARD=Generic_1 HD-Audio Generic, ALC295 Analog Default Audio Device etc etc
Using the default config pulseaudio binds to hdmi:CARD=Generic,dev=0 and does not show default:CARD=Generic_1. It's not possible to switch to default:CARD=Generic_1 or to mark it as default in for example pavucontrol.
Alsa without pulseaudio works fine:
$ speaker-test -Ddefault:CARD=Generic_1
After adding the following line to .config/pulse/default.pa pulseaudio sound works on the speakers. (Add to /etc/pulse/default.pa for all users):
load-module module-alsa-sink device=default:CARD=Generic_1