You are not logged in.

#26 2025-07-30 17:38:34

retchut
Member
Registered: 2023-04-13
Posts: 20

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

Hello, and I apologize once again for the delay in my response.

I will be honest, I am not entirely sure how PS works, but I thought I did not have to explicitly set the offload sink, as I am using the modesetting driver,going off of the note on this wiki entry.

Currently, the modesetting provider is set to "Source Offload", which I believe is what we want:

$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x42 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 1 associated providers: 1 name:modesetting
Provider 1: id: 0x26d cap: 0x2, Sink Output crtcs: 4 outputs: 3 associated providers: 1 name:NVIDIA-G0

Offline

#27 2025-07-30 21:34:26

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,177

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

https://wiki.archlinux.org/title/PRIME# … ronization

xrandr --props

and see the wiki on how to flip that - the provider isn't "set" to anything, those are capabilities.

Offline

#28 2025-08-02 22:43:08

retchut
Member
Registered: 2023-04-13
Posts: 20

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

Ah, I had looked into that before, but noticed that the external display had Prime Synchronization set to 1, so I stopped researching this. However, I just noticed that the internal display does not have that variable set. Perhaps that might be leading to issues?
I'm not sure if it is supposed to be set on the internal display. But I also noticed that e-DP-1-1 (the internal display output id when in nvidia mode) has it set to 1.
Attempting to set Prime Sync to 1 on the internal display reports issues, however.

xrandr --output eDP-1 --set "PRIME Synchronization" 1

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  46
  Current serial number in output stream:  46

Here's the output of xrandr --props

Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
	EDID: 
		00ffffffffffff0006afed8200000000
		0a1c0104a5221378026a75a456529c27
		0b505400000001010101010101010101
		010101010101ce8f80b6703888403020
		a50058c210000000ce8f80b670382b47
		3020a50058c110000000000000fe0041
		554f0a202020202020202020000000fe
		004231353648414e30382e32200a0017
	Colorspace: Default 
		supported: Default, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	panel orientation: Normal 
		supported: Normal, Upside Down, Left Side Up, Right Side Up
	scaling mode: Full aspect 
		supported: Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CTM: 	1.000000 0.000000 0.000000
		0.000000 1.000000 0.000000
		0.000000 0.000000 1.000000
	CONNECTOR_ID: 99 
		supported: 99
	non-desktop: 0 
		range: (0, 1)
   1920x1080    144.03*+  60.08    60.01    59.97    59.96    59.93  
   [..... other resolutions .....]
   320x175       85.27  
DP-1-0 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 	1.000000 0.000000 0.000000
		0.000000 1.000000 0.000000
		0.000000 0.000000 1.000000
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 0 
	_ConnectorLocation: 0 
	non-desktop: 0 
		supported: 0, 1
DP-1-1 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 	1.000000 0.000000 0.000000
		0.000000 1.000000 0.000000
		0.000000 0.000000 1.000000
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 0 
	_ConnectorLocation: 0 
	non-desktop: 0 
		supported: 0, 1
HDMI-1-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 368mm x 207mm
	EDID: 
		00ffffffffffff000d04700201000000
		2a1d010380351d78ea3d15a3544da027
		125054bfef00714f818081409500a940
		b300d1c0a9c0023a801871382d40582c
		450070cf1000001a000000fd00324c1e
		530f000a202020202020000000fc004d
		544d3438373347520a202020000000ff
		0030300a202020202020202020200147
		02031ef14b900504030201111213141f
		230907078301000065030c0010001a36
		80a070381e403020350022602100001a
		662156aa51001e30468f330022602100
		001e011d007251d01e206e2855002260
		2100001e8c0ad08a20e02d10103e9600
		2260210000180e1f008051001e303020
		370022602100009e0000000000000035
	PRIME Synchronization: 		supported: ?, ?
	CTM: 	1.000000 0.000000 0.000000
		0.000000 1.000000 0.000000
		0.000000 0.000000 1.000000
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: HDMI 
	ConnectorNumber: 1 
	_ConnectorLocation: 1 
	non-desktop: 0 
		supported: 0, 1
   1920x1080     60.00*+  60.00    59.99    59.94    50.00  
   [..... other resolutions .....]
  640x480 (0x9b) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz

Offline

#29 2025-08-05 20:51:08

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,177

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

but noticed that the external display had Prime Synchronization set to 1

the idea would then be to flip that and set it to "0", you cannot "add" that to an output and there's also nothing to prime-sync on the output that's connected to the GPU that runs the X11 server.

Offline

#30 2025-08-12 17:57:15

retchut
Member
Registered: 2023-04-13
Posts: 20

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

Wouldn't the external display (the one connected via hdmi, and directly connected to the dGPU), need to have Prime Synchronization set to 1 in order for the gpu offloading to work?

In either case, I flipped it to 0 on the connected external display, and met crashes in the exact same way.

Offline

#31 2025-08-12 18:45:01

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,177

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

No, that's to align vsync (for tearing prevention, in the best case scenario)

crashes in the exact same way

blast! sad

For recap: #17, #20 and #21 lead us there

problem is essentially down to that: reverse prime + vulkan

Have we ever tried downgrading the nvidia driver? (eg. to 570xx, you'll need to use the dkms package if you intend to try)

Offline

#32 2025-08-12 19:27:06

retchut
Member
Registered: 2023-04-13
Posts: 20

Re: Crashing when offloading proton games to nvidia dGPU on hybrid mode

I remember this issue starting a few years ago, in either 2021 or 2022, when the proprietary drivers were somewhere around version 460. Eventually I gave up and just started using nvidia mode 24/7, which did not give me issues.

I have not experimented with other versions of the nvidia driver, such as noveau or dkms.
I can try to experiment with noveau or downgrade to a more recent version and report back.

Offline

Board footer

Powered by FluxBB