You are not logged in.

#1 2013-12-04 09:08:44

pmk1c
Member
Registered: 2013-11-25
Posts: 4

Pixel glitches in GNOME with Nvidia

Since I switched from nouveau to nvidia I get weird pixel glitches in the top left corner of my screen. They seem to disappear when parts of the screen change, but come back immediately.
Also they seem to be gone for the whole session when I logout / login in after boot.

Has anyone an idea how to get rid of this?

Last edited by pmk1c (2013-12-07 12:42:22)

Offline

#2 2013-12-04 09:56:48

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,952
Website

Re: Pixel glitches in GNOME with Nvidia

It might be helpful if you tell us what nVidia card you have. Also, what DE/WM/Compositor combination are you using?


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2013-12-06 13:54:14

pmk1c
Member
Registered: 2013-11-25
Posts: 4

Re: Pixel glitches in GNOME with Nvidia

I'm using Gnome 3.10 (with Mutter) and have a Nvidia GTX 650.

I also added a screenshot of the problem. Those big black rectangles are the problem. I can't make a screenshot since they disappear when I hit the button (probably because the snapshot effect in Gnome modifies the whole screen).

https://oc.bmind.de/public.php?service= … e49a24b968

Last edited by pmk1c (2013-12-17 11:18:37)

Offline

#4 2013-12-06 14:35:23

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,952
Website

Re: Pixel glitches in GNOME with Nvidia

I think you need to upload your screenshot to a different hoster, that image isn't loading for me.

You also might want to edit the topic title to make it clear that you're using gnome, so that you catch the attention of people who use it.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2013-12-17 11:20:24

pmk1c
Member
Registered: 2013-11-25
Posts: 4

Re: Pixel glitches in GNOME with Nvidia

I reuploaded the picture now you should see it:

https://oc.bmind.de/public.php?service= … e49a24b968

Sadly, the problem still exists.

Offline

#6 2013-12-17 14:30:43

Thorsten Reinbold
Member
From: Germany
Registered: 2011-12-06
Posts: 353

Re: Pixel glitches in GNOME with Nvidia

Are there any warnings in the log files?

Offline

#7 2013-12-18 23:50:03

pmk1c
Member
Registered: 2013-11-25
Posts: 4

Re: Pixel glitches in GNOME with Nvidia

This is the log of GDM. Can't find anything really unusual in there. Maybe somebody else?

Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
(II) NVIDIA GLX Module  331.20  Wed Oct 30 17:36:48 PDT 2013
Loading extension GLX
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
(II) NVIDIA dlloader X Driver  331.20  Wed Oct 30 17:16:53 PDT 2013
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(++) using VT number 1

(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.14.5, module version = 1.0.0
(WW) Unresolved symbol: fbGetGCPrivateKey
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
	compiled for 1.14.5, module version = 1.0.0
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling 2D acceleration
(II) NVIDIA(0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(0):     stereo.
(II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
(II) NVIDIA(0): NVIDIA GPU GeForce GTX 650 (GK107) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 1048576 kBytes
(--) NVIDIA(0): VideoBIOS: 80.07.35.00.60
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Valid display device(s) on GeForce GTX 650 at PCI:1:0:0
(--) NVIDIA(0):     Ancor Communications Inc ASUS VW193D (CRT-0) (boot, connected)
(--) NVIDIA(0):     DFP-0
(--) NVIDIA(0):     SAMSUNG (DFP-1) (connected)
(--) NVIDIA(0):     DFP-2
(--) NVIDIA(0): Ancor Communications Inc ASUS VW193D (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): DFP-0: Internal Single Link TMDS
(--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
(--) NVIDIA(0): SAMSUNG (DFP-1): Internal Single Link TMDS
(--) NVIDIA(0): SAMSUNG (DFP-1): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): DFP-2: Internal Single Link TMDS
(--) NVIDIA(0): DFP-2: 330.0 MHz maximum pixel clock
(**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
(**) NVIDIA(0):     device Ancor Communications Inc ASUS VW193D (CRT-0) (Using
(**) NVIDIA(0):     EDID frequencies has been enabled on all display
(**) NVIDIA(0):     devices.)
(**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
(**) NVIDIA(0):     device SAMSUNG (DFP-1) (Using EDID frequencies has been
(**) NVIDIA(0):     enabled on all display devices.)
(==) NVIDIA(0): 
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0):     will be used as the requested mode.
(==) NVIDIA(0): 
(II) NVIDIA(0): Validated MetaModes:
(II) NVIDIA(0):     "CRT-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 3360 x 1080
(--) NVIDIA(0): DPI set to (89, 87); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(--) Depth 24 pixmap format is 32 bpp
(II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
(II) NVIDIA:     access.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0):     configuration option may not be set correctly.  When the
(II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
(II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
(II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0):     Config Options in the README.
(II) NVIDIA(0): Setting mode "CRT-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
Loading extension NV-GLX
(==) NVIDIA(0): Disabling shared memory pixmaps
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
Loading extension NV-CONTROL
Loading extension XINERAMA
(II) NVIDIA(0): [DRI2] Setup complete
(II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
(--) RandR disabled
(II) Initializing extension GLX
(II) config/udev: Adding input device Power Button (/dev/input/event1)
(**) Power Button: Applying InputClass "system-keyboard"
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: Applying InputClass "system-keyboard"
(**) Power Button: Applying InputClass "Keyboard Defaults"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
	compiled for 1.14.3, module version = 2.8.2
(II) Using input driver 'evdev' for 'Power Button'
(**) Power Button: always reports core events
(**) evdev: Power Button: Device: "/dev/input/event1"
(--) evdev: Power Button: Vendor 0 Product 0x1
(--) evdev: Power Button: Found keys
(II) evdev: Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
(WW) Option "xkb_variant" requires a string value
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(II) config/udev: Adding input device Power Button (/dev/input/event0)
(**) Power Button: Applying InputClass "system-keyboard"
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: Applying InputClass "system-keyboard"
(**) Power Button: Applying InputClass "Keyboard Defaults"
(II) Using input driver 'evdev' for 'Power Button'
(**) Power Button: always reports core events
(**) evdev: Power Button: Device: "/dev/input/event0"
(--) evdev: Power Button: Vendor 0 Product 0x1
(--) evdev: Power Button: Found keys
(II) evdev: Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
(WW) Option "xkb_variant" requires a string value
(II) config/udev: Adding drm device (/dev/dri/card0)
(II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event10)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event9)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event8)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event11)
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "Keyboard Defaults"
(II) Using input driver 'evdev' for 'Logitech USB Receiver'
(**) Logitech USB Receiver: always reports core events
(**) evdev: Logitech USB Receiver: Device: "/dev/input/event11"
(--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52e
(--) evdev: Logitech USB Receiver: Found keys
(II) evdev: Logitech USB Receiver: Configuring as keyboard
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 8)
(WW) Option "xkb_variant" requires a string value
(II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event12)
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
(**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "Keyboard Defaults"
(II) Using input driver 'evdev' for 'Logitech USB Receiver'
(**) Logitech USB Receiver: always reports core events
(**) evdev: Logitech USB Receiver: Device: "/dev/input/event12"
(--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52e
(--) evdev: Logitech USB Receiver: Found 20 mouse buttons
(--) evdev: Logitech USB Receiver: Found scroll wheel(s)
(--) evdev: Logitech USB Receiver: Found relative axes
(--) evdev: Logitech USB Receiver: Found x and y relative axes
(--) evdev: Logitech USB Receiver: Found absolute axes
(II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
(--) evdev: Logitech USB Receiver: Found keys
(II) evdev: Logitech USB Receiver: Configuring as mouse
(II) evdev: Logitech USB Receiver: Configuring as keyboard
(II) evdev: Logitech USB Receiver: Adding scrollwheel support
(**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
(WW) Option "xkb_variant" requires a string value
(II) evdev: Logitech USB Receiver: initialized for relative axes.
(WW) evdev: Logitech USB Receiver: ignoring absolute axes.
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) acceleration profile 0
(**) Logitech USB Receiver: (accel) acceleration factor: 2.000
(**) Logitech USB Receiver: (accel) acceleration threshold: 4
(II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "system-keyboard"
(**) Logitech USB Receiver: Applying InputClass "Keyboard Defaults"
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device Generic X-Box pad (/dev/input/event13)
(**) Generic X-Box pad: Applying InputClass "joystick catchall"
(II) Loading /usr/lib/xorg/modules/input/joystick_drv.so
(II) Module joystick: vendor="X.Org Foundation"
	compiled for 1.14.0, module version = 1.6.2
(II) Using input driver 'joystick' for 'Generic X-Box pad'
(**) Generic X-Box pad: always reports core events
(**) Generic X-Box pad (keys): Applying InputClass "joystick catchall"
(II) Using input driver 'joystick' for 'Generic X-Box pad (keys)'
(**) Generic X-Box pad (keys): always reports core events
(II) XINPUT: Adding extended input device "Generic X-Box pad (keys)" (type: JOYSTICK, id 10)
(II) XINPUT: Adding extended input device "Generic X-Box pad" (type: JOYSTICK, id 11)
(II) Joystick: Generic X-Box pad. bus 0x3 vendor 0x46d product 0xc21f version 0x305
(II) Joystick: found 8 axes, 11 buttons
JOYSTICK: DebugLevel set to 0
(**) Generic X-Box pad: (accel) keeping acceleration scheme 1
(**) Generic X-Box pad: (accel) acceleration profile 0
(**) Generic X-Box pad: (accel) acceleration factor: 2.000
(**) Generic X-Box pad: (accel) acceleration threshold: 4
(II) config/udev: Adding input device Generic X-Box pad (/dev/input/js0)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event5)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event4)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event3)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event2)
(II) No input driver specified, ignoring this device.
(II) This device may have been added with another device file.
(II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event7)
(**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
(**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
(**) Eee PC WMI hotkeys: Applying InputClass "system-keyboard"
(**) Eee PC WMI hotkeys: Applying InputClass "Keyboard Defaults"
(II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
(**) Eee PC WMI hotkeys: always reports core events
(**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event7"
(--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
(--) evdev: Eee PC WMI hotkeys: Found keys
(II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
(II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
(WW) Option "xkb_variant" requires a string value
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +1440+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
(II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select @1440x900 +0+0 {ViewPortIn=1440x900, ViewPortOut=1440x900+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +1440+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select @1440x900 +0+0 {ViewPortIn=1440x900, ViewPortOut=1440x900+0+0}"
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.
(II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS VW193D (CRT-0)) does
(II) NVIDIA(GPU-0):     not support NVIDIA 3D Vision stereo.
(II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
(II) NVIDIA(GPU-0):     stereo.

Offline

Board footer

Powered by FluxBB