Didn't restart display manager after choose graphic card?

[askannz]

Didn't restart display manager after choose graphic card?

[Askannz]

Please format your logs using code blocks (https://guides.github.com/features/mastering-markdown/), or use a pastebin (https://pastebin.com/).

It looks like the issue is that the alias service display-manager.service is not actually linked to your display manager.

What is are your distribution and desktop environment ?

[xversion1]

Please format your logs using code blocks (https://guides.github.com/features/mastering-markdown/), or use a pastebin (https://pastebin.com/).

Here pastebin: https://pastebin.com/sYau9Dxw

It looks like the issue is that the alias service display-manager.service is not actually linked to your display manager.

What is are your distribution and desktop environment ?

I use openbox on Arch Linux.

[Askannz]

Ah so no desktop environment then. Do you use a login manager ? (GDM, SDDM, LightDM) ?

[xversion1]

If the ones you mentioned don't come with other packages then I don't think so. I didn't remember install any of them, and I have to type username and password at terminal to login. There appears no fancy login screen.

[Askannz]

Yeah, you don't have a login manager, that's why the daemon cannot restart it (login manager = display manager).

Please read this section of the README : https://github.com/Askannz/optimus-manager#i-do-not-use-a-display-manager-i-use-startx-or-xinit

[xversion1]

I dont understand the part "do it from TTY". Does it mean I have to switch card before I login openbox?

[xversion1]

First, you have to add the line /usr/bin/optimus-manager_Xsetup to your .xinitrc so that this script is executed when X starts

So I just put this line on .xinitrc or I need something like exec or export before it?

[Askannz]

I dont understand the part "do it from TTY". Does it mean I have to switch card before I login openbox?

Actually you can run optimus-manager --switch <mode> anytime, but to apply the change you need to stop the X server (i.e. logout from Openbox), run /usr/bin/optimus-manager-setup --setup-start and log back in.

So I just put this line on .xinitrc or I need something like exec or export before it?

No, just put the line.

[xversion1]

I think I did it. When I login the text size smaller than before and I can run nvidia-settings without error. But when I check by using you command glxinfo | grep "server glx vendor string", the result is SGI? Is there another way to check?

[Askannz]

What's the output of nvidia-smi ? You should see a list of processes there. If X or Xorg is in the list, it means it's running on the Nvidia GPU.

[xversion1]

Is that it?
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 803 G /usr/lib/Xorg 61MiB |
+-----------------------------------------------------------------------------+

[Askannz]

Yep, it's there, you should be good then.

It worries me that glxinfo does not report Nvidia, though...because I rely on that in the client program to check the current GPU in use.

Are you able to run any OpenGL program ? Like for instance, the program glxgears from the package mesa-demos ? (it's a simple OpenGL demo)

[xversion1]

Are you able to run any OpenGL program ? Like for instance, the program glxgears from the package mesa-demos ? (it's a simple OpenGL demo)

Yeah, paste the command in the terminal and I saw 3 gears running.
I have another problem. After reboot and login I can see any on the screen. I think the screen is off. I had this problem before when I tried to use bumblebee. My built-in screen was off and the second screen which was connected via HDMI port was on (kind of like one of you trouble shoot on the main page). I know what caused it. It's the /etc/X11/xorg.conf.d/10-optimus-manager.conf file, if I delete this one then my built-in screen back on, but it's very inconvenient way to fix. Do you have any suggestion?

Update:

It worries me that glxinfo does not report Nvidia, though...because I rely on that in the client program to check the current GPU in use.

I tried optimus-manager --print-mode and it returned Intel. You really need to fix it.

[Askannz]

I know what caused it. It's the /etc/X11/xorg.conf.d/10-optimus-manager.conf file, if I delete this one then my built-in screen back on

Well this file is auto-generated by optimus-manager to tell Xorg which GPU to use. If you delete it then it's as if you are not using optimus-manager at all.
Does this problem happens not matter which GPU you use ?

[xversion1]

Does this problem happens not matter which GPU you use ?

No, it doesn't. If I run all of your steps to switch to nvidia then everything is fine, but if I do nothing and login as usual then I got a black screen.
And I can't enable optimus-manager so it can run at startup.

$ systemctl enable optimus-manager.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

You see, either the way (complete steps to switch to nvidia or delete file so buit-in screen can back on) costs me time to login.

[Askannz]

Ah yes, not being able to enable the daemon is a bug indeed, thanks for reporting that. I'll fix it for the next release.

You see, either the way (complete steps to switch to nvidia or delete file so buit-in screen can back on) costs me time to login.

Well, I suggest you use an alias to run those commands automatically. Like if you use startx for instance, you can set up an alias to run
/usr/bin/optimus-manager-setup --setup-start; startx; /usr/bin/optimus-manager-setup --setup-stop
all at once.

[xversion1]

Is there any conflict between optimus-manager and laptop-mode-tools/tlp?
I don't know why but from yesterday it doens't work anymore, and I also did update nvidia driver to 4.15.

[Askannz]

Is there any conflict between optimus-manager and laptop-mode-tools/tlp?

As far as I know, there's no reason to be any conflict. Unless maybe they are doing something broken with PCI power management, but in that case it's a bug you should report to them.