Penguin
Diff: HowToXineramaHOWTO
EditPageHistoryDiffInfoLikePages

Differences between current version and predecessor to the previous major change of HowToXineramaHOWTO.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 5 Last edited on Tuesday, April 20, 2004 2:41:54 am by ThomasLindroth
Older page: version 1 Last edited on Friday, June 7, 2002 1:07:53 am by perry Revert
@@ -1,14 +1,11 @@
-  
-  
-  
- Using the Xinerama Extensions to MultiHead XFree86 V. 4.+ 
+Using the Xinerama Extensions to ! MultiHead XFree86 V. 4.+ 
  
  
  
 ---- 
  
-!!!Using the Xinerama Extensions to MultiHead XFree86 V. 4.+ 
+!!!Using the Xinerama Extensions to ! MultiHead XFree86 V. 4.+ 
  
 !!Dennis Baker drbaker@softhome.netv2.0 Revised November 2, 2000 
  
  
@@ -59,9 +56,9 @@
 ****5.1 Adding all of your video cards 
  
 ****5.2 Identifying Your Video Cards 
  
-****5.3 Configuring the ServerLayout Section 
+****5.3 Configuring the ! ServerLayout Section 
  
  
  
  
@@ -94,9 +91,9 @@
  
 !!10. Credits 
 ---- 
  
-!!1. IntroductionMany changes made based input from Nico Schottelius nicos@pcsystems.de 
+!!1. ! IntroductionMany changes made based input from Nico Schottelius nicos@pcsystems.de 
  
 !!1.1 What is Xinerama? 
  
  
@@ -345,9 +342,9 @@
 This is a good time to put all of your video cards into your system and set up your monitors. Set everything up the way you want it when you are done, as you will have to repeat steps later if you change things. 
  
  
  This next step needs to be done from the console with-out X running. If you are in X, exit now. If your system uses a display manager such as xdm or gdm exit you need to stop that service. 
-If you need to stop a display manager from RedHat the easiest way is like this: 
+If you need to stop a display manager from ! RedHat the easiest way is like this: 
  
  
  
  
@@ -405,9 +402,27 @@
  
  
 PCI cards and devices are identified with a leading 0, AGP cards with a 1. In my case I have a Matrox Millenium II (0:12:0) and a Diamond FireGL(1:0:0). Find your video cards and write down the numbers associated with them. It is important that you know which number goes with which card. 
  
+!Alternate Method to Scanning the PCI Bus  
  
+You can also find these numbers without having to shut your X server down as long as you have /proc enabled. Simply look at the contents of /proc/pci which will have the appropriate information. The three numbers you are looking for are the Bus, Device, and Function. For example, The last few lines of my /proc/pci read:  
+  
+----  
+ Bus 0, device 9, function 0:  
+ VGA compatible controller: S3 Inc. 86c764/765 Trio32/64/64V+ (rev 68).  
+ IRQ 11.  
+ Non-prefetchable 32 bit memory at 0xe8000000 0xebffffff.  
+ Bus 1, device 5, function 0:  
+ VGA compatible controller: nVidia Corporation NV10 Geforce 256 SDR (rev 16  
+).  
+ IRQ 11.  
+ Master Capable. Latency=64. Min Gnt=5.Max Lat=1.  
+ Non-prefetchable 32 bit memory at 0xe6000000 0xe6ffffff.  
+ Prefetchable 32 bit memory at 0xc8000000 0xcfffffff.  
+----  
+  
+As you can see, my S3 card is on Bus 0, device 9 and function 0 which would correspond to (0:9:0) from a XFree86 -scanpci output. My Geforce card would be listed as (1:5:0)  
  
 ---- 
  
 !!5. Editing your XConfig File 
@@ -460,9 +475,9 @@
 Section "Device" 
 Identifier "FireGL" 
 Driver "glint" 
 BusID "PCI:1:0:0" 
-EndSection 
+! EndSection 
  
 ---- 
  
  
@@ -471,13 +486,13 @@
  
  
  
  
-!!5.3 Configuring the ServerLayout Section 
+!!5.3 Configuring the ! ServerLayout Section 
  
  
  
-Now you need to edit the ServerLayout Section at the end of the XF86Config File. The ServerLayour Section is exactally that, it tells you what Screens to use, how to lay them out logically, and what input devices to assign to them. Your current layout is for one screen, keyboard, and mouse. For each Screen section you have created about you need reference in this section for them to appear in your display. 
+Now you need to edit the ! ServerLayout Section at the end of the XF86Config File. The ! ServerLayour Section is exactally that, it tells you what Screens to use, how to lay them out logically, and what input devices to assign to them. Your current layout is for one screen, keyboard, and mouse. For each Screen section you have created about you need reference in this section for them to appear in your display. 
  
  
  
  
@@ -488,19 +503,19 @@
  
  
 Screen "Screen 2" Relationship "Screen 1" 
  
-This defines the relationship between the "Screen 2" and "Screen 1". Valid Relationships include: RightOf, Below, Above, LeftOf, Absolute X Y, Relative. Use of the first four relationships is pretty obvious as illustrated in my sample: 
+This defines the relationship between the "Screen 2" and "Screen 1". Valid Relationships include: ! RightOf, Below, Above, ! LeftOf, Absolute X Y, Relative. Use of the first four relationships is pretty obvious as illustrated in my sample: 
  
 ---- 
  
-Section "ServerLayout" 
+Section "! ServerLayout" 
 Identifier "Simple Layout" 
 Screen "Screen 2" 
-Screen "Screen 1" RightOf "Screen 2"  
-InputDevice "Mouse1" "CorePointer"  
-InputDevice "Keyboard1" "CoreKeyboard"  
-EndSection 
+Screen "Screen 1" ! RightOf "Screen 2"  
+! InputDevice "Mouse1" "! CorePointer"  
+! InputDevice "Keyboard1" "! CoreKeyboard"  
+! EndSection 
  
 ---- 
  
  
@@ -593,8 +608,10 @@
 ie. 
 :0 local /usr/X11R6/bin/X +xinerama 
 It appears that KDM uses standard XFree xdm files, so this should work if you 
 use xdm as well 
+  
+If you use kde3.2 edit /usr/kde/3.2/share/config/kdm/Xservers as above.  
  
 ---- 
  
  
@@ -622,9 +639,9 @@
  
  
  
  
-I searched the mailing lists, FAQs, and emailed the developers of most of the major window managers to see if they were working on any Xinerama related extensions. The Window Managers/ Desktop environments I reviewed included Blackbox, Enlightenment, KDE, WindowMaker, and XFCE. Enlightenment and Sawfish were the only two which I found significant enhancements for Xinerama. I have detailed what I discovered below. 
+I searched the mailing lists, FAQs, and emailed the developers of most of the major window managers to see if they were working on any Xinerama related extensions. The Window Managers/ Desktop environments I reviewed included Blackbox, Enlightenment, KDE, ! WindowMaker, and XFCE. Enlightenment and Sawfish were the only two which I found significant enhancements for Xinerama. I have detailed what I discovered below. 
  
 !!8.1 Enlightenment 
  
  
@@ -663,129 +680,129 @@
 ---- 
  
 Section "Module" 
 Load "dbe" # Double buffer extension 
-SubSection "extmod" 
+! SubSection "extmod" 
 Option "omit xfree86-dga" # don't initialise the DGA extension 
-EndSubSection 
+! EndSubSection 
 Load "type1" 
 Load "freetype" 
 # This loads the GLX module 
 # Load "glx" 
-EndSection 
+! EndSection 
 Section "Files" 
-RgbPath "/usr/X11R6/lib/X11/rgb"  
-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/" 
+! RgbPath "/usr/X11R6/lib/X11/rgb"  
+! 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  
-Section "ServerFlags"  
-EndSection  
-Section "InputDevice" 
+# ! ModulePath "/usr/X11R6/lib/modules"  
+! EndSection  
+Section "! ServerFlags"  
+! EndSection  
+Section "! InputDevice" 
 Identifier "Keyboard1" 
 Driver "Keyboard" 
-Option "AutoRepeat" "500 30"  
-Option "XkbRules" "xfree86"  
-Option "XkbModel" "pc101"  
-Option "XkbLayout" "us"  
-EndSection  
-Section "InputDevice" 
+Option "! AutoRepeat" "500 30"  
+Option "! XkbRules" "xfree86"  
+Option "! XkbModel" "pc101"  
+Option "! XkbLayout" "us"  
+! EndSection  
+Section "! InputDevice" 
 Identifier "Mouse1" 
 Driver "mouse" 
 Option "Protocol" "PS/2" 
 Option "Device" "/dev/psaux" 
-EndSection 
+! EndSection 
 Section "Monitor" 
 Identifier "Mini" 
-HorizSync 31.5  
-VertRefresh 50-90  
-EndSection 
+! HorizSync 31.5  
+! VertRefresh 50-90  
+! EndSection 
 Section "Monitor" 
 Identifier "Impression" 
-HorizSync 31.5 - 82.  
-VertRefresh 50-100  
-EndSection 
+! HorizSync 31.5 - 82.  
+! VertRefresh 50-100  
+! EndSection 
 # Video Card #1, Matrox Millenium II PCI Video Card 
 Section "Device" 
 Identifier "Matrox" 
 Driver "mga" 
-VideoRam 8192 
+! VideoRam 8192 
 BusID "PCI:0:12:0" 
-EndSection 
+! EndSection 
 # Video Card # 2, Fire GL 1000 AGP video card. 
 Section "Device" 
 Identifier "FireGL" 
 Driver "glint" 
-#VideoRam 8192 
+#! VideoRam 8192 
 BusID "PCI:1:0:0" 
-EndSection 
+! EndSection 
 Section "Screen" 
 Identifier "Screen 2" 
 Device "FireGL" 
 Monitor "Impression" 
-DefaultDepth 16 
+! DefaultDepth 16 
 Subsection "Display" 
 Depth 16 
 Modes "1280x1024" "640x480" 
-ViewPort 0  
-EndSubsection  
-EndSection 
+! ViewPort 0  
+! EndSubsection  
+! EndSection 
 # My Miniature monitor, notice that I used the virtual option so it is 
 # the same heighth as the larger monitor, this is not necessary. 
 Section "Screen" 
 Identifier "Screen 1" 
 Device "Matrox" 
 Monitor "Mini" 
-DefaultDepth 16 
+! DefaultDepth 16 
 Subsection "Display" 
 Depth 16 
 Modes "640x480" 
-ViewPort 0  
+! ViewPort 0  
 Virtual 640 1024 
-EndSubsection  
-EndSection  
-Section "ServerLayout" 
+! EndSubsection  
+! EndSection  
+Section "! ServerLayout" 
 Identifier "Simple Layout" 
 Screen "Screen 2" 
 Screen "Screen 1" Rightof "Screen 2" 
-InputDevice "Mouse1" "CorePointer"  
-InputDevice "Keyboard1" "CoreKeyboard"  
-EndSection 
+! InputDevice "Mouse1" "! CorePointer"  
+! InputDevice "Keyboard1" "! CoreKeyboard"  
+! EndSection 
  
 ---- 
  
  
-An alternate ServerLayout Section with one Monitor above the other. 
+An alternate ! ServerLayout Section with one Monitor above the other. 
 ---- 
  
-Section "ServerLayout" 
+Section "! ServerLayout" 
 Identifier "Simple Layout" 
 Screen "Screen 2" 
 Screen "Screen 1" Below "Screen 2" 
-InputDevice "Mouse1" "CorePointer"  
-InputDevice "Keyboard1" "CoreKeyboard"  
-EndSection 
+! InputDevice "Mouse1" "! CorePointer"  
+! InputDevice "Keyboard1" "! CoreKeyboard"  
+! EndSection 
  
 ---- 
  
  
 Screens can overlap too. In this configuration I make the two monitors overlap by 80 pixels.. 
 ---- 
  
-Section "ServerLayout" 
+Section "! ServerLayout" 
 Identifier "Simple Layout" 
 Screen "Screen 2" 
 Screen "Screen 1" Relative "Screen 2" 1200 0 
-InputDevice "Mouse1" "CorePointer"  
-InputDevice "Keyboard1" "CoreKeyboard"  
-EndSection 
+! InputDevice "Mouse1" "! CorePointer"  
+! InputDevice "Keyboard1" "! CoreKeyboard"  
+! EndSection 
  
 ---- 
 ---- 
  
The following authors of this page have not agreed to the WlugWikiLicense. As such copyright to all content on this page is retained by the original authors.
  • perry
  • EddieDean
  • ThomasLindroth
The following authors of this page have agreed to the WlugWikiLicense.

    PHP Warning

    lib/blame.php (In template 'html'):177: Warning: Invalid argument supplied for foreach()

    lib/plugin/WlugLicense.php (In template 'html'):99: Warning: Invalid argument supplied for foreach()

    lib/plugin/WlugLicense.php (In template 'html'):111: Warning: in_array() [<a href='function.in-array'>function.in-array</a>]: Wrong datatype for second argument