Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio pulseaudio[783]: Failed to find a working profile.
Jan 27 19:11:29 oblio kernel: vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
Jan 27 19:11:29 oblio pulseaudio[783]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
But they seem to reference HDMI, which works fine, so maybe not.
After resetting it to 0, now it appears only once in /proc/cmdline (I assume since the parameter is a duplicate with a duplicate value). But you can see our cmdline.txt parameters start with root=.
Have no clue what is going on. You have different aplay names also. Could be something with the 5.10.9 kernel or how your video is configured. But that card 1 should be your headphone jack. Also remember because of the nature of the on board jack being a A/V jack not all plugs will produce audio because of wiring differences. I had to try a couple different phone headphones here to play audio. I have a cheap set of speakes also here with a stero jack that will not play. They sell an A/V splitter adapter.
Neither setting snd_bcm2835.enable_hdmi=0 nor removing ~/.config caused any change.
I am going to try switching to fkms and see if that effects the audio drivers loaded.
I believe there is a hack re-writing the alsa card config. It is in the 5.10 next kernel thread on the pi forum. It also involves disabling dtparam=audio=on I think.
We were on the right track with the command line parameters. I tried them but it didn’t work. However, that is from a thread on 5.10, so I probably need to upgrade first.
It is late… 5.10… I was thinking 5.10.10. So it should have worked. But then those are for the bcm2835 driver and I seem to be using vc4 driver.
It is? I don’t have headphone jack as an option but maybe I need to change something in config.txt or cmdline.txt. I’ll hack around some and see if I can get lucky.
So far, no luck. I’ll keep working on it.
I can disable sound but so far no combination that I have tried has produced the headphone jack. I was hopeful that disabling sound from the vc4 would cause the bcm_2835 driver to drive both hdmi and headphone jack.
I did not notice a change in the kernel modules but I’ll look closer as I hack around more.