DE agnostic problems on login 18 January 2025, 22:42:00 I have an old laptop (Lenovo Y70-70) on which I wanted to install artix, but i've encountered a visual glitch on login that makes it unusable.First I tried with a KDE Plasma image, which got the glitch the moment SDDM started, after that I tried with xfce, which worked fine, installed properly, but upon update and reboot, a similar glitch happens, but only after entering credentials for an x11 session (wayland session just kicks me back to login).The visual glitch looks either like a starry sky with blue and pink dots, or pink/black barcodes, if that even says anything. Anyone know what's going on?
Re: DE agnostic problems on login Reply #1 – Yesterday at 01:05:28 What kind of GPU does this laptop have exactly, some NVIDIA GTX card?Asking because in general nvidia has some specific demands to work correctly.artist
Re: DE agnostic problems on login Reply #2 – Yesterday at 03:35:50 Quote from: Artist – on Yesterday at 01:05:28What kind of GPU does this laptop have exactly, some NVIDIA GTX card?Asking because in general nvidia has some specific demands to work correctly.artistYeah, it has a GTX 860M. The demands must be recent because the install images are both from august '24, and xfce works fine until it's updated, but KDE doesn't work at all (however I remember the '23 KDE iso worked).
Re: DE agnostic problems on login Reply #3 – Yesterday at 10:40:23 Wayland requirements for Nvidia are described here: https://wiki.archlinux.org/title/NVIDIA#Basic_supportIn case the problem persists then provide details about the installed related packages, setup, etc.artist
Re: DE agnostic problems on login Reply #4 – Yesterday at 14:32:43 Quote from: Artist – on Yesterday at 10:40:23Wayland requirements for Nvidia are described here: https://wiki.archlinux.org/title/NVIDIA#Basic_supportIn case the problem persists then provide details about the installed related packages, setup, etc.artist"fbdev is specifically a hard requirement on Linux 6.11 and later, but it is currently unclear whether this is intended behavior or a bug"This was it, thanks! Also explains the recency of the problem