Comment=
# 8
on bug 68075<=
/a>
from Pasi K=C3=A4rkk=C3=A4inen
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 D=
VI
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 nou=
veau
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 fo=
cus
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 a=
ll
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).