blech.
Why? cause when I update things break, when I use the stuff in repos, stuff breaks less often when I update.
This time X refused to load the newest nvidia driver, probably because the location that X in etch expects modules is different than the place nvidia puts em. I did not investigate further.
Note the driver from the repo *IS* the nvidia binary, 1.0-8776, a little old, but I see no reason it would work any differently than the 1.0-8776 driver from nvidia's website.
I think debian just makes a deb for the nvidia stuff, without changing it.
If nvidia's latest driver "just worked" as it used to, I'd be using it. But alas its doing something wrong from the eyes of my debian/etch machine, and I doubt that is the problem in the first place, though I guess I should figure out why the thing does not work on my machine... if only there was more time.
.b.
chris clepper wrote:
On 1/26/07, *B. Bogart* <ben@ekran.org mailto:ben@ekran.org> wrote:
Hey all, I changed from nvidia's binary driver to the one in the etch repo (8776).Why? Only the Nvidia binary actually uses the GPU for rendering.
Gem compiles (anon cvs update from today), but PD wont load it: /usr/lib/pd/extra/Gem.pd_linux: /usr/lib/pd/extra/Gem.pd_linux: undefined symbol: glUniform2iThis was covered in the two previous postings to this list. You need non busted drivers with OpenGL 2.0 support. The NV binaries certainly work.