You are not logged in.

#1 2009-09-17 14:24:35

moonman89
Member
Registered: 2009-09-17
Posts: 6

2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

Hey guys,
I've managed to get 2 screens working on my GTX260 PCI-E card. Thats fine.
The issue I'm having is getting the 3rd screen and 2nd card to work.

The second PCI card is a FX5200. I've posted relevant info's below. Any help would be fantastic, I want this 3rd monitor to run VM windows seamlessly smile

[root@moonman-linux ~]# lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1)
05:01.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
[root@moonman-linux ~]#

xorg.conf

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildmeister@builder63)  Fri Aug 14 17:55:55 PDT 2009


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 1280 0
    Screen      1  "Screen1" LeftOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "ServerFlags"

# Removed Option "Xinerama" "0"
    Option         "Xinerama" "1"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 75.0
    VertRefresh     56.0 - 61.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Proview"
    HorizSync       30.0 - 80.0
    VertRefresh     60.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Proview"
    HorizSync       30.0 - 80.0
    VertRefresh     60.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 260"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 260"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce FX 5200"
    BusID          "PCI:5:1:0"
    Screen          2
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Extensions"
    Option         "Composite"
EndSection

Xorg.0.log

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH i686 
Current Operating System: Linux moonman-linux 2.6.30-ARCH #1 SMP PREEMPT Mon Aug 17 18:04:53 CEST 2009 i686
Build Date: 04 September 2009  03:37:03PM
 
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 17 23:41:48 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Device0"
(**) |-->Screen "Screen1" (1)
(**) |   |-->Monitor "Monitor1"
(**) |   |-->Device "Device1"
(**) |-->Screen "Screen2" (2)
(**) |   |-->Monitor "Monitor2"
(**) |   |-->Device "Device2"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(**) Option "Xinerama" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/100dpi").
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/75dpi").
(WW) The directory "/usr/share/fonts/TTF" does not exist.
    Entry deleted from font path.
(==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/Type1,
    built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0xec0
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:1:0:0) 10de:05e2:1043:82cf nVidia Corporation GT200 [GeForce GTX 260] rev 161, Mem @ 0xee000000/16777216, 0xd0000000/268435456, 0xec000000/33554432, I/O @ 0x0000a000/128, BIOS @ 0x????????/524288
(--) PCI: (0:5:1:0) 10de:0322:1682:203e nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xf0000000/16777216, 0xe0000000/134217728, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
    [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(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
    Module class: X.Org Server Extension
(II) NVIDIA GLX Module  185.18.36  Fri Aug 14 17:50:12 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(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
    Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver  185.18.36  Fri Aug 14 17:24:40 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.6.3.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is
(WW) NVIDIA(0):     supported through the NVIDIA 173.14.xx Legacy drivers.
(WW) NVIDIA(0):     Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0):     more information.  The 185.18.36 NVIDIA driver will ignore
(WW) NVIDIA(0):     this GPU.  Continuing probe... 
(II) resource ranges after probing:
    [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
(**) 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): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "DFP: nvidia-auto-select +0+0"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0):     enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce GTX 260 (GT200) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 917504 kBytes
(--) NVIDIA(0): VideoBIOS: 62.00.52.00.00
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce GTX 260 at PCI:1:0:0:
(--) NVIDIA(0):     Proview (CRT-0)
(--) NVIDIA(0):     Samsung SyncMaster (DFP-1)
(--) NVIDIA(0): Proview (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Display Device found referenced in MetaMode: DFP-1
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1152x864" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1152x864".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "640x480" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (72.8 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "640x480".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "640x480" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "640x480".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "800x600" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (72.2 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "800x600".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "800x600" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "800x600".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1024x768" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (70.1 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1024x768".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1024x768" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1024x768".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1280x1024" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid HorizSync range (30.000-75.000 kHz) would
(WW) NVIDIA(0):     exclude this mode's HorizSync (80.0 kHz); ignoring
(WW) NVIDIA(0):     HorizSync check for mode "1280x1024".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1280x1024" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1280x1024".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1152x864" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1152x864".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "640x480" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (72.8 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "640x480".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "640x480" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "640x480".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "800x600" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (72.2 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "800x600".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "800x600" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "800x600".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1024x768" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (70.1 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1024x768".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1024x768" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1024x768".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1280x1024" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid HorizSync range (30.000-75.000 kHz) would
(WW) NVIDIA(0):     exclude this mode's HorizSync (80.0 kHz); ignoring
(WW) NVIDIA(0):     HorizSync check for mode "1280x1024".
(WW) NVIDIA(0): The EDID for Samsung SyncMaster (DFP-1) contradicts itself:
(WW) NVIDIA(0):     mode "1280x1024" is specified in the EDID; however, the
(WW) NVIDIA(0):     EDID's valid VertRefresh range (56.000-61.000 Hz) would
(WW) NVIDIA(0):     exclude this mode's VertRefresh (75.0 Hz); ignoring
(WW) NVIDIA(0):     VertRefresh check for mode "1280x1024".
(II) NVIDIA(0): Assigned Display Device: DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "DFP:nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "TwinView" "0"
(**) NVIDIA(1): Option "MetaModes" "CRT: nvidia-auto-select +0+0"
(**) NVIDIA(1): Option "TwinViewXineramaInfoOrder" "CRT-0"
(**) NVIDIA(1): Enabling RENDER acceleration
(II) NVIDIA(1): NVIDIA GPU GeForce GTX 260 (GT200) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(1): Memory: 917504 kBytes
(--) NVIDIA(1): VideoBIOS: 62.00.52.00.00
(II) NVIDIA(1): Detected PCI Express Link width: 16X
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce GTX 260 at PCI:1:0:0:
(--) NVIDIA(1):     Proview (CRT-0)
(--) NVIDIA(1):     Samsung SyncMaster (DFP-1)
(--) NVIDIA(1): Proview (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(1): Samsung SyncMaster (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(1): Display Device found referenced in MetaMode: CRT-0
(WW) NVIDIA(1): The EDID for Proview (CRT-0) contradicts itself: mode
(WW) NVIDIA(1):     "800x600" is specified in the EDID; however, the EDID's
(WW) NVIDIA(1):     valid VertRefresh range (60.000-75.000 Hz) would exclude
(WW) NVIDIA(1):     this mode's VertRefresh (56.2 Hz); ignoring VertRefresh
(WW) NVIDIA(1):     check for mode "800x600".
(II) NVIDIA(1): Assigned Display Device: CRT-0
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1):     "CRT:nvidia-auto-select+0+0"
(II) NVIDIA(1): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(1): DPI set to (95, 96); computed from "UseEdidDpi" X config
(--) NVIDIA(1):     option
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  Yes, I do.
(II) resource ranges after preInit:
    [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GPU GART.
(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 "DFP:nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(1):     may not be running or the "AcpidSocketPath" X
(II) NVIDIA(1):     configuration option may not be set correctly.  When the
(II) NVIDIA(1):     ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(1):     try to use it to receive ACPI event notifications.  For
(II) NVIDIA(1):     details, please see the "ConnectToAcpid" and
(II) NVIDIA(1):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(1):     Config Options in the README.
(II) NVIDIA(1): Setting mode "CRT:nvidia-auto-select+0+0"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(1): Disabling shared memory pixmaps
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(1): Backing store disabled
(==) NVIDIA(1): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(1): DPMS enabled
(==) RandR enabled
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 2.2.5
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Microsoft IntelliMouse? Explorer
(**) Microsoft Microsoft IntelliMouse? Explorer: always reports core events
(**) Microsoft Microsoft IntelliMouse? Explorer: Device: "/dev/input/event4"
(II) Microsoft Microsoft IntelliMouse? Explorer: Found 9 mouse buttons
(II) Microsoft Microsoft IntelliMouse? Explorer: Found x and y relative axes
(II) Microsoft Microsoft IntelliMouse? Explorer: Found scroll wheel(s)
(II) Microsoft Microsoft IntelliMouse? Explorer: Configuring as mouse
(**) Microsoft Microsoft IntelliMouse? Explorer: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft IntelliMouse? Explorer: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft IntelliMouse? Explorer" (type: MOUSE)
(**) Microsoft Microsoft IntelliMouse? Explorer: (accel) keeping acceleration scheme 1
(**) Microsoft Microsoft IntelliMouse? Explorer: (accel) filter chain progression: 2.00
(**) Microsoft Microsoft IntelliMouse? Explorer: (accel) filter stage 0: 20.00 ms
(**) Microsoft Microsoft IntelliMouse? Explorer: (accel) set acceleration profile 0
(II) Microsoft Microsoft IntelliMouse? Explorer: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Microsoft? Digital Media Pro Keyboard
(**) Microsoft Microsoft? Digital Media Pro Keyboard: always reports core events
(**) Microsoft Microsoft? Digital Media Pro Keyboard: Device: "/dev/input/event6"
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Found 1 mouse buttons
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Found scroll wheel(s)
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Found x and y absolute axes
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Found keys
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Configuring as mouse
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Configuring as keyboard
(**) Microsoft Microsoft? Digital Media Pro Keyboard: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft? Digital Media Pro Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft? Digital Media Pro Keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Microsoft Microsoft? Digital Media Pro Keyboard: (accel) keeping acceleration scheme 1
(**) Microsoft Microsoft? Digital Media Pro Keyboard: (accel) filter chain progression: 2.00
(**) Microsoft Microsoft? Digital Media Pro Keyboard: (accel) filter stage 0: 20.00 ms
(**) Microsoft Microsoft? Digital Media Pro Keyboard: (accel) set acceleration profile 0
(II) Microsoft Microsoft? Digital Media Pro Keyboard: initialized for absolute axes.
(II) config/hal: Adding input device Microsoft Microsoft? Digital Media Pro Keyboard
(**) Microsoft Microsoft? Digital Media Pro Keyboard: always reports core events
(**) Microsoft Microsoft? Digital Media Pro Keyboard: Device: "/dev/input/event5"
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Found keys
(II) Microsoft Microsoft? Digital Media Pro Keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsoft Microsoft? Digital Media Pro Keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
[root@moonman-linux ~]# lsmod
Module                  Size  Used by
ipv6                  277908  22 
fan                     4392  0 
battery                10984  0 
ac                      4360  0 
fuse                   60896  2 
snd_seq_dummy           2696  0 
snd_hda_codec_realtek   206504  1 
joydev                 10400  0 
snd_seq_oss            31168  0 
snd_seq_midi_event      7012  1 snd_seq_oss
snd_seq                53744  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          6768  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_hda_intel          26664  0 
snd_hda_codec          71716  2 snd_hda_codec_realtek,snd_hda_intel
intel_agp              27484  0 
nvidia               9592776  36 
snd_pcm_oss            40352  0 
snd_mixer_oss          17540  1 snd_pcm_oss
snd_hwdep               7656  1 snd_hda_codec
iTCO_wdt               10952  0 
usbhid                 40608  0 
i2c_i801                9656  0 
ppdev                   7656  0 
ohci1394               30196  0 
snd_pcm                73672  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer              21100  2 snd_seq,snd_pcm
iTCO_vendor_support     3080  1 iTCO_wdt
agpgart                32756  2 intel_agp,nvidia
hid                    42496  1 usbhid
pcspkr                  2372  0 
i2c_core               22776  2 nvidia,i2c_i801
thermal                13888  0 
parport_pc             36964  1 
ieee1394               85324  1 ohci1394
serio_raw               5704  0 
lp                      9700  0 
parport                34380  3 ppdev,parport_pc,lp
button                  5556  0 
slhc                    5796  0 
snd                    58436  11 snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_hwdep,snd_pcm,snd_timer
soundcore               6848  1 snd
snd_page_alloc          8876  2 snd_hda_intel,snd_pcm
evdev                  10176  10 
processor              35800  4 
sg                     27928  0 
r8169                  33896  0 
mii                     4804  1 r8169
natsemi                27904  0 
rtc_cmos               11212  0 
rtc_core               18048  1 rtc_cmos
rtc_lib                 2500  1 rtc_core
xfs                   578752  1 
exportfs                4260  1 xfs
sd_mod                 27328  3 
sr_mod                 16612  0 
cdrom                  36032  1 sr_mod
uhci_hcd               23540  0 
floppy                 55780  0 
ehci_hcd               35664  0 
usbcore               150192  4 usbhid,uhci_hcd,ehci_hcd
ata_piix               23080  2 
ahci                   34004  0 
ata_generic             4680  0 
pata_jmicron            3044  0 
pata_acpi               4228  0 
libata                168012  5 ata_piix,ahci,ata_generic,pata_jmicron,pata_acpi
scsi_mod              110708  4 sg,sd_mod,sr_mod,libata
[root@moonman-linux ~]#

Is this even possible??

Offline

#2 2009-09-17 14:35:54

moonman89
Member
Registered: 2009-09-17
Posts: 6

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

OK, Just changed the screen option in DEVICE... And now I'm getting this in my log files. When I try and install that package with pacman, it wants to remove the normal nvidia driver. Can I run one for each graphics card?

Xorg.0.log

(II) Module "ramdac" already built-in
(WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is
(WW) NVIDIA(0):     supported through the NVIDIA 173.14.xx Legacy drivers.
(WW) NVIDIA(0):     Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0):     more information.  The 185.18.36 NVIDIA driver will ignore
(WW) NVIDIA(0):     this GPU.  Continuing probe... 
(II) resource ranges after probing:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[b]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[b]
        [5] -1  0       0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888

Offline

#3 2009-09-17 14:59:24

Zariel
Member
Registered: 2008-10-07
Posts: 446

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

You need the nvidia-legacy package also, i would bet that it conflicts with nvidia driver also, you could try using nouveau mind you.

/e its the nvidia-173xx which does conflict. Ill try to work around it.

Last edited by Zariel (2009-09-17 15:01:37)

Offline

#4 2009-09-17 15:24:12

moonman89
Member
Registered: 2009-09-17
Posts: 6

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

Cool, I'll have a look down the nouveau path now smile

Offline

#5 2009-09-20 09:58:01

moonman89
Member
Registered: 2009-09-17
Posts: 6

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

That didn't seem to want to work at all.
Does anyone know how I can install both the legacy Nvidia driver and the nvidia dirver?

Offline

#6 2009-09-20 10:59:47

Dheart
Member
From: Sofia, Bulgaria
Registered: 2006-10-26
Posts: 956

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

That's not possible since they both use vitually the same files.... I don't think using chroot would help either.....


My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

Offline

#7 2009-09-20 21:23:05

moonman89
Member
Registered: 2009-09-17
Posts: 6

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

So I would have more luck with an older PCI VGA card and use the default driver then?

Offline

#8 2009-09-20 21:25:01

Zariel
Member
Registered: 2008-10-07
Posts: 446

Re: 2 Nvidia GFX cards one PCI-E and ONE PCI , 3 Screens, Compiz???

Try using vesa for the second card, can you not specify what card uses what driver?

Offline

Board footer

Powered by FluxBB