Package Details: nvidia-xrun-git 0.3.79.gaf3b734-1

Git Clone URL: (read-only, click to copy)
Package Base: nvidia-xrun-git
Description: Script to run dedicated X server with discrete nvidia graphics (git version)
Upstream URL:
Licenses: GPL
Conflicts: nvidia-xrun
Provides: nvidia-xrun, nvidia-xrun-git
Submitter: robus
Maintainer: None
Last Packager: Witko
Votes: 19
Popularity: 0.000000
First Submitted: 2016-10-20 20:37 (UTC)
Last Updated: 2019-05-07 10:32 (UTC)

Latest Comments

1 2 3 4 Next › Last »

seniorkiller commented on 2022-06-20 02:55 (UTC)

somehow i got an error with this tee /sys/bus/pci/devices/0000:00:01.0/power/control no such file or dir

i followed the wiki but still it doesnt work. i ever use it before and it work fine then i give optimus manager a try

falling back to xrun because optimus manager doenst support ly dm and i cant get this going again

ive tried to change the /etc/default/nvidia-xrun controler bus but i found 4 PCI express in lspci, just used the first one and it didnt work.

i some how manage to get it to the black screen but it instanly stopped(the server terminate by it self)

topcat01aur commented on 2022-04-29 20:24 (UTC)

@edoantonioco yes I use it on multiple machines. Works perfectly. Make sure to follow my recommendations and double check ALL folders for stray configuration files.

edoantonioco commented on 2022-01-12 21:42 (UTC)

Is this working properly? Since its flagged out of date

topcat01aur commented on 2021-11-22 00:22 (UTC)

There seems to a race condition between nvidia-xrun-pm.service and systemd-moudules-load.service which loads the nvidia modules. If the latter runs first, nvidia-xrun-pm will hang (actually the tee command) during device removal. If on the other hand nvidia-xrun-pm runs first then it will succeed, and later the modules will fail to load with an error (which is harmless but ugly).

The solution is to blacklist the nvidia modules as already described in In this case the subsequent failed module load attempt is also avoided. This of course does not affect running nvidia-xrun later.

I understand all this is known but probably still worth a mention.

radiomike commented on 2021-11-15 12:33 (UTC) (edited on 2021-11-15 12:35 (UTC) by radiomike)

Another solution, as I wasn't able to get others working.

In the serverlayout section of /etc/X11/nvidia-xorg.conf change Screen 1 "nvidia" to Screen "nvidia"

Also placing 10-nvidia-drm-outputclass.conf from in /etc/X11/nvidia-xorg.conf.d seems to help with some small issues I came accross.

aiyion commented on 2021-11-14 16:19 (UTC)

Crap. It worked. May somebody explain, what we just did?

aiyion commented on 2021-11-14 16:16 (UTC) (edited on 2021-11-14 16:19 (UTC) by aiyion)

This feels wrong -.-' Will try. Isn't there some sort of config checker, we can throw at this? I mean, sure I'll delete that folder; but by all means; your contents possibly aren't mine? Blindly replacing and deleting stuff is not a proper solution...

Lander commented on 2021-11-14 13:14 (UTC)

@aiyion Got the same issue, fixed it by deleting the contents of the /etc/X11/nvidia-xorg.conf.d directory

aiyion commented on 2021-11-14 12:54 (UTC)

xorg does indeed crash, but replacing the contents hangs the system on my end.