It happened on a fresh install, and the computer is brand new so I don't
have any clue about the past!

I've tested upstream kernel, and the bug seems to be fixed, but please
check that I'm right:

- I turn on Ubuntu, I run glxgear, I get a normal frame rate of 60fps (I
guess I'm using Intel graphics)

- xrandr --listproviders gives:
Providers: number : 2
Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 
associated providers: 0 name:Intel
Provider 1: id: 0x3f cap: 0x0 crtcs: 0 outputs: 0 associated providers: 0 
name:HAINAN @ pci:0000:01:00.0

Note that there were only 2 listed when I reported the bug

- DRI_PRIME=1 glxgears now works, gives extremely high frame rate
(6000), renders smoothly

- xrandr --setprovideroffloadsink 0x3f 0x66 doesn't work anymore, now gives 
error: 
 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:  34 (RRSetProviderOffloadSink)
  Value in failed request:  0x3f
  Serial number of failed request:  16
  Current serial number in output stream:  17

So, even if I don't understand exactly how to switch rendering engine
systemwide, I think that using DRI_PRIME=1 actually turns the GPU on and
it is working fine now!

I'm tagging accordingly, but please tell me if I understand correctly.

** Tags added: kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570802

Title:
  ATI Radeon not working: from no rendering to system freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570802/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to