Attachment 2235 Details for Bug 2845 – xorg config file

xorg config file

xorg.conf (text/plain), 3.48 KB, created by Michel MENGIS on 2005-03-29 01:56:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michel MENGIS

Created: 2005-03-29 01:56:36 UTC

Size: 3.48 KB

patch

obsolete

># Xorg configuration created by system-config-display
>
>Section "ServerLayout"
>	Identifier     "single head configuration"
>	Screen      0  "Screen0" 0 0
>	InputDevice    "Mouse0" "CorePointer"
>	InputDevice    "Keyboard0" "CoreKeyboard"
>EndSection
>
>Section "Files"
>
># RgbPath is 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.
># 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.
>	RgbPath      "/usr/X11R6/lib/X11/rgb"
>	FontPath     "unix/:7100"
>EndSection
>
>Section "Module"
>	Load  "dbe"
>	Load  "extmod"
>	Load  "fbdevhw"
>	Load  "glx"
>	Load  "record"
>	Load  "freetype"
>	Load  "type1"
>	Load  "dri"
>EndSection
>
>Section "InputDevice"
>
># Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
>#	Option	"Xleds"		"1 2 3"
># To disable the XKEYBOARD extension, uncomment XkbDisable.
>#	Option	"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:
>#	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"
># Or if you just want both to be control, use:
>#	Option	"XkbOptions"	"ctrl:nocaps"
>#
>	Identifier  "Keyboard0"
>	Driver      "kbd"
>	Option	    "XkbModel" "pc105"
>	Option	    "XkbLayout" "fr_CH"
>EndSection
>
>Section "InputDevice"
>	Identifier  "Mouse0"
>	Driver      "mouse"
>	Option	    "Protocol" "IMPS/2"
>	Option	    "Device" "/dev/input/mice"
>	Option	    "ZAxisMapping" "4 5"
>	Option	    "Emulate3Buttons" "yes"
>EndSection
>
>Section "Monitor"
>        # Block type: 2:0 3:fe
>        # Block type: 2:0 3:fe
>        Identifier "SEC:5034"
>        VendorName "SEC"
>        ModelName "DELL Latitude D610 Flat panel"
>        # Block type: 2:0 3:fe
>        # Block type: 2:0 3:fe
>        # DPMS capabilities: Active off:no  Suspend:no  Standby:no
>
> #       Mode    "1400x1050"     # vfreq 60.020Hz, hfreq 63.981kHz
> #               DotClock        108.000000
> #               HTimings        1400 1448 1560 1688
> #               VTimings        1050 1051 1055 1066
> #               Flags   "-HSync" "-VSync"
> #       EndMode
>	
>#        Mode    "1400x1050"     # vfreq 50.000Hz, hfreq 53.300kHz
>#                DotClock        89.970000
>#                HTimings        1400 1448 1560 1688
>#                VTimings        1050 1051 1055 1066
>#                Flags   "-HSync" "-VSync"
>#        EndMode
>
>	Modeline "1400x1050" 108.000 1400 1448 1560 1688 1050 1051 1055 1066 -hsync -vsync
>	# Block type: 2:0 3:fe
>        # Block type: 2:0 3:fe
>EndSection
>
>
>Section "Device"
>	#BusID "00:02.00"
>	Identifier  "Videocard0"
>	Driver      "i810"
>	VendorName  "Videocard vendor"
>	BoardName   "Intel 915"
>	VideoRam    65536
>EndSection
>
>Section "Screen"
>	Identifier "Screen0"
>	Device     "Videocard0"
>	Monitor    "SEC:5034"
>	DefaultDepth     24
>	SubSection "Display"
>		Viewport   0 0
>		Depth     24
>		Modes    "1400x1050"
>	EndSubSection
>EndSection
>
>Section "DRI"
>	Group        0
>	Mode         0666
>EndSection
>

Actions: View

Attachments on bug 2845: 2234 | 2235

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.