You are not logged in.

#1 2022-07-08 15:39:59

justsquid
Member
Registered: 2022-07-07
Posts: 12

When attempting to set up PRIME, X spits out BadValue

This is a continuation of this thread where I had issues using both gpus, however the root problem of that issue was indeed solved. The issue I have now is setting up PRIME, as that seems more appealing to my use case. While I was following PRIME_GPU_offloading, I used the example

xrandr --setprovideroffloadsink 1 0

. When I did so, I got this:

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:  0x62
  Serial number of failed request:  16
  Current serial number in output stream:  17

How can I get PRIME offloading working?

Offline

#2 2022-07-08 15:49:24

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: When attempting to set up PRIME, X spits out BadValue

From your other thread you're using a static server config that selects only one of the devices?

xrandr --listproviders

and also post your xorg log.

Offline

#3 2022-07-08 16:01:25

justsquid
Member
Registered: 2022-07-07
Posts: 12

Re: When attempting to set up PRIME, X spits out BadValue

Providers: number : 2
Provider 0: id: 0x62 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 2 outputs: 2 associated providers: 1 name:nouveau
Provider 1: id: 0x9c cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 5 outputs: 4 associated providers: 1 name:AMD Radeon RX 6600 XT @ pci:0000:0b:00.0

http://ix.io/41XN Xorg.0.log

Offline

#4 2022-07-08 16:24:37

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: When attempting to set up PRIME, X spits out BadValue

You're running on the nvidia chip. If you want access to the outputs on the AMD chip, try

xrandr --setprovideroutputsource 0x9c 0x62

The other way round (using prime to run on the amd chip and posting that to the outputs on the nvidia chip) should™ already be established by default.

Offline

#5 2022-07-08 16:48:08

justsquid
Member
Registered: 2022-07-07
Posts: 12

Re: When attempting to set up PRIME, X spits out BadValue

seth wrote:

You're running on the nvidia chip...
The other way round (using prime to run on the amd chip and posting that to the outputs on the nvidia chip) should™ already be established by default.

Wait, so I should™ be getting AMD rendering posted to Nvidia outputs already? Then why is OpenGL rendering saying

 OpenGL renderer string: NV138 

when I use glxinfo | grep "OpenGL renderer"?

Offline

#6 2022-07-09 07:52:59

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,808

Re: When attempting to set up PRIME, X spits out BadValue

Because you're running on the nvidia chip.
Try

DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

Offline

Board footer

Powered by FluxBB