Bug 92571 - After activating the second GPU (setprovideroutputsource) changing any XRandr setting leads to inavlid dpi and wrong framebuffer size
Summary: After activating the second GPU (setprovideroutputsource) changing any XRandr...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-21 14:51 UTC by Jan Burgmeier
Modified: 2018-12-13 22:34 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Xrandr output before setting the dpi manually (8.92 KB, text/plain)
2015-10-21 14:51 UTC, Jan Burgmeier 		no flags Details
Xrandr output after setting the dpi manually (8.92 KB, text/plain)
2015-10-21 14:52 UTC, Jan Burgmeier 		no flags Details
Xorg server logfile (281.13 KB, text/plain)
2015-10-21 15:07 UTC, Jan Burgmeier 		no flags Details
dmesg output (50.31 KB, text/plain)
2015-10-21 15:07 UTC, Jan Burgmeier 		no flags Details
View All

Description Jan Burgmeier 2015-10-21 14:51:43 UTC 
Created attachment 119034 [details]
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.
Comment 1 Jan Burgmeier 2015-10-21 14:52:38 UTC 
Created attachment 119035 [details]
Xrandr output after setting the dpi manually
Comment 2 Alex Deucher 2015-10-21 14:53:38 UTC 
Please attach your xorg log and dmesg output.
Comment 3 Jan Burgmeier 2015-10-21 15:07:14 UTC 
Created attachment 119037 [details]
Xorg server logfile
Comment 4 Jan Burgmeier 2015-10-21 15:07:31 UTC 
Created attachment 119038 [details]
dmesg output
Comment 5 Michel Dänzer 2015-10-22 02:56:54 UTC 
Assuming this is an xserver issue as well.
Comment 6 GitLab Migration User 2018-12-13 22:34:06 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/xorg/xserver/issues/486.

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.