Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Bubmlebee nvidia driver problem

Need help with peripherals or devices?
Post Reply
Message
Author
Bloris
Posts: 24
Joined: 2018-12-09 15:53

Bubmlebee nvidia driver problem

#1 Post by Bloris »

Hiii!

I'm tyring to use bumblebee in my laptop, but i have a strange problem i'm not able to fix.

First of all if i run primusrun glxgears -info it work perfectly. The problem shows up when i try to run a 32bit game with wine (League of Legends):

Code: Select all

0079:fixme:wininet:InternetSetOptionW Option 77 STUB
0079:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 15000
0077:fixme:win:RegisterDeviceNotificationA (hwnd=0x10082, filter=0xd7ffe90,flags=0x00000000) returns a fake device notification handle!
0071:fixme:win:RegisterDeviceNotificationA (hwnd=0x10076, filter=0xd19fe90,flags=0x00000000) returns a fake device notification handle!
0073:fixme:win:RegisterDeviceNotificationA (hwnd=0x1007c, filter=0xd3bfe50,flags=0x00000004) returns a fake device notification handle!
0079:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
007b:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
007b:fixme:wbemprox:enum_class_object_Next timeout not supported
primus: fatal: failed to load any of the libraries: /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1:/usr/lib/i386-linux-gnu/nvidia/libGL.so.1:/usr/lib/nvidia/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: classe ELF errata: ELFCLASS64
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1: impossibile aprire il file oggetto condiviso: File o directory non esistente
/usr/lib/nvidia/libGL.so.1: impossibile aprire il file oggetto condiviso: File o directory non esistente
0079:err:ntdll:RtlpWaitForCriticalSection section 0x7bd25260 "loader.c: loader_section" wait timed out in thread 0079, blocked by 007c, retrying (60 sec)
007b:err:ntdll:RtlpWaitForCriticalSection section 0x7bd25260 "loader.c: loader_section" wait timed out in thread 007b, blocked by 007c, retrying (60 sec)
006d:err:ntdll:RtlpWaitForCriticalSection section 0x7bd25260 "loader.c: loader_section" wait timed out in thread 006d, blocked by 007c, retrying (60 sec)
007d:err:ntdll:RtlpWaitForCriticalSection section 0x7bd25260 "loader.c: loader_section" wait timed out in thread 007d, blocked by 007c, retrying (60 sec)
Probalby it's only a symlink problem? I've tried to edit bumblebeed.conf with some paths, but it didn't work.

Anyone can help me to fix this?

Sorry for my bad english.

Thank you,
Loris

journalctl

Code: Select all

dic 09 17:44:47 msi kernel: vgaarb: this pci device is not a vga device
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:44:47 msi kernel: vgaarb: this pci device is not a vga device
dic 09 17:44:48 msi bumblebeed[5681]: [  857.616897] [WARN][XORG] (WW) NVIDIA(0): Unable to get display device for DPI computation.
dic 09 17:44:48 msi bumblebeed[5681]: [  857.616913] [WARN][XORG] (WW) NVIDIA(0): Option "NoLogo" is not used
dic 09 17:44:48 msi bumblebeed[5681]: [  857.616925] [ERROR][XORG] (EE) PreInit returned 2 for "<default keyboard>"
dic 09 17:45:01 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:45:33 msi systemd[1]: Starting Cleanup of Temporary Directories...
dic 09 17:45:33 msi systemd[1]: Started Cleanup of Temporary Directories.
dic 09 17:46:15 msi kernel: vgaarb: this pci device is not a vga device
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
dic 09 17:46:15 msi kernel: vgaarb: this pci device is not a vga device
dic 09 17:46:16 msi bumblebeed[5681]: [  945.667257] [WARN][XORG] (WW) NVIDIA(0): Unable to get display device for DPI computation.
dic 09 17:46:16 msi bumblebeed[5681]: [  945.667282] [WARN][XORG] (WW) NVIDIA(0): Option "NoLogo" is not used
dic 09 17:46:16 msi bumblebeed[5681]: [  945.667302] [ERROR][XORG] (EE) PreInit returned 2 for "<default keyboard>"
dic 09 17:46:36 msi kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
bumblebee.conf

Code: Select all

# 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=nvidia
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
# Xorg binary to run
XorgBinary=/usr/lib/xorg/Xorg

## 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/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/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=bbswitch #auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia
#LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia:/usr/lib/nvidia:/usr/lib32/nvidia:/usr/lib:/usr/lib32
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia/nvidia,/usr/lib/xorg/modules
#XorgModulePath=/usr/lib/nvidia/nvidia,/usr/lib/nvidia/xorg,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=bbswitch
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
xorg.conf.nvidia

Code: Select all

Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"
EndSection

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
   BusID "PCI:01:00:0"

#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
EndSection

Section "Screen"
	Identifier "Default Screen"
	Device "DiscreteNvidia"
EndSection
dpkg -l | grep nvidia

Code: Select all

dpkg -l | grep nvidia
ii  bumblebee-nvidia                              3.2.1-14                                   amd64        NVIDIA Optimus support using the proprietary NVIDIA driver
ii  glx-alternative-nvidia                        0.8.3~deb9u1                               amd64        allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64                          384.130-1                                  amd64        NVIDIA binary EGL library
ii  libegl1-glvnd-nvidia:amd64                    384.130-1                                  amd64        Vendor neutral GL dispatch library -- libEGL
ii  libgl1-glvnd-nvidia-glx:amd64                 384.130-1                                  amd64        Vendor neutral GL dispatch library -- libGL
ii  libgl1-nvidia-glvnd-glx:amd64                 384.130-1                                  amd64        NVIDIA binary OpenGL/GLX library (GLVND variant)
ii  libgles-nvidia1:amd64                         384.130-1                                  amd64        NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64                         384.130-1                                  amd64        NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64                          384.130-1                                  amd64        NVIDIA binary GLX library
ii  libglx0-glvnd-nvidia:amd64                    384.130-1                                  amd64        Vendor neutral GL dispatch library -- libGLX
ii  libnvidia-cfg1:amd64                          384.130-1                                  amd64        NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-egl-wayland1:amd64                  384.130-1                                  amd64        NVIDIA binary Wayland EGL external platform library
ii  libnvidia-eglcore:amd64                       384.130-1                                  amd64        NVIDIA binary EGL core libraries
ii  libnvidia-glcore:amd64                        384.130-1                                  amd64        NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-ml1:amd64                           384.130-1                                  amd64        NVIDIA Management Library (NVML) runtime library
ii  nvidia-alternative                            384.130-1                                  amd64        allows the selection of NVIDIA as GLX provider
ii  nvidia-driver                                 384.130-1                                  amd64        NVIDIA metapackage
ii  nvidia-driver-bin                             384.130-1                                  amd64        NVIDIA driver support binaries
ii  nvidia-driver-libs:amd64                      384.130-1                                  amd64        NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-egl-common                             384.130-1                                  amd64        NVIDIA binary EGL driver - common files
ii  nvidia-egl-icd:amd64                          384.130-1                                  amd64        NVIDIA EGL installable client driver (ICD)
ii  nvidia-egl-wayland-common                     384.130-1                                  amd64        NVIDIA binary Wayland EGL external platform - common files
ii  nvidia-egl-wayland-icd:amd64                  384.130-1                                  amd64        NVIDIA Wayland EGL external platform library (ICD)
ii  nvidia-installer-cleanup                      20151021+4                                 amd64        cleanup after driver installation with the nvidia-installer
ii  nvidia-kernel-common                          20151021+4                                 amd64        NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms                            384.130-1                                  amd64        NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support                         384.130-1                                  amd64        NVIDIA binary kernel module support files
ii  nvidia-legacy-check                           384.130-1                                  amd64        check for NVIDIA GPUs requiring a legacy driver
ii  nvidia-modprobe                               384.111-2~deb9u1                           amd64        utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-persistenced                           384.111-1~deb9u1                           amd64        daemon to maintain persistent software state in the NVIDIA driver
ii  nvidia-settings                               384.111-1~deb9u1                           amd64        tool for configuring the NVIDIA graphics driver
ii  nvidia-support                                20151021+4                                 amd64        NVIDIA binary graphics driver support files
ii  nvidia-vdpau-driver:amd64                     384.130-1                                  amd64        Video Decode and Presentation API for Unix - NVIDIA driver
ii  nvidia-vulkan-common                          384.130-1                                  amd64        NVIDIA Vulkan driver - common files
ii  nvidia-vulkan-icd:amd64                       384.130-1                                  amd64        NVIDIA Vulkan installable client driver (ICD)
ii  nvidia-xconfig                                384.111-1~deb9u1                           amd64        deprecated X configuration tool for non-free NVIDIA drivers
ii  xserver-xorg-video-nvidia                     384.130-1                                  amd64        NVIDIA binary Xorg driver
dpkg -l |grep bumblebee & primus

Code: Select all

ii  bumblebee                                     3.2.1-14                                   amd64        NVIDIA Optimus support for Linux
ii  bumblebee-nvidia                              3.2.1-14                                   amd64        NVIDIA Optimus support using the proprietary NVIDIA driver
ii  primus                                        0~20150328-4                               amd64        client-side GPU offloading for NVIDIA Optimus
ii  primus-libs:amd64                             0~20150328-4                               amd64        Shared libraries for primus
ii  primus-libs:i386                              0~20150328-4                               i386         Shared libraries for primus
ii  primus-libs-ia32:i386                         0~20150328-4                               i386         Shared libraries for primus (32-bit)
dpkg -l | grep wine

Code: Select all

ii  wine-staging                                  4.0~rc1~stretch                            amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-staging-amd64                            4.0~rc1~stretch                            amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-staging-i386:i386                        4.0~rc1~stretch                            i386         WINE Is Not An Emulator - runs MS Windows programs
ii  winehq-staging                                4.0~rc1~stretch                            amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  winetricks                                    0.0+20170101-1                             all          package manager for Wine to install software easily

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#2 Post by stevepusser »

You need to install i386 packages for the Nvidia driver as well.

Code: Select all

apt install libgl1-nvidia-glx:i386
Some games might also need a texture compression library

Code: Select all

apt install libtxc-dxtn-s2tc libtxc-dxtn-s2tc:i386
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#3 Post by Bloris »

I think i've already installed 32bit packages

Code: Select all

apt install libgl1-nvidia-glx:i386
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
Alcuni pacchetti non possono essere installati. Questo può voler dire
che è stata richiesta una situazione impossibile oppure, se si sta
usando una distribuzione in sviluppo, che alcuni pacchetti richiesti
non sono ancora stati creati o sono stati rimossi da Incoming.
Le seguenti informazioni possono aiutare a risolvere la situazione:

I seguenti pacchetti hanno dipendenze non soddisfatte:
 libgl1 : Dipende: libglx0 (= 1.1.0-1~bpo9+1) ma non sta per essere installato
 libglx-nvidia0 : Dipende: libglx0 ma non sta per essere installato oppure
                           libglx0-glvnd-nvidia ma non sta per essere installato
 libqtwebkit4 : Dipende: libqt4-opengl (>= 4:4.8.6+git64-g5dc8b2b+dfsg-2~) ma non sta per essere installato
E: Errore, pkgProblemResolver::Resolve ha generato delle interruzioni. Questo potrebbe essere causato da pacchetti bloccati.

Code: Select all

apt install libtxc-dxtn-s2tc libtxc-dxtn-s2tc:i386
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
libtxc-dxtn-s2tc is already the newest version (1.0+git20151227-2).
È stato impostato libtxc-dxtn-s2tc per l'installazione manuale.
libtxc-dxtn-s2tc:i386 is already the newest version (1.0+git20151227-2).
È stato impostato libtxc-dxtn-s2tc:i386 per l'installazione manuale.
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#4 Post by stevepusser »

It doesn't appear that libgl1-nvidia-glx:i386 is installed.

In your case, since you seem to have installed the Nvidia driver from backports, you must also install the i386 versions from backports to make sure the versions match.

What do you get for

Code: Select all

apt policy libgl1-nvidia-glx:i386
?
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#5 Post by Bloris »

But i can't install it cause of dependency problems....

Code: Select all

apt policy libgl1-nvidia-glx:i386
libgl1-nvidia-glx:i386:
  Installato: (nessuno)
  Candidato:  384.130-1
  Tabella versione:
     390.87-2~bpo9+1 100
        100 http://ftp.it.debian.org/debian stretch-backports/non-free i386 Packages
     384.130-1 500
        500 http://ftp.it.debian.org/debian stretch/non-free i386 Packages

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#6 Post by stevepusser »

I was wrong: it appears that your Nvidia 64-bit packages are actually the stock Stretch 384.130 packages, so I'd disable the backports repo instead, update apt, and then see if the i386 versions become installable.
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#7 Post by Bloris »

You were so damn right! The problem was backport packages, i didn't think about it :lol:

Anyway, performance with NVIDIA graphics are the same of Intel....I think there is a problem.
Before to use bumblebee, i was able to play with 80/120 fps with this NVIDIA and Wine, now i've 30/40 fps with it. Do you think it's a configuration problem?

User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: Bubmlebee nvidia driver problem

#8 Post by llivv »

Bloris wrote:Anyway, performance with NVIDIA graphics are the same of Intel....I think there is a problem.
Before to use bumblebee, i was able to play with 80/120 fps with this NVIDIA and Wine, now i've 30/40 fps with it. Do you think it's a configuration problem?
do you look at the log?
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#9 Post by Bloris »

This is the log of primusrun with debian game supertuxkart
primusrun supertuxkart

Code: Select all

verbose  ] main: Error messages and other text output will be logged to /home/loris/.config/supertuxkart/0.8.2/stdout.log.
[info   ] [FileManager]: Data files will be fetched from: '/usr/share/games/supertuxkart/data/'
[info   ] [FileManager]: User directory is '/home/loris/.config/supertuxkart/0.8.2/'.
[info   ] [FileManager]: Addons files will be stored in '/home/loris/.local/share/supertuxkart/addons/'.
[info   ] [FileManager]: Screenshots will be stored in '/home/loris/.cache/supertuxkart/screenshots/'.
[info   ] [FileManager]: User-defined grand prix will be stored in '/home/loris/.local/share/supertuxkart/grandprix/'.
[info   ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/supertuxkart/data/challenges/'.
[info   ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/supertuxkart/data/gfx/'.
[info   ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/supertuxkart/data/grandprix/'.
[info   ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/supertuxkart/data/gui/'.
[info   ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/supertuxkart/data/library/'.
[info   ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/supertuxkart/data/models/'.
[info   ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/supertuxkart/data/music/'.
[info   ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/supertuxkart/data/replay/'.
[info   ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/supertuxkart/data/tracks/'.
[info   ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/supertuxkart/data/sfx/'.
[info   ] [FileManager]: Asset 10 will be loaded from '/usr/share/games/supertuxkart/data/shaders/'.
[info   ] [FileManager]: Asset 11 will be loaded from '/usr/share/games/supertuxkart/data/skins/'.
[info   ] [FileManager]: Asset 12 will be loaded from '/usr/share/games/supertuxkart/data/textures/'.
[info   ] [FileManager]: Asset 13 will be loaded from '/usr/share/games/supertuxkart/data/ttf/'.
[info   ] [FileManager]: Asset 14 will be loaded from '/usr/share/games/supertuxkart/data/po/'.
Irrlicht Engine version 1.8.0
Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
[info   ] IrrDriver: OpenGL version: 4.3
[info   ] IrrDriver: OpenGL vendor: NVIDIA Corporation
[info   ] IrrDriver: OpenGL renderer: GeForce GTX 950M/PCIe/SSE2
[info   ] IrrDriver: OpenGL version string: 4.3.0 NVIDIA 384.130
[info   ] GLDriver: ARB Buffer Storage Present
[info   ] GLDriver: ARB Base Instance Present
[info   ] GLDriver: ARB Draw Indirect Present
[info   ] GLDriver: ARB Compute Shader Present
[info   ] GLDriver: ARB Arrays of Arrays Present
[info   ] GLDriver: ARB Texture Storage Present
[info   ] GLDriver: ARB Texture View Present
[info   ] GLDriver: ARB Bindless Texture Present
[info   ] GLDriver: ARB Image Load Store Present
[info   ] GLDriver: ARB Shader Atomic Counters Present
[info   ] GLDriver: ARB Shader Storage Buffer Object Present
[info   ] GLDriver: ARB Multi Draw Indirect Present                                                                                  
[info   ] GLDriver: EXT Texture Compression S3TC Present                                                                             
[info   ] GLDriver: ARB Uniform Buffer Object Present                                                                                
[info   ] GLDriver: ARB Explicit Attrib Location Present
[info   ] GLDriver: Geometry Shaders Present
[info   ] irr_driver: GLSL supported.
[info   ] Freetype Environment: Loading fonts...
[info   ] Freetype Environment: DPI for Normal Font is 31.
[info   ] Freetype Environment: DPI for Title Font is 78.
[info   ] Freetype Environment: DPI for Digit Font is 46.
[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[warn   ] [IrrDriver Temp Logger]: Level 2: PNG warning: iCCP: known incorrect sRGB profile

[info   ] ScalableFont::loadTTF: Created 15 glyphs supporting 16 characters for high-res digits font Sigmar using 1 glyph page(s).
[info   ] ScalableFont::loadTTF: Created 61 glyphs supporting 88 characters for bold title font Cantarell using 1 glyph page(s).
[info   ] ScalableFont::loadTTF: Created 98 glyphs supporting 101 characters for normal font Cantarell using 1 glyph page(s).
[info   ] shader: Compiling shader : texturedquad.vert
[info   ] shader: Compiling shader : texturedquad.frag
[info   ] shader: Compiling shader : texturedquad.vert
[info   ] shader: Compiling shader : uniformcolortexturedquad.frag
[info   ] shader: Compiling shader : colortexturedquad.vert
[info   ] shader: Compiling shader : colortexturedquad.frag
[info   ] HTTPRequest: Downloading http://addons.supertuxkart.net/dl/xml/news.xml
Cannot connect to server socket err = File o directory non esistente
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
[info   ] GrandPrixManager: Loading Grand Prix files from /usr/share/games/supertuxkart/data/grandprix/
[info   ] GrandPrixManager: Loading Grand Prix files from /home/loris/.local/share/supertuxkart/grandprix/
[info   ] addons: Using cached addons.xml.
[info   ] HTTPRequest: Downloading http://addons.supertuxkart.net/dl/images/249644655931060f5fb4c.png
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[info   ] HTTPRequest: Downloading http://addons.supertuxkart.net/dl/images/32999604857af930517f49.png
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] Irrlicht: PNG warning: iCCP: profile 'ICC profile': 1000000h: invalid rendering intent
[warn   ] EventHandler: Error while loading kart 'Adiumy':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Amanda':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Emule':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG
[warn   ] EventHandler: Error while loading kart 'Gavroche':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Hexley':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: profile 'Photoshop ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG
[warn   ] EventHandler: Error while loading kart 'Konqi':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[warn   ] EventHandler: Error while loading kart 'Tux':
[warn   ] Irrlicht: PNG warning: iCCP: known incorrect sRGB profile
[info   ] shader: Compiling shader : coloredquad.vert
[info   ] shader: Compiling shader : coloredquad.frag
This is journalctl

Code: Select all

...skipping...
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:16 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 19:27:17 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
I don't see something important here...

that's the command console with wine+lol
vblank_mode=0 optirun -b primus wine start 'C:\Riot Games\League of Legends\LeagueClient.exe'

Code: Select all

021c:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #216:
021c:fixme:d3d_shader:print_glsl_info_log     Vertex info
021c:fixme:d3d_shader:print_glsl_info_log     -----------
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[0].zw" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[1]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[2]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[3]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[4]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[5]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[6]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[7]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[9]" might be used before being initialized
021c:fixme:d3d_shader:print_glsl_info_log     0(22) : warning C7050: "vs_out[11]" might be used before being initialized
01f5:fixme:ntdll:NtQuerySystemInformation returning fake driver list
01f5:fixme:ntdll:NtQuerySystemInformation returning fake driver list
it's full of these messages, don't know if it means something

...and this is journalctl

Code: Select all

dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:22 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:23 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
dic 10 20:18:24 msi kernel: pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#10 Post by stevepusser »

Hmmm...what about if you install the MX 17 version debs of the 64-bit virtualgl and virtualgl-libs packages from here:

http://mxrepo.com/mx/repo/pool/main/v/virtualgl/

and then compare the benchmark

Code: Select all

glxspheres64
versus

Code: Select all

optirun glxspheres64
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#11 Post by Bloris »

As you can see NVIDIA graphics works perfectly with this benchmark

Code: Select all

glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0xc5
Context is Direct
OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
61.407793 frames/sec - 68.531096 Mpixels/sec
59.973426 frames/sec - 66.930343 Mpixels/sec
59.992505 frames/sec - 66.951636 Mpixels/sec

Code: Select all

optirun glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce GTX 950M/PCIe/SSE2
231.840918 frames/sec - 258.734465 Mpixels/sec
238.890588 frames/sec - 266.601896 Mpixels/sec

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#12 Post by stevepusser »

What about the Unigine Valley or Heaven benchmark? https://benchmark.unigine.com/
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#13 Post by Bloris »

I tried this https://benchmark.unigine.com/superposi ... ing_valley

This was quite okay https://imgur.com/nUhjOkf
Image

This one a little less https://imgur.com/X1CPSit
Image

but still bettar than lol

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#14 Post by stevepusser »

I thought Superposition would be a bit heavy for your hardware, so that's why I suggested Valley instead. But you do seem to be getting better framerates with the Nvidia GPU, right?
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#15 Post by Bloris »

yes, that's right.

I don't know if can help, but hwne i run the game with wine, all the system start to be slowy like the game is taking every resource something like that...it's hard to write this message too.

I'm watching right now with HTOP and the game is taking 100% of core and the other 7 are just sleeping. Maybe the problem isn't about Graphics, but about primus is using my cores?

https://imgur.com/eSNtvS7
Image

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#16 Post by stevepusser »

You're getting out of the range of my knowledge. :?

I'm not a gamer, but I do have "Space Engine" in Wine for testing. With my Skylake Acer Optimus laptop, which just worked out of the box with Bumblebee, I did have to use the primusrun -b command to run it in Wine, but with my newer MSI GP63 8RD, I had to do some tweaking to get Bumblebee working, and primusrun won't work now for the same programs, but optirun does. Go figure. Either way, Space Engine didn't eat all my CPUs like you say yours is.
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#17 Post by Bloris »

I tried to set VLGTransport in bumblebee.conf from proxy to other values and i get some improvements.
With XV i got a max of 99FPS in game. I still had some low spikes to 50, but it's still better than 30/60. Do you think it's just a lucky coincidence?

Code: Select all

# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=xv 
and this was the command i run form console

Code: Select all

PRIMUS_SYNC=1 VGL_READBACK=pbo vblank_mode=0 optirun -b primus wine start 'C:\Riot Games\League of Legends\LeagueClient.exe'

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Bubmlebee nvidia driver problem

#18 Post by stevepusser »

You're getting out of my range of knowledge now. I just know a bit about the Nvidia drivers and how to set it up. The Arch wiki also has some extra troubleshooting tips for Bumblebee, if you haven't already seen it.

I think we need a "Bumblee Users Support Group" here or on Reddit, where those that have got it to work can share tips. All I see on Reddit is that most people can't get it to work, or that it has terrible performance if they do manage to get it to work.
MX Linux packager and developer

Bloris
Posts: 24
Joined: 2018-12-09 15:53

Re: Bubmlebee nvidia driver problem

#19 Post by Bloris »

Exactly...the problem is i've no idea where i've to ask for problems, there isn't a real bumblebee support.

I would like to continue with bumblebee, but if i can't get it works i just have to find other ways to use my NVIDIA card... :cry:

Post Reply