[Asus K55DR] When VGA plugged into laptop, only one monitor working at a time

[lazanet]

Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=99784
Imgur post that explains problem: http://imgur.com/a/3kwiq

When my ASUS VW193 external monitor is connected to the VGA port of my laptop (AMD Radeon 7470m) internal laptop monitor stops working. Using the Unity Control Center I'm able to set laptop monitor as primary which disables external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04, 17.04 and 17.10 (develop branch) with same results.

However, if I plug the Asus monitor into the laptop via VGA, plug my Vox TV into the laptop via HDMI, and set the resolution to 1280x720, it displays fine on both the monitor and TV.

Also, the internal monitor and just HDMI together show properly.

However, if I adjust to 1080i, the above working dual screen configurations show a graphical glitch:
https://launchpadlibrarian.net/302517159/IMG_20170114_225834.jpg

WORKAROUND: Use Ubuntu 14.04 with fglrx.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.5.0-040500rc6-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Mar 5 04:32:48 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed
 virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
 virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b]
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff)
InstallationDate: Installed on 2016-02-18 (15 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK COMPUTER INC. K55DR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55DR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55DR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Mar 5 04:27:41 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.1-1ubuntu3
xserver.video_driver: radeon

[Timo Aaltonen (tjaalton)]

does kernel 4.4.0-12 help? it has backports from 4.5+

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Removed tag="trusty"

http://packages.ubuntu.com/search?keywords=xserver-xorg-video-amdgpu&searchon=names&suite=all&section=all

The version of amd-gpu in Wily is quite old (outdated).

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]

[lazanet (lazanet96)]

I reverted to Trusty with fglrx at the time, so I wasn't able to submit additional input.

Here is log file from live 16.10 usb from same machine: http://pastebin.com/aWeKJpfH
On print screen, both desktops are visible: http://imgur.com/a/Rj5rG
Yet laptop internal monitor shows no image http://imgur.com/a/qgxmE
Settings show all valid options http://imgur.com/a/aVewC

When switching screen modes (either by using fn keys, or settings), I am able to change which monitor is outputing image, but only one at the time (even though they are clearly configured).

I'm not sure whether mainline kernel would change anything, but I'm willing to test whatever feels necessary.

[penalvch (penalvch)]

lazanet, it would be much more helpful to test the latest version of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ (live is fine).

Also, please attach images/files uncompressed/untarred to this report (not pastebin, imgur, etc.) as this allows developers to review quicker.

[lazanet (lazanet96)]

I'm downloading daily image right now, so I'll be able to provide new tests later today.

[lazanet (lazanet96)]

Same problem occurs at 17.04 daily build (details tab shows 16.10 for some reason, even though lsbrelease reports right version string)

[penalvch (penalvch)]

lazanet, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[penalvch (penalvch)]

lazanet:
1) Could you please provide the full manufacturer and model of the external monitor?
2) What program are you using to adjust the laptop monitor to primary/secondary when the problem occurs?

[lazanet (lazanet96)]

Monitor is ASUS VW183
I'm using unity-control-center.

[lazanet (lazanet96)]

I realized that I haven't tested HDMI output on radeon driver (and 17.04 with mainline kernel), so I decided to test it out.
Initially, after plugging both VGA monitor (ASUS), and HDMI TV (VOX), HDMI and VGA outputs were showing image (however at 1080i, image was buggy and scrambled at TV screen) while internal monitor was off. After changing TV resolution to 1280x720 image was looking ok.

After changing resolution options, I was able to output image on both VGA and HDMI or internal monitor and HDMI (but never all three or VGA and internal monitor at the same time). So, except that 1080i glitch (which can be seen on provided image), HDMI would always be on and functioning.

Interestingly enough, even with same resolution options, VGA and Internal Monitor would work seemingly at random (at first setting of that resolution combination internal monitor would work and VGA wouldn't, but if I set same settings again later VGA would display image and internal wouldn't).

I know that you told me not to send logs, but I believe that they might be relevant (especially for HDMI@1080 bug).

[penalvch (penalvch)]

lazanet, to clarify, I never said don't send logs.

Despite this, the issue you are reporting is an upstream one. Could you please report this problem via https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon ?

Please provide a direct URL to your bug report once you have made it so that it may be tracked.

Thank you for your help.

[lazanet (lazanet96)]

Bug submitted @ https://bugs.freedesktop.org/show_bug.cgi?id=99784

[lazanet (lazanet96)]

[Copy/Pasted from freedesktop.org] After testing new version of kernel on Ubuntu 17.10 installation (wayland + systemd) I discovered by chance that after suspend and unsuspend (systemctl suspend), internal monitor starts displaying image and everything works (for the first time with radeon driver).

So as a workaround I used /etc/rc.local compatibility to trigger suspend after appropriate ring level is initialized during boot(sudo chmod +x /etc/rc.local is also required).

I tested same method with 14.04 LTS with no success (so I don't know exactly what upgrade made it work).