LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Dual Monitor (https://www.linuxquestions.org/questions/linux-hardware-18/dual-monitor-27860/)

jpc82 08-13-2002 05:11 PM

Dual Monitor
 
Well I installed Mandrake and everything went fine except for my dual monitor setup, Both screens were at 800x600 and spanned. The huge problem was though that the left part of the screen was my right monitor and the right part of the screen was my left monitor (not fun at all).

So now I have it configured so that only my Geforce card is working and the Matrox card is ignored.

Now how, if its possible, to set it up like this

Main Monitior: Geforce2MX at 1280x1024 at 32bit color
Secondary Monitor: Matrox at 800x600 at 32 bit color

Thanx for all the help in my last thread, other then this problem the install went fine.

jpc82 08-13-2002 05:11 PM

BTW, I hope to use KDE

finegan 08-16-2002 10:14 AM

I'm assuming Mandrake 8.0 or higher as this will only wirk with XFree86 4.x.x:

You will have to run /usr/X11/bin/XFree86 -configure and let XFree determine the BusID of your cards, also get the horiz and vert refresh rates of your monitors to put in there to replace mine. Remember, you also don't have to run xinerama, which is a spanning desktop where windows can be dragged accross, you can simply have two desktops whish the mouse can move freely between by turning the xinerama option off.

The XF86Config down there is built so that the bigger of the two monitors (I assume), will be hooked up to the GeForce and that it will appear to the left of the other.

Also, you may want to un-comment some of the modules I'm not using, yadyadya... add more font paths...

Cheers,

Finegan
-------------------------------------
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Option "xinerama" "on"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
Load "dbe"
# Load "GLcore"
# Load "pex5"
# Load "xie"
# Load "dri"
Load "extmod"
Load "glx"
Load "record"
Load "xtrap"
Load "speedo"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
EndSection

Section "Monitor"
#DisplaySize 370 270 # mm
Identifier "Biggun"
HorizSync 30.0 - 86.0
VertRefresh 50-160
VendorName "MAG"
ModelName "986FS"
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Littun"
HorizSync 30.0 - 62.0
VertRefresh 50-90
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
Identifier "Matrox"
Driver "????"
VendorName "Matrox"
BoardName "Blah blah"
BusID "XXX:XXX:XX"
EndSection

Section "Device"
Identifier "GeForce"
Driver "???"
VendorName "Who CARES"
BoardName "GeForce 2"
BusID "XXX:XX:XXX"
EndSection

Section "Screen"
Identifier "Screen0"
Device "GeForce"
Monitor "Biggun"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Matrox"
Monitor "Littun"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "800x600"
EndSubSection
EndSection

acid_kewpie 08-16-2002 12:49 PM

i say xinerama sucks, and i have more than twice as many posts as finegan, which means i'm right... :D don't use it, it will probably cripple any video applications you use (my experience.. maybe i was unlucky)

finegan 08-16-2002 01:59 PM

I finally got mplayer to work after I switched to a Xinerama set-up, but chalk that up to quirkiness and possibly that it was also the first time I was trying mplayer out on XFree 4.2.0.

Kewp is the ninja though, even though he hides his actual yearning for some KDE lovin'

Cheers,

Finegan

jpc82 08-16-2002 04:15 PM

Thanx for all the help guys,

I installed Mandrake 8.2, and I really didn't like it at all, I much prefer RedHat. So this weekend I'll be installing RedHat 7.3 and hopefully your sugestions will transfer over fine

Sorry for the late reply, I've been very busy with work and havn't had much time to get online.

jpc82 08-23-2002 08:24 AM

Finegan I tried running XFree86 -configure, and this is what I get

Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
Please report problems to xfree86@xfree86.org.



This is what my current /etc/X11/XF86config looks like

# File generated by anaconda.
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# 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 (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

FontPath "unix/:7100"

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

# NoTrapSignals

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# DontZap

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# DontZoom
EndSection

# Pointer section
# **********************************************************************

Section "Pointer"
Protocol "IMPS/2"
Device "/dev/psaux"

# For wheel support - can not be used with Emulate3Buttons
#
# ZAxisMapping 4 5

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Protocol "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice
# BaudRate 9600
# SampleRate 150

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Emulate3Buttons
Emulate3Timeout 50

# ChordMiddle is an option for some 3-button Logitech mice
# ChordMiddle

EndSection

# **********************************************************************
# Keyboard section
# **********************************************************************

Section "Keyboard"
Protocol "Standard"

AutoRepeat 500 5

# when using XQUEUE, comment out the above line, and uncomment the
# following line
# Protocol "Xqueue"

# Let the server do the NumLock processing. This should only be
# required when using pre-R6 clients
# ServerNumLock

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Xleds 1 2 3

# To set the LeftAlt to Meta, RightAlt key to ModeShift,
# RightCtl key to Compose, and ScrollLock key to ModeLock:

LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control

# To disable the XKEYBOARD extension, uncomment XkbDisable.
# XkbDisable

# 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:
# XkbModel "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# XkbModel "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# XkbLayout "de"
# or:
# XkbLayout "de"
# XkbVariant "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# XkbOptions "ctrl:swapcaps"
#
# If you'd like to disable the capslock key, use:
# XkbOptions "ctrl:nocaps"


XkbRules "xfree86"
XkbModel "pc105"
XkbLayout "us"
#XkbVariant ""
#XkbOptions ""
EndSection

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

# Any number of monitor sections may be present
Section "Monitor"
Identifier "Generic Monitor"
VendorName "Unknown"
ModelName "Unknown"
# HorizSync 31.5
# VertRefresh 60
HorizSync 35.15
VertRefresh 55-65

# ModeLine "640x480" 25.175 640 664 760 800
# 480 491 493 525

# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600" 36 800 824 896 1024
600 601 603 625

EndSection

Section "Monitor"
Identifier "Probed Monitor"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 46.876
VertRefresh 75.121
ModeLine "800x600" 48.002 800 832 928 1024 600 604 608 624 -HSync -VSync
EndSection


Section "Monitor"
Identifier "Dell D2026T"
VendorName "Unknown"
ModelName "Unknown"

# 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.0-96.0

# 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.0-100.0

# Modes can be specified in two formats. A compact one-line format, or
# a multi-line format.

# These two are equivalent

# ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace

# Mode "1024x768i"
# DotClock 45
# HTimings 1024 1048 1208 1264
# VTimings 768 776 784 817
# Flags "Interlace"
# EndMode

# This is a set of standard mode timings. Modes that are out of monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.

# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.

# --320x200--
<<<I CUT THIS STUFF OUT TO MAKE POST SMALLER>>>

# Normal video modes

# -- 512x384
<<<I CUT THIS STUFF OUT TO MAKE POST SMALLER>>>

EndSection

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

Section "Device"
Identifier "Generic VGA Card"
VendorName "Unknown"
BoardName "Unknown"
Chipset "generic"
EndSection


Section "Device"
Identifier "NVIDIA GeForce 2 MX (generic)"
VideoRam 32768
EndSection


# **********************************************************************
# Screen section
# **********************************************************************

# The kernel framebuffer server
Section "Screen"
Driver "fbdev"
Device "Generic VGA Card"
Monitor "Probed Monitor"
Subsection "Display"
# Depth 16
Depth 16
Modes "default"
EndSubsection
EndSection

# The 16-color VGA server
Section "Screen"
Driver "vga16"
Device "Generic VGA Card"
Monitor "Dell D2026T"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection

# The Mono server
Section "Screen"
Driver "vga2"
Device "Generic VGA Card"
Monitor "Dell D2026T"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection


# The svga server
Section "Screen"
Driver "svga"
Device "NVIDIA GeForce 2 MX (generic)"
Monitor "Dell D2026T"
DefaultColorDepth 32

Subsection "Display"
Depth 32
Modes "1280x1024"
ViewPort 0 0
EndSubsection
EndSection

# The accel server
Section "Screen"
Driver "accel"
Device "NVIDIA GeForce 2 MX (generic)"
Monitor "Dell D2026T"
DefaultColorDepth 32

Subsection "Display"
Depth 32
Modes "1280x1024"
ViewPort 0 0
EndSubsection
EndSection

acid_kewpie 08-23-2002 09:00 AM

well.. IS a server already running????

jpc82 08-23-2002 09:12 AM

what server?, I don't know much about XFree86.
I'm in the GUI, is that the problem? If not which server?


If it is that I'm in the GUI, how do I shut it down?

acid_kewpie 08-23-2002 09:18 AM

yes, you can't have X running while trying to configure X.. it'ds not possible. if you login with an X login manager then as root run "init 3" and then exit X your normal way, or just kill X with ctrl+alt+backspace

Can i suggest you try to make better use of the error messages you get when something fails? they're there for a reason. thanks.

jpc82 08-26-2002 08:46 AM

Ok, I closed X and ran that file. It placed a XF86Config.new file in my root directory. So I looked at it and my XF86Config-4 in myX11 dir, and the one finegan posted and made what I thought was a good confige file, well it wasn't.

I renamed my old XF86Config-4 file to XF86Config-4.old and put the new one in its place, and rebooted. The system booted fine, but instead of getting the KDE login screen all I have is thedefualt screen that you get with init 3 on my main monitor blinking on and off.


This is my new XF86Config-4


Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
Load "glx"
Load "dbe"
# Load "dri"
Load "fbdevhw"
Load "freetype"
Load "extmod"
Load "record"
Load "xtrap"
Load "speedo"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31.0-96.0
VertRefresh 50.0-100.0
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 46.876
VertRefresh 75.121
EndSection

Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "NVidia"
BoardName "GeForce2 MX/MX 400"
BusID "PCI:1:0:0"
EndSection

Section "Device"

Identifier "Card1"
Driver "mga"
VendorName "Matrox"
BoardName "MGA 2064W"
BusID "PCI:0:13:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection

EndSection

Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Depth 24
Modes "800x600"
EndSubSection

EndSection

finegan 08-26-2002 11:46 AM

This looks fine, aside from the ranges on this strike me as a little odd...

Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 46.876
VertRefresh 75.121
EndSection

Sure it isn't 75-121 and 46-76? With the monitor its only getting to try exactly one range combination.

Cheers,

Finegan

jpc82 08-26-2002 11:58 AM

I figured out the problem, it was with the color depths. Once I changed that they work.

As for the rates that I put in, thats exactly what was in XF86Config.new, which is my new problem. I want it to run at 72 Vertical, but it will only run at 75 right now. Is there a way to probe the monitor to find out what rates I can put in there?

finegan 08-26-2002 12:14 PM

Well, you can check /var/log/XFReesomethingorother to see the modes it tried before settling on one, but really its best to just look up the specs of what your monitor is capable of.

Cheers,

Finegan

jpc82 08-26-2002 12:23 PM

I got this monitor used and free, so I won't be able to find out that info. I guess I'lljust have to live with it this way.

It seems so far that the problems I get in Windows when I have it at 75 or higher does not happen in linux, so it should be ok


All times are GMT -5. The time now is 10:24 PM.