Some problems with optimus-manager and switching

Hello all.

After messing around on Manjaro KDE for a while, I went back to GNOME yesterday (did a clean install). I had the installer set up nvidia-455xx-prime.

After first reboot, I set up optimus-manager, and used the Manjaro wiki and the Github instructions, I did uncomment the WaylandEnable=false. I have also installed gdm-prime.

I installed optimus-manager-qt and rebooted after installing and enabling optimus-manager.

Now, switching to to Nvidia resulted (note past tense, but might be current as well) the computer to come to a halt on my HP logo. I was able to use TTY2 to log in and startx. Upon logging in, I needed to insert keyring key. Going back to TTY1 seems to have weird effect to it, the optimus-manager was missing from the top panel, and it just felt weird…

Anyway, TTY2 worked fine.

Today, I tried to switch again, resulting in same process, so I did some digging and found this. I tried changing the settings in optimus-manager as suggested, but every change I tried resulted in the inability to switch to Nvidia (I tried more than 2 times on each setting). I finally reverted to default settings (and rebooted)… which now can’t switch to Nvidia.

I am currently at a loss working around this and I do not have enough knowledge to work through the log it self.

inxi -Fazy
~ >>> inxi -Fazy                                                                                 
System:
  Kernel: 5.9.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.9-x86_64 
  root=UUID=4aeb67d6-2818-4be4-b376-d5e17ef83701 rw quiet udev.log_priority=3 
  Desktop: GNOME 3.38.1 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.38.2 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: HP product: HP Pavilion Gaming Laptop 15-cx0xxx 
  v: Type1ProductConfigId serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: HP model: 8478 v: 70.57 serial: <filter> UEFI: Insyde v: F.22 
  date: 04/21/2020 
Battery:
  ID-1: BAT1 charge: 26.9 Wh condition: 26.9/52.8 Wh (51%) volts: 12.8/11.6 
  model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter> 
  status: Full 
CPU:
  Info: Quad Core model: Intel Core i5-8300H bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 9E (158) stepping: A (10) microcode: DE 
  L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 36812 
  Speed: 857 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 878 2: 844 3: 846 
  4: 840 5: 844 6: 842 7: 830 8: 848 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: Hewlett-Packard driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b 
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Hewlett-Packard 
  driver: N/A alternate: nouveau, nvidia_drm, nvidia bus ID: 01:00.0 
  chip ID: 10de:1c8d 
  Device-3: Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD 
  Integrated Webcam 
  type: USB driver: uvcvideo bus ID: 1-5:5 chip ID: 05c8:03bc 
  Display: x11 server: X.org 1.20.9 compositor: gnome-shell 
  driver: modesetting resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.2.2 
  direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard 
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci 
  bus ID: 00:1f.3 chip ID: 8086:a348 
  Sound Server: ALSA v: k5.9.10-1-MANJARO 
Network:
  Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter 
  vendor: Hewlett-Packard driver: rtw_8822be v: N/A modules: rtw88_8822be 
  port: 4000 bus ID: 02:00.0 chip ID: 10ec:b822 
  IF: wlo1 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 05:00.0 
  chip ID: 10ec:8168 
  IF: eno1 state: down mac: <filter> 
Drives:
  Local Storage: total: 1.60 TiB used: 466.23 GiB (28.5%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000H1 
  size: 238.47 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: CXB73H1Q scheme: GPT 
  ID-2: /dev/sda type: USB vendor: Toshiba model: External USB 3.0 
  size: 931.51 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 5438 scheme: MBR 
  ID-3: /dev/sdb type: USB vendor: Western Digital model: WD My Passport 0740 
  size: 465.73 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 1007 scheme: GPT 
Partition:
  ID-1: / raw size: 237.97 GiB size: 233.24 GiB (98.01%) 
  used: 51.55 GiB (22.1%) fs: ext4 dev: /dev/nvme0n1p2 
Swap:
  Alert: No Swap data was found. 
Sensors:
  System Temperatures: cpu: 57.0 C mobo: 29.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 270 Uptime: 15m Memory: 15.53 GiB used: 1.45 GiB (9.3%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 11.0.0 Packages: 
  pacman: 1387 lib: 432 flatpak: 0 Shell: Zsh v: 5.8 
  running in: gnome-terminal inxi: 3.1.08 
optimus-manager log
[35] INFO: # Xorg pre-start hook
[35] INFO: Previous state was: {'type': 'pending_pre_xorg_start', 'requested_mode': 'intel', 'current_mode': None}
[35] INFO: Requested mode is: intel
[35] INFO: Checking for GDM display servers
[64] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[64] INFO: Falling back to default value "3"
[374] INFO: Available modules: ['nouveau', 'nvidia', 'nvidia_drm', 'nvidia_modeset', 'nvidia_uvm']
[375] INFO: Unloading modules ['nvidia_drm', 'nvidia_modeset', 'nvidia_uvm', 'nvidia'] (if loaded)
[392] INFO: Loaded extra Intel Xorg options (0 lines)
[392] INFO: Loaded extra Intel Xorg options (0 lines)
[392] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
[392] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20201126T100455', 'requested_mode': 'intel'}
[393] INFO: Xorg pre-start hook completed successfully.
[4] INFO: # Xorg post-start hook
[4] INFO: Running /etc/optimus-manager/xsetup-intel.sh
[7] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[7] INFO: Falling back to default value "3"
[158] INFO: Writing state {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[159] INFO: Xorg post-start hook completed successfully.
[8] INFO: # Xorg pre-start hook
[8] INFO: Previous state was: {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[8] INFO: Requested mode is: intel
[8] INFO: Checking for GDM display servers
[30] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[30] INFO: Falling back to default value "3"
[38] INFO: Loaded extra Intel Xorg options (0 lines)
[38] INFO: Loaded extra Intel Xorg options (0 lines)
[38] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
[38] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20201126T100455', 'requested_mode': 'intel'}
[39] INFO: Xorg pre-start hook completed successfully.
[4] INFO: # Xorg post-start hook
[4] INFO: Running /etc/optimus-manager/xsetup-intel.sh
[7] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[7] INFO: Falling back to default value "3"
[10] INFO: Writing state {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[11] INFO: Xorg post-start hook completed successfully.
[13] INFO: # Xorg pre-start hook
[13] INFO: Previous state was: {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[13] INFO: Requested mode is: intel
[13] INFO: Checking for GDM display servers
[45] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[45] INFO: Falling back to default value "3"
[54] INFO: Loaded extra Intel Xorg options (0 lines)
[54] INFO: Loaded extra Intel Xorg options (0 lines)
[54] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
[54] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20201126T100455', 'requested_mode': 'intel'}
[54] INFO: Xorg pre-start hook completed successfully.
[4] INFO: # Xorg post-start hook
[4] INFO: Running /etc/optimus-manager/xsetup-intel.sh
[7] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[7] INFO: Falling back to default value "3"
[10] INFO: Writing state {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[11] INFO: Xorg post-start hook completed successfully.
[9] INFO: # Xorg pre-start hook
[9] INFO: Previous state was: {'type': 'done', 'switch_id': '20201126T100455', 'current_mode': 'intel'}
[9] INFO: Requested mode is: intel
[9] INFO: Checking for GDM display servers
[30] ERROR: Config parsing : error in option "dri" in section [intel] : invalid value "0"
[30] INFO: Falling back to default value "3"
[38] INFO: Loaded extra Intel Xorg options (0 lines)
[38] INFO: Loaded extra Intel Xorg options (0 lines)
[38] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
[39] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20201126T100455', 'requested_mode': 'intel'}
[39] INFO: Xorg pre-start hook completed successfully.

I know GDM doesn’t play well with optimus-manager, but I really don’t want to reinstall again, and I have actually come acustom to usinng GNOME :confounded:

Starting to think this install is somehow broken, theming is all over the place and looks weird for some applications, so I think my best bet is to reinstall.

So I installed GNOME again, still had strange theming problem, and optimus-manager just wouldn’t work properly for me. So after some trial and error I ended up again on KDE which seems to work much better with my hardware.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.