Jump to content











Photo
- - - - -

Kali Linux Persistent Nvidia/Nouveau Video Driver Boot Fail


Best Answer toejam , 07 January 2014 - 06:07 AM

Bah nevermind, adding nomodeset to the .mnu file was the ticket. Go to the full post


  • Please log in to reply
3 replies to this topic

#1 toejam

toejam
  • Members
  • 3 posts
  •  
    Canada

Posted 06 January 2014 - 10:30 AM

Long time lurker first time poster.  Thank you for all the informative information!!

 

 

This is my first time making a persistant for  Kali Linux.  When I ususally boot up Kali I can enter the extra commands into the Kali Live Boot Menu by pressing tab and adding  "nouveau.modeset=0" into the boot commands.  Which in return won't use the Nouveau driver it likes to load up which leaves a graphical smear all over my screen.

 

Since I've turned it to persistent I can't add those commands that I usually can from Kali Linux main boot menu leaving me unable to even get onto kali to install the proper drivers.  I've been working on this for two days straight and i'm completely stumped. Please Help a guy out!!  

 

extra info : Nvida gts360m graphics card, 64 bit kali

 

Thanks in advance for any help!!

 

 

 

 



#2 dog

dog

    Frequent Member

  • Expert
  • 236 posts

Posted 06 January 2014 - 01:07 PM

When the grub2 text menu appears, hit e to edit, then use the cursor keys to navigate to the line that ends with "quiet", add your kernel parameters there, then F10 to boot it. When it's booted, you can replace GRUB_CMDLINE_LINUX_DEFAULT = "quiet" in /etc/default/grub then run update-grub to generate a new grub.cfg


  • toejam likes this

#3 toejam

toejam
  • Members
  • 3 posts
  •  
    Canada

Posted 06 January 2014 - 11:26 PM

Thanks dog I appreciate the reply but with persistence it boots directly into the kernal from e2b there is no menu after. I just get a continuous boot loop of pgraph tlb flush idle time out.

#4 toejam

toejam
  • Members
  • 3 posts
  •  
    Canada

Posted 07 January 2014 - 06:07 AM   Best Answer

Bah nevermind, adding nomodeset to the .mnu file was the ticket.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users