Nouveau - Feb 2011 - [Bug 33967] New: No image on a VGA screen attached to DVI with a dvi to vga adaptor on NVa3 card..

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

           Summary: No image on a VGA screen attached to DVI with a dvi to
                    vga adaptor on NVa3 card..
           Product: xorg
           Version: 7.6
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: GatoLoko at gmail.com
         QAContact: xorg-team at lists.x.org


Created an attachment (id=42994)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42994)
dmesg log

On a dualhead system, the second screen (a VGA CRT with a DVI adaptor) never
shows anything, remaining in power save mode since boot until shutdown.

I disconnected the other screen, forcing this one to show the bios and boot
messages, and once while the kernel is loading, the screen goes off. The system
is reachable through ssh and seems to be working right.

When both screens are connected, xrandr shows info about both of them. I can
change resolutions on both of them, change the refresh rate on both of them,
... but no image on the screen connected to DVI.

Booting windows, dualhead works, and both screens show proper
images/resolutions/refresh.

Looking at xrandr output, it seems the connectors naming is wrong.
The screen connected to VGA is shown as connected to "DVI-I-1" and the
one
connected to DVI is shown as connected to "VGA-1"

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

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

--- Comment #1 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-06
09:11:06 PST ---
Created an attachment (id=42995)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42995)
lspci output

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

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

--- Comment #2 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-06
09:11:45 PST ---
Created an attachment (id=42996)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42996)
xrandr output

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

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

--- Comment #3 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-06
09:12:20 PST ---
Created an attachment (id=42997)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42997)
Xorg log

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

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

--- Comment #4 from Dragos Delcea <dragos.delcea at gmail.com> 2011-02-07
05:13:55 PST ---
just finished submitting a bug report to the gentoo bugzilla about the same
behaviour: upon boot the internal display goes blank at KMS activation time,
but external monitor works - xrandr reports both working and X (of course)
thinks it too.
(http://bugs.gentoo.org/show_bug.cgi?id=353957)

in my case the situation is a bit clearer: it all worked up to and including
2.6.36, so it's a 2.6.37 regression.

also, one more hint can be found in the fact that between the working and
non-working xrandr output there are differences in refresh rates for the
internal, non-working display.
my hw is a bit different (see the gentoo bug for details)

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

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

--- Comment #5 from Maarten Maathuis <madman2003 at gmail.com> 2011-02-07
12:34:46 PST ---
Taken from dmesg log:

Found Display Configuration Block version 4.0
Raw DCB entry 0: 02000300 00020030
Raw DCB entry 1: 01011312 00020030
Raw DCB entry 2: 01011310 00000000
Raw DCB entry 3: 02022362 00020010
Raw DCB entry 4: 0000000e 00000000
DCB connector table: VHER 0x40 5 16 4
0: 0x00001030: type 0x30 idx 0 tag 0x07
1: 0x00000100: type 0x00 idx 1 tag 0xff
2: 0x00002261: type 0x61 idx 2 tag 0x08

Conclusion:

It seems that the DCB connector table or DCB output table is wrong. VGA
connector is linked to an digital and analog output, while the DVI is only
linked to an analog. Very small chance it's being misparsed, but more likely
it's a broken DCB connector table.

I'll try to see if can get the attention of Ben Skeggs, maybe you need a
quirk
for this broken bios table.

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

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

--- Comment #6 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-13
07:57:45 PST ---
Created an attachment (id=43317)
 View: https://bugs.freedesktop.org/attachment.cgi?id=43317
 Review: https://bugs.freedesktop.org/review?bug=33967&attachment=43317

Posible patch for wrong DCB table

I replied to the last bugzilla message by mail, but it doesn't show here, so
I'm adding it again.

I don't know if this is a proper fix or a piece of trash, so I wonder if
somebody can have a look at it and tell me how it looks, and whether it's
safe
to test it or I'm doing it wrong. Or just fix it so I see where i messed up.

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

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

Ra?l Soriano <GatoLoko at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #43317|0                           |1
        is obsolete|                            |

--- Comment #7 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-13
17:51:22 PST ---
Created an attachment (id=43327)
 View: https://bugs.freedesktop.org/attachment.cgi?id=43327
 Review: https://bugs.freedesktop.org/review?bug=33967&attachment=43327

Incomplete patch with working dualhead

The previous patch didn't even build (my mistake). This one builds and run,
dualhead works again, but both connectors are named DVI-I now, which is still
wrong.

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

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

Ra?l Soriano <GatoLoko at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #43327|0                           |1
        is obsolete|                            |

--- Comment #8 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-13
18:29:23 PST ---
Created an attachment (id=43328)
 View: https://bugs.freedesktop.org/attachment.cgi?id=43328
 Review: https://bugs.freedesktop.org/review?bug=33967&attachment=43328

XFX GT-240X-YA DCB connector quirk

Signed-of-by: Ra?l Soriano <GatoLoko at gmail.com>

Now it builds and works for me.

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

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

--- Comment #9 from Ben Skeggs <skeggsb at gmail.com> 2011-02-13 19:42:35
PST ---
Created an attachment (id=43329)
 View: https://bugs.freedesktop.org/attachment.cgi?id=43329
 Review: https://bugs.freedesktop.org/review?bug=33967&attachment=43329

Possible alternate fix: encoder quirks

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

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

Ben Skeggs <skeggsb at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #43329|0                           |1
        is obsolete|                            |

--- Comment #10 from Ben Skeggs <skeggsb at gmail.com> 2011-02-13 19:45:39
PST ---
Created an attachment (id=43330)
 View: https://bugs.freedesktop.org/attachment.cgi?id=43330
 Review: https://bugs.freedesktop.org/review?bug=33967&attachment=43330

Fixed version of encoder table quirk

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

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

--- Comment #11 from Ra?l Soriano <GatoLoko at gmail.com> 2011-02-14
07:13:08 PST ---
I've tested Ben's patch and it works nicely, surely in a better fashion
than my
own.

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

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

--- Comment #12 from Ra?l Soriano <GatoLoko at gmail.com> 2011-03-19
13:30:19 PDT ---
Review of attachment 43330:
 --> (https://bugs.freedesktop.org/review?bug=33967&attachment=43330)

Tested it for a while, works as it should.

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

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

Marcin Slusarz <marcin.slusarz at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

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