You are not logged in.

#51 2013-12-21 08:35:51

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

pan-bolek wrote:

...

Sounds like you're running separate screens (ie. multiple X instances). Which would mean you are not using Xinerama. Which means you can not drag a window from any screen to any other screen or span one window across all screens.

To run one screensaver would require enabling Xinerama which will probably break everything.

Last edited by oz (2013-12-21 08:41:04)

Offline

#52 2013-12-21 16:09:47

pan-bolek
Member
Registered: 2013-12-21
Posts: 5

Re: Xinerama seems to be broken with latest updates

No - not the case.

I AM running xinerama.

I HAVE one window spanning all three monitors.

I CAN drag a window from display 0 to display 2.

xorg.conf:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 295.20  (buildmeister@swio-display-x86-rhel47-05.nvidia.com)  Mon Feb  6 22:13:16 PST 2012


Section "ServerLayout"

# Removed Option "Xinerama" "1"
# Removed Option "Xinerama" "0"
    Identifier     "Layout0"
    Screen      0  "Screen0" 3200 0
    Screen      1  "Screen1" LeftOf "Screen2"
    Screen      2  "Screen2" LeftOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "1"
EndSection

Section "Files"
EndSection

.....

The xorg.conf files are identical between the two previous installs...

Just wondering if anyone else has seen this effect?

Google only brings up problems of SEGFAULTS - I've seen nothing on nvidia's site or other forums...

Just thought I would take a shot here...

Offline

#53 2013-12-21 16:25:14

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

Are you running the cards in SLI?

Can you post the output of your Xorg.log file? I'm interested to see how it is initializing. I'm quite surprised it even runs with Xinerama enabled. Are you sure you're running the most recent nvidia driver?

Last edited by oz (2013-12-21 16:29:59)

Offline

#54 2013-12-21 17:13:00

pan-bolek
Member
Registered: 2013-12-21
Posts: 5

Re: Xinerama seems to be broken with latest updates

I am not running the cards in SLI - to be honest, I've never even encountered that issue before and never did anything specific. I just put the cards in the machine, ran the nvidia proprietary installer and it just worked.

Also, I am not running ArchLinux, but openSuSE 12.3 (I know, not your distro), but as I said before, I was hoping that someone had run across something similar as well.

I appreciate you taking a look at this...

Xorg.0.log:

[    13.189] 
X.Org X Server 1.13.2
Release Date: 2013-01-24
[    13.189] X Protocol Version 11, Revision 0
[    13.189] Build Operating System: openSUSE SUSE LINUX
[    13.189] Current Operating System: Linux machine.local 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) x86_64
[    13.189] Kernel command line: root=/dev/VG_Data_00/root resume=/dev/disk/by-id/md-uuid-929ab81c:4e64cef8:c6d43b40:0d0484be splash=silent quiet  showopts vga=0x31a
[    13.189] Build Date: 21 February 2013  10:01:18AM
[    13.189]  
[    13.189] Current version of pixman: 0.28.2
[    13.189] 	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
[    13.189] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    13.189] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 18 22:28:45 2013
[    13.205] (==) Using config file: "/etc/X11/xorg.conf"
[    13.205] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    13.205] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    13.206] (==) ServerLayout "Layout0"
[    13.206] (**) |-->Screen "Screen0" (0)
[    13.206] (**) |   |-->Monitor "Monitor0"
[    13.207] (**) |   |-->Device "Device0"
[    13.207] (**) |-->Screen "Screen1" (1)
[    13.207] (**) |   |-->Monitor "Monitor1"
[    13.207] (**) |   |-->Device "Device1"
[    13.207] (**) |-->Screen "Screen2" (2)
[    13.207] (**) |   |-->Monitor "Monitor2"
[    13.207] (**) |   |-->Device "Device2"
[    13.207] (**) |-->Input Device "Keyboard0"
[    13.207] (**) |-->Input Device "Mouse0"
[    13.207] (**) Option "Xinerama" "1"
[    13.208] (==) Automatically adding devices
[    13.208] (==) Automatically enabling devices
[    13.208] (==) Automatically adding GPU devices
[    13.208] (**) Xinerama: enabled
[    13.216] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
[    13.216] 	Entry deleted from font path.
[    13.216] (==) FontPath set to:
	/usr/share/fonts/misc:unscaled,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi:unscaled,
	/usr/share/fonts/75dpi:unscaled,
	/usr/share/fonts/ghostscript/,
	/usr/share/fonts/cyrillic:unscaled,
	/usr/share/fonts/truetype/,
	built-ins
[    13.216] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
[    13.216] (**) Extension "Composite" is disabled
[    13.216] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    13.216] (WW) Disabling Keyboard0
[    13.216] (WW) Disabling Mouse0
[    13.216] (II) Loader magic: 0x801c20
[    13.216] (II) Module ABI versions:
[    13.216] 	X.Org ANSI C Emulation: 0.4
[    13.216] 	X.Org Video Driver: 13.1
[    13.216] 	X.Org XInput driver : 18.0
[    13.216] 	X.Org Server Extension : 7.0
[    13.217] (--) PCI: (0:2:0:0) 10de:104a:1462:809f rev 161, Mem @ 0xfb000000/16777216, 0xc8000000/134217728, 0xd2000000/33554432, I/O @ 0x0000b800/128, BIOS @ 0x????????/524288
[    13.217] (--) PCI:*(0:7:0:0) 10de:104a:1462:809f rev 161, Mem @ 0xfd000000/16777216, 0xd8000000/134217728, 0xd6000000/33554432, I/O @ 0x0000e800/128, BIOS @ 0x????????/524288
[    13.217] (II) Open ACPI successful (/var/run/acpid.socket)
[    13.217] Initializing built-in extension Generic Event Extension
[    13.217] Initializing built-in extension SHAPE
[    13.217] Initializing built-in extension MIT-SHM
[    13.217] Initializing built-in extension XInputExtension
[    13.217] Initializing built-in extension XTEST
[    13.217] Initializing built-in extension BIG-REQUESTS
[    13.217] Initializing built-in extension SYNC
[    13.217] Initializing built-in extension XKEYBOARD
[    13.217] Initializing built-in extension XC-MISC
[    13.217] Initializing built-in extension SECURITY
[    13.217] Initializing built-in extension XINERAMA
[    13.217] Initializing built-in extension XFIXES
[    13.217] Initializing built-in extension RENDER
[    13.217] Initializing built-in extension RANDR
[    13.217] Initializing built-in extension COMPOSITE
[    13.217] Initializing built-in extension DAMAGE
[    13.217] Initializing built-in extension MIT-SCREEN-SAVER
[    13.217] Initializing built-in extension DOUBLE-BUFFER
[    13.217] Initializing built-in extension RECORD
[    13.217] Initializing built-in extension DPMS
[    13.217] Initializing built-in extension X-Resource
[    13.217] Initializing built-in extension XVideo
[    13.217] Initializing built-in extension XVideo-MotionCompensation
[    13.217] Initializing built-in extension XFree86-VidModeExtension
[    13.217] Initializing built-in extension XFree86-DGA
[    13.217] Initializing built-in extension XFree86-DRI
[    13.217] Initializing built-in extension DRI2
[    13.217] (II) "glx" will be loaded by default.
[    13.217] (II) LoadModule: "dri2"
[    13.217] (II) Module "dri2" already built-in
[    13.217] (II) LoadModule: "glamoregl"
[    13.281] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    13.553] (EE) Failed to load /usr/lib64/xorg/modules/libglamoregl.so: /usr/lib64/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context
[    13.553] (II) UnloadModule: "glamoregl"
[    13.553] (II) Unloading glamoregl
[    13.553] (EE) Failed to load module "glamoregl" (loader failed, 7)
[    13.553] (II) LoadModule: "glx"
[    13.553] (II) Loading /usr/lib64/xorg/modules/updates/extensions/libglx.so
[    13.645] (II) Module glx: vendor="NVIDIA Corporation"
[    13.645] 	compiled for 4.0.2, module version = 1.0.0
[    13.645] 	Module class: X.Org Server Extension
[    13.645] (II) NVIDIA GLX Module  331.20  Wed Oct 30 17:36:48 PDT 2013
[    13.646] Loading extension GLX
[    13.646] (II) LoadModule: "nvidia"
[    13.646] (II) Loading /usr/lib64/xorg/modules/updates/drivers/nvidia_drv.so
[    13.648] (II) Module nvidia: vendor="NVIDIA Corporation"
[    13.648] 	compiled for 4.0.2, module version = 1.0.0
[    13.648] 	Module class: X.Org Video Driver
[    13.648] (II) NVIDIA dlloader X Driver  331.20  Wed Oct 30 17:16:53 PDT 2013
[    13.648] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    13.648] (++) using VT number 7

[    13.648] (II) Loading sub module "fb"
[    13.648] (II) LoadModule: "fb"
[    13.649] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    13.649] (II) Module fb: vendor="X.Org Foundation"
[    13.649] 	compiled for 1.13.2, module version = 1.0.0
[    13.649] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    13.649] (WW) Unresolved symbol: fbGetGCPrivateKey
[    13.649] (II) Loading sub module "wfb"
[    13.649] (II) LoadModule: "wfb"
[    13.650] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[    13.651] (II) Module wfb: vendor="X.Org Foundation"
[    13.651] 	compiled for 1.13.2, module version = 1.0.0
[    13.651] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    13.651] (II) Loading sub module "ramdac"
[    13.651] (II) LoadModule: "ramdac"
[    13.651] (II) Module "ramdac" already built-in
[    13.651] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the
[    13.651] (WW) NVIDIA:     X server.
[    13.652] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[    13.652] (==) NVIDIA(0): RGB weight 888
[    13.652] (==) NVIDIA(0): Default visual is TrueColor
[    13.652] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    13.652] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
[    13.653] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +0+0"
[    13.653] (**) NVIDIA(2): Option "MetaModes" "DFP: nvidia-auto-select +0+0"
[    13.653] (**) NVIDIA(0): Enabling 2D acceleration
[    14.530] (II) NVIDIA(0): Display (Jean JC229x1-2 (CRT-1)) does not support NVIDIA 3D
[    14.530] (II) NVIDIA(0):     Vision stereo.
[    14.542] (II) NVIDIA(0): Display (HannStar Display Corp JC199D (DFP-0)) does not
[    14.542] (II) NVIDIA(0):     support NVIDIA 3D Vision stereo.
[    14.609] (II) NVIDIA(0): NVIDIA GPU GeForce GT 610 (GF119) at PCI:2:0:0 (GPU-0)
[    14.609] (--) NVIDIA(0): Memory: 2097152 kBytes
[    14.609] (--) NVIDIA(0): VideoBIOS: 75.19.55.00.03
[    14.609] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    14.613] (--) NVIDIA(0): Valid display device(s) on GeForce GT 610 at PCI:2:0:0
[    14.613] (--) NVIDIA(0):     CRT-0
[    14.613] (--) NVIDIA(0):     Jean JC229x1-2 (CRT-1) (boot, connected)
[    14.613] (--) NVIDIA(0):     HannStar Display Corp JC199D (DFP-0) (connected)
[    14.613] (--) NVIDIA(0):     DFP-1
[    14.613] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[    14.613] (--) NVIDIA(0): Jean JC229x1-2 (CRT-1): 400.0 MHz maximum pixel clock
[    14.613] (--) NVIDIA(0): HannStar Display Corp JC199D (DFP-0): Internal Dual Link TMDS
[    14.613] (--) NVIDIA(0): HannStar Display Corp JC199D (DFP-0): 330.0 MHz maximum pixel clock
[    14.613] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[    14.613] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[    14.613] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    14.613] (**) NVIDIA(0):     device Jean JC229x1-2 (CRT-1) (Using EDID frequencies has
[    14.613] (**) NVIDIA(0):     been enabled on all display devices.)
[    14.614] (II) NVIDIA(0): Validated MetaModes:
[    14.614] (II) NVIDIA(0):     "CRT:nvidia-auto-select+0+0"
[    14.614] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[    14.616] (WW) NVIDIA(0): Unable to match display device name "DFP-0" from
[    14.616] (WW) NVIDIA(0):     nvidiaXineramaInfoOrder
[    14.620] (--) NVIDIA(0): DPI set to (90, 91); computed from "UseEdidDpi" X config
[    14.620] (--) NVIDIA(0):     option
[    14.621] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
[    14.621] (==) NVIDIA(1): RGB weight 888
[    14.621] (==) NVIDIA(1): Default visual is TrueColor
[    14.621] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[    14.621] (**) NVIDIA(1): Option "TwinViewXineramaInfoOrder" "CRT-1"
[    14.621] (**) NVIDIA(1): Option "MetaModes" "nvidia-auto-select +0+0"
[    14.621] (**) NVIDIA(1): Enabling 2D acceleration
[    15.365] (II) NVIDIA(0): Display (NTS MB24W (CRT-1)) does not support NVIDIA 3D Vision
[    15.365] (II) NVIDIA(0):     stereo.
[    15.437] (II) NVIDIA(1): NVIDIA GPU GeForce GT 610 (GF119) at PCI:7:0:0 (GPU-1)
[    15.437] (--) NVIDIA(1): Memory: 2097152 kBytes
[    15.437] (--) NVIDIA(1): VideoBIOS: 75.19.55.00.03
[    15.437] (II) NVIDIA(1): Detected PCI Express Link width: 16X
[    15.445] (--) NVIDIA(1): Valid display device(s) on GeForce GT 610 at PCI:7:0:0
[    15.445] (--) NVIDIA(1):     CRT-0
[    15.445] (--) NVIDIA(1):     NTS MB24W (CRT-1) (boot, connected)
[    15.445] (--) NVIDIA(1):     DFP-0
[    15.445] (--) NVIDIA(1):     DFP-1
[    15.445] (--) NVIDIA(1): CRT-0: 400.0 MHz maximum pixel clock
[    15.445] (--) NVIDIA(1): NTS MB24W (CRT-1): 400.0 MHz maximum pixel clock
[    15.445] (--) NVIDIA(1): DFP-0: Internal Single Link TMDS
[    15.445] (--) NVIDIA(1): DFP-0: 330.0 MHz maximum pixel clock
[    15.445] (--) NVIDIA(1): DFP-1: Internal Single Link TMDS
[    15.445] (--) NVIDIA(1): DFP-1: 165.0 MHz maximum pixel clock
[    15.445] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
[    15.445] (**) NVIDIA(1):     device NTS MB24W (CRT-1) (Using EDID frequencies has been
[    15.445] (**) NVIDIA(1):     enabled on all display devices.)
[    15.446] (WW) NVIDIA(GPU-1): The EDID for NTS MB24W (CRT-1) contradicts itself: mode
[    15.446] (WW) NVIDIA(GPU-1):     "1600x1200" is specified in the EDID; however, the EDID's
[    15.446] (WW) NVIDIA(GPU-1):     valid HorizSync range (30.000-74.000 kHz) would exclude
[    15.446] (WW) NVIDIA(GPU-1):     this mode's HorizSync (75.0 kHz); ignoring HorizSync check
[    15.446] (WW) NVIDIA(GPU-1):     for mode "1600x1200".
[    15.448] (II) NVIDIA(1): Validated MetaModes:
[    15.448] (II) NVIDIA(1):     "nvidia-auto-select+0+0"
[    15.448] (II) NVIDIA(1): Virtual screen size determined to be 1920 x 1200
[    15.479] (--) NVIDIA(1): DPI set to (95, 95); computed from "UseEdidDpi" X config
[    15.479] (--) NVIDIA(1):     option
[    15.479] (**) NVIDIA(2): Depth 24, (--) framebuffer bpp 32
[    15.479] (==) NVIDIA(2): RGB weight 888
[    15.479] (==) NVIDIA(2): Default visual is TrueColor
[    15.479] (==) NVIDIA(2): Using gamma correction (1.0, 1.0, 1.0)
[    15.479] (**) NVIDIA(2): Option "TwinViewXineramaInfoOrder" "DFP-0"
[    15.479] (II) NVIDIA(2): NVIDIA GPU GeForce GT 610 (GF119) at PCI:2:0:0 (GPU-0)
[    15.479] (--) NVIDIA(2): Memory: 2097152 kBytes
[    15.479] (--) NVIDIA(2): VideoBIOS: 75.19.55.00.03
[    15.479] (II) NVIDIA(2): Detected PCI Express Link width: 16X
[    15.483] (--) NVIDIA(2): Valid display device(s) on GeForce GT 610 at PCI:2:0:0
[    15.483] (--) NVIDIA(2):     CRT-0
[    15.483] (--) NVIDIA(2):     Jean JC229x1-2 (CRT-1) (boot, connected)
[    15.483] (--) NVIDIA(2):     HannStar Display Corp JC199D (DFP-0) (connected)
[    15.483] (--) NVIDIA(2):     DFP-1
[    15.483] (--) NVIDIA(2): CRT-0: 400.0 MHz maximum pixel clock
[    15.483] (--) NVIDIA(2): Jean JC229x1-2 (CRT-1): 400.0 MHz maximum pixel clock
[    15.483] (--) NVIDIA(2): HannStar Display Corp JC199D (DFP-0): Internal Dual Link TMDS
[    15.483] (--) NVIDIA(2): HannStar Display Corp JC199D (DFP-0): 330.0 MHz maximum pixel clock
[    15.483] (--) NVIDIA(2): DFP-1: Internal Single Link TMDS
[    15.483] (--) NVIDIA(2): DFP-1: 165.0 MHz maximum pixel clock
[    15.483] (**) NVIDIA(2): Using HorizSync/VertRefresh ranges from the EDID for display
[    15.483] (**) NVIDIA(2):     device HannStar Display Corp JC199D (DFP-0) (Using EDID
[    15.483] (**) NVIDIA(2):     frequencies has been enabled on all display devices.)
[    15.484] (II) NVIDIA(2): Validated MetaModes:
[    15.484] (II) NVIDIA(2):     "DFP:nvidia-auto-select+0+0"
[    15.484] (II) NVIDIA(2): Virtual screen size determined to be 1280 x 1024
[    15.489] (--) NVIDIA(2): DPI set to (85, 86); computed from "UseEdidDpi" X config
[    15.489] (--) NVIDIA(2):     option
[    15.489] (--) Depth 24 pixmap format is 32 bpp
[    15.489] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[    15.489] (II) NVIDIA:     access.
[    15.498] (II) NVIDIA(0): Setting mode "CRT:nvidia-auto-select+0+0"
[    15.540] Loading extension NV-GLX
[    15.553] (==) NVIDIA(0): Disabling shared memory pixmaps
[    15.553] (==) NVIDIA(0): Backing store disabled
[    15.553] (==) NVIDIA(0): Silken mouse enabled
[    15.553] (**) NVIDIA(0): DPMS enabled
[    15.553] Loading extension NV-CONTROL
[    15.553] (WW) NVIDIA(0): Option "TwinView" is not used
[    15.553] (II) Loading sub module "dri2"
[    15.553] (II) LoadModule: "dri2"
[    15.553] (II) Module "dri2" already built-in
[    15.553] (II) NVIDIA(0): [DRI2] Setup complete
[    15.553] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    15.553] (WW) NVIDIA(0): Not registering RandR
[    15.554] (==) RandR enabled
[    15.562] (II) NVIDIA(1): Setting mode "nvidia-auto-select+0+0"
[    15.616] (==) NVIDIA(1): Disabling shared memory pixmaps
[    15.616] (==) NVIDIA(1): Backing store disabled
[    15.616] (==) NVIDIA(1): Silken mouse enabled
[    15.617] (**) NVIDIA(1): DPMS enabled
[    15.617] (WW) NVIDIA(1): Option "TwinView" is not used
[    15.617] (II) Loading sub module "dri2"
[    15.617] (II) LoadModule: "dri2"
[    15.617] (II) Module "dri2" already built-in
[    15.617] (II) NVIDIA(1): [DRI2] Setup complete
[    15.617] (II) NVIDIA(1): [DRI2]   VDPAU driver: nvidia
[    15.617] (WW) NVIDIA(1): Not registering RandR
[    15.617] (==) RandR enabled
[    15.620] (II) NVIDIA(2): Setting mode "DFP:nvidia-auto-select+0+0"
[    15.702] (==) NVIDIA(2): Disabling shared memory pixmaps
[    15.702] (==) NVIDIA(2): Backing store disabled
[    15.702] (==) NVIDIA(2): Silken mouse enabled
[    15.702] (==) NVIDIA(2): DPMS enabled
[    15.702] (WW) NVIDIA(2): Option "TwinView" is not used
[    15.702] (II) Loading sub module "dri2"
[    15.702] (II) LoadModule: "dri2"
[    15.702] (II) Module "dri2" already built-in
[    15.702] (II) NVIDIA(2): [DRI2] Setup complete
[    15.702] (II) NVIDIA(2): [DRI2]   VDPAU driver: nvidia
[    15.702] (WW) NVIDIA(2): Not registering RandR
[    15.702] (==) RandR enabled
[    15.706] (II) Initializing extension GLX
[    15.993] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[    15.993] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    15.993] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    15.993] (**) Power Button: Applying InputClass "LocalKeyboard"
[    15.993] (II) LoadModule: "evdev"
[    16.017] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    16.017] (II) Module evdev: vendor="X.Org Foundation"
[    16.017] 	compiled for 1.13.1, module version = 2.7.3
[    16.017] 	Module class: X.Org XInput Driver
[    16.017] 	ABI class: X.Org XInput driver, version 18.0
[    16.017] (II) Using input driver 'evdev' for 'Power Button'
[    16.017] (**) Power Button: always reports core events
[    16.017] (**) evdev: Power Button: Device: "/dev/input/event4"
[    16.017] (--) evdev: Power Button: Vendor 0 Product 0x1
[    16.017] (--) evdev: Power Button: Found keys
[    16.017] (II) evdev: Power Button: Configuring as keyboard
[    16.017] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[    16.017] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    16.017] (**) Option "xkb_rules" "evdev"
[    16.017] (**) Option "xkb_model" "evdev"
[    16.017] (**) Option "xkb_layout" "us"
[    16.048] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[    16.048] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    16.048] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    16.048] (**) Power Button: Applying InputClass "LocalKeyboard"
[    16.048] (II) Using input driver 'evdev' for 'Power Button'
[    16.048] (**) Power Button: always reports core events
[    16.048] (**) evdev: Power Button: Device: "/dev/input/event3"
[    16.048] (--) evdev: Power Button: Vendor 0 Product 0x1
[    16.048] (--) evdev: Power Button: Found keys
[    16.048] (II) evdev: Power Button: Configuring as keyboard
[    16.048] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3"
[    16.048] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    16.048] (**) Option "xkb_rules" "evdev"
[    16.048] (**) Option "xkb_model" "evdev"
[    16.048] (**) Option "xkb_layout" "us"
[    16.049] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event6)
[    16.049] (II) No input driver specified, ignoring this device.
[    16.049] (II) This device may have been added with another device file.
[    16.050] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event7)
[    16.050] (II) No input driver specified, ignoring this device.
[    16.050] (II) This device may have been added with another device file.
[    16.050] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event8)
[    16.050] (II) No input driver specified, ignoring this device.
[    16.051] (II) This device may have been added with another device file.
[    16.051] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event9)
[    16.051] (II) No input driver specified, ignoring this device.
[    16.051] (II) This device may have been added with another device file.
[    16.052] (II) config/udev: Adding input device GASIA PS2toUSB Adapter (/dev/input/event1)
[    16.052] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev keyboard catchall"
[    16.052] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev keyboard catchall"
[    16.052] (**) GASIA PS2toUSB Adapter: Applying InputClass "LocalKeyboard"
[    16.052] (II) Using input driver 'evdev' for 'GASIA PS2toUSB Adapter'
[    16.052] (**) GASIA PS2toUSB Adapter: always reports core events
[    16.052] (**) evdev: GASIA PS2toUSB Adapter: Device: "/dev/input/event1"
[    16.052] (--) evdev: GASIA PS2toUSB Adapter: Vendor 0xe8f Product 0x20
[    16.052] (--) evdev: GASIA PS2toUSB Adapter: Found keys
[    16.052] (II) evdev: GASIA PS2toUSB Adapter: Configuring as keyboard
[    16.052] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.0/usb4/4-3/4-3:1.0/input/input1/event1"
[    16.052] (II) XINPUT: Adding extended input device "GASIA PS2toUSB Adapter" (type: KEYBOARD, id 8)
[    16.052] (**) Option "xkb_rules" "evdev"
[    16.052] (**) Option "xkb_model" "evdev"
[    16.052] (**) Option "xkb_layout" "us"
[    16.053] (II) config/udev: Adding input device GASIA PS2toUSB Adapter (/dev/input/event2)
[    16.053] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev pointer catchall"
[    16.053] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev keyboard catchall"
[    16.053] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev pointer catchall"
[    16.053] (**) GASIA PS2toUSB Adapter: Applying InputClass "evdev keyboard catchall"
[    16.053] (**) GASIA PS2toUSB Adapter: Applying InputClass "LocalKeyboard"
[    16.053] (II) Using input driver 'evdev' for 'GASIA PS2toUSB Adapter'
[    16.053] (**) GASIA PS2toUSB Adapter: always reports core events
[    16.053] (**) evdev: GASIA PS2toUSB Adapter: Device: "/dev/input/event2"
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Vendor 0xe8f Product 0x20
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found 9 mouse buttons
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found scroll wheel(s)
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found relative axes
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found x and y relative axes
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found absolute axes
[    16.053] (II) evdev: GASIA PS2toUSB Adapter: Forcing absolute x/y axes to exist.
[    16.053] (--) evdev: GASIA PS2toUSB Adapter: Found keys
[    16.053] (II) evdev: GASIA PS2toUSB Adapter: Configuring as mouse
[    16.053] (II) evdev: GASIA PS2toUSB Adapter: Configuring as keyboard
[    16.053] (II) evdev: GASIA PS2toUSB Adapter: Adding scrollwheel support
[    16.053] (**) evdev: GASIA PS2toUSB Adapter: YAxisMapping: buttons 4 and 5
[    16.053] (**) evdev: GASIA PS2toUSB Adapter: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    16.053] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.0/usb4/4-3/4-3:1.1/input/input2/event2"
[    16.053] (II) XINPUT: Adding extended input device "GASIA PS2toUSB Adapter" (type: KEYBOARD, id 9)
[    16.053] (**) Option "xkb_rules" "evdev"
[    16.053] (**) Option "xkb_model" "evdev"
[    16.053] (**) Option "xkb_layout" "us"
[    16.053] (II) evdev: GASIA PS2toUSB Adapter: initialized for relative axes.
[    16.053] (WW) evdev: GASIA PS2toUSB Adapter: ignoring absolute axes.
[    16.053] (**) GASIA PS2toUSB Adapter: (accel) keeping acceleration scheme 1
[    16.053] (**) GASIA PS2toUSB Adapter: (accel) acceleration profile 0
[    16.053] (**) GASIA PS2toUSB Adapter: (accel) acceleration factor: 2.000
[    16.053] (**) GASIA PS2toUSB Adapter: (accel) acceleration threshold: 4
[    16.054] (II) config/udev: Adding input device GASIA PS2toUSB Adapter (/dev/input/mouse0)
[    16.054] (**) GASIA PS2toUSB Adapter: Applying InputClass "LocalKeyboard"
[    16.054] (II) No input driver specified, ignoring this device.
[    16.054] (II) This device may have been added with another device file.
[    16.054] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[    16.054] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[    16.054] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[    16.054] (**) AT Translated Set 2 keyboard: Applying InputClass "LocalKeyboard"
[    16.054] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    16.054] (**) AT Translated Set 2 keyboard: always reports core events
[    16.054] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[    16.054] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    16.054] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    16.054] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    16.054] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[    16.054] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[    16.054] (**) Option "xkb_rules" "evdev"
[    16.054] (**) Option "xkb_model" "evdev"
[    16.054] (**) Option "xkb_layout" "us"
[    16.054] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[    16.054] (II) No input driver specified, ignoring this device.
[    16.054] (II) This device may have been added with another device file.

System Specs: MSI 890FXA-GD65, AMD Phenom(tm) II X6 1090T Processor 6 core @ 3.2 GHz, 16 GB DDR3 1333, 4x Seagate 1 TB ST31000528AS, 2x Nvidia GeForce GT610

Moderator edit:  Added BBCode code tags -- ewaller

Last edited by ewaller (2013-12-21 18:48:09)

Offline

#55 2013-12-21 17:14:17

pan-bolek
Member
Registered: 2013-12-21
Posts: 5

Re: Xinerama seems to be broken with latest updates

Hopefully you can point me in the right direction and I can learn something as well.

Cheers!

Offline

#56 2013-12-21 17:16:49

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

Interesting, I'm going to have to study it.

Anyone interested in trying the SuSE kernel in Arch? Maybe that will make it work. Could be something broken with the Arch kernel that has always been there but didn't show up until after the 313 nVidia driver.

Offline

#57 2013-12-21 18:46:48

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 18,629

Re: Xinerama seems to be broken with latest updates

pan-bolek,
Welcome to Arch Linux.  Please use BBCode tags when posting output.  I am going to go ahead and add them to your post, you can edit it to see how its done.

Thanks.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#58 2013-12-21 19:09:42

pan-bolek
Member
Registered: 2013-12-21
Posts: 5

Re: Xinerama seems to be broken with latest updates

Thanks ewaller - see, I've learned something already... ;-)

Offline

#59 2013-12-26 00:50:23

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

Finally got a response from my nVidia ticket. Apparently they are looking in to it. Haha, we'll see. I imagine in a few weeks I will get a request to provide more information before they even look at it.

Last edited by oz (2013-12-26 00:51:02)

Offline

#60 2014-01-16 10:49:36

jarshvor
Member
Registered: 2012-07-26
Posts: 31

Re: Xinerama seems to be broken with latest updates

oz, that's somewhat "great" news (ha). They might take ages, but if they actually look at it it might get resolved eventually. Thanks, keep us posted.
wink

Offline

#61 2014-01-16 11:12:45

jarshvor
Member
Registered: 2012-07-26
Posts: 31

Re: Xinerama seems to be broken with latest updates

this might be slightly tangent to the topic,
but this arch user DJYoshaBYD has an interesting post on the nvidia forums on 3+ monitor setup with nouveau and nvidia blob.

https://devtalk.nvidia.com/default/topi … nt=3980519

Offline

#62 2014-02-10 03:04:20

q5sys
Member
Registered: 2014-02-10
Posts: 2

Re: Xinerama seems to be broken with latest updates

Has there been any progress with this?  This is the only thing holding me back from installing Arch on my system.  I have dual Quadro NVS 420 cards pushing 6 screens, Xinerama is critical for me.

Offline

#63 2014-02-10 13:11:29

jarshvor
Member
Registered: 2012-07-26
Posts: 31

Re: Xinerama seems to be broken with latest updates

For some strange reason, as I was fiddling around in relation to the link in my last post, I now have nouveau running, spanning my GT 630 and nvidia integrated graphics.
Hardware accelerated desktop (that is compositing) on all 3 monitors, and dragging windows normally.

Xinerama *is* enabled in xorg.conf, xrandr *is not* working.

in other words: nouveau + xinerama - xrandr and I have accelerated desktop across 3 monitors.

dont ask me how :S i know xinerama should be making compositing unavailable but.... its working.. 0_0

Offline

#64 2014-03-02 14:44:11

q5sys
Member
Registered: 2014-02-10
Posts: 2

Re: Xinerama seems to be broken with latest updates

Has anyone checked to see if this problem still exists with a non-mainline kernel?  I might pop a new drive in my system and see if that makes any difference.   I'm also wondering how this is an nvidia bug when this behavior doesnt occur on any other distro.  Are we compiling X/Xinerama in some odd way compared to other distros?

Offline

#65 2014-03-12 13:16:23

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

It's broken in Ubuntu Saucy also (kernel there is 3.11.0 and nvidia 319.60).

I have seen some mention that using an older kernel may make it work. Or course using an older nVidia also works too so I'm not sure what is going on.

nVidia got back to me on my and ticket and wanted all sorts of detailed logs from my workstation that I simply can not provide due to business security restrictions. I have tried explaining that it's very easy to recreate, just stick two different nVidia cards (not sure if that matters but it's my setup) in the machine and start X with Xinerama "true" and it will crash, but no joy so far.

This issue has gone on way too long. sad

Offline

#66 2014-04-23 01:10:37

karkhaz
Member
Registered: 2014-01-25
Posts: 79

Re: Xinerama seems to be broken with latest updates

oz wrote:

nVidia got back to me on my and ticket and wanted all sorts of detailed logs from my workstation that I simply can not provide

Would you mind sharing what they asked for? Perhaps somebody else on this thread might be able to provide that information instead. It's a miracle that they got back to you, we should use this oppourtunity! Although yes, it does seem obtuse to be asking for that information when it is clear what causes the symptoms, and they should be able to reproduce it...

Offline

#67 2014-04-23 01:17:20

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

karkhaz wrote:
oz wrote:

nVidia got back to me on my and ticket and wanted all sorts of detailed logs from my workstation that I simply can not provide

Would you mind sharing what they asked for? Perhaps somebody else on this thread might be able to provide that information instead. It's a miracle that they got back to you, we should use this oppourtunity! Although yes, it does seem obtuse to be asking for that information when it is clear what causes the symptoms, and they should be able to reproduce it...

Basically this:

Please generate and attach a bugreport which gives us more information. You can
generate one by 'sh nvidia-bug-report.sh' as root user or by ‘sudo sh /usr/bin/nvidia-bug-report.sh’ as a normal user.

You have look at the "nvidia-bug-report.sh" script be see what information it is collecting. Quite a number of logs, hardware information, and such. Maybe nothing critical but it would take some effort to vet that script in a corporate environment. I mean it runs as root for one thing. smile

Edit:
Also, they closed the report after a couple days so yeah, they haven't looked at it.

Last edited by oz (2014-04-23 01:46:28)

Offline

#68 2014-05-03 15:17:43

ZippyF
Member
Registered: 2014-05-02
Posts: 3

Re: Xinerama seems to be broken with latest updates

Reading this thread is a bit disappointing. I have a 2 nvidia gpu, 3 monitor setup that I am struggling to get to work properly.

I am a Linux beginner attempting to set up a new Ubuntu box with a 3 monitor setup. I read here that people have downgraded the kernel to 3.8 and the nvidia driver to 313 to work around problems with Xinerama. I have done some searching to figure out how to downgrade my kernel (I am currently on 14.04 with kernel 3.13), but I don't understand how to do this. I am thinking maybe I should start over and install a previous version of Ubuntu (like Ubuntu 10.04) or is there some other, easier path?

thanks for any help or advice.

Offline

#69 2014-05-07 21:44:05

masmullin
Member
Registered: 2014-04-10
Posts: 28

Re: Xinerama seems to be broken with latest updates

ZippyF wrote:

Reading this thread is a bit disappointing. I have a 2 nvidia gpu, 3 monitor setup that I am struggling to get to work properly.
maybe I should start over and install a previous version of Ubuntu (like Ubuntu 10.04) or is there some other, easier path?

This is the same setup that I have at work.  I have trouble with everything other than Xubuntu 13.10 or Linux MINT 16.  I suggest you install Xubuntu 13.10.

Offline

#70 2014-05-08 22:09:04

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,131
Website

Re: Xinerama seems to be broken with latest updates

ZippyF wrote:

I am a Linux beginner attempting to set up a new Ubuntu box with a 3 monitor setup.

Then you need to ask on the Ubuntu boards: we only support Arch https://wiki.archlinux.org/index.php/Fo … pport_ONLY


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#71 2014-05-28 16:08:32

oz
Member
Registered: 2004-05-20
Posts: 98

Re: Xinerama seems to be broken with latest updates

Just tested the 331.79 pre-release and 337.19 beta driver.  Still broken. hmm

Been broken for over a year now, seriously, wth...

Last edited by oz (2014-05-28 16:09:37)

Offline

#72 2014-05-30 10:32:55

expatcoder
Member
Registered: 2014-05-30
Posts: 4

Re: Xinerama seems to be broken with latest updates

Nvidia 331.67 works just fine here with multiple monitors and Xinerama enabled on a recent kernel (K2000M chip).

uname -a
Linux localhost.localdomain 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

What was an absolute show stopper was gdm and gnome-shell, god help you if you depend on these atrocities O_o

Having wrapped Gnome under the covers for a couple of years with i3wm I just let it be, too much of a hassle to untangle the mess. Trying to get my previous setup running with the new kernel and latest stable Nvidia drivers however, that was a nightmare (as this thread confirms).

In the end I gave up and went with a fresh minimal install, no DE, just i3, startx and StudioFlat + gnome-colors-icon for a clean gtk3 look.

Very, very happy to be free from the worst parts of Gnome, thank you Gnome team for forcing me away! ;-)

As for the problem at hand, if your DM or shell depend on compositing then it seems Xinerama is not an option given that compositing needs to disabled via xorg conf (Nvidia spews some warnings about compositing and Xinerama not playing well together in Xorg.log if you don't explicitly disable it).

Offline

#73 2014-09-23 07:14:58

jose1711
Member
Registered: 2006-07-08
Posts: 143

Re: Xinerama seems to be broken with latest updates

i have been able to run halflife 2 (steam version) and distance beta (albeit stretched) in a windowed mode spanning 3 monitors and xinerama enabled (nvidia 340.32). wm used: openbox - gnome was unable to start (compositing?). does it mean that xinerama issues are gone with newer kernel/nvidia-blob versions?

Offline

Board footer

Powered by FluxBB