all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: X/GDM fails on linux 5.0.7 AMD Radeon RX 580 after system reconfigure
Date: Thu, 9 May 2019 17:22:21 -0600	[thread overview]
Message-ID: <20190509232220.rxg37sdrtla7y3hr@cf0> (raw)
In-Reply-To: <871s17fwmp.fsf@ambrevar.xyz>

I can confirm this exact same issue with the same video card, RX 580, and my
last attempt to update pulled in kernel 5.0.13. When the login screen shows up
the screen is horribly corrupt, nothing is even recognizable as being a part of
the normal login screen, just random colored lines all over the screen.
I first experienced the issue at the release of Guix v1.0.0, but wasn't sure if
I should wait before reporting since I couldn't be sure if it was a guix
specific issue or something else.

Here is what I have discovered:
* I doubt the issue is either caused by GDM itself or the kernel, because after
  updating from a working generation (but without restarting my machine) if I
  attempt to play a video in mpv (or start a game) the same graphical artifacts
  appear, but only in that 1 window.
* I have attempted to upgrade individual applications while using
  "package-input-rewriting" to replace their dependencies on Mesa 18.3.5 with
  18.3.1 (the version they're using on my working generation) and I can confirm
  that the replacement succeeded with "ldd", however they still receive
  graphical artifacts.
* I have successfully managed to run an updated copy of mpv without artifacts by
  using LD_PRELOAD to force it to point to the exact copy of libGL.so.1 used by
  mpv on my working generation.

This leads me to believe that the problem lies somewhere in Mesa (which contains
libGL.so.1). However, the issue doesn't seem to be just the version of Mesa
since mpv still had corrupt video when built to use the older version of Mesa,
but had no corrupt video when forced to link to the exact copy of libGL.so.1
from a previously working generation.

Note: mpv was merely used as a test so I didn't have to constantly restart my
machine. However, generations which resulted in corrupt video in mpv (and games)
always resulted in corrupt video in GDM if I also rebooted into that generation.

  reply	other threads:[~2019-05-09 23:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 15:58 X/GDM fails on linux 5.0.7 AMD Radeon RX 580 after system reconfigure Pierre Neidhardt
2019-05-09 23:22 ` ison [this message]
2019-05-10  0:34   ` Danny Milosavljevic
2019-05-10  1:59     ` ison
2019-05-10  2:53       ` Danny Milosavljevic
2019-05-10  4:59         ` ison
2019-05-10  7:46           ` Pierre Neidhardt
2019-05-10 12:11           ` Marius Bakke
2019-05-10 12:33             ` Pierre Neidhardt
2019-05-10 12:36               ` Marius Bakke
2019-05-10 12:46                 ` Pierre Neidhardt
2019-05-14  9:25                   ` Pierre Neidhardt
2019-05-10 21:07             ` ison
2019-05-11  2:20               ` ison
2019-05-11  7:44                 ` Giovanni Biscuolo
2019-05-13  9:51                   ` Pierre Neidhardt
2019-05-10 12:12 ` Boris A. Dekshteyn
2019-05-24 10:26   ` Pierre Neidhardt
2019-05-26  0:24     ` ison
2019-05-26  7:50       ` Pierre Neidhardt
2019-05-29 16:58         ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190509232220.rxg37sdrtla7y3hr@cf0 \
    --to=ison@airmail.cc \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.