| View previous topic :: View next topic |
| Author |
Message |
Graymi
n00b
Joined: 25 Jan 2005
Posts: 50
|
 Posted: Wed Jun 08, 2005 3:22 pm Post subject: Dual Monitor Headache |
 |
|
okay, i'm no ace with gentoo or anything, so i'll try to give as much relevant information as i can.
right.
I have a geforce4 ti 4400. in the DVI socket is a TFT monitor that runs at 1280x1024@60Hz. in the VGA socket is a crt monitor that runs at 1024x768@60Hz.
right.
i've managed to set up the following xorg.conf:
| Code: | # File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "gb"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "explorerps/2"
# Option "Dev Name" "Logitech USB Reciever"
# Option "Dev Phys" "usb-0000:00:03.0-2/input0"
# Option "Device" "/dev/input/mice"
# Option "Buttons" "12"
# Option "ZAxisMapping" "11 12"
# Option "Resolution" "800"
Option "Device" "/dev/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "CRT_monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5 - 48.5
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-70
EndSection
Section "Monitor"
Identifier "LCD_monitor"
HorizSync 24-80
VertRefresh 49-75
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "nv"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "nvidiaCRT"
Driver "nvidia"
BusID "PCI:01:00:0"
VideoRam 131072
Option "RenderAccel" "true"
Option "ConnectedMonitor" "CRT"
# Option "Chipset" "Geforce4 Ti 4400"
#screen 0
EndSection
Section "Device"
Identifier "nvidiaLCD"
Driver "nvidia"
VideoRam 131072
BusID "PCI:01:00:0
Option "RenderAccel" "true"
#Option "Chipset" "Geforce4 Ti 4400"
Option "ConnectedMonitor" "DFP"
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "CRT_Screen"
Device "nvidiaCRT"
Monitor "CRT_monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "LCD_Screen"
Device "nvidiaLCD"
Monitor "LCD_monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600"
ViewPort 0 0
EndSubSection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "dual"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen 0 "LCD_Screen"
Screen 1 "CRT_Screen" leftof "LCD_Screen"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "ServerLayout"
Identifier "crt"
Screen "CRT_Screen"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "ServerLayout"
Identifier "lcd"
Screen "LCD_Screen"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
|
and when i run
X -layout crt
X -layout lcd
i can choose which monitor the display is on. that works fine.
but when i run
X -layout dual
only the lcd comes on... not what i wanted at all.
i've had a look around on the internet, and some suggest setting the BusID different for each output, but setting BusID PCI:01:00:1 just stops whichever monitor its associated with from working atall.
all i wanted was two monitors i could drag my programs between  i would use TwinView, but i think you need the same resolution on both monitors, and the CRT won't go higher than 1024x768 (and i refuse to run my lcd at lower than 1280x1024) |
|
| Back to top |
|
 |
Tlaloc
Guru
Joined: 21 Feb 2005
Posts: 451
Location: Europe - Alps - Tyrol
|
| Posted: Wed Jun 08, 2005 5:53 pm Post subject: |
|
|
You can use Twinview. Just look at the nvidia readme you have in /usr/share/doc/nvidia* for the details how to set it up. Here are the relevant parts of mine xorg.conf for example, but my monitors have the same resolution, though. Look at the MetaModes option especially.
| Quote: |
Section "Monitor"
Identifier "mon"
HorizSync 31.5-81
VertRefresh 56.25-61
Option "DPMS"
EndSection
EndSection
Section "Device"
Identifier "vid"
Driver "nvidia"
# Option "RandRRotation" "true"
Option "NvAgp" "1"
Option "CursorShadow" "true"
Option "CursorShadowAlpha" "150"
Option "Nologo" "true"
Option "DigitalVibrance" "5"
Option "RenderAccel" "true"
#Option "ConnectedMonitor" "DFP-0, CRT-1"
Option "TwinView"
Option "SecondMonitorHorizSync" "31.5-81"
Option "SecondMonitorVertRefresh" "56.25-61"
Option "MetaModes" "1280x1024,1280x1024;1280x1024,null"
Option "TwinViewOrientation" "DFP-0 RightOf CRT-1"
# Option "AllowGLXWithComposite" "true"
EndSection
|
A word of caution still. As I am not certain which monitor will be seen as first and which as second by the nvidia driver you should check that out for yourself first, because if you specify too high horizontal or vertical refresh rates for your crt and if the crt does not return proper EdidFreqs when queried by the driver it may get damaged.
Bye, Valentin. |
|
| Back to top |
|
|
kauschovar
n00b
Joined: 05 Sep 2002
Posts: 17
|
| Posted: Sat Jun 11, 2005 2:58 am Post subject: |
|
|
| Tlaloc wrote: | | You can use Twinview. Just look at the nvidia readme you have in /usr/share/doc/nvidia* for the details how to set it up. Here are the relevant parts of mine xorg.conf for example, but my monitors have the same resolution, though. Look at the MetaModes option especially. |
TwinView doesn't seem to be friendly with separate resolutions. I have a 2048x1536 CRT and a 1600x1200 CRT and there's a large region under the 1600x1200 monitor where the mouse cursor can go and windows sometimes appear, but nothing in that region will ever be rendered so I risk losing windows in the void. That's actually why I'm on the forums now too. |
|
| Back to top |
|
|
babyfai
n00b
Joined: 09 Jun 2002
Posts: 40
|
| Posted: Sat Jun 11, 2005 4:27 am Post subject: |
|
|
I think you need :
#~~~~~~~~~~~~~~
Section "ServerFlags"
Option "Xinerama" "true"
EndSection |
|
| Back to top |
|
|
Tlaloc
Guru
Joined: 21 Feb 2005
Posts: 451
Location: Europe - Alps - Tyrol
|
| Posted: Sat Jun 11, 2005 6:56 am Post subject: |
|
|
| kauschovar wrote: | | Tlaloc wrote: | | You can use Twinview. Just look at the nvidia readme you have in /usr/share/doc/nvidia* for the details how to set it up. Here are the relevant parts of mine xorg.conf for example, but my monitors have the same resolution, though. Look at the MetaModes option especially. |
TwinView doesn't seem to be friendly with separate resolutions. I have a 2048x1536 CRT and a 1600x1200 CRT and there's a large region under the 1600x1200 monitor where the mouse cursor can go and windows sometimes appear, but nothing in that region will ever be rendered so I risk losing windows in the void. That's actually why I'm on the forums now too. |
Look at this post for some hints. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
