[Solved] nvidia-settings CurrentMetaMode error: unable to init server

Shinra · 2021-08-09 04:31:51

Solution: make sure to run nvidia-settings from a termnial in a gui session like KDE Plasma, not from tty.

So I'm following the install guide for nvidia-settings and multi head with Xinerama.
However when executing "nvidia-settings -q CurrentMetaMode" as instructed I get the following output:

Unable to init server: Could not connect: Connection refused
ERROR: The control display is undefined; please run 'nvidia-settings --help' for usage information.

Despite having set the env variable for DISPLAY and it showing up in printenv, I add
"-c :0.0"
Which then returns the same error except instead of complaining the control display is undefined it complains about being unable to find monitors 2 and 3, and does nothing.
(Neither monitor 2 nor 3 are receiving a signal, only 1 has a terminal open, before with nouveau instead of nvidia both worked fine, mimicking the primary monitor)

I added .conf files in /etc/X11/xorg.conf.d
according to the instructions provided for Xinerama configuration.
pacman -Syu shows all packages are up-to-date, no unofficial packages currently installed.
The conf generated by nvidia-xconfig only contains one screen and monitor.

I hope that's sufficient info if not please let me know.

Last edited by Shinra (2021-08-09 20:10:03)

Shinra · 2021-08-09 04:35:22

I should note that I do need 3D capability, if I could go with open source drivers I gladly would

loqs · 2021-08-09 05:14:13

Please post the output of dmesg and the contents of Xorg.0.log from a run with the configuration generated by nvidia-xconfig disabled.

Shinra · 2021-08-09 15:31:21

loqs wrote:

Please post the output of dmesg and the contents of Xorg.0.log from a run with the configuration generated by nvidia-xconfig disabled.

Thanks for your reply,
here is the dmesg output:
http://sprunge.us/641us7

And the Xorg log, with nvidia generated config disabled:
http://sprunge.us/xcdB8B

I should note that to my surprise when I ran Xorg, after blacking out my primary monitor, the other two sprung to life and are now mimicking the primary one, despite spotting lines in the log saying it can't find the screens.

Thanks in advance for the assistance

Edit: optimistic about the monitors working I retried passing the query to nvidia-settings, unfortunately the error mentioned above persists.:
ERROR: Unable to find display on any available system
Twice, presumably for the second and third monitor.
And the server error mentioned before.

-Shinra

Last edited by Shinra (2021-08-09 15:35:56)

Shinra · 2021-08-09 15:50:33

Another thing perhaps worth noting is when I read through the log myself I noted that there is mention of DFP-6, DFP-2, and DFP-4.
However, in the configurations I created in xorg.conf.d as instructed, I instead defined DFP-0, DFP-1, and DFP-2 for my monitors.
I reckon this means I defined these wrongly, but I'm unsure if that would be the cause of the error detailed below that trace.

seth · 2021-08-09 16:04:53

That xorg log is not from a successful Xorg run - the consequence would be to not have a GUI session.
The cause is that there's still some garbage config file in /{etc,usr/share}/X11/xorg.conf*, forcing a server layout and some monitors that don't exist.

ls /{etc,usr/share}/X11/xorg.conf*

To understand what you're currently running and on which driver

glxinfo -B
echo $XDG_SESSION_TYPE

Shinra · 2021-08-09 16:18:18

seth wrote:

That xorg log is not from a successful Xorg run - the consequence would be to not have a GUI session.
The cause is that there's still some garbage config file in /{etc,usr/share}/X11/xorg.conf*, forcing a server layout and some monitors that don't exist.
ls /{etc,usr/share}/X11/xorg.conf*
To understand what you're currently running and on which driver
glxinfo -B
echo $XDG_SESSION_TYPE

The ls command you posted returns the following:
/etc/X11/xorg.conf.backup
/etc/X11/xorg.conf.nvidia-xconfig-original

/etc/X11/xorg.conf.d:
20-nvidia.conf
30-screen-AOC24G2U-0.conf
31-screen-AOC24G2U-1.conf
32-screen-AOC24G2U-2.conf
90-serverlayout.conf

/usr/share/X11/xorg.conf.d:
10-nvidia-drm-outputclass.conf
10-quirks.conf
40-libinput.conf

glxinfo doesn't exist, and the last command returns "tty"

seth · 2021-08-09 16:24:24

* nvidia-settings requires a GUI session, you cannot run that from a console.
* glxinfo is in mesa-demos
* move away everything in /etc/X11/xorg.conf.d

Shinra · 2021-08-09 16:33:06

seth wrote:

* nvidia-settings requires a GUI session, you cannot run that from a console.
* glxinfo is in mesa-demos
* move away everything in /etc/X11/xorg.conf.d

Understood, I'll have a go after dinner and relay back my findings

Shinra · 2021-08-09 17:06:43

I moved all the configs in xorg.conf.d to a backup directory, and running glxinfo returns the following:
Error: unable to open display :0.0

I suppose this is okay to ask since we're in the noob corner, I was planning to use plasma but that requires a working Xorg install, would one of the display managers listed on the wiki work or am I looking at the wrong thing?
Edit: to run nvidia-settings in I mean

Update: ran Xorg after doing the above, I assume it works; all displays are receiving a signal but they're all blank (embarrassingly not sure how to exit this rn haha)

Last edited by Shinra (2021-08-09 17:18:58)

seth · 2021-08-09 17:16:30

glxinfo requires a running X11 server as well (hence glXinfo)
You need to setup the means to run one, whether through any DM or xinit/startx does ultimately not matter.

Punching all these commands into the linux console is pointless, though.

Shinra · 2021-08-09 17:21:39

seth wrote:

glxinfo requires a running X11 server as well (hence glXinfo)
You need to setup the means to run one, whether through any DM or xinit/startx does ultimately not matter.
Punching all these commands into the linux console is pointless, though.

My bad, I'll reboot and setup xinit

Shinra · 2021-08-09 18:11:28

Alright so I've set up KDE with xinit, this is the output of glxinfo:
http://sprunge.us1U70hp

However unless you see an issue that I don't I think you've solved it for me, the CurrentMetaMode query passed to nvidia-settings actually outputs some useful data now that I run it with yakuake within KDE.

If that's it then thanks very much, I'll edit the op to say that running it from within a gui session is required, and not within tty, otherwise please let me know if there's something I still have to do.

seth · 2021-08-09 19:56:50

http://sprunge.us1u70hp/ is a bad link and even http://sprunge.us/1u70hp doesn't exist.

Either way, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Shinra · 2021-08-09 20:07:42

seth wrote:

http://sprunge.us1u70hp/ is a bad link and even http://sprunge.us/1u70hp doesn't exist.
Either way, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Apologies, these are the only pastebins I got to work with the large files.
I'll mark the problem as solved.

Thanks a lot for the help ^^
-shinra

Arch Linux

#1 2021-08-09 04:31:51

[Solved] nvidia-settings CurrentMetaMode error: unable to init server

#2 2021-08-09 04:35:22

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#3 2021-08-09 05:14:13

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#4 2021-08-09 15:31:21

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#5 2021-08-09 15:50:33

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#6 2021-08-09 16:04:53

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#7 2021-08-09 16:18:18

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#8 2021-08-09 16:24:24

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#9 2021-08-09 16:33:06

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#10 2021-08-09 17:06:43

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#11 2021-08-09 17:16:30

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#12 2021-08-09 17:21:39

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#13 2021-08-09 18:11:28

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#14 2021-08-09 19:56:50

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

#15 2021-08-09 20:07:42

Re: [Solved] nvidia-settings CurrentMetaMode error: unable to init server

Board footer