For the last week I've been using beta 270.26 and I'm happy to say this problem is corrected in that version. In addition, I also no longer get the X server corruption as shown here, http://www.nvnews.net/vbulletin/show...8&postcount=28
Furthermore, everytime I switch mplayer to fullscreen I get the following message, but it doesn't seem to have any ill effects:
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library 270.26 Mon Feb 14 01:49:57 PST 2011
VDPAU nvidia: Error detected 1 2407
Additional observations about 270.26:
I'm still having problems with Flash 10.2.x like everyone else, but I assume that problem lies elsewhere.
Sometimes when opening a video with mplayer I get X server pauses as described here, http://www.nvnews.net/vbulletin/showthread.php?t=157499
, and then if I look in /var/log/Xorg.0.log I have message blocks like this:
[ 88655.345] (II) XKB: reuse xkmfile /var/lib/xkb/server-DAEA4C886ED13CCB49EF0284D9D47E5611DB4ADA.xkm
[ 96002.616] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 96002.616] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef31b]
[ 96002.616] 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80ecb5b]
[ 96002.616] 2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80bd662]
[ 96002.616] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x4911) [0xb4ce7911]
[ 96002.616] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x4a06) [0xb4ce7a06]
[ 96002.616] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x5246) [0xb4ce8246]
[ 96002.616] 6: /usr/bin/X (0x8048000+0x62e7f) [0x80aae7f]
[ 96002.616] 7: /usr/bin/X (0x8048000+0x121b4e) [0x8169b4e]
[ 96002.616] 8: (vdso) (__kernel_sigreturn+0x0) [0xb7733400]
[ 96002.616] 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3fe748) [0xb5643748]
[ 96002.616] 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3fea91) [0xb5643a91]
[ 96002.616] 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3feb09) [0xb5643b09]
[ 96003.926] nvLock: client timed out, taking the lock
These freezes are a completely random event and can't be tied to any particular video. In summary, from a users point of view I'd say 270.26 it's much improved over the 260.xx series, but not quite back to the stability of 195.xx.