From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104206] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
Date: Mon, 11 Dec 2017 17:37:38 +0000 [thread overview]
Message-ID: <bug-104206-502-eVBUy6EMq5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104206-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104206
--- Comment #8 from Andrew <formisc@gmail.com> ---
Correct you are about _not_ disabling the "accel". I was trying to figure
out what is breaking X this time around (i have a long thread on forums
trying to get amdgpu to work on this laptop).
I run on init3. And use "startx" when logged in as root. (Usually im on
init 5, but on all prior kernels to 4.15rc2 i didnt even got to see
terminals , just a black screen).
On Dec 11, 2017 11:10, <bugzilla-daemon@freedesktop.org> wrote:
> *Comment # 7 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c7> on
> bug 104206 <https://bugs.freedesktop.org/show_bug.cgi?id=104206> from
> Michel Dänzer <michel@daenzer.net> *
>
> (In reply to Andrew from comment #6 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c6>)> the X doesn't hard crash when i turn an acceleration off.
>
> Normally you'd want Option "Accel" "off" to disable accleration, not
> "AccelMethod" "none".
>
> > X still doesn't work - just exists back to the terminal.
>
> The Xorg log doesn't show any problem anymore, so it sounds like that's an X
> client session issue now. How exactly are you trying to start X?
>
> ------------------------------
> You are receiving this mail because:
>
> - You reported the bug.
>
>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3748 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 prev parent reply other threads:[~2017-12-11 17:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 3:15 [Bug 104206] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! bugzilla-daemon
2017-12-11 11:18 ` bugzilla-daemon
2017-12-11 11:24 ` bugzilla-daemon
2017-12-11 13:24 ` bugzilla-daemon
2017-12-11 15:32 ` bugzilla-daemon
2017-12-11 15:33 ` bugzilla-daemon
2017-12-11 15:48 ` bugzilla-daemon
2017-12-11 16:06 ` bugzilla-daemon
2017-12-11 16:09 ` bugzilla-daemon
2017-12-11 17:37 ` bugzilla-daemon [this message]
2017-12-14 20:11 ` bugzilla-daemon
2017-12-14 20:12 ` bugzilla-daemon
2017-12-14 20:14 ` bugzilla-daemon
2017-12-14 20:23 ` bugzilla-daemon
2017-12-14 20:33 ` bugzilla-daemon
2017-12-15 0:09 ` bugzilla-daemon
2017-12-15 8:39 ` bugzilla-daemon
2017-12-21 0:04 ` bugzilla-daemon
2017-12-21 0:35 ` bugzilla-daemon
2018-06-16 16:29 ` bugzilla-daemon
2018-08-11 16:56 ` bugzilla-daemon
2018-08-13 19:44 ` bugzilla-daemon
2019-01-01 21:20 ` bugzilla-daemon
2019-04-17 8:19 ` bugzilla-daemon
2019-04-17 8:21 ` bugzilla-daemon
2019-05-18 22:29 ` bugzilla-daemon
2019-09-03 16:34 ` bugzilla-daemon
2019-11-19 8:27 ` 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-104206-502-eVBUy6EMq5@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 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).