[SOLVED] optimus-manager ERROR : cannot get current display manager na

RichKat · 2020-10-02 14:08:45

Trying to configure optimus-manager. When I run optimus-manager --status I get

Current GPU mode : intel
GPU mode requested for next login : no change
GPU at startup : intel
Temporary config path: no

I would like to configure it to switch to the nvidia gpu when needed, as per https://github.com/Askannz/optimus-mana … nt-options
But when I just try to switch to the nvidia gpu to test that it works using optimus-manager --switch nvidia I get the following error:

ERROR : cannot get current display manager name : No display-manager.service file found
You are about to switch GPUs. This will forcibly close all graphical sessions and all your applications WILL CLOSE.
(you can pass the --no-confirm option to disable this warning)
Continue ? (y/N)

And I'm really not sure what to do.

Last edited by RichKat (2020-10-06 15:23:53)

Lone_Wolf · 2020-10-02 14:23:33

Using optimus-manager switch requires special configuration.

If you're using sddm, lightdm or gdm it should work, For other display managers / methods to startx extra steps are needed.
Check https://github.com/Askannz/optimus-manager and the faq sections the first paragraph links to.

RichKat · 2020-10-02 14:31:21

Yes, I'm using bspwm, but the FAQ sections just say to make sure it starts and cloases with X, nothing about configuring to make the switch command work, I don't think?

Lone_Wolf · 2020-10-02 14:39:21

You need to log out , make the switch, then re-login .

https://github.com/Askannz/optimus-mana … logged-out states that this should be done automagickally by optimus-manager for bspwm .
If that doesn't work for you, you may have to create a new issue on github.

V1del · 2020-10-02 14:49:33

How are you making sure it starts with X? Post your .xinitrc in doubt and make sure you've read: https://wiki.archlinux.org/index.php/Xinit#xinitrc and https://wiki.archlinux.org/index.php/Xinit#xserverrc

RichKat · 2020-10-02 18:08:31

It does log me out and allow me to log back in, but when I run optimus-manager --status I get

A GPU switch from intel to nvidia is pending.
Log out and log back in to apply.

Optimus Manager (Client) version 1.3

Current GPU mode : intel
GPU mode requested for next login : nvidia
GPU at startup : intel
Temporary config path: no

If I su "username" nothing changes. If I restart my computer it goes back to

 Current GPU mode : intel
GPU mode requested for next login : no change
GPU at startup : intel
Temporary config path: no

Am I logging in and out wrong?

My xinitrc looks like this:

~/.fehbg &
/usr/bin/prime-offload &
picom & 
sxhkd &
thunar --daemon &
polybar bar &
bluetoothctl power on &
devmon --info-on-mount &
exec bspwm

The github page says I need to make sure that /usr/bin/prime-switch is run after log out, which I'm still figuring out, so that's not in the xinitrc, if it's meant to be.

RichKat · 2020-10-03 09:51:18

Okay, I am now able to switch GPU's, I added sudo /usr/bin/prime-switch to the end of my xinitrc and removed the exec before the bspwm, so now the switch can happen after log out,

Unfortunately,

When I try to switch to the nvidia GPU the result is many small versions of my desktop tiled around my screen, only the top left one of which I can use. Polybar also vanishes. When I switch desktops it's the top left desktop that changes, not any of the others. Why could this be happening? I'll try to post a screenshot.

Edit, I got a screenshot:
https://imgur.com/a/zzyj98I

Last edited by RichKat (2020-10-03 10:15:47)

Lone_Wolf · 2020-10-03 11:45:00

Your xinitrc is a mess.

You didn't start with a copy of /etc/X11/xinit/xinitrc , see https://wiki.archlinux.org/index.php/Xinit

Some commands in it shouldn't even be in xinitrc at all.

example :
polybar wiki page makes clear that bspwn users should start polybar through an entry in bspwmrc.
https://wiki.archlinux.org/index.php/Polybar#bspwm
THe bspwm wiki page mentions the same thing.

example:
sxhkd comes with a systemd user service file, that should be enabled by systemctl.
https://wiki.archlinux.org/index.php/Sxhkd#Usage

Fix your xinitrc.

Last edited by Lone_Wolf (2020-10-03 11:45:33)

RichKat · 2020-10-03 12:48:27

Ah, I was afraid that would be the case. I'll get on that directly. Still, I don't think that will fix the current issue, so I'm still looking for a solution to that

Lone_Wolf · 2020-10-04 11:31:11

The reason optimus-manager --switch forces a logout is to stop all processes using the gpu before the switch is made.

Almost all lines in your xinitrc end with a & , which tells your shell to run those commands in the background forever.
When you are logging out user processes started with & aren't killed or stopped (on archlinux, other distros may behave differently) .

Some of the commands do need the & , most don't .
Fix your xinitrc , post it so forum users can verify if it is correct.

RichKat · 2020-10-06 15:20:46

First off, thank you very much for your help, I would never have thought that it was my xinitrc that was causing issues.

Here it is at present:

# Some important commands
/usr/bin/prime-offload  
picom & 

# Assorted commands
~/.fehbg &
thunar --daemon &
bluetoothctl power on &
devmon --info-on-mount &

# Start bspwm
bspwm

sudo /usr/bin/prime-switch

I know there are still probably too many &'s, but it's better; most importantly, optimus-manager --switch now works without issue!
I'm currently trying to figure out which of these need &'s and which don't. Before I thought & just meant "go on to the next line"

Is there anything else I need to do to improve my xinitrc?

Lone_Wolf · 2020-10-07 12:05:04

look at /etc/X11/xinit/xinitrc .

The if-fi block just above the twm line is necessary to ensure scripts in /etc/X11/xinit/xinitrc.d folder are executed .
one of them has to do with dbus activation.

fehbg does need the & .

If the bluetootctl command is there to ensure bluetooth is powered on, there's a simple method to enable it systemwide.
https://wiki.archlinux.org/index.php/Bl … after_boot

Arch Linux

#1 2020-10-02 14:08:45

[SOLVED] optimus-manager ERROR : cannot get current display manager na

#2 2020-10-02 14:23:33

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#3 2020-10-02 14:31:21

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#4 2020-10-02 14:39:21

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#5 2020-10-02 14:49:33

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#6 2020-10-02 18:08:31

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#7 2020-10-03 09:51:18

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#8 2020-10-03 11:45:00

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#9 2020-10-03 12:48:27

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#10 2020-10-04 11:31:11

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#11 2020-10-06 15:20:46

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

#12 2020-10-07 12:05:04

Re: [SOLVED] optimus-manager ERROR : cannot get current display manager na

Board footer