Page 3 of 8 FirstFirst 12345678 LastLast
Results 101 to 150 of 376

Thread: (Guide) Installing Nvidia + Bumblebee + CUDA for Optimus enabled Laptops

  1. #101
    Join Date
    2014-Oct
    Posts
    2

    Angry Two NVIDIA and one Intel graphic cards

    Hi,
    I have the following problem: when I enter this last command
    Code:
    optirun glxspheres64
    , my screen goes totally black and my nvidia vgas start to run on full speed (vents go on full throttle) and after 20s my laptop shuts down. I suppose my hardware causes the peoblem, I have 3VGAs: the integrated intel hd4400, and 2 nvidia gt750M.
    I know that this problem was mention here, but I did everything what staticn0de recomend, but nothing change.
    dmesg has to long output. What you need exactly? I also erase comments from files for the same reason.

    /etc/bumblebee/bumblebee.conf
    Code:
    [bumblebeed]
    VirtualDisplay=:8
    KeepUnusedXServer=false
    ServerGroup=bumblebee
    TurnCardOffAtExit=false
    NoEcoModeOverride=false
    Driver=nvidia
    XorgConfDir=/etc/bumblebee/xorg.conf.d
    
    [optirun]
    Bridge=auto
    VGLTransport=proxy
    PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
    AllowFallbackToIGC=false
    
    [driver-nvidia]
    KernelDriver=nvidia
    PMMethod=auto
    LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia
    XorgModulePath=/usr/lib/nvidia,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    /etc/bumblebee/xorg.conf.nvidia
    Code:
    Section "ServerLayout"
        Identifier  "Layout0"
        Option      "AutoAddDevices" "false"
        Option      "AutoAddGPU" "false"
    EndSection
    
    Section "Device"
        Identifier  "DiscreteNvidia"
        Driver      "nvidia"
        VendorName  "NVIDIA Corporation"
        BusID "PCI:01:00:0"
        BusID "PCI:07:00:0"
    
        Option "ProbeAllGpus" "false"
    
        Option "NoLogo" "true"
        Option "UseEDID" "false"
        Option "UseDisplayDevice" "none"
        Option "SLI" "AA"
    EndSection
    lspci | egrep 'VGA|3D'
    Code:
    root@kali:~# lspci | egrep 'VGA|3D'
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 0fe4 (rev a1)
    07:00.0 3D controller: NVIDIA Corporation Device 0fe4 (rev a1)
    modinfo nvidia
    Code:
    root@kali:~# modinfo nvidia
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.46
    supported:      external
    license:        NVIDIA
    alias:          pci:v000010DEd00000E00sv*sd*bc04sc80i00*
    alias:          pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
    alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
    alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
    depends:        drm,i2c-core
    vermagic:       3.14-kali1-amd64 SMP mod_unload modversions 
    parm:           NVreg_Mobile:int
    parm:           NVreg_ResmanDebugLevel:int
    parm:           NVreg_RmLogonRC:int
    parm:           NVreg_ModifyDeviceFiles:int
    parm:           NVreg_DeviceFileUID:int
    parm:           NVreg_DeviceFileGID:int
    parm:           NVreg_DeviceFileMode:int
    parm:           NVreg_RemapLimit:int
    parm:           NVreg_UpdateMemoryTypes:int
    parm:           NVreg_InitializeSystemMemoryAllocations:int
    parm:           NVreg_UsePageAttributeTable:int
    parm:           NVreg_MapRegistersEarly:int
    parm:           NVreg_RegisterForACPIEvents:int
    parm:           NVreg_CheckPCIConfigSpace:int
    parm:           NVreg_EnablePCIeGen3:int
    parm:           NVreg_EnableMSI:int
    parm:           NVreg_MemoryPoolSize:int
    parm:           NVreg_RegistryDwords:charp
    parm:           NVreg_RmMsg:charp
    parm:           NVreg_AssignGpus:charp
    modinfo nvidia-uvm
    Code:
    root@kali:~# modinfo nvidia-uvm
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
    supported:      external
    license:        MIT
    depends:        nvidia
    vermagic:       3.14-kali1-amd64 SMP mod_unload modversions
    lsmod
    Code:
    root@kali:~# lsmod
    Module                  Size  Used by
    nls_utf8               12456  1 
    nls_cp437              16553  1 
    vfat                   17185  1 
    fat                    57965  1 vfat
    nouveau              1053347  0 
    ttm                    69667  1 nouveau
    drm_kms_helper         39998  1 nouveau
    drm                   240557  3 ttm,drm_kms_helper,nouveau
    i2c_algo_bit           12751  1 nouveau
    nfnetlink_log          17241  0 
    nfnetlink              12989  1 nfnetlink_log
    binfmt_misc            16949  1 
    loop                   26605  0 
    dm_crypt               22731  0 
    snd_hda_codec_hdmi     45004  1 
    arc4                   12543  2 
    iwldvm                130998  0 
    mac80211              488308  1 iwldvm
    snd_hda_codec_realtek    54360  1 
    snd_hda_codec_generic    59079  1 snd_hda_codec_realtek
    uvcvideo               78910  0 
    iTCO_wdt               12831  0 
    videobuf2_vmalloc      12816  1 uvcvideo
    iTCO_vendor_support    12649  1 iTCO_wdt
    videobuf2_memops       12519  1 videobuf2_vmalloc
    videobuf2_core         35348  1 uvcvideo
    videodev              122088  2 uvcvideo,videobuf2_core
    usb_storage            52037  1 
    media                  18303  2 uvcvideo,videodev
    joydev                 17108  0 
    x86_pkg_temp_thermal    12965  0 
    intel_powerclamp       17159  0 
    coretemp               12854  0 
    kvm_intel             138949  0 
    mxm_wmi                12515  1 nouveau
    kvm                   404503  1 kvm_intel
    snd_hda_intel          39656  5 
    iwlwifi                87784  1 iwldvm
    btusb                  25619  0 
    snd_hda_codec          99921  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
    bluetooth             243618  2 btusb
    psmouse                86464  0 
    snd_hwdep              13148  1 snd_hda_codec
    ideapad_laptop         17499  0 
    sparse_keymap          12760  1 ideapad_laptop
    cfg80211              436618  3 iwlwifi,mac80211,iwldvm
    6lowpan_iphc           16588  1 bluetooth
    snd_pcm                88538  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
    serio_raw              12849  0 
    lpc_ich                20768  0 
    snd_timer              26606  1 snd_pcm
    i2c_i801               16963  0 
    mfd_core               12601  1 lpc_ich
    evdev                  17489  9 
    snd                    61039  18 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
    i2c_core               24265  6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
    mei_me                 13446  0 
    rfkill                 18902  4 cfg80211,ideapad_laptop,bluetooth
    soundcore              13026  1 snd
    mei                    50039  1 mei_me
    ac                     12678  0 
    battery                13101  0 
    wmi                    17339  2 mxm_wmi,nouveau
    video                  17804  1 nouveau
    processor              28221  0 
    button                 12944  1 nouveau
    ext4                  489943  1 
    crc16                  12343  2 ext4,bluetooth
    mbcache                13082  1 ext4
    jbd2                   86788  1 ext4
    dm_mod                 89276  1 dm_crypt
    hid_generic            12393  0 
    usbhid                 44481  0 
    hid                    94062  2 hid_generic,usbhid
    sg                     30043  0 
    sd_mod                 44346  5 
    crc_t10dif             12431  1 sd_mod
    crct10dif_pclmul       13348  1 
    crct10dif_common       12356  2 crct10dif_pclmul,crc_t10dif
    crc32_pclmul           12915  0 
    crc32c_intel           21809  0 
    ghash_clmulni_intel    12978  0 
    aesni_intel           151423  0 
    aes_x86_64             16719  1 aesni_intel
    lrw                    12757  1 aesni_intel
    gf128mul               12970  1 lrw
    glue_helper            12690  1 aesni_intel
    ablk_helper            12572  1 aesni_intel
    cryptd                 14560  3 ghash_clmulni_intel,aesni_intel,ablk_helper
    xhci_hcd              111830  0 
    ahci                   29195  2 
    libahci                27103  1 ahci
    alx                    36175  0 
    mdio                   12599  1 alx
    ehci_pci               12472  0 
    ehci_hcd               48517  1 ehci_pci
    libata                169163  2 ahci,libahci
    scsi_mod              186841  4 sg,usb_storage,libata,sd_mod
    usbcore               166472  8 btusb,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd
    usb_common             12440  1 usbcore
    thermal                17468  0 
    thermal_sys            27685  5 video,intel_powerclamp,thermal,processor,x86_pkg_temp_thermal
    cat /proc/acpi/bbswitch
    Code:
    root@kali:~# cat /proc/acpi/bbswitch
    cat: /proc/acpi/bbswitch: No such file or directory
    echo $PATH
    Code:
    root@kali:~# echo $PATH
    /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin
    find 2> /dev/null / -name nvidia*.ko
    Code:
    root@kali:~# find 2> /dev/null / -name nvidia*.ko
    /var/lib/dkms/nvidia/340.46/3.14-kali1-amd64/x86_64/module/nvidia.ko
    /var/lib/dkms/nvidia/340.46/3.14-kali1-amd64/x86_64/module/nvidia-uvm.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
    Thak you for help

  2. #102
    Join Date
    2014-Oct
    Posts
    2
    Sorry, now the output is
    Code:
    root@kali:~# optirun glxspheres64
    [ 3199.014506] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
    
    [ 3199.014616] [ERROR]Aborting because fallback start is disabled.

  3. #103
    Join Date
    2014-Nov
    Posts
    18

    X won't start with nvidia driver

    I followed all the steps given by staticn0de in Post 25. After installing the NVIDIA drivers, I rebooted my machine. And X does not start anymore. If I change the Driver to intel and comment out the BusID "PCI:01:00:0" line, then X starts. I have an intel HD4000 along with NVidia 720M in my laptop (ASUS X550CC).

    My Xorg.0.log give me the following:

    Code:
    Fatal server error:
    no screens found
    
    Please consult the The X.Org Foundation support 
    	 at http://wiki.x.org
     for help. 
    Please also check the log file at "/var/log/Xorg.1.log" for additional information.
    What could be wrong?

    EDIT:
    I found that the nvidia module was not loaded. I did a modprobe to load nvidia_uvm. Also, I removed the the xorg.conf file from /etc/X11/xorg.conf. It seems like I have made some progress but I have a different situation now. NVidia graphics does not seem to be working:

    Code:
    root@kali:~# grep EE /var/log/Xorg.0.log.old 
    	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [    58.071] (II) Loading extension MIT-SCREEN-SAVER
    [    58.179] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
    [    58.180] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
    [    58.180] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
    [    58.180] (EE) NVIDIA(0):     you continue to encounter problems, Please try
    [    58.180] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
    [    63.816] (EE) NVIDIA(0): Failed to initiate mode change.
    [    63.817] (EE) NVIDIA(0): Failed to complete mode change
    [   103.649] (EE) NVIDIA(0): Failed to initiate mode change.
    [   103.649] (EE) NVIDIA(0): Failed to complete mode change
    [   112.896] (EE) NVIDIA(0): Failed to initiate mode change.
    [   112.896] (EE) NVIDIA(0): Failed to complete mode change
    [   119.568] (EE) NVIDIA(0): Failed to initiate mode change.
    [   119.569] (EE) NVIDIA(0): Failed to complete mode change
    [  1301.003] (EE) NVIDIA(0): Failed to initiate mode change.
    [  1301.003] (EE) NVIDIA(0): Failed to complete mode change
    [  1307.356] (EE) NVIDIA(0): Failed to initiate mode change.
    [  1307.356] (EE) NVIDIA(0): Failed to complete mode change
    Code:
    root@kali:~# glxspheres64 
    Polygons in scene: 62464
    Visual ID of window: 0x95
    Context is Direct
    OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile 
    60.561352 frames/sec - 50.915140 Mpixels/sec
    60.224465 frames/sec - 50.631912 Mpixels/sec
    60.468060 frames/sec - 50.836707 Mpixels/sec
    
    root@kali:~# optirun glxspheres64
    Polygons in scene: 62464
    Visual ID of window: 0x21
    Context is Direct
    OpenGL Renderer: Gallium 0.4 on llvmpipe (LLVM 0x209)
    10.274823 frames/sec - 8.638249 Mpixels/sec
    10.256073 frames/sec - 8.622486 Mpixels/sec
    10.965270 frames/sec - 9.218722 Mpixels/sec
    9.337846 frames/sec - 7.850514 Mpixels/sec
    9.863799 frames/sec - 8.292693 Mpixels/sec
    
    root@kali:~# dmesg|grep -i bbsw
    [   16.506061] bbswitch: version 0.8
    [   16.506085] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    [   16.506096] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    [   16.506434] bbswitch: detected an Optimus _DSM function
    [   16.506653] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    [   16.512184] bbswitch: disabling discrete graphics
    root@kali:~#
    Code:
    root@kali:~# optirun -vv glxspheres64
    [  195.766002] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [  195.766908] [INFO]Configured driver: nvidia
    [  195.767264] [DEBUG]optirun version 3.2.1 starting...
    [  195.767307] [DEBUG]Active configuration:
    [  195.767329] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [  195.767350] [DEBUG] X display: :8
    [  195.767373] [DEBUG] LD_LIBRARY_PATH: /usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia
    [  195.767393] [DEBUG] Socket path: /var/run/bumblebee.socket
    [  195.767413] [DEBUG] Accel/display bridge: auto
    [  195.767433] [DEBUG] VGL Compression: proxy
    [  195.767452] [DEBUG] VGLrun extra options: 
    [  195.767477] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
    [  195.767633] [DEBUG]Using auto-detected bridge virtualgl
    [  203.267664] [INFO]Response: Yes. X is active.
    
    [  203.267701] [INFO]Running application using virtualgl.
    [  203.267911] [DEBUG]Process vglrun started, PID 4424.
    Polygons in scene: 62464
    Visual ID of window: 0x21
    Context is Direct
    OpenGL Renderer: Gallium 0.4 on llvmpipe (LLVM 0x209)
    12.681075 frames/sec - 10.661233 Mpixels/sec
    10.998630 frames/sec - 9.246768 Mpixels/sec
    10.563611 frames/sec - 8.881039 Mpixels/sec
    11.111996 frames/sec - 9.342077 Mpixels/sec
    [  212.685700] [DEBUG]SIGCHILD received, but wait failed with No child processes
    [  212.685776] [DEBUG]Socket closed.
    [  212.685814] [DEBUG]Killing all remaining processes.
    root@kali:~#
    What could be going wrong? Any help would be appreciated. Thanks in advance!!
    Last edited by nikkipolya; 2014-11-08 at 09:52.

  4. #104
    Join Date
    2014-Nov
    Posts
    18

    apt-get install complains -- 'nvidia-installer --uninstall'

    I followed Post 25 to download and install the nvidia-drivers from nvidia's website. Now, each time I run 'apt-get install' to install something, apt-get asks me to run 'nvidia-installer --uninstall'. Do you folks also face the same issue? I have commented out the wheezy-backport from sources.list but still the problem persists.

    Code:
    │                                                                                                                                   │  
    │ The nvidia-installer program was found on this system. This is probably left over from an earlier installation of the non-free   │  
    │ NVIDIA graphics driver, installed using the NVIDIA *.run file directly. This installation is incompatible with the Debian        │  
    │ packages. To install the Debian packages safely, it is therefore necessary to undo the changes performed by nvidia-installer.    │  
    │                                                                                                                                  │  
    │ Run "nvidia-installer --uninstall"?
    │                                       <Yes>                                          <No>                                        │
    Last edited by nikkipolya; 2014-11-08 at 07:54.

  5. #105
    Join Date
    2014-Nov
    Posts
    18
    Ok, I've solved the 'nvidia-installer --uninstall' problem. There was the nvidia-installer-cleanup package in 'iF' status. Doing the following solved the problem:
    Code:
    apt-get purge nvidia-installer-cleanup

  6. #106
    Join Date
    2014-Nov
    Posts
    18
    Hi static0node,

    Here's my configuration:

    Code:
    root@kali:~# 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=nvidia
    # 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/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=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
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia,/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=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    
    root@kali:~#
    And strangely, none of the colon separated directories in my 'LibraryPath' exist!
    Code:
    root@kali:~# cd /usr/lib/x86_64-linux-gnu/nvidia
    bash: cd: /usr/lib/x86_64-linux-gnu/nvidia: No such file or directory
    root@kali:~# cd /usr/lib/i386-linux-gnu/nvidia
    bash: cd: /usr/lib/i386-linux-gnu/nvidia: No such file or directory
    root@kali:~# cd /usr/lib/nvidia
    bash: cd: /usr/lib/nvidia: No such file or directory
    root@kali:~#
    I see that nVidia libraries are in /usr/lib. If I include that in my LibraryPath, then optirun glxgears dumps.
    Code:
    /usr/lib/libkwinnvidiahack.so.4
    /usr/lib/libkwinnvidiahack.so.4.8.0
    /usr/lib/libnvidia-cfg.so
    /usr/lib/libnvidia-cfg.so.1
    /usr/lib/libnvidia-cfg.so.340.46
    /usr/lib/libnvidia-compiler.so.340.46
    /usr/lib/libnvidia-eglcore.so.340.46
    /usr/lib/libnvidia-encode.so
    /usr/lib/libnvidia-encode.so.1
    /usr/lib/libnvidia-encode.so.340.46
    /usr/lib/libnvidia-fbc.so
    /usr/lib/libnvidia-fbc.so.1
    /usr/lib/libnvidia-fbc.so.340.46
    /usr/lib/libnvidia-glcore.so.340.46
    /usr/lib/libnvidia-glsi.so.340.46
    /usr/lib/libnvidia-ifr.so
    /usr/lib/libnvidia-ifr.so.1
    Code:
    root@kali:~# optirun -vv glxgears
    [22184.002479] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [22184.003239] [INFO]Configured driver: nvidia
    [22184.003544] [DEBUG]optirun version 3.2.1 starting...
    [22184.003587] [DEBUG]Active configuration:
    [22184.003621] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [22184.003658] [DEBUG] X display: :8
    [22184.003692] [DEBUG] LD_LIBRARY_PATH: /usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia:/usr/lib
    [22184.003729] [DEBUG] Socket path: /var/run/bumblebee.socket
    [22184.003762] [DEBUG] Accel/display bridge: auto
    [22184.003797] [DEBUG] VGL Compression: proxy
    [22184.003829] [DEBUG] VGLrun extra options: 
    [22184.003863] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
    [22184.003969] [DEBUG]Using auto-detected bridge virtualgl
    [22191.468977] [INFO]Response: Yes. X is active.
    
    [22191.469014] [INFO]Running application using virtualgl.
    [22191.469293] [DEBUG]Process vglrun started, PID 5223.
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  137 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x200002
      Serial number of failed request:  38
      Current serial number in output stream:  38
    [22191.630283] [DEBUG]SIGCHILD received, but wait failed with No child processes
    [22191.630313] [DEBUG]Socket closed.
    [22191.630332] [DEBUG]Killing all remaining processes.
    root@kali:~# optirun -b primus -vv glxgears
    [22199.144120] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [22199.144849] [INFO]Configured driver: nvidia
    [22199.145104] [DEBUG]optirun version 3.2.1 starting...
    [22199.145143] [DEBUG]Active configuration:
    [22199.145164] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [22199.145184] [DEBUG] X display: :8
    [22199.145205] [DEBUG] LD_LIBRARY_PATH: /usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia:/usr/lib
    [22199.145226] [DEBUG] Socket path: /var/run/bumblebee.socket
    [22199.145247] [DEBUG] Accel/display bridge: primus
    [22199.145268] [DEBUG] VGL Compression: proxy
    [22199.145292] [DEBUG] VGLrun extra options: 
    [22199.145311] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
    [22207.331180] [INFO]Response: Yes. X is active.
    
    [22207.331221] [INFO]Running application using primus.
    [22207.331496] [DEBUG]Process glxgears started, PID 5250.
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  137 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x200002
      Serial number of failed request:  38
      Current serial number in output stream:  38
    [22207.434966] [DEBUG]SIGCHILD received, but wait failed with No child processes
    [22207.434987] [DEBUG]Socket closed.
    [22207.435001] [DEBUG]Killing all remaining processes.
    root@kali:~#

  7. #107
    Join Date
    2014-Nov
    Posts
    18
    I think I have a better bumblebee.conf file now. I now have a different error, after doing the following:
    Code:
    root@kali:~# mkdir -p /usr/lib/nvidia
    root@kali:~# mv /usr/lib/libGL* /usr/lib/nvidia
    root@kali:~# 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=nvidia
    # 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/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=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
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    # XorgModulePath=/usr/lib/nvidia,/usr/lib/xorg/modules
    XorgModulePath=/usr/lib/xorg/modules/drivers,/usr/lib/xorg/modules/extensions
    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
    Code:
    root@kali:~# optirun  glxspheres64 
    [ 3856.451352] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
    
    [ 3856.451431] [ERROR]Aborting because fallback start is disabled.
    root@kali:~#

  8. #108
    Join Date
    2014-Nov
    Posts
    18
    Great! Everything works fine now. I am able to run both with my integrated intel graphics and nvidia graphics. My CUDA tests PASS too!! Thanks to all of you, and most importantly to static0node for the excellent howto.

    In case somebody faces the same problem as I did, here's what I did:

    bumblebee's log at /var/log/Xorg.8.log gave me all the info I needed to correct my problems. Alternatively, you can stop bumblebee with '/etc/init.d/bumblebee stop' command. Then you can manually launch the daemon by issuing 'bumblebeed -vv' from a console. Note: that is two consecutive 'v's.

    I figured out from the log file that the Xorg server for my nvidia card was using the libglx.so library built by "X.org Foundation" and not the one supplied by NVIDIA. The one supplied by NVIDIA was located in '/usr/lib/xorg/modules/extensions' and was named as 'libglx.so.340.46'. I made a backup of my libglx.so in that directory and renamed libglx.so.340.46 to libglx.so. And tried to relaunch bumblebee, and lo and behold, it all worked like a charm. But when I restarted my X server, my intel glx stopped working. Predictably. Long story short, here is what I effectively did:

    Code:
    root@kali:~# cd /usr/lib/xorg
    root@kali:/usr/lib/xorg# mkdir -p nvidia
    root@kali:/usr/lib/xorg# cp -R modules/* nvidia/
    root@kali:/usr/lib/xorg# cd nvidia/extensions/
    root@kali:/usr/lib/xorg/nvidia/extensions# mv libglx.so.340.46 libglx.so
    And here's my bumblebee.conf
    Code:
    root@kali:~# 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=nvidia
    # 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/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=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
    
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/xorg/nvidia/drivers,/usr/lib/xorg/nvidia
    # XorgModulePath=
    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
    
    root@kali:~#
    That was it. Every thing work fine now! Both OpenGL and CUDA apps use my nvidia 720m card.

    Code:
    root@kali:/opt/cuda/NVIDIA_CUDA-6.0_Samples/bin/x86_64/linux/release# optirun ./deviceQuery 
    ./deviceQuery Starting...
    
     CUDA Device Query (Runtime API) version (CUDART static linking)
    
    Detected 1 CUDA Capable device(s)
    
    Device 0: "GeForce GT 720M"
      CUDA Driver Version / Runtime Version          6.5 / 6.0
      CUDA Capability Major/Minor version number:    3.5
      Total amount of global memory:                 2048 MBytes (2147352576 bytes)
      ( 1) Multiprocessors, (192) CUDA Cores/MP:     192 CUDA Cores
      GPU Clock rate:                                758 MHz (0.76 GHz)
      Memory Clock rate:                             800 Mhz
      Memory Bus Width:                              64-bit
      L2 Cache Size:                                 524288 bytes
      Maximum Texture Dimension Size (x,y,z)         1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096)
      Maximum Layered 1D Texture Size, (num) layers  1D=(16384), 2048 layers
      Maximum Layered 2D Texture Size, (num) layers  2D=(16384, 16384), 2048 layers
      Total amount of constant memory:               65536 bytes
      Total amount of shared memory per block:       49152 bytes
      Total number of registers available per block: 65536
      Warp size:                                     32
      Maximum number of threads per multiprocessor:  2048
      Maximum number of threads per block:           1024
      Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
      Max dimension size of a grid size    (x,y,z): (2147483647, 65535, 65535)
      Maximum memory pitch:                          2147483647 bytes
      Texture alignment:                             512 bytes
      Concurrent copy and kernel execution:          Yes with 1 copy engine(s)
      Run time limit on kernels:                     Yes
      Integrated GPU sharing Host Memory:            No
      Support host page-locked memory mapping:       Yes
      Alignment requirement for Surfaces:            Yes
      Device has ECC support:                        Disabled
      Device supports Unified Addressing (UVA):      Yes
      Device PCI Bus ID / PCI location ID:           1 / 0
      Compute Mode:
         < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
    
    deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.5, CUDA Runtime Version = 6.0, NumDevs = 1, Device0 = GeForce GT 720M
    Result = PASS
    My laptop is an ASUS X550CC with ETPS/2 Elantech Touchpad. My CUDA driver and run-time don't match. I will try upgrading to CUDA 6.5 and see what happens later on.

    Code:
    root@kali:~# optirun glxspheres64 
    Polygons in scene: 62464
    Visual ID of window: 0x21
    Context is Direct
    OpenGL Renderer: GeForce GT 720M/PCIe/SSE2
    126.708808 frames/sec - 123.235973 Mpixels/sec
    126.436952 frames/sec - 122.971568 Mpixels/sec
    125.862084 frames/sec - 122.412456 Mpixels/sec
    128.373977 frames/sec - 124.855503 Mpixels/sec
    126.762602 frames/sec - 123.288292 Mpixels/sec
    128.711295 frames/sec - 125.183576 Mpixels/sec
    root@kali:~#
    Last edited by nikkipolya; 2014-11-10 at 16:40.

  9. #109
    Join Date
    2014-Nov
    Posts
    18
    Hi Filip0913,

    launch optirun -vv glxspheres64 and then paste here the output from /var/log/Xorg.8.log (assuming a new instance of X launches on tty 8)


    Code:
    optirun -vv glxspheres64
    Code:
    cat /var/log/Xorg.8.log

  10. #110
    Join Date
    2013-May
    Posts
    35
    Thank you . your thread helped me a lot.
    I had done it successfully before without cuda only I could run apps with optirun. after a re-installation of kali I followed your post and here are the result : deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.5, CUDA Runtime Version = 6.5, NumDevs = 1, Device0 = GeForce GT 740M
    Result = PASS

  11. #111
    Join Date
    2014-Oct
    Posts
    3
    Hi,
    i have the following problem:

    i followed the guide and i arrived at the step in which i have to edit xorg.conf.nvidia

    Edit xorg.conf.nvidia and add a line under the 'Section "Device"' area so that is matches what is shown below. Change the bus ID to match what you recorded previously and take note that you recored a . before the last number and it is now a ':'. You need the ':'.
    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BusID "PCI:03:00:0"
    i don't have that file (is it supposed to be in /etc/X11 ? ) so i could create it and the only content would be that in quote tag.. is that correct?

  12. #112
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    open a console >
    Code:
    nano /etc/bumblebee/xorg.conf.nvidia
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  13. #113
    Join Date
    2013-May
    Posts
    35
    I'm having a strange issue.
    first as I stated before in a reply everything worked well. I even proceeded and tried pyrit and cudahashcat on a wpa2 handshake it worked well I successfully cracked my own wpa2 password with both methods.
    got a problem then i fixed it with grub . I got another one with nvidia-uvm so I compiled it and replaced it in dkms/ .

    now when I restart and run modprobe nvidia or modprobe nvidia-uvm I get no such device. so I checked the Cuda devicequery test to see if still passes which it did , suddenly the modprobe worked again
    I restarted the same thing happened it only works after I do the cuda test . I checked my paths in bashrc everything is right in it. what could be the problem ?

  14. #114
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    - can you copy/paste the error message here.

    - run
    Code:
    optirun pyrit benchmark
    right after having booted on to Kali(don't wait too long after having booted, or it might not work).
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  15. #115
    Join Date
    2013-May
    Posts
    35
    here is my pyrit benchmark and cores
    Code:
     # optirun pyrit list_cores
    
    Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
    This code is distributed under the GNU General Public License v3+
    
    The following cores seem available...
    #1:  'CPU-Core (SSE2)'
    #2:  'CPU-Core (SSE2)'
    #3:  'CPU-Core (SSE2)'
    #4:  'CPU-Core (SSE2)'
    #5:  'CPU-Core (SSE2)'
    #6:  'CPU-Core (SSE2)'
    #7:  'CPU-Core (SSE2)'
    #8:  'CPU-Core (SSE2)
    It's clear No GPU is detected even if i used optirun
    Code:
     optirun pyrit benchmark
    Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
    This code is distributed under the GNU General Public License v3+
    
    Running benchmark (2922.3 PMKs/s)... / 
    
    Computed 2922.27 PMKs/s total.
    #1: 'CPU-Core (SSE2)': 389.2 PMKs/s (RTT 3.3)
    #2: 'CPU-Core (SSE2)': 384.7 PMKs/s (RTT 3.3)
    #3: 'CPU-Core (SSE2)': 402.0 PMKs/s (RTT 3.3)
    #4: 'CPU-Core (SSE2)': 394.1 PMKs/s (RTT 3.3)
    #5: 'CPU-Core (SSE2)': 401.3 PMKs/s (RTT 3.2)
    #6: 'CPU-Core (SSE2)': 395.2 PMKs/s (RTT 3.3)
    #7: 'CPU-Core (SSE2)': 401.6 PMKs/s (RTT 3.2)
    #8: 'CPU-Core (SSE2)': 395.8 PMKs/s (RTT 3.3)
    no GPU .

    But for cudahashcat it detects GPU
    here is MD5 test
    Code:
    Speed.GPU.#1.:  1875.2 MH/s
    
    Hashtype: MD5
    Workload: 1024 loops, 256 accel
    I'm using pyrit that comes preinstalled with Kali 1.0.9 I checked it's the same version that exist in the dev site
    to load the modules i created an alias to run the cuda test pass everytime i restart .
    Last edited by bahha; 2014-11-26 at 11:10.

  16. #116
    Join Date
    2014-Oct
    Posts
    3
    i followed the guide at post #25 and then i installed pyrit but when i try to benchmark i get:

    [12953.257431] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please

    [12953.257532] [ERROR]Aborting because fallback start is disabled.

  17. #117
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    @ bahha & rego, the only thing I can recommend is to try a fresh Kali install until staticn0de returns.

    This whole installation is somewhat fragile and any subsequent modification to core files seems to mess things up. I wish to be more precise but all I know is that I have to run 'optirun pyrit benchmark' in the following minutes after booting into Kali to be able to use cudaHashcat, or else I get the same error as the above post #116, and I have to reboot.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  18. #118
    Join Date
    2013-May
    Posts
    35
    @ Quest I did install everything after a fresh install of the Os .
    everything is working except pyrit I'll try to compile it from source and see .
    having to run optirun after moments of boot . I think I may make it as a start up application. so far for cuda test pass I made an alias in bashrc .

  19. #119
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    but wait, mine is exactly like yours in post #115. No mention of GPU, ever.

    Your telling me that Pyrit is supposed to detect and use GPU along with CPUs? If that's the case then mine never worked.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  20. #120
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    opps actually Pyrit does detect/use my GPU..

    Code:
    root@kali:~# optirun pyrit benchmark
    Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
    This code is distributed under the GNU General Public License v3+
    
    Running benchmark (9002.1 PMKs/s)... - 
    
    Computed 9002.07 PMKs/s total.
    #1: 'CUDA-Device #1 'GeForce GT 630M'': 5761.6 PMKs/s (RTT 2.8)
    #2: 'CPU-Core (SSE2/AES)': 520.8 PMKs/s (RTT 3.0)
    #3: 'CPU-Core (SSE2/AES)': 521.7 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2/AES)': 523.7 PMKs/s (RTT 3.0)
    #5: 'CPU-Core (SSE2/AES)': 523.5 PMKs/s (RTT 3.0)
    #6: 'CPU-Core (SSE2/AES)': 518.2 PMKs/s (RTT 3.0)
    #7: 'CPU-Core (SSE2/AES)': 523.5 PMKs/s (RTT 3.0)
    #8: 'CPU-Core (SSE2/AES)': 507.0 PMKs/s (RTT 3.0)
    root@kali:~#
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  21. #121
    Join Date
    2013-May
    Posts
    35
    @ Quest yes it should show your GPU

    I removed the pre-installed pyrit and installed it from source following the guide on the first page .

    and it works finally


    here is the output of benchmark before installing it from source, notice how there is no GPU in the list and look at the second output

    Code:
     
    optirun pyrit benchmark
    Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
    This code is distributed under the GNU General Public License v3+
    
    Running benchmark (2922.3 PMKs/s)... / 
    
    Computed 2922.27 PMKs/s total.
    #1: 'CPU-Core (SSE2)': 389.2 PMKs/s (RTT 3.3)
    #2: 'CPU-Core (SSE2)': 384.7 PMKs/s (RTT 3.3)
    #3: 'CPU-Core (SSE2)': 402.0 PMKs/s (RTT 3.3)
    #4: 'CPU-Core (SSE2)': 394.1 PMKs/s (RTT 3.3)
    #5: 'CPU-Core (SSE2)': 401.3 PMKs/s (RTT 3.2)
    #6: 'CPU-Core (SSE2)': 395.2 PMKs/s (RTT 3.3)
    #7: 'CPU-Core (SSE2)': 401.6 PMKs/s (RTT 3.2)
    #8: 'CPU-Core (SSE2)': 395.8 PMKs/s (RTT 3.3)
    here is the output after installing it from source .
    Code:
    Computed 9013.16 PMKs/s total.
    #1: 'CUDA-Device #1 'GeForce GT 740M'': 7018.6 PMKs/s (RTT 2.8)
    #2: 'CPU-Core (SSE2/AES)': 408.2 PMKs/s (RTT 3.2)
    #3: 'CPU-Core (SSE2/AES)': 409.0 PMKs/s (RTT 3.3)
    #4: 'CPU-Core (SSE2/AES)': 411.4 PMKs/s (RTT 3.3)
    #5: 'CPU-Core (SSE2/AES)': 413.1 PMKs/s (RTT 3.3)
    #6: 'CPU-Core (SSE2/AES)': 413.3 PMKs/s (RTT 3.2)
    #7: 'CPU-Core (SSE2/AES)': 410.9 PMKs/s (RTT 3.3)
    #8: 'CPU-Core (SSE2/AES)': 412.8 PMKs/s (RTT 3.3)
    look at the deference between computed PMKs/s in both outputs !

  22. #122
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    wow great!

    I thought for you to install Pyrit like the guide said, because this whole installation is very tricky/complex, and if one does not follow the exact procedure then it does not work, or it partially does.

    *Funny how Pyrit does not use the 8th core when it use the GPU... Anyway.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  23. #123
    Join Date
    2013-May
    Posts
    35
    Quote Originally Posted by rego View Post
    i followed the guide at post #25 and then i installed pyrit but when i try to benchmark i get:
    that happened to me . I fixed it with by modifying grub

    here is the guide post link

  24. #124
    Join Date
    2013-May
    Posts
    35

    Fix intel driver after installing nvidia

    After I installed the nvidia proprietary driver from this post with cuda6

    I found that the INTEL driver is broken and some apps need it for 3D acceleration like GDM3 or anything that can't run with optirun

    so here is a fix I did after reading and searching in other places .


    first : to check if your INTEL driver is broken run this command without optirun

    Code:
    glxgears
    if it works you are good nothing to do after this if not follow next instruction


    --- remove the invidia driver if you installed it from NVIDIAxxx*.run that is the one you downloaded from nvidia site.

    --- remove it with nividia-intaller-cleanup just intall it and it'll prompt you to remove the driver.

    --- then follow the first post to install the driver from repository which is 331-xx version. don't forget to change bumblebee and xorg as mentioned in the first post, for the repo driver to work. | the first post is changed it doesn't have the repo driver anymore .| so install it by apt-get intall nvidia-glx and apt-get install nvidia alternative
    it will grab everything else . or google how to install nvidia driver 331 would be better.
    --- at this point you have the nvidia driver functioning with optirun but if you have cuda6-5 it won't function because it requires a higher version of driver 340.xx. at least that's what happened to me

    --- to fix it remove cuda6-5 by entering the folder where you installed the NVIDIA Cuda samples, probably you installed it in root folder. then run

    Code:
    make clean
    --- remove the samples folder

    --- go to /usr/local/ and delete cudaxx and its symlink .

    --- you can still use cuda6-5 if you upgrade the driver follow last lines in this post

    --- if you are ok with cuda5 download cuda5.xx and install it follow the firt page in this thread .

    --- if you have the intel mesa driver broken still then do the next

    --- download mesa-alternative-glx I often use synaptic to install my packages else apt-get from terminal .

    --- when it's installed run

    Code:
    update-alternative  --config glx
    --- when you have both nvidia and intel drivers installed it will display three options

    auto (with the selected driver)
    manual nvidia
    manual intel

    --- enter the number in the far left that correspond to intel and hit Enter
    --- now it will fix your intel driver. reboot and try glxgears and optirun glxgears it should work, works for me

    --- finally if you still want to use cuda6-5 update the nvidia driver

    --- *add this repo to your source.list
    deb http://http.us.debian.org/debian/ sid main non-free contrib
    .

    --- run apt-get update when done open synaptic and upgrade the nvidia driver and reboot

    --- now you can install cuda6-5 again following this post

    . don't forget to remove the repo you added to your source.list, before you break something

    I hope someone will find this useful it works for me
    here is glxgears with intel and nvidia notice fps and compare it with nvidia one .

    Code:
    glxgears
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    300 frames in 5.0 seconds = 59.828 FPS
    300 frames in 5.0 seconds = 59.807 FPS
    with optirun
    Code:
    optirun glxgears
    4139 frames in 5.0 seconds = 827.670 FPS
    4114 frames in 5.0 seconds = 822.686 FPS
    Last edited by bahha; 2015-06-12 at 08:47.

  25. #125
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    good stuff! Thanks bahha.

    My fan does not decelerate after running "optirun pyrit benchmark". I have to reboot the computer for it to normalize. So something(probly my nVidia HD 630M) stays ON long after finishing operations when should be OFF. If anyone has any ideas...

    I'm suspecting Bumblebee
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  26. #126
    Join Date
    2013-May
    Posts
    35
    you can try
    echo OFF >> /proc/acpi/bbswitch
    then see if it works with
    cat /proc/acpi/bbswitch
    if says OFF then it's OFF otherwise it's refusing to unload it, because it's being used by the nvidia module
    you can try to reinstall bbswitch and bumblebee
    Last edited by bahha; 2014-12-10 at 18:55.

  27. #127
    Join Date
    2014-Feb
    Posts
    6
    Till today all working perfect!!After updating xserver-xorg-core to 2:1.12.4-6+deb7u5 now when i run "optirun glxspheres64" gives the error :
    Code:
    Polygons in scene: 62464
    Visual ID of window: 0x21
    Context is Direct
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  137 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x200002
      Serial number of failed request:  38
      Current serial number in output stream:  38
    if i run any other program eg "optirun pyrit" its working fine.
    Any help would be appreciated.
    Im using kali 1.09 3.14-kali1-amd64

  28. #128
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Useful to know these commands, but it didn't work for me..

    root@kali:~# cat /proc/acpi/bbswitch
    0000:01:00.0 ON
    root@kali:~# echo OFF >> /proc/acpi/bbswitch
    root@kali:~# cat /proc/acpi/bbswitch
    0000:01:00.0 ON
    root@kali:~#
    Edit:

    root@kali:~# glxgears
    Xlib: extension "GLX" missing on display ":0.0".
    Error: couldn't get an RGB, Double-buffered visual
    root@kali:~#
    Had no idea that my Intel driver was broken!! Geez what a mess...

    Thanks again bahha!
    Last edited by Quest; 2014-12-11 at 10:48.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  29. #129
    Join Date
    2014-Feb
    Posts
    6
    Quote Originally Posted by darkshadowman View Post
    Till today all working perfect!!After updating xserver-xorg-core to 2:1.12.4-6+deb7u5 now when i run "optirun glxspheres64" gives the error :
    Code:
    Polygons in scene: 62464
    Visual ID of window: 0x21
    Context is Direct
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  137 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x200002
      Serial number of failed request:  38
      Current serial number in output stream:  38
    if i run any other program eg "optirun pyrit" its working fine.
    Any help would be appreciated.
    Im using kali 1.09 3.14-kali1-amd64

    problem solved. what i did was :
    Code:

    mv /usr/lib/xorg/modules/extensions/libglx.so /usr/lib/xorg/modules/extensions/libglx.so.orig
    ln -s /usr/lib/xorg/modules/extensions/libglx.so.XXX.YY /usr/lib/xorg/modules/extensions/libglx.so
    where XXX.YY is your driver version

  30. #130
    Join Date
    2013-May
    Posts
    35
    my recommendation for you is to use my post above too fix everything, that's what I did and everything is ok for now .

    @ darkshadowman
    pyrit works even without installing the nvidia driver. you can check if your driver works by :
    optirun pyrit list_cores
    if it lists your GPU to then it's ok , look at the example bellow
    The following cores seem available...
    #1: 'CUDA-Device #1 'GeForce GT 740M''
    #2: 'CPU-Core (SSE2/AES)'
    #3: 'CPU-Core (SSE2/AES)'
    #4: 'CPU-Core (SSE2/AES)'
    #5: 'CPU-Core (SSE2/AES)'
    #6: 'CPU-Core (SSE2/AES)'
    #7: 'CPU-Core (SSE2/AES)'
    #8: 'CPU-Core (SSE2/AES)'

  31. #131
    Join Date
    2014-Dec
    Posts
    2
    Hi everybody!
    I need some help, please.
    Kali -32 Bits
    Nvidia card integrated on a HP notebook dv9 series with nvidia integrated.
    I did a fresh install and the first thing to do was installing the graphics.
    Unfortunatlly my bumblebee tells me:

    [ERROR]No integrated video card found, quitting.

    well the Virtualgl was instaled well, the Cuda was instaled well , and the driver Nvidia was installed well.
    Everything done as static0de last update post for the 340 driver. Exception for the packages wich were i386 compatible. and one or another path I had to chage.

    well the last thing I was expecting to see was no hardware found!
    Last edited by gp_uva; 2014-12-14 at 14:37.

  32. #132
    Join Date
    2014-Dec
    Posts
    2

    Bumblebee not activated

    Quote Originally Posted by gp_uva View Post
    Hi everybody!
    I need some help, please.
    Kali -32 Bits
    Nvidia card integrated on a HP notebook dv9 serieswith nvidia integrated.
    I did a fresh install and the first thing to do was the instalation of the graphics. well....
    My bumblebee tels me:
    [ERROR]No integrated video card found, quitting.
    well the Virtualgl was instaled the Cuda was instaled the and the driver Nvidia was installed. Everything done with static0de last update post for the 340 driver. Exception for the packages wich were i386 compatible. and one or another path I had to chage.

    well the last thing I was expecting to see is no harware found?????.
    Help
    Edited

    here is what I am experiencing

    root@GP-Notebook:~# modinfo nvidia
    filename: /lib/modules/3.14-kali1-686-pae/updates/dkms/nvidia.ko
    alias: char-major-195-*
    version: 340.65
    supported: external
    license: NVIDIA
    alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
    alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
    alias: pci:v000010DEd*sv*sd*bc03sc02i00*
    alias: pci:v000010DEd*sv*sd*bc03sc00i00*
    depends: drm,i2c-core
    vermagic: 3.14-kali1-686-pae SMP mod_unload modversions 686
    parm: NVreg_Mobile:int
    parm: NVreg_ResmanDebugLevel:int
    parm: NVreg_RmLogonRC:int
    parm: NVreg_ModifyDeviceFiles:int
    parm: NVreg_DeviceFileUID:int
    parm: NVreg_DeviceFileGID:int
    parm: NVreg_DeviceFileMode:int
    parm: NVreg_RemapLimit:int
    parm: NVreg_UpdateMemoryTypes:int
    parm: NVreg_InitializeSystemMemoryAllocations:int
    parm: NVreg_UsePageAttributeTable:int
    parm: NVreg_MapRegistersEarly:int
    parm: NVreg_RegisterForACPIEvents:int
    parm: NVreg_CheckPCIConfigSpace:int
    parm: NVreg_EnablePCIeGen3:int
    parm: NVreg_EnableMSI:int
    parm: NVreg_MemoryPoolSize:int
    parm: NVreg_RegistryDwords:charp
    parm: NVreg_RmMsg:charp
    parm: NVreg_AssignGpus:charp
    root@GP-Notebook:~# optirun glxspheres64
    [ 3634.315931] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
    [ 3634.316064] [ERROR]Could not connect to bumblebee daemon - is it running?
    root@GP-Notebook:~# bumblebeed
    [ 3818.730812] [ERROR]No integrated video card found, quitting.

  33. #133
    Join Date
    2014-Dec
    Posts
    5

    NVIDIA will not install correctly

    First of all many thanks to staticn0de, I could not have made half the progress I have without his posts.

    I really hope someone can help me with this issue. I have been struggling for days now trying to get this up and running, i.e. my Nvidia graphics card.

    I have listed below all the information I think might be pertinent, maybe over kill but I didn't want to leave anything out. I am new to this so forgive me if I am on the wrong thread or have used the wrong format.

    I have downloaded the NVIDIA drivers NVIDIA GeForce 610m (1GB) from the nvidia web site as directed, these are the drivers the specs for my pc state, Lenovo Ideapad U410.
    I am running Kali 64 bit as my primary OS, no dual boot, kernel details are also listed below.

    Below are the steps I have gone through trying to get this working: These were all done as a regular user then again as root.
    -stopped gdm3 / terminal ./NVIDIA-Linux-x86_64-340.65.run -dkms -z (failed)
    -stopped gdm3 /terminal ./NVIDIA-Linux-x86_64-340.65.run (failed)
    -booted to command prompt ./NVIDIA-Linux-x86_64-340.65.run -dkms -z (failed)
    -booted to command prompt ./NVIDIA-Linux-x86_64-340.65.run (failed)

    Removed all files containing NVIDIA with Synaptic Package Manager then went through the steps listed above, same results.

    Removed all files containing nouveau with Synaptic Package Manager then went through the steps listed above, same results.

    I have now reinstalled the nouveau files I removed previously.

    I have NOT reinstalled the nvidia files referenced to in Synaptic Package Manager.
    I have included my sources list below for verification..it contains notes to myself in it as well.

    I have followed the below link on what to do post Kali install
    HTML Code:
    http://www.blackmoreops.com/2014/03/03/20-things-installing-kali-linux/
    I followed these instructions, but lost the gui altogether. This happend a number of times and I reinstalled the OS twice before I found the xorg file and removed it...(I guess I should have read step B and saved some time)
    HTML Code:
    http://www.blackmoreops.com/2014/06/27/kali-linux-1-0-7-kernel-3-14-install-proprietary-nvidia-driver/
    etc/fstab/
    Code:
    ## CD/DVD Repositories ##
    #deb cdrom:[Debian GNU/Linux 7.0 _Kali_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141002-11:29]/ kali contrib main non-free
    #deb cdrom:[Debian GNU/Linux 7.0 _Kali_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141002-11:29]/ kali contrib main non-free
    
    ## Regular Repositories ##
    deb http://http.kali.org/kali kali main non-free contrib
    #deb http://security.kali.org/kali-security kali/updates main contrib non-free
    
    ## Source Repositories ##
    deb-src http://http.kali.org/kali kali main non-free contrib
    deb-src http://security.kali.org/kali-security kali/updates main contrib non-free
    
    ## Security Updates ##
    deb http://security.kali.org/kali-security kali/updates main contrib non-free
    
    ## HOWTO - Install GNS3 1.2 using Kali Linux 1.0.9 64-bit ## 
    ## https://community.gns3.com/thread/3752 ##
    ## REMOVE THESE FROM SOURCES AFTER INTSLLING GNS3 SEEMED TO CAUSE PROBLEMS WITH GUI IF USED W/APT-GET UPDATE / UPGRADE ##
    #deb http://http.us.debian.org/debian testing main non-free contrib
    #deb-src http://http.us.debian.org/debian testing main non-free contrib
    Code:
    user@gabrielle:~$ lspci -vnn | grep VGA -A 12
    00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device [17aa:3903]
        Flags: bus master, fast devsel, latency 0, IRQ 47
        Memory at eb000000 (64-bit, non-prefetchable) [size=4M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 4000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: i915
    
    00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
        Subsystem: Lenovo Device [17aa:3977]
        Flags: bus master, medium devsel, latency 0, IRQ 41
    --
    01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1058] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device [17aa:3903]
        Flags: bus master, fast devsel, latency 0, IRQ 46
        Memory at ea000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=128M]
        Memory at e8000000 (64-bit, prefetchable) [size=32M]
        I/O ports at 3000 [size=128]
        Expansion ROM at <ignored> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
    
    03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
        Subsystem: Lenovo Device [17aa:3975]
    Code:
    user@gabrielle:~$ uname -a
    Linux gabrielle 3.14-kali1-amd64 #1 SMP Debian 3.14.5-1kali1 (2014-06-07) x86_64 GNU/Linux
    Code:
    user@gabrielle:~$ lsmod | grep nouveau
    nouveau              1053347  0
    mxm_wmi                12515  1 nouveau
    ttm                    69667  1 nouveau
    drm_kms_helper         39998  2 i915,nouveau
    video                  17804  2 i915,nouveau
    drm                   240557  5 ttm,i915,drm_kms_helper,nouveau
    i2c_algo_bit           12751  2 i915,nouveau
    i2c_core               24265  7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
    wmi                    17339  2 mxm_wmi,nouveau
    button                 12944  2 i915,nouveau
    Code:
    user@gabrielle:/home/user# passwd -S sys | tail -1 | awk '{print $3}'
    10/02/2014
    Code:
    user@gabrielle:/home/user# tune2fs -l /dev/sda1 | grep 'Filesystem created'
    Filesystem created:       Thu Dec 25 12:43:33 2014
    Code:
    user@gabrielle:/home/user# lscpu
    Architecture:          x86_64
    CPU op-mode(s):        32-bit, 64-bit
    Byte Order:            Little Endian
    CPU(s):                4
    On-line CPU(s) list:   0-3
    Thread(s) per core:    2
    Core(s) per socket:    2
    Socket(s):             1
    NUMA node(s):          1
    Vendor ID:             GenuineIntel
    CPU family:            6
    Model:                 58
    Stepping:              9
    CPU MHz:               806.250
    BogoMIPS:              4988.59
    Virtualization:        VT-x
    L1d cache:             32K
    L1i cache:             32K
    L2 cache:              256K
    L3 cache:              4096K
    NUMA node0 CPU(s):     0-3
    Code:
    user@gabrielle:/home/user# lspci | grep VGA
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 1058 (rev a1)
    Code:
    user@gabrielle:~$ lspci | egrep 'VGA|3D'
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 1058 (rev a1)
    nvidia-installer log file '/var/log/nvidia-installer.log'

    Code:
    nvidia-installer log file '/var/log/nvidia-installer.log'
    creation time: Wed Dec 31 10:46:46 2014
    installer version: 340.65
    
    PATH: /sbin:/usr/sbin:/bin:/usr/bin
    
    nvidia-installer command line:
        ./nvidia-installer
    
    Using: nvidia-installer ncurses user interface
    -> License accepted.
    -> Installing NVIDIA driver version 340.65.
    -> There appears to already be a driver installed on your system (version: 340.65).  As part of installing this driver (version: 340.65), the existing driver will be uninstalled.  Are you sure you want to continue? (Answer: Continue installation)
    -> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: Yes)
    -> Installing both new and classic TLS OpenGL libraries.
    -> Installing both new and classic TLS 32bit OpenGL libraries.
    -> Install NVIDIA's 32-bit compatibility libraries? (Answer: No)
    -> Parsing log file:
    -> done.
    -> Validating previous installation:
    -> done.
    -> Uninstalling NVIDIA Accelerated Graphics Driver for Linux-x86_64 (1.0-34065 (340.65)):
    -> DKMS module detected; removing...
    -> done.
    -> Uninstallation of existing driver: NVIDIA Accelerated Graphics Driver for Linux-x86_64 (340.65) is complete.
    -> Skipping installation of the libvdpau wrapper library.
    -> Searching for conflicting X files:
    -> done.
    -> Searching for conflicting OpenGL files:
    -> done.
    -> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (340.65):
       executing: '/sbin/ldconfig'...
    -> done.
    -> Driver file installation is complete.
    -> Installing DKMS kernel module:
    ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 340.65 -k 3.14-kali1-amd64`:
    Kernel preparation unnecessary for this kernel.  Skipping...
    
    Building module:
    cleaning build area....
    make KERNELRELEASE=3.14-kali1-amd64 module KERNEL_UNAME=3.14-kali1-amd64; make -C uvm module KERNEL_UNAME=3.14-kali1-amd64 KBUILD_EXTMOD=/var/lib/dkms/nvidia/340.65/build/uvm....(bad exit status: 2)
    Error! Bad return status for module build on kernel: 3.14-kali1-amd64 (x86_64)
    Consult /var/lib/dkms/nvidia/340.65/build/make.log for more information.
    -> error.
    ERROR: Failed to install the kernel module through DKMS. No kernel module was installed; please try installing again without DKMS, or check the DKMS logs for more information.
    ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

  34. #134
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Hi there,

    First things first, clean up the NIVIDA drivers already installed. I've added sudo for if you are a regular user

    sudo ./NVIDIA-Linux-x86_64-340.65.run --uninstall

    The command you linked above does not have the double - before the dkms flag. Use this below

    ./NVIDIA-Linux-x86_64-340.65.run --dkms -z

    You don't touch the xorg.conf file at all. You don't need it and generating one under NVIDIA will break your install.

    While I'm a huge fan of blackmoreops and his guides, you should not just follow them if you don't know what they are doing.

    For example, his guide on NVIDIA is not for optimus platforms and it will break your install.

    The easiest way would be to do a fresh install (as I don't know what you have done to your system) and then follow my guide from the start.

    It would also be good to see the log here:

    /var/lib/dkms/nvidia/340.65/build/make.log
    chown -R us ./base

  35. #135
    Join Date
    2014-Dec
    Posts
    5
    Staticn0de thank you so much for you help with this. I think I may have a couple of python type errors going on as well, I will post the code from those later. I was impatient waiting for the moderators to post my thread and may have broken other "stuff" before I saw your reply. I think have answered and posted correctly below your requests, for some reason I am getting a security alert when I try to preview this so I am posing it as is.

    This security site has been blocking me from posting here for the last two day...***
    https://forums.kali.org/newreply.php...treply&t=21956
    https://sucuri.net/




    Quote Originally Posted by staticn0de View Post
    First things first, clean up the NIVIDA drivers already installed. I've added sudo for if you are a regular user

    sudo ./NVIDIA-Linux-x86_64-340.65.run --uninstall
    Done...uninstall appeared to work.

    This was reran with --dkms -z (the installation failed)
    Quote Originally Posted by staticn0de View Post
    The command you linked above does not have the double - before the dkms flag. Use this below
    ./NVIDIA-Linux-x86_64-340.65.run --dkms -z
    Before removal
    Code:
    user@gabrielle:/var/lib/dkms/nvidia/340.65/build$ cat make.log
    DKMS make.log for nvidia-340.65 for kernel 3.14-kali1-amd64 (x86_64)
    Wed Dec 31 10:47:09 MST 2014
    
    gcc-version-check failed:
    
    The compiler used to compile the kernel (gcc
    4.7) does not exactly match the current compiler
    (gcc 4.9).  The Linux 2.6 kernel module loader
    rejects kernel modules built with a version of gcc
    that does not exactly match that of the compiler
    used to build the running kernel.
    
    If you know what you are doing and want to override
    the gcc version check, you can do so by setting the
    IGNORE_CC_MISMATCH environment variable to "1".
    
    In any other case, set the CC environment variable
    to the name of the compiler that was used to compile
    the kernel.
    
    *** Failed CC version check. Bailing out! ***
    
    make: *** [build-sanity-checks] Error 1
    make: Entering directory `/var/lib/dkms/nvidia/340.65/build/uvm'
    cd ./..; make module SYSSRC=/lib/modules/3.14-kali1-amd64/source SYSOUT=/lib/modules/3.14-kali1-amd64/build KBUILD_EXTMOD=./..
    make[1]: Entering directory `/var/lib/dkms/nvidia/340.65/build'
    NVIDIA: calling KBUILD...
    make[2]: Entering directory `/usr/src/linux-headers-3.14-kali1-common'
    make -C /lib/modules/3.14-kali1-amd64/build \
        KBUILD_SRC=/usr/src/linux-headers-3.14-kali1-common \
        KBUILD_EXTMOD="./.." -f /usr/src/linux-headers-3.14-kali1-common/Makefile \
        modules
    test -e include/generated/autoconf.h -a -e include/config/auto.conf || (        \
        echo >&2;                            \
        echo >&2 "  ERROR: Kernel configuration is invalid.";        \
        echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
        echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";    \
        echo >&2 ;                            \
        /bin/false)
    mkdir -p ./../.tmp_versions ; rm -f ./../.tmp_versions/*
    make -f /usr/src/linux-headers-3.14-kali1-common/scripts/Makefile.build obj=./..
    /usr/src/linux-headers-3.14-kali1-common/scripts/Makefile.build:44: /usr/src/linux-headers-3.14-kali1-common/./../Makefile: No such file or directory
    make[4]: *** No rule to make target `/usr/src/linux-headers-3.14-kali1-common/./../Makefile'.  Stop.
    make[3]: *** [_module_./..] Error 2
    make[2]: *** [sub-make] Error 2
    make[2]: Leaving directory `/usr/src/linux-headers-3.14-kali1-common'
    NVIDIA: left KBUILD.
    nvidia.ko failed to build!
    make[1]: *** [nvidia.ko] Error 1
    make[1]: Leaving directory `/var/lib/dkms/nvidia/340.65/build'
    make: *** [../Module.symvers] Error 2
    make: Leaving directory `/var/lib/dkms/nvidia/340.65/build/uvm'
    user@gabrielle:/var/lib/dkms/nvidia/340.65/build$
    after...the ./NVIDIA install failed

    Code:
    root@gabrielle:/var/lib/dkms/nvidia/340.65/build# cat make.log
    DKMS make.log for nvidia-340.65 for kernel 3.14-kali1-amd64 (x86_64)
    Thu Jan  1 12:28:45 MST 2015
    
    gcc-version-check failed:
    
    The compiler used to compile the kernel (gcc
    4.7) does not exactly match the current compiler
    (gcc 4.9).  The Linux 2.6 kernel module loader
    rejects kernel modules built with a version of gcc
    that does not exactly match that of the compiler
    used to build the running kernel.
    
    If you know what you are doing and want to override
    the gcc version check, you can do so by setting the
    IGNORE_CC_MISMATCH environment variable to "1".
    
    In any other case, set the CC environment variable
    to the name of the compiler that was used to compile
    the kernel.
    
    *** Failed CC version check. Bailing out! ***
    
    make: *** [build-sanity-checks] Error 1
    make: Entering directory `/var/lib/dkms/nvidia/340.65/build/uvm'
    cd ./..; make module SYSSRC=/lib/modules/3.14-kali1-amd64/source SYSOUT=/lib/modules/3.14-kali1-amd64/build KBUILD_EXTMOD=./..
    make[1]: Entering directory `/var/lib/dkms/nvidia/340.65/build'
    NVIDIA: calling KBUILD...
    make[2]: Entering directory `/usr/src/linux-headers-3.14-kali1-common'
    make -C /lib/modules/3.14-kali1-amd64/build \
        KBUILD_SRC=/usr/src/linux-headers-3.14-kali1-common \
        KBUILD_EXTMOD="./.." -f /usr/src/linux-headers-3.14-kali1-common/Makefile \
        modules
    test -e include/generated/autoconf.h -a -e include/config/auto.conf || (        \
        echo >&2;                            \
        echo >&2 "  ERROR: Kernel configuration is invalid.";        \
        echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
        echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";    \
        echo >&2 ;                            \
        /bin/false)
    mkdir -p ./../.tmp_versions ; rm -f ./../.tmp_versions/*
    make -f /usr/src/linux-headers-3.14-kali1-common/scripts/Makefile.build obj=./..
    /usr/src/linux-headers-3.14-kali1-common/scripts/Makefile.build:44: /usr/src/linux-headers-3.14-kali1-common/./../Makefile: No such file or directory
    make[4]: *** No rule to make target `/usr/src/linux-headers-3.14-kali1-common/./../Makefile'.  Stop.
    make[3]: *** [_module_./..] Error 2
    make[2]: *** [sub-make] Error 2
    make[2]: Leaving directory `/usr/src/linux-headers-3.14-kali1-common'
    NVIDIA: left KBUILD.
    nvidia.ko failed to build!
    make[1]: *** [nvidia.ko] Error 1
    make[1]: Leaving directory `/var/lib/dkms/nvidia/340.65/build'
    make: *** [../Module.symvers] Error 2
    make: Leaving directory `/var/lib/dkms/nvidia/340.65/build/uvm'
    root@gabrielle:/var/lib/dkms/nvidia/340.65/build#

  36. #136
    Join Date
    2014-Dec
    Posts
    5

    Just a test

    I know this post has nothing to do with this thread, and for that I apologize in advance.

    This is just a test
    HTML Code:
    https://securi.net
    website has been blocking my access to advanced post and "preview post" options, I tested this from three different locations on two difference pc's. The only time I did not get blocked was when I chose the "quick reply" option.

    I am now connecting through tor browser and it appears to be working accept I have been asked to log in multiple times.

  37. #137
    Join Date
    2014-Dec
    Posts
    5

    NVIDIA will not install correctly

    Staticn0de...again many thanks. I do NOT have python errors anymore, infact I just rebuilt this Kali install, 3x. I had a backup file which I used, but that failed. Anyway post 25 was followed exactly, after a clean install.

    As you can see I am still having issues, and the NVIDIA drivers failed to install.


    Edit xorg.conf.nvidia and add a line under the 'Section "Device"' area so that is matches what is shown below. Change the bus ID to match what you recorded previously and take note that you recored a . before the last number and it is now a ':'. You need the ':'.
    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BusID "PCI:03:00:0"
    Above directions were not compete...file xorg.conf.nvidia does not exist, see below code.

    Code:
    root@Debian:/var/lib/dkms/nvidia/340.65/build# locate xorg.conf.
    /usr/share/X11/xorg.conf.d
    /usr/share/X11/xorg.conf.d/10-evdev.conf
    /usr/share/X11/xorg.conf.d/50-synaptics.conf
    /usr/share/X11/xorg.conf.d/50-vmmouse.conf
    /usr/share/X11/xorg.conf.d/50-wacom.conf
    /usr/share/man/man5/xorg.conf.5.gz
    /usr/share/man/man5/xorg.conf.d.5.gz
    It would also be good to see the log here:

    /var/lib/dkms/nvidia/340.65/build/make.log
    The above requested file does not exist, see below.

    Code:
    root@Debian:/var/lib/dkms/nvidia/340.65/build# ls
    conftest.sh          Makefile     nv-dma.c       nv_gpu_ops.h  nvidia-modules-common.mk  nv-misc.h  nv-procfs.c   nv_uvm_interface.c  os-interface.h  os-usermap.c
    cpuopsys.h           nv-acpi.c    nv-drm.c       nvgputypes.h  nv-kernel.o               nv-mmap.c  nv-proto.h    nv_uvm_interface.h  os-mlock.c      rmil.h
    dkms.conf            nv.c         nverror.h      nv-gvi.c      nv-linux.h                nv-p2p.c   nv-reg.h      nv-vm.c             os-pci.c        rmretval.h
    gcc-version-check.c  nv-chrdev.c  nv-frontend.c  nv.h          nv-memdbg.h               nv-p2p.h   nvtypes.h     nv-vtophys.c        os-registry.c   uvm
    g_nvreadme.h         nv-cray.c    nv-frontend.h  nv-i2c.c      nv-mempool.c              nv-pat.c   nv-usermap.c  os-interface.c      os-smp.c        xapi-sdk.h
    root@Debian:/var/lib/dkms/nvidia/340.65/build#
    I do have this file...
    Code:
    root@Debian:/usr/share/doc/NVIDIA_GLX-1.0# cat README.txt
    The above file had too many characters to post.

    I use Kali is my primary OS, bad practice I know, but I use it with work constantly. I hope that my installing additional applications doesn't impair our working on my NVIDIA graphics driver. As you can see I am still in need of some assistance. Please let me know what files or data I can post that will help this along.


    Vr/

  38. #138
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    @Hun75m4n,

    Nothing wrong with using Kali as the primary OS.

    Installing other applications is not normally the problem. Its all about how much you install from non-official repos as they will break you install very quickly.

    Now, the file you are after is found in the bumblebee directory

    Code:
    root@kali /etc/bumblebee$ ls                                                   
    bumblebee.conf  xorg.conf.d  xorg.conf.nouveau  xorg.conf.nvidia
    The two files you modify as part of my guide are bumbelbee.conf and xorg.conf.nvidia.

    If you don't have this folder, you have not installed bumblebee yet. You need to add the debian repo listed in the guide and run apt-get update and then install bumblebee.

    Now you have the correct file, keep following the guide and make the modifications listend. If you still can't get it to work, let me know.
    chown -R us ./base

  39. #139
    Join Date
    2014-Dec
    Posts
    5

    NVIDIA will not install correctly

    @staticn0de

    Thanks for pointing out the files, apprantly I don't know how to use the command 'locate'.
    I have completed the install now, without error. I guess maybe I am not in the know for how NVIDIA Gforce is used. Under Applications -> System Tools -> Preferences -> NVIDIA X server settings I have the below error.

    Code:
    You do not appear to be using the NVIDIA X driver.  Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
    Applications -> System Tools -> Preferences -> Systems Settings -> Details -> Graphics (there is no driver listed and Experience states "Fallback)

    Applications -> Programming -> Nvidia Visual Profiler (not sure what this is all about, it appears to be a web page)

    I guess I am confused as to what getting the NVIDIA drivers installed correctly was supposed to accomplish.

  40. #140
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Hun75m4n View Post
    @staticn0de

    Thanks for pointing out the files, apprantly I don't know how to use the command 'locate'.
    I have completed the install now, without error. I guess maybe I am not in the know for how NVIDIA Gforce is used. Under Applications -> System Tools -> Preferences -> NVIDIA X server settings I have the below error.

    Code:
    You do not appear to be using the NVIDIA X driver.  Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
    Applications -> System Tools -> Preferences -> Systems Settings -> Details -> Graphics (there is no driver listed and Experience states "Fallback)

    Applications -> Programming -> Nvidia Visual Profiler (not sure what this is all about, it appears to be a web page)

    I guess I am confused as to what getting the NVIDIA drivers installed correctly was supposed to accomplish.
    The reason it is giving you an NVIDIA X driver error is because it's not loaded (the driver) unless you call it with optirun. This is a power saving feature and the entire reason we install bumblebee.

    try the command below:

    Code:
     
    optirun glxspheres64
    You should see a pretty window appear and terminal will be printing some FPS for you. That means the driver install worked.

    If you want to use the NVIDIA card (such as in a graphics demanding application), prefix the command with optirun.

    Say I wanted to run cudahashcat i would use the command

    Code:
     
    optirun cudahashcat
    chown -R us ./base

  41. #141
    Join Date
    2015-Jan
    Posts
    6

    Bumblebee install errors

    Hi everyone. Please help. I followed the guide from post 25 step by step till Cuda install, everything works well, no error but when i try to see if it works what have I done with optirun glxspheres64, i got 2 errors

    [ 1465.806859] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.

    [ 1465.806942] [ERROR]Aborting because fallback start is disabled.

    and for primusrun glxgears
    Xlib: extension "GLX" missing on display ":0.0".
    Error: couldn't get an RGB, Double-buffered visual

    In xorg.conf.nvidia I have:

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

    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BusID "PCI:01:00.0"
    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
    EndSection

    in bumblebee.conf i changed only line 22 "Driver=nvidia"

    lspci | grep 3D comand give me as a result 01:00.0 3D controller: NVIDIA Corporation Device 1292 (rev a1)

    I use Nvidia 740M in an asus laptop, I just installed kali and updated&upgraded without any error after I tried to install from first post and I got
    root@kali:~# modprobe nvidia-uvm
    ERROR: could not insert 'nvidia_uvm': No such device but optirun glxspheres64 it worked that time.
    but that time i installed and uninstalled too many times and I haven't any ideea how to solve and it was too much mess around.
    Any help appreciated. Thank you in advance

  42. #142
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    and the award for Most Helpful Topic of 2014 goes to... staticn0de!



    Thanks for all the help mate!
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  43. #143
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    and the award for Most Helpful Topic of 2014 goes to... staticn0de!



    Thanks for all the help mate!
    Shucks mate, you will make me blush.
    chown -R us ./base

  44. #144
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    seriously they have not wrapped up a cudahashcat package yet http://git.kali.org/gitweb/?a=project_list;pf=packages , so many thanks for that .deb and this howto bro. I'd still be without my nVidia under linux without this tut. We(nVidia users) all appreciate that guide you've created here. Not that many have the knowledge and willing to help.

    Cheers static!
    Last edited by Quest; 2015-01-04 at 02:54.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  45. #145
    Join Date
    2013-Mar
    Posts
    10
    excellent stuff

  46. #146
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    You actually reminded me that I have been meaning to repackage the new cudahashcat 1.31. So, I went and did that. I've also changed the host because mirror creator is awful and should feel awful.

    Install with:
    Code:
    dpkg -i cudahashcat-1.31.deb
    In the future, if you want to remove it:
    Code:
    dpkg -r cudahashcat-1.31
    If you want to make sure its completely removed, check the following and remove them:
    Code:
    /usr/bin/cudahashcat32
    /usr/bin/cudahashcat64
    /usr/share/cudahashcat
    If you need to remove my old deb, run the following. Check the listings in the code block above to make sure they were removed:
    Code:
    dpkg -r cudahashcat-1.30
    Sums for cudahashcat-1.31.deb:
    Code:
    md5sum = b753c393264b3c40e51f057a96f3f6e9 
    sha1sum = f4abc533f4ced0f7e9a82255ceecf0333c212fa2
    When installed, test with the following:
    Code:
    optirun cudahashcat64 -t 32 -a 7 example0.hash ?a?a?a?a example.dict
    The file is 475MB
    https://mega.co.nz/#!kFMC2RQC!D1ccQY...KFFxs7Qj1pgcw0
    chown -R us ./base

  47. #147
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    @2code

    Edit xorg.conf.nvidia and adjust the line:

    BusID "PCI:01:00.0"

    To read

    BusID "PCI:01:00:0"

    And restart bumblebeed

  48. #148
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    I really like MEGA over mirror creator. Thx for that new cudahashcat 1.31 deb!

    I will wait for KL 1.1.0 to install it, as will have to reinstall everything when it comes out. Tomorrow(5) me thinks.

    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  49. #149
    Join Date
    2015-Jan
    Posts
    6
    Thank you very much staticn0de, your advice took me in the right direction and I ran optirun glxspheres64 whitout problems. But I got another error after I've installed cuda_6.0.37_linux_64 when i have run ./deviceQuery, i got
    ERROR: could not insert 'nvidia': No such device
    cudaGetDeviceCount returned 38
    -> no CUDA-capable device is detected
    Result = FAIL

    modinfo nvidia filename: /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias: char-major-195-*
    version: 340.65
    supported: external
    license: NVIDIA
    alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
    alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
    alias: pci:v000010DEd*sv*sd*bc03sc02i00*
    alias: pci:v000010DEd*sv*sd*bc03sc00i00*
    depends: drm,i2c-core
    vermagic: 3.14-kali1-amd64 SMP mod_unload modversions
    parm: NVreg_Mobile:int
    parm: NVreg_ResmanDebugLevel:int
    parm: NVreg_RmLogonRC:int
    ...

    Must I downgrade to an old nvidia driver version(340.24) or to upgrade cuda or a clean install again ?

    modinfo nvidia-current | grep version ERROR: Module nvidia-current not found.
    nvidia-smi -a ERROR: could not insert 'nvidia': No such device
    NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
    lspci | egrep 'VGA|3D' 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    01:00.0 3D controller: NVIDIA Corporation Device 1292 (rev ff)

    I read on a forum that is possible to have a version mismatch between installed nvidia kernel module and libcuda1 library but I don't know if is the case and how to solve it.

    Thank you for help.

  50. #150
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by 2Code View Post
    Thank you very much staticn0de, your advice took me in the right direction and I ran optirun glxspheres64 whitout problems. But I got another error after I've installed cuda_6.0.37_linux_64 when i have run ./deviceQuery, i got
    ERROR: could not insert 'nvidia': No such device
    cudaGetDeviceCount returned 38
    -> no CUDA-capable device is detected
    Result = FAIL

    modinfo nvidia filename: /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias: char-major-195-*
    version: 340.65
    supported: external
    license: NVIDIA
    alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
    alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
    alias: pci:v000010DEd*sv*sd*bc03sc02i00*
    alias: pci:v000010DEd*sv*sd*bc03sc00i00*
    depends: drm,i2c-core
    vermagic: 3.14-kali1-amd64 SMP mod_unload modversions
    parm: NVreg_Mobile:int
    parm: NVreg_ResmanDebugLevel:int
    parm: NVreg_RmLogonRC:int
    ...

    Must I downgrade to an old nvidia driver version(340.24) or to upgrade cuda or a clean install again ?

    modinfo nvidia-current | grep version ERROR: Module nvidia-current not found.
    nvidia-smi -a ERROR: could not insert 'nvidia': No such device
    NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
    lspci | egrep 'VGA|3D' 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    01:00.0 3D controller: NVIDIA Corporation Device 1292 (rev ff)

    I read on a forum that is possible to have a version mismatch between installed nvidia kernel module and libcuda1 library but I don't know if is the case and how to solve it.

    Thank you for help.
    After you run ./deviceQuery, capture the tail of the dmesg command and post it here

    Edit: did you run optirun. /deviceQuery or just

    ./deviceQuery?

    It needs the optirun prefix
    Last edited by staticn0de; 2015-01-07 at 04:58.
    chown -R us ./base

Similar Threads

  1. Replies: 6
    Last Post: 2017-01-04, 19:39
  2. NVIDIA and CUDA with OPTIMUS
    By jolubedju in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2014-06-03, 10:52
  3. Kali Linux 1.05 nvidia optimus cuda and pyrit
    By gfbaggio in forum TroubleShooting Archive
    Replies: 3
    Last Post: 2014-04-28, 20:15

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •