[Bug 18564] DVI display detected, but won't turn on (tried latest git)

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=18564





--- Comment #21 from Tyson Whitehead <twhitehead at gmail.com>  2009-12-10 12:36:18 PST ---
Hi Alex,

First of all, thank you very much for your continued work on this.  I'm pleased
to report that I have some good news.  I just tried the latest git (46630d) and
it now mostly works.  While it does come on at startup despite being plugged
in, I can now get it to turn on using xrandr.  Full details are as follows.

To reiterate a bit, my laptop has a VGA and an HDMI port on it. I plug my DVI
monitor into it the HDMI one via a HDMI -> DVI cable.  I also understand that
the docking bay has a DVI port, however, I don't have this piece of equipment.

The XOrg log file and XRandR show that four ports are detected.

(II) RADEON(0): Port0:
  XRANDR name: VGA-0
  Connector: VGA
  CRT1: INTERNAL_KLDSCP_DAC1
  DDC reg: 0x7e40
(II) RADEON(0): DispPath index = 0: usConnObjectId = 3105 (id=05,num=1,type=3)
(II) RADEON(0):         GraphicObjIds index = 0: usConnObjectId = 2115
(id=15,num=1,type=2)

(II) RADEON(0): Port1:
  XRANDR name: HDMI-0
  Connector: HDMI-A
  DFP1: INTERNAL_KLDSCP_TMDS1
  DDC reg: 0x7e50
(II) RADEON(0): DispPath index = 1: usConnObjectId = 310c (id=0c,num=1,type=3)
(II) RADEON(0):         GraphicObjIds index = 0: usConnObjectId = 2213
(id=13,num=2,type=2)
(II) RADEON(0):         GraphicObjIds index = 1: usConnObjectId = 4101
(id=01,num=1,type=4)

(II) RADEON(0): Port2:
  XRANDR name: DVI-0
  Connector: DVI-D
  DFP2: INTERNAL_KLDSCP_TMDS1
  DDC reg: 0x7e50
(II) RADEON(0): DispPath index = 2: usConnObjectId = 3104 (id=04,num=1,type=3)
(II) RADEON(0):         GraphicObjIds index = 0: usConnObjectId = 2113
(id=13,num=1,type=2)
(II) RADEON(0):         GraphicObjIds index = 1: usConnObjectId = 4101
(id=01,num=1,type=4)

(II) RADEON(0): Port3:
  XRANDR name: LVDS
  Connector: LVDS
  LCD1: INTERNAL_LVTM1
  DDC reg: 0xac0
(II) RADEON(0): DispPath index = 3: usConnObjectId = 310e (id=0e,num=1,type=3)
(II) RADEON(0):         GraphicObjIds index = 0: usConnObjectId = 210f
(id=0f,num=1,type=2)

I added some debugging code to dump the object ids, and we can see the HDMI-0
port is the only one being detected as a linkb port (the encoder has num=2). 
Indeed, as long as DVI-0 is turned off, running "xrandr --output HDMI-0 --auto"
and "xrandr --output HDMI-0 --off" turns on and off the display as it should.

The strange thing now is, if I plug in the display before starting up, XOrg
chooses to begin with DVI-0 enabled and HDMI-0 disabled.  As XRandR shows

XOrg.Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 1920 x 1920
VGA-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected (normal left inverted right x axis y axis)
   1920x1200      60.0 +
   ... (and a bunch more modes) ...
DVI-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm
x 324mm
   1920x1200      60.0*+
   ... (and a bunch more modes) ...
LVDS connected 1680x1050+0+0 (normal left inverted right x axis y axis) 331mm x
207mm
   1680x1050      60.1*+   60.0  
   ... (and a bunch more modes) ...

So I then always have to manually turn on off DVI-0 using "xrandr --output
DVI-0 --off" and then turn on HDMI-0 using "xrandr --output HDMI-0 --auto" in
order to get my display to come on.  If I don't first turn off DVI-0, then I
get the the error message "xrandr: cannot find crtc for output HDMI-0".

I've attached a full XOrg log file of just starting up XOrg and then shutting
it back down in case this will shed some light on this situation.

Again, thanks again for your continued work on this.  I'm pretty excited to
have it mostly working now.

Cheers!  -Tyson


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.