Boot Problem

Hello all!

First, english is not my primary language so its way not perfect!


Okay. Im runing on my laptop windows 7 64 bit.
Now i installed Backtrack 5 too with dualboot. During the installation all gone easy.

But i just cant boot backtrack!
I turn my laptop on, choose backtrack then many lines apear and after some seconds it stops with this line:
"4.094320] fb: conflict fb hw usage nouveaufb vs VESA VGA - removing generic driver"

When i start the live-CD in the boot menu there is 2 time something with "text mode" or something..
when i run the first text mode i also get this error, the second one runs without problems!?

Of course i googled alot! But there no tuts i understand :/
I just found out that it could be a driver problem, i just downloaded the actual driver for my gfx-card for linux but i dont know how to install it.
This is first time im using Linux so im an absolute noob on linux so i hope here is someone who can explain me noob-friendly what to do with exact comands.


Here informations you may need:

Backtrack 5 R1:
64 bit
Gnome
version: 2.30.2
Distributor: Ubuntu
Build Date: 06/25/2010
installed on HDD (in real its an SSD but i think thats not important)

graphic-card:
Nvidia geforce gtx 570m

RAM:
16 GB

CPU:
intel core i7 (will edit the exact model if you need)


hope so much someone could help me!

nice greets

Well, you're a brave person to dive into BackTrack without having some Linux background :) Although it's probably what you don't want to hear, I advise removing your BT partition, get some virtual machine software, and install BackTrack in a vm. That way, you can play all you want, and won't risk messing up your base operating system. This will also help you troubleshoot your BT install. Honestly, though, if you're brand new to Linux, using BackTrack is not the recommended way to start out. I'd install Ubuntu in a VM, and spend a lot of time at the command line, before going into BackTrack. There's a lot you need to understand about Linux first.

bernibern,

Paste you /boot/grub/grub.cfg file here and I will advise...


Cheers!

thanks for your answers!

@scottm99
yeah i know BT is not the best to start with linux... but not a noob when it goes on computer itself... i now how networks work and so on you know ;)
So i thought i will find a way to get comfortable with BT!

@snafu777
here is it! i hope its the one from my hdd not from live-cd ^^

Code:

---

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.39.4' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 1c8323a7-c6e3-4e8a-b409-96a09257d185
    linux    /boot/vmlinuz-2.6.39.4 root=UUID=1c8323a7-c6e3-4e8a-b409-96a09257d185 ro  text splash vga=791
    initrd    /boot/initrd.img-2.6.39.4
}
menuentry 'Ubuntu, with Linux 2.6.39.4 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 1c8323a7-c6e3-4e8a-b409-96a09257d185
    echo    'Loading Linux 2.6.39.4 ...'
    linux    /boot/vmlinuz-2.6.39.4 root=UUID=1c8323a7-c6e3-4e8a-b409-96a09257d185 ro single
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-2.6.39.4
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 1c8323a7-c6e3-4e8a-b409-96a09257d185
    linux16    /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 1c8323a7-c6e3-4e8a-b409-96a09257d185
    linux16    /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
  if keystatus; then
    if keystatus --shift; then
      set timeout=-1
    else
      set timeout=0
    fi
  else
    if sleep --interruptible 3 ; then
      set timeout=0
    fi
  fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

---