Page 2 of 8 FirstFirst 12345678 LastLast
Results 51 to 100 of 376

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

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    2014-Jul
    Posts
    5
    Hi staticn0de and all,

    I have problems with bumblebee, my gear is: Lenovo thinkpad T440p with geforce 730m card.

    My source.list file:

    ## Regular Updates
    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 Updates
    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

    ## Bumblebee
    #deb http://ftp.debian.org/debian wheezy-blackports main contrib non-free

    The last entry is commented out I'm deleting the comment before installing bumblebee primus and apt-get update

    With above configuration of source list I have an error while apt-get update && apt-get upgrade -y && apt-get dist-update -y:

    Errors were encountered while processing:
    Linux-image-3.14-kali1-amd64
    extlinux
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    After Configuring bumblebee.conf and xorg.conf.nvidia and restarting bumblebeed service which fails I did /etc/init.d/gdm3 stop and i receive the following error:

    bash: /etc/init.d/gdm3: cannot execute binary file

    I need to hard restart the laptop and after this me kali installation totally breaks. I have an error while booting:

    The root filesystem is currently mounted in read-only mode. A maintenece will now be started. After performing system maintenance, press Ctrl+D to terminate the maintenance shell and restart the system...

    If You need more additional info on the behavior or configuration files please let me know.
    If you have any ideas whats wrong Please let me know

  2. #2
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by johnnyinc View Post
    Hi staticn0de and all,

    I have problems with bumblebee, my gear is: Lenovo thinkpad T440p with geforce 730m card.

    My source.list file:

    ## Regular Updates
    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 Updates
    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

    ## Bumblebee
    #deb http://ftp.debian.org/debian wheezy-blackports main contrib non-free

    The last entry is commented out I'm deleting the comment before installing bumblebee primus and apt-get update

    With above configuration of source list I have an error while apt-get update && apt-get upgrade -y && apt-get dist-update -y:

    Errors were encountered while processing:
    Linux-image-3.14-kali1-amd64
    extlinux
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    After Configuring bumblebee.conf and xorg.conf.nvidia and restarting bumblebeed service which fails I did /etc/init.d/gdm3 stop and i receive the following error:

    bash: /etc/init.d/gdm3: cannot execute binary file

    I need to hard restart the laptop and after this me kali installation totally breaks. I have an error while booting:

    The root filesystem is currently mounted in read-only mode. A maintenece will now be started. After performing system maintenance, press Ctrl+D to terminate the maintenance shell and restart the system...

    If You need more additional info on the behavior or configuration files please let me know.
    If you have any ideas whats wrong Please let me know
    Edit Again: After all that is below, I did reinstall the packages autoremove removed with the exception of libplrpc-perl as it was not in the repo.
    Code:
    apt-get install libnet-daemon-perl memtest86+ syslinux-themes-debian syslinux-themes-debian-wheezy
    Everything works with the exception of memtest86 (but that is a known bug as I am EFI booting)

    Edit:

    Ok, so I an update (see next post) and had the same error. It's not related to bumblebee or nvidia (it's a repo issue)

    Boot into Kali recovery mode and run:
    Code:
    apt-get autoremove
    After that, reboot. Should be back in Kali.

    Run
    Code:
    apt-get update && apt-get upgrade
    and you should have no more errors.

    The following are the packages which were removed under my apt-get autoremove. I have not tried reinstalling them yet.
    Code:
    libnet-daemon-perl libplrpc-perl memtest86+ syslinux-themes-debian syslinux-themes-debian-wheezy
    From looking at the packages which were updated just before all this happened, I'd hazard a guess and say updating either of the following caused the broken package
    Code:
    syslinux or syslinux-common
    Last edited by staticn0de; 2014-07-20 at 04:56.

  3. #3
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Edit: Sorted in previous post


    I just ran an apt-get upgrade and received the same:

    Setting up syslinux-common (3:6.03~pre1+dfsg-1kali3) ...
    Setting up syslinux (3:6.03~pre1+dfsg-1kali3) ...
    Setting up extlinux (3:6.03~pre1+dfsg-1kali3) ...
    P: Checking for EXTLINUX directory... found.
    /boot/vmlinuz-3.14-kali1-amd64
    P: Writing config for /boot/vmlinuz-3.14-kali1-amd64...
    P: Updating /boot/extlinux/linux.cfg...
    I: os-proper disabled in /etc/default/extlinux: Skipping /boot/extlinux/os-proper.cfg
    E: /usr/share/EXTLINUX/themes/debian: No such file or directory
    dpkg: error processing extlinux (--configure):
    subprocess installed post-installation script returned error exit status 1

    Errors were encountered while processing:
    extlinux
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    Seems like the repo has bad packages
    Last edited by staticn0de; 2014-07-20 at 04:43.

  4. #4
    Join Date
    2014-Jul
    Posts
    5
    Thank You staticn0de

    apt-get autoremove cleared the issue but it still not resolve the bumblebee problem. I have now the following problems:

    After stoping gdm3 I receive the following error messages non stop:
    [ 835.063840] ata6.00: status: { DRDY }
    [ 835.638286] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    [ 835.736372] ata6.00: irq_stat 0x40000001
    [ 835.762738] ata6.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 30
    [ 835.638286] res 50/00:03:00:12:00/00:00:00:00:00/a0 Emask 0x1 (device error)
    [ 837.036379] ata6.00: status: { DRDY }
    And so on and so on

    I have rebooted the laptop and install nVidia driver in recovery mode after install and reboot i have issued the command: optirun glxspheres64 and receive the following error:
    [ 42.235078] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
    [ 42.235176] [ERROR]Aborting because fallback start is disabled

    Do You have any ideas whats the case ?
    Thank You so much for Your help.

  5. #5
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by johnnyinc View Post
    Thank You staticn0de

    apt-get autoremove cleared the issue but it still not resolve the bumblebee problem. I have now the following problems:

    After stoping gdm3 I receive the following error messages non stop:
    [ 835.063840] ata6.00: status: { DRDY }
    [ 835.638286] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    [ 835.736372] ata6.00: irq_stat 0x40000001
    [ 835.762738] ata6.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 30
    [ 835.638286] res 50/00:03:00:12:00/00:00:00:00:00/a0 Emask 0x1 (device error)
    [ 837.036379] ata6.00: status: { DRDY }
    And so on and so on

    I have rebooted the laptop and install nVidia driver in recovery mode after install and reboot i have issued the command: optirun glxspheres64 and receive the following error:
    [ 42.235078] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
    [ 42.235176] [ERROR]Aborting because fallback start is disabled

    Do You have any ideas whats the case ?
    Thank You so much for Your help.
    Few things,

    That may be a hard drive error. Check your hard drive smart stats and run a test.

    Otherwise, did bumblebee install correctly?

    I'll need some information. Post the results of the following commands

    Code:
    uname -r
    Code:
    cat /etc/modprobe.d/bumblebee.conf
    Run optirun glxspheres64 and then run
    Code:
    dmesg
    Code:
    lspci | egrep 'VGA|3D'
    What version of Kali are you using?

    Are you 32bit or 64bit?

    The important part is you have this in your /etc/modprobe.d/bumblebee.conf file

    blacklist nouveau
    Last edited by staticn0de; 2014-07-23 at 10:41.

  6. #6
    Hey n0de, thanks for this write up! There's one problem I'm experiencing:

    The drivers are correctly installed when I check 'modinfo nvidia', but when I run the command 'optirun glxspheres64' I get the error:

    Code:
    [ 2037.152986] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    
    [ 2037.153044] [ERROR]Aborting because fallback start is disabled.
    When I check lspci | egrep "VGA|3D" it comes back as a 3D controller, not VGA. Not sure if that matters when configuring /etc/bumblebee/xorg.conf.nvidia

    Also, I noticed in your updated post you didn't include

    Quote Originally Posted by staticn0de View Post
    Now install the nvidia drivers
    apt-get install nvidia-glx
    Are there not certain dependencies needed from this? Cause even when I run glxspheres64 I get

    Code:
    Polygons in scene: 62464
    Xlib:  extension "GLX" missing on display ":0.0".
    ERROR (603): Could not obtain RGB visual with requested properties
    Thanks again!! I'm looking forward to finally getting my video card recognized.

  7. #7
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Rarity View Post
    Hey n0de, thanks for this write up! There's one problem I'm experiencing:

    The drivers are correctly installed when I check 'modinfo nvidia', but when I run the command 'optirun glxspheres64' I get the error:

    Code:
    [ 2037.152986] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    
    [ 2037.153044] [ERROR]Aborting because fallback start is disabled.
    When I check lspci | egrep "VGA|3D" it comes back as a 3D controller, not VGA. Not sure if that matters when configuring /etc/bumblebee/xorg.conf.nvidia

    Also, I noticed in your updated post you didn't include



    Are there not certain dependencies needed from this? Cause even when I run glxspheres64 I get

    Code:
    Polygons in scene: 62464
    Xlib:  extension "GLX" missing on display ":0.0".
    ERROR (603): Could not obtain RGB visual with requested properties
    Thanks again!! I'm looking forward to finally getting my video card recognized.
    Hey there,

    nvidia-glx is not required for the second install. This is a transitional package to install the older drivers.

    That being said, i'm going to need a lot more information from you to help.

    use the [CODE] brackets to paste the output of commands (the code close bracket is a [*/CODE] without the *. Put all the text between them.

    run optirun glxspheres64 and then paste the output of the command below. The last 30 lines or so.
    Code:
    dmesg
    Paste your /etc/bumblebee/bumblebee.conf

    Paste your /etc/bumblebee/xorg.nvidia.conf

    Paste the output of
    Code:
    lspci | egrep 'VGA|3D'
    Paste the output of
    Code:
    modinfo nvidia
    and

    Code:
    modinfo nvidia-uvm
    and

    Code:
    echo $PATH
    Paste the output of
    Code:
    find 2> /dev/null / -name nvidia*.ko
    That should do for a start
    Last edited by staticn0de; 2014-07-25 at 09:51.

  8. #8
    Quote Originally Posted by staticn0de View Post
    Hey there,

    nvidia-glx is not required for the second install. This is a transitional package to install the older drivers.

    That being said, i'm going to need a lot more information from you to help.

    -snip-

    That should do for a start
    Okay, here we go! About time, right? Lol.

    dmesg after running optirun glxspheres64:
    Code:
    [  239.050292] nvidia: module license 'NVIDIA' taints kernel.
    [  239.050298] Disabling lock debugging due to kernel taint
    [  239.620698] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
    [  239.620969] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
    [  239.620973] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.32  Tue Aug  5 20:58:26 PDT 2014
    [  303.632166] vgaarb: this pci device is not a vga device
    [  303.633346] nvidia 0000:01:00.0: irq 54 for MSI/MSI-X
    [  303.646647] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.646790] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.646873] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.646950] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.647024] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.647098] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.647214] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  303.647290] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  309.149085] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  309.150859] NVRM: RmInitAdapter failed! (0x24:0x38:1170)
    [  309.150873] NVRM: rm_init_adapter failed for device bearing minor number 0
    [  309.150909] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5
    /etc/bumblebee/bumblebee.conf

    Code:
    # 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
    /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"
    
    #   If the X server does not automatically detect your VGA device,
    #   you can manually set it here.
    #   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
    #   as you see in the commented example.
    #   This Setting may be needed in some platforms with more than one
    #   nvidia card, which may confuse the proprietary driver (e.g.,
    #   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
    #   BusID "PCI:01:00:0"
    
    #   Setting ProbeAllGpus to false prevents the new proprietary driver
    #   instance spawned to try to control the integrated graphics card,
    #   which is already being managed outside bumblebee.
    #   This option doesn't hurt and it is required on platforms running
    #   more than one nvidia graphics card with the proprietary driver.
    #   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
    #   If this option is not set, the new Xorg may blacken the screen and
    #   render it unusable (unless you have some way to run killall Xorg).
        Option "ProbeAllGpus" "false"
    
        Option "NoLogo" "true"
        Option "UseEDID" "false"
        Option "UseDisplayDevice" "none"
    EndSection
    lspci | egrep 'VGA|3D'
    Code:
    00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06)
    01:00.0 3D controller: NVIDIA Corporation Device 0fe4 (rev a1)
    modinfo nvidia
    Code:
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.32
    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:
    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
    echo $PATH
    Code:
    /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin:/usr/local/cuda-6.5/bin
    find 2> /dev/null / -name nvidia*.ko
    Code:
    /var/lib/dkms/nvidia/340.32/3.14-kali1-amd64/x86_64/module/nvidia.ko
    /var/lib/dkms/nvidia/340.32/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

  9. #9
    Thanks for the quick reply, but I won't be able to respond until later tonight. I'll edit this once I can.

  10. #10
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Hi staticn0de!

    so everything was working fine, but then when I tried to use cowpatty/pyrit/crunch with FrankenScript, I get an error..
    "ERROR: could not insert 'nvidia': No such device"

    So then I ran some tests, and I cannot run optirun glxspheres64 anymore!? Here are the outputs...
    Code:
    root@kali:~# optirun glxspheres64
    [ 3086.847274] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
    
    [ 3086.847338] [ERROR]Aborting because fallback start is disabled.
    root@kali:~# dmesg
    [    0.000000] Initializing cgroup subsys cpuset
    [    0.000000] Initializing cgroup subsys cpu
    [    0.000000] Initializing cgroup subsys cpuacct
    [    0.000000] Linux version 3.14-kali1-amd64 ([email protected]) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.14.5-1kali1 (2014-06-07)
    [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.14-kali1-amd64 root=UUID=df2555ed-577b-46d4-b82c-bae880f39864 ro quiet
    [    0.000000] e820: BIOS-provided physical RAM map:
    [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    SNIP
    [ 2809.151223]  [<ffffffff814efb08>] ? page_fault+0x28/0x30
    [ 2809.151228]  [<ffffffff810d81e1>] ? SyS_init_module+0xb1/0xe0
    [ 2809.151234]  [<ffffffff814f7879>] ? system_call_fastpath+0x16/0x1b
    [ 2809.151237] ---[ end trace a26dc4680320df79 ]---
    [ 2809.151431] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
    [ 2809.151474] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
    [ 2809.151474] NVRM: installed in this system is not supported by the 340.24
    [ 2809.151474] NVRM: NVIDIA Linux driver release.  Please see 'Appendix
    [ 2809.151474] NVRM: A - Supported NVIDIA GPU Products' in this release's
    [ 2809.151474] NVRM: README, available on the Linux driver download page
    [ 2809.151474] NVRM: at www.nvidia.com.
    [ 2809.151553] nvidia: probe of 0000:01:00.0 failed with error -1
    [ 2809.151961] NVRM: The NVIDIA probe routine failed for 1 device(s).
    [ 2809.151964] NVRM: None of the NVIDIA graphics adapters were initialized!
    [ 2809.151966] [drm] Module unloaded
    [ 2809.152095] NVRM: NVIDIA init module failed!
    [ 3085.254654] ------------[ cut here ]------------
    [ 3085.254666] WARNING: CPU: 4 PID: 6853 at /build/kalibuild-linux_3.14.5-1kali2-amd64-igeTGG/linux-3.14.5/fs/proc/generic.c:315 proc_register+0xd8/0x170()
    [ 3085.254669] proc_dir_entry 'driver/nvidia' already registered
    [ 3085.254670] Modules linked in: nvidia(PO+) nls_utf8 nls_cp437 vfat fat ctr ccm nfnetlink_log nfnetlink bbswitch(O) binfmt_misc loop 
    SNIP
    [ 3085.254767] CPU: 4 PID: 6853 Comm: modprobe Tainted: P        W  O 3.14-kali1-amd64 #1 Debian 3.14.5-1kali1
    [ 3085.254769] Hardware name: TOSHIBA Satellite P850/QFKAA, BIOS 1.90 08/21/2012
    [ 3085.254771]  0000000000000000 0000000000000009 ffffffff814e9b1e ffff8802235afbe8
    [ 3085.254776]  ffffffff810639d6 ffff880224ed9680 ffff8802230a2175 ffff8802230a2100
    [ 3085.254780]  ffff880226501b80 0000000000000000 ffffffff81063ab5 ffffffff81718cc0
    [ 3085.254784] Call Trace:
    [ 3085.254795]  [<ffffffff814e9b1e>] ? dump_stack+0x41/0x51
    [ 3085.254802]  [<ffffffff810639d6>] ? warn_slowpath_common+0x86/0xb0
    [ 3085.254807]  [<ffffffff81063ab5>] ? warn_slowpath_fmt+0x45/0x50
    [ 3085.254813]  [<ffffffff811fe238>] ? proc_register+0xd8/0x170
    [ 3085.254819]  [<ffffffff811fe3db>] ? proc_mkdir_data+0x4b/0x70
    [ 3085.254925]  [<ffffffffa0d764f9>] ? nv_register_procfs+0x39/0x1b0 [nvidia]
    [ 3085.254994]  [<ffffffffa1c06286>] ? nvidia_init_module+0x286/0x79d [nvidia]
    [ 3085.255061]  [<ffffffffa1c067ac>] ? nv_drm_init+0xf/0xf [nvidia]
    [ 3085.255126]  [<ffffffffa1c067ac>] ? nv_drm_init+0xf/0xf [nvidia]
    [ 3085.255191]  [<ffffffffa1c0682e>] ? nvidia_frontend_init_module+0x82/0x854 [nvidia]
    [ 3085.255198]  [<ffffffff8100218a>] ? do_one_initcall+0x10a/0x160
    [ 3085.255203]  [<ffffffff81057b74>] ? set_memory_nx+0x44/0x50
    [ 3085.255210]  [<ffffffff810d7903>] ? load_module+0x1ac3/0x22f0
    [ 3085.255215]  [<ffffffff810d3d90>] ? show_initstate+0x50/0x50
    [ 3085.255221]  [<ffffffff811668b5>] ? map_vm_area+0x25/0x40
    [ 3085.255229]  [<ffffffff814efb08>] ? page_fault+0x28/0x30
    [ 3085.255234]  [<ffffffff810d81e1>] ? SyS_init_module+0xb1/0xe0
    [ 3085.255240]  [<ffffffff814f7879>] ? system_call_fastpath+0x16/0x1b
    [ 3085.255242] ---[ end trace a26dc4680320df7a ]---
    [ 3085.255404] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
    [ 3085.255442] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
    [ 3085.255442] NVRM: installed in this system is not supported by the 340.24 <---!? all tests were fine before
    [ 3085.255442] NVRM: NVIDIA Linux driver release.  Please see 'Appendix
    [ 3085.255442] NVRM: A - Supported NVIDIA GPU Products' in this release's
    [ 3085.255442] NVRM: README, available on the Linux driver download page
    [ 3085.255442] NVRM: at www.nvidia.com.
    [ 3085.255501] nvidia: probe of 0000:01:00.0 failed with error -1
    [ 3085.256058] NVRM: The NVIDIA probe routine failed for 1 device(s).
    [ 3085.256064] NVRM: None of the NVIDIA graphics adapters were initialized!
    [ 3085.256067] [drm] Module unloaded
    [ 3085.256272] NVRM: NVIDIA init module failed!
    root@kali:~# 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 GF108 [GeForce GT 630M] (rev a1)
    root@kali:~# modinfo nvidia
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.24
    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_RMEdgeIntrCheck: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@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 
    root@kali:~# echo $PATH
    /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin
    root@kali:~# find 2> /dev/null / -name nvidia*.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
    /var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia.ko
    /var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia-uvm.ko
    root@kali:~# 
    Edit:

    root@kali:~# modprobe nvidia
    ERROR: could not insert 'nvidia': No such device
    root@kali:~#
    root@kali:~# optirun pyrit benchmark
    [ 5141.410827] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

    [ 5141.410896] [ERROR]Aborting because fallback start is disabled.
    so it would appear that nothing works, when everything was working before. weird

    Edit2:

    Nevermind.
    I've reinstalled the image of my Kali installation, and all tests passed like before. A likely reason for the above problems is that I set my swapiness to 0 after the installation(?) I cannot see anything else that might have caused that.

    Now I will do tests to try to make cowpatty/pyrit/crunch work in real life...

    Edit3: Everything works, and swapiness set to 0 had nothing to do with my previous problems. So I have no idea what caused it. I'm suspecting an update(?)
    Last edited by Quest; 2014-07-28 at 18:44.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  11. #11
    Join Date
    2014-Jul
    Posts
    1
    Dude u are the best, perfect tut!!!!

    go ahead dude!

    love u!

  12. #12
    Join Date
    2014-Nov
    Posts
    15
    Please Help Someone, I am trying to install Nvidia from last few months but what ever I try It doesn't work.
    Everything goes smoth till 14th step of current tutorial on first post.

    But when I test it using:
    Code:
    ~# optirun glxspheres64
    I get this error:
    Code:
    [  126.985430] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    
    [  126.985473] [ERROR]Aborting because fallback start is disabled.
    But one thing to mention I think, when I run:
    Code:
    ~# optirun glxgears
    It gives output like:
    Code:
    9438 frames in 5.0 seconds = 1887.557 FPS
    11288 frames in 5.0 seconds = 2257.418 FPS
    10784 frames in 5.0 seconds = 2156.696 FPS
    11002 frames in 5.0 seconds = 2200.381 FPS
    10775 frames in 5.0 seconds = 2154.836 FPS
    11150 frames in 5.0 seconds = 2229.996 FPS
    10977 frames in 5.0 seconds = 2195.273 FPS
    11148 frames in 5.0 seconds = 2229.536 FPS
    11307 frames in 5.0 seconds = 2261.351 FPS
    11206 frames in 5.0 seconds = 2241.059 FPS
    10499 frames in 5.0 seconds = 2099.786 FPS
    11355 frames in 5.0 seconds = 2270.971 FPS
    11375 frames in 5.0 seconds = 2274.890 FPS
    11146 frames in 5.0 seconds = 2229.126 FPS
    11259 frames in 5.0 seconds = 2251.711 FPS
    11134 frames in 5.0 seconds = 2226.800 FPS
    Please tell me what should I do ?

    Thanks
    Kali-Linux 1.1.0a 32Bit (VM)
    kali-linux 2.0-amd64
    Lenovo Y510p
    RAM 8GB
    HDD 1TB
    GRAPHICS 2GB NVIDIA GT755M && 1GB Intel Integrated

  13. #13
    Quote Originally Posted by Rajnish357 View Post
    Please Help Someone, I am trying to install Nvidia from last few months but what ever I try It doesn't work.
    Everything goes smoth till 14th step of current tutorial on first post.

    But when I test it using:
    Code:
    ~# optirun glxspheres64
    I get this error:
    Code:
    [  126.985430] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    
    [  126.985473] [ERROR]Aborting because fallback start is disabled.
    Hi Rajnish,

    Take a look at the solution tonrin posted.

  14. #14
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    yes really, he saved me from 2months of searching/testing. Good to know that there are ppl like that outhere. Sharp contrast with the rest. "linux community" is an oxymoron.



    For those who want to install oclHashcat

    Download oclHashcat 1.01 (508Mb) to your Home folder.
    http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/

    Install oclHashcat
    Code:
    dpkg -i oclhashcat*.deb
    Test CudaHashcat(GeForce)
    Code:
    cd /usr/share/oclhashcat/ 
    
    ./cudaHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict
    Last edited by Quest; 2014-07-30 at 18:28.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  15. #15
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    yes really, he saved me from 2months of searching/testing. Good to know that there are ppl like that outhere. Sharp contrast with the rest. "linux community" is an oxymoron.



    For those who want to install oclHashcat

    Download oclHashcat 1.01 (508Mb) to your Home folder.
    http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/

    Install oclHashcat
    Code:
    dpkg -i oclhashcat*.deb
    Test CudaHashcat(GeForce)
    Code:
    cd /usr/share/oclhashcat/ 
    
    ./cudaHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict
    Hey there quest,

    oclhashcat is in the kali repos (version 1.01) so there is no need to download the .deb file.

    oclhashcat from the repo also includes the cudahashcat which is what all us nvidia users are after anyway.

    I'm currently trying to get the new hashcat working on kali but it has this habit of breaking other things when I get it to work....
    Last edited by staticn0de; 2014-07-30 at 23:02.

  16. #16
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Hi friend,

    Yes it's in the Kali repo root@kali:~# apt-get install oclhashcat but that is still 508Mb to download every time for every installation. I much prefer to get it once and keep it, otherwise it never ends.

    Speaking of. My Kali installation is now at 14Gb with all this. So this howto alone(including Kali updates) gets about 5Gb of archives if I'm not mistaken.

    Good luck with the R&D
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  17. #17
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    Hi friend,

    Yes it's in the Kali repo root@kali:~# apt-get install oclhashcat but that is still 508Mb to download every time for every installation. I much prefer to get it once and keep it, otherwise it never ends.

    Speaking of. My Kali installation is now at 14Gb with all this. So this howto alone(including Kali updates) gets about 5Gb of archives if I'm not mistaken.

    Good luck with the R&D
    If you have a computer that stays on all the time, like a media server - take a look at apt-cacher.

    It stores stuff that is downloaded from a repo locally. This way, you don't have to download it from the repo each time as it will come from your local server. A lot easier and faster than trying to mirror the repo.

  18. #18
    Used this guide and installed bumblebee and cuda with pyrit. thanks
    but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
    Cant boot into kali only windows.

  19. #19
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by nekromantik View Post
    Used this guide and installed bumblebee and cuda with pyrit. thanks
    but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
    Cant boot into kali only windows.
    Quote Originally Posted by nekromantik View Post
    Used this guide and installed bumblebee and cuda with pyrit. thanks
    but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
    Cant boot into kali only windows.
    Hi there,

    Can you press CTRL + ALT + F1 and reach a terminal?

    Is it blank screen or do you have a blinking cursor?

    That is the typical symptom for if the laptop was not restarted after installing the NVIDIA drivers (after stopping gdm3) or x-config was run. I say this because you should not have been able to install CUDA without a restart and you have said you installed everything up to pyrit and then could not restart without a blank screen.

    If you can reach terminal, run

    cd ~
    ./NVIDIA*.run --uninstall

    and then apt-get purge nvidia* bumblebee* primus*

    and restart

  20. #20
    Quote Originally Posted by staticn0de View Post
    Hi there,

    Can you press CTRL + ALT + F1 and reach a terminal?

    Is it blank screen or do you have a blinking cursor?

    That is the typical symptom for if the laptop was not restarted after installing the NVIDIA drivers (after stopping gdm3) or x-config was run. I say this because you should not have been able to install CUDA without a restart and you have said you installed everything up to pyrit and then could not restart without a blank screen.

    If you can reach terminal, run

    cd ~
    ./NVIDIA*.run --uninstall

    and then apt-get purge nvidia* bumblebee* primus*

    and restart
    Hi

    No I dont get a blinking cursor.
    So ctl alt F1 dont work.

    Can only access grub menu and edit grub parameters pressing e key.

  21. #21
    Join Date
    2014-Aug
    Posts
    2
    Hi staticn0de!
    First, thank for your guide. it helped me a lot. The result show pass.
    But i don't know is it working? I see in system setting->details: it don't show graphics driver!
    Then i tried test:
    glxinfo | grep -i "direct rendering"
    It show:
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Error: couldn't find RGB GLX visual or fbconfig
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".

    Is it problem?

  22. #22
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by nab View Post
    Hi staticn0de!
    First, thank for your guide. it helped me a lot. The result show pass.
    But i don't know is it working? I see in system setting->details: it don't show graphics driver!
    Then i tried test:
    glxinfo | grep -i "direct rendering"
    It show:
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Error: couldn't find RGB GLX visual or fbconfig
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".
    Xlib: extension "GLX" missing on display ":0.0".

    Is it problem?
    Hi there,

    Prefix your command with optirun.

    If you have a pass from the cuda device detect script the driver is working. You must prefix commands which require the driver to be loaded with optirun.

    The nvidia card is disabled during normal use to save power. Optirun enables it for the duration the program running needs it

  23. #23
    Join Date
    2014-Aug
    Posts
    2
    Quote Originally Posted by staticn0de View Post
    Hi there,

    Prefix your command with optirun.

    If you have a pass from the cuda device detect script the driver is working. You must prefix commands which require the driver to be loaded with optirun.

    The nvidia card is disabled during normal use to save power. Optirun enables it for the duration the program running needs it
    Oh, it working. thank you.
    And one more thing i can't understand. nvidia-settings require me do nvdia-xconfig. If i do , X server can't start and i have to remove xorg.conf. it like cycle! (sr my bad english)

  24. #24
    Join Date
    2014-Aug
    Location
    lotusland
    Posts
    3
    Hi static, first, thanks for taking me further along the road to installing my cuda drivers than I had thought possible, outstanding instructions. Like the fellow above me, when I run "optirun glxinfo | grep -i "direct rendering"", I get the following:

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

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


    Dual boot win7/ kali 1.08 AMD64, lenovo w530

    Bumblebee isn't starting for whatever reason. Any thoughts? Thanks.

  25. #25
    I followed latest instructions using latest Nvidia drivers but now my Nvidia card is running all the time.
    It wont switch to Intel. Also should we not be installing bumblebee-nvidia as we are now using official drivers?
    Kali boots using Intel and as soon as you use optirun or primerun it loads Nvidia and then never switches it off.
    Last edited by nekromantik; 2014-08-08 at 10:26.

  26. #26
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by nekromantik View Post
    I followed latest instructions using latest Nvidia drivers but now my Nvidia card is running all the time.
    It wont switch to Intel. Also should we not be installing bumblebee-nvidia as we are now using official drivers?
    Kali boots using Intel and as soon as you use optirun or primerun it loads Nvidia and then never switches it off.

    Please post the output of

    lsmod

    and

    cat /proc/acpi/bbswitch

    No. bumblebee-nvidia is a meta package which installs both the bumbelbee and nvidia-driver packages. The nvidia-driver package in the repo is old and not supported by many modern graphics cards. That is why the driver package is downloaded from the nvidia website.

    If you are stuck on the nvidia driver and will not swap to the power saving one, try

    service bumblebeed restart

    and

    service bumblebeed status

    Also, how do you know the driver is being loaded and not being switched off?

    For example, run

    Code:
    optirun glxspheres64
    and then run

    Code:
    glxspheres64
    Did the second command work without optirun?

  27. #27
    Join Date
    2014-Aug
    Posts
    3
    Even I am experiencing the same problem!! I am a new member to this forum and kali linux too, so forgive me if there are any mistakes.
    the second command works fine (the one without optirun)
    for me the optirun glxspheres64 returns

    [ 3224.482379] [ERROR]Cannot access secondary GPU - error: X did not start properly

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

  28. #28
    Quote Originally Posted by staticn0de View Post
    Please post the output of

    lsmod

    and

    cat /proc/acpi/bbswitch

    No. bumblebee-nvidia is a meta package which installs both the bumbelbee and nvidia-driver packages. The nvidia-driver package in the repo is old and not supported by many modern graphics cards. That is why the driver package is downloaded from the nvidia website.

    If you are stuck on the nvidia driver and will not swap to the power saving one, try

    service bumblebeed restart

    and

    service bumblebeed status

    Also, how do you know the driver is being loaded and not being switched off?

    For example, run

    Code:
    optirun glxspheres64
    and then run

    Code:
    glxspheres64
    Did the second command work without optirun?
    It seems like bbswitch was not installed by default.
    I installed it and now it switches fine.
    Thanks

  29. #29
    Join Date
    2014-Aug
    Location
    lotusland
    Posts
    3
    Hi static0de, thanks for your excellent instructional post!

    I've gotten pretty close to having functioning CUDA (i think), but running 'optirun glxinfo | grep -i "direct rendering"' gets me the following:

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

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


    dmesg gives me the following info:

    475.365641] bbswitch: enabling discrete graphics
    [ 475.612133] thinkpad_acpi: EC reports that Thermal Table has changed
    [ 475.880304] nvidia: module license 'NVIDIA' taints kernel.
    [ 475.880312] Disabling lock debugging due to kernel taint
    [ 475.893068] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=nonewns=none
    [ 475.893576] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
    [ 475.893586] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.24 Wed Jul 2 14:24:20 PDT 2014
    [ 476.103074] nvidia 0000:01:00.0: irq 48 for MSI/MSI-X
    [ 476.111216] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.111432] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.111591] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.111754] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.111917] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.112465] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.112993] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 476.113149] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 490.533192] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [ 490.559213] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    [ 490.595710] NVRM: RmInitAdapter failed! (0x25:0x28:1181)
    [ 490.595722] NVRM: rm_init_adapter failed for device bearing minor number 0
    [ 490.595746] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error


    Kernel taint! I generally only have that after a huge feeding of corn!

    I'm a complete n00b with linux, having last monkeyed with unix systems during my university days in the early 90's, before the internet had a GUI. Any help you can give me would be appreciated. If you need any further info, let me know. Thanks!

  30. #30
    Join Date
    2014-Aug
    Location
    lotusland
    Posts
    3
    I've opted to just go into my bios and disable optimus and the integrated graphics, and will install my vendor drivers and CUDA the old fashioned way - without bumbling with bumblebee. thanks for your help. if anything, this entire experience has helped me along the road that much closer to understanding the workings of debian linux.

  31. #31
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by weak_superhero View Post
    I've opted to just go into my bios and disable optimus and the integrated graphics, and will install my vendor drivers and CUDA the old fashioned way - without bumbling with bumblebee. thanks for your help. if anything, this entire experience has helped me along the road that much closer to understanding the workings of debian linux.
    Hi there,

    I'm sorry I missed your post above asking for help. If you change your mind and try and get it working again, send me a message.

  32. #32
    Join Date
    2014-Aug
    Posts
    3

    correct installed nvidia driver, but no acces to GPU (1/2)

    hello, I have a problem after installing the nvidia driver (which works apparently correct, because there is no error and 'modinfo nvidia' shows version 340.24)
    after rebooting, I use "optirun glxspheres64" but i get this error message and my fans going crazy (maximum speed):
    Code:
    optirun glxspheres64
    [ 1492.076369] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    
    [ 1492.076523] [ERROR]Aborting because fallback start is disabled.
    Maybe you could help me with this issue?
    I'll give you some information about my system:

    uname -r
    Code:
    3.14-kali1-amd64
    cat /etc/modprobe.d/bumblebee.conf
    Code:
    # installed by bumblebee-nvidia
    
    # do not automatically load nouveau as it may prevent nvidia from loading
    blacklist nouveau
    # do not automatically load nvidia as it's unloaded anyway when bumblebeed
    # starts and may fail bumblebeed to disable the card in a race condition.
    blacklist nvidia
    blacklist nvidia-current
    blacklist nvidia-current-updates
    # 304
    blacklist nvidia-304
    blacklist nvidia-304-updates
    blacklist nvidia-experimental-304
    # 310
    blacklist nvidia-310
    blacklist nvidia-310-updates
    blacklist nvidia-experimental-310
    # 313
    blacklist nvidia-313
    blacklist nvidia-313-updates
    blacklist nvidia-experimental-313
    # 319
    blacklist nvidia-319
    blacklist nvidia-319-updates
    blacklist nvidia-experimental-319
    # 325
    blacklist nvidia-325
    blacklist nvidia-325-updates
    blacklist nvidia-experimental-325
    dmesg (bbswitch can't "enable discrete graphics", maybe this is the problem?)
    Code:
    dmesg
    
    [    7.331956] Console: switching to colour frame buffer device 240x67
    [    7.340826] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
    [    7.340829] i915 0000:00:02.0: registered panic notifier
    [    7.341167] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20131218/video-1245)
    [    7.341418] ACPI: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
    [    7.341835] acpi device:38: registered as cooling_device5
    [    7.341913] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:36/LNXVIDEO:00/input/input12
    [    7.359788] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
    [    7.360290] acpi device:44: registered as cooling_device6
    [    7.360511] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input13
    [    7.360745] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [    7.361764] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
    [    7.606402] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input14
    [    7.765829] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
    [    7.766024] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
    [    7.766179] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
    [    7.811610] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
    [    9.639508] Adding 1413116k swap on /dev/sda6.  Priority:-1 extents:1 across:1413116k 
    [    9.658588] EXT4-fs (sda5): re-mounted. Opts: (null)
    [    9.906212] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
    [   10.352065] loop: module loaded
    [   12.470646] atl1c 0000:0e:00.0: irq 47 for MSI/MSI-X
    [   12.471338] atl1c 0000:0e:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
    [   14.629139] bbswitch: version 0.8
    [   14.629154] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    [   14.629163] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    [   14.629188] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [   14.629343] bbswitch: detected an Optimus _DSM function
    [   14.629366] pci 0000:01:00.0: enabling device (0006 -> 0007)
    [   14.629451] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    [   14.633271] bbswitch: disabling discrete graphics
    [   14.633294] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [   14.925969] Netfilter messages via NETLINK v0.30.
    [   18.198246] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [  482.635755] bbswitch: enabling discrete graphics
    [  483.339458] nvidia: module license 'NVIDIA' taints kernel.
    [  483.339466] Disabling lock debugging due to kernel taint
    [  483.353271] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
    [  483.353819] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
    [  483.353829] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.24  Wed Jul  2 14:24:20 PDT 2014
    [  483.627585] nvidia 0000:01:00.0: irq 48 for MSI/MSI-X
    [  483.635720] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635781] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635809] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635834] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635859] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635884] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635967] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  483.635993] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  501.309962] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [  501.336065] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    [  501.336100] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    [  501.368958] NVRM: RmInitAdapter failed! (0x25:0x28:1181)
    [  501.368970] NVRM: rm_init_adapter failed for device bearing minor number 0
    [  501.368995] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5
    [  935.094761] bbswitch: enabling discrete graphics
    [ 1493.777226] bbswitch: enabling discrete graphics
    [ 1493.792829] nvidia 0000:01:00.0: Refused to change power state, currently in D3
    [ 2000.720559] bbswitch: enabling discrete graphics
    [ 2000.736015] nvidia 0000:01:00.0: Refused to change power state, currently in D3
    lspci | egrep 'VGA|3D'
    Code:
    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 GK107 [GeForce GT 650M] (rev ff)
    modinfo nvidia
    Code:
    modinfo nvidia
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.24
    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_RMEdgeIntrCheck: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:
    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
    echo $PATH
    Code:
    echo $PATH
    /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin

  33. #33
    Join Date
    2014-Aug
    Posts
    3

    correct (?) installed nvidia driver, but no acces to GPU (2/2)

    find 2> /dev/null / -name nvidia*.ko
    Code:
    find 2> /dev/null / -name nvidia*.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
    /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    /var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia-uvm.ko
    /var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia.ko
    /etc/bumblebee/xorg.nvidia.conf
    Code:
    /etc/bumblebee/xorg.nvidia.conf
    bash: /etc/bumblebee/xorg.nvidia.conf: No such file or directory
    /etc/bumblebee/bumblebee.conf
    Code:
    # 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


    I hope someone can help me, please
    thx

  34. #34
    Join Date
    2014-Aug
    Posts
    3

    the solution for a very common error with bumblebee: Failed to initialize...

    ERROR: Failed to initialize the NVIDIA GPU at PCI:1:0:0

    solution found on this site:
    https://github.com/Bumblebee-Project...bee/issues/542

    changing
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet"
    to
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet rcutree.rcu_idle_gp_delay=1"
    in /etc/default/grub.
    I tried it and it worked

  35. #35
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by tonrin View Post
    ERROR: Failed to initialize the NVIDIA GPU at PCI:1:0:0

    solution found on this site:
    https://github.com/Bumblebee-Project...bee/issues/542

    changing
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet"
    to
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet rcutree.rcu_idle_gp_delay=1"
    in /etc/default/grub.
    I tried it and it worked
    Hi tonrin!

    Thanks for sharing your fix, I know a lot of users will appreciate it.

    For anyone using this fix, make sure you run an update-grub after making changes.

    To see if this will work for you as a fix before modifying that file and running update-grub, you can run the following (I can't credit the original creator as this has been posted on about 40 different sites in relation to this fix)

    Code:
    sudo tee /sys/module/rcutree/parameters/rcu_idle_gp_delay <<<1
    and then try optirun glxspheres64

    If that fixes it, you should update the grub file.

  36. #36
    Join Date
    2014-Jul
    Posts
    5
    Hey all,

    I have a problem with the following:
    Code:
    root@kali:~# optirun glxspheres64 
    [  347.923592] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
    [  347.923672] [ERROR]Could not connect to bumblebee daemon - is it running?
    Code:
    root@kali:~# dmesg | tail -n 30
    [    5.971403] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [    5.971960] bbswitch: detected an Optimus _DSM function
    [    5.971977] pci 0000:02:00.0: enabling device (0004 -> 0007)
    [    5.972028] bbswitch: Succesfully loaded. Discrete card 0000:02:00.0 is on
    [    6.106233] Netfilter messages via NETLINK v0.30.
    [    6.226566] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
    [    6.329054] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
    [    6.329158] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [    6.330542] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
    [    6.330782] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
    [    6.343007] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [    6.620947] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [    6.820633] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input10
    [   13.634626] wlan0: authenticate with 24:a2:e1:ec:af:5a
    [   13.638425] wlan0: send auth to 24:a2:e1:ec:af:5a (try 1/3)
    [   13.640307] wlan0: authenticated
    [   13.641771] wlan0: associate with 24:a2:e1:ec:af:5a (try 1/3)
    [   13.645717] wlan0: RX AssocResp from 24:a2:e1:ec:af:5a (capab=0x1411 status=0 aid=1)
    [   13.647617] wlan0: associated
    [   13.647676] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [   13.647758] cfg80211: Calling CRDA for country: PL
    [   13.655344] cfg80211: Regulatory domain changed to country: PL
    [   13.655351] cfg80211:  DFS Master region: unset
    [   13.655354] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [   13.655359] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [   13.655362] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [   13.655365] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [   13.655368] cfg80211:   (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
    [   13.655371] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
    [   13.691353] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 24:a2:e1:ec:af:5a
    Do you have any ideas ?
    if more info needed please let me know

  37. #37
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by johnnyinc View Post
    Hey all,

    I have a problem with the following:
    Code:
    root@kali:~# optirun glxspheres64 
    [  347.923592] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
    [  347.923672] [ERROR]Could not connect to bumblebee daemon - is it running?
    Code:
    root@kali:~# dmesg | tail -n 30
    [    5.971403] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    [    5.971960] bbswitch: detected an Optimus _DSM function
    [    5.971977] pci 0000:02:00.0: enabling device (0004 -> 0007)
    [    5.972028] bbswitch: Succesfully loaded. Discrete card 0000:02:00.0 is on
    [    6.106233] Netfilter messages via NETLINK v0.30.
    [    6.226566] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
    [    6.329054] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
    [    6.329158] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [    6.330542] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
    [    6.330782] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
    [    6.343007] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [    6.620947] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [    6.820633] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input10
    [   13.634626] wlan0: authenticate with 24:a2:e1:ec:af:5a
    [   13.638425] wlan0: send auth to 24:a2:e1:ec:af:5a (try 1/3)
    [   13.640307] wlan0: authenticated
    [   13.641771] wlan0: associate with 24:a2:e1:ec:af:5a (try 1/3)
    [   13.645717] wlan0: RX AssocResp from 24:a2:e1:ec:af:5a (capab=0x1411 status=0 aid=1)
    [   13.647617] wlan0: associated
    [   13.647676] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [   13.647758] cfg80211: Calling CRDA for country: PL
    [   13.655344] cfg80211: Regulatory domain changed to country: PL
    [   13.655351] cfg80211:  DFS Master region: unset
    [   13.655354] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [   13.655359] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [   13.655362] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [   13.655365] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [   13.655368] cfg80211:   (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
    [   13.655371] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
    [   13.691353] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 24:a2:e1:ec:af:5a
    Do you have any ideas ?
    if more info needed please let me know
    Try the following

    /etc/init.d/bumblebeed start

    If that fails, I would guess that bbswitch failed to install correctly.

    Try :

    apt-get install linux-headers-$(uname -r)
    apt-get install --reinstall bbswitch
    /etc/init.d/bumblebeed start

    Edit: try optirun -vv glxspheres64

    The above will give more debugging info. With dmesg, try -n 100 so it has some more info in it.
    Last edited by staticn0de; 2014-08-21 at 09:39.

  38. #38
    Join Date
    2014-Aug
    Posts
    1

    pls

    Hi staticn0de! Greate job. thank you.
    excuse me for my English.
    i did everything like 25 post suggests. and use last version of driver from nvidia
    but have the same problem with "optirun glxspheres" like Xperianist

    my HW
    HP Pavilion 15-n060er with Intel and Nvidia GeForce 750M VGA
    do you know how can i configure the system to use only discrete VGA?

    Maybe Xperianist solved this problem? if you did please share solution

    Any ideas? please help me with this. waiting for your answer

  39. #39
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Hashcat 1.30 seems to be out http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/
    oclhashcat_1.30-0kali1_amd64.deb 2014-08-22 21:36 120M
    Any theory as to why the new package is now 120Mb instead of 508Mb !?



    Sincerely,

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

  40. #40
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    Hashcat 1.30 seems to be out http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/


    Any theory as to why the new package is now 120Mb instead of 508Mb !?



    Sincerely,

    Seriously Confused
    Hey Quest,

    The obvious changes are that the cudahashcat binary has been removed (no large change in file size there)

    The other one is that the 4318 folder within usr/share/kernels has been removed. That was a very large folder and accounts for the size difference.

    On the + the change log says support for 340.24 has been added

  41. #41
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Thanks again friend. Good to have someone onboard that understand these things =]

    How did you go about installing 1.30 (I presume you did install it) ? Did you uninstall 1.01 first? If so what is the alchemical formula? How many dead frogs and bats will I need to upgrade to 1.30, or do I simply install on top of 1.01?
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  42. #42
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    Thanks again friend. Good to have someone onboard that understand these things =]

    How did you go about installing 1.30 (I presume you did install it) ? Did you uninstall 1.01 first? If so what is the alchemical formula? How many dead frogs and bats will I need to upgrade to 1.30, or do I simply install on top of 1.01?
    I have not installed it yet, I downloaded and unpacked the .debs and ran them through some compare software.

    at a guess, I would say

    apt-get remove --purge oclhashcat && apt-get install oclhashcat

    I'll try soon though and post how it goes

  43. #43
    Join Date
    2014-Aug
    Posts
    1
    Many thanks man! it's work very nice for me

    Code:
    CUDA Device Query (Runtime API) version (CUDART static linking)
    
    Detected 1 CUDA Capable device(s)
    
    Device 0: "GeForce GTX 870M"
      CUDA Driver Version / Runtime Version          6.5 / 6.0
      CUDA Capability Major/Minor version number:    3.0
      Total amount of global memory:                 3072 MBytes (3221028864 bytes)
      ( 7) Multiprocessors, (192) CUDA Cores/MP:     1344 CUDA Cores
      GPU Clock rate:                                967 MHz (0.97 GHz)
      Memory Clock rate:                             2500 Mhz
      Memory Bus Width:                              192-bit
      L2 Cache Size:                                 393216 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 GTX 870M
    Result = PASS

  44. #44
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    ehh, something funky is going on. After uninstall 1.01 and installing 1.30, using the test command
    ./cudaHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict
    does not work.



    ./oclHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict
    rturns:
    ERROR: No AMD/SDS compatible platform found

    root@kali:/usr/share/oclhashcat#

    could this be a AMD only release?


    Edit:
    Code:
    apt-get install oclhashcat
    returns:
    http://http.kali.org/kali/ kali/non-free oclhashcat amd64 1.01-1kali2 [533 MB]
    so I do not know what that oclHashcat 1.30 package is.
    Last edited by Quest; 2014-08-25 at 03:23.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  45. #45
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    ehh, something funky is going on. After uninstall 1.01 and installing 1.30, using the test command
    does not work.



    rturns:



    could this be a AMD only release?


    Edit:
    Code:
    apt-get install oclhashcat
    returns:


    so I do not know what that oclHashcat 1.30 package is.
    Well, you are right. That is an AMD only release.

    The good news is, cudahashcat 1.30 does work on Kali (I just crunched that example hash). The bad news is, it is not in the repo and I had to install it manually (first world problems, right?)

    I'm trying my hand at making my own .deb which will install 1.30 on Kali. I've never done that before so I have no ETA. May be easier to extract hashcat and my soft links to the .bin.

  46. #46
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    ehh, something funky is going on. After uninstall 1.01 and installing 1.30, using the test command
    does not work.



    rturns:



    could this be a AMD only release?


    Edit:
    Code:
    apt-get install oclhashcat
    returns:


    so I do not know what that oclHashcat 1.30 package is.
    Amazingly, my deb works.

    Code:
    root@kali:~# dpkg -i cudaHashcat-1.30.deb 
    Selecting previously unselected package cudahashcat-1.30.
    (Reading database ... 349321 files and directories currently installed.)
    Unpacking cudahashcat-1.30 (from cudaHashcat-1.30.deb) ...
    Setting up cudahashcat-1.30 (1.30) ...          
    root@kali:~# optirun cudahashcat64 -t 32 -a 7 example0.hash ?a?a?a?a example.dict 
    cudaHashcat v1.30 starting...
    I have taken the archive from the hashcat site and modified it under section 6 of their EULA. The deb installs the program is /usr/share/cudahashcat and places scripts in /usr/bin which calls hashcat like any other command.

    I'll upload it tonight for anyone that wants to use it. Provided as is with no expectation it will work and it may cause damages including death and your wife leaving you (tic) but you get the idea.

    Weighs in at 172mb

    Edit:

    Download link:
    https://www.mirrorcreator.com/files/...1.30.deb_links

    SHA1SUM
    f2c0d96c75d1c186b48e11c5b399f3e2ccc5e459

    when installed, its called with 'cudahashcat64' for 64bit or 'cudahashcat32' for 32 bit.
    Last edited by staticn0de; 2014-08-26 at 04:58.

  47. #47
    Join Date
    2013-Aug
    Location
    lost in space
    Posts
    580
    Thanks staticn0de!

    What a bizarre file naming convention. They seem to have enormous difficulties identifying their own creation... And now I'm abit suspicious about the file size difference between 1.01/1.30 What else are we missing?

    I cannot try it now, and I have very little experience with Hashcat anyways, but something tells me that 1.30 is missing a few feathers...



    Edit:

    Works bro!

    Not much difference (for this test). Actually I'm now 2mins slower than I was with 1.01

    Code:
    ===============================CudaHashcat 1.01:
    
    Session.Name...: cudaHashcat
    Status.........: Exhausted
    Input.Base.....: Mask (?a?a?a?a) [4]
    Input.Mod......: File (example.dict)
    Hash.Target....: File (example0.hash)
    Hash.Type......: MD5
    Time.Started...: Mon Jul 28 18:22:33 2014 (12 mins, 7 secs)
    Time.Estimated.: 0 secs
    Speed.GPU.#1...:   187.9 MH/s
    Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
    Progress.......: 136302297088/136302297088 (100.00%)
    Rejected.......: 0/136302297088 (0.00%)
    HWMon.GPU.#1...: -1% Util, 69c Temp, -1% Fan
    
    Started: Mon Jul 28 18:22:33 2014
    Stopped: Mon Jul 28 18:34:46 2014 (12mins)
    
    
    
    ===============================CudaHashcat 1.30:
    
    Session.Name...: cudaHashcat
    Status.........: Exhausted
    Input.Base.....: Mask (?a?a?a?a) [4]
    Input.Mod......: File (example.dict)
    Hash.Target....: File (example0.hash)
    Hash.Type......: MD5
    Time.Started...: 0 secs
    Time.Estimated.: 0 secs
    Speed.GPU.#1...: 41304.2 kH/s
    Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
    Progress.......: 136302297088/136302297088 (100.00%)
    Skipped........: 0/136302297088 (0.00%)
    Rejected.......: 0/136302297088 (0.00%)
    HWMon.GPU.#1...: -1% Util, 66c Temp, -1% Fan
    
    Started: Mon Aug 25 20:44:03 2014
    Stopped: Mon Aug 25 20:58:04 2014 (14mins)
    Regardless, your .deb works!
    Last edited by Quest; 2014-08-26 at 01:09.
    Kali Linux USB Installation using LinuxLive USB Creator
    Howto Install HDD Kali on a USB Key
    Clean your laptop fan | basic knowledge

  48. #48
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Quest View Post
    Thanks staticn0de!

    What a bizarre file naming convention. They seem to have enormous difficulties identifying their own creation... And now I'm abit suspicious about the file size difference between 1.01/1.30 What else are we missing?

    I cannot try it now, and I have very little experience with Hashcat anyways, but something tells me that 1.30 is missing a few feathers...



    Edit:

    Works bro!

    Not much difference (for this test). Actually I'm now 2mins slower than I was with 1.01

    Code:
    ===============================CudaHashcat 1.01:
    
    Session.Name...: cudaHashcat
    Status.........: Exhausted
    Input.Base.....: Mask (?a?a?a?a) [4]
    Input.Mod......: File (example.dict)
    Hash.Target....: File (example0.hash)
    Hash.Type......: MD5
    Time.Started...: Mon Jul 28 18:22:33 2014 (12 mins, 7 secs)
    Time.Estimated.: 0 secs
    Speed.GPU.#1...:   187.9 MH/s
    Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
    Progress.......: 136302297088/136302297088 (100.00%)
    Rejected.......: 0/136302297088 (0.00%)
    HWMon.GPU.#1...: -1% Util, 69c Temp, -1% Fan
    
    Started: Mon Jul 28 18:22:33 2014
    Stopped: Mon Jul 28 18:34:46 2014 (12mins)
    
    
    
    ===============================CudaHashcat 1.30:
    
    Session.Name...: cudaHashcat
    Status.........: Exhausted
    Input.Base.....: Mask (?a?a?a?a) [4]
    Input.Mod......: File (example.dict)
    Hash.Target....: File (example0.hash)
    Hash.Type......: MD5
    Time.Started...: 0 secs
    Time.Estimated.: 0 secs
    Speed.GPU.#1...: 41304.2 kH/s
    Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
    Progress.......: 136302297088/136302297088 (100.00%)
    Skipped........: 0/136302297088 (0.00%)
    Rejected.......: 0/136302297088 (0.00%)
    HWMon.GPU.#1...: -1% Util, 66c Temp, -1% Fan
    
    Started: Mon Aug 25 20:44:03 2014
    Stopped: Mon Aug 25 20:58:04 2014 (14mins)
    Regardless, your .deb works!
    Hey Quest,

    Thanks for trying it, you can unpack it manually and see how I did it with the 'ar' command.

    Regards to what else we are missing, it's all kernel files. At a guess I would say they are no longer supported. When they are unpacked they take up huge amounts of disk space.

  49. #49
    Join Date
    2014-Aug
    Posts
    1

    optirun glxspheres64 suddenly shutdown laptop

    Hi,I am setting up bumblebee for my GT 650M following the guide on post #25 but when I run optirun glxspheres64 my laptop suddenly shutdown. Here's some command returns:

    Code:
    # 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 GK107 [GeForce GT 650M] (rev ff)
    Code:
    modinfo nvidia
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.32
    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
    Thanks in advance.

  50. #50
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by ryuga View Post
    Hi,I am setting up bumblebee for my GT 650M following the guide on post #25 but when I run optirun glxspheres64 my laptop suddenly shutdown. Here's some command returns:

    Code:
    # 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 GK107 [GeForce GT 650M] (rev ff)
    Code:
    modinfo nvidia
    filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
    alias:          char-major-195-*
    version:        340.32
    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
    Thanks in advance.
    Hi there,

    Try this from terminal and then run glxspheres64 with optirun

    Code:
    sudo tee /sys/module/rcutree/parameters/rcu_idle_gp_delay <<<1
    If that works, follow this post to make the change permanent

    https://forums.kali.org/showthread.p...ll=1#post36390

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
  •