[Bug 89155] Dual monitor setup does not initialize

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 1904 bytes --]

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

            Bug ID: 89155
           Summary: Dual monitor setup does not initialize
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adam.reichold@t-online.de

Created attachment 113508
  --> https://bugs.freedesktop.org/attachment.cgi?id=113508&action=edit
journalctl -b | grep "\[drm"

I am running Arch Linux on an AMD A6-3500 with Radeon HD 6530D graphics on an
Gigabyte A55M-S2V mainboard. I just received updated X server to version 1.17.1
together with a rebuilt version 7.5.0 of the XFree86 ATI driver with the kernel
staying at 3.18.6.

I do have two Samsung monitors connected to the system, one via DVI and one via
VGA. This setup always initialized unreliably and I had to manually add modes
for the VGA-connected monitor using

xrandr --newmode "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059
1089 -hsync +vsync
xrandr --addmode VGA-0 "1680x1050_60.00"
xrandr --output VGA-0 --mode "1680x1050_60.00"

for it to work at all. But after the update described above, the two monitors
never initialize properly anymore. Before the update, I sometimes had to
power-cycle (meaning switch off power not just a reboot) but it did eventually
work after two or three tries.

The reason I am reporting this as a Radeon DRM issue instead of an X server
problem is that my system log contains errors from the DRM driver about
"channel eq" and "clock recovery". I attached those logs grepped for "[drm".

Thank for your help and please tell me if I can provide any further information
to help diagnose this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3361 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 321 bytes --]

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

--- Comment #1 from Adam Reichold <adam.reichold@t-online.de> ---
Created attachment 113509
  --> https://bugs.freedesktop.org/attachment.cgi?id=113509&action=edit
journalctl -b | grep "\[drm"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1250 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 289 bytes --]

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

--- Comment #2 from Adam Reichold <adam.reichold@t-online.de> ---
Maybe as a clarification: Both monitors always initialize properly when only
one is connected.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1039 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 407 bytes --]

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

--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Adam Reichold from comment #2)
> Maybe as a clarification: Both monitors always initialize properly when only
> one is connected.

When only one is connected at boot time?  If so does it matter which one?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1225 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]

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

--- Comment #4 from Adam Reichold <adam.reichold@t-online.de> ---
(In reply to Alex Deucher from comment #3)
> (In reply to Adam Reichold from comment #2)
> > Maybe as a clarification: Both monitors always initialize properly when only
> > one is connected.
> 
> When only one is connected at boot time?  If so does it matter which one?

If at boot time, only one monitor is connected, then it does initialize
properly. This is true for both monitors, i.e. VGA-only works and DVI-only
works, but not both at the same time. (It also works correctly if I boot using
only one monitor and attach the second one later.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1620 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 879 bytes --]

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

--- Comment #5 from Adam Reichold <adam.reichold@t-online.de> ---
I had some more time to test this (now on kernel 4.1.4 and X server 1.17.2) and
have made two hopefully useful observations:

* The Catalyst driver (version 15.7) is always able to initialize the setup
even though VGA-connected monitor seems to always "flicker" two times before
reaching the final mode.

* I have found a somewhat reliable workaround to use with the free driver: By
adding

xrandr --output VGA-0 --off

before

xrandr \
    --output VGA-0 --preferred --primary \
    --output DVI-0 --preferred --rotate left --right-of VGA-0

to my .xinitrc, the system will properly initialize both displays even though
the first command seems to take around two seconds to complete.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1639 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 610 bytes --]

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

--- Comment #6 from Adam Reichold <adam.reichold@t-online.de> ---
Maybe of interest w.r.t this: Running kernel 4.3.3. by now, I found a seemingly
reliable workaround, i.e. if the VGA-connected monitor does not initialize
after boot, it will always properly initialize when I put the system into
suspend-to-memory and wake it up again immediately after that. (But the
VGA-connected monitor will sometimes go dark for a few seconds some time after
it initialized for the first time.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1360 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 89155] Dual monitor setup does not initialize

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]

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

Martin Peres <martin.peres@free.fr> changed:

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

--- Comment #7 from Martin Peres <martin.peres@free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/583.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2333 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel