Ok, I think I've got this display card under control - or so it seems. It hasn't crashed since Wednesday.
I guess this is a combo AMD RDNA3 Navi23 and KDE Plasma (+ Wayland?) bug...
I backed out all my Linux kernel command line switches for AMD GPUs and it crashed to green screen in less than a half hour. So, re-adding them stopped that from happening.
... amdgpu.dcdebugmask=0x410 amdgpu.tmz=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 ...
And then the cursor thing is fixed <?!> by adding
KWIN_FORCE_SW_CURSOR=1
Currently this is what is set:
cat /proc/$(pidof kwin_wayland)/environ | tr '\0' '\n' | grep KWIN :
KWIN_DRM_NO_AMS=1
KWIN_DRM_NO_DIRECT_SCANOUT=1
KWIN_FORCE_SW_CURSOR=1
From a user experience point of view I don't see any difference with that software cursor setting.
There's another wrinkle to this that might be a factor but I can't really test around it currently. This is a multi-head machine and one screen is connected via HDMI and one is DP.
Perhaps this wouldn't be a problem if both screens were connected via the same type of connector.
Both screens are set to the same refresh frequency. But, in the display control app one reads back at 60.00 Hz while the other is 60.000 Hz. Minor thing right? But in trying to make this work I've seen references to AMD GPU weirdness in multi-head configurations where the refresh rates were different between screens. Red herring perhaps.
Anyway, don't know if there are (or will be) any people trying to make a RX 5800 XT GPU behave under Linux but this seems to be what worked for me and my dual head setup. I'll update if anything changes.
#Linux #AMD #AMDGPU #KDE #KDEPlasma #Plasma #AlpineLinux #kwin #Wayland
installed on my main pooter's sda, & whilst it is still very reliable for me, the friction from the routine maintenance [he listed some of the items / actions, but there's others too] has been a bit of a drag for me for some years now, plus the ongoing #AUR attacks necessitate a perpetually heightened defensive posture that's tiring, & to which i chose eventually to respond to by replacing most of my AUR pkgs with #flatpak or #distrobox ones, or in several cases nothing at all [ie, i chose to just abandon some apps altogether].
so for a couple of months now [after more than a year in various VMs], my delightful daily penguin is the immutable atomic alpha 
, on sdc. it is really pleasant to use, albeit ofc i needed to adjust several of my workflows to accommodate its RO base.
my sdb remains largely empty atm, but once it reaches Beta i hope to install 
kalpa here
unfortunately my old 2011 Dell xps-15 lappy is "stuck" with Arch, coz it only has bios not uefi boot, which eliminates both of those atomics, alas
#DropbearPooterising #Linux #LinuxWomen #FOSS
#ArchLinux #KDEPlasma
#SparkyLinux | 
#Kinoite
#FirefoxNightly #FirefoxSecondSidebar #NativeTreeTabs
) koski nimenomaan CachyOSia, muilla käyttöjärjestelmissä näkyy oikein selaimesta riippumatta.
Nyt vasta hoksasin tarkistaa KDE Plasman asetukset tarkemmin ja sieltä löytyikin syypää.
Ulkoasut ja Teemat > Animoinnit > Animoinnin nopeus 'välitön'. Välitön tila laukaisi tämän ongelman. Säädin animoinnin nyt hitaammaksi ja heti ratkesi ongelma. 'Välitön' aiheutti sydämen animoinnin poistamisen, kun se on aktiivisena. Kyseisen asetuksen lisäinfossa mainitaan, että ongelma saattaa koskea nimenomaan GTK sovelluksia ja animointi ei toimi niissä oikein tässä tilassa.
PS. Tämä oli muistiinpano itselleni. 🤓
Tässä kokeilin vähän Asahille uusia alusvaatteita ja housuja. Testissä vaatemallisto Arc Dark.
CachyOS + i3wm Aviso: parei de aceitar "seguidores" automaticamente. Motivo? Spam; também não estou aceitando mais perfis cujo foco seja IA, perdão. PS: O gol é do outro lado.