Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A amd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,280
    • Issues 1,280
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drm
  • amd
  • Issues
  • #772

Closed
Open
Created Feb 12, 2017 by Bugzilla Migration User@bugzilla-migration

AMD 7470m When VGA plugged into laptop, only one monitor working at a time

Submitted by laz..@..il.com

Assigned to Default DRI bug account

Link to original bug (#99784)

Description

Monitors are correctly reported in xrandr, however when both VGA (ASUS VW193) and internal laptop monitor (ASUS K55DR) are connected, image is only shown on one screen at the time. When HDMI output is connected (another monitor or tv) image is displayed seemingly random (either both HDMI and VGA output image, or only VGA, or internal monitor and HDMI - but never all three or VGA and internal monitor at the same time). Also at 1080i screen glitches (as seen on ubuntu bug report).

Hardware is functional under Windows or fglrx drivers

Original issue was reported @ launchpad.net here https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441
That bug report contains log files from xOrg, and images that could better explain bug that is affecting me (as I'm not native speaker, if that isn't obvious enough :)). If necessary I can provide more logs from latest mainline kernel.

Last kernel version which I tested (and reproduced bug) was mainline Ubuntu 4.10.0-041000rc7-lowlatency

Assignee
Assign to
Time tracking