AMD GPU drivers issue [SOLVED]

[Hooten]

I have a dell inspiron 3537 with intel and amd r9 m265x gpu cards. I never had any issue with amd card since recently.
After few updates on kernel and mesa drivers amd card is not listed in xrandr --listproviders, even if inxi -F clearly shows amd gpu as second device. I also rolled back in previous kernels, but with no luck at all.

Thank you in advance.

xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x46 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:Intel


inxi -F

Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] driver: radeon
v: kernel
Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.9

[Hooten]

I went to /etc/X11/xorg.conf.d/ and changed the 20-radeon.conf because there was wrong driver name and amd card now is listed in xrandr --listproviders :

xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x7c cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:Intel
Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 0 name:VERDE @ pci:0000:03:00.0

BUT, when i launch steam from terminal using DRI_PRIME=1 steam, amd card is not used for some weird reason. Now i really have no idea how to troubleshoot this.
Please anyone can solve this?

[Hooten]

I think i solved it but it's kinda weird how though. I "xrandr --setprovideroffloadsink 1 0" in terminal and now when i launch steam, through terminal "DRI_PRIME=1 steam", actually opens with amd card and games run fine. I have now idea why "xrandr --setprovideroffloadsink 1 0" command needed, i never done this before and everything was working fine.

Anyway, i checked it with reboot if it's fixed permanently and it is. So it's probably fixed now.
Sorry for the hassle.