LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 03-15-2007, 08:45 PM   #1
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Rep: Reputation: 31
Trying to set up dual displays, and failing miserably.


I have two 17" monitors which I want to use together on my computer. I have done a lot of searching over the past week and haven't found any solutions yet, so here I am. One thing I have tried is
Code:
X -configure
Which told me it had configured a multihead system and told me to test it, which I did. The result, the monitor switched on and was full of crappy colours, then nothing, my computer froze. I tried xorgconfig, which I think only does one display, and also xorgcfg, with xorgcfg I could move my mouse into the other display but it was a big white square and eventually the system froze again.
I remembered that my brother and I once set up a Windows machine to use a massive widescreen TV with a monitor and it was easy, so I installed Windows and tried it on there, it worked straight away. Which makes me even more determined to make it work on Linux too.

Hardware:
SiS 6326 PCI on 01.0a.0
Intel 82810 onboard on 00.01.0

Distro:
Slackware 11

Thanks,

John
 
Old 03-15-2007, 09:21 PM   #2
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
I think it's still easier at this point to take your existing (presumably working) xorg.conf and edit it by hand. I've read a few articles/posts recently that have me thinking this stuff will be as easy as windows really soon though(thanks to recent x.org releases).

You need to add a second Monitor section, a second Device section, and a second Screen section. And then specify 2 screens in the ServerLayout. this PDF seems to explain all the details. I would only suggest that you use common Identifiers for all the various sections attributed to a single monitor. Meaning the screen, monitor and device sections that setup your first monitor will all be called CRT1, and all those sections setting up your second should all be called CRT2 (or really whatever you want to call them, LEFT_MONITOR, RIGHT_MONITOR or something if you want), this way it is so much easier to tie them all together and see which sections are for which monitor. Hope that makes sense after all the rambling. Post your xorg.conf and I'll try to help more.

Last edited by lurko; 03-15-2007 at 09:23 PM.
 
Old 03-15-2007, 10:10 PM   #3
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
I am actually in the process of editing the xorg.conf by hand right now. Which one do you want me to post? the modified one? I am in Windows right now, just having a look if anyone had repied, but now I am going to reboot, then I will post what I have so far.
 
Old 03-15-2007, 10:18 PM   #4
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
Here is my modified 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/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    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/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"

# 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 <Ctrl><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 <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><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"    "pc105"
# 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"    "pc105"
#    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"    "Auto"	# Auto detect
    Option "Device"      "/dev/mouse"

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

#    Option "Protocol"	"Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"	"9600"
#    Option "SampleRate"	"150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button 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  "Monitor 0"

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

#    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

EndSection

Section "Monitor"
	Identifier "Monitor 1"
	HorizSync 30-72
	VertRefresh 50-160
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"onboard"
    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     "i810"
# 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:01:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "SiS"
    Driver      "sis"
    BusID	"PCI:01:10:0
    #VideoRam    8192
    # Option "no_accel" # Use this if acceleration is causing problems
    # Option "fifo_moderate" 
    # Option "fifo_conserv" 
    # Option "fifo_aggressive" 
    # Option "fast_vram"
    # Option "pci_burst_on"
    # Option "xaa_benchmark" # DON'T use with "ext_eng_queue" !!!
    # Option "ext_eng_queue" # Turbo-queue. This can cause drawing 
                             # errors, but gives some accel
    # 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  "Screen 0"
    Device      "SiS"
    Monitor     "Monitor 0"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
	Identifier "Screen 1"
	Device "onboard"
	Monitor "Monitor 1"
	DefaultDepth 24
	Subsection "Display"
		Depth 8
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	SubSection "Display"
		Depth 16
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	Subsection "Display"
		Depth 24
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		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  "Simple 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.  In this example, screen 2 is located to the
# right of screen 1.

    Screen 0 "Screen 0" 0 0
    Screen 1 "Screen 1" RightOf "Screen 0"
# 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
After pasting that, I just tried to do :wq for some reason.
 
Old 03-15-2007, 11:57 PM   #5
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
looks good except that you're missing the Screen options in the Device sections.

Code:
Section "Device"
    Identifier  "SiS"
    Driver      "sis"
    BusID	"PCI:01:10:0
    Screen      0
EndSection

Section "Device"
    Identifier	"onboard"
    Driver     "i810"
    BusID      "PCI:0:01:0"
    Screen     1
EndSection
a better way to (now) explain what I was rambling about before would be to suggest that you change the Identifiers(and their references) "Screen 0" and "Monitor 0" to "SiS", and the Identifiers "Screen 1" and "Monitor 1" to "onboard". Anyway, that's not necessary to get dual screens working, it just makes it easier to see at a glance that your config is OK. The screen sections also become a kind of sign that your all set:
Code:
Section "Screen"
	Identifier "onboard"
	Device "onboard"
	Monitor "onboard"
...
 
Old 03-16-2007, 12:43 AM   #6
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
I did change the identifiers, as I realize it makes things easier. I have added the screen part to the Device sections and am going to try it now.
 
Old 03-16-2007, 01:02 AM   #7
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
Screen 1 was deleted because of no matching config session. That was the error message I got. I do not know what this means, I'm going to go and look and see if I changed anything else (or forgot to change something).

EDIT: Sorry that error message should read
Code:
Screen 1 deleted because of no matching config section.

Last edited by johngreenwood; 03-16-2007 at 01:18 AM.
 
Old 03-16-2007, 01:27 AM   #8
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
double-check the Identifiers (and when they're referenced in other sections) maybe? If you want to post what you've got now I'll take another look. Definitely sounds like a typo somewhere or the like.

Last edited by lurko; 03-16-2007 at 01:28 AM.
 
Old 03-16-2007, 02:00 AM   #9
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
Ok, here are the Monitor, Screen, Device, and ServerLayout sections. If you need more I'll post that too, thanks.
Code:
# **********************************************************************
# Monitor section
# **********************************************************************

Section "Monitor"
    Identifier  "Monitor 0"
    HorizSync   30-72
    VertRefresh 50-160
EndSection

Section "Monitor"
	Identifier "Monitor 1"
	HorizSync 30-72
	VertRefresh 50-160
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************

Section "Device"
    Identifier	"Card 1"
    VendorName	"Intel"
    BoardName	"Unknown"
    Screen 	1
#    Chipset	"generic"
    Driver     "i810"
    BusID      "PCI:0:01:0"
#    VideoRam	256
#    Clocks	25.2 28.3
EndSection

Section "Device"
    Identifier  "Card 0"
    Driver      "sis"
    BusID	"PCI:01:10:0"
    Screen 	0
    #VideoRam    8192
    # Option "no_accel" # Use this if acceleration is causing problems
    # Option "fifo_moderate" 
    # Option "fifo_conserv" 
    # Option "fifo_aggressive" 
    # Option "fast_vram"
    # Option "pci_burst_on"
    # Option "xaa_benchmark" # DON'T use with "ext_eng_queue" !!!
    # Option "ext_eng_queue" # Turbo-queue. This can cause drawing 
                             # errors, but gives some accel
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

Section "Screen"
    Identifier  "Screen 0"
    Device      "Card 0"
    Monitor     "Monitor 0"
    DefaultDepth 24
    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
	Identifier "Screen 1"
	Device "Card 1"
	Monitor "Monitor 1"
	DefaultDepth 24
	Subsection "Display"
		Depth 8
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	SubSection "Display"
		Depth 16
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	Subsection "Display"
		Depth 24
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************
Section "ServerLayout"

    Identifier  "Simple Layout"

    Screen 0 "Screen 0" 0 0
    Screen 1 "Screen 1" RightOf "Screen 0"
    #Option "Xinerama"

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection
 
Old 03-16-2007, 03:15 AM   #10
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
it seems I was mistaken about needing the Screen options in the device sections, the manpage says that's only mandatory with 2 heads on the same card. Sorry

I can't seem to find anything wrong with your setup, I tidied what you posted and did what I've been suggesting with the identifiers, try this I guess, it looks good to me:
Code:
# **********************************************************************
# Monitor section
# **********************************************************************

Section "Monitor"
    Identifier  "sis"
    HorizSync   30-72
    VertRefresh 50-160
EndSection

Section "Monitor"
	Identifier  "intel"
	HorizSync   30-72
	VertRefresh 50-160
EndSection

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

Section "Device"
    Identifier  "sis"
    Driver      "sis"
    BusID	"PCI:01:10:0"
#    Screen 	0
EndSection

Section "Device"
    Identifier	"intel"
    Driver      "i810"
    BusID       "PCI:0:01:0"
#    Screen      1
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

Section "Screen"
    Identifier  "sis"
    Device      "sis"
    Monitor     "sis"
    DefaultDepth 24
    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
	Identifier "intel"
	Device     "intel"
	Monitor    "intel"
	DefaultDepth 24
	Subsection "Display"
		Depth 8
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	SubSection "Display"
		Depth 16
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
	Subsection "Display"
		Depth 24
		Modes "1280x1024" "1024x768" "800x600" "640x480"
		Viewport 0 0
	EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************
Section "ServerLayout"
    Identifier  "Simple Layout"
    Screen 0    "sis" 0 0
    Screen 1    "intel" RightOf "sis"
    #Option "Xinerama"
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
EndSection
I'm sorry but I'm at a loss here, I don't think I'm overlooking some typo or mis-configuration, I hope someone will mention if I am
 
Old 03-16-2007, 03:31 AM   #11
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
I have done as you suggested, it still doesn't work. But I would like to thank you for reading through my boring xorg.conf and trying to find a solution. I appreciate it very much.
Back to the logs I think.
 
Old 03-16-2007, 03:37 AM   #12
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
what about the BusID's? does 01.0a.0 translate to 01:10:0 (for the SiS device)? If the drivers are correct, BusID is only thing in those sections I would think that could be the culprit (but I am no expert by any means). at least it's the only thing in those sections that can't be checked by reading xorg.conf for spec-compliance.

np by the way.

Last edited by lurko; 03-16-2007 at 03:39 AM.
 
Old 03-16-2007, 05:04 AM   #13
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
Yes, the bus ID is correct, when I was setting up Kubuntu a while back I had a problem putting 01:0a:0 as an identifier, also I did a
Code:
X -scanpci
and it says the same.

I have been looking through the xorg logs and I noticed something like:
[II]Screen 0 shares mem and io resources
[II]Screen 1 shares mem and io resources

I don't think it was an error though, right now I am using both monitors. KDE recognises there are two screens, my primary one is working fine, but my secondary is only 640x480 and just has lines on it, I can move a window onto the second screen, but can't see it. I have to drag it back with the Desktop pager thing or use move in the right click menu on it's taskbar entry. One thing I have done is change my primary card to the onboard one, it seems that once it has started, it won't stop. I mean that after trying to startx or something, I could not return to my VT, only do a CTRL+ALT+DEL for a reboot. I am going to try lowering the resolution of both monitors, removing the lower ones, and also lower the colour depth and see if that works.

Last edited by johngreenwood; 03-16-2007 at 05:07 AM.
 
Old 03-16-2007, 05:32 AM   #14
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
I don't know what this means, but I have just found that my onboard card and my sound card share IRQ9. I have a setting for this in BIOS but when I change it, they both change together. Now I am going to find out what an IRQ is.
 
Old 03-17-2007, 11:44 PM   #15
johngreenwood
Member
 
Registered: Nov 2006
Location: Lancashire, United Kingdom
Distribution: Slackware 13
Posts: 243

Original Poster
Rep: Reputation: 31
Finally done it!

After many hours trying to get it to work, I decided to look in the big box of computer crap in the cellar to see if I could find another graphics card. I managed to find an old Matrox Mystique, and with all the optimism in the world, stuck in my computer. After three frustrating hours, using everything you have told me in this thread, I finally managed to get it working. then I tried 'xinerama' and it worked too. You have no idea how happy I am, I can now re-remove that waste of space called Windows from my hard drive and install something more worthwhile. Thank you very much lurko, you have made me very happy indeed.

Cheers,

John
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Using dual monitors/dual heads displays a black screen (Fedora 6) ttnunam Linux - General 4 04-21-2007 01:50 AM
Help with Dual Displays Leveecius Linux - Hardware 1 06-21-2006 04:57 PM
noob trying to install sound drivers ... failing miserably lowpingnoob Linux - Software 36 06-12-2005 06:23 PM
Dual Displays p0rt Linux - General 2 06-25-2003 02:36 PM
RHL 9.0 install failing miserably Spytap Linux - Newbie 7 05-26-2003 06:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 03:19 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration