Why my xorg.conf is so short?

[cr4ck3r]

Hello everyone,
I do a fresh install of FC6, and notice that my xorg.conf file is too short

# Xorg configuration created by pyxf86config

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
Option "LeftEdge" "120"
Option "RightEdge" "830"
Option "TopEdge" "120"
Option "BottomEdge" "650"
Option "FingerLow" "14"
Option "FingerHigh" "15"
Option "MaxTapMove" "110"
Option "VertScrollDelta" "20"
Option "HorizScrollDelta" "20"
Option "MinSpeed" "0.3"
Option "MaxSpeed" "0.75"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "radeon"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection


It's much shorter than xorg.conf in FC5.
By the way, I've got this warning when I executed the command
[user@localhost ~]$ glxgears
libGL warning: 3D driver claims to not support visual 0x4b
8777 frames in 5.0 seconds = 1755.327 FPS
9050 frames in 5.0 seconds = 1809.820 FPS
9118 frames in 5.0 seconds = 1823.462 FPS
9073 frames in 5.0 seconds = 1814.418 FPS
[user@localhost ~]$
Glad to hear from you.

[Seve]

Hello:
Why is it so short?
Well I think it has to do with Xorg 7.1 versus Xorg 7.0
That being said, if you look through your Xorg.0.log you will likely see lots of warnings and perhaps errors related to missing items.
I would look at your log file and see if you can add back some items to your xorg.conf file more along the lines of what you had in FC5
I don't know if the configuration of X is pooched or that is exactly how it is supposed to be. In my case on 3 different machines I had to work at adding items back to the xorg.conf file to get rid of errors ?
Others' experience may be different?

Seve

[Janl]

Supposedly Xorg is able to "automagically" add in the bits it needs. I ran across a message regarding that, but atm I don't remember where it was.

[Seve]

Supposedly Xorg is able to "automagically" add in the bits it needs. I ran across a message regarding that, but atm I don't remember where it was.
Hello:
Yes I think you are right.
However, the actual results seem to fall somewhat short of the advertised :confused:

Seve

[cr4ck3r]

I found something interesting in the Xorg.0.log file

*** Direct rendering support is highly experimental for Radeon 9500
*** and newer cards. The 3d mesa driver is not provided in this tree.
*** A very experimental (and incomplete) version is available from Mesa CVS.
*** Additional information can be found on http://r300.sourceforge.net
*** This message has been last modified on 2005-08-07.

:D And
(II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and newer.
(II) RADEON(0): Render acceleration disabled
It seems that my video card is so new (ATI Radeon Mobility X600) :confused:
And here is the the errors:
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
Actually, I could enable desktop effects, but I can not run some game with Wine.
Do I need to switch back to the closed-source driver?