[Bug 92571] New: After activating the second GPU (setprovideroutputsource) changing any XRandr setting leads to inavlid dpi and wrong framebuffer size
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Oct 21 07:51:43 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=92571
Bug ID: 92571
Summary: After activating the second GPU
(setprovideroutputsource) changing any XRandr setting
leads to inavlid dpi and wrong framebuffer size
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/Radeon
Assignee: xorg-driver-ati at lists.x.org
Reporter: jan.burgmeier at unicon-software.com
QA Contact: xorg-team at lists.x.org
Created attachment 119034
--> https://bugs.freedesktop.org/attachment.cgi?id=119034&action=edit
Xrandr output before setting the dpi manually
Hi,
My setup is the following:
PC: HP T620 Plus with two AMD graphics card
Monitors: 3 Dell 4k Monitos running at 1920x1080. Two are attached to the
primary card and one to the secondary card.
After activating the secondary GPU with "xrandr --setprovideroutputsource"
changing any XRandr setting (resolution, rotation, ...) leads in a too small
framebuffer. It seems that the dpi is wrongly set. It is also not possible to
change the framebuffer with "xrandr --fb". The following commands will fix the
problem:
-----------------------------------------------------------------------
user> xrandr --dryrun --verbose --fb 4080x1920
screen 0: 4080x1920 0x0 mm infdpi
user> xrandr --verbose --fb 4080x1920
screen 0: 4080x1920 0x0 mm infdpi
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 7 (RRSetScreenSize)
Value in failed request: 0x0
Serial number of failed request: 52
Current serial number in output stream: 54
user> xrandr --verbose --dpi 96
screen 0: 4080x1920 1079x507 mm 96.00dpi
---------------------------------------------------------------------
The following versions were used:
Xorg-1.17.2
xf86-video-ati latest git version (ce9914a)
mesa-11.0.0
libdrm-2.4.64
libLLVM-3.7
It does not matter if using DRI2 or DRI3.
It does not matter if ColorTiling2D is on or off.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-driver-ati/attachments/20151021/71d49d31/attachment-0001.html>
More information about the xorg-driver-ati
mailing list