| View previous topic :: View next topic |
| Author |
Message |
theProphecy
n00b
Joined: 29 Oct 2003
Posts: 50
Location: Denmark, Århus-->Åbyhøj
|
 Posted: Sat Nov 15, 2003 4:37 pm Post subject: X + GeForce4-440 GO + two monitors, how? |
 |
|
I haven't been able to find any posts on this problem. But if there is, im sorry. 
The thing i am trying to do is getting two monitors running on X. Not with different x servers on the two screens, but with the same x server running on both, so that it is just an extra space. .
The next problem is its on a laptob, with a Nvidia GeForce4-440 GO card, so its two monitors on the same card.
Can somebody help me out a little, 
_________________
Michael Dahl
theprophecy software
innovations make the future |
|
| Back to top |
|
 |
smasher
Tux's lil' helper
Joined: 15 Nov 2003
Posts: 95
|
| Posted: Sat Nov 15, 2003 6:12 pm Post subject: |
|
|
Here's what I'm using in XF86Config for my FX5600:
Section "Device"
Identifier "NV AGP TwinView"
VendorName "nvidia"
Driver "nvidia"
Option "NvAGP" "3"
# update this with the PCI id of your card. Consult the output
# of the 'lspci' command. The BusID is usually optional when
# only using one graphics card.
#BusID "PCI:1:0:0"
# sample twinview setup
Option "TwinView" "1"
# be sure to replace the HorizSync and VertRefresh with correct values
# for your monitor!
Option "SecondMonitorHorizSync" "30-69"
Option "SecondMonitorVertRefresh" "50-100"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1024x768,1024x768;1024x768,null;800x600,null;640x400,null"
Option "ConnectedMonitor" "crt,crt"
Option "CursorShadow" "1"
Option "CursorShadowAlpha" "64"
Option "CursorShadowYOffset" "2"
Option "CursorShadowXOffset" "4"
Option "TVStandard" "NTSC-M"
EndSection |
|
| Back to top |
|
|
theProphecy
n00b
Joined: 29 Oct 2003
Posts: 50
Location: Denmark, Århus-->Åbyhøj
|
| Posted: Sat Nov 15, 2003 9:09 pm Post subject: |
|
|
Well, it seems its not working for me... I don't know why...
Here is my XF86Config
| Code: |
Section "Device"
BoardName "GeForce4 440 Go"
BusID "PCI:1:0:0"
Driver "nvidia"
Identifier "Device[0]"
Option "NoLogo" "on"
#Dual screens
Option "TwinView" "1"
Option "SecondMonitorHorizSync" "30-69"
Option "SecondMonitorVertRefresh" "50-100"
Option "MetaNodes" "1400x1050,1280x1024; 1280x1024,1280x1024; 1024x768,1024x768; 800x600,800x600; 640x480,640x480"
Option "TwinViewOrientation" "LeftOf"
Option "ConnectedMonitor" "DFP, CRT"
vendorname ""
EndSection
|
_________________
Michael Dahl
theprophecy software
innovations make the future |
|
| Back to top |
|
|
smasher
Tux's lil' helper
Joined: 15 Nov 2003
Posts: 95
|
| Posted: Sun Nov 16, 2003 12:09 am Post subject: |
|
|
Are you sure this is correct? It's only needed when you have more than one video card. I'm told the correct value can be found with lspci.
| Code: |
Identifier "Device[0]"
|
This looks a little suspicious. The section called "Screen" should have matching device names, I believe...don't hold me to this one
If it'll help further here's my whole XF86Config file:
| Code: |
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# 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 XFREE86 PROJECT 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 XFree86 Project 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
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) 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 Type1 and FreeType font modules
Load "type1"
Load "speedo"
# Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
Load "v4l"
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)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# 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 "Keyboard"
# 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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
# Option "XkbRules" "xfree86"
# Option "XkbModel" "microsoft"
# Option "XkbLayout" "us"
# Option "XkbKeycodes" "xfree86"
# Option "XkbTypes" "complete"
# Option "XkbCompat" "complete"
# Option "XkbSymbols" "us(pc104win)"
# Option "XkbGeometry" "pc(pc104)"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" ""
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5"
# 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 XF86Config 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 "dell"
# 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 30-70
# 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-160
vendorname "Dell"
modelname "UltraScan-17FS"
ModeLine "1024x768/85Hz" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync
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 "vga"
# 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
Option "NvAGP" "1"
Option "CursorShadow" "1"
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "NV AGP TwinView"
VendorName "nvidia"
Driver "nvidia"
Option "NvAGP" "3"
# update this with the PCI id of your card. Consult the output
# of the 'lspci' command. The BusID is usually optional when
# only using one graphics card.
#BusID "PCI:1:0:0"
# sample twinview setup
Option "TwinView" "1"
# be sure to replace the HorizSync and VertRefresh with correct values
# for your monitor!
Option "SecondMonitorHorizSync" "30-69"
Option "SecondMonitorVertRefresh" "50-100"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1024x768,1024x768;1024x768,null;800x600,null;640x400,null"
Option "ConnectedMonitor" "crt,crt"
Option "CursorShadow" "1"
Option "CursorShadowAlpha" "64"
Option "CursorShadowYOffset" "2"
Option "CursorShadowXOffset" "4"
Option "TVStandard" "NTSC-M"
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 1"
Device "NV AGP TwinView"
Monitor "dell"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768/85Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768/85Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768/85Hz" "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 "NV AGP 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 1"
# 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
|
|
|
| Back to top |
|
|
theProphecy
n00b
Joined: 29 Oct 2003
Posts: 50
Location: Denmark, Århus-->Åbyhøj
|
| Posted: Sun Nov 16, 2003 7:04 am Post subject: |
|
|
Well i don't think that the screen and device should have the same name, but im not shure... But the config is working, just not the TwinView part (yet )...
Well here is the part of my XF86Config thats about the screen...
| Code: |
# **********************************************************************
# Display Section
# **********************************************************************
###
### Monitors
###
Section "Monitor"
HorizSync 31-70
Option "IgnoreEDID" "on"
Identifier "Monitor[0]"
ModelName "Dell 8200"
VendorName "--> LCD"
VertRefresh 58-78
UseModes "Modes[0]"
EndSection
###
### Modes
###
Section "Modes"
Identifier "Modes[0]"
# -- 1400x1050 @ 60z --
Modeline "1400x1050" 129 1400 1464 1656 1960 1050 1051 1054 1100
EndSection
###
### Screens
###
Section "Screen"
DefaultDepth 24
SubSection "Display"
Depth 16
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1400x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection
###
### Devices
###
Section "Device"
BoardName "GeForce4 440 Go"
BusID "PCI:1:0:0"
Driver "nvidia"
Identifier "Device[0]"
Option "NoLogo" "on"
#Dual screens
Option "TwinView" "1"
Option "SecondMonitorHorizSync" "30-69"
Option "SecondMonitorVertRefresh" "50-100"
Option "MetaNodes" "1400x1050,1280x1024; 1280x1024,1280x1024; 1024x768,1024x768; 800x600,800x600; 640x480,640x480"
Option "TwinViewOrientation" "LeftOf"
Option "ConnectedMonitor" "DFP, CRT"
vendorname ""
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen[0]"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "USB Mouse" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
|
_________________
Michael Dahl
theprophecy software
innovations make the future |
|
| Back to top |
|
|
smasher
Tux's lil' helper
Joined: 15 Nov 2003
Posts: 95
|
| Posted: Sun Nov 16, 2003 5:58 pm Post subject: |
|
|
Hmm... I'm not sure what the max resolution specs are for TwinView but you might try activating your other meta modes with CTRL-ALT [keypad]- or CTRL-ALT [keypad]+.
Other than that you might test it with my config, edit the orientation, modeline, and connected monitor settings. |
|
| Back to top |
|
|
theProphecy
n00b
Joined: 29 Oct 2003
Posts: 50
Location: Denmark, Århus-->Åbyhøj
|
| Posted: Fri Nov 21, 2003 7:05 pm Post subject: |
|
|
Well i know as muchs, as it is working in Windows, so it HAS TO work in linux..
_________________
Michael Dahl
theprophecy software
innovations make the future |
|
| Back to top |
|
|
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2508
Location: Silver City, NM
|
| Posted: Fri Nov 21, 2003 7:52 pm Post subject: Re: X + GeForce4-440 GO + two monitors, how? |
|
|
| theProphecy wrote: | [...]
The next problem is its on a laptob, with a Nvidia GeForce4-440 GO card, so its two monitors on the same card.
Can somebody help me out a little, |
I've got TwinView working on my laptop (and I love it). I just needed to add two lines to the Nvidia card section of my XF86Config: | Code: | option "TwinView"
option "MetaModes" "1600x1200,1600x1200; NULL,1600x1200" |
I'm using an Nvidia GeForce 2 Go.
The Nvidia readme.txt had all the info I needed to get up and running. Here is an excerpt from APPENDIX K: CONFIGURING A LAPTOP: | Quote: | All mobile NVIDIA chips support TwinView. TwinView on a laptop can
be configured in the same way as on a desktop machine (please refer
to APPENDIX I above); note that in a TwinView configuration using
the laptop's internal flat panel and an external CRT, the CRT is the
primary display device (specify it's HorizSync and VertRefresh in
the Monitor section of your XF86Config file) and the flat panel is
the secondary display device (specify it's HorizSync and VertRefresh
through the SecondMonitorHorizSync and SecondMonitorVertRefresh options).
You can also employ the UseEdidFreqs option to acquire the HorizSync and
VertRefresh from the EDID of each display devices, and not worry about
setting them in your XF86Config file (this should only be done if you
trust your display device's reported EDIDs -- please see the description
of the UseEdidFreqs option in APPENDIX D for details). |
One thing I've discovered about my laptop is that it is not possible to use it to drive two external monitors in TwinView mode. If I want to use TwinView then one of the screens must be the built-in lcd screen. Nor have I found a way to make the built-in lcd the primary display device.
Finally, when TwinView fails to work for you, what happens? Any interesting messages in the log files or burbs or hiccups when X starts up or does it just appear to ignore all TwinView related parts of your config file? |
|
| Back to top |
|
|
earlNameless
n00b
Joined: 01 Apr 2003
Posts: 47
|
| Posted: Sat Nov 22, 2003 4:01 am Post subject: |
|
|
I do not think this will do anything to the people currently viewing this thread, but it might some other people.
i am using a crt monitor and a tv
this is the part of my XF86Config file:
| Code: |
# Device configured by xf86config:
Section "Device"
Identifier "geforece4nv"
# Driver "nv"
Driver "nvidia"
Option "NvAGP" "3"
#VideoRam 65536
# Insert Clocks lines here if appropriate
# twinview settings
Option "TwinView" "1"
Option "SecondMonitorHorizSync" "30-69"
Option "SecondMonitorVertRefresh" "50-70"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1280x1024, 640x480"
Option "ConnectedMonitor" "CRT, DFP"
EndSection |
|
|
| Back to top |
|
|
telex4
l33t
Joined: 21 Sep 2002
Posts: 704
Location: Reading, UK
|
| Posted: Sat Dec 13, 2003 6:06 pm Post subject: |
|
|
To pick up on this, I've got it working so that I either have a cloned screen, or one large screen that spans the two monitors. But I find that solution a little bit annoying because if I run a fullscreen app, it spans across the two monitors.
Can I set my laptop up, either with twinview or by setting up a separate display, so that I can have two distinct screens rather than one large screen? Or at least so that non-KDE apps will fullscreen only in one of the two monitors (since KDE supports maximising only in one). I only want to be able to put odd things onto the second screen (the CRT) like a browser window, a video, etc. It needn't be too interactive. |
|
| Back to top |
|
|
smasher
Tux's lil' helper
Joined: 15 Nov 2003
Posts: 95
|
| Posted: Sat Dec 13, 2003 7:39 pm Post subject: |
|
|
For full screen apps you'll need to make sure you have the metamodes setup correctly. Here's what I'm using:
| Code: | Option "MetaModes" "1280x1024,1280x1024;1280x1024,1024x768;1024x768,1024x768;1024x768,null;800x600,null;640x400,null"
|
Note the 'null' modes. I can't think of any games I have that doesn't switch to a single monitor when going to full screen mode. The only other option would be to switch modes manually (ctrl-alt-keypadminus or ctrl-alt-kaypadplus) before starting the program.
If you're using KDE you might want to enable Xinerama support. It's located in the Window Behaviour KDE control panel under the Advanced tab.
Oh, and speaking of games... Unreal tournament is kicks running at 2560x2048. I was amazed to find out it actually worked with dual head under linux. |
|
| 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
