|
|
#1 | |
|
Registered User
Join Date: Jul 2007
Posts: 38
|
Hi, the nvidia installer has a bad reputation for overwriting existing files (e.g. /usr/include/GL/gl.h and /usr/lib/xorg/modules/extensions/libglx.so), which has the undesirable side-effects of stopping xorg from compiling, mucking up the distro's package manager by not informing it of changed files, and generally confusing newbies with FUD.
So, why the need to overwrite *any* files? Surely it is possible to agree a convention with xorg, e.g. use nvidia-gl.h rather than clobbering the existing gl.h ("--no-opengl-headers" is not the solution). |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Nov 2006
Posts: 37
|
Standard answer #23: Use correct packages for your distribution to install the Nvidia driver. (I don't mean to offend... that's just what these Fedorabuntu type pricks always say)
... and just how is nvidia-gl.h going to be found by build configuration systems that look for gl.h? Are they all going to have to be rewritten? This is obviously why they replace it. Personally I'm glad that Nvidia provides us with a complete interface to their OpenGL libraries. Why is --no-opengl-headers not the solution, if you don't want the opengl headers to get installed? What the heck should the xorg build be doing going for the openGL headers installed on your system during the build anyways? Do you not point the x11-server build to the location of the MESA source tree so it can compile the back end? It doesn't even install the headers at that stage. You (or at least, I) compile and install MESA stuff in a subsequent step (e.g. make linux-dri). Oh wait, I see. You were compiling Xorg using Fedora's SRCRPMs. I read a little further in your fedora forum link and I see what it's including in the compile command. They should not be doing that. Distributions like Fedora and Ubuntu have their own (silly) ways of doing things that deviate from traditional practices. So yes, installing and uninstalling "third party drivers" can cause problems. I would say that it's them who are causing the problems. That's why I don't eat that dog food. As for FUD, that just comes from certain free software zealots. Others just get on with their work and lives, and realize that if you want good support for your graphics card, it's necessary to install proprietary drivers. (Yes, it certainly would be "nice" if everyone opened their source and hardware specs. Don't get me wrong, I'd be very happy. It just isn't going to happen.) Saying "use our packages to install third party drivers" isn't really FUD though. |
|
|
|
|
|
|
#3 | |
|
Registered User
Join Date: Jul 2007
Posts: 38
|
Quote:
Because they *should* be installed. Only, they should not *overwrite* the existing files. There's plenty of room in a Linux filesystem for new files. |
|
|
|
|
|
|
#4 | |
|
Unbuffered User
Join Date: Jun 2005
Posts: 388
|
(er, nevermind.)
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Nov 2006
Posts: 37
|
You've got a good idea, mind you, but there are a few things that make it impractical for Nvidia to do.
1) If you want to link against the library, the headers must be found. 2) If existing binaries (and there are a lot of games that can't be recompiled and linked) are to work with the Nvidia driver, they must be able to load libGl.so.1 and friends that point to the Nvidia opengl libraries. When ldconfig is run, it must not move the symlinks back to the mesa libraries either. This is why they are yanked out of the way. 3) Distributors aren't exactly sticking with xorg defaults for the locations of files, or even doing everything consistently. (e.g. "/usr/lib/dri") Who better to arrange the tomfoolery so that Xorg DRI and Nvidia OpenGL can coexist, and the package managers are aware of the changes, but the distributors themselves, then? The same goes with the includes, if they want to keep the option of compiling against mesa. (though to me the solution to that is to NOT replace the gl includes. Stuff compiled against Mesa would usually still work with Nvidia's OpenGL at runtime, at least in my experiences.) That's all I'm trying to say here. |
|
|
|
|
|
#6 | ||
|
Registered User
Join Date: Jul 2007
Posts: 38
|
Quote:
Quote:
![]() |
||
|
|
|
|
|
#7 | ||
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Quote:
Quote:
Edit: I don't think zealotry has anything to do with it, and I wouldn't accuse anyone of spreading FUD here. |
||
|
|
|
|
|
#8 |
|
Registered User
Join Date: Jul 2007
Posts: 38
|
Looks like nothing ("In particular, Andy's response about why they're uninterested in a common libGL is basically The Last Word on the subject.") came of this thread. Presumably a death by committee.
I suppose, at least, Windows is in pretty much the same situation - nvidia & ati drivers will conflict there (with uninstall & reboot cycles needed), but it's much less user-visible, because the vast majority of users don't compile a single thing. |
|
|
|
![]() |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| NVIDIA CORP Files SEC form 10-Q, Quarterly Report | News | Latest Tech And Game Headlines | 0 | 05-24-12 02:50 AM |
| Need Help Installing NVIDIA Tesla M2070Q in Linux RHEL5 | Ferianto85 | NVIDIA Linux | 0 | 05-18-12 08:35 PM |
| Getting the proprietary nvidia driver to run with Debian 3.0 r0 (woody) | Katchina404 | NVIDIA Linux | 9 | 01-12-03 08:49 AM |