| View previous topic :: View next topic |
| Author |
Message |
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
 Posted: Tue Jun 01, 2004 4:15 pm Post subject: dual head, xinerama, (kde), ati radeon... trouble |
 |
|
Hi,
sorry to ask this again (I guess), but I can't figure out how to do it...
I have an ATI Radeon 9800 card, with 2 monitors.
The monitors are different, I mean: primary display should do 1280*1024; secondary can't get above 640*480 (currently)...
I use KDE and'd like to have the screen as it is now, with my secondary screen just "extra". So no toolbar's on it (by default). Also, window's should maximize to the screen (just one, not the two).
currently I'm using the ati-drivers (in portage). I got it a bit to work using this XF86Config (snipped):
| Code: |
Section "Monitor"
Identifier "Iiyama"
HorizSync 30-150
VertRefresh 50-200
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
HorizSync 31.5
VertRefresh 50-70
EndSection
Section "Device"
Identifier "ATI Graphics Adapter connector 0"
Driver "fglrx"
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "PAL-B"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4e48
Screen 0
EndSection
Section "Device"
Identifier "ATI Graphics Adapter connector 1"
Driver "fglrx"
BusID "PCI:1:0:0" # vendor=1002, device=4e48
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter connector 0"
Monitor "Iiyama"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
Section "Screen"
Identifier "Screen1"
Device "ATI Graphics Adapter connector 1"
Monitor "Monitor1"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Server Layout"
Screen "Screen0"
Screen "Screen1" LeftOf "Screen0"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
|
This generates kind of 2 "screens", but there is no interaction between them (only the mouse pointer is able to cross screen-boundary).
I can't drag windows accros, my background isn't there anymore,...
I also checked the KDE-config-pannel but it keeps telling me that I don't have a multi-monitor setup.
I read somewhere (can't find it anymore) to USE xinerama. I did, re-emerged qt and libsdl (as described). Still kde tells me I don't have a multiple monitor setup...
what to do? is it even possible?
Some side info: I use kernel 2.6.5 (gentoo-dev-sources), on a P4 with HT. All progs are optimized -march=pentium4 -O2
Last edited by nielchiano on Wed Jun 02, 2004 5:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Tue Jun 01, 2004 4:54 pm Post subject: |
|
|
You have found a disadvantage of using linux over windows. Currently, Xfree's support for dual monitors needs a lot of work. The setup you have is called "Dual Head", which essentially runs 2 instances of X. With this setup, the only thing the 2 displays have in common is a mouse and keyboard. You cannot move a window from one display to the next, nor can you alt+tab between windows on different displays.
The alternative is the "Big Desktop" option, but if you maximize a window here it will take up both displays.
To my knowledge, there really isn't a way to handle dual displays in linux like you can in windows...and I don't really think Xfree has plans to make it so. If you happen across a means of doing this, I would be interested in hearing it! 
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
Watchoo
Tux's lil' helper
Joined: 24 May 2004
Posts: 79
Location: Slovakia
|
| Posted: Tue Jun 01, 2004 6:44 pm Post subject: |
|
|
I must agree with YopWongSapn , linux really can't handle two monitors in a usefull way .... so in linux I am using only single display for now ...
_________________
Error 404: "Beer not found !!!" |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Tue Jun 01, 2004 6:53 pm Post subject: |
|
|
I would like to clarify that dispite this inconvenience, dual displays in linux are still quite useful. I have 2x 20" trinitrons on my radeon 9600 pro, and love it. Wouldn't trade that for a single display. 
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Tue Jun 01, 2004 7:22 pm Post subject: |
|
|
| and how are they set-up? big-desktop? |
|
| Back to top |
|
|
Scott Price
n00b
Joined: 07 Feb 2003
Posts: 44
Location: Hopkins, MN
|
| Posted: Tue Jun 01, 2004 7:36 pm Post subject: |
|
|
I have been using 2 monitors in Linux since XFree 3.3.6. There are a couple of different methods of running Linux with more than one monitor.
1 - Dual X displays: Pro: DRI works. Con: Can't move windows between monitors
2 - Same as above with Xinerama: Pro: Can move windows between monitors. Con: DRI currently doesn't work
3 - Merged Frame buffer. Pros: DRI works, Can move windows between screens. Con ?
I think ATI calls the merged frame buffer "Twin-View", but I may be wrong.
I am currently using a PNY nVidia GeForce FX5600 with dual monitor support. It works great. I use the nVidia binary driver in the merged frame buffer mode. I will shortly be adding another PNY card to give myself 4 monitors. 
Scott =) |
|
| Back to top |
|
|
Sugarat
Guru
Joined: 24 Jul 2002
Posts: 348
|
| Posted: Tue Jun 01, 2004 8:16 pm Post subject: |
|
|
I will soon have 3 Sun 22" displays connected.
As for getting X.org working on all three... I'm dreading it..
_________________
--[ UltraSPARC ]--
Accept no imitations |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Tue Jun 01, 2004 8:58 pm Post subject: |
|
|
| Scott Price wrote: | | I think ATI calls the merged frame buffer "Twin-View", but I may be wrong. |
Actually, that's what nVidia calls it. ATI just calls it "Big Desktop"
I've not heard much about this Xinerama...I'll have to look into it. Know of any good references to get me started?
One more note on the merged frame buffer...Con is that when you maximize a window it takes up both displays (on the Radeon, anyway).
| nielchiano wrote: | | and how are they set-up? big-desktop? |
If you use the flgrxconfig script that comes with the ati-drivers emerge, you will have no troubles setting up the Big Desktop or Dual Head modes.
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
superjaded
l33t
Joined: 05 Jul 2002
Posts: 802
|
| Posted: Tue Jun 01, 2004 10:25 pm Post subject: |
|
|
I've just recently converted my used-to-be Windows computer to Linux. And that Windows computer sports both an ATI Radeon 9600pro and two monitors hooked up to it.
I've tried both Dual Head (which seemed more like what I'm used to in WIndows than "Big Desktop") and Big Desktop. Dual Head "sort of" worked, well.. not really.. I think it was acting the same way as the terminal -- just showing a the same thing I saw in the primary monitor (Clone view, type).
But Big Desktop doesn't seem to work at all. Here's the log from me trying to do Big Desktop. As you can tell, I have the additional challenge of trying to use Xorg instead of Xfree 4.3. Is that why DRI doesn't work? Oddly enough I get the same error with single monitor mode, but it still works fine for non-DRI. Quite a few lines from that log that make me nervous.. like the "clone (secondary) head:" line. -_-
Last edited by superjaded on Tue Jun 01, 2004 10:36 pm; edited 1 time in total |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Tue Jun 01, 2004 10:34 pm Post subject: |
|
|
File Not Found. Re-post the link?
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
superjaded
l33t
Joined: 05 Jul 2002
Posts: 802
|
| Posted: Tue Jun 01, 2004 10:37 pm Post subject: |
|
|
Woops. Typo.
Should work now. |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Tue Jun 01, 2004 10:42 pm Post subject: |
|
|
hmmm...that one timed out. 
EDIT: OK, it works now.
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
superjaded
l33t
Joined: 05 Jul 2002
Posts: 802
|
| Posted: Tue Jun 01, 2004 10:43 pm Post subject: |
|
|
Yeah, sometimes my ISP picks convenient times to go down.
Should work now, again. 
EDIT: Actually, nix that config. I forgot I re-ran fglrxconfig for single monitor config. |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Wed Jun 02, 2004 10:00 am Post subject: |
|
|
| YopWongSapn wrote: | | I've not heard much about this Xinerama...I'll have to look into it. Know of any good references to get me started? |
any? |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 10:30 am Post subject: |
|
|
um, I got the "Big Desktop" to work with my ati 9800 pro card.
Just one thing puzzles me is that how do I know which monitor is primary or secondary, and which one is set to be on the left or right? There is one session at the fglrxconfig, it's asking | Code: |
horizontal arrangement: monitor connector: 1 => left display
|
,
| Code: | | horizontal arrangement: monitor connector: 1 => right display |
and there is an option for | Code: | | "overlapping screen" [y/n] |
?
, it's very vague here, cuz what exactly does it mean by that, meaning left display as the primary one if I pick that, and vice versa?
I think this is pretty important, I did indeed get them to work, but I'm afraid that both monitors may get the wrong syncs causing my monitors burned out or inconsistency.., since that choosing "Big Desktop" doesn't have the option changing resolution for each screen, it's odd..
so there is only one screen, but how does it manage to get the syncs taken place correctly...
Here is my lame working one though..
| Code: |
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# 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.
# **********************************************************************
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# 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"
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
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/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
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><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" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2" #must need it, closest match
Option "Device" "/dev/input/mice"
#Option "ButtonNumber" "7" # tell x how many buttons it has
Option "Buttons" "10"
Option "ZAxisMapping" "6 7" # thumb buttons
Option "Resolution" "800"
# 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 "Monitor0"
HorizSync 31.5 - 80.5
VertRefresh 20 - 60
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
EndSection
Section "Monitor"
Identifier "Monitor1"
HorizSync 31.5 - 91.1
VertRefresh 60 - 100
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +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
# installed.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
Option "DesktopSetup" "0x00000201"
Option "MonitorLayout" "TMDS, CRT"
Option "IgnoreEDID" "off"
Option "HSync2" "31.5 - 91.1"
Option "VRefresh2" "60 - 100"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000800"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "on"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAScale" "6"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "2"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4e48
Screen 0
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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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 "Server Layout"
# 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.
Screen "Screen0"
# 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 |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Wed Jun 02, 2004 11:10 am Post subject: |
|
|
ok, I currently got xinerama going... works fine, but I have 1 (HUGE) problem:
my second screen is a copy of the first, instead of the 2nd part (it should be)... any ideas how to fix it?
Also, I can get it only to work if both monitors are in the same resolution... is this needed?
I have a ATI Radeon 9800, using the ati-drivers in protage (latest stable) |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 12:28 pm Post subject: |
|
|
hi, I don't really understand what to do with xinerama, as I couldn't find it in portage either, and I don't use it, the only place that I use it is in the USE flag,
I just pick the default ati driver's script setting, it allows me to have that so called "BIG Desktop"  , then without a hitch it just works..
about your second question, I couldn't get both monitors to have different resolutions...  , it really sucks.. cuz I'm worried about my monitors' refresh rates being puched to the limited or some sorts....
cuz apparantly I have one monitor capable of 1280x1024 resol, the other one only capable at 1024x768, but in the driver's flgrxconfig I can only choose 1 screen's resol there I choose 1280x1024; in windows xp, I could set those resol seperately.. but.. with ati's linux driver..  it seems to be a no no..
I'm searching for an answer too. |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 12:32 pm Post subject: |
|
|
and the only way to have different resolution is to pick the "dual monitor" setting in fglrxconfig
but then.. that will be no "Big Desktop" ..
I may be wrong...
Last edited by beastmaster on Wed Jun 02, 2004 12:33 pm; edited 1 time in total |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Wed Jun 02, 2004 12:32 pm Post subject: |
|
|
apparently, to what I've read, xinerama should do what windows does... give a "big desktop", but makes the WM aware that it are 2 screens!.
So the maximizing and stuff works fine.
I don't know about the resolution... It's strange... I also have an expensive monitor that's capable of doing 1920*1440 (I only use 1280*1024) and a cheap one that's bounded to 1024*768@75Hz... |
|
| Back to top |
|
|
nielchiano
Veteran
Joined: 11 Nov 2003
Posts: 1287
Location: 50N 3E
|
| Posted: Wed Jun 02, 2004 12:33 pm Post subject: |
|
|
| beastmaster wrote: | and the only way to have different resolution is to pick the "dual monitor" setting in fglrxconfig
but then.. that will be no "Big Desktop" ..
I may be wrong... |
you'll have a dual monitor, indeed; 1 computer with 2 "X-terminals" on it; but there is no interaction between those 2 screens (Expept for the mouse & keyb) |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 12:37 pm Post subject: |
|
|
Can you provide some more info of how and what you did in "xinerama" ?
see that in my bottom session
| Code: |
Section "ServerLayout"
Identifier "Server Layout"
Screen "Screen0"
|
Do you have something like this or with 2 screens, such as screen0 and screen1 in it? |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 12:39 pm Post subject: |
|
|
| also the XF86config file that I posted earlier works for One Big Deskop setting. generated by flgrxconfig. |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Wed Jun 02, 2004 2:45 pm Post subject: |
|
|
| beastmaster wrote: | um, I got the "Big Desktop" to work with my ati 9800 pro card.
Just one thing puzzles me is that how do I know which monitor is primary or secondary, and which one is set to be on the left or right? There is one session at the fglrxconfig, it's asking | Code: |
horizontal arrangement: monitor connector: 1 => left display
|
,
| Code: | | horizontal arrangement: monitor connector: 1 => right display |
and there is an option for | Code: | | "overlapping screen" [y/n] |
?
, it's very vague here, cuz what exactly does it mean by that, meaning left display as the primary one if I pick that, and vice versa? |
"Monitor connector: 1" in this case is the DVI connector on your card. The VGA connector is #2. The overlapping screen section is not vital, it does just what it says it does. I usually say "no" to this one.
I home last night and played around a bit with Xinerama and did a little reading up on it. Unfortunately, I couldn't find much on the subject, especially in the context of gentoo. I did manage to find this article, which tells me to add to the ServerLayout section in my XF86Config. I gave this a try with the "Big Desktop" config, and just like nielchiano I got a mirror image on the second display. Based on what I've read in the forums about xinerama, the method for getting it to work in gentoo seems to be drastically different from what this article had to say.
Now beastmaster, you say all you did was add xinerama to your USE flags. Was this before or after you emerged your window manager? Same question about your ati-drivers package.
I'm really quite confused at this point. Everything I read on the subject seems to contradict the previous resource. Does anyone out there have a (somewhat) concrete method for getting it to work?
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
YopWongSapn
l33t
Joined: 26 Jan 2004
Posts: 627
|
| Posted: Wed Jun 02, 2004 2:58 pm Post subject: |
|
|
OK, I found a how-to here.
Unfortunately, I'm not at home right now, so I can't try it out. I'd be interested if any of you folks try it to see if it worked for you.
EDIT: So, I tried adding the Xinerama option to my dual head system at work (2 crappy video cards). Works beautifully. I'm wondering if ATI's binary drivers have some sort of Xinerama support? That might explain why I got the mirror images...some sort of conflict with xfree's xinerama, perhaps. I'll keep looking for info....
EDIT 2: According to [ulr=http://www.rage3d.com/content/articles/atilinuxhowto/Linux_ATI.html#SECTION000144000000000000000]this article[/url], the fglrx driver does not support xinerama. Which driver are you using, beastmaster? Before you mentioned that it works for you....are you using the fglrx driver?
EDIT 3: OK, last one (for now). The how-to mentioned in edit 2 has a link to what looks like ATI's "official" XF86Config for the Xinerama option, and it differs from what the author of the how-to said needs to be done. There's a Xinerama option in the ServerFlags section. If anyone wants to give that one a try, I'm interested to see if it works.
_________________
Gentoo...it's like wiping your ass with silk. Or sandpaper. |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 02, 2004 4:21 pm Post subject: |
|
|
Hello YopWongSapn,
I have the ati-drivers verion 3.2.8-r1, I believe it's the latest stable, and also got the ati-drivers-extra as well.
All I did was simple, using the fglrxconfig, letting it configure the "Big Desktop" as in the option, and I got it to work nicely, you can see my complete XF86config from the previous post.
I don't really understand what ximerama is all about though... just thought that why not giving the native ati driver a try first, heck, it works...
it's after I have my windows manager, and yes, I added the xinerama to my USE flag and that's the most by far I have associated with it.
One draw back with this "Big Desktop" setting is that I can't set resolution on each screen individually, the big screen seems to want to uniform one as in the whole, which sounds kind of bad, cuz my other not-so-great monitor can't really handle more than 1024x768, but my other monitor can, my setting is at 1280x1024, thus... don't know how the other monitor will be able to handle it after a while |
|
| 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
