Summary: | x11/gnome3(-lite) & x11/gdm lags significantly on amdgpu | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Neel Chauhan <nc> |
Component: | Individual Port(s) | Assignee: | freebsd-gnome (Nobody) <gnome> |
Status: | Open --- | ||
Severity: | Affects Some People | CC: | Alexander88207, autofocus111, bpurgar, grahamperrin, michael, nc |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(gnome) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253746 |
Description
Neel Chauhan
2021-08-13 15:23:05 UTC
About this phrase:
>This also happens on the Envy with OpenBSD, on both GNOME 3 and 40, unless I use scfb. I don't know about Linux as I only booted non-GNOME-based distros via LiveUSB.
It is unclear. I meant that OpenBSD also lags, but scfb does not.
(In reply to Neel Chauhan from comment #0) > … lags significantly … not usable. … If you switch away from ttyv8 to e.g. ttyv1 (Control-Alt-F2) then back to ttyv8 (Alt-F9): is there a frame-by-frame effect, for each switch? The thing is, I no longer own an amdgpu-powered laptop. Since posting this bug report, I switched to an Intel-based 14" HP Spectre. Even then, only GNOME lagged. KDE and others did not. This was also the case with OpenBSD. Hi .. i have same problem and only workaround is to disable dri 3 in xorg.conf (use dri 2) Sadly, yes. At least for now. Maybe a future drm-kmod may fix this, know knows. But for now, just use DRI 2. (In reply to Neel Chauhan from comment #6) Thanks, is there any non-GNOME use case that benefits from DRI 2? I assume that <https://wiki.freebsd.org/GraphicsOld/DRI3> is stale but not yet <https://wiki.freebsd.org/CategoryStale> categorised as such. What's the simplest possible concise explanation of preferring 2 instead of 3? (I see <https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure#DRI3> but trying to interpret that in normal order, let alone in reverse (2 instead of 3), is quite mind-bending.) <https://www.freebsd.org/cgi/man.cgi?query=xorg.conf&sektion=5&manpath=FreeBSD-Ports#DRI_SECTION> directs readers to <https://dri.freedesktop.org/> but then (sorry) it's not clear which path to take; <https://dri.freedesktop.org/wiki/CategoryFaq/> is a scattering of things. Here in Bugzilla is not the best place for explanations, so maybe someone can edit something temporarily into <https://wiki.freebsd.org/Graphics> or <https://wiki.freebsd.org/Gnome> pending more formal edition into (I guess) <https://www.freebsd.org/gnome/>. Could this bug be https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253746 ? Could this bug be https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253746 ? It's probably that. Sorry for the delay in responding. I sadly cannot test this now, since my main laptop now has an Intel CPU/GPU: I no longer own the said Envy. System: Dell Precision T3500 w Intel X5650 CPU and ATI HD4850 GPU PCIE card OS: FreeBSD 13.1 (fresh install). Packages installed: xorg, drm-kmod, xf86-video-ati. Kernel graphics driver (from dmesg): [drm] Initialized radeon 2.50.0 20080528 Xorg graphics driver (from Xorg log): radeon Test1: Installed KDE5/SDDM and get proper graphical login and hardware accelerated graphics in desktop environment. Test2: Installed Gnome422/GDM and get blank login screen w active mouse pointer. Disabling DRI3 (DRI2 only) and now able to access desktop but gnome reports software rendering. Observed some display artifacts after a few minutes. So I can confirm this issue also affects and older GPU running the radeon driver. Saved xorg and system message logs and can post if anyone wants to see them. |