Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been using the step by step on this site to install my nvidia drivers.
I changed my inittab file, changed vesa to nvidia. I've killed x and I'm at the command prompt.
When I issue ls as root I get
Desktop/ drakx/ nvidia-llinux-x86-1.0-4496-pkg2.run.txt/ tmp/ (in blue)
Now just by looking I can see that this isn't right, as it's giving me part of a directory output, but I tried anyway.
I tried exactly as above and it didn't work. So I thought maybe if I cd'd over to my Desktop directory nope. I tried to cd over to a directory similar to the Desktop / drakx/ dir and found nothing. The only directory ls works in is the root dir.
Here's exactly what I've done. I've downloaded the driver from Nvidia. Placed it on my local user Desktop (even though I had the keys in the taskbar it wouldn't let me move the file in my local account). I had to log in as root to edit the correct files. I don't know what the deal with that is, again I had the root keys in my taskbar but it wouldn't allow me to make any changes.
Anyhow, I rebooted and issued ls and the above problem started. Also will it effect my local user account if I issued the commands logged in under root?
I don't know what you're expecting to get from ls, but as far as I can tell, you got exactly what I'd expect.
'nvidia-llinux-x86-1.0-4496-pkg2.run.txt' looks wrong, though....it may not work if it was downloaded as a text file (i think it's supposed to be a binary?).
Try (as root, and without the txt extension):
./nvidia-llinux-x86-1.0-4496-pkg2.run
or
~/nvidia-llinux-x86-1.0-4496-pkg2.run
I downloaded the file from Windows which is probably the problem. When I clicked the download link it sent me to the actual code page. So I right clicked and did a save as.
Ok I've just ventured back to the NVIDIA page and checked the download it gives a run extension but when you right click in Windows under save as it says (save as text document). Oh man, now I remember why I'm switching to Linux.
Thanks that's really all I needed. I'm just going to go ahead and download the file again.
I don't think that it downloaded properly. That may not be the most recent driver also. Also, the install program will not run when x is running. It will look on the net for a more recent version, and may need to compile a driver interface for your kernel. You will want to make sure you have the kernel source installed. It will install a long document in /usr/local/doc/. I don't remember the exact name, but I think it's something like NVIDIA-GLX.doc It displays options you may need to use to get the newest source off the web. After installing, print out this document before editing your XF86config-4.
control + alt + f2
login as root
enter ur password
type telinit 3
make sure u had the driver in your root (home) folder
type:
sh "drivername" where drivername is the name of the driver (IT IS CASE SENSITIVE)
itll take u through the install
when alls done type
telinit 5
gl
Are you sure that you edited your XF86config-4 file correctly before rebooting? IIRC, all you need to change is under the Section "Device", the Driver "nv" to Driver "nvidia" and you should be good to go.
Ok I'll try that. Yes I removed vesa and replaced it with nvidia. Under the other section I was supposed to edit none of the things that I was supposed to remove were there, so I didn't bother touching anything in that section of the xF86.
I also have read about a known issue with APIC (I believe). It sounded similar to my problem so I disabled that, and it still didn't work.
I was on another site and read that the default size settings can cause this issue, I haven't tried this but I'm going to try it later tonight, I'm going to set it to 800x600 and see if that takes me anywhere. I'll look at the error log's first though.
The weird thing is, is that it act's as if it installs flawlessly, but then nothing happens.
I got to command as it starts on 3 instead of 5, and realized that I didn't have one of the buttons to issue the above commands on my laptop keyboard. The squiggle after startx >.
I did however hit tab or shift by mistake and got a list of commands. I saw an xservererror command I entered it and it looked like it tried to load x and then I got a black screen I hit enter and got a list of things. The screen looked bad it was poorly lit and it looked like it had small lines down all of it.
When I got the command line back I entered KDE and it started and went black and I hit enter.
I got this. I wrote it by hand so it may not be formatted correctly but whatever.
>Warning: Symbol map for key <SPCE> redifined (a bunch of these for different keys on my keyboard, I figured one was sufficent)
>Using last definition for conflicting fields
Errors from xkbcomp are not fatal to xserver
Startkde: Starting up...
Kbuildsyscoca running...
Mcop warning: User defined signal handles found for SIG_PIPE overriding
Startkde: Shutting down
Klauncher: Exiting on signal 1
Startkde: Running shutdown scripts
Startdke: Done
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.