HDMI audio cutouts
HDMI audio cutouts persist from 6.9 to 6.11. The 6.11 update was supposed to bring improvements/fixes for this issue but nothing has changed. Chimera os was able to patch it manually and fix it on 6.9 where it was previously broken there as well. Not sure where the fault lies or what to try to fix this on bazzite. Using 7800xt
114 Replies
its not the kernel though, its something else maybe fedora related
I dont think its fedora, if I recall chimera is arch based and that was having issues before prior to the "fix"
what was the fix though
I can’t help, but have a similar graphics card. With ChimeraOS, were you just using the default install, or did you do something special?
I was thinking of maybe trying CachyOS for my HTPC. Running Bazzite on the ROG AllyX and that seems fine.
included in our kernel
So its something else then entirely
Since we ruled out the kernel it seems should I spin up straight fedora and see what happens?
probably yea
although before you can try some workarounds such as increasing buffer sizes
Well I gotta reinstall anyway since I have manjaro loaded, before I try any bazzite tweaks might as well do fedora first and just see what happens
yea
I think you were onto something with it being fedora related, I got straight fedora running and issue is back
yea
At this point do you want me to spin back up bazzite and we can try increasing the buffer?
you can also do it in fedora
Would you mind giving me instructions on how to do that and I can try it?
i dont remember :clueless:
something alsa
wireplumber
Oop, well im not entirely sure either then lol
At least its narrowed down and definitely not kernel related at this point
Where do we go from here? I suppose I can use something else in the meantime but this is clearly some bug/issue and I dunno how we go about fixing it in the long term
https://wiki.archlinux.org/title/PipeWire hopefully you read this
Are you referring to section 5.1.13 or 5.1.14?
just go through all of it
Alright I read through it but I dont exactly understand a lot of this
Are you suggesting this?
yea that could also help
You probably wont know the answer to this but would it be possible to pull the settings off of something like chimera or manjaro (assuming the audio is set up the same) and copy the settings over?
Are you getting underruns?
In the journal
Underruns?
In the screenshot you posted
It gives an example
Do you see those in the journal as the mention
Basically, there if a buffer that holds processed audio before it is played back. If the buffer runs out, the audio will glitch.
If you are not getting those errors, then it's not a buffer size issue
The audio glitches only happen with HDMI, right? Like if you plug in headphones it works?
This is correct
I will take a look
Have you tried a different HDMI cable? Cheap/old cables can cause audio issues.
Different cables, different TVs, different GPUs, mobos, CPUs. Its not hardware
How do I read the journal on bazzite? Im not seeing it anywhere
Figured it out, journalctl, however there is nothing when reading pipewire-pulse.service
Than it's likely not the issue
Just tried spinning up cachyOS which is arch based, issue is there as well. Its not just fedora
Chimera corrected themselves, they said this was the fix they used, not the one I previously linked https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus&id=478689b5990deb626a0b3f1ebf165979914d6be4
The patch was supposed to be in 6.11 but it caused regressions with other machines
It looks like there is a new fix in 6.12
this is the snoop fix
and you tried the snoop
and you said it did not work
They recommended disabling IOMMU from my mobo, if this is the issue then by disabling it completely it should fix it on an unpatched kernel
it doesnt matter patched or unpatched
all that patch does is not disable snoop
Welp I dunno then
IOMMU might help
disable it
although it might lower perf in some applications
add this to your kernel command line
amd_iommu=off
same as snoopMy mobo had IOMMU set to auto, I disabled it completely and loading back in now
Dont think I need that if I disable it in bios but I suppose it doesnt hurt
Nope disabled IOMMU and issue was still present
You could install Rawhide and see if the fix in 6.12 works.
I tested manjaro with 6.12 and issue was fixed there, but it was also working on manjaro 6.11 too
However chimera gave me an idea, they suggested I try cachy where the issue was also happening, and try loading the chimera kernel into it
the patch Chimera is using was dropped though due to regression, I would see if the changes in 6.12 fix it
it's sounds like a fixed implementation instead of a workaround
Just out of curiosity, have you tried Bazzite desktop edition instead? I had a weird issue with Steam / Linux game mode with my htpc where it wouldn’t do surround in the game mode. Maybe related, maybe not… just curious.
I decided to do some troubleshooting on my end that might be worth looking deeper into. I decided to install base arch and test it there. The sound issue was still present, however I pulled the chimera kernel and applied it to my arch install and after the issue is completely gone. Its definitely something in their kernel
6.9 is hard to bisect on arch because it can't make packages. @matt_schwartz how did you bisect on arch before
6.11
I used 6.11 for both the arch base kernel as well as the 6.11 chimera kernel
Sorry should have specified
What
There's no 6.11 chimera kernel
That released in chos
This makes it very simple
Link me the branch
I think this is what you mean? Sorry I dont use github that often https://github.com/ChimeraOS/linux/commits/6.11/chimeraos/
GitHub
Commits · ChimeraOS/linux
Linux kernel source tree. Contribute to ChimeraOS/linux development by creating an account on GitHub.
where did you download it from
From here
which other kernel did you try?
install the downgrade package and test 6.11.3
Okay thats my bad I shouldve been testing the same versions, I used the downgrade package and tested 6.11.3 and issue is not there. But I do see chimera released a 6.11.5 kernel, I can try that next
dont
you found the culprit
do 6.11.4 now
6.11.4 is fine, no cutouts
so its 6.11.5, @Kyle Gospo do we revert to 6.11.4
let me check 6.11.6
try 6.11.6 for funzies
I'm not against that
theres also another issue i think
wtf is wrong with the kernel can they release one version where they dont break everything
They just don't have enough unit testing
Simple as
They need a fleet of like 10,000 different pieces of hardware
And a very robust testing suite for each one of them
then they make you sacrifice a newborn to make a bug report
Its borked
ok, go make a thread here https://gitlab.freedesktop.org/drm/amd/-/issues
GitLab
Issues · drm / amd · GitLab
amd (amdgpu, amdkfd, radeon) drm project, currently for issues only.
cry about it say you used a stock arch kernel and the regression is inbetween 6.11.3 and 6.11.4
*4 and 5
then when they tell you the commit that did it tell us
I will submit that as soon as im off work here in a bit and let ya know. Btw do you all take donations for the work you put into this? For all the help you are giving me plus I love the project, I wanna give back
Sorry last night was hectic but I just out it in this morning and I guess now we wait https://gitlab.freedesktop.org/drm/amd/-/issues/3732
GitLab
HDMI Audio Regression (#3732) · Issues · drm / amd · GitLab
Brief summary of the problem: Since the beginning of 2024 I have been having issues with my HTPC (ryzen 3600 & 7800XT) while playing games and the audio...
You mentioned bazzite being reverted to 6.11.4, is that still the case?
probably not
lets hope they answer soon otherwise we will think about it
Hello, I have a problem, installing bazzite on my onexplayer 2 and I don't have audio, I don't know how to solve it or maybe install another iso like chimera or not?
Onexplayer 2 does not have audio support in Linux right now
Pending a bios update
Is there an OS for oneexplayer 2 to be able to have steamos without problems?
Yes, bazzite but without audio for now
And the audio doesn't work either if I connect it to a TV or monitor?
It works then
Seems I was asked to bisect but I'm not exactly sure how to do that or what I'm looking for
Are you on arch?
It's a pain in the ass you might as well buy new speakers
If you learn how it should take you around an hour so it's not bad
I have not touched my arch install since I last used the downgrade script, in case I needed to go back into it
I really don't want to buy speakers when this was a pc I built for not only home use but also cons/game events. I made it small and portable for a reason, adding speakers to the mix isn't ideal
In this case
You'll want to clone the stable remote of the kernel
Im learning how to bisect as it was recommended to me in two other places, however in the meantime I saw cachyos released a 6.12 kernel. I decided to spin it up and the issue is fixed where as before on cachy it was broken. I think the easier option will just be waiting again for 6.12 tbh
@Kyle Gospo @antheas thank you both for the help and support through this issue over the past year. It was at least a learning experience for me, trying many fixes, kernel swapping, bisecting, etc. Gonna go ahead and mark this as resolved for now assuming it will also be fixed when bazzite goes 6.12. Love the project and I mentioned it before but if you all take donations I would love to contribute even if its not much ❤️
Ugh nevermind I spoke too soon. Issue is back again on 6.12 cachy. Back to bisecting I go
Well it took some time but I was able to bisect between 6.11.4 and 6.11.5, I did it twice as a sanity check, both yielded the same results if you're curious
Tbh I looked at the commit history and spotted that garbage
Post the closes and link here so I can see them
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3618
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/3131
GitLab
RDNA3 Power Management/clockspeed bug (#3618) · Issues · drm / amd ...
When starting a game or other demanding 3D application the GPU seems to be powerlimited and/or clockspeed limited. On my case it was only drawing 270W power and...
thanks
and thanks for going through this
Happy to help, it's both a learning experience for me but also I just want to see this fixed, I hope something comes of it. I'll also be updating my post here later today too
GitHub
Release 6.11.6-303: Powersave optimization revert · hhd-dev/kernel-...
6.11.5 amdgpu forces a powersave optimization that causes HDMI cutouts in certain dGPU devices. Revert it even if it means a small performance loss.
Full Changelog: 6.11.6-302...6.11.6-303
If/when this get pushed to testing would you mind pinging me and I'll happily test it?
Sure
Kyle is moving though
So it will take a bit
No rush, I waited this long to get this far, I can wait a little more. In the meantime I'll update my gitlab report and see what comes of it
Kernel is in testing
Oh wow that was faster than expected, I'm heading to bed for the night but I'll test tomorrow while I'm working
Is the branch switching in gamescope working? I selected beta/release candidate and restarted. I opened terminal to confirm the branch and it still says im on stable
Well haha sometimes
I got it loaded anyway, I just rebased from term
But yeah gamescope rebasing wasnt working, figured I'd mention it
Good news, I dont want to jinx it bit I have been letting it sit in game for over 10 minutes now and no issues
Let it sit for nearly an hour now, still working, no issues
Will try some other games tonight for a more extended test but I think we got it
follow up on the issue there might have to be a revision to fix the old issue + not cause your issue
Whatcha mean?
Are you referring to this comment? https://gitlab.freedesktop.org/drm/amd/-/issues/3732#note_2653681
GitLab
HDMI Audio Regression (#3732) · Issues · drm / amd · GitLab
Brief summary of the problem: Since the beginning of 2024 I have been having issues with my HTPC (ryzen 3600 & 7800XT) while playing games and the audio...
Guess so
Yeah im not sure how to pull those patches into what im guessing is a custom kernel patch I need to make
the way you bisected
you will checkout rc7
then git apply <patch>
Do you know what to insert for <patch>? That part isnt exactly clear with the links they gave me
Oh just inset the link itself?
b4 am -o- $url | git apply
download the file
url=https://lore.kernel.org/amd-gfx/[email protected]/T/#u
you can git am both thats true
b4 am -o- $url | git am thats how you do thatSo for example
b4 am -o- https://gitlab.freedesktop.org/agd5f/linux/-/commit/74e1006430a5377228e49310f6d915628609929e.patch | git am
i usually do
url=url
then run the command i sent
so i dont mess with it
git apply patches the files
git am applies commits
bash: b4: command not found
error: No valid patches in input (allow with "--allow-empty")
Do I do it with --allow-empty?
Be careful about applying the patch twice
If it says allow empty it means the patch is already applied
Install b4
Yes if b4 does not exist it will error
That was after the first time I did the command, with stock 6.12-rc7
Doing that now
Does this output look correct after installing b4?
Grabbing thread from lore.kernel.org/all/[email protected]/t.mbox.gz
Analyzing 6 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
[PATCH] drm/amd/pm: fix and simplify workload handling
---
NOTE: install dkimpy for DKIM signature verification
---
Total patches: 1
---
Link: https://lore.kernel.org/r/[email protected]
Base: not specified
error: patch failed: drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c:1268
error: drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c: patch does not apply
Yes
No
Does not apply
Means you're cooked
So I suppose respond to the gitlab report with that?
I dont know what your procedure from moving testing to stable but is it possible to move the patch that was made in testing over to stable?
Dumb question, do I need to build 6.12, boot into it, then do git am?
No, you need to do git am before
Build with the changes
Okay so I was doing it right then
Rip
Sadly so far none of their patches appear to be working so far, they are definitely minimizing the issue but its still heavily present in some cases