Bug 95320 - Neither ATI nor AMDGPU supports the resolutions for my 6520g BeaverCreek Graphics that catalyst does
Summary: Neither ATI nor AMDGPU supports the resolutions for my 6520g BeaverCreek Grap...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-08 20:35 UTC by Lizzi Swane
Modified: 2019-11-19 07:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
attachment-11336-0.html (2.16 KB, text/html)
2016-05-10 03:02 UTC, Lizzi Swane 		no flags Details
View All

Description Lizzi Swane 2016-05-08 20:35:03 UTC 
In catalyst i can get:

randr
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
DFP1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 640mm x 360mm
   1600x900      59.94*+
   1920x1080     60.00 +  59.94  
   1776x1000     59.94  
   1680x1050     60.00    59.94  
   1400x1050     60.00    59.94  
   1280x1024     60.00    59.94  
   1440x900      59.94  
   1280x960      59.94  
   1360x768      59.94  
   1280x768      59.94  
   1280x720      60.00    59.94  
   1024x768      60.00  
   1152x648      59.94  
   1024x600      60.00  
   800x600       60.32  
   800x480       60.32  
   720x480       60.00    60.00    59.94    59.94  
   640x480       60.00    59.94  


but with the open source drivers i can not get  (that is to say that xrandr doesn't list them):

   1600x900      59.94*+
   1776x1000     59.94  
   1680x1050     60.00    59.94  
   1400x1050     60.00    59.94  
   1440x900      59.94  
   1280x960      59.94  
   1360x768      59.94  
   

With either of the free drivers, ati or amdgpu the highest res i can get to fit on my viewable area is 1024x768 and that just sucks.

I've tried making a simple xorg.conf and added modelines for the above resolutions like this:

xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync

xrandr --addmode YOUR_OUT "1600x900_60.00"

xrandr --output YOUR_OUT --mode "1600x900_60.00" 

I tried this with all the resolutions that don't show up in xrandr with the free driver and for the results of that effort i get a blank screen.

Could you please provide the same resolution support with the free drivers that my graphics card is capable of supporting.

Thank you.
Comment 1 Lizzi Swane 2016-05-08 23:36:06 UTC 
6520g APU Beavercreek
Comment 2 Alex Deucher 2016-05-09 15:07:38 UTC 
Please attach your xorg log and dmesg output.
Comment 3 Lizzi Swane 2016-05-09 16:07:25 UTC 
sudo dmesg | pastebinit
http://pastebin.com/NFj3TMWV

xrandr --verbose
http://pastebin.com/YeCKkpDs

cat /var/log/Xorg.0.log | pastebinit
http://pastebin.com/CiEL6t9k

xrandr -q |pastebinit
http://pastebin.com/rNsTbTQf

Also i tried to create an xorg.conf to configure the free driver to tun one of the resolutions that works with catalyst and the config will not load.

Here's that xorg.conf
http://pastebin.com/J4zBGRa1

Also i tried this:
xrandr --newmode "1600x900_59.94"  118.00  1600 1696 1856 2112  900 903 908 934 -hsync +vsync

xrandr --addmode HDMI-0 "1600x900_59.94"

xrandr --output HDMI-0 --mode "1600x900_59.94"

And i got a blank screen for my trouble.

Thank you for your help
Comment 4 Lizzi Swane 2016-05-09 17:21:32 UTC 
Also i went back to the catalyst driver to see what it does differently that i haven't tried and it uses for 1600x900 a 30htz refresh rate but also it uses monitor scaling and not gpu scaling.  Is that helpful to know?  Even in catalyst the gpu scaling wasn't so good but monitor scaling seemed useful.
Comment 5 Lizzi Swane 2016-05-09 17:26:58 UTC 
Also when i used graphics scaling with the catalyst i had to set underscan to 7% at 1600x900 30hz under maintain aspect ratio.
Comment 6 Alex Deucher 2016-05-09 17:52:31 UTC 
The TV does not appear to support 1600x900.  I think catalyst must add it as a "fake" scaled mode.  You can enable scaling in the open source driver by setting:
xrandr --output HDMI-0 --set "scaling mode" "Full aspect"
xrandr --output HDMI-0 --mode 1600x900_60.00
you can replace "Full aspect" with None, Full, Center, "Full aspect" depending on what type of scaling you want.  None disables the GPU's scaler so that the one on the monitor is used.
Comment 7 Lizzi Swane 2016-05-09 17:56:30 UTC 
I have tried that several times and i get a blank screen with the opensource driver.
Comment 8 Lizzi Swane 2016-05-09 17:59:57 UTC 
the open source drive default scaling mode is none.

Also catalyst uses 30hz not 60hz for the resolutions above 1280x720 and when i tried to use those with the opensource driver i get a blank screen.
Comment 9 Lizzi Swane 2016-05-09 18:14:23 UTC 
When the system boots, it boots into 1920x1080.  if i use then the xrandr to set underscan to on the desktop size is still greater than the viewable area.  With underscan off the best resolution i can get is 1024x768 with the opensource driver and with underscan set to on the best resolution i can get is 1280x720.

However, with catalyst i can get 1776x1000, 1600x900, & 1400x900 that scale well to the viewable are.  A few others are availaable but its the 1600x900 that i like.  The opensource driver isn't providing those resolutions but the catalyst does, hence my request that the opensource driver display the same resolutions as the fglrx.  This is of huge concern to me because with the new crimson drivers that amd has released, my apu and all 5000 and 6000 series gpus have reached eol for non-free support.  If you won't support these cards to their full no one else will.

Thank you for your help!
Comment 10 Lizzi Swane 2016-05-09 18:23:40 UTC 
You know what's funny is that i have seen the specs for the tv and see that 1366x768 is the default resolution for the tv.  Also for this laptop that was the default resoultion for the lcd built into it but xorg doesn't recognize it as a viable display.

http://www.cnet.com/products/philips-26pf5321d/specs/
Comment 11 Alex Deucher 2016-05-09 18:26:27 UTC 
Turn off underscan if you want to use scaling.  Also, underscan compensates for overscan applied by the TV so you'll end up getting scaled twice (once by the GPU and once by the TV).  Ideally you'd disable overscan on the TV.
Comment 12 Lizzi Swane 2016-05-09 18:29:39 UTC 
Even catalyst doesn't see it as a viable resolution for 1366x768
Comment 13 Alex Deucher 2016-05-09 18:36:03 UTC 
(In reply to Lizzi Swane from comment #12)
> Even catalyst doesn't see it as a viable resolution for 1366x768

The monitor announces all modes that it supports via the EDID.  If it's not available in the EDID, the driver has no way to know what the native mode of the panel is and what modes the scaler on the monitor provides.


	EDID: 
		00ffffffffffff00410c000001010101
		00000103804024780ae692a3544a9926
		0f4a4c21080001010101010101010101
		010101010101011d8018711c1620582c
		250080682100009e011d007251d01e20
		6e28550080682100001e000000fc0050
		68696c697073204654560a20000000fd
		00303e0f3209000a202020202020019c
		020320f0470102030405060729091f07
		1507501907868301000065030c001000
		8c0ad08a20e02d10103e960080682100
		00188c0aa01451f01600267c43008068
		210000988c0ad08a20e02d10103e9600
		902c110000188c0aa01451f01600267c
		4300902c110000980000000000000000
		000000000000000000000000000000dc
Comment 14 Lizzi Swane 2016-05-09 18:55:10 UTC 
so what can i do?  Catalyst/fglrx has some notion of it in spite of the edid not reporting all it's modes.  How does catalyst do that when the opensource driver can not?
Comment 15 Alex Deucher 2016-05-09 18:59:17 UTC 
(In reply to Lizzi Swane from comment #14)
> so what can i do?  Catalyst/fglrx has some notion of it in spite of the edid
> not reporting all it's modes.  How does catalyst do that when the opensource
> driver can not?

Maybe I misunderstood your question.  I thought you said catalyst couldn't see 1366x768 either?

With respect to the modes exposed by default, catalyst adds "fake" modes that use the GPU scaler by default while radeon does not.
Comment 16 Lizzi Swane 2016-05-09 19:03:46 UTC 
Yes that's correct, catalyst doesn't see the 1366x768 either but it does offer me other resolutions which are useful to me and i would like the same available from the opensource driver.

All i want are the ability to use the same resolutions in the opensource driver that catalyst provides.  That's the point of the OP.

Thank you for your help!  :)
Comment 17 Lizzi Swane 2016-05-09 19:58:17 UTC 
Also trying to adjust the scaling mode from the default of none gives me a blank screen, regardless of wheter i have underscan set to off or on with the opensource driver.
Comment 18 Lizzi Swane 2016-05-09 20:04:25 UTC 
xrandr --addmode HDMI-0 "1366x768_59.94"
xrandr: cannot find mode "1366x768_59.94"

xrandr --addmode HDMI-0 "1366x768_60"
xrandr: cannot find mode "1366x768_60"

cvt 1366 768
# 1368x768 59.88 Hz (CVT) hsync: 47.79 kHz; pclk: 85.25 MHz
Modeline "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync

xrandr --addmode HDMI-0 "1366x768_59.88"
xrandr: cannot find mode "1366x768_59.88"

xrandr --addmode HDMI-0 "1366x768_60.00"
xrandr: cannot find mode "1366x768_60.00"

xrandr --addmode HDMI-0 "1366x768"
xrandr: cannot find mode "1366x768"
Comment 19 Alex Deucher 2016-05-09 20:19:33 UTC 
(In reply to Lizzi Swane from comment #18)
> xrandr --addmode HDMI-0 "1366x768_59.94"
> xrandr: cannot find mode "1366x768_59.94"
> 
> xrandr --addmode HDMI-0 "1366x768_60"
> xrandr: cannot find mode "1366x768_60"
> 
> cvt 1366 768
> # 1368x768 59.88 Hz (CVT) hsync: 47.79 kHz; pclk: 85.25 MHz
> Modeline "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync
> +vsync
> 
> xrandr --addmode HDMI-0 "1366x768_59.88"
> xrandr: cannot find mode "1366x768_59.88"
> 
> xrandr --addmode HDMI-0 "1366x768_60.00"
> xrandr: cannot find mode "1366x768_60.00"
> 
> xrandr --addmode HDMI-0 "1366x768"
> xrandr: cannot find mode "1366x768"

You have to define the mode first.  E.g.,

xrandr --newmode "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync
xrandr --addmode HDMI-0 "1366x768_60.00"
Comment 20 Lizzi Swane 2016-05-09 20:20:33 UTC 
sorry about that last post.  I'm fatigued.

xrandr --newmode "1368x768_60.00" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync

xrandr --addmode HDMI-0 "1368x768_60.00"

xrandr --output HDMI-0 --mode "1368x768_60.00"


i did copy and paste those lines into the terminal with the opensource ati driver running and was rewarded with a blank screen.
Comment 21 Lizzi Swane 2016-05-09 20:22:06 UTC 
I'm very tired.  I need to take a break.  Even the native resolution for my laptoop and the monitor im using arent available with the opensource driver.  

Thank you for your help.
Comment 22 Michel Dänzer 2016-05-10 00:44:59 UTC 
Beware that the amdgpu kernel driver currently has issues with GPU scaling, see bug 95131.
Comment 23 Michel Dänzer 2016-05-10 00:47:17 UTC 
Never mind, you're using the radeon driver, not amdgpu.
Comment 24 Lizzi Swane 2016-05-10 03:02:12 UTC 
Created attachment 123588 [details]
attachment-11336-0.html

Yup.  The amdgpu driver doesn't support my beaver creek apu

On Mon, May 9, 2016 at 8:47 PM, <bugzilla-daemon@freedesktop.org> wrote:

> Michel Dänzer <michel@daenzer.net> changed bug 95320
> <https://bugs.freedesktop.org/show_bug.cgi?id=95320>
> What Removed Added
> Component Driver/AMDgpu Driver/Radeon
>
> *Comment # 23 <https://bugs.freedesktop.org/show_bug.cgi?id=95320#c23> on
> bug 95320 <https://bugs.freedesktop.org/show_bug.cgi?id=95320> from Michel
> Dänzer <michel@daenzer.net> *
>
> Never mind, you're using the radeon driver, not amdgpu.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 25 Martin Peres 2019-11-19 07:56:32 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/driver/xf86-video-ati/issues/159.

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.