I can’t get any HDMI audio with kernel 6.1+, and more precisely:
kernels ‘linux-lts 6.1.15-1’ and ‘linux 6.2.2.arch1-1’ audio fails (‘Dummy Output’) via HDMI, but is OK via audio jack/cable, as well as via bluetooth;
Kernel ‘5.15.96.61.realtime1-1-rt-lts’ works well.
I’ve logged the results of the following tests for both kernel 6 (no HDMI audio) and kernel 5 (all audio ok), and I’ve published them all on my MEGA cloud:
$ pulsemixer -l
$ pactl list short sinks
$ pactl list sinks
HDMI-lts-pipewiredaemons.log
$ systemctl --user status pipewire pipewire-pulse
My neofetch log is:
$ neofetch --off --stdout
Distro: EndeavourOS Linux x86_64
Model: PC BOX
Kernel: 5.15.94.59.realtime1-1-rt-lts (vs. 6.1.15-1-lts)
Pac: 1871 (pacman)
Shell: zsh 5.9
Res: 1920x1080
WM: bspwm
Theme: Arc-Dark [GTK3]
Icons: Adwaita [GTK3]
CPU: Intel Pentium J4205 (4) @ 2.600GHz [48.0°C]
GPu: Intel Apollo Lake [HD Graphics 505]
Memory: 1547MiB / 5764MiB
CPU Usage: 5%
Disk (/): 41G / 230G (19%)
My knowledge about all this is really poor, but I suspect the only way is to wait for a new release of kernel(s) 6.1+: but just in case, Your help is so appreciated.
After all I have changed nothing, and the same identical hardware and configs are completely ok with Kernel ‘5.15.96.61.realtime1-1-rt-lts’ (exactly as with all my previous linux-lts: I don’t even know what ‘rt-lts’ is - I’ve learnt it exists by chance, searching for any linux kernel < 6 )
Audio issues are extremely difficult to decipher because there is are so many variables and so many logs to look at and configuration files. When you post output from commands that are smaller you can just paste the output here as long as you use code tags. If the output is large it is better to use for instance commands to send the output and then post the url. It is also much easier to read.
Uhm: y-y-yes, I did that: but as I told you, I’m shamefully ignorant about all this.
For instance, only now I learn that it’s possible to save/preset/etc alsa settings.
So: thanks, I’m going to see what I can do: maybe beginning with
It will take some time, tough, because I have to understand/learn ‘why & how to do what’, and then do it in both installations.
(And yes - incidentally I need that box up running - regardless of its HDMI audio )
This is the problem with sound issues. You have to start from the beginning and go through each thing and check and check and check. It takes a long time but is easier in the long run than posting a whole bunch of logs and information which I would never be able to figure it out that way. I always do one thing at a time. Show me a log for this. Show me the output for this and so on. Try this … try that! It’s a bit complicated as it may be codecs are incorrect or hardware assignments. etc etc.