Attachment 3960 Details for Bug 5071 – The xorg conf I use with revision 1.14 of mouse.c

The xorg conf I use with revision 1.14 of mouse.c

xorg.conf (text/plain), 3.39 KB, created by Mathias Fröhlich on 2005-12-01 17:12:31 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Mathias Fröhlich

Created: 2005-12-01 17:12:31 UTC

Size: 3.39 KB

patch

obsolete

># XFree86 4 configuration created by pyxf86config
>
>Section "ServerLayout"
>	Identifier     "Default Layout"
>	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"
>        SubSection "extmod"
>                Option      "omit xfree86-dga"   # don't initialise the DGA extension
>        EndSubSection
>#	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" "de"
>	Option	    "XkbVariant" "nodeadkeys"
>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"
>	Identifier   "Monitor0"
>	VendorName   "Monitor Vendor"
>	ModelName    "NEC MultiSync LCD2080UX"
>	HorizSync    20.0 - 75
>	VertRefresh  43.0 - 72.0
>#	Option	    "dpms"
>EndSection
>
>Section "Device"
>	Identifier  "Videocard0"
>	Driver      "radeon"
>	VendorName  "Videocard vendor"
>	BoardName   "ATI Radeon"
>        Option "MonitorLayout" "TMDS, NONE"
>#        Option "AGPMode" "4"
>#        Option "DDCMode" "on"
>#        BusID       "PCI:3:0:0"
>EndSection
>
>Section "Device"
>        Identifier  "ATI Graphics Adapter"
>        Driver      "fglrx"
>        Option      "no_accel" "no"
>        Option      "no_dri" "no"
>        Option      "MonitorLayout" "AUTO, NONE"
>        Option      "NoTV" "yes"
>#        Option      "FSAAEnable" "yes"
>#        Option      "FSAAScale" "2"
>        Option      "UseInternalAGPGART" "yes"
>	Option      "UseFastTLS" "2" 
>        BusID       "PCI:3:0:0"
>EndSection
>
>
>Section "Screen"
>	Identifier "Screen0"
>#	Device     "Videocard0"
>        Device  "ATI Graphics Adapter"
>	Monitor    "Monitor0"
>	DefaultDepth     24
>	SubSection "Display"
>		Viewport   0 0
>		Depth     24
>		Modes    "1600x1200"
>	EndSubSection
>EndSection
>
>Section "DRI"
>	Group        0
>	Mode         0666
>EndSection
>

Actions: View

Attachments on bug 5071: 3960 | 4316

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.