Two mouse pointers on screen

alexandrevicenzi · January 29, 2015, 2:15am

Hi,

Somethimes I have two mouse cursor on screen. One doens’t work.

Basically this happes because I have 2 monitor and my notebook has dual graphics. Intel + NVidia.

I was looking at display manager and it shows 3 screen, but I have two. Just changed with Win + P a few times and it shows 2. After this there’s no second cursor.

How can I solve this at boot time, or related?

https://scontent-a-mia.xx.fbcdn.net/hphotos-xfp1/v/t1.0-9/10944714_936287816406180_5229178852850695483_n.jpg?oh=5196ece31198f253333845e2837798ac&oe=556AB52E

gogalthorp · January 29, 2015, 2:39am

You did not say what video drivers you have installed? Are you using Bumblebee to manage the hybrid GPU’s on your Optimus based machine?

alexandrevicenzi · January 29, 2015, 2:43am

How can I check this?

gogalthorp · January 29, 2015, 2:58am

Did you install it or not. I assume if you don’t know if you installed it you did not thus maybe you need to

Follow these instruction exactly

https://en.opensuse.org/SDB:NVIDIA_Bumblebee

alexandrevicenzi · January 29, 2015, 3:29am

I followed all steps but I get:

alexandre@suse:~> optirun --status
Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

alexandre@suse:~> optirun glxspheres
141.907657] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
141.907718] [ERROR]Aborting because fallback start is disabled.

Config file:

alexandre@suse:~> cat /etc/bumblebee/bumblebee.conf

Configuration file for Bumblebee. Values should not be put between quotes

Server options. Any change made in this section will need a server restart

to take effect.

[bumblebeed]

The secondary Xorg server DISPLAY number

VirtualDisplay=:8

Should the unused Xorg server be kept running? Set this to true if waiting

for X to be ready is too long and don’t need power management at all.

KeepUnusedXServer=false

The name of the Bumbleblee server group name (GID name)

ServerGroup=bumblebee

Card power state at exit. Set to false if the card shoud be ON when Bumblebee

server exits.

TurnCardOffAtExit=false

The default behavior of ‘-f’ option on optirun. If set to “true”, ‘-f’ will

be ignored.

NoEcoModeOverride=false

The Driver used by Bumblebee server. If this value is not set (or empty),

auto-detection is performed. The available drivers are nvidia and nouveau

(See also the driver-specific sections below)

Driver=

Directory with a dummy config file to pass as a -configdir to secondary X

XorgConfDir=/etc/bumblebee/xorg.conf.d

Client options. Will take effect on the next optirun executed.

[optirun]

Acceleration/ rendering bridge, possible values are auto, virtualgl and

primus.

Bridge=auto

The method used for VirtualGL to transport frames between X servers.

Possible values are proxy, jpeg, rgb, xv and yuv.

VGLTransport=proxy

List of paths which are searched for the primus libGL.so.1 when using

the primus bridge

PrimusLibraryPath=/usr/lib64/primus:/usr/lib/primus

Should the program run under optirun even if Bumblebee server or nvidia card

is not available?

AllowFallbackToIGC=false

Driver-specific settings are grouped under [driver-NAME]. The sections are

parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-

detection resolves to NAME).

PMMethod: method to use for saving power by disabling the nvidia card, valid

values are: auto - automatically detect which PM method to use

bbswitch - new in BB 3, recommended if available

switcheroo - vga_switcheroo method, use at your own risk

none - disable PM completely

https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

Section with nvidia driver specific options, only parsed if Driver=nvidia

[driver-nvidia]

Module name to load, defaults to Driver if empty or unset

KernelDriver=nvidia
PMMethod=auto

colon-separated path to the nvidia libraries

LibraryPath=/usr/lib64/nvidia:/usr/lib/nvidia

comma-separated path of the directory containing nvidia_drv.so and the

default Xorg modules path

XorgModulePath=/usr/lib64/nvidia/xorg/,/usr/lib64/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

Section with nouveau driver specific options, only parsed if Driver=nouveau

[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

alexandrevicenzi · January 29, 2015, 3:47am

Not sure if this help, but when I boot suse I get: [FAILED] Failed to start Load Kernel Modules.See “systemctl status systemd-modules-load.service” for details.

alexandre@suse:~> systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: active (exited) since Qui 2015-01-29 00:41:35 BRST; 4min 3s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 412 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Main PID: 412 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-modules-load.service

gogalthorp · January 29, 2015, 5:37am

Do you have one of the card turned off in the BIOS??

Some BIOS are reported to allow that other have no off switch it is hard to guess right.

You did a install the NVIDIA-bumblebee package right??

alexandrevicenzi · January 29, 2015, 9:35pm

There’s no option to disable on BIOS. It’s a Samsung laptop.

I followed all steps to install. If optirun --status shows Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off. it’s installed correctly I think. :\

wolfi323 · January 29, 2015, 10:10pm

Ok, but did you install the nvidia driver? (the package “nvidia-bumblebee”)
It might be a bug in nouveau.

OTOH, 899610 – [intel, snb] extra static mouse pointer would suggest it is rather a problem with the intel driver.
One workaround apparently would be to uninstall it (xf86-video-intel) and use the “modesetting” driver (package xf86-video-modesetting) instead.
You won’t have any hardware acceleration on the intel chip then though, in particular no hardware accelerated 3D for your desktop.

alexandrevicenzi · January 29, 2015, 10:36pm

I’ve installed nvidia-bumblebee. The mouse problem is solved, but I can’t run optirun.

I want to use nvidia graphic card to play some games.

wolfi323 · January 29, 2015, 10:55pm

Why? What happens when you run it?

alexandrevicenzi · January 29, 2015, 11:14pm

alexandre@suse:~> optirun --status
Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

alexandre@suse:~> optirun glxspheres
141.907657] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
141.907718] [ERROR]Aborting because fallback start is disabled.

wolfi323 · January 29, 2015, 11:29pm

Well, apparently the nvidia driver cannot be loaded.

What’s in /var/log/Xorg.8.log?

What nvidia card do you actually have?
nvidia-bumblebee installs the latest 346.35 driver, which only supports GTX 420 and higher.

alexandrevicenzi · January 29, 2015, 11:32pm

alexandre@suse:~> cat /var/log/Xorg.8.log
cat: /var/log/Xorg.8.log: No such file or directory

:sarcastic:

My graphic card is NVIDIA® GeForce® GT 630M Graphics (Optimus™ technology)

wolfi323 · January 29, 2015, 11:49pm

It might have a different number, I’m not sure.

ls -l /var/log/Xorg.*

Is nouveau blacklisted? (should be done automatically when you install nvidia-bumblebee)

grep nouveau /etc/modprobe.d/*

Try to run “sudo mkinitrd” manually to be sure the blacklist is in the initrd.

Have you ever tried to install the standard nvidia driver?

Did you get any error messages when installing nvidia-bumblebee?
Try to reinstall it and post the whole output:

sudo zypper in -f nvidia-bumblebee

Did optirun work before installing nvidia-bumblebee?

My graphic card is NVIDIA® GeForce® GT 630M Graphics (Optimus™ technology)

This should be supported, yes.

alexandrevicenzi · January 30, 2015, 12:00am

There’s no log file.

Is nouveau blacklisted? (should be done automatically when you install nvidia-bumblebee)

grep nouveau /etc/modprobe.d/*

Try to run “sudo mkinitrd” manually to be sure the blacklist is in the initrd.

Yes

Have you ever tried to install the standard nvidia driver?

No. It works with dual graphics? Intel + NVidia

Did you get any error messages when installing nvidia-bumblebee?
Try to reinstall it and post the whole output:

sudo zypper in -f nvidia-bumblebee

Did optirun work before installing nvidia-bumblebee?

Not tried.

See the whole output.


alexandre@suse:~> ls -l /var/log/
total 7124
-rw-r--r-- 1 root root              27030 Jan 28 22:33 alternatives.log
drwxr-xr-x 1 root root                  0 Out 23 15:20 apparmor
drwx------ 1 root root                 18 Jan 28 20:32 audit
-rw-r--r-- 1 root root              13078 Jan 29 18:26 boot.log
-rw------- 1 root root                384 Jan 28 20:49 btmp
drwxr-xr-x 1 lp   lp                   54 Jan 28 20:32 cups
-rw------- 1 root root              15968 Jan 28 22:42 faillog
drwx--x--x 1 root gdm                   0 Out 16 11:27 gdm
drwxrwxr-x 1 root lp                    6 Jan 28 20:26 hp
drwxr-sr-x 1 root systemd-journal      64 Nov 27 12:46 journal
drwx------ 1 root root                  0 Out  8 15:45 krb5
-rw-r--r-- 1 root root             292292 Jan 29 18:27 lastlog
-rw-r--r-- 1 root root                  0 Out 26 06:59 ntp
-rw------- 1 root root             368568 Jan 29 00:18 pbl.log
-rw-r----- 1 root root             687308 Jan 29 20:35 pk_backend_zypp
-rw-r--r-- 1 root root               1040 Nov 27 12:46 README
drwxr-x--- 1 root root                  0 Out 15 07:08 samba
-rw-r----- 1 root root             135673 Jan 29 20:53 snapper.log
drwx------ 1 root root                  0 Set 25 16:24 speech-dispatcher
drwxr-xr-x 1 root root                  0 Out  8 18:43 tuned
-rw-r--r-- 1 root root              14320 Jan 29 20:52 wpa_supplicant.log
-rw-rw-r-- 1 root utmp              38400 Jan 29 20:53 wtmp
drwx------ 1 root root                508 Jan 28 22:00 YaST2
drwxr-xr-x 1 root root                 14 Jan 21 15:27 zypp
-rw-r----- 1 root root            5181083 Jan 29 20:53 zypper.log
-rw-r----- 1 root root             622948 Jan 28 23:04 zypper.log-20150129.xz


alexandre@suse:~> grep nouveau /etc/modprobe.d/*
/etc/modprobe.d/50-blacklist.conf:blacklist nouveau
/etc/modprobe.d/51-blacklist-nouveau.conf:blacklist nouveau


alexandre@suse:~> sudo zypper in -f nvidia-bumblebee
root's password:
Loading repository data...
Reading installed packages...
Forcing installation of 'nvidia-bumblebee-346.35-3.1.x86_64' from repository 'Bumblebee'.
Resolving package dependencies...

The following package is going to be reinstalled:
  nvidia-bumblebee 

1 package to reinstall.
Overall download size: 13,5 KiB. Already cached: 0 B  No additional space will be used or freed after the operation.
Continue? [y/n/? shows all options] (y): y
Retrieving package nvidia-bumblebee-346.35-3.1.x86_64                                                             (1/1),  13,5 KiB (  885 B unpacked)
Retrieving: nvidia-bumblebee-346.35-3.1.x86_64.rpm ............................................................................................[done]
Checking for file conflicts: ..................................................................................................................[done]
(1/1) Installing: nvidia-bumblebee-346.35-3.1 .................................................................................................[done]
Additional rpm output:
check sums and md5 sums are ok


Output of nvidia-bumblebee-346.35-3.1.x86_64.rpm %posttrans script:
    ++ '' -x /usr/sbin/dkms ']'
    ++ /usr/sbin/dkms add -m nvidia -v 346.35 --rpm_safe_upgrade
    Error! DKMS tree already contains: nvidia-346.35
    You cannot add the same module/version combo more than once.
    ++ /usr/sbin/dkms build -m nvidia -v 346.35
    Module nvidia/346.35 already built for kernel 3.16.7-7-desktop/4
    ++ /usr/sbin/dkms install -m nvidia -v 346.35
    Module nvidia/346.35 already installed on kernel 3.16.7-7-desktop/x86_64
    ++ popd


alexandre@suse:~> sudo mkinitrd
Creating initrd: /boot/initrd-3.16.6-2-desktop
Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.6-2-desktop 3.16.6-2-desktop
dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
*** Including module: bash ***
*** Including module: warpclock ***
*** Including module: i18n ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: btrfs ***
*** Including module: kernel-modules ***
Omitting driver i2o_scsi
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
*** Including module: systemd ***
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: shutdown ***
*** Including module: suse ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image ***
*** Constructing GenuineIntel.bin ****
*** Store current command line parameters ***
Stored kernel commandline:
 resume=UUID=c48773f3-e3a6-4eea-92e4-1e0b20227331
root=UUID=002c5336-8d1e-492c-a35c-d41c1cf928ae rootflags=rw,relatime,space_cache rootfstype=btrfs
*** Creating image file ***
*** Creating image file done ***
Creating initrd: /boot/initrd-3.16.7-7-desktop
Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.7-7-desktop 3.16.7-7-desktop
dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
*** Including module: bash ***
*** Including module: warpclock ***
*** Including module: i18n ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: btrfs ***
*** Including module: kernel-modules ***
Omitting driver i2o_scsi
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
*** Including module: systemd ***
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: shutdown ***
*** Including module: suse ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image ***
*** Constructing GenuineIntel.bin ****
*** Store current command line parameters ***
Stored kernel commandline:
 resume=UUID=c48773f3-e3a6-4eea-92e4-1e0b20227331
root=UUID=002c5336-8d1e-492c-a35c-d41c1cf928ae rootflags=rw,relatime,space_cache rootfstype=btrfs
*** Creating image file ***
*** Creating image file

alexandrevicenzi · January 30, 2015, 12:13am

Not sure if it’s relevant.


alexandre@suse:~> cat /proc/acpi/bbswitch
0000:01:00.0 ON


alexandre@suse:~> systemctl status bumblebeed
bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
   Active: active (running) since Qui 2015-01-29 21:02:28 BRST; 6min ago
 Main PID: 1168 (bumblebeed)
   CGroup: /system.slice/bumblebeed.service
           └─1168 /usr/sbin/bumblebeed


alexandre@suse:~> optirun -vvv glxspheres 
  632.489659] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
  632.490367] [DEBUG]optirun version 3.2.1 starting...
  632.490384] [DEBUG]Active configuration:
  632.490389] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
  632.490394] [DEBUG] X display: :8
  632.490398] [DEBUG] LD_LIBRARY_PATH: /usr/lib64/nvidia:/usr/lib/nvidia
  632.490402] [DEBUG] Socket path: /var/run/bumblebee.socket
  632.490406] [DEBUG] Accel/display bridge: auto
  632.490411] [DEBUG] VGL Compression: proxy
  632.490415] [DEBUG] VGLrun extra options: 
  632.490419] [DEBUG] Primus LD Path: /usr/lib64/primus:/usr/lib/primus
  632.490459] [DEBUG]Using auto-detected bridge virtualgl
  632.535663] [INFO]Response: No - error: Could not load GPU driver

  632.535686] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

  632.535694] [DEBUG]Socket closed.
  632.535713] [ERROR]Aborting because fallback start is disabled.
  632.535721] [DEBUG]Killing all remaining processes.
alexandre@suse:~>

gogalthorp · January 30, 2015, 12:41am

No the normal NVIDIA does not work on Optimus systems. DO NOT try it. The problem has been seen here that some people just install the regular NVIDIA driver which does not work and breaks things then try bumblebee without first removing the regular drive which leave bad stuff laying around (at least for Optimus systems).

wolfi323 · January 30, 2015, 12:47am

None at all?
Then you’re probably using gdm, which redirects all Xorg logs to systemd’s journal.
I should have noticed from your screenshot that you are using GNOME…

Great, I have no idea how to extract the Xorg log (and Xorg.8.log in particular) from the journal, and I cannot try either as I use kdm here.
According to Who-T: Viewing the Xorg.log with journalctl, this should work:

journalctl -e _COMM=Xorg

This will of course extract all Xorg logs ever written (the last 1000 lines).

So better do that directly after running optirun again, and post the last lines.

No. It works with dual graphics? Intel + NVidia

No it doesn’t. (at least not out of the box, there is a way to make the rpm packages from the nvidia repo work with Bumblebee by creating some symlinks)

That’s why I’m asking.
And also if you installed it and didn’t completely remove it, the remnants could cause problems.

Not tried.

Well, you already posted the same error message before I joined in here and wrote you should install nvidia-bumblebee.

See the whole output.


...
Output of nvidia-bumblebee-346.35-3.1.x86_64.rpm %posttrans script:
    ++ '' -x /usr/sbin/dkms ']'
    ++ /usr/sbin/dkms add -m nvidia -v 346.35 --rpm_safe_upgrade
    Error! DKMS tree already contains: nvidia-346.35
    You cannot add the same module/version combo more than once.
    ++ /usr/sbin/dkms build -m nvidia -v 346.35
    Module nvidia/346.35 already built for kernel 3.16.7-7-desktop/4
    ++ /usr/sbin/dkms install -m nvidia -v 346.35
    Module nvidia/346.35 already installed on kernel 3.16.7-7-desktop/x86_64
    ++ popd

Ok, that doesn’t really show whether the kernel module was actually compiled correctly.

Can you please remove nvidia-bumblebee completely, install it again and post the output?

sudo zypper rm nvidia-bumblebee
sudo zypper in nvidia-bumblebee

alexandrevicenzi:

Not sure if it’s relevant.


...
alexandre@suse:~> optirun -vvv glxspheres 
  632.489659] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
  632.490367] [DEBUG]optirun version 3.2.1 starting...
  632.490384] [DEBUG]Active configuration:
  632.490389] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
  632.490394] [DEBUG] X display: :8
  632.490398] [DEBUG] LD_LIBRARY_PATH: /usr/lib64/nvidia:/usr/lib/nvidia
  632.490402] [DEBUG] Socket path: /var/run/bumblebee.socket
  632.490406] [DEBUG] Accel/display bridge: auto
  632.490411] [DEBUG] VGL Compression: proxy
  632.490415] [DEBUG] VGLrun extra options: 
  632.490419] [DEBUG] Primus LD Path: /usr/lib64/primus:/usr/lib/primus
  632.490459] [DEBUG]Using auto-detected bridge virtualgl
  632.535663] [INFO]Response: No - error: Could not load GPU driver

  632.535686] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

  632.535694] [DEBUG]Socket closed.
  632.535713] [ERROR]Aborting because fallback start is disabled.
  632.535721] [DEBUG]Killing all remaining processes.
alexandre@suse:~>

Well, this looks rather normal to me, except for that error message of course which you already posted before.

Another idea, inspired by 13.10 - No - error: Could not load GPU driver; Cannot access secondary GPU - error: Could not load GPU driver - Ask Ubuntu
Try changing “Driver=” to "Driver=nvidia"and “KernelDriver=nvidia” to “KernelDriver=nvidia-current” in /etc/bumblebee/bumblebee.conf .

alexandrevicenzi · January 30, 2015, 1:46am

None at all?

Yes.

Then you’re probably using gdm, which redirects all Xorg logs to systemd’s journal.
I should have noticed from your screenshot that you are using GNOME…

Yes, I’m using gnome.

Great, I have no idea how to extract the Xorg log (and Xorg.8.log in particular) from the journal, and I cannot try either as I use kdm here.
According to http://who-t.blogspot.co.at/2014/03/...ournalctl.html, this should work:

There’s no log too.

Can you please remove nvidia-bumblebee completely, install it again and post the output?

http://hastebin.com/xifiqozali.pl

Another idea, inspired by http://askubuntu.com/questions/42459...pu-error-coul:
Try changing “Driver=” to "Driver=nvidia"and “KernelDriver=nvidia” to “KernelDriver=nvidia-current” in /etc/bumblebee/bumblebee.conf .

If I change to KernelDriver=nvidia-current bumblebee fail to start. I think this is a package only for Ubuntu.