View Single Post
Old 02-25-04, 05:47 PM   #2
prplxd
Registered User
 
Join Date: Feb 2004
Posts: 42
Exclamation Try this,...

Take a peek at this and see if it will give you some hints.
You also need the H and V values of your 2nd monitor.


# ************************************************** ********************
# Monitor section
# ************************************************** ********************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My 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-79

# 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-75

vendorname "[My Monitor]"
modelname "[My Monitor]"
ModeLine "1024x768/70Hz" 75 1024 1048 1184 1328 768 771 777 806 -HSync -VSync
EndSection


# ************************************************** ********************
# Graphics device section
# ************************************************** ********************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Geforce4 TwinView"
VendorName "MSI"
BoardName "GF4 TI4400"

# 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 "nvidia"
# 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:1:00:0"

VideoRam 128

Clocks 25.2 28.3

Option "NoLogo" "true"
Option "NvAGP" "1"
Option "TwinView"
Option "SecondMonitorHorizSync" "31.5-79"
Option "SecondMonitorVertRefresh" "56-75"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1024x768,1024x768"
Option "ConnectedMonitor" "crt,crt"

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "Geforce4 TwinView"
Driver "nvidia"
VideoRam 131072
# Insert Clocks lines here if appropriate
Clocks 25.2 28.3
Option "NoLogo" "true"
Option "NvAGP" "1"
Option "TwinView"
Option "SecondMonitorHorizSync" "31.5-79"
Option "SecondMonitorVertRefresh" "56-75"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1024x768,1024x768"
Option "ConnectedMonitor" "crt,crt"
vendorname "MSI"
boardname "Geforce4 TI4400"
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 "Screen AGP TwinView"
Device "Geforce4 TwinView"
Monitor "My Monitor"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1024x768/70Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768/70Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768/70Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 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 "Geforce4 TwinView"

# 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 "Screen AGP TwinView"

# 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 "DRI"
# Mode 0666
# EndSection


Section "InputDevice"

Identifier "Keyboard"

Option "XkbModel" "pc104"
Option "XkbLayout" "us"
Driver "keyboard"
EndSection


Section "InputDevice"

Identifier "Mouse"

Option "Protocol" ""
Option "Device" "/dev/mouse"
Driver "mouse"
Option "Emulate3Buttons"
Option "ZAxisMapping" "4 5"
EndSection

Post back so that we might be able to help you a little more.
prplxd is offline   Reply With Quote