#Plasma 6 artifacts

1 messages · Page 1 of 1 (latest)

south jetty
#

I was so scared

#

GTX 970, proprietary nvidia-drivers

#

X11 plasma has no artifacts

#

Lemme paste it rq

#

Link went brrr

glacial blaze
#

afaik plasma-wayland and nvidia-drivers is (still) not a "stable" combination

#

this is plasma 6? it should be significantly better in 6 compared to 5

south jetty
#

But, like, why, exact same versions have absolutely no issues on arch

south jetty
glacial blaze
#

is drm_modeset enabled?

south jetty
#

Yep, it is

#

Sanity check

#

Yeah

#

Even tho i did a bit of configuration in plasma x11, plasma wayland is still empty

#

I need to check logs

#

Ew.

#

Moving windows leaves goofy artifacts behind

#

People said that its something wrong with blur implementation, but its been fixed already...

#

Okay, i got some logs

#

It said that "could not load Qt platform plugin 'wayland' in '' " even tho it was found

#

Failed to create framebuffer...

#

Framebuffer is cooked, can that be related to kernel config?

#

@dense zenith sorry for ping, but do you have any ideas?

bold quest
#

i'm curious if you were aware the functionally complete or capable kenrel config is provided as a default with the distro kernel packages

#

if you were lead to believe editing a kernel config was a rerquirement while using gentoo-kernel you can but it's not required and nvidia drivers should work fine with zero config changes required

south jetty
#

I don't use gentoo-kernel

#

I have stock 6.10.10 with localmodconfig from my arch setup

#

I will try default gentoo-kernel tomorrow

bold quest
#

if you werent using gentoo-kernel the provided config can be harvested and used with gentoo-sources

#

functional reference configs are helpful starting points

south jetty
#

Im not sure that my current config is not cooked, so i will go with dist kernel

bold quest
#

you can study how that is configured by loading that with menuconfig in a linux kernel source directory

#

make tea, read menuconfig section by section :)

south jetty
#

I have ~amd64 keyword enabled, so, again, i will try stock gentoo-kernel without any changes. It takes like 2-3 hours to compile, when defconfig or my localmodconfig took like 10 minutes

bold quest
#

i've stopped pursuing custom kernels for everything but I have several older gentoo-sources configs you could study and learn from on my github

south jetty
#

K, thank you

bold quest
#

those were also correctly to my standards at the time configred for uefi

south jetty
#

@glacial blaze sorry for ping man, i tried, sbverify and sbattach keep throwing segfaults