poor graphics performance with nvidia-current in maverick

[dorpm]

With the actual nvidia-current which obviously contains the driver 260.19.06 the graphics performance with my Nvidia 9500 GT is much slower than it was in Lucid. Especially the vdpau device seems not to work. In mplayer I see no difference if I use vdpau output or X11. vdpau-va-driver is installed!

Regards,
Florian

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nvidia-current 260.19.06-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Wed Dec 15 18:26:59 2010
DkmsStatus:
 vboxhost, 3.2.12, 2.6.35-23-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.35-23-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.32-25-generic, x86_64: built
 nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: built
GdmLog: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7369
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=c8585acb-f3ce-44e4-ae62-a499b5b1c647 ro quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers
dmi.bios.date: 03/17/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.9
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7369
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.9:bd03/17/2009:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7369
dmi.product.version: 1.0
dmi.sys.vendor: MSI
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-23-generic

[Pasi Savolainen (pasi.savolainen)]

I also failed to get VDPAU acceleration on 10.10. The fix was to create a link to /usr/lib/nvidia-current/vdpau/libvdpau_nvidia.so in /usr/lib (it already existed in /usr/lib32) like so:

sudo ln -s /usr/lib/nvidia-current/vdpau/libvdpau_nvidia.so /usr/lib/libvdpau_nvidia.so

After this, both xbmc (Dharma) and "mplayer -vo vdpau" seemed to use vdpau OK.
Prior to fix, the error was: "Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory".

AFAIK this affects 64bit systems only.

[dorpm (dorpmueller)]

Obviously a still existing bug for cooperation of nvidia and xorg 1.9. I reverted to xorg of Lucid and received much more performance (see also http://ubuntuforums.org/showpost.php?p=9874780&postcount=12).

Hopefully this bug disappears soon!

Regards,
Florian

[bugbot (bugbot)]

Hey dorpm,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.