Bug 93270 - Only one of LVDS and VGA-0 work on HP Pavilion m6 with Radeon HD 7660G
Summary: Only one of LVDS and VGA-0 work on HP Pavilion m6 with Radeon HD 7660G
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-06 10:18 UTC by Suren Karapetyan
Modified: 2019-11-19 09:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xrandr --verbose output (11.11 KB, text/plain)
2015-12-07 08:07 UTC, Suren Karapetyan
no flags Details
xorg log (56.06 KB, text/plain)
2015-12-07 08:08 UTC, Suren Karapetyan
no flags Details

Description Suren Karapetyan 2015-12-06 10:18:18 UTC
When I attach an external monitor to my laptop and put it next to the internal one using xrandr, the internal monitor goes blank.
If I then disable the external monitor, the internal one starts working.
Sometimes (after a lot of switching), they both go blank.  Weren't able to make them both work at the same time.
Based on the logs, the system thinks that both outputs are working (the screen size gets increased to fit both monitors, the taskbar remains on the primary screen even if it is not working).

I'm using the free "radeon" driver. I don't think the version is important, because I have the same issue with Fedora 20 and Fedora 22.

The system has a second discreet radeon GPU, but I don't use it.

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff)

And from xrandr output it looks like all outputs are connected to the default integrated GPU:

[skarap@roadrunner ~]$ xrandr --listproviders 
Providers: number : 3
Provider 0: id: 0x8c cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:radeon
Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon
Provider 2: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon
Comment 1 Michel Dänzer 2015-12-07 06:17:16 UTC
Please attach the Xorg log file and the output of dmesg and xrandr --verbose, all of them preferably captured when one of the monitors is off but supposed to be on.
Comment 2 Suren Karapetyan 2015-12-07 08:07:29 UTC
Created attachment 120381 [details]
xrandr --verbose output
Comment 3 Suren Karapetyan 2015-12-07 08:08:23 UTC
Created attachment 120382 [details]
xorg log
Comment 4 Suren Karapetyan 2015-12-07 08:16:39 UTC
The outputs are taken when an external monitor is working and the laptop display is off (no backlight and no image).

One more things. Not sure if it is related, but the automatic detection of connecting the VGA monitor doesn't work either. With the previous laptop when I connected an external display to the VGA port, the desktop environment (KDE or GNOME) would automatically detect it and configure with the previous setup. With this laptop it doesn't do it - I have to run the configuration utility manually for it to see the new display.
Comment 5 Suren Karapetyan 2015-12-11 20:35:52 UTC
Is there any other information I can provide to help with this?
I'll have time to spend on this during the weekend and a little system programming experience.
Comment 6 Martin Peres 2019-11-19 09:10:35 UTC
-- 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/670.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.