Can't switch to nvidia card about optimus-manager HOT 43 CLOSED

Try latest version on AUR

from optimus-manager.

Yes please, latest version should be 0.6.

(If the problem persists, please also post the log from the GDM service)

from optimus-manager.

I installed yaourt and then installed optimus-manager's last version (0.6). After I reboot GDM didn't start.

Here my installed nvidia drivers (some of this installed by optimus-manager as a dependency):

And here the gdm status and logs:

from optimus-manager.

Can't do much with that limited log, use the command journalctl -u gdm -b0 to get the full log.

from optimus-manager.

I removed the nvidia drivers and I could login, then I installed again the latest version with its dependencies.
Now I can login but I can't switch, like the beginning

Here are the logs now..

 journalctl -u gdm -b0
-- Logs begin at Tue 2018-12-25 22:30:42 -03, end at Thu 2019-01-03 23:21:03 -03. --
ene 03 18:36:44 Meli systemd[1]: Starting GNOME Display Manager...
ene 03 18:36:44 Meli python[581]: Optimus Manager (DM setup) version 0.6
ene 03 18:36:44 Meli python[581]: Setting up Optimus configuration
ene 03 18:36:44 Meli python[581]: Cannot read requested mode : File /var/lib/optimus-manager/requested_mode not found..
ene 03 18:36:44 Meli python[581]: Using startup mode instead.
ene 03 18:36:44 Meli python[581]: Startup mode : nvidia_once
ene 03 18:36:44 Meli python[581]: Requested mode : nvidia
ene 03 18:36:44 Meli python[581]: Switching to Nvidia
ene 03 18:36:44 Meli python[581]: Unloading nouveau module
ene 03 18:36:44 Meli python[581]: Loading Nvidia modules
ene 03 18:36:44 Meli python[581]: Cannot switch GPUS : Cannot load Nvidia modules : Failed to execute 'modprobe nvidia NVreg_UsePageAttributeTable=1' : modprobe: FATAL: Module nvidia not found in directory /lib/>
ene 03 18:36:44 Meli systemd[1]: Started GNOME Display Manager.
ene 03 18:36:44 Meli gdm-launch-environment][619]: accountsservice: Could not get current seat: No hay datos disponibles
ene 03 18:36:54 Meli gdm-password][1241]: accountsservice: Could not get current seat: No hay datos disponibles
ene 03 18:37:00 Meli gdm-password][1241]: pam_unix(gdm-password:session): session opened for user martin by (uid=0)

from optimus-manager.

Failed to execute 'modprobe nvidia NVreg_UsePageAttributeTable=1' : modprobe: FATAL: Module nvidia not found in directory...

Sounds like your Nvidia driver isn't installed properly.
I wonder if it could be a stupid conflict between the driver packages of Manjaro and the dependencies pulled by optimus-manager. That's probably something I should have allocated more testing to.

If you completely remove optimus-manager and install the latest nvidia driver like you did before, are you able to execute the following commands without errors ?

sudo modprobe nvidia
nvidia-smi

from optimus-manager.

With this installed:

➜  ~ pacman -Q |grep nvidia
linux316-nvidia 1:415.25-1
mhwd-nvidia 1:415.25-1
mhwd-nvidia-340xx 340.107-1
mhwd-nvidia-390xx 390.87-1
nvidia-utils 1:415.25-1
➜  ~ pacman -Q |grep optimus
optimus-manager 0.6-1

This is the error:

➜  ~ sudo modprobe nvidia
[sudo] password for martin: 
modprobe: FATAL: Module nvidia not found in directory /lib/modules/4.19.13-1-MANJARO
➜  ~ nvidia-smi

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

from optimus-manager.

Remove optimus-manager, and remove linux316-nvidia, mhwd-nvidia-340xx, mhwd-nvidia-390xx as well (those are outdated).
Then reinstall the nvidia driver using MHWD.

Then try those commands again.

from optimus-manager.

It works!!! The problem was the linux316-nvidia driver.
I saw the kernel configuration:

So I searched for a linux driver with this version. I installed linux419-nvidia and it works.
In summary:
1- Remove linux316-nvidia and its files (but not its dependencies.. with -dd):
sudo pacman -Rsn -dd linux316-nvidia
2 - Install new driver (linux419-nvidia):
sudo pacman -S linux419-nvidia

3- My installed packages at last:

➜  ~ pacman -Q |grep nvidia                 
linux419-nvidia 1:415.25-2
mhwd-nvidia 1:415.25-1
mhwd-nvidia-340xx 340.107-1
mhwd-nvidia-390xx 390.87-1
nvidia-utils 1:415.25-1
➜  ~ pacman -Q |grep optimus                
optimus-manager 0.6-1

4 - Set startup intel just in case:
optimus-manager --set-startup intel

5 - Reboot your pc
6 - Switch to nvidia
optimus-manager --switch nvidia

Really thanks a lot for your time!!

from optimus-manager.

It works!!! The problem was the linux316-nvidia driver.
I saw the kernel configuration:

So I searched for a linux driver with this version. I installed linux419-nvidia and it works.
In summary:
1- Remove linux316-nvidia and its files (but not its dependencies.. with -dd):
sudo pacman -Rsn -dd linux316-nvidia
2 - Install new driver (linux419-nvidia):
sudo pacman -S linux419-nvidia

3- My installed packages at last:

➜  ~ pacman -Q |grep nvidia                 
linux419-nvidia 1:415.25-2
mhwd-nvidia 1:415.25-1
mhwd-nvidia-340xx 340.107-1
mhwd-nvidia-390xx 390.87-1
nvidia-utils 1:415.25-1
➜  ~ pacman -Q |grep optimus                
optimus-manager 0.6-1

4 - Set startup intel just in case:
optimus-manager --set-startup intel

5 - Reboot your pc
6 - Switch to nvidia
optimus-manager --switch nvidia

This solution does not seem to work for linux420-nvidia drivers.

~ pacman -Q |grep nvidia   
linux420-nvidia 1:415.25-0
mhwd-nvidia 1:415.25-1
nvidia-utils 1:415.25-1

➜  ~ pacman -Q |grep optimus                
optimus-manager 0.6-1

I'm still unable to switch to Nvidia after following the above suggestions despite the optimus-manager service being active.

from optimus-manager.

I don't close this issue because I want to test it again.. It worked for me, but when I removed all and reinstall the drivers, it stop working.
I'm trying to find a solution.
If you get a black screen and you can't login you can do this:

• on grub's manjaro entry press 'e'
• add 'systemd.unit=rescue.target' at the end of the line that start with linux
• press F10 to boot
• login as root and uninstall all nvidia packages
• reboot

from optimus-manager.

I don't close this issue because I want to test it again.. It worked for me, but when I removed all and reinstall the drivers, it stop working.
I'm trying to find a solution.
If you get a black screen and you can't login you can do this:

on grub's manjaro entry press 'e'
add 'systemd.unit=rescue.target' at the end of the line that start with linux
press F10 to boot
login as root and uninstall all nvidia packages
reboot

I have the same issue. If I remove optimus-manger, uninstall then reinstall drivers I'm able to switch to Nvidia. However, upon reboot I'm unable to switch back to Nvidia.

I was able to solve any issues with a black screen upon boot by adding acpi_osi=! acpi_osi="Windows 2015" to my kernel boot parameters

from optimus-manager.

Still having the same issue so will add to this thread instead of creating a new ticket because I think I'm experiencing the same problem as @Martin317

OS: Manjaro 18.0.2 Illyria
Kernel: x86_64 Linux 4.20.0-1-MANJARO
DE: KDE 5.53.0 / Plasma 5.14.4
WM: KWin
CPU: Intel Core i7-8750H
GPU:Intel® HD Graphics 630 and Nvidia GeForce GTX 1050Ti
Laptop: Dell XPS 9570

pacman -Q |grep optimus  
optimus-manager 0.6-1

~ pacman -Q |grep nvidia
linux420-nvidia 1:415.25-0
mhwd-nvidia 1:415.25-1
nvidia-utils 1:415.25-1

Would having a mhwd-gpu.conf file interfere with GPU switching?

~ ls /etc/modprobe.d/
`mhwd-gpu.conf  optimus-manager.conf`

from optimus-manager.

Could you describe the issue more accurately ?

Are you having an issue with starting in Nvidia mode, or starting in Intel and then switching to Nvidia ?

In any case, how does it fail ? (like, is there a black screen, are you back to the login screen, are you able to switch to a TTY, etc)

from optimus-manager.

Could you describe the issue more accurately ?

Are you having an issue with starting in Nvidia mode, or starting in Intel and then switching to Nvidia ?

In any case, how does it fail ? (like, is there a black screen, are you back to the login screen, are you able to switch to a TTY, etc)

The issue is starting in Intel and then switching to Nvidia.
Steps:
When in Intel mode and I want to switch to Nvidia I will use the --switch nvidia command

optimus-manager --switch nvidia              
WARNING : You are about to switch GPUs. This will restart the display manager and all your applications WILL CLOSE.
(you can pass the --no-confirm option to disable this warning)
Continue ? (y/N)

Afterward the screen goes black for 2 seconds before displaying the login screen.
After I login --print-mode still shows it's using intel

optimus-manager --print-mode   
Current mode : intel

from optimus-manager.

Can you post the log of SDDM after trying to switch to Nvidia ? (use journalctl -u sddm -b0 --no-pager)

from optimus-manager.

https://pastebin.com/KbLWL079

Issue here:
Jan 17 12:08:25 n-pc python[1775]: Cannot switch GPUS : Cannot load Nvidia modules : Failed to execute 'modprobe nvidia NVreg_UsePageAttributeTable=1' : modprobe: FATAL: Module nvidia not found in directory /lib/modules/4.20.0-1-MANJARO

from optimus-manager.

This error means that the nvidia module is not installed for your current kernel. This is not a bug of optimus-manager. Try installing the package linux420-nvidia.

from optimus-manager.

This error means that the nvidia module is not installed for your current kernel. This is not a bug of optimus-manager. Try installing the package linux420-nvidia.

After reinstalling 'linux420-nvidia' and rebooting, there is still an issue.

https://pastebin.com/tAC0garJ

from optimus-manager.

Cannot switch GPUS : bbswitch refuses to turn ON the GPU

That could be a hardware incompatibility with your laptop model. What happens if you set the switching option to nouveau ?

(note : please use pastebins to post logs instead of copypasting them directly in your posts)

from optimus-manager.

That could be a hardware incompatibility with your laptop model. What happens if you set the switching option to nouveau ?

Never considered that.
After setting the switching option to nouveau the same happens when trying to switch to nvidia. Black screen for a few seconds then login screen. After logging in the system is still in intel mode.

Logs: https://pastebin.com/LEL8HQwc

from optimus-manager.

modprobe: ERROR: could not insert 'nvidia': No such device

Hmmm 🤔
Try to blacklist the module bbswitch (create the file /usr/lib/modprobe.d/blacklist_bbswitch.conf and put blacklist bbswitch).

Then restart your computer and try again.

from optimus-manager.

modprobe: ERROR: could not insert 'nvidia': No such device

Hmmm thinking
Try to blacklist the module bbswitch (create the file /usr/lib/modprobe.d/blacklist_bbswitch.conf and put blacklist bbswitch).

Then restart your computer and try again.

This seems to work!

from optimus-manager.

Alright, so it's a bbswitch conflict.

Someone else has asked for the bbswitch package to be removed from the dependencies because of another issue, so from the next release on I'll just mark it as optional and have a runtime check to see if it is available. That should solve both issues.

Thanks for your input !

from optimus-manager.

Optimus-manager works for me, but I have a friend I tried to guide to set it up but he has the same issue, or at least the outcome is the same: system boots in intel mode and when trying to switch to nvidia, session restarts and he is still in intel mode. We couldn't see any errors in any journals so far.

I we wanted to try blacklisting bbswitch, one needs to have nouveau installed first? Right? But by default, it isn't so which package needs to be added to install nouveau?

So am I right to say that first we need to install:

sudo pacman -S xf86-video-nouveau

then blacklist bbswitch, reboot and test if it works?

from optimus-manager.

Hello, I will try it!! Thanks to all.

from optimus-manager.

@michaldybczak , the nouveau driver is already built into the kernel so you don't have to install anything else. Not sure what this package does.

Also, even though the symptoms of your problem are similar to Martin's, there can be a whole range of reasons why optimus-manager refuses to do the switch. It may not necessary be a problem with bbswitch. But to troubleshoot further I would need some logs (at least the one from the display manager).

from optimus-manager.

It works for me too! Should I close this issue?

My final packages:

linux419-nvidia 1:415.25-3
mhwd-nvidia 1:415.25-1
mhwd-nvidia-340xx 340.107-1
mhwd-nvidia-390xx 390.87-1
nvidia-utils 1:415.25-1

And blacklist conf file like @Askannz said:
/usr/lib/modprobe.d/blacklist_bbswitch.conf
with blacklist bbswitch inside.

from optimus-manager.

@michaldybczak , the nouveau driver is already built into the kernel so you don't have to install anything else. Not sure what this package does.

Also, even though the symptoms of your problem are similar to Martin's, there can be a whole range of reasons why optimus-manager refuses to do the switch. It may not necessary be a problem with bbswitch. But to troubleshoot further I would need some logs (at least the one from the display manager).

He tried blacklisting bbswitch but it didn't help. Here are outputs I got from him. There are couple of differences in files here and there but I thought that you may notice something alarming or suspicious. Can you look? Most look OK but some things make me wonder...

For example, I have optimus-manager.conf with intel in intel mode. He doesn't have it. He has /etc/mhwd-x86_64.conf I don't (optimus-manager works for me). At this point I'm not sure where to look or what looks OK or not. He has some amd confs, which is confusing for me. How? I asked him and I'm waiting for replay. Any of these may or may not interfere with optimus-manager but I can only guess.

Here is the output:

[fla@15-pc ~]$ optimus-manager --print-mode
Current mode : intel
[fla@15-pc ~]$ journalctl -u optimus-manager.service
-- Logs begin at Sat 2019-01-19 14:14:01 +0330, end at Tue 2019-01-22 11:27:57 +0330. --
Jan 22 11:10:21 15-pc systemd[1]: Started Optimus Manager Commands Daemon.
Jan 22 11:10:23 15-pc python[1726]: Optimus Manager (Daemon) version 0.6
Jan 22 11:10:23 15-pc python[1726]: Awaiting commands
Jan 22 11:12:05 15-pc python[1726]: Process stop requested
Jan 22 11:12:05 15-pc python[1726]: Closing and removing the socket...
Jan 22 11:12:05 15-pc python[1726]: Goodbye !
Jan 22 11:12:05 15-pc systemd[1]: Stopping Optimus Manager Commands Daemon...
Jan 22 11:12:05 15-pc systemd[1]: Stopped Optimus Manager Commands Daemon.
-- Reboot --
Jan 22 11:12:43 15-pc systemd[1]: Started Optimus Manager Commands Daemon.
Jan 22 11:12:50 15-pc python[517]: Optimus Manager (Daemon) version 0.6
Jan 22 11:12:50 15-pc python[517]: Awaiting commands
Jan 22 11:25:14 15-pc python[517]: Received command : nvidia
Jan 22 11:25:14 15-pc python[517]: Writing requested mode
Jan 22 11:25:14 15-pc python[517]: Restarting login manager

[fla@15-pc ~]$ ls /usr/lib/modprobe.d/
blacklist_bbswitch.conf       bluetooth-usb.conf  systemd.conf
blacklist_bbswitch.conf.save  bumblebee.conf      uvesafb.conf
[fla@15-pc ~]$ cat /usr/lib/modprobe.d/blacklist_bbswitch.conf
blacklist bbswitch

[fla@15-pc ~]$ ls /etc/X11/
mhwd.d  xinit  xorg.conf.d
[fla@15-pc ~]$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf  90-mhwd.conf.bak
[fla@15-pc ~]$ ls /etc/X11/mhwd.d/
intel.conf.bak
[fla@15-pc ~]$ ls /usr/share/X11/
app-defaults  locale  twm  Xcms.txt  XErrorDB  xkb  xorg.conf.d
[fla@15-pc ~]$ ls /usr/share/X11/xorg.conf.d/
10-amdgpu.conf  10-evdev.conf  10-nvidia-drm-outputclass.conf  10-quirks.conf  10-radeon.conf  40-libinput.conf
[fla@15-pc ~]$ cat /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf
Section "OutputClass"
    Identifier "intel"
    MatchDriver "i915"
    Driver "modesetting"
EndSection

Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "PrimaryGPU" "yes"
    Option "AllowEmptyInitialConfiguration"
    ModulePath "/usr/lib/nvidia/xorg"
    ModulePath "/usr/lib/xorg/modules"
EndSection

/etc/mhwd-x86_64.conf (cat: MHWD64_IS_LIB32=“true”)

[fla@15-pc ~]$ ls /etc/modprobe.d/
mhwd-bbswitch.conf  mhwd-nvidia.conf  optimus-manager.conf
[fla@15-pc ~]$ ls /etc/modules-load.d/
modules.conf
[fla@15-pc ~]$ cat /etc/modprobe.d/mhwd-bbswitch.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##
 
 
options bbswitch load_state=0 unload_state=0

[fla@15-pc ~]$ cat /etc/modprobe.d/mhwd-nvidia.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##

blacklist nouveau
blacklist nvidia
blacklist nvidia-modeset
blacklist nvidia-uvm
blacklist ttm
blacklist drm_kms_helper
blacklist drm

[fla@15-pc ~]$ cat /etc/modprobe.d/optimus-manager.conf
blacklist nouveau
blacklist nvidia_drm
blacklist nvidia_uvm
blacklist nvidia_modeset
blacklist nvidia

from optimus-manager.

thank you @michaldybczak for helping me.
[fla@15-pc ~]$ inxi -Fxzc0

System:    Host: 15-pc Kernel: 4.19.14-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 
           Desktop: KDE Plasma 5.14.5 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Micro-Star product: CX61 2PC v: REV:1.0 serial: <filter> 
           Mobo: Micro-Star model: MS-16GD v: REV:1.0 serial: <filter> UEFI: American Megatrends 
           v: E16GDIMS.50N date: 03/25/2014 
CPU:       Topology: Dual Core model: Intel Core i5-4210M bits: 64 type: MT MCP arch: Haswell rev: 3 
           L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20761 
           Speed: 796 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 800 2: 798 3: 798 4: 799 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Micro-Star MSI driver: i915 
           v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] 
           vendor: Micro-Star MSI driver: nouveau v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.3 driver: modesetting resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.3.1 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-3: C-Media CM108 Audio Controller type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 2-6:6 
           Sound Server: ALSA v: k4.19.14-1-MANJARO 
Network:   Device-1: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel 
           port: d000 bus ID: 04:00.0 
           IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Realtek RTL8723AE PCIe Wireless Network Adapter vendor: AzureWave driver: rtl8723ae 
           v: kernel port: c000 bus ID: 05:00.0 
           IF: wlp5s0 state: down mac: <filter> 
Drives:    Local Storage: total: 698.64 GiB used: 38.37 GiB (5.5%) 
           ID-1: /dev/sda vendor: Western Digital model: WD7500BPVX-22JC3T0 size: 698.64 GiB 
Partition: ID-1: / size: 46.68 GiB used: 7.88 GiB (16.9%) fs: ext4 dev: /dev/sda6 
           ID-2: /home size: 240.78 GiB used: 30.46 GiB (12.6%) fs: ext4 dev: /dev/sda8 
           ID-3: swap-1 size: 6.68 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda7 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 179 Uptime: 37m Memory: 7.71 GiB used: 1.58 GiB (20.5%) Init: systemd Compilers: 
           gcc: 8.2.1 Shell: bash v: 4.4.23 inxi: 3.0.28 
[fla@15-pc ~]$ 

we using mhwd -a pci nonfree 0300
then #35
my Packages : Packages (9) egl-wayland-1.1.1-1 eglexternalplatform-1.0+3+g7c8f8e2-1 primus-20151110-8 bumblebee-3.2.1-22 lib32-nvidia-utils-1:415.25-1 lib32-primus-20151110-4 linux419-bbswitch-0.8-11 linux419-nvidia-1:415.25-3 nvidia-utils-1:415.25-1
before install driver: https://forum.manjaro.org/uploads/default/original/3X/6/6/66c66bae5271cbcdc61f9d6252f2d0f8c9a60640.png

from optimus-manager.

Reporting back again.

Updated to the latest stable release of Manjaro which updated the kernel and Nvidia drivers.

The update seems to have prevented switching from Intel to Nvidia again. To confirm, when on intel and trying to switch, the system simply goes back to the login screen after a few seconds. After logging in and checking the mode, Intel is shown.

See the log of SDDM when trying to switch to Nvidia:

https://pastebin.com/TDkwZrnR

from optimus-manager.

There was update a few days ago in Manjaro testing that complained about not being able to write into nvidia-xorg.conf and that surprised me, so I looked up and it RESTORED this conf so I had to disable it again. I rebooted and optimus-manager worked as always for me, so aside of that, I didn't notice any problems.

from optimus-manager.

Sorry for the loooong delay, I was on leave.

I think the root cause to all of those problems is MHWD (the hardware detection/driver installation tool of Manjaro).

MHWD should NOT be used with optimus-manager (I should have made that more clear in the README).

It's going to autogenerate files in /etc/X11/xorg.conf.d/(and possibly in /etc/modprobe.d/ and /etc/modules-load.d/) which conflict with optimus-manager.

If you have used it already, try wiping everything in /etc/X11/xorg.conf.d/.

from optimus-manager.

MHWD confs are disabled but MHWD itself is still on the system so I guess, updates may trigger refreshing of confs. I don't think that uninstalling MHWD is wise thou.
I did disable the generated conf as soon as I saw this message on update output, so all works fine for me but I can easily imagine a scenario that someone won't see that, reboots and then tries to use optimus-manager and fails not knowing what happened and then came to the conclusion that update broke optimus-manager.

from optimus-manager.

I have never seen mhwd regenerate files in /etc/X11/xorg.conf.d. The directory used to contain a symlink to the mhwd intel configuration found at /etc/X11/mhwd.d/intel.conf. I deleted it in order to use this program. It never got back. I think it only gets created when you run the mhwd tool and not during normal updates.

from optimus-manager.

I didn't touch mhwd and the info was definitely during the update, so something else must have triggered it. At this moment it's pointless to discuss it since I don't have the update output anymore.
I just wanted to warn that a recent update may have "broken" optimus-manager by regenerating this conf, so the easy solution was clear or for future reference when the same may happen.

from optimus-manager.

This issue occurs on ArchLinux too if you have the resume=/dev/yourdisk paramater set, doesn't matter if it is actually suspended or not.

from optimus-manager.

Further investigation leads to this:

# modprobe bbswitch
modprobe: ERROR: could not insert 'bbswitch': No such device

from optimus-manager.

Further findings lead me to this:

No matter if you use nouveau or bbswitch the PCI device (the GPU) will disappear after suspending. And is present until you completely shut off the machine (POWEROFF, reboot won't work)

from optimus-manager.

So it's an ACPI thing?

from optimus-manager.

Is there any issue remaining with the current Git version of optimus-manager ? It should have a better compatibility with Manjaro and MHWD.

from optimus-manager.

Finally I installed primus. I could never make optimus-manager work. I'll try it another time.

from optimus-manager.

I'm closing this issue since the original problem should be long gone by now. Feel free to open a new one if you are still having problems.

from optimus-manager.