From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96470] [AMDGPU][CIK] PRIME doesn't work, X doesn't start at all (no screen found)
Date: Fri, 10 Jun 2016 01:14:48 +0000 [thread overview]
Message-ID: <bug-96470-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96470
Bug ID: 96470
Summary: [AMDGPU][CIK] PRIME doesn't work, X doesn't start at
all (no screen found)
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: shawn.starr@rogers.com
Created attachment 124431
--> https://bugs.freedesktop.org/attachment.cgi?id=124431&action=edit
Xorg Log file
Kernel: agd5f's drm-next-4.8-wip
Xorg: xorg-x11-server-1.18.3-2.fc24
AMDGPU DDX: git master
Intel DDX: xorg-x11-drv-intel-2.99.917-23.20160512.fc24.x86_64
Attached, Xorg log, kernel boot log.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2335 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:[~2016-06-10 1:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 1:14 bugzilla-daemon [this message]
2016-06-10 1:15 ` [Bug 96470] [AMDGPU][CIK] PRIME doesn't work, X doesn't start at all (no screen found) bugzilla-daemon
2016-06-10 1:15 ` bugzilla-daemon
2016-06-10 1:18 ` bugzilla-daemon
2016-06-10 1:18 ` bugzilla-daemon
2016-06-10 5:06 ` bugzilla-daemon
2016-06-10 5:12 ` bugzilla-daemon
2016-06-10 6:10 ` bugzilla-daemon
2016-06-10 8:13 ` bugzilla-daemon
2016-08-31 3:29 ` bugzilla-daemon
2016-08-31 3:59 ` 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-96470-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.