Summary: | Only one of LVDS and VGA-0 work on HP Pavilion m6 with Radeon HD 7660G | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Suren Karapetyan <surenkarapetyan> | ||||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||
Status: | RESOLVED MOVED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Suren Karapetyan
2015-12-06 10:18:18 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. Created attachment 120381 [details]
xrandr --verbose output
Created attachment 120382 [details]
xorg log
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. 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. -- 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.