From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland
Date: Tue, 10 Jan 2017 21:57:30 +0000 [thread overview]
Message-ID: <bug-99353-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1228 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bug ID: 99353
Summary: Kaveri 7400K shows random colored noise instead of GUI
in X or Wayland
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: vedran@miletic.net
QA Contact: dri-devel@lists.freedesktop.org
I have a Kaveri 7400K on ASRock FM2A58M-VG3+. Running Fedora 25, KMS works and
it boots nicely, but instead of GDM running on Wayland, I get screen full of
colored noise. Using Xorg makes no difference.
Phoronix claims this APU worked in 2014[1]. It never worked for me with the
open source driver (previously not even KMS worked), however it worked
perfectly with fglrx last time I tried it.
I can try older Mesa and LLVM if that would be useful, but compiling it will
take a while.
[1] https://www.phoronix.com/scan.php?page=article&item=amd_apus_august&num=1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2706 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-01-10 21:57 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 21:57 bugzilla-daemon [this message]
2017-01-11 9:40 ` [Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland bugzilla-daemon
2017-06-26 12:40 ` bugzilla-daemon
2017-07-07 23:22 ` bugzilla-daemon
2017-07-07 23:23 ` bugzilla-daemon
2017-07-07 23:27 ` bugzilla-daemon
2017-07-08 11:51 ` bugzilla-daemon
2017-07-08 11:53 ` bugzilla-daemon
2017-07-08 11:59 ` bugzilla-daemon
2017-07-10 7:08 ` bugzilla-daemon
2017-07-13 12:47 ` bugzilla-daemon
2017-07-15 22:28 ` bugzilla-daemon
2017-07-15 23:29 ` bugzilla-daemon
2017-07-16 1:12 ` bugzilla-daemon
2017-07-30 9:42 ` bugzilla-daemon
2018-01-10 22:59 ` bugzilla-daemon
2018-01-11 21:39 ` bugzilla-daemon
2018-01-12 14:33 ` bugzilla-daemon
2018-01-12 22:53 ` bugzilla-daemon
2018-01-16 15:15 ` bugzilla-daemon
2018-01-26 2:16 ` bugzilla-daemon
2018-01-26 8:54 ` bugzilla-daemon
2018-01-29 6:54 ` bugzilla-daemon
2018-01-29 6:57 ` bugzilla-daemon
2018-01-29 7:59 ` bugzilla-daemon
2018-02-06 8:05 ` bugzilla-daemon
2018-02-06 8:20 ` bugzilla-daemon
2018-02-08 8:41 ` bugzilla-daemon
2018-02-08 9:31 ` bugzilla-daemon
2018-02-08 16:03 ` bugzilla-daemon
2018-02-13 12:38 ` bugzilla-daemon
2018-02-13 15:11 ` bugzilla-daemon
2018-02-13 15:26 ` bugzilla-daemon
2018-02-15 14:29 ` bugzilla-daemon
2018-02-15 14:30 ` bugzilla-daemon
2018-02-16 22:00 ` bugzilla-daemon
2018-02-17 3:17 ` bugzilla-daemon
2018-02-17 13:18 ` bugzilla-daemon
2018-02-19 6:38 ` bugzilla-daemon
2018-02-20 0:19 ` bugzilla-daemon
2018-02-22 2:51 ` bugzilla-daemon
2018-02-22 3:10 ` bugzilla-daemon
2018-02-22 3:17 ` bugzilla-daemon
2018-02-22 3:54 ` bugzilla-daemon
2018-02-22 3:55 ` bugzilla-daemon
2018-02-22 18:44 ` bugzilla-daemon
2018-02-23 0:35 ` bugzilla-daemon
2018-02-28 5:07 ` bugzilla-daemon
2018-03-01 10:53 ` bugzilla-daemon
2018-03-01 10:54 ` bugzilla-daemon
2018-03-01 11:18 ` bugzilla-daemon
2018-03-01 16:07 ` bugzilla-daemon
2018-03-01 16:07 ` bugzilla-daemon
2018-03-02 0:40 ` bugzilla-daemon
2018-03-02 0:44 ` bugzilla-daemon
2018-03-04 6:20 ` bugzilla-daemon
2018-03-04 18:49 ` bugzilla-daemon
2018-03-04 18:49 ` bugzilla-daemon
2018-03-07 12:39 ` bugzilla-daemon
2018-03-22 16:29 ` 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-99353-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.