NVIDIA 260.19 Issues

English Applications
1

Hey guys,
I am an OpenSuse lover since 3 months. Today, I decided to install it again on my computer. I saw some strange things. My GPU is a NVIDIA GT 240 so i tried to install the drivers as I did three months ago. Two months ago, the version was 256.45 in NVIDIA repository and today the 260.19 is released. First, I installed Mumble and it worked great (I turned off the overlay) but when I install 260.19 driver, i can’t launch Mumble after. Here the results BEFORE and AFTER the driver installation

BEFORE with nouveau or 256.45 driver:

mumble
CELT bitstream 8000000b from /usr/lib/mumble/libcelt0.so.0.7.0
PulseAudio: Connection failure: Connection refused
Locale is fr_FR
TextToSpeech: Compiled without support for speech-dispatcher
*** WARNING *** The program 'mumble' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=mumble>
OpenSSL Support: 1
Overlay: Listening on "/home/cobramad/.MumbleOverlayPipe" 
Mumble(6138)/ KIconCache::Private::themeDirsChanged: Theme directory has been modified
GlobalShortcutX: Unable to open any keyboard input devices under /dev/input, falling back to XInput
GlobalShortcutX: Using XInput 2.0
GlobalShortcutX: XInput 4:Virtual core XTEST pointer
GlobalShortcutX: XInput 5:Virtual core XTEST keyboard
GlobalShortcutX: XInput 6:Power Button
GlobalShortcutX: XInput 7:Power Button
GlobalShortcutX: XInput 8:Logitech USB Gaming Mouse
GlobalShortcutX: XInput 9:Chicony Saitek Eclipse Keyboard
GlobalShortcutX: XInput 10:Chicony Saitek Eclipse Keyboard
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioOutput: Initialized
ALSAAudioOutput: Actual buffer 48000 hz, 1 channel 3072 samples [1024 per period]
ALSAAudioOutput: Initializing 1 channel, 48000 hz mixer
AudioOutput: Initialized 1 channel 48000 hz mixer
ALSAAudioInput: Initing audiocapture default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioInput: Releasing ALSA Mic.
ALSAAudioOutput: Destroyed
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioOutput: Initialized
ALSAAudioInput: Initing audiocapture default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
ALSAAudioOutput: Actual buffer 48000 hz, 1 channel 3072 samples [1024 per period]
ALSAAudioOutput: Initializing 1 channel, 48000 hz mixer
AudioOutput: Initialized 1 channel 48000 hz mixer
ALSAAudioInput: Releasing ALSA Mic.
ALSAAudioOutput: Destroyed
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioOutput: Initialized
ALSAAudioInput: Initing audiocapture default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
ALSAAudioOutput: Actual buffer 48000 hz, 1 channel 3072 samples [1024 per period]
ALSAAudioOutput: Initializing 1 channel, 48000 hz mixer
AudioOutput: Initialized 1 channel 48000 hz mixer
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioInput: Releasing ALSA Mic.
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioInput: Initing audiocapture default:CARD=Intel.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioInput: Releasing ALSA Mic.
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioInput: Initing audiocapture default:CARD=default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioInput: Releasing ALSA Mic.
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioInput: Initing audiocapture dsnoop:CARD=Intel,DEV=0.
ALSAAudio: snd_pcm_hw_params_set_format(capture_handle, hw_params, SND_PCM_FORMAT_S16): Argument invalide
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 3840 samples [480 per period]
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioInput: Initing audiocapture default:CARD=default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioInput: Releasing ALSA Mic.
ALSAAudioOutput: Destroyed
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioOutput: Initialized
ALSAAudioInput: Initing audiocapture default:CARD=default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
ALSAAudioOutput: Actual buffer 48000 hz, 1 channel 3072 samples [1024 per period]
ALSAAudioOutput: Initializing 1 channel, 48000 hz mixer
AudioOutput: Initialized 1 channel 48000 hz mixer
ALSAAudioInput: Releasing ALSA Mic.
ALSAAudioOutput: Destroyed

AFTER with the 260.19 version

mumble
Exception en point flottant (core dumped)

I use use the 32 bits OpenSuse 11.3 with KDE 4.4.5

It’s a very important problems so I think we could report it to the engineers but before that, I wanted to talk with the community.

For french people: Gros problèmes NVIDIA 260.19

Cheers

2

So the new nVidia proprietary video driver version 260.19 adds support for the new kernel 2.6.36 which was just released, though I have not yet tried to use it. The real question to you is of course, why did you upgrade your video driver? Unless you plan on installing the new kernel, I would have stuck with the older nVidia driver. Since a new kernel came out, I will most likely give it a try, on something I don’t mind reloading from scratch, if needed.

Thank You,

3

I didn’t decided to upgrade my driver. I just re-installed OpenSuse 11.3 and now the NVIDIA repository provides only the latest version (260.19).

4

Ypnose I didn’t decided to upgrade my driver. I just re-installed OpenSuse 11.3 and now the NVIDIA repository provides only the latest version (260.19).
Thanks for clarifying the situation. I would not have thought they would have released the new nVidia driver so soon. So I did take one computer down and installed the kernel 2.6.36 and then installed the new nVidia 260.19 video driver and it does all seem to be working. Mumble does not appear in the normal repositories to test out and I would not have a chat setup to use it anyway. Perhaps someone else that uses it can pipe in.

Thank You,

5

On Sat, 23 Oct 2010 01:36:02 +0530, Ypnose <Ypnose@no-mx.forums.opensuse.org> wrote:

> I didn’t decided to upgrade my driver. I just re-installed OpenSuse 11.3
> and now the NVIDIA repository provides only the latest version (260.19).

ha, i didn’t know that. time to switch back to the repo driver! thanks for letting me know…

–
phani.

6

Yes, dude. I tested the driver with Sauerbraten and it runs so good. The problem seems to be Mumble only.
Please test the Mumble (just check my link). It will show me if the problem is my computer or the driver. Don’t worry, the package is OK. I used it during three months.

software.opensuse.org: Résultats de recherche

7

On Sat, 23 Oct 2010 02:06:01 +0530, jdmcdaniel3 <jdmcdaniel3@no-mx.forums.opensuse.org> wrote:

> So I did take one
> computer down and installed the kernel 2.6.36 and then installed the new
> nVidia 260.19 video driver and it does all seem to be working. Mumble
> does not appear in the normal repositories to test out and I would not
> have a chat setup to use it anyway. Perhaps someone else that uses it
> can pipe in.

i’ve been using this driver for quite a while, more or less since it came out. i used to have trouble with nvidia drivers and the standard kernel a long while ago (Xorg kept eating most of my CPU cycles), and therefore switched to Kernel:/HEAD, solving that problem. since then i’ve been using the latest kernels. soon after beta versions of the new nvidia driver started to appear, and even though each of them was working to satisfaction, i kept updating to the newer drivers–had to recompile for each new kernel anyway.

i haven’t experienced any problems with kernel or video drivers; not even when others reported KDE crashing on them after installing versions of nvidia 260.19. i suspect my system is nvidia-friendly somehow.

intel core2 @ 2.93 GHz, 4 GB RAM
openSUSE 11.3, KDE 4.5.2 (factory repos)
GeForce 9400 GT, nvidia 260.19.12 (.run file from nvidia site; now i’m going to try the oS repo version)

only trouble i have is i can’t get virtualBox guests to run; most times i try, the whole system freezes the moment i try to start the guest. have been trying around with different settings & kernels, but so far i couldn’t get it to work. this isn’t something i really need, just playing around, so i don’t mind. and since i’m using several non-standard repos, i’m not really surprised either. not sure if this related to kernel and/or video configuration.

–
phani.

8

On Sat, 23 Oct 2010 02:36:03 +0530, Ypnose <Ypnose@no-mx.forums.opensuse.org> wrote:

> Please test the Mumble (just check my link). It will show me if the
> problem is my computer or the driver. Don’t worry, the package is OK. I
> used it during three months.

can i check this w/o having any game that uses mumble? and if yes, should i try with stable or unstable?

–
phani.

9

Yes you can. Just install the first package (stable) from my link and try to start the program. You don’t need to join a server. I just want to see if you can start it without any issues.
Thanks.

10

On Sat, 23 Oct 2010 03:36:01 +0530, Ypnose <Ypnose@no-mx.forums.opensuse.org> wrote:

>
> Yes you can. Just install the first package (stable) from my link and
> try to start the program. You don’t need to join a server. I just want
> to see if you can start it without any issues.
> Thanks.

installing … and … it works ok. i finished the audio adjustment (using pulseaudio), but canceled when it came to creating a certificate to use on public servers. didn’t see any problem, except that i could probably have gotten better adjustment had i opened pulseaudio volume control…

–
phani.

11

I think the new driver offers more than just support for the newer kernel. I note this from the nVidia site for the 260.19.12 driver: NVIDIA DRIVERS 260.19.12 Certified

  -   Added support for the following GPUs:
        GeForce GTS 450
        GeForce GTX 460M
        GeForce GT 415M
        GeForce GT 425M
        GeForce GT 420M
        GeForce GT 435M
        Quadro 2000
        Quadro 600

  • Stopped installing OpenGL, VDPAU, CUDA, and OpenCL header files with the driver. Those interested in these files can get them from their Linux distributions’ packages, where available, or upstream from:
    OpenGL header files (gl.h, glext.h glx.h, glxext.h):
    OpenGL® Registry

    VDPAU header files (vdpau.h and vdpau_x11.h):
    freedesktop.org - Software/VDPAU

    CUDA and OpenCL header files (cuda.h, cudaGL.h, cudaVDPAU.h,
    cl.h, cl_gl.h, cl_platform.h):
    NVIDIA GPU Computing Developer Home Page

    Note that while libvdpau.so is still included in 260.xx drivers, it will be removed from a future release series in early 2011. Distributors are encouraged to package libvdpau.so from freedesktop.org - Software/VDPAU

    Note that OpenGL® Registry does not presently provide gl.h or glx.h. Until that is resolved, NVIDIA’s OpenGL " header files can still be chosen, through the “–opengl-headers” installer option.

    • Fixed the CustomEDID X configuration option so that it can handle EDID files from Linux procfs; e.g., /proc/acpi/video/IGPU/LCD0/EDID.
    • Fixed an interaction problem with a change in X server behavior that caused slow text rendering on X.Org xserver 1.9.
    • Enhanced VDPAU to support interop with CUDA and OpenGL when Xinerama is active.
    • Fixed a bug in VDPAU that prevented temporal-spatial de-interlacing from operating when temporal de-interlacing was not also enabled.
    • Added support for configuring the dithering depth used when driving a flat panel with a GeForce 8 family or Quadro 4600/5600 or newer GPU. See the “Dithering Controls” in the Flat Panel page in nvidia-settings.
    • Added support for the nvcuvid API.

    nvcuvid provides a mechanism for decoding video and exposing the surfaces to CUDA, allowing applications to perform custom processing of the video. nvcuvid is primarily targeted at transcoding and video- processing applications. nvcuvid was already available on other platforms.

    By default, nvidia-installer places headers in /usr/include/nvcuvid, and library in /usr/lib/libnvcuvid.so, or in the appropriate library path for your system.

    • Fixed a bug in VDPAU that could cause a “display preemption” when toggling MPlayer to full-screen the first time.
    • Added OpenGL 4.1 support for Quadro Fermi, GeForce GTX 4xx, and later GPUs.
    • Enhanced VDPAU to fully support Xinerama.
    • Fixed a bug in the X driver that prevented operation of Xinerama when using multiple NVIDIA GPUs from different major hardware generations
      on X with ABI 4 or greater.
    • Fixed a bug in the OpenGL driver’s Xinerama support.

    Rendering should have ocurred to all physical X screens driven by an NVIDIA GPU compatible with the NVIDIA GPU driving physical X screen 0. However, if some physical X screen did not satisfy that requirement, then not only would that physical X screen not be rendered to (as expected), but also all physical X screens with a higher number would not be rendered to (which was unexpected).

    • Added GPU “Processor Clock” reporting to the nvidia-settings PowerMizer page.
    • Implemented support for SLI Mosaic Mode on Quadro FX 5800 and Quadro Fermi and newer Quadro GPUs.
    • Enhanced the VDPAU overlay-based presentation queue to allow it to be used when SLI is active, and in some cases when the X composite extension is enabled. See the README for further details.
    • Added support for configuring the dithering mode used when driving a flat panel with a GeForce 8 family or Quadro 4600/5600 or newer GPU.See the “Dithering Controls” in the Flat Panel page in nvidia-settings.
    • Added unofficial GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
      GL_EXT_texture_integer
      GL_ARB_stencil_two_side
      GL_EXT_transform_feedback2
      GL_NV_transform_feedback2
      GL_NV_conditional_render
    • Added GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
      GL_NV_point_sprite
      GL_EXT_stencil_two_side
      GL_EXT_point_parameters
      GL_ARB_transpose_matrix
      GL_EXT_framebuffer_blit
      GL_EXT_framebuffer_multisample
    • GLX protocol for the following OpenGL extension is promoted from unofficial GLX ptotocol to ARB approved GLX protocol:
      GL_EXT_geometry_shader4
      GL_ARB_shader_objects
      GL_ARB_vertex_shader
      GL_ARB_fragment_shader
    • Added support for configuring individual displays as any eye in passive stereo mode “4” when using TwinView or SLI Mosaic through extensions to the MetaMode syntax.
      *] Added ColorSpace and ColorRange features for HDMI. These give the ability to output YUV over HDMI and select full/reduced color range on RGB over HDMI. ColorSpace and ColorRange are X Configuration options and can be changed dynamically through nvidia-settings.
12

Wow, that is an impressive list of fixes and enhancements in the nVidia driver version 260.19 there oldcpu. I have another thread on the new kernel 2.6.36 and so I put a pointer there to your nVidia listing here for reference. I also have installed this new driver on two PC’s with the new kernel and so far no problems, but it is hard to test everything in a single night.

Thanks for the information.

Thank You,

13

I note on the nVidia forum an openSUSE-11.3 user reported a bug with this new driver and a recent KDE-4.5.1: KDE4 4.5.1 plasma-desktop fails with 260.19 - nV News Forums

To quote:

Edit : the bug ‘may’ be with KDE-4.5.x and not the graphic driver.

14

oldcpu I note on the nVidia forum an openSUSE-11.3 user reported a bug with this new driver and a recent KDE-4.5.1: KDE4 4.5.1 plasma-desktop fails with 260.19 - nV News Forums
That is very interesting oldcpu. As luck would have it, I have been running KDE 4.4.4 on everything. I have no intentions of moving up until I see what openSUSE 11.4 does with KDE and I will decide my fate then as to the KDE version I will be running, perhaps 4.6 by then.

Thank You,

15

I installed the new Nvidia driver from the repo on two 11.3 KDE 4.4 machines. No problems on either machine so far. The most taxing thing it’s done so far is play Minecraft.
Since it was in the Nvidia repo I figured it’s stable. I am running “2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux”
glxgears runs about like it always has.

I still get the occasional xorg caused momentary intermittent hitches.

16

It appears other problems are being reported with the 260.19 driver: 260.19.06 regression - nV News Forums

From that thread:

… so not all is solved yet .

As often is the case with new drivers, one needs to consider one’s requirements, and then do some investigations to see where the problems still lay to see if the problems are important for one’s use.

17

I am not happy at all with this driver. “Present Windows” which I use a lot to switch between applications is quite choppy and … no fun. No idea what other problems might show up. Meh.

18

How would one roll back if they were using the Nvidia repo for 11.3?

19

If the driver is not on the repos, then its not so easy.

I always install/build the driver ‘the hardway’ (which is not hard) and keep a copy of the older .run file drivers on my PC.

20

Would what Sagemta described here still apply: Nvidia for Newbies part 1 ?
Only with the previous drivers (256.53??)