On Wed, 2009-05-27 at 21:16 +0000, VintagePC wrote:
> I think I’ve found the cause.
> Normally, executing an .so file results in version information being
…so files normally DO NOT have an entry point defined. At least not on
Linux (from my experience). So if Nvidia’s .so files are designed to be
executable, that’s news to me… it may well be true. The only platform
where I saw this technique done was AIX, but they really didn’t
have .so’s is the same sense of the word.
> However, running any of the associated NVIDIA GL files produces a
> I have also noted that if I install the RPM packages from nvidia, then
> 3Ddiag DOES find the board, but still indicates I’m using MESA.
While it is very true that the best 3D acceleration is found using
Nvidia boards, it is equally true that they release often and often with
a TON of bugs… such is the beast when you operate as a rogue away from
the other kernel developers. Nvidia drivers are right/wrong/who knows?
Nvidia is NO different from Microsoft, well… that’s not true,
Microsoft actually has some open source stuff now… sigh. I like
Nvidia’s technology, but they’re hiding something that has to be HUGE
(in a bad way) for them to not do what AMD is trying to do.
Long term, we’ll all switch to AMD for the best quality and
performance… but it may still be a couple of years off. And that
assumes that AMD can stay alive, which doesn’t look promising from here.
Intel’s got some surprises up its sleeve for this year… they could be
the sleeper hit that puts them all to shame… we’ll see.
So… I guess, we’ll all likely move to Intel… but that’s banking on
some unreleased surprises… will know more in a year or so. Intel is
holding a LOT of “cards”, so they aren’t compelled to release to much
Back to Nvidia drivers. I usually do try the ones that openSUSE
packages at first, but because Nvidia is notoriously buggy, sometimes
you NEED to go backward in order to get something that works right… so
I usually end up pulling drivers straight from Nvidia eventually.