Natlampen wrote:I have just installed a RX 6700XT in my computer. To get it booting I needed linux-firmware-git from AUR as you noted. And to remove the screen glitches I installed also mesa-git from AUR. Although I did not notice the squares in the terminal. I saw it only in gnome and games.
@Natlampen Thanks for replying, I will give it shot if it worked for you.
@Natlampen I just installed mesa-git and lib32-mesa-git from AUR as you said worked for you, that seems to have worked for me as well since I am not getting any more screen glitches in my terminal or graphical applications, as well as not seeing any more text fading out in my terminal emulator.
Thanks sharing what worked for you!
Thanks to all those who took the time to respond and help find a solution! I'll mark the topic as solved.
]]>I have just installed a RX 6700XT in my computer. To get it booting I needed linux-firmware-git from AUR as you noted. And to remove the screen glitches I installed also mesa-git from AUR. Although I did not notice the squares in the terminal. I saw it only in gnome and games.
@Natlampen Thanks for replying, I will give it shot if it worked for you.
]]>Does it go away if you drive the output at 60Hz?
("xrandr --output DP1-whatever --rate 60")
I just tried that the other day forgot to mention it, with the refresh rate set through xrandr the screen glitching is still there.
]]>No, that's fine…
Does it happen w/ only "amdgpu.dc=0"?
Just tried it and it also happens only with "amdgpu.dc=0". I also came across a section in the AMDGPU wiki page
because it sounded like it could maybe be something because my monitors support refresh rates above 60hz
but that didn't change anything, neither high or low using a udev rule.
Can you please post the literal commandline you tried?
It seems weird that either of the other parameters would have caused the outputs to fail and I rather suspect a syntax issue.
I added those kernel parameters to /etc/default/grub so that the following line looks like this.
GRUB_CMDLINE_LINUX="rd.luks.name=b098b6ea-965b-4d24-91ad-247662d3a62d=cryptlvm amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0"
Then I generated my grub configuration with grub-mkconfig, after which I rebooted and when booting into the kernel neither of my monitors got any output so they went to sleep mode.
]]>??
'key...Try only "amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0" .
That gives the same results as before, both my monitors not receiving any input when booting into the kernel
with those kernel parameters added too my grub configuration and when I only use amdgpu.dpm=0 it boots
without my monitors not receiving any input but the glitches still appear. I also tried this
which I just came across in the wiki but neither high or low did anything for the glitching problem.
Try only "amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0" .
]]>You're supposed to try whether the parameters make the problem go away.
That was misunderstood sorry, I added those kernel parameters too my grub configuration, as soon
as it starts booting the kernel both my monitors give no output and also give the message no output.
When I boot from the archiso to arch-crhoot into my installation and remove those kernel parameters then
I am able to boot the kernel again without both my monitors going blank because of not receiving any input.
glitches only appear on the selected monitor
What does that mean specifically? Actve window or mouse position?
Do you also run a compositor?Also, the usual suspicious kernel parameters:
amdgpu.dc=0 amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0
@seth Thanks for your reply, the monitor that my mouse is active on, so in i3wm terminology "active workspace". Although I
did some more testing and it seems with a graphical application such as Steam the glitches stay and never leave and with
my terminal emulator or my filemanager the glitches disappear when switching to the workspace that has the glitches making
it the active one where my mouse is at. I don't use any of those kernel parameters and I do not run a compositor. Here's an
example of how the glitches look on Steam.
glitches only appear on the selected monitor
What does that mean specifically? Actve window or mouse position?
Do you also run a compositor?
Also, the usual suspicious kernel parameters:
amdgpu.dc=0 amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0