Vdpau and full screen youtube problems on Nvidia Quadro NVS 140M

I have Nvidia NVS 140M on 64-bit Arch. I am trying to find perfect configuration for my Thinkpad with no luck.
I used to have nouveau drivers, now using nvidia-173xx. The problems are following:
1) YouTube videos:
- with nouveau I was not able to watch any video (it was like a slideshow)
- with nvidia everything works fine.
I'd prefer nouveau than nvidia, because of KMS.
2) Glxgears
As far as I remember, you can check if acceleration is working, using this tool - CPU usage should be not changed after glxgears started. On both drivers (nouveau and nvidia) running glxgears process uses 100% CPU.
3) vdpau
According to this thread, my card supports vdpau. I can not make it to work.
Additional information:
thinkpad ~ $ pacman -Qs nvidia
local/lib32-libvdpau 0.4.1-3
Nvidia VDPAU library (32-bit)
local/libvdpau 0.4.1-1
Nvidia VDPAU library
local/nvidia-173xx 173.14.28-3
NVIDIA drivers for kernel26, 173xx branch.
local/nvidia-173xx-utils 173.14.28-1
NVIDIA drivers utilities and libraries, 173xx branch.
thinkpad ~ $ vainfo
libva: libva version 0.31.1
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/nvidia_drv_video.so
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
libva error: /usr/lib/dri/nvidia_drv_video.so init failed
libva: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
thinkpad ~ $ cat /etc/X11/xorg.conf.d/20-nvidia.conf
Section "Module"
Load "glx"
Disable "dri"
Disable "dri2"
EndSection
Section "Device"
Identifier "Default nvidia Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
thinkpad ~ $ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_NV_float_buffer, GLX_ARB_fbconfig_float,
GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap,
GLX_EXT_framebuffer_sRGB, GLX_NV_present_video
GLX version: 1.3
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro NVS 140M/PCI/SSE2
OpenGL version string: 2.1.2 NVIDIA 173.14.28
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
OpenGL extensions:
GL_ARB_color_buffer_float, GL_ARB_depth_texture, GL_ARB_draw_buffers,
GL_ARB_fragment_program, GL_ARB_fragment_program_shadow,
thinkpad ~ $ cat /var/log/Xorg.0.log
[ 2830.098]
X.Org X Server 1.9.4
Release Date: 2011-02-04
[ 2830.098] X Protocol Version 11, Revision 0
[ 2830.099] Build Operating System: Linux 2.6.37-ARCH x86_64
[ 2830.099] Current Operating System: Linux thinkpad 2.6.37-ARCH #1 SMP PREEMPT Tue Mar 8 08:34:35 CET 2011 x86_64
[ 2830.099] Kernel command line: root=/dev/sda3 ro
[ 2830.100] Build Date: 04 February 2011 09:38:18PM
[ 2830.100]
[ 2830.100] Current version of pixman: 0.20.2
[ 2830.101] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2830.101] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2830.103] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 12 21:24:44 2011
[ 2830.104] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2830.104] (==) No Layout section. Using the first Screen section.
[ 2830.104] (==) No screen section available. Using defaults.
[ 2830.104] (**) |-->Screen "Default Screen Section" (0)
[ 2830.104] (**) | |-->Monitor "<default monitor>"
[ 2830.105] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2830.105] (**) | |-->Device "Default nvidia Device"
[ 2830.105] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2830.105] (==) Automatically adding devices
[ 2830.105] (==) Automatically enabling devices
[ 2830.105] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2830.105] Entry deleted from font path.
[ 2830.105] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2830.105] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2830.105] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2830.105] (II) Loader magic: 0x7d3b20
[ 2830.105] (II) Module ABI versions:
[ 2830.105] X.Org ANSI C Emulation: 0.4
[ 2830.105] X.Org Video Driver: 8.0
[ 2830.105] X.Org XInput driver : 11.0
[ 2830.105] X.Org Server Extension : 4.0
[ 2830.108] (--) PCI:*(0:1:0:0) 10de:0429:17aa:20d8 rev 161, Mem @ 0xd6000000/16777216, 0xe0000000/268435456, 0xd4000000/33554432, I/O @ 0x00002000/128
[ 2830.108] (II) Open ACPI successful (/var/run/acpid.socket)
[ 2830.108] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[ 2830.108] (WW) "dri2" will not be loaded unless you've specified it to be loaded elsewhere.
[ 2830.108] (II) "extmod" will be loaded by default.
[ 2830.108] (II) "dbe" will be loaded by default.
[ 2830.108] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 2830.108] (II) "record" will be loaded by default.
[ 2830.108] (II) "dri" will be loaded even though the default is to disable it.
[ 2830.108] (II) "dri2" will be loaded even though the default is to disable it.
[ 2830.108] (II) LoadModule: "glx"
[ 2830.109] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2830.118] (II) Module glx: vendor="NVIDIA Corporation"
[ 2830.118] compiled for 4.0.2, module version = 1.0.0
[ 2830.118] Module class: X.Org Server Extension
[ 2830.118] (II) NVIDIA GLX Module 173.14.28 Wed Sep 29 10:19:01 PDT 2010
[ 2830.118] (II) Loading extension GLX
[ 2830.118] (II) LoadModule: "extmod"
[ 2830.118] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2830.118] (II) Module extmod: vendor="X.Org Foundation"
[ 2830.118] compiled for 1.9.4, module version = 1.0.0
[ 2830.119] Module class: X.Org Server Extension
[ 2830.119] ABI class: X.Org Server Extension, version 4.0
[ 2830.119] (II) Loading extension MIT-SCREEN-SAVER
[ 2830.119] (II) Loading extension XFree86-VidModeExtension
[ 2830.119] (II) Loading extension XFree86-DGA
[ 2830.119] (II) Loading extension DPMS
[ 2830.119] (II) Loading extension XVideo
[ 2830.119] (II) Loading extension XVideo-MotionCompensation
[ 2830.119] (II) Loading extension X-Resource
[ 2830.119] (II) LoadModule: "dbe"
[ 2830.119] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2830.119] (II) Module dbe: vendor="X.Org Foundation"
[ 2830.119] compiled for 1.9.4, module version = 1.0.0
[ 2830.119] Module class: X.Org Server Extension
[ 2830.119] ABI class: X.Org Server Extension, version 4.0
[ 2830.119] (II) Loading extension DOUBLE-BUFFER
[ 2830.119] (II) LoadModule: "record"
[ 2830.119] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2830.119] (II) Module record: vendor="X.Org Foundation"
[ 2830.119] compiled for 1.9.4, module version = 1.13.0
[ 2830.119] Module class: X.Org Server Extension
[ 2830.119] ABI class: X.Org Server Extension, version 4.0
[ 2830.119] (II) Loading extension RECORD
[ 2830.119] (II) LoadModule: "nvidia"
[ 2830.119] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2830.120] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2830.120] compiled for 4.0.2, module version = 1.0.0
[ 2830.120] Module class: X.Org Video Driver
[ 2830.120] (II) NVIDIA dlloader X Driver 173.14.28 Wed Sep 29 10:00:06 PDT 2010
[ 2830.120] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2830.120] (--) using VT number 7
[ 2830.124] (II) Loading sub module "fb"
[ 2830.124] (II) LoadModule: "fb"
[ 2830.124] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2830.124] (II) Module fb: vendor="X.Org Foundation"
[ 2830.124] compiled for 1.9.4, module version = 1.0.0
[ 2830.124] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2830.124] (II) Loading sub module "wfb"
[ 2830.125] (II) LoadModule: "wfb"
[ 2830.125] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2830.125] (II) Module wfb: vendor="X.Org Foundation"
[ 2830.125] compiled for 1.9.4, module version = 1.0.0
[ 2830.125] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2830.125] (II) Loading sub module "ramdac"
[ 2830.125] (II) LoadModule: "ramdac"
[ 2830.125] (II) Module "ramdac" already built-in
[ 2830.125] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2830.125] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 2830.125] (==) NVIDIA(0): RGB weight 888
[ 2830.125] (==) NVIDIA(0): Default visual is TrueColor
[ 2830.125] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2830.125] (**) NVIDIA(0): Option "NoLogo" "True"
[ 2830.125] (**) NVIDIA(0): Enabling RENDER acceleration
[ 2830.125] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 2830.126] (II) NVIDIA(0): enabled.
[ 2834.780] (II) NVIDIA(0): NVIDIA GPU Quadro NVS 140M (G86GL) at PCI:1:0:0 (GPU-0)
[ 2834.780] (--) NVIDIA(0): Memory: 524288 kBytes
[ 2834.780] (--) NVIDIA(0): VideoBIOS: 60.86.3e.00.00
[ 2834.780] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 2834.780] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 2834.780] (--) NVIDIA(0): Connected display device(s) on Quadro NVS 140M at PCI:1:0:0:
[ 2834.781] (--) NVIDIA(0): LEN (DFP-0)
[ 2834.781] (--) NVIDIA(0): LEN (DFP-0): 330.0 MHz maximum pixel clock
[ 2834.781] (--) NVIDIA(0): LEN (DFP-0): Internal Dual Link LVDS
[ 2834.785] (WW) NVIDIA(0): The EDID for LEN (DFP-0) contradicts itself: mode "1280x800"
[ 2834.785] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 2834.785] (WW) NVIDIA(0): HorizSync range (42.088-49.305 kHz) would exclude this
[ 2834.785] (WW) NVIDIA(0): mode's HorizSync (32.9 kHz); ignoring HorizSync check for
[ 2834.785] (WW) NVIDIA(0): mode "1280x800".
[ 2834.785] (WW) NVIDIA(0): The EDID for LEN (DFP-0) contradicts itself: mode "1280x800"
[ 2834.785] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 2834.785] (WW) NVIDIA(0): VertRefresh range (52.000-60.000 Hz) would exclude this
[ 2834.785] (WW) NVIDIA(0): mode's VertRefresh (39.9 Hz); ignoring VertRefresh check
[ 2834.785] (WW) NVIDIA(0): for mode "1280x800".
[ 2834.785] (WW) NVIDIA(0): The EDID for LEN (DFP-0) contradicts itself: mode "1280x800"
[ 2834.785] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 2834.785] (WW) NVIDIA(0): HorizSync range (42.088-49.305 kHz) would exclude this
[ 2834.785] (WW) NVIDIA(0): mode's HorizSync (32.9 kHz); ignoring HorizSync check for
[ 2834.785] (WW) NVIDIA(0): mode "1280x800".
[ 2834.785] (WW) NVIDIA(0): The EDID for LEN (DFP-0) contradicts itself: mode "1280x800"
[ 2834.785] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 2834.785] (WW) NVIDIA(0): VertRefresh range (52.000-60.000 Hz) would exclude this
[ 2834.785] (WW) NVIDIA(0): mode's VertRefresh (39.9 Hz); ignoring VertRefresh check
[ 2834.785] (WW) NVIDIA(0): for mode "1280x800".
[ 2834.787] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 2834.787] (==) NVIDIA(0):
[ 2834.787] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 2834.787] (==) NVIDIA(0): will be used as the requested mode.
[ 2834.787] (==) NVIDIA(0):
[ 2834.787] (II) NVIDIA(0): Validated modes:
[ 2834.787] (II) NVIDIA(0): "nvidia-auto-select"
[ 2834.787] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 800
[ 2836.069] (--) NVIDIA(0): DPI set to (98, 96); computed from "UseEdidDpi" X config
[ 2836.069] (--) NVIDIA(0): option
[ 2836.069] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 2836.069] (--) Depth 24 pixmap format is 32 bpp
[ 2836.074] (II) NVIDIA(0): Initialized GPU GART.
[ 2836.084] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 2836.968] (II) Loading extension NV-GLX
[ 2837.035] (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
[ 2837.037] (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
[ 2837.037] (==) NVIDIA(0): Backing store disabled
[ 2837.037] (==) NVIDIA(0): Silken mouse enabled
[ 2837.040] (==) NVIDIA(0): DPMS enabled
[ 2837.040] (II) Loading extension NV-CONTROL
[ 2837.041] (==) RandR enabled
[ 2837.041] (II) Initializing built-in extension Generic Event Extension
[ 2837.041] (II) Initializing built-in extension SHAPE
[ 2837.041] (II) Initializing built-in extension MIT-SHM
[ 2837.041] (II) Initializing built-in extension XInputExtension
[ 2837.041] (II) Initializing built-in extension XTEST
[ 2837.041] (II) Initializing built-in extension BIG-REQUESTS
[ 2837.041] (II) Initializing built-in extension SYNC
[ 2837.041] (II) Initializing built-in extension XKEYBOARD
[ 2837.041] (II) Initializing built-in extension XC-MISC
[ 2837.041] (II) Initializing built-in extension SECURITY
[ 2837.041] (II) Initializing built-in extension XINERAMA
[ 2837.042] (II) Initializing built-in extension XFIXES
[ 2837.042] (II) Initializing built-in extension RENDER
[ 2837.042] (II) Initializing built-in extension RANDR
[ 2837.042] (II) Initializing built-in extension COMPOSITE
[ 2837.042] (II) Initializing built-in extension DAMAGE
[ 2837.042] (II) Initializing extension GLX
[ 2837.204] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 2837.204] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2837.204] (II) LoadModule: "evdev"
[ 2837.204] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2837.205] (II) Module evdev: vendor="X.Org Foundation"
[ 2837.205] compiled for 1.9.4, module version = 2.6.0
[ 2837.205] Module class: X.Org XInput Driver
[ 2837.205] ABI class: X.Org XInput driver, version 11.0
[ 2837.205] (**) Power Button: always reports core events
[ 2837.205] (**) Power Button: Device: "/dev/input/event4"
[ 2837.216] (--) Power Button: Found keys
[ 2837.216] (II) Power Button: Configuring as keyboard
[ 2837.216] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2837.216] (**) Option "xkb_rules" "evdev"
[ 2837.216] (**) Option "xkb_model" "evdev"
[ 2837.216] (**) Option "xkb_layout" "us"
[ 2837.264] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 2837.264] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 2837.264] (**) Video Bus: always reports core events
[ 2837.264] (**) Video Bus: Device: "/dev/input/event3"
[ 2837.279] (--) Video Bus: Found keys
[ 2837.279] (II) Video Bus: Configuring as keyboard
[ 2837.279] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 2837.279] (**) Option "xkb_rules" "evdev"
[ 2837.280] (**) Option "xkb_model" "evdev"
[ 2837.280] (**) Option "xkb_layout" "us"
[ 2837.284] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 2837.284] (II) No input driver/identifier specified (ignoring)
[ 2837.284] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 2837.284] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 2837.284] (**) Sleep Button: always reports core events
[ 2837.284] (**) Sleep Button: Device: "/dev/input/event2"
[ 2837.306] (--) Sleep Button: Found keys
[ 2837.306] (II) Sleep Button: Configuring as keyboard
[ 2837.306] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 2837.306] (**) Option "xkb_rules" "evdev"
[ 2837.306] (**) Option "xkb_model" "evdev"
[ 2837.306] (**) Option "xkb_layout" "us"
[ 2837.312] (II) config/udev: Adding input device Logitech USB Laser Mouse (/dev/input/event9)
[ 2837.312] (**) Logitech USB Laser Mouse: Applying InputClass "evdev pointer catchall"
[ 2837.312] (**) Logitech USB Laser Mouse: always reports core events
[ 2837.312] (**) Logitech USB Laser Mouse: Device: "/dev/input/event9"
[ 2837.333] (--) Logitech USB Laser Mouse: Found 12 mouse buttons
[ 2837.333] (--) Logitech USB Laser Mouse: Found scroll wheel(s)
[ 2837.333] (--) Logitech USB Laser Mouse: Found relative axes
[ 2837.333] (--) Logitech USB Laser Mouse: Found x and y relative axes
[ 2837.333] (II) Logitech USB Laser Mouse: Configuring as mouse
[ 2837.333] (II) Logitech USB Laser Mouse: Adding scrollwheel support
[ 2837.333] (**) Logitech USB Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2837.333] (**) Logitech USB Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2837.333] (II) XINPUT: Adding extended input device "Logitech USB Laser Mouse" (type: MOUSE)
[ 2837.333] (**) Logitech USB Laser Mouse: (accel) keeping acceleration scheme 1
[ 2837.333] (**) Logitech USB Laser Mouse: (accel) acceleration profile 0
[ 2837.333] (**) Logitech USB Laser Mouse: (accel) acceleration factor: 2.000
[ 2837.333] (**) Logitech USB Laser Mouse: (accel) acceleration threshold: 4
[ 2837.333] (II) Logitech USB Laser Mouse: initialized for relative axes.
[ 2837.334] (II) config/udev: Adding input device Logitech USB Laser Mouse (/dev/input/mouse1)
[ 2837.334] (II) No input driver/identifier specified (ignoring)
[ 2837.335] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 2837.335] (II) No input driver/identifier specified (ignoring)
[ 2837.342] (II) config/udev: Adding input device Integrated Camera (/dev/input/event8)
[ 2837.342] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
[ 2837.342] (**) Integrated Camera: always reports core events
[ 2837.342] (**) Integrated Camera: Device: "/dev/input/event8"
[ 2837.373] (--) Integrated Camera: Found keys
[ 2837.373] (II) Integrated Camera: Configuring as keyboard
[ 2837.373] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD)
[ 2837.373] (**) Option "xkb_rules" "evdev"
[ 2837.373] (**) Option "xkb_model" "evdev"
[ 2837.373] (**) Option "xkb_layout" "us"
[ 2837.382] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2837.382] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2837.382] (**) AT Translated Set 2 keyboard: always reports core events
[ 2837.382] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2837.403] (--) AT Translated Set 2 keyboard: Found keys
[ 2837.403] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 2837.403] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 2837.403] (**) Option "xkb_rules" "evdev"
[ 2837.403] (**) Option "xkb_model" "evdev"
[ 2837.403] (**) Option "xkb_layout" "us"
[ 2837.404] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event6)
[ 2837.404] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 2837.404] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 2837.404] (**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event6"
[ 2837.419] (--) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 2837.419] (--) TPPS/2 IBM TrackPoint: Found relative axes
[ 2837.419] (--) TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 2837.419] (II) TPPS/2 IBM TrackPoint: Configuring as mouse
[ 2837.419] (**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 2837.419] (**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2837.419] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
[ 2837.420] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 2837.420] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 2837.420] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 2837.420] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 2837.420] (II) TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 2837.420] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse0)
[ 2837.420] (II) No input driver/identifier specified (ignoring)
[ 2837.422] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event5)
[ 2837.422] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 2837.422] (**) ThinkPad Extra Buttons: always reports core events
[ 2837.422] (**) ThinkPad Extra Buttons: Device: "/dev/input/event5"
[ 2837.446] (--) ThinkPad Extra Buttons: Found keys
[ 2837.446] (II) ThinkPad Extra Buttons: Configuring as keyboard
[ 2837.446] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
[ 2837.446] (**) Option "xkb_rules" "evdev"
[ 2837.446] (**) Option "xkb_model" "evdev"
[ 2837.446] (**) Option "xkb_layout" "us"

lukaszg wrote:GlxGears still uses 100% CPU - is it OK?
Should I disable both dri and dri2 in xorg.conf, for nvidia drivers?
Dunno. Comment them out, restart X and see what happens.
Last edited by skunktrader (2011-03-13 16:01:02)

Similar Messages

T61 (7662CTO) - NVidia Quadro NVS 140M

Hello
My laptop is T61 (7662CTO)
it hase a lotof hanging up when I use my computer .
so I reinstalled again Windows Vista (reset to Factory setup)
then I use "Lenovo system tools (pc doctor) for checking my hardware.
I saw some problem in my graphic card test .
see this result & please tel me what is that reason ..
should bringe my Laptop to warranty becuase I am not happy about it .
here is my test check :
Lenovo System Toolbox Log File
February-20-09 5:58:38 PM
NVIDIA Quadro NVS 140M
Manufacturer:     NVIDIA
Driver:     c:\windows\system32\drivers\nvlddmkm.sys
Driver Version:     7.15.11.7693, 11-14-2008
Local Video Memory Test
Test Started        20/02/2009 5:01:12 PM
Test Finished:     Passed    20/02/2009 5:01:37 PM
Non-Local Video Memory Test
Test Started        20/02/2009 5:01:37 PM
Test Finished:     Passed    20/02/2009 5:05:57 PM
Primary Surface Test
Test Started        20/02/2009 5:05:57 PM
Warning Message:     Error at pixel 0 0 : Input color 000F0F0F not equal to output color 00000000.    20/02/2009 5:06:02 PM
Test Finished:     Failed    20/02/2009 5:06:08 PM
Fixed Transformation and Lighting Test
Test Started        20/02/2009 5:06:08 PM
Test Finished:     Passed    20/02/2009 5:06:56 PM
Wireframe Line Test
Test Started        20/02/2009 5:06:56 PM
Test Finished:     Passed    20/02/2009 5:07:41 PM
GPU Pipeline Data Test
Test Started        20/02/2009 5:07:42 PM
Test Finished:     Passed    20/02/2009 5:08:42 PM
Shader Rendering Test
Test Started        20/02/2009 5:08:42 PM
Test Finished:     Failed    20/02/2009 5:08:47 PM
Wireframe Shader Rendering Test
Test Started        20/02/2009 5:08:47 PM
Test Finished:     Failed    20/02/2009 5:08:53 PM
Shader Rendering DX10 Test
Test Started        20/02/2009 5:08:53 PM
Test Finished:     Passed    20/02/2009 5:09:42 PM
PCI Express Status Test
Test Started        20/02/2009 5:09:42 PM
Test Finished:     Passed    20/02/2009 5:09:43 PM
Product Version: 5.1.5122.07

Hello,
I would suggest to give service a call. Tell them about your results.
If you are in warranty till now, it should be serviced.
Message Edited by Agotthelf on 21-02-2009 11:34 PM
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
English Community      Deutsche Community      Comunidad en Español

Driver please! NVidia Quadro NVS 140M Windows 7 64-bit

Installed Windows 7 RTM (Professional, x64) on my T61. Surprise! There's no driver for my NVidia Quadro NVS 140M, and I can't install the one that I downloaded from NVidia. I'm stuck in 1024x768. Ouch!
What's the plan, Stan?
If there are any driver hackers out there who could help me install NVidia's driver, please speak up.

I'm running now using the NVidia-provided driver for Windows 7 x64. I was able to install it by running the installer in Vista compatibility mode.
For Windows 7 newbies, the specific steps are:
* Download the installer (186.81_notebook_win7_winvista_64bit_international_whql.exe)
* Run this file to extract the files to C:\DRIVERS\WIN\VIDEO
* For the two files nvudisp.exe and setup.exe in C:\DRIVERS\WIN\VIDEO, do the following:
* Right-click the file, select Properties.
* Click the Compatibility tab
* Check the box for "Run this program in compatibility mode for:" Select "Windows Vista (Service Pack 2)
* Click OK.
Then double-click setup.exe to run it.
So far this is working for me.

NVIDIA Quadro NVS 140M display driver updates?

I was wondering, when will the updates for NVIDIA Quadro NVS 140M driver be release? I tried playing some games and they say that my display driver is not uptodateand they do not allow me to play it =(
[code]
link : http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67890
Display (NVIDIA Quadro NVS 140M / Quadro FX 570M) driver for Windows Vista 32-bit - ThinkPad
This package installs the software (display driver) to enable the following video chips on the system board.
- NVIDIA Quadro NVS 140M
- NVIDIA Quadro FX 570M
Supported operating systems:
- Microsoft Windows Vista 32-bit
Supported systems:
- ThinkPad R61 (Machine types: 7742, 7743, 7744, 7751, 7753, 7754, 7755, 8914, 8918, 8919, 8920, 8927, 8928, 8929)
- ThinkPad R61i (Machine types: 7742, 8918)
- ThinkPad T61, T61p
Version: 7.15.11.7597 Release Date: 2008/06/16
Version 7.15.11.7597
(New) Support for Vista SP1.[/code]

Bump...
Non - replied me

When I'm using Safari, acasionally the menu bar just disappears. I'm running the latest version of Lion and the latest version of Safari. This is not a full screen app problem. I have multiple windows open. This happens all the time! Firefox is fine! ???

When I'm using Safari, ocasionally the menu bar just disappears. I'm running the latest version of Lion and the latest version of Safari. This is not a full screen app problem. I have multiple windows open. This happens all the time! Firefox is fine! What the ****? Please help!

Right, like I'm trying to say, THERE IS NO SAFARI MENU bar. Example: I have multiple applications open, I click on a Photoshop window, the correct menu or title bar or whatever changes. Every other application window I click on brings up the correct "whatever" bar. If I click on the desktop, the "Finder Bar" shows up.
Everythiing else, BUT SAFARI, works the same way since OS X came out. This is ridiculous.
I'm getting the vibe that Apple is trying to get rid of the finder.... this is the way wrong direction.

MISSION CONTROL, LAUNCHPAD, and FULL SCREEN APPS (one month later)

I'm pretty good embracing a new thing when it comes along. I downloaded LION the day it come out, which was over a month ago at this point. On that day, I immediately found MISSION CONTROL and LAUNCHPAD both uninituitve and pointless. Unhandy iCandy. And of FULL SCREEN APPS? Not necessary on an iMac anyway.
So I quickly sought out quick solutions to 'fix' these new features. Launchpad and full screen apps have the advantage that they can be simply ignored. This is a good thing. Mission Control, on the other hand, got in the way of a beloved feature for me: what was once SPACES and EXPOSE. That is, I couldn't simply ignore MC because I still needed the previous helpful features in Snow Leopard.
My solution was kind of surprising and eye-opening. It's complicated to explain but I thought I'd share. This conclusion is likely best suited for someone not using a small screened Mac. It turns out that most users (with big enough screens) don't really need Mission Control, Launchpad, Spaces, or Full Screen apps.
At all.
Let's go through that conclusion, one by one:
FULL SCREEN APPS
If you have a relatively big screen (20 iMac for instance), why do you need Safari full screen? Unless you intend to sit across the room from the computer, no reason. And there's lots of bright empty space when you do this. Do you need the Mail app full screen? If you need reading glasses, maybe, but otherwise, nope. I find it's easier just to stretch out an app pretty big and leave it at that.
Full screen apps DO offer a nice feature which is making your desktop, menubar, and dock go BYE BYE. I can see where sometimes this is a useful feature, but typically -- NOPE. Typically I want access to my dock (to switch between open apps without the added step of cancelling full screen first), and typically I want access to my menubar so that I can glance up and see what time it is or find an app menu quickly.
The only feature I find worthy of praise with full screen apps is that they hide the clutter on your desktop. But there's an app in the Mac App Store which makes your desktop icons vanish with the touch of a button (CAMOUFLAGE). I mean, what's the point of a wallpaper if you bury it with desktop clutter or eliminate it with full screen apps? If it's a busy and distracting wallpaper, umm... you picked bad wallpaper.
LAUNCH PAD
LAUNCH PAD offers an iOS experience inside OS X. At first I thought it was completely silly. After a month now, I kinda get why it's there. Kinda.
You see, before LP, to duplicate it's functionality, you'd have to organize folders yourself. Put folders of various apps together. Place them somewhere in the finder heirarchy. Then drag those folders into the part of the dock with the trashcan. Then you could click them open and have access to similarly themed folders of apps. The problem here, of course, is that unless you're a power user, you'll never do this.
So Apple thought, AH-HA, we'll just drag into OS X a paradigm that users already get from iOS. Clumping apps together any way you like them. The misfire, if you ask me, is not allowing users to drag the new iOS folders straight into the dock when finished. That is to say: copies of said organized folders. It's as if Apple's software people have complete contempt for the dock -- and are desperate to have users abandon it.
My problem is that I like having folders in my dock of stuff I need. It just works, as Steve says. Going to the same EXACT place every time I need anything is more intuitive and graceful than ADDING an app called Launchpad that launches you into a different finder altogether. Makes zero sense and THIS is why I say, like FULL SCREEN APPS, LP can basically be abandoned.
By the way: need proof that Apple has complete contempt for the Dock?
MISSION CONTROL/SPACES
A month has passed since MC was introduced and SPACES was eliminated. I dare anyone to tell me why either is needed at all. Before you get iMiffed, humor me for a moment and hear me out.
The notion of SPACES was that it's a neat way to keep like minded open apps together. I totally bought into this, back in the day. So much so that I was iMiffed when it was gone in Lion. But let's look at this closer.
The REASON why we needed SPACES was that we could have WAY too many windows open at once on a Mac. Right? A big mess of windows covering each other up. Suppose you're surfing in Safari but need iTunes? But iTunes is hidden. So what did you do? You went to Spaces as step one, moused over to your iTunes space as move two, and then clicked it as move three. Seems like a great solution until the day you discover that you could simply click on iTunes in the dock as move one and arrive at iTunes. As one step. Period. Really simple, right?
Why have Spaces and apps dance around when you can just click the app you want and be done with it? That's the critical observation to make in order to follow my entire line of reasoning. Sure, it may look really cool and make Windows machines look like junk, but at the end of the day, why add two steps to something you might do 100 times a day -- switching between apps.
So why OH why did Apple add Spaces? Simple: because too many apps were visible at once in one 'desktop' window. So if you can build many new desktops, there might only be one or two in each. Great solution. Right?
Wrong, as it turns out. Because we still have the two extra steps. It's a weak solution. And it's in complete contempt of the Dock, which as it turns out, offers the strongest solution.
The strong solution would be that only one app is visible in your Mac's window at all times. Say you're in Safari. Despite having 12 other apps open, you only see Safari. Your dock tells you that you have other apps open, but nothing else sits in your window BUT the app you're using. So you want to go to iTunes? So click on it in the dock and Safari vanishes and iTunes emerges by itself. No other windows. What could be simpler? (This app is freeware known as ISOLATOR.)
If you download and try ISOLATOR, you'll say, umm, okay, but wait: sometimes I do want more than one window in view. Okay, fine, turn it off then. From the handy menu bar menu. I find that 98% of the time I need ISOLATOR on. Mileage may vary.
So let's recap. One third party software removes distracting desktop clutter, the other removes distracting app windows. Both can be toggled on and off from the menu bar. One is free, one costs $2. These two solutions remove the only real feature of FULL SCREEN APPS and make SPACES and it's newfangled cousin MISSION CONTROL pointless.
Need that last one explained? Well, what's Mission Control but a variant of spaces? To invoke MC and switch to the needed window are those same two annoying steps Spaces added into the mix. Nothing was fixed. Plus, like spaces, you must invest time and energy organizing such spaces.
Why bother? And so I ask again: can somebody who's read and tried the above carefully explain to me why Mission Control, Launchpad, and Full Screen Apps are really needed at all? (Outside of small screened Macs.) Doesn't the dock and these two sharewares together solve most problems?
Am I missing something?

I agree with everything you said about full screen apps, mission control and launchpad. For apps that made sense to run full screen, they already could under SL. Launchpad is totally unnecessary and Mission Control is a mere shadow of Expose and Spaces.
However, I feel you have not given due credit to Spaces. The point of Spaces is to let one organise logical desktops for different tasks, not just a way to reduce the number of windows on display. For example, I have a Space for software development where I run Xcode and the iPhone simulator, a Firefox window showing perhaps documentation or some other websites pertaining to software development, a Finder window that is opened in the folder with my design docs. I have another Space where I have the remote login sessions, yet another Space with another Firefox window where I do general surfing and emailing. I can switch between these spaces using a keyboard shortcut, which is much quicker than having to lift my hand off the keyboard, move it over to the mouse, move the mouse pointer over the Dock, find the app and click on it, only to find that it has switched to the wrong window of the app.
Without Spaces, organisation of my desktop is disrupted each time I want to switch task, whereas Spaces allows me to drop everything I am doing, go and do something completely different for a while and go back to my exact previous environment. I have a 27" iMac so am not short of screen space but I use Spaces extensively. BTW, switching Spaces using a keyboard shortcut is a lot faster on SL than the equivalent on Lion, thanks to the gratuitous screen animation of the latter.

Timeline and full screen view in PSE11

I have read as many reviews of PSE11 as I can find but none have mentioned the Timeline, which I use every day. Does it still exist in PSE11? What about the full screen view and compare side by side view? Do they still exist. If they do, can you still see the image full-size by clicking on it in full screen view?

Timeline and Full Screen View exists in PSE11 and all the earlier functionalities present in full screen view are present. The Timeline and Full Screen View can be accessed from View menu of Elements Organizer.

Full screen images and full screen color background boxes are cropping horizontally.

Full screen images aren't loading and full screen color background boxes are cropping horizontally. I'm forced to make my images a full screen slide show (of 1 image) to make it work, but then I lose the option to pin the image. Am I alone in this?

Hello,
I would request you to share the a url or few screenshot so that i can get better idea about the issue.
To create a temporry url you can go to File > publish in muse.
Regards
Vivek

Is it possible to install Snow Leopard on a PC and to run it with two Nvidia Quadro Cards and 8 Screens?

Is it possible to install Snow Leopard on a PC and to run it with two Nvidia Quadro Cards and 8 Screens?

Furthermore, all new Macs since 2006 have been able to have Windows or Linux installed on them natively with virtualization engines*:
http://www.macmaps.com/macosxnative.html#WINTEL
You may even want to consider a used Mac Pro*:
http://www.macmaps.com/usedrefurbished.html

Hello, i have a problem with nvidia quadro k4200. in AE CS6 is not compatible? Why? Please??

hello, i have a problem with nvidia quadro k4200. in AE CS6 is not compatible? Why? Please??

jasonf18090788 wrote:
i saw in the site Adobe that the video card is compatible with AE and Pr, but not work.
Where did you see that? It's not on the list for AE: System requirements | After Effects
Keep in mind that After Effects only uses the GPU for one, obsolete thing. GPU matters very little for AE. See this: GPU (CUDA, OpenGL) features in After Effects CS6 and After Effects CC

NVidia Quadro NVS 285 and 30" titanium cinema display

Does the nVidia Quadro NVS 285 (or 55/280 PCI) support the old 30" titanium cinema display? I'm running the display to an HP tower via DVI-D dual link adapted to a DVI dual link (DMS-59), and I can't get it to work. Can anyone help?

I wish I could offer some advice. Instead, I am seeking your thoughts on the new card. Did the X800XT work? I have the same machine as you and am looking to upgrade my 64mb geForce 5200 card with either the 9600Pro for Mac or PC or the X800XT card (by Radeon).
Though it seems like production of the X800XT card has slowed to a crawl, I've found some for sale online. Just nervous, as I've read mixed things!
Your opinion would be welcomed.
Thank you,
Kevin

Troubleshooting a freeze: HP DC7800, NVIDIA Quadro NVS 290, Windows 7

Hello everyone,
I'm having problems with my HP DC7800 & Windows 7 (fresh install, 64 bit). The video card is NVIDIA Quadro NVS 290.
When any official NVIDIA driver is installed, I can boot into Windows 7, but just a few seconds into reaching the log in screen, there is a brief flicker & everything freezes. Though sometimes, the keyboard does respond: the CapsLock & the NumLock lights on my keyboard respond after a delay of, 5 seconds to 2 minutes.
When rolling back to whatever the default Windows drivers are available before installing the official drivers (WDDM v1.1?), I can't even get to the Windows log-in screen. The monitor displays "No Signal" and it's all blacked out. I have to shut it down with the physical power button.
When going back even further to the Standard VGA Graphics Adapter, I can boot into normal mode. Though using the same driver as the one in safe-mode is far from what I'm after.
Also, I should mention that I'm on a multi-boot system with Linux. They are on a separate drive and they can boot with comparitively-minimal problems.
Debian 7.7 with the open-source nouveau drivers work perfectly well.
Ubuntu-Gnome 14.04.1 with nouveau works well. With enough arm-twisting & the right combo of packages, I can get Ubuntu to work with the latest, official proprietary NVIDIA drivers.
Because I can get the NVIDIA card to work in 2 Linux distros, I'm fairly certain that the card is NOT completely broken.
It is the fresh-install of Windows 7 that is giving me trouble.
I've upgraded my BIOS to the latest available: 786F1 v01.32, 7/21/2011.
After updating BIOS, I've tried uninstalling & reinstalling several official drivers (309.00, 331.82, 333.11 & the latest: 341.05) with similar results.
For what it's worth, there is also an HP announcement. Should I update my Video BIOS, as the announcement says? How would I do that?
Other possibly important or irrelevant info:
* when the NVIDIA card is not in the computer, I connect using the motherboard's VGA slot & I can boot into Windows 7 normal mode perfectly well.
* when the NVIDIA card is in the computer, I can only boot into Windows safe mode. Booting Windows 7 into normal mode will freeze the computer a few seconds afterlogging in or reaching the login screen.
* At an earlier point in my troubleshooting, I was getting a BSOD screen, which mentioned the nvlddmkm.sys file.
* I've looked at my error logs, and they mostly report Event ID 7001 (Service Control Manager) and Event ID 10005 (Distributed DCOM)
Main questions:
Is there something about updating my Video BIOS, as per the link above, that would help? Or is that video BIOS update included in the whole-system BIOS update to v01.32?
If I can get my computer to work in Windows 7 safe mode, Debian Linux (with open source driver) & Ubuntu (with open source & official proprietary drivers), why can't I get Windows 7 to work in normal mode?
Are there any display-specific error logs that could clue me in? The only error log I know about is the one available through Administrative Tools > Event Viewer.
Are there any alternative, reputable drivers available for the Quadro NVS 290 on Windows 7?
Thank you for your time and please let me know if you need any more info or if there's something else I can do.

When installing that HP Nvidia driver you linked, and even switching to DVI port #1. I got the same results:
boot into Windows normal mode, get to the log-in screen. There's a flicker on the screen & everything freezes.
Hmm, well I went ahead and tried using an official NVIDIA driver in my Ubuntu setup (14.04.1). The packages I installed for Ubuntu were 'nvidia-331-updates' and 'nvidia-331-updates-uvm'.
It works well, as long as I go into my NVIDIA X Server Settings > GPU 0 > PowerMizer > Preferred Mode > Prefer Maximum Performance.
I have to do this immediately after logging in, otherwise Ubuntu will freeze after about a minute.
I can do some moderate gaming, Team Fortress 2, resolution set to 1280x720, after about 15 minutes I log out and see that my GPU temp is 77 Celsius.
With the same configuration, at rest, the GPU is 64-66 Celsius.
Maybe my card is toasted? From my limited understanding of drivers, the official, proprietary driver will enable the more advanced features of the card. This only seems to be a problem when I use the NVIDIA drivers...But please correct me if I'm wrong.
Moderate gaming with open source nouveau drivers on Ubuntu doesn't perform well, but it doesn't crash either.
Anyway, I think I'll go ahead and order another card.
In the meantime, is there a way to configure the NVIDIA card from the command line for Windows normal mode? I'm trying to think of a way to work with it before the Windows GUI is loaded.

Which display driver package do I need for Nvidia Quadro NVS 110m?

Hi there,
I'm new to (Arch) Linux and was wondering which display driver package I need. I have a Dell Latitude D620 with a "nvidia quadro nvs 110m".
In the Arch Linux beginners guide it says:
1. nvidia-96xx slightly newer cards up to the GF 4.
2. nvidia-173xx Geforce FX series cards
3. nvidia newest GPUs after the GF FX
Consult the NVIDIA-Homepage to see which one is for you.
But on the NVIDIA-Homepage it says:
The GeForce M series and GeForce Go series notebook GPUs use drivers that have been customized by the notebook manufacturers to support hot key functions, power management functions, lid close and suspend/resume behavior. NVIDIA has worked with some notebook manufacturers to provide notebook-specific driver updates, however, most notebook driver updates must come from the notebook manufacturer.
And they just forward me to Dell Support which obviously neither offers a linux driver nor linux driver information for the D620.
So which of the three packages do I have to install?
Are these packages open-source drivers? Do I need proprietary nvidia drivers to get full 3D-performance?
Does anybody have experience with the D620?
Although I'm new to Linux and I like the KISS idea behind Arch Linux, I still want to have all that Compiz Fusion eye candy. I also want to play a few games which need 3D performance (once I'm familiar with wine). ;-)
Thanks in advance for your help,
Blackhole
Last edited by blackhole (2008-12-14 10:22:05)

Thanks a lot.
Final question: How does Arch Linux deal with license issues? If the nvidia package includes the original nvidia drivers linked above, doesn't that cause any legal/moral problems? Like in Ubuntu for example they always point out that it's proprietary software you're gonna install when enabling the nvidia drivers.
Just wondering...

Nvidia Quadro NVS 110M (Dell Latitude D620) driver issue

I'm having trouble installing the right driver for Nvidia QUadro NVS 110M video card on my laptop. What ever driver I install it requests for a reboot and when I restart, I get a blue screen.
Things that I have tried (all resulted in blue screen after restart).
Update driver using Automatic update
Downloaded driver from Dell support site (for Vista)
Downloaded driver from nVidia
Downloaded beta driver from nVidia
Please note: It used to work on Windows 7 before on the same laptop - I was trying to replace HDD and cant seem to make it work again with the new OS installation.Chandra Sekhar

Hello,
I'd suggest you installing the XP driver in Compatibility mode. Remove that hardware device in Device Manager, right-click on the driver executable/installer file and select the Compatibility tab; click the checkbox before Run this program in Compatibility mode for option and select Windows XP in the list-down box;
If the problem still persists, please understand that Windows 7 is a new operating system (only the beta version) and whole driverstore has been reprogrammed; some old driver is not compatible with new OS. I suggest that you should wait for another period of time till the retail version is released and push the vendor company to upgrade their device driver. Thanks for your time and understanding!
For more details, please look at the first Sticky thread at the top of this forum.
What can I do if my hardware does not work?
This will give you some guidelines.
Good Luck!

NVIDIA Quadro NVS 160M/150M GPU on T500?

Hi
does anyone know if NVIDIA Quadro NVS 160M or 150M workson T500 with Advanced Dock?
Thanks

Hello!
I'm using the same card as you:
lspci:
01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1)
I'm using the arch kernel: kernel26 + nvidia + nvidia-utils
My Xorg.conf:
65 Section "Device"
66
67 Identifier "Nvidia Quadro NVS 160M"
68 VendorName "Nvidia Corporation"
69 Boardname "Quadro NVS 160M"
70 Driver "nvidia"
71 Option "NoLogo" "true"
72 Option "DPI" "96 x 96"
73
Best regards,
Flasher

Vdpau and full screen youtube problems on Nvidia Quadro NVS 140M

Similar Messages

Maybe you are looking for