Hi,
After updating to the new bundle of updates on -current, I have a strange issue.

OpenGL is somehow working, but some of KDE's effects complain that they cannot find OpenGL libs (wobbly windows, etc.)

At first I had forgotten to install the new glu- package. But even after installing it, and reinstalling NVIDIA 310.32 the issue is still present.

I've also tried NVIDIA 313.18 but no change.

What could it be??

Well, nvidia-switch not work properly now, because the GL version is changed.

In the nvidia-switch script:

should be:

Then, execute:

Reboot and enjoy!

Hmmm, something doesn't feel right here either. After turning off the GL "sync to vblank option" in nvidia-settings I'm getting around 2900fps from glxgears when I usually expect to see around 17000. Also, moving an openGL app window around ("/usr/libexec/xscreensaver/glknots -window") is excruciatingly slow under dwm (a no-frills basic window manager) and I'm seeing CPU SYS Time > 90%.

I'm using NVIDIA-Linux-x86_64-310.32.run, on 3.7.9 kernel, reinstalled after applying today's current updates.


update:

Well, I'm getting 17500fps again now from glxgears. Really don't know what was upsetting it earlier as I haven't changed anything and it just started working again (haven't even logged out of X11). Unless it happens again I'll write it off as a one-off weirdness.

hmm well, I've never used nvidia-switch nor the drivers package from SBo. I've always just downloaded the drivers from nvidia's website and run it as is. It moves the GL files that it has to move and everything works.

But this time something seems to be broken. Is is because Nvidia's drivers still don't support Mesa 9 ? Should I go back to mesa 8.0.4 ?

I've tried to run just nvidia-switch on top of manually installed drivers but nothing changed.

Nvidia moves mesa out of the way so it doesn't matter which mesa is installed.

That's not entirely true. The libGL library gets replaced by an accelerated version coming from the binary driver package, but there are other libraries in mesa that do make a difference. For instance the newly added libglapi.so. And the mesa application programming interface in /usr/include/GL is not removed either.

Eric

and after today's x86-64 update, I get black screen and unresponsive keyboard as X tries to start, curiously I also cannot start the machine in either run level 3 or 1 from a LILO prompt...the machine always shows INIT: entering runlevel 4...so I'm not able to get to a console to sort this out as it is...maybe I missed the memo...

How did you upgrade? Check http://docs.slackware.com/howtos:sla...:systemupgrade to see what you missed (did you install the new "glu" package? Did you re-install your binary Nvidia/Ati graphics driver if you had installed that before?)

Eric

Assuming your lilo label for slackware is "linux" then linux nomodeset vga=normal 3 at the lilo boot prompt should put you into runlevel 3 without any graphical entanglements.

If it's still running rc.4 even when you do that, then you must have broken your inittab.

Hi Eric, the upgrade was done in the correct slackpkg order/fashion and I wasn't using a proprietary ATI driver
cheers

then I must have broken inittab somehow because it still goes direct to runlevel 4...meh...I should be able to start the machine from an install disk and see what extra voodoo I might have typed into /etc/inittab when all I needed to do was erase a 3 and insert a 4...but all the same, I could start the machine manually to another runlevel prior to the upgrade to the 3.7.1 kernel...interesting....

libglapi is used internally and once the libGL is replaced by nvidia's version there is no longer a link to it
Also I haven't yet got the Slackware version so I can't see why it would have this extra lib as it is only required if you have enabled GL ES and can be disabled if that is not the case.

The includes are standardized as OpenGL is a standard so there is not much point in replacing them as only the copyright notice at the top would change.

I've tried to reinstall mesa 8.0.4 but the issue is still present, so I guess it's not about Mesa but maybe XOrg 1.13.2 itself.

But before getting too far I would like to know if any other can confirm the same issue, with nvidia drivers and the new set of XOrg/Mesa packages?

If it's just me, then it would be my fault.

There is no need for mesa libraties to link to it. The need is with the applications that dynamically link to it. I play a game which requires the presence of libglapi.so.

I asked Pat to build and add it (earlier versions of the mesa package did not enable it in the build configuration). Quoting:

[CODE]
[--enable-shared-glapi

By default, libGL has its own copy of libglapi. This options makes libGL use the shared libglapi. This is required if applications mix OpenGL and OpenGL ES.
/CODE]

Eric

No problems here.
I'm running all the latest packages posted last night, my time, and the Nvidia 310.19 drivers, in Slackware64-current with Xfce, and everything is working flawlessly... so far.
:-)