Installing Graphics card drivers - Nubiddy nub
Okay, so for about 4 hours now ive been reading reading reading on how to install this Nvidia Geforce 8800 driver, and have gotten about halfway to nowhere. I've been told that the installation files i got will do everything - it doesnt. I've been told about some kind of xorg.conf file that doesnt exist- xorg.conf-vesa does though, i assume thats vesa drivers and theres something else for other drivers.. I'm extremely confused right now.. so many controdictions .... D:
How do i install the drivers!!!??? |
next time post your system 64 or 32 bit. for 32 bit here for 64 bit here down load it save it. now you have to be in telinit 3 run level 3.
how open a terminal and type su then password the type killall kdm or telinit 3. or you could reboot to slackware default run level 3. login as root then cd (change directory) /to/your/saved/ nvidia driver type Quote:
|
Yes to everything above.
Just save the nvidia driver, like above get the correct arch 32 or 64. Save that file somewhere. CTRL+ALT+DEL to kill X. If your not root, then logout and log in as root. Go to the directory where you saved the file. then run ./NVIDIA-<version>.run. Follow the on screen instructions, just let it do its thing. The last question asks if you want the installer to make a xorg.conf file for your, In your case select "yes". After that your the installer will finish and you shold be good to go. |
I am happy to see that this thread was started just two days ago. I am new to slackware, but have several years of Linux experience and just went through the process as described in the above posts. At first, all appeared to be working. However, I found that some thing did not. For example, glxgears would not run, the Composting kept disabling itself, and many of the effects would not 'load'. Looking at the /var/log/Xorg.0.log indicated that a lot of the modules were not correct stating as an error (EE) that it needed to be using NVIDIA GLX.
I re-ran the 260.19.21 .run script with the --UNinstall option. This crashed my X display completely. I recovered it by launching the other Linux install on this machine and restoring the xorg.conf file to the original VESA one installed. I then followed the instructions here. Basically, I downloaded the 256 run rile (from nvidia), and then the kernel-driver and the nvidia-drive from Slackbuilds. You need to put the nvidia .run driver in the folder to run the pkgbuild script, but they compile without difficulty and install themselves into the /tmp folder. I then used installpkg on those two packages. Note, it was not necessary to stop X for this process. I then logged out of X and then re-entered it. All functions appear to be working now. My question is, what did I miss or what wasn't done as part of the .run file from nvidia that should (?) have installed everything? Do you still need to install the kernel-driver and was that my missing piece? |
Quote:
I am using the gallium nouveau open source driver from slackware64-current /extra and it does a great job with Three D openGL rendering. |
What is the model of your video card?
|
1 Attachment(s)
Quote:
Quote:
|
yes I have run into this before nvidia will merge the the xorg.config and this can be a problem if you have installed nvidia drivers more than once. a old nvidia config with a newer xorg. this will creates
Quote:
we had a major xorg upgrade if using current. Yes I know you have been around the block a few time around here. Quote:
|
Interesting. I still have copies of the various xorg.conf files. It might prove enlightening to compare them for the differences. In my case, I was installing the driver into a virgin Slackware install that had only been using the default vesa-compatible driver. I am curious if the problem was entirely in the xorg.conf file or if something went wrong with the .run file install. It might be an interesting experiment to remove the current drivers and try the new one again and manually modifying the xorg.conf file, only changing what is necessary.
It turns out that there is a rather lengthy release notes read me file for the driver (link available from the additional information tab on the driver download page). Looking through it, I found an answer to one of my own questions, regarding the kernel-module. Specifically the document says: "The NVIDIA kernel module has a kernel interface layer that must be compiled specifically for each kernel. NVIDIA distributes the source code to this kernel interface layer.". I assume that if it does not find this that the installation will fail and that this can be ruled out as part of the problem. As an aside, since encountering this a few days ago, I have also been looking at the Slackbook, which has a large section on configuring X and I also noticed that there is a sticky thread regarding the drivers. As a quote I saw before trying Slackware said, "I have learned more by using Slackware for 6 months that I have learned from other distributions in 6 years". I am starting to understand what they meant by this and it is a lot of the reason why I decided to give it a try. |
Wow...
Everybody is STILL confused...Nvidia is, by far, the easiest proprietary driver to install and configure. Why use package managers? It adds a layer that is, IMO, useless. The driver itself can, and does, uninstall nicely. So, I just use the NV*run file ONLY. Here's how to install a Nvidia driver:
How much easier CAN it get? |
I run a 64 bit system only and I never say yes to installing the 32 bit libraries. I've never had a problem running only the Nvidia binary.
|
Quote:
Quote:
Quote:
|
I agree that in theory is quite easy and in most cases I am sure that it is. In fact, installing the drivers in slackware is easier than it used to be in Ubuntu where you used to have to go through a whole process with depmod and insmod and the driver would clobber your wireless networking in the process. In simple terms there appears to be three major components: the kernel module, the driver, and xorg-conf and the .run file is supposed to modify all three of them. I had the experience of having something go wrong in the process and used an alternative method to success. I don't recall being asked if I want to download a module, but I do recall it running a build process. I am not certain of what part of the process went wrong but I haven't taken the time to investigate it thoroughly either. I am reasonably certain that I did not do anything unwarranted or make a procedural mistake.
|
Quote:
I thought that was already covered.Diferent kernels different xorg's in current it was a must to do a full unistall. do to the newer mesa and xorg lib's |
I got it awhile ago, sorry. I was so excited to get it working i played HoN for a week straight... :D I got it with the 2nd posts idea. So thank you, kind sir.
|
All times are GMT -5. The time now is 02:01 AM. |