From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 68075] nouveau inconsistent changing output connector names in xrandr
Date: Tue, 20 Aug 2013 16:13:38 +0000 [thread overview]
Message-ID: <bug-68075-8800-MMV4JyDn1H@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68075-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 783 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68075
--- Comment #6 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
As far as I can see, everything's working totally fine from the kernel end.
There is one difference between the two "dvi plugged in at boot" cases, in that
in one, nouveau ends up as card0, in the other i915 does.
All the connectors seem fine, and are properly reporting status. There's
nothing funny in dmesg.
So... I think we should shift our attention to X. Can you attach your
Xorg.0.log for the same three cases? Although let's amend the first case ("no
dvi plugged in") to "no dvi plugged in at boot, then plugged in later" (since
that still functions, right).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1585 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-08-20 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:04 [Bug 68075] New: nouveau inconsistent changing output connector names in xrandr bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-68075-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-13 18:52 ` [Bug 68075] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 21:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 21:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 21:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 21:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-21 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 18:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 19:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 20:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 0:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 17:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 17:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 18:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 18:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 18:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-20 13:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-20 16:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-68075-8800-MMV4JyDn1H@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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