[Bug 68075] nouveau inconsistent changing output connector names in xrandr - bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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: Wed, 21 Aug 2013 19:00:58 +0000	[thread overview]
Message-ID: <bug-68075-8800-b5Bd7R2A88@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68075-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

[-- Attachment #1.1: Type: text/plain, Size: 1661 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=68075

--- Comment #8 from Pasi Kärkkäinen <pasik-X3B1VOXEql0@public.gmane.org> ---
Xorg logs (also with dmesg and xrandr output) attached.

Summary about each test-case:

01-dvi-not-connected-at-boot-but-is-connected-later:
- DVI monitor is not connected to nouveau at boot time, but I connect the DVI
cable later while in Xorg session.
- xrandr shows nouveau outputs as DP-1, DP-2 and DP-3.
- I am able to successfully enable and disable DVI monitor connected to nouveau
adapter.
- xrandr shows correct connected/disconnected state for the DVI output.
- Graphics on the DVI monitor are corrupted, for example moving xterm around
the DVI display leaves trace of the xterm contents behind, but let's not focus
on that on this bug :) it kind of works.

02-dvi-connected-at-boot-no-nouveau-outputs-detected-in-xrandr:
- DVI cable is connected to nouveau at boot time.
- xrandr does *not* show any nouveau outputs, so it's not possible to
enable/disable DVI monitor.
- DVI monitor shows black/white corrupted pattern, even when it should be all
empty/black in this case because it's not in use.
- Screenshot of the DVI monitor included in the .tar.gz.

03-dvi-connected-at-boot-nouveau-outputs-detected-as-displayport-in-xrandr:
- DVI cable is connected to nouveau at boot time.
- xrandr shows nouveau outputs as DisplayPort-0, DisplayPort-1 and
DisplayPort-2.
- Trying to enable DVI monitor connected to nouveau results in hard kernel
crash (but we have the other bug open about the kernel crash issue).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2456 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau