From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204725] black screen
Date: Sun, 01 Sep 2019 08:53:35 +0000 [thread overview]
Message-ID: <bug-204725-2300-KK2YbCCRbh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204725-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #35 from Dmitri Seletski (drjoms@gmail.com) ---
we got some progress. Or may be not. Since I suspect original issue is still
not solved. Still get black screen when amdgpu is loaded. This time, however, I
can start Xorg, with no 3d or 2d acceleration, but not using VESA driver, but
using AMDGPU.
My guess is, we fixed second problem, I did not know existed. Which is good all
the same.
Because I had several versions of LLVM, older one was used by default and only
newer was showing up as installed by portage(gentoo packaging system). It shows
only last installed. Shame on me, I hsould have known better. To my defence,
there are very a few packages where you have several versions of same package
installed and they usually can be chosed using 'eselect' command.
eselect |grep llvm
(nothing)
this is now me sitting under:
uname -a
Linux (none)dimko's Desktop 5.3.0-rc6+ #8 SMP PREEMPT Sun Sep 1 07:39:44 IST
2019 x86_64 AMD Ryzen 5 1600 Six-Core Processor AuthenticAMD GNU/Linux
glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
glxgears
Error: couldn't get an RGB, Double-buffered visual
see new dmesg(nothing interesting there)
and new Xorg.log files in next message.(a lot of interesting there)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-01 8:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 22:23 [Bug 204725] New: black screen bugzilla-daemon
2019-08-28 22:25 ` [Bug 204725] " bugzilla-daemon
2019-08-28 22:34 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-28 22:35 ` bugzilla-daemon
2019-08-29 2:36 ` bugzilla-daemon
2019-08-30 16:27 ` bugzilla-daemon
2019-08-31 4:31 ` bugzilla-daemon
2019-08-31 4:55 ` bugzilla-daemon
2019-08-31 17:58 ` bugzilla-daemon
2019-08-31 19:52 ` bugzilla-daemon
2019-08-31 19:56 ` bugzilla-daemon
2019-08-31 19:57 ` bugzilla-daemon
2019-08-31 20:39 ` bugzilla-daemon
2019-08-31 20:53 ` bugzilla-daemon
2019-08-31 20:55 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:56 ` bugzilla-daemon
2019-08-31 20:57 ` bugzilla-daemon
2019-08-31 21:09 ` bugzilla-daemon
2019-08-31 21:11 ` bugzilla-daemon
2019-08-31 21:13 ` bugzilla-daemon
2019-08-31 21:38 ` bugzilla-daemon
2019-08-31 22:03 ` bugzilla-daemon
2019-08-31 22:07 ` bugzilla-daemon
2019-08-31 22:08 ` bugzilla-daemon
2019-09-01 0:43 ` bugzilla-daemon
2019-09-01 0:48 ` bugzilla-daemon
2019-09-01 7:17 ` bugzilla-daemon
2019-09-01 7:20 ` bugzilla-daemon
2019-09-01 7:22 ` bugzilla-daemon
2019-09-01 7:25 ` bugzilla-daemon
2019-09-01 7:30 ` bugzilla-daemon
2019-09-01 7:35 ` bugzilla-daemon
2019-09-01 7:40 ` bugzilla-daemon
2019-09-01 8:53 ` bugzilla-daemon [this message]
2019-09-01 8:59 ` bugzilla-daemon
2019-09-01 9:04 ` bugzilla-daemon
2019-09-01 9:04 ` bugzilla-daemon
2019-09-01 9:20 ` bugzilla-daemon
2019-09-01 9:29 ` bugzilla-daemon
2019-09-01 9:29 ` bugzilla-daemon
2019-09-01 17:08 ` bugzilla-daemon
2019-09-01 18:28 ` bugzilla-daemon
2019-09-02 10:42 ` bugzilla-daemon
2019-09-02 17:26 ` bugzilla-daemon
2019-09-02 18:06 ` bugzilla-daemon
2019-09-02 20:37 ` bugzilla-daemon
2019-09-03 21:17 ` bugzilla-daemon
2019-09-03 21:23 ` bugzilla-daemon
2019-09-03 21:25 ` bugzilla-daemon
2019-09-03 21:28 ` bugzilla-daemon
2019-09-03 21:30 ` bugzilla-daemon
2019-09-04 16:20 ` bugzilla-daemon
2019-10-05 11:49 ` bugzilla-daemon
2019-10-07 14:24 ` bugzilla-daemon
2019-10-07 16:11 ` bugzilla-daemon
2019-10-14 20:57 ` bugzilla-daemon
2019-10-14 20:58 ` bugzilla-daemon
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=bug-204725-2300-KK2YbCCRbh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).