[Bug 33438] New: Blank display and locked monitor with KMS and HDMI monitr

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 24 15:14:19 PST 2011


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

           Summary: Blank display and locked monitor with KMS and HDMI
                    monitr
           Product: xorg
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: kam1kaz3 at gmail.com
         QAContact: xorg-team at lists.x.org


Created an attachment (id=42415)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=42415)
Xorg and dmesg logs using HDMI and DVI

My graphics card is a Sapphire Radeon 3870 HD, with 2 DVI outputs, and I have 2
monitors; a Samsung one that has VGA, DVI and HDMI inputs, and a Philips one
that has only a VGA input.

Let my Philips monitor be connected to the first port of the card using a
DVI->VGA cable.

Now if I have the Samsung connected to the 2nd port using a DVI->DVI cable,
everything works fine, but if I connect it using a DVI->HDMI cable, at the
moment KMS initializes it displays a blank image, doesn't go into stand-by
mode, doesn't display any info, and pressing it's buttons don't do anything (no
menus).
Having it connected to the 1st port and/or just this one monitor shows same
behavior.

The Philips monitor keeps displaying the boot processs normally and it reaches
the GDM login screen just fine, so I know that xorg isn't crashing.

I collected some logs with drm.debug=15 first the Samsung connected using HDMI,
and then with it connected using the DVI port. These are attached.

I have been experiencing this bug since the early stages of KMS development, so
it's nothing new. With KMS disabled everything works fine.

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


More information about the xorg-driver-ati mailing list