Post #1823050
2026-04-23 14:52 UTC
@stark sorry, I have no idea, as your question is way too vague. Here is why:
Like many bug reporters, you seem to assume that the problem you face is something generic that other people encounter and know about. No problem, that is totally normal[1].
And sometimes it really is something like that. But the thing is: most of the time it is not -- especially if the problem is not fixed within a few weeks.
That's because the Linux kernel is a complex beast that supports thousands of devices that support HDMI audio. Some of those will always be broken. Sometimes, because support was not implemented yet (for example, due to the lack of documentation). Sometimes, because some change broke things for a specific driver, some of the hardware a specific driver supports, or a particular system a driver supports. And in the latter case you might be the only one that encounters the problem, so it most likely won't be fixed unless you report it.
[1] I used to think along those lines myself for many years before I delved deeper into hardware and the kernel.
Replies (1)
-
@stark@mastodon.mit.edu 2026-04-23 15:27
@kernellogger in the abstract I understand all that. But when it works fine for some versions but breaks one release and works the next over and over it feels less like some hardware issue and more like some code churn. The first time it broke was when they added the "silent stream" to avoid the latency when sound plays. Then a subsequent version started working again. Then subsequent versions randomly worked or didn't as they kept tweaking this code. How would you suggest reporting this?