Printable View
i have backtrack 4 rc2 on a dvd, when i boot it up i put fixvesa since startx doesnt work, then i tried startx and it dtill doesnt work, how do i fix this?
do i need special drivers?
btw i have a gt 420M gpu and my wireless card is
intel r wifi link 1000 bgn
my laptop is a dellxps 15
Any error messages you get when running startx?
Also you might have to install the mobile device drivers at first.
Hi, I have been unable to startx from backtrack 4 rc2 on dvd.Quote:
Originally Posted by omega666
When startx was entered at root@bt:~#, I was graced with a black screen, or maybe my screen switching off.
I've burnt at least 4 or 5 copys of backtrack 4 rc2 on dvd using bt4r2.iso from 2 different sources, 'direct link' and 'torrent'.
I thought the problem was with my Macbook Superdrive or a bad iso.
I did a little searching for info and came across a few mentions of using:
fixvesa
or
fix-vesa
I don't know exactly what either do, yet I used fix-vesa at root@bt:~# then startx and BT4R2 entered the GUI with no problem.
I could of got straight to the point or fix but this will help others looking for answers.
I'm a Linux noob, but it worked for me... Hope I've helped.
fixvesa didnt work, where can i get the right drivers?
Hello again,Quote:
Originally Posted by omega666
Like I say; I'm a Linux Noob...
I'm using a White MacBook. (not sure of exact model/firmware etc...)
Results may differ depending on the hardware your using.
This is what I did/have noticed and has worked for me;
- Booted from bt4r2 on DVD
- Entered fix-vesa at the root@bt:~# promt.
(Not fixvesa. although I'm unsure as to exactly what both do, they are two seperate comands.)- Entered startx at the root@bt:~# promt.
- The BT4R2 GUI started successfully.
- Used the Install script on the desktop to perform a Hard Drive Install.
- On first boot from the Hard Drive I had to;
Enter fix-vesa at the root@bt:~# promt.
Enter startx at the root@bt:~# promt.- Every boot after that all I did was/am still doing is;
Enter startx at the root@bt:~# promt.
Like I say, things may differ depending on hardware...
The above method does work on the type of MacBook I'm using and may work across many other, if not all, hardware setups.
The reason I dare to imagine such a thing is due to me getting hints of the problem being related to xorg config. (or summat... ouch, I'm a noob) fix-vesa may rewrite said config file/s or pop them in the right place or something.
Anyway, hope it works for you and if not, hope you find your fix soon.:)