Bug 103599

Summary: My AMD Radeon R7 M265 dedicated VGA not recognized by ATI Radeon driver
Product: xorg Reporter: yousifjkadom2-new
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED NOTABUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg
none
lscpi -vnn
none
Xorg.0.log
none
Xorg.1.log
none
Xorg.2.log
none
Xorg.9.log none

Description yousifjkadom2-new 2017-11-06 19:38:42 UTC
Hi. I'm on Fedora Linux 26 X64 Cinnamon edition on my Lenovo ThinkPad e550 with with Intel core i7 5500 CPU @ 2.40 GH X 2, RAM = 8 GB, HHD = 1 TB, Hybrid VGA (Intel Corporation HD Graphic 5500 + Radeon R7 M265 2GB)

Problem is that open source ATI Radeon driver (which installed by default on my system: package name is "xorg-x11-drv-ati") not recognizing my dedicated AMD Radeon R7 M265 VGA !!

It should be recognized according to the following link (please correct to me if I'm wrong):

https://www.x.org/wiki/RadeonFeature/

From above link, "Southern Island" cards (which my Radeon R7 M265 is one of them) are supported & should be recognized - correct to me if I'm wrong ...
Comment 1 Alex Deucher 2017-11-06 19:45:18 UTC
It's not clear to me what you mean.  Please attach your xorg log and lspci -vnn and dmesg output.
Comment 2 yousifjkadom2-new 2017-11-06 20:29:42 UTC
Hi. Thank you very much for your kind & rapid response !

I attached all of them by files carrying their names.

Only one note: regarding xorg log, I got log files as following: using my file manager to navigate to /var/log where I saw following xorg log files:

Xorg.0.log
Xorg.1.log
Xorg.2.log
Xorg.9.log

Xorg.0.log.old
Xorg.1.log.old
Xorg.2.log.old

I attached 1st 4 files & ignored .old files. Do you need .old files also ?
Comment 3 yousifjkadom2-new 2017-11-06 20:30:14 UTC
Created attachment 135270 [details]
dmesg
Comment 4 yousifjkadom2-new 2017-11-06 20:30:59 UTC
Created attachment 135271 [details]
lscpi -vnn
Comment 5 yousifjkadom2-new 2017-11-06 20:31:35 UTC
Created attachment 135272 [details]
Xorg.0.log
Comment 6 yousifjkadom2-new 2017-11-06 20:32:24 UTC
Created attachment 135273 [details]
Xorg.1.log
Comment 7 yousifjkadom2-new 2017-11-06 20:33:02 UTC
Created attachment 135274 [details]
Xorg.2.log
Comment 8 yousifjkadom2-new 2017-11-06 20:33:32 UTC
Created attachment 135275 [details]
Xorg.9.log
Comment 9 Alex Deucher 2017-11-06 21:12:46 UTC
The kernel driver and xorg driver are loading fine.  What's the problem?  Note that there are no displays attached to the amd chip so it can only be used for offscreen rendering (e.g., render offload) where the frame is rendered by the dGPU and then copied to the integrated chip for display.  For more info on setting up prime for render off load see this page:
https://wiki.archlinux.org/index.php/PRIME
or others like it.
Comment 10 yousifjkadom2-new 2017-11-06 22:09:00 UTC
Thank you very very very much !!! 1 & 1/2 years rotate about this issue thought that my AMD Radeom not supported by ATI Radeon driver !!! It was wrong from incorrect instructions from Fedora forum !!!

Please please, only 2 questions (I understand that this is a bug tracker not support forum & I will never ask for further support - if needed - here, but in Fedora forum BUT I NEED YOUR ANSWERS ABOUT FOLLOWING TO BE A LIGHT UNDER WHICH FEDORA FORUM MEMBERS CAN HELP ME CORRECTLY & AVOID FURTHER MISTAKES FROM THEM):

1) I understood from your previous kind replay that my AMD Radeon VGA is already recognized & WORKING ACTIVELY in my system, isn't it ?

2) You said that: "Note that there are no displays attached to the amd chip so it can only be used for offscreen rendering -----" 

is this the default setting & position of my AMD Radeon VGA ?

3) regarding link you gave me: is this mean that I have to perform further setting to get my dedicated AMD Radeon card work or this link just for further information ?

Best
Comment 11 Alex Deucher 2017-11-06 22:22:34 UTC
(In reply to yousifjkadom2-new from comment #10)
> Thank you very very very much !!! 1 & 1/2 years rotate about this issue
> thought that my AMD Radeom not supported by ATI Radeon driver !!! It was
> wrong from incorrect instructions from Fedora forum !!!
> 
> Please please, only 2 questions (I understand that this is a bug tracker not
> support forum & I will never ask for further support - if needed - here, but
> in Fedora forum BUT I NEED YOUR ANSWERS ABOUT FOLLOWING TO BE A LIGHT UNDER
> WHICH FEDORA FORUM MEMBERS CAN HELP ME CORRECTLY & AVOID FURTHER MISTAKES
> FROM THEM):
> 
> 1) I understood from your previous kind replay that my AMD Radeon VGA is
> already recognized & WORKING ACTIVELY in my system, isn't it ?

The drivers are loaded correctly.  To actively use the AMD GPU, you need to select it for render offload using xrandr.  See the link I posted.

> 
> 2) You said that: "Note that there are no displays attached to the amd chip
> so it can only be used for offscreen rendering -----" 
> 
> is this the default setting & position of my AMD Radeon VGA ?
> 

Yes.

> 3) regarding link you gave me: is this mean that I have to perform further
> setting to get my dedicated AMD Radeon card work or this link just for
> further information ?

You need to select the dGPU for render offload, otherwise it's kept powered down to save power.  You'll have to follow those instructions to use the dGPU for render offload.
Comment 12 yousifjkadom2-new 2017-11-06 22:43:16 UTC
I understand now ! Finally I get releaf from this headache !

Only one question (last one here) whay laptop can not perform automatic switch between dedicated VGA & built-in Intel card ? Is the case is same in Windows OS ? I never ever shift to Windows OS, but I like to be oriented. Is amdgpu same regarding need for manual switching between built-in & dedicated cards ? 

Or it could be that I'm wrong in principle & there is no such automatic switching ? They said that Fedora 25 + will support such hybrid system & from that time I have in my mind an automatic switch ..... !  

------------------------------

By the way, can you kindly look for this bug that I file it:

https://bugs.freedesktop.org/show_bug.cgi?id=102520

you ask me about files & I supplied you them but no further replay or comment from your side .... 

According to your kind replies here, it seem that bug102520 contain nonsense speech from my side about amdgpu & my AMD Radeon card & ATI Radeon driver on my system. But what about the remainder (issue in it's title) ?
Comment 13 Alex Deucher 2017-11-06 23:04:07 UTC
(In reply to yousifjkadom2-new from comment #12)
> I understand now ! Finally I get releaf from this headache !
> 
> Only one question (last one here) whay laptop can not perform automatic
> switch between dedicated VGA & built-in Intel card ? Is the case is same in
> Windows OS ? I never ever shift to Windows OS, but I like to be oriented. Is
> amdgpu same regarding need for manual switching between built-in & dedicated
> cards ? 

The driver does do dynamic switching.  The hardware is the same.  There are no displays connected to the dGPU, so it can only be used for offscreen rendering.  The integrated GPU always handles the displays.  I think windows uses app profiles to determine which GPU does the rendering whereas on Linux, it's explicit (you can choose which GPU to use per app).  You could do something similar on Linux (e.g., set DRI_PRIME=1 in the script that starts the game or in the launchers).

> 
> Or it could be that I'm wrong in principle & there is no such automatic
> switching ? They said that Fedora 25 + will support such hybrid system &
> from that time I have in my mind an automatic switch ..... !  
> 

It's automatic in that the dGPU is only powered on when you request rendering.  You just get to pick when the dGPU is used. see above.
Comment 14 Michel Dänzer 2017-11-07 08:49:42 UTC
FWIW, since the modesetting driver enables DRI3 by default, DRI_PRIME=1 should work without using xrandr first.

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.