Results 1 to 3 of 3

Thread: Nvidia driver problems install....

  1. #1
    Just burned his ISO
    Join Date
    Jan 2012

    Default Nvidia driver problems install....

    I am following this process with installing nvidia drivers and cuda

    everything seemed to install fine but when i get to this part:

    Ideally you should install the CUDA toolkit to /opt. this guide assumes this installation path. Configure your environment variables so that the nvcc command works. You can do this by appending the following lines in your /root/.bashrc file:

    export PATH
    export LD_LIBRARY_PATH
    root@bt:~# source /root/.bashrc
    root@bt:~# ldconfig
    I get this response when i run "source /root/.bashrc"

    root@bt:~# source /root/.bashrc
    bash: /opt/cuda/bin: is a directory
    Below is my edited /root/.bashrc file

    # ~/.bashrc: executed by bash(1) for non-login shells.
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
    # for examples

    # If not running interactively, don't do anything
    if [[ -n "$PS1" ]]; then

    # don't put duplicate lines in the history. See bash(1) for more options
    # ... or force ignoredups and ignorespace

    # append to the history file, don't overwrite it
    shopt -s histappend

    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

    # check the window size after each command and, if necessary,
    # update the values of LINES and COLUMNS.
    shopt -s checkwinsize

    # make less more friendly for non-text input files, see lesspipe(1)
    [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

    # set variable identifying the chroot you work in (used in the prompt below)
    if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)

    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
    xterm-color) color_prompt=yes;;

    # uncomment for a colored prompt, if the terminal has the capability; turned
    # off by default to not distract the user: the focus in a terminal window
    # should be on the output of commands, not on the prompt

    if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)

    if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
    unset color_prompt force_color_prompt

    # If this is an xterm set the title to user@host:dir
    case "$TERM" in
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"

    # enable color support of ls and also add handy aliases
    if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'

    # some more ls aliases
    alias ll='ls -alF'
    alias la='ls -A'
    alias l='ls -CF'

    # Alias definitions.
    # You may want to put all your additions into a separate file like
    # ~/.bash_aliases, instead of adding them here directly.
    # See /usr/share/doc/bash-doc/examples in the bash-doc package.

    if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases

    # enable programmable completion features (you don't need to enable
    # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
    # sources /etc/bash.bashrc).
    #if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
    # . /etc/bash_completion
    export HISTCONTROL=ignoreboth

    export PATH=$PATH:/etc/alternatives/gem-bin

    PATH=$PATH: /opt/cuda/bin
    export PATH
    export LD_LIBRARY_PATH

    Im not sure what it is i have done wrong....and yes i did install cuda to /opt

    Please help, Im still pretty new so im sure its just a dumb user mistake but i cant seem to figure it out. and google didnt help nor did i see anything related in the forums.

  2. #2
    My life is this forum Snayler's Avatar
    Join Date
    Jan 2010

    Default Re: Nvidia driver problems install....

    Just remove the space between "PATH=$PATH:" and "/opt/cuda/bin" and it should work fine.

  3. #3
    Senior Member
    Join Date
    Jul 2011

    Default Re: Nvidia driver problems install....

    export PATH=$PATH:/etc/alternatives/gem-bin

    PATH=$PATH: /opt/cuda/bin
    export PATH
    export LD_LIBRARY_PATH

    Try this
    export PATH
    export PATH
    export LD_LIBRARY_PATH
    Pffbt..[quote]I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. [/quote]

Similar Threads

  1. Nvidia driver install problem
    By looserkiller in forum BackTrack 5 Beginners Section
    Replies: 2
    Last Post: 10-09-2011, 04:58 PM
  2. Nvidia driver install
    By Digitaljester in forum BackTrack 5 Fixes
    Replies: 0
    Last Post: 09-27-2011, 03:36 PM
  3. How can i install nvidia driver in bt3 final
    By t1nm@n in forum OLD Newbie Area
    Replies: 2
    Last Post: 01-17-2010, 10:38 PM
  4. Problems with nvidia driver instalation
    By RaZZoR6 in forum OLD BackTrack 4 General Support
    Replies: 3
    Last Post: 11-06-2009, 12:30 PM
  5. install Nvidia driver?
    By -=DDOS=- in forum OLD Newbie Area
    Replies: 2
    Last Post: 05-24-2009, 05:10 PM

Posting Permissions

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