Article View: alt.pl.comp.os.linux.debian
Article #29686Re: debian na dwa monitory
From: pawell32
Date: Mon, 23 Feb 2009 06:13
Date: Mon, 23 Feb 2009 06:13
238 lines
8569 bytes
8569 bytes
wywal_dodaj_krokpe pisze: > pawell32 pisze: >> Witam. >> >> Może i ten temat już był, lecz nie trafiłem dokładnie na to co >> potrzebuje. Otóż przechodzę na Debiana, zaistalowałem 4.0 r6 64, >> KDE 3.5.5, karta graficzna GF7300, i potrzebuje uruchomić obsługę dwóch >> monitorów. W chwili obecnej obydwa monitory wyświetlają to samo, ale >> potrzebuje większej przestrzenie roboczej. >> >> Pozdrwaiam > Musisz sobie skonfigurowac odpowiednio xorg.conf, ja swego czasu na > Debianie to robilem, niestety nie posiadam juz konfiga xorga z niego. > > Na moim gentoo dzialam na dwoch monitorach, ale na kazdym z nich jest > uruchomiona i sesja X-ów. Zapodaje konfiga, przerob sobie go dla > wlasnych potrzeb. > > > # nvidia-xconfig: X configuration file generated by nvidia-xconfig > # nvidia-xconfig: version 1.0 (buildmeister@builder58) Wed Oct 1 > 15:12:53 PDT 2008 > > > Section "Module" > Load "dbe" > Load "extmod" > Load "type1" > Load "freetype" > Load "glx" > EndSection > > Section "InputDevice" > # generated from data in "/etc/conf.d/gpm" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" > Option "Device" "/dev/input/mice" > Option "Emulate3Buttons" "no" > Option "ZAxisMapping" "4 5" > EndSection > > Section "InputDevice" > # generated from default > Identifier "Keyboard0" > Driver "kbd" > EndSection > > # Monitor section for CRT2 (master head > # > Section "Monitor" > > Identifier "CRT2" > VendorName "Monitor Vendor" > ModelName "My CRT2 device" > > # VertRefresh & HorizSync: > # # This decribes CTZ2; if CRT2 is LCD or TV, the driver will ignore the > # # values given here. You only need to set these if you use CRT2 as > secondary > # # (analog) VGA and your monitor does not support DDC2. > # > # > > # VertRefresh 60-75 > # HorizSync 30-90 > EndSection > > # Monitor section for CRT1 (slave head) > # > Section "Monitor" > Identifier "CRT1" > VendorName "Monitor Vendor" > ModelName "My VGA monitor" > > > # These values are actually used to determine the resolution/refresh rates > # # to be used on CRT1! If your monitor supported DDC2, you can leave these > # # out. > # > VertRefresh 60-75 > HorizSync 30-90 > Option "DPMS" > EndSection > > # ---------------------------------------------------------- > # # DEVICE sections > # # ---------------------------------------------------------- > # # This section contains configuration data of the video card. > # > # # Device section for CRT2 (master head) -------------------- > # > Section "Device" > > Identifier "SiS chip-1" > VendorName "SiS" # Value does not matter > BoardName "SiS" # value does not matter > > Driver "sis" > Option "EnableSiSCtrl" "yes" > #Option "ForceCRT2Type" "TV" > # > ## Since this is the driver section for CRT2, options for > adjusting the TV > ## image (such as TVStandard, CHTVOverscan, etc) should be > placed in this > ## section (and not the Device section for CRT1 below) > # > ## Generally: Set as many options as possible in this device > section, > ## not the one for CRT1. CRT2 is initialized first (thus the term > # "master head") and its settings rule in many cases over the one > # # given in the slave device's (CRT1) section. The only exceptions for > # # this rule are all gamma correction and Xv related options, see below. > # > # # For dual head mode, BusID has to be specified! Check this using lspci! > # > BusID "PCI:1:00:0" > # "Screen" selects the screen number for this device in dual head mode > # # Screen 0 is master (always CRT2) > # > # > Screen 0 > > EndSection > > # Device section for CRT1 (Slave head) -------------------- > # > Section "Device" > Identifier "SiS chip-2" > > Driver "sis" > > # For dual head mode, BusID must be specified! > # > BusID "PCI:1:00:0" > > # Generally: Set all the options you need in the master > # # section, not here. See above. The only exeptions to this > # # rule are all Xv and gamma correction related options, such as > # #Option "CRT1Gamma" "false" > # #Option "StoredGammaBrightness" "1.1 1.1 1.1" > # #Option "StoredGammaPreBrightness" "1.2 1.2 1.2" > # #Option "XvGamma" "1.0 1.2 0.8" > # #Option "XvDefault..." > # > # # "Screen" selects the screen > number for this device in dual head mode > # # Screen 1 is slave (always > CRT1 = external VGA) > > Screen 1 > Option "EnableSiSCtrl" "yes" > EndSection > > > # ---------------------------------------------------------- > # # SCREEN section(s) > # # ---------------------------------------------------------- > # # This section defines the available resulutions and depths. > # > # # Screen section for CRT2 (LCD/Plasma/DVI-D, TV, VGA2/DVI-A) > # > > Section "Screen" > Identifier "Screen1" > Device "SiS chip-1" > Monitor "CRT2" > DefaultDepth 24 > Option "AddARGBVisuals" "True" > Option "AllowGLXWithComposite" "True" > Option "RenderAccel" "True" > Option "AddARGBGLXVisuals" "True" > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > # Screen section for CRT1 (VGA) > # > # # DefaultDepth must be identical to master screen if using Xinerama. > # # Otherwise, depths can be different. > # # A depth of 8 is not supported in dual head mode. > # # Resolutions can be different. > # > Section "Screen" > Identifier "Screen2" > Device "SiS chip-2" > Monitor "CRT1" > DefaultDepth 24 > Option "AddARGBVisuals" "True" > Option "AllowGLXWithComposite" "True" > Option "RenderAccel" "True" > Option "AddARGBGLXVisuals" "True" > > > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > > Section "ServerLayout" > Identifier "Default Layout" > > # Now enable dual head mode: > # > Screen "Screen1" > Screen "Screen2" LeftOf "Screen1" > > # This enables Xinerama. If you don't set this to "on", startx will spawn > # # two indepentent X sessions. In Xinerama mode, both screens are virtually > # # one screen and only one X session is started. > # Option "Xinerama" "on" > > InputDevice "Keyboard0" > InputDevice "Mouse0" > # InputDevice "USB Mouse" > EndSection > > # Section "DRI" > # Mode 0666 > # EndSection > > > Section "Extensions" > Option "Composite" "Enable" > EndSection > > dzięki, przyjacielu - działa pawell
Technical Details
Message-ID:
<49a23e83$1@news.home.net.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!nf1.ipartners.pl!ipartners.pl!news.home.net.pl!not-for-mailReferences:
<49644fe5@news.home.net.pl> <gnp1o9$rvs$1@julia.coi.pw.edu.pl>Show Full Headers
Complete Article Headers
Date: Mon, 23 Feb 2009 07:13:14 +0100 From: pawell32 <pahat@wp.pl> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 Newsgroups: alt.pl.comp.os.linux.debian Subject: Re: debian na dwa monitory References: <49644fe5@news.home.net.pl> <gnp1o9$rvs$1@julia.coi.pw.edu.pl> In-Reply-To: <gnp1o9$rvs$1@julia.coi.pw.edu.pl> NNTP-Posting-Host: 94.40.65.240 Message-ID: <49a23e83$1@news.home.net.pl> X-Trace: news.home.net.pl 1235369603 94.40.65.240 (23 Feb 2009 07:13:23 +0100) Organization: home.pl news server Lines: 238 X-Authenticated-User: pawel.hatala@im.pl Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!nf1.ipartners.pl!ipartners.pl!news.home.net.pl!not-for-mail Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit