[SOLVED] PRIME issues after recent update

epse · 2023-07-23 08:37:16

I daily drive a laptop that has both an nvidia RTX2070 GPU and integrated intel. Intel runs the laptop screen, all other outputs are wired into the nvidia.
Eons ago, I struggled to get PRIME to function halfway decent and ended up just making nvidia the primary GPU all the time because this laptop doesn't have any battery life to speak of anyway.
This setup broke with a recent update (recent is relative, for a variety of reasons my system was a bit out of date). I've managed to get it all set back up to the point where outputs from the nvidia work, but the internal display is always blank.

The setup as I configured it eons ago:

nvidia-drm.modesetting=1

in the kernel parameters
nvidia closed source drivers
nouveau is also installed, but blacklisted. I cannot remember why.

This config snippet in an xorg conf file:

Section "OutputClass"
	Identifier "intel"
	MatchDriver "i915"
	Driver "modesetting"
EndSection

Section "OutputClass"
	Identifier "nvidia"
	MatchDriver "nvidia-drm"
	Driver "nvidia"
	Option "AllowEmptyInitialConfiguration"
	Option "PrimaryGPU" "yes"
	ModulePath "/usr/lib/nvidia/xorg"
	ModulePath "/usr/lib/xorg/modules"
EndSection

and finally, a two-line script that is run by lightdm:

	xrandr --setprovideroutputsource modesetting NVIDIA-0
	xrandr --auto

I've tried various combinations of the new recommendations in the wiki and nvidia pages (except for removing the nvidia proprietary drivers alltogether), most result in both internal and external displays being blank. I'm typing this with this exact setup described above, but the script disabled. The first line of the script runs fine, but the second line (or any xrandr command that attempts to configure the internal display) errors out with

xrandr: Configure crtc 4 failed

Not a terribly great xorg debugging expert, I've just been trial-and-erroring my way across with the help of my trusty live USB, so any help greatly appreciated.

Any setup that removes the above xorg config (and replaces it with the recommended snippet in current wiki or nvidia docs) results in two blank monitors.

Last edited by epse (2023-07-24 08:53:41)

seth · 2023-07-23 13:22:24

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Also see https://wiki.archlinux.org/title/LightD … TTY_output

Do you intend to run the system on the nvidia chip or would you prefer to run it as regular prime setup on the IGP?

epse · 2023-07-24 08:11:13

The lightdm setting was already set by default I see. I have been running it purely on the nvidia chip pretty much since I first got it, because regular prime got quite slow with lots of displays attached and the power savings don't matter for my usecase.

I don't exactly know for which situation you'd like an xorg log, but I'll link one that is running the nvidia drivers and the xorg config I'll quote at the end of this post.
The very last few log lines are from running the two-line script mentioned in the OP.

Pastebin for log: https://pastebin.com/GSVZGH0y

Section "OutputClass"
	Identifier "intel"
	MatchDriver "i915"
	Driver "modesetting"
EndSection

Section "OutputClass"
	Identifier "nvidia"
	MatchDriver "nvidia-drm"
	Driver "nvidia"
	Option "AllowEmptyInitialConfiguration"
	Option "PrimaryGPU" "yes"
	ModulePath "/usr/lib/nvidia/xorg"
	ModulePath "/usr/lib/xorg/modules"
EndSection

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

seth · 2023-07-24 08:16:10

[     6.913] (II) modeset(G0): Supported detailed timing:
[     6.913] (II) modeset(G0): clock: 368.1 MHz   Image Size:  344 x 193 mm
[     6.913] (II) modeset(G0): h_active: 1920  h_sync: 1968  h_sync_end 2000 h_blank_end 2102 h_border: 0
[     6.913] (II) modeset(G0): v_active: 1080  v_sync: 1090  v_sync_end 1095 v_blanking: 1216 v_border: 0
[     6.913] (II) modeset(G0):  AUO
[     6.913] (II) modeset(G0):  B156HAN07.1
[     6.913] (II) modeset(G0): EDID (in hex):
[     6.913] (II) modeset(G0): 	00ffffffffffff0006afed7100000000
[     6.913] (II) modeset(G0): 	101b0104a5221378026a75a456529c27
[     6.913] (II) modeset(G0): 	0b505400000001010101010101010101
[     6.913] (II) modeset(G0): 	010101010101ce8f80b6703888403020
[     6.913] (II) modeset(G0): 	a50058c1100000000000000000000000
[     6.913] (II) modeset(G0): 	00000000000000000000000000fe0041
[     6.913] (II) modeset(G0): 	554f0a202020202020202020000000fe
[     6.913] (II) modeset(G0): 	004231353648414e30372e31200a00f1
[     6.914] (II) modeset(G0): Printing probed modes for output eDP-1-1
[     6.914] (II) modeset(G0): Modeline "15360x8640"x60.0  11669.25  15360 16824 18560 21760  8640 8643 8648 8938 -hsync +vsync (536.3 kHz d)
[     6.914] (II) modeset(G0): Modeline "15360x8640"x60.0  8273.75  15360 15408 15440 15520  8640 8643 8648 8886 +hsync -vsync (533.1 kHz d)
[     6.914] (II) modeset(G0): Modeline "7680x4320"x120.0  5834.62  7680 8412 9280 10880  4320 4321 4324 4469 doublescan -hsync +vsync (536.3 kHz d)
[     6.914] (II) modeset(G0): Modeline "7680x4320"x120.0  4136.88  7680 7704 7720 7760  4320 4321 4324 4443 doublescan +hsync -vsync (533.1 kHz d)

https://bbs.archlinux.org/viewtopic.php?id=287415

Try the LTS kernel

epse · 2023-07-24 08:53:15

LTS kernel appears to make it all work again! I am not entirely sure what I'm currently rendering on, as the setprovideroutputsource command appears to error out, but it's smooth and functional so I'll just leave it at this. Thanks for the help

seth · 2023-07-24 08:55:26

I'm currently rendering on, as the setprovideroutputsource command appears to error out

You can check xorg log, glxinfo -B, xrandr --listproviders and what is the actual error?

Arch Linux

#1 2023-07-23 08:37:16

[SOLVED] PRIME issues after recent update

#2 2023-07-23 13:22:24

Re: [SOLVED] PRIME issues after recent update

#3 2023-07-24 08:11:13

Re: [SOLVED] PRIME issues after recent update

#4 2023-07-24 08:16:10

Re: [SOLVED] PRIME issues after recent update

#5 2023-07-24 08:53:15

Re: [SOLVED] PRIME issues after recent update

#6 2023-07-24 08:55:26

Re: [SOLVED] PRIME issues after recent update

Board footer