Bug 57034 - [NVA0] second dp monitor stays powered off
Summary: [NVA0] second dp monitor stays powered off
Status: REOPENED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 21:37 UTC by Orion Poplawski
Modified: 2015-01-07 15:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (47.10 KB, text/plain)
2012-11-12 21:37 UTC, Orion Poplawski
no flags Details
Xorg.0.log (45.46 KB, text/plain)
2013-08-26 15:44 UTC, Orion Poplawski
no flags Details
dmesg (71.01 KB, text/plain)
2013-08-26 15:45 UTC, Orion Poplawski
no flags Details
dmesg (71.23 KB, text/plain)
2014-03-17 15:19 UTC, Orion Poplawski
no flags Details
Xorg log on boot (34.30 KB, text/plain)
2014-03-17 15:19 UTC, Orion Poplawski
no flags Details
Xorg log on restart of X server (38.47 KB, text/plain)
2014-03-17 15:19 UTC, Orion Poplawski
no flags Details
dmesg-3.17.7-300.fc21.x86_64 (66.10 KB, text/plain)
2015-01-07 15:52 UTC, Orion Poplawski
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Orion Poplawski 2012-11-12 21:37:17 UTC
Created attachment 69963 [details]
Xorg.0.log

02:00.0 VGA compatible controller: NVIDIA Corporation GT200GL [Quadro FX 4800] (rev a1)

System does not appear to recognize or be able to use the two display port connectors on this card.

# dmesg |grep drm
[    2.771310] [drm] Initialized drm 1.1.0 20060810
[    2.775685] [drm] nouveau 0000:02:00.0: Detected an NV50 generation card (0x0a0f00b1)
[    2.778295] [drm] nouveau 0000:02:00.0: Checking PRAMIN for VBIOS
[    2.849995] [drm] nouveau 0000:02:00.0: ... appears to be valid
[    2.849997] [drm] nouveau 0000:02:00.0: Using VBIOS from PRAMIN
[    2.850000] [drm] nouveau 0000:02:00.0: BIT BIOS found
[    2.850002] [drm] nouveau 0000:02:00.0: Bios version 62.00.25.01
[    2.850004] [drm] nouveau 0000:02:00.0: TMDS table version 2.0
[    2.850101] [drm] nouveau 0000:02:00.0: MXM: no VBIOS data, nothing to do
[    2.850103] [drm] nouveau 0000:02:00.0: DCB version 4.0
[    2.850105] [drm] nouveau 0000:02:00.0: DCB outp 00: 04000320 00000028
[    2.850106] [drm] nouveau 0000:02:00.0: DCB outp 01: 01000322 00020030
[    2.850107] [drm] nouveau 0000:02:00.0: DCB outp 02: 02132336 0f220d00
[    2.850108] [drm] nouveau 0000:02:00.0: DCB outp 03: 02132332 00020d00
[    2.850109] [drm] nouveau 0000:02:00.0: DCB outp 04: 01121336 0f220e00
[    2.850110] [drm] nouveau 0000:02:00.0: DCB outp 05: 01121332 00020e00
[    2.850111] [drm] nouveau 0000:02:00.0: DCB conn 00: 00001030
[    2.850113] [drm] nouveau 0000:02:00.0: DCB conn 01: 0000a146
[    2.850114] [drm] nouveau 0000:02:00.0: DCB conn 02: 00050246
[    2.850115] [drm] nouveau 0000:02:00.0: DCB conn 03: 00000360
[    2.850118] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 0 at offset 0xD0B6
[    2.872973] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 1 at offset 0xD39A
[    2.875818] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 2 at offset 0xE7FE
[    2.875824] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 3 at offset 0xE8FF
[    2.876832] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 4 at offset 0xE9BA
[    2.876833] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table at offset 0xEA1F
[    2.896837] [drm] nouveau 0000:02:00.0: 0xEA1F: Condition still not met after 20ms, skipping following opcodes
[    2.901853] [drm] nouveau 0000:02:00.0: Detected 1536MiB VRAM (GDDR3)
[    2.907334] [drm] nouveau 0000:02:00.0: 512 MiB GART (aperture)
[    2.955290] [drm] nouveau 0000:02:00.0: Off-chip encoder 6/1 unsupported
[    2.955292] [drm] nouveau 0000:02:00.0: Off-chip encoder 2/1 unsupported
[    2.955293] [drm] nouveau 0000:02:00.0: Off-chip encoder 6/0 unsupported
[    2.955294] [drm] nouveau 0000:02:00.0: Off-chip encoder 2/0 unsupported
[    2.957289] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    2.957291] [drm] No driver support for vblank timestamp query.
[    2.965008] [drm] nouveau 0000:02:00.0: 3 available performance level(s)
[    2.965011] [drm] nouveau 0000:02:00.0: 0: core 300MHz shader 600MHz memory 100MHz voltage 1050mV fanspeed 100%
[    2.965013] [drm] nouveau 0000:02:00.0: 2: core 400MHz shader 800MHz memory 300MHz voltage 1050mV fanspeed 100%
[    2.965015] [drm] nouveau 0000:02:00.0: 3: core 602MHz shader 1204MHz memory 800MHz voltage 1180mV fanspeed 100%
[    2.965017] [drm] nouveau 0000:02:00.0: c: core 399MHz shader 810MHz memory 297MHz voltage 1180mV
[    3.010759] [drm] nouveau 0000:02:00.0: MM: using CRYPT for buffer copies
[    3.084261] [drm] nouveau 0000:02:00.0: allocated 1600x1200 fb: 0x2c0000, bo ffff880134e45000
[    3.103452] drm: registered panic notifier
[    3.103457] [drm] Initialized nouveau 1.0.0 20120316 for 0000:02:00.0 on minor 0
[   29.907369] [drm] nouveau 0000:02:00.0: Failed to idle channel 4.
[   32.907403] [drm] nouveau 0000:02:00.0: Failed to idle channel 4.
[   35.907393] [drm] nouveau 0000:02:00.0: Failed to idle channel 4.
[   38.907465] [drm] nouveau 0000:02:00.0: Failed to idle channel 4.
[   41.907473] [drm] nouveau 0000:02:00.0: Failed to idle channel 4.
Comment 1 Ilia Mirkin 2013-08-25 03:29:54 UTC
Please retest with the latest kernel. I see two dcb outputs with dp, so they're definitely at least somewhat recognized. Take a look at /sys/class/drm/card*-*/status -- that should indicate what it sees.
Comment 2 Orion Poplawski 2013-08-26 15:44:02 UTC
Things are looking better with 3.10.9:

$ ls /sys/class/drm/card*-*/status
/sys/class/drm/card0-DP-1/status  /sys/class/drm/card0-DP-2/status  /sys/class/drm/card0-DVI-I-1/status
$ cat /sys/class/drm/card*-*/status
connected
connected
disconnected

But I'm not getting any output on DP-2 - monitor is in power save but I don't know why.

$ xrandr
Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200      60.0*+
   1280x1024      75.0     60.0
   1152x864       75.0
   1024x768       75.1     60.0
   800x600        75.0     60.3
   640x480        75.0     60.0
   720x400        70.1
DP-2 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200      60.0*+
   1280x1024      75.0     60.0
   1152x864       75.0
   1024x768       75.1     60.0
   800x600        75.0     60.3
   640x480        75.0     60.0
   720x400        70.1
Comment 3 Orion Poplawski 2013-08-26 15:44:29 UTC
Created attachment 84660 [details]
Xorg.0.log
Comment 4 Orion Poplawski 2013-08-26 15:45:18 UTC
Created attachment 84661 [details]
dmesg
Comment 5 Ilia Mirkin 2013-08-26 15:54:45 UTC
Things are looking up :)

What happens if you do

xrandr --output DP-2 --off
xrandr --output DP-2 --auto

Alternatively, what happens if you physically unplug and then re-plug the second DP monitor?
Comment 6 Orion Poplawski 2013-08-26 15:59:57 UTC
(In reply to comment #5)
> Things are looking up :)
> 
> What happens if you do
> 
> xrandr --output DP-2 --off
> xrandr --output DP-2 --auto

Then I seem to lose the second monitor (screen size shrinks):

Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 8192 x 8192
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200      60.0*+
   1280x1024      75.0     60.0
   1152x864       75.0
   1024x768       75.1     60.0
   800x600        75.0     60.3
   640x480        75.0     60.0
   720x400        70.1
DP-2 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200      60.0*+

> Alternatively, what happens if you physically unplug and then re-plug the
> second DP monitor?

Essentially the same.
Comment 7 Orion Poplawski 2013-08-26 16:06:57 UTC
Seems to be the same with 3.11.0-0.rc6.git4
Comment 8 Ilia Mirkin 2014-02-11 02:54:02 UTC
Could you test kernel 3.8.x? There another bug (#67628) which bisected a similar-sounding DP issue to commit 5cc027f6b1, which first appeared in 3.9-rc1.
Comment 9 Ilia Mirkin 2014-02-14 19:37:25 UTC
(In reply to comment #8)
> Could you test kernel 3.8.x? There another bug (#67628) which bisected a
> similar-sounding DP issue to commit 5cc027f6b1, which first appeared in
> 3.9-rc1.

http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html

This patch fixed issues for the other users. Can you give it a shot?
Comment 10 Orion Poplawski 2014-02-14 20:44:51 UTC
Sorry for the delay - things have been working fine since at least 3.12.6-300.fc20.  Thanks!
Comment 11 Orion Poplawski 2014-03-17 15:18:09 UTC
Well, it was working fine until I updated my BIOS, now this appears to have returned.  I am able to get the second monitor to turn on though by killing and restarting the X server.
Comment 12 Orion Poplawski 2014-03-17 15:19:07 UTC
Created attachment 95945 [details]
dmesg

dmesg including X restart
Comment 13 Orion Poplawski 2014-03-17 15:19:34 UTC
Created attachment 95946 [details]
Xorg log on boot
Comment 14 Orion Poplawski 2014-03-17 15:19:56 UTC
Created attachment 95947 [details]
Xorg log on restart of X server
Comment 15 Orion Poplawski 2014-04-16 15:08:17 UTC
Now with 3.13 kernels, the DP-1 monitor is in power save on boot.  Restarting X doesn't help anymore.  xrandr reports it as active though.  Need to disable and re-enable to get it to come on.  
kernel-3.13.10-200.fc20.x86_64
Comment 16 Ilia Mirkin 2014-06-11 23:35:27 UTC
There is a substantial DP rework bound for 3.16. Can you give http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next a shot?
Comment 17 Orion Poplawski 2014-06-25 16:34:09 UTC
Still the same with that (which reports a version of 3.15.0_rc8+-2).
Comment 18 Orion Poplawski 2015-01-07 15:52:52 UTC
Created attachment 111923 [details]
dmesg-3.17.7-300.fc21.x86_64

Still the same with 3.17.7.  DP-2 is in power save.  xrandr can't get it to come back.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.