MulletRobZ Posted December 30, 2003 Share Posted December 30, 2003 Greetings. Today, I noticed that this version of the NVidia Drivers is currently available, but I don't know if I should use those or the old 3123 drivers. Perhaps someone could tell me how the new drivers run and what I should do after editing the XF86Config file if I can't access the X server upon reboot. Link to comment Share on other sites More sharing options...
CaKeY Posted December 30, 2003 Share Posted December 30, 2003 Sweet! I've been having lockup problems with UT and UT2k3 using the 44.96's. I'll try these out asap. Link to comment Share on other sites More sharing options...
MG-Cloud Posted December 30, 2003 Share Posted December 30, 2003 I've read mixed reports on these - some people say it doubles their performance, others aren't even able to start x ;) That's why I'm sticking with my current ones (4496) until I can get some more conclusive reports. How did they work for you guys? Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted December 30, 2003 Veteran Share Posted December 30, 2003 I just tried them. I d/l the new 5328 version for IA32 platform, and exited X with init 3. From the console, I executed the .run file (after chmoding it, of course) and the license screen came up. I accepted. The screen switched to the "install" screen. And then... then... it just hung there... :pinch: No indication of what it was trying to do, or what the hang-up was. :no: AFAIK, using init 3 to quit X is valid. I did a CRTL-c to kill the program, and it died without incident. init 5 got x runnign again, and I am back to where I was before. Is there a different way that this should be done? Otherwise, I would add a "didn't seem to extract" to the list of problems. :rofl: Link to comment Share on other sites More sharing options...
MG-Cloud Posted December 30, 2003 Share Posted December 30, 2003 You may want to try these patches: http://www.minion.de/nvidia.html The patches are mainly for 2.6, but they do fix a problem with 2.4 on newer Via chipsets If you find that 1.0-5328 hangs on X startup on a newer Via chipset, please download the current 2.6 patch for this release. This bug is not specific to Linux 2.6. Link to comment Share on other sites More sharing options...
MulletRobZ Posted December 30, 2003 Author Share Posted December 30, 2003 Well I'm just going to scan some pictures for yearbook, get my data backed up, and wipe out my entire system before I do this. My Windows 2000 partition is absolutely f***ed up, LOL! :D And if I get the new NVidia to work, then I'll practice installing the new 2.6 kernel on Slackware 9.0 just for the heck of it! Link to comment Share on other sites More sharing options...
MG-Cloud Posted December 30, 2003 Share Posted December 30, 2003 :D I can't wait for people to post results, so I'm going to be installing the new nvidia drivers as soon as my gcc compile is done. Will let you know the results (along with a glxgears before and after, assuming after will work ;P) Link to comment Share on other sites More sharing options...
Xe|oN Posted December 30, 2003 Share Posted December 30, 2003 I've been running 5328 since the day they came out and they are fine for me. I am running the 2.6 kernel and patched using the patches available from minion.de so I highly suggest, as MG-Cloud did that you do this even if on a 2.4 kernel. As for performance, well if only I could remember how well glxgears ran in my previous 4496 and 4620 but 3D performance seems pretty good. No worse than before. One thing they don't have is the nice nvidia-settings program like 4620 did, but then again that wasn't an official driver release. Link to comment Share on other sites More sharing options...
JadeWolf324 Posted December 30, 2003 Share Posted December 30, 2003 ill stick with the ones i got....did they upgrade the info on MDK 9.2 so i dont hafta have the headers and source and all that mess? Link to comment Share on other sites More sharing options...
MG-Cloud Posted December 30, 2003 Share Posted December 30, 2003 Dunno about MDK, sorry. For me, the drivers have absolutely *zero* effect. The glxgears scores before and after are pretty much identical ;) Link to comment Share on other sites More sharing options...
JiveMasterT Posted December 31, 2003 Share Posted December 31, 2003 as far as i know those drivers are only for linux? can someone hit me up with a windows download if im wrong? im trying every new driver that comes along cause i have that icon changing problem on my desktop. bleh. *edit* and i am a stupid boy for i have come to realize that this IS under the linux distros section. my apologies. Link to comment Share on other sites More sharing options...
MulletRobZ Posted January 6, 2004 Author Share Posted January 6, 2004 What the hell? These freakin' drivers will not install on my system because it could not find the so-called Kernel headers! I'm running Slackware 9.0 with the standard kernel 2.4.20. How can I find these kernel headers and if not, I guess I'll have to do an attempt to install Kernel 2.6.0. Link to comment Share on other sites More sharing options...
MrStaticVoid Posted January 6, 2004 Share Posted January 6, 2004 First off, make sure you have /usr/src/linux-<KV> symlinked to /usr/src/linux. If it still needs kernel headers, cp -R /usr/src/linux/include/linux /usr/include/ and that should do it :). Link to comment Share on other sites More sharing options...
MulletRobZ Posted January 6, 2004 Author Share Posted January 6, 2004 Ah. So that would be the answer to the problem. The only thing is that there isn't even a /usr/src/linux directory for some strange reason. :s The only directory in /usr/src is rpm. So now what do I do since Slackware does not include /usr/src/linux? EDIT: There is a directory called /usr/include/linux, but it's only 3.4 MB and if I'm not mistaken, the kernel source has to be at least 50 MB, right? Link to comment Share on other sites More sharing options...
MrStaticVoid Posted January 7, 2004 Share Posted January 7, 2004 /usr/include/linux is your kernel headers, but you need full Linux sources to compile the module (or any module for that matter). Not only do you need the sources, but your kernel must have been compiled from those sources. So, get the sources and recompile your kernel (don't forget the /usr/src/linux symlink). Then try compiling the driver again. Link to comment Share on other sites More sharing options...
MulletRobZ Posted January 7, 2004 Author Share Posted January 7, 2004 So in other words, I might as well just give 2.6.0 a shot. BTW, does the tarball have to be extracted in /usr/src or can I just use my regular /root directory? Link to comment Share on other sites More sharing options...
metal_dragen Veteran Posted January 7, 2004 Veteran Share Posted January 7, 2004 Technically you can put it wherever you want as long as it's symlinked to /usr/src/linux, but it's traditional and probably better to put it in /usr/src Link to comment Share on other sites More sharing options...
MulletRobZ Posted January 7, 2004 Author Share Posted January 7, 2004 Never mind the kernel upgrade for now. I just had to add the --kernel-include-path /usr/include to the command to run the NVidia installer and it worked fine. As a matter of fact, better than 3123. But thank you all for your information. Link to comment Share on other sites More sharing options...
Recommended Posts