After install video-nvidia manjaro can't boot

Show me the content of the directories by showing me the output of those commands:

ls /etc/X11/
ls /etc/X11/xorg.conf.d/
ls /etc/X11/mhwd.d/

[fla@fla-pc ~]$ ls /etc/X11/
mhwd.d  xinit  xorg.conf.d
[fla@fla-pc ~]$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  90-mhwd.conf
[fla@fla-pc ~]$ ls /etc/X11/mhwd.d/
intel.conf
[fla@fla-pc ~]$

Now stay in the session, don't reboot, because you won't be able to boot system if you won't finish it completely.

Install optimus-manager:

sudo pacman -S optimus-manager

I see only two graphical confs in your folders. Now let's disable them by adding .bak extension (so you could bring it back just in case) by running those commands:

sudo mv /etc/X11/xorg.conf.d/90-mhwd.conf /etc/X11/xorg.conf.d/90-mhwd.conf.bak
sudo mv /etc/X11/mhwd.d/intel.conf /etc/X11/mhwd.d/intel.conf.bak

Then check the status of bumblebee:

sudo systemctl status bumblebeed

If it's active run:

sudo systemctl stop bumblebeed
sudo systemctl disable bumblebeed

Activate optimus-manager:

sudo systemctl start optimus-manager.service
sudo systemctl enable optimus-manager.service

Check if it's running correctly:

sudo systemctl status optimus-manager

If all went well, it's time to reboot, cross fingers if the system boot correctly. Let me know how it went and we go to the next step which is checking which card is used and how to switch them.


[fla@fla-pc ~]$ ls /etc/X11/
mhwd.d  xinit  xorg.conf.d
[fla@fla-pc ~]$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  90-mhwd.conf
[fla@fla-pc ~]$ ls /etc/X11/mhwd.d/
intel.conf
[fla@fla-pc ~]$ sudo pacman -S optimus-manager
[sudo] password for fla: 
resolving dependencies...
looking for conflicting packages...

Packages (1) optimus-manager-0.5-1

Total Download Size:   0.04 MiB
Total Installed Size:  0.20 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 optimus-manager-0.5-1-any                                                                  43.2 KiB  22.1K/s 00:02 [#####################################################################] 100%
(1/1) checking keys in keyring                                                                                      [#####################################################################] 100%
(1/1) checking package integrity                                                                                    [#####################################################################] 100%
(1/1) loading package files                                                                                         [#####################################################################] 100%
(1/1) checking for file conflicts                                                                                   [#####################################################################] 100%
(1/1) checking available disk space                                                                                 [#####################################################################] 100%
:: Processing package changes...
(1/1) installing optimus-manager                                                                                    [#####################################################################] 100%
:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...
[fla@fla-pc ~]$ sudo mv /etc/X11/xorg.conf.d/90-mhwd.conf /etc/X11/xorg.conf.d/90-mhwd.conf.bak
[fla@fla-pc ~]$ sudo mv /etc/X11/mhwd.d/intel.conf /etc/X11/mhwd.d/intel.conf.bak
[fla@fla-pc ~]$ sudo systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-12-26 23:36:02 +0330; 29min ago
 Main PID: 512 (bumblebeed)
    Tasks: 1 (limit: 4915)
   Memory: 1.4M
   CGroup: /system.slice/bumblebeed.service
           └─512 /usr/bin/bumblebeed --use-syslog

Dec 26 23:36:02 fla-pc systemd[1]: Started Bumblebee C Daemon.
Dec 26 23:36:03 fla-pc bumblebeed[512]: /usr/bin/bumblebeed 3.2.1-2017-02-27-Format:%h$ started
[fla@fla-pc ~]$ sudo systemctl stop bumblebeed
[fla@fla-pc ~]$ sudo systemctl disable bumblebeed
Removed /etc/systemd/system/multi-user.target.wants/bumblebeed.service.
[fla@fla-pc ~]$ sudo systemctl start optimus-manager.service
[fla@fla-pc ~]$ sudo systemctl enable optimus-manager.service
Created symlink /etc/systemd/system/graphical.target.wants/optimus-manager.service β†’ /usr/lib/systemd/system/optimus-manager.service.
[fla@fla-pc ~]$ sudo systemctl status optimus-manager
● optimus-manager.service - Optimus Manager Commands Daemon
   Loaded: loaded (/usr/lib/systemd/system/optimus-manager.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2018-12-27 00:06:26 +0330; 27s ago
 Main PID: 14009 (python)
    Tasks: 1 (limit: 4915)
   Memory: 16.5M
   CGroup: /system.slice/optimus-manager.service
           └─14009 /usr/bin/python -u /usr/bin/optimus-manager-daemon

Dec 27 00:06:26 fla-pc systemd[1]: Started Optimus Manager Commands Daemon.
Dec 27 00:06:27 fla-pc python[14009]: Optimus Manager (Daemon) version 0.5
Dec 27 00:06:27 fla-pc python[14009]: Awaiting commands
[fla@fla-pc ~]$

OK, looks good :slight_smile:

Now reboot.

Don't keep me waiting. I'm eager to know if it works :stuck_out_tongue_winking_eye: .

1 Like

yes manjaro is boot
I fear to :grin:

optimus-manager --switch nvidia

what is this launcher

So system booted correctly. Yay :grinning:

Check what it's running now, I expect intel:


optimus-manager --print-mode

Then close everything and leave only terminal and switch using this command:

optimus-manager --switch nvidia

Then check again with:


optimus-manager --print-mode

If it works and you can switch correctly I can show you how to create desktop files to switch GPU mode without using a terminal.

1 Like

first was on Intel after

optimus-manager --switch nvidia

and rest display and check with

optimus-manager --print-mode

again on intel :thinking: but my laptop power color changed to red (in windows when i used nvidia driver color changed to red)
are you sure don't should reboot for first time?

Well, maybe reboot will help. I thought the first one will do but maybe you need to use the command and then reboot. This is what I did so go ahead, reboot it now. After it starts working reboots won't be needed, only session reloads.

just showing intel (switch to intel and nvidia just showing intel)

Did you cleared everythink in /etc/X11/mhwd.d and /etc/X11/xorg.conf.d ?

If yes maybe U forgot to enable daemon "sudo systemctl enable optimus-manager" then reboot :slight_smile:

Hmm... That was the case for me until I rebooted and now it works.

So let's check journalctl:

journalctl -u optimus-manager.service

and

journalctl -u display-manager.service

And also, what is your DE? I forgot to ask but this is important because some display managers that come with certain DEs are not supported or must be configured manually.

Thats right its litte broken on GDM. I tried to figure problem on gdm recently

He already posted the output above and yes, optimus-manager process is running. If I red his ls output correctly he only had 2 confs, but maybe some showed up, this was very fresh setup of bumblebee so @fla let's check again:

ls /etc/X11/
ls /etc/X11/xorg.conf.d/
ls /etc/X11/mhwd.d/

i have KDE. it should be SDDM :thinking:

[fla@fla-pc ~]$ journalctl -u optimus-manager.service
-- Logs begin at Wed 2018-12-26 21:32:07 +0330, end at Thu 2018-12-27 00:49:40 +0330. --
Dec 27 00:06:26 fla-pc systemd[1]: Started Optimus Manager Commands Daemon.
Dec 27 00:06:27 fla-pc python[14009]: Optimus Manager (Daemon) version 0.5
Dec 27 00:06:27 fla-pc python[14009]: Awaiting commands
Dec 27 00:10:46 fla-pc python[14009]: Process stop requested
Dec 27 00:10:46 fla-pc python[14009]: Closing and removing the socket...
Dec 27 00:10:46 fla-pc python[14009]: Goodbye !
Dec 27 00:10:46 fla-pc systemd[1]: Stopping Optimus Manager Commands Daemon...
Dec 27 00:10:46 fla-pc systemd[1]: Stopped Optimus Manager Commands Daemon.
-- Reboot --
Dec 27 00:11:19 fla-pc systemd[1]: Started Optimus Manager Commands Daemon.
Dec 27 00:11:26 fla-pc python[526]: Optimus Manager (Daemon) version 0.5
Dec 27 00:11:26 fla-pc python[526]: Awaiting commands
Dec 27 00:26:50 fla-pc python[526]: Received command : nvidia
Dec 27 00:26:50 fla-pc python[526]: Writing requested mode
Dec 27 00:26:50 fla-pc python[526]: Restarting login manager
Dec 27 00:35:44 fla-pc python[526]: Process stop requested
Dec 27 00:35:44 fla-pc python[526]: Closing and removing the socket...
Dec 27 00:35:44 fla-pc python[526]: Goodbye !
Dec 27 00:35:44 fla-pc systemd[1]: Stopping Optimus Manager Commands Daemon...
Dec 27 00:35:44 fla-pc systemd[1]: Stopped Optimus Manager Commands Daemon.
-- Reboot --
Dec 27 00:36:16 fla-pc systemd[1]: Started Optimus Manager Commands Daemon.
Dec 27 00:36:24 fla-pc python[509]: Optimus Manager (Daemon) version 0.5
Dec 27 00:36:24 fla-pc python[509]: Awaiting commands
Dec 27 00:38:09 fla-pc python[509]: Received command : nvidia
Dec 27 00:38:09 fla-pc python[509]: Writing requested mode
Dec 27 00:38:09 fla-pc python[509]: Restarting login manager
Dec 27 00:38:57 fla-pc python[509]: Received command : intel
Dec 27 00:38:57 fla-pc python[509]: Writing requested mode
Dec 27 00:38:57 fla-pc python[509]: Restarting login manager
Dec 27 00:40:04 fla-pc python[509]: Received command : nvidia
Dec 27 00:40:04 fla-pc python[509]: Writing requested mode
Dec 27 00:40:04 fla-pc python[509]: Restarting login manager
[fla@fla-pc ~]$ journalctl -u display-manager.service
-- Logs begin at Wed 2018-12-26 21:32:07 +0330, end at Thu 2018-12-27 00:49:50 +0330. --
-- No entries --
[fla@fla-pc ~]$
[fla@fla-pc ~]$ ls /etc/X11/
mhwd.d  xinit  xorg.conf.d
[fla@fla-pc ~]$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  90-mhwd.conf.bak
[fla@fla-pc ~]$ ls /etc/X11/mhwd.d/
intel.conf.bak
[fla@fla-pc ~]$

90-mhwd.conf.bak color is red and moving up!!

this? :thinking:

sudo mv /etc/X11/xorg.conf.d/90-mhwd.conf /etc/X11/xorg.conf.d/90-mhwd.conf.bak
sudo mv /etc/X11/mhwd.d/intel.conf /etc/X11/mhwd.d/intel.conf.bak

It looks good. No additional, conflicting confs in those locations.
journalctl also shows everything OK. It looks the same for me.

So far all looks correct. Plasma is supported, I also use it so there should be nothing extra to do.

Check again:

sudo systemctl status optimus-manager
sudo systemctl status bumblebeed
and then try again switch to nvidia and after session starts check:

optimus-manager --print-mode

Not sure what you are asking. Those commands simply re-named graphical confs and added .bak in the end which made them inactive. Confs are there but not working. You can get rid of the .bak to enable them but they would conflict with optimus-manager so leave them as they are. So all looks all right so far. I see no errors and everything behaves as it should. If it really stays in intel and isn't switching to nvidia then I have no idea what is wrong.

It's late for you, go to sleep for now. Maybe someone will have idea how to debug it.

EDIT: I just noticed, you should have /etc/X11/xorg.conf.d/10-optimus-manager.conf and I don't see this new conf on your computer. That may be the cause.

1 Like

not working. just intel.
after shot down it's there

[fla@fla-pc ~]$ ls /etc/X11/
mhwd.d  xinit  xorg.conf.d
[fla@fla-pc ~]$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  10-optimus-manager.conf  90-mhwd.conf.bak
[fla@fla-pc ~]$ ls /etc/X11/mhwd.d/
intel.conf.bak
[fla@fla-pc ~]$

sudo systemctl status optimus-manager
sudo systemctl status bumblebeed

optimus-manager has active
bumblebeed is inactive (dead)

Forum kindly sponsored by