| View previous topic :: View next topic |
| Author |
Message |
cchee
Apprentice
Joined: 29 Jul 2003
Posts: 214
Location: NYC
|
 Posted: Wed Aug 20, 2003 3:29 am Post subject: |
 |
|
I have a dell inspiron 5100 and i can't seem to get the dri working even follows the exact steps in HOWTO as well as other solution posted in the forum. But before I dig deep, i just wonder if this chipset is supported or not. I can't seems to find a match in the Kernel->Character devices.
| Quote: | lspci | grep AGP
00:01.0 PCI bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset AGP Bridge (rev 03)
|
Any insight is greatly appreciated. |
|
| Back to top |
|
 |
diegs
Tux's lil' helper
Joined: 06 Aug 2003
Posts: 79
Location: nyc
|
| Posted: Wed Aug 20, 2003 5:42 am Post subject: |
|
|
well i emerged ati-drivers, and everything seems to work on my radeon 9000 (mobility m9).
however, speed sucks with both the stable drivers and the masked ones. I've tried kernel apgart and built-in, and i get
| Code: | diegs@chimera diegs $ glxgears
5437 frames in 5.0 seconds = 1087.400 FPS
6589 frames in 5.0 seconds = 1317.800 FPS
6587 frames in 5.0 seconds = 1317.400 FPS |
However everything seems to be ok.
| Code: | diegs@chimera diegs $ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: Radeon 9000/Mobility Fire GL 8800 Prototype DDR Pentium 4 (SSE2)
OpenGL version string: 1.3 (X4.3.0-2.9.12)
OpenGL extensions:
GL_ARB_multitexture, GL_EXT_texture_env_add, GL_EXT_compiled_vertex_array,
GL_S3_s3tc, GL_ARB_point_parameters, GL_ARB_texture_border_clamp,
GL_ARB_texture_compression, GL_ARB_texture_cube_map,
GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix,
GL_ARB_vertex_blend, GL_ARB_vertex_program, GL_ARB_window_pos,
GL_ATI_element_array, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader,
GL_ATI_map_object_buffer, GL_ATI_texture_env_combine3,
GL_ATI_texture_mirror_once, GL_ATI_vertex_array_object,
GL_ATI_vertex_attrib_array_object, GL_ATI_vertex_streams,
GL_ATIX_texture_env_combine3, GL_ATIX_texture_env_route,
GL_ATIX_vertex_shader_output_point_size, GL_EXT_abgr, GL_EXT_bgra,
GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_minmax,
GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal,
GL_EXT_polygon_offset, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_stencil_wrap,
GL_EXT_texgen_reflection, GL_EXT_texture3D,
GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle,
GL_EXT_vertex_array, GL_EXT_vertex_shader, GL_HP_occlusion_test,
GL_NV_texgen_reflection, GL_NV_blend_square, GL_NV_occlusion_query,
GL_SGI_color_matrix, GL_SGI_texture_edge_clamp,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_lod,
GL_SGIS_generate_mipmap, GL_SGIS_multitexture, GL_SUN_multi_draw_arrays
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess
... |
Anyone have any ideas why my framerate is down? I do get this line when starting X on my console:
| Code: | | (EE) fglrx(0): board is third party board |
but that's it. I wonder... although I think things are accelerated and quake 3 was playable. I've tried ac-sources and gaming-sources, and both drivers as I said. Absolutely no agpgart or DRI(DRM? I forget) compiled into the kernel or modularized. Am I missing something?
By the way this is a 1.6ghz centrino laptop, 32mb ddr mobility m9 9000 graphics.
_________________
knowledge = fv |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Wed Aug 20, 2003 7:45 am Post subject: |
|
|
cchee: It looks like you have an i845 chipset, which should be supported by the following kernel setting: | Code: | | < > Intel 440LX/BX/GX, I8xx and E7x05 chipset support |
| diegs wrote: | Anyone have any ideas why my framerate is down? I do get this line when starting X on my console:
| Code: |
(EE) fglrx(0): board is third party board |
|
That's nothing to worry about, I get it as well. It should really be a warning message, not an error ( WW instead of EE ).
| diegs wrote: | | but that's it. I wonder... although I think things are accelerated and quake 3 was playable. I've tried ac-sources and gaming-sources, and both drivers as I said. Absolutely no agpgart or DRI(DRM? I forget) compiled into the kernel or modularized. Am I missing something? |
If you have no AGP in the kernel, then I guess you must be using the drivers AGP support. You could try adding support for your AGP chipset to the kernel (you don't need to remove AGP from the kernel for the drivers to work, just DRM), then setting "UseInternalAGPGART" to "no" in your XF86Config. It might work faster that way.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Rüpel
Guru
Joined: 06 Nov 2002
Posts: 316
Location: Berlin/Germany
|
| Posted: Wed Aug 20, 2003 12:31 pm Post subject: |
|
|
| NuclearFusi0n wrote: | | emerge module-init-tools if you haven't already. |
that worked! thx! - back to the ati-drivers setup now... 
btw: i always thought, one of gentoo's portage features is exactly that: if you have one packet (the kernel-sources) that depends on another one (module-init-tools) and you emerge the first, emerge automatically installes the needed packets first... strange...  |
|
| Back to top |
|
|
schoett
n00b
Joined: 26 Jan 2003
Posts: 63
|
| Posted: Wed Aug 20, 2003 6:34 pm Post subject: 3.2.4: Gamma correction broken |
|
|
I installed driver 3.2.4 for my Radeon 9600 TX under Kernel 2.4.21, and I find that gamma correction no longer works (it worked before). The screen is now too dark.
From my XF86Config:
| Code: | Section "Monitor"
Identifier "Fujitsu-Siemens X19-1"
HorizSync 31.5-80
VertRefresh 56.3-75
Gamma 2.2
[...]
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
[...]
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
#
|
From my XFree86.log:
| Code: | (II) fglrx(0): EDID data from the display on Secondary head ---------------------------
(II) fglrx(0): Manufacturer: FUS Model: 470 Serial#: 16843009
(II) fglrx(0): Year: 2003 Week: 14
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) fglrx(0): Sync: Separate
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 38 vert.: 31
(II) fglrx(0): Gamma: 2.20
[...]
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
|
The last line used to say (2.2, 2.2, 2.2) with the 2.9.13 driver; there has been no significant change in the XF86Config file. |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Wed Aug 20, 2003 7:11 pm Post subject: |
|
|
Try the 3.2.0 driver. DGA is broken in 3.2.4, so maybe gamma correction is too 
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Wed Aug 20, 2003 7:12 pm Post subject: |
|
|
Ok, whew.
I have an Abit IS7 motherboard and I can load agpgart with agp_try_unsupported=1
i've used the internal agpgart and external kernel one with "fglrx" as the driver and DRI works but I cant get over 2300fps in glxgears (i have a radeon 9700 pro on a 3.4ghz machine, something is wrong. especially when i remember breaking 6k some months ago on an old gentoo install)
if I use the "radeon" driver i can NEVER EVER get DRI working no matter what i do. help pls?  |
|
| Back to top |
|
|
ralfie
n00b
Joined: 12 Aug 2003
Posts: 7
Location: Naaldwijk
|
| Posted: Wed Aug 20, 2003 7:27 pm Post subject: |
|
|
| Quote: | Screen goes black when X starts. Not able to use CTRL-ALT-Fn to change back to the console. Servers still working (ex Apache, SSH, etc).
Problable Cause: FSAA bug on some machines, pattern yet to be determined.
Solution:
Turn off FSAA. Post your problem on https://forums.gentoo.org/viewtopic.php?t=54793 |
IS this done by __GL_FSAA_MODE=0, export __GL_FSAA_MODE?
Or by setting FSAAscale in the XFree86 config to 0 ?
Last edited by ralfie on Thu Aug 21, 2003 2:26 pm; edited 2 times in total |
|
| Back to top |
|
|
schoett
n00b
Joined: 26 Jan 2003
Posts: 63
|
| Posted: Wed Aug 20, 2003 8:03 pm Post subject: |
|
|
| Wedge_ wrote: | | Try the 3.2.0 driver. DGA is broken in 3.2.4, so maybe gamma correction is too |
Well, I went back to 3.2.0 and 2.9.13 and had the same problem in every case (although 2.9.13 had worked before!). Once again I had fallen into that silly trap: fglrxconfig generates a file named XF86Config-4, which takes priority over my hand-edited XF86Config! |
|
| Back to top |
|
|
neuron
Advocate
Joined: 28 May 2002
Posts: 2371
|
| Posted: Wed Aug 20, 2003 8:29 pm Post subject: |
|
|
| schoett wrote: | | Wedge_ wrote: | | Try the 3.2.0 driver. DGA is broken in 3.2.4, so maybe gamma correction is too |
Well, I went back to 3.2.0 and 2.9.13 and had the same problem in every case (although 2.9.13 had worked before!). Once again I had fallen into that silly trap: fglrxconfig generates a file named XF86Config-4, which takes priority over my hand-edited XF86Config! |
umm... standard behavior, XF86Config-4 overrides XF86Config, but the files are identical, you can cp one over the other if you like.. |
|
| Back to top |
|
|
diegs
Tux's lil' helper
Joined: 06 Aug 2003
Posts: 79
Location: nyc
|
| Posted: Thu Aug 21, 2003 6:04 am Post subject: |
|
|
| Wedge_ wrote: | cchee: It looks like you have an i845 chipset, which should be supported by the following kernel setting: | Code: | | < > Intel 440LX/BX/GX, I8xx and E7x05 chipset support |
|
i can't get kernel AGP to work. I selected that one but it says unsupported agp chipset when booting, try passing agp_try_unsupported=1. I tried that and no dice. This is on gs-sources 2.4.21. I think my centrino is like an intel 855 or 865 or something. I am going to try a 2.6 kernel with dri drivers and see where that takes me. I found on other forums that the dri drivers are faster than the ati-driver.
i tried them with my current kernel but glxinfo shows that it is not accelerated, obviously, since i have no functioning agpgart.
thanks for your suggestions though.
_________________
knowledge = fv |
|
| Back to top |
|
|
Rüpel
Guru
Joined: 06 Nov 2002
Posts: 316
Location: Berlin/Germany
|
| Posted: Thu Aug 21, 2003 4:58 pm Post subject: |
|
|
i think i have it basically working now (radeon 9800, kt400, kernel 2.6), but there are two things left:
i had alsa compiled as a module on my 2.4.20 before and now it's compiled in, but still in the autoload-section when booting. how can i safely remove alsa from the automatically loaded modules?
second: is 550 fps ok in fgl_glxgears?
*edit* 4450 in glxgears seems ok  (firebird works now too)
thx all for your help so far.
(mozilla is emerging in the background, so i still post from lynx - hope it doesn't look too bad  |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Thu Aug 21, 2003 8:19 pm Post subject: |
|
|
| Quote: | | i had alsa compiled as a module on my 2.4.20 before and now it's compiled in, but still in the autoload-section when booting. how can i safely remove alsa from the automatically loaded modules? |
You should do "emerge -C alsa-driver" if you haven't already, but you should leave the other alsa- packages (lib, utils etc). Then just remove the alsa module names from the modules autoload file.
| Quote: | second: is 550 fps ok in fgl_glxgears?
*edit* 4450 in glxgears seems ok |
Those are fine, they're almost the same as I'm getting (9800 Pro/nForce2).
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Rüpel
Guru
Joined: 06 Nov 2002
Posts: 316
Location: Berlin/Germany
|
| Posted: Thu Aug 21, 2003 8:58 pm Post subject: |
|
|
thx wedge! you're the "ati-radeon-sticky-hero"!
btw: i should add that i also have a radeon 9800 pro - it just runs, nothing is optimized (if there actually is some space for optimization...) |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 12:26 am Post subject: |
|
|
Guys I'm getting 2500fps with a radeon 9700 pro on a 3.4ghz machine, something is seriously wrong here. I remember breaking 6k a while ago when I had gentoo installed but for the life of me i cannot remember if iw as using ATI drivers or the xfree-drm ones. I'm aware that the 9700 is not supported in the opensource drivers but maybe it was a while ago and support was removed? I get the same score in glxgears using internal and external agpgart. I have an abit IS7 motherboard so I have to load with agp_try_unsupported=1
.....
I'm really not obsessed with benches or anything but 2500 is considerably low for my system, and no FSAA is not turned on. |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 4:18 am Post subject: |
|
|
I also wanted to add/ask ...
does anyone else notice that 2D is a lot slower using fglrx over the default "ati" X driver? |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Aug 22, 2003 1:14 pm Post subject: |
|
|
Yuber: the first thing to remember is that glxgears is not really a benchmarking tool, it's mainly just a little program you can use to check if hardware accelerated rendering is working, which it seems to be. Try benchmarking on Q3A or something similar to get a better idea of performance. Secondly, the recent versions of the ati-drivers, 3.2.0 and 3.2.4, seem to be significantly slower than the 2.9.x versions. I lose over 1000fps in glxgears going from 2.9.13 to 3.2.0, even with FSAA at the lowest setting. Check the output of dmesg for error messages in case something is going wrong, and make sure the output of glxinfo is correct.
| Yuber wrote: | | does anyone else notice that 2D is a lot slower using fglrx over the default "ati" X driver? |
2D seems nice and fast for me, I've never noticed any problems with it.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 1:27 pm Post subject: |
|
|
| Wedge_ wrote: | Yuber: the first thing to remember is that glxgears is not really a benchmarking tool, it's mainly just a little program you can use to check if hardware accelerated rendering is working, which it seems to be. Try benchmarking on Q3A or something similar to get a better idea of performance. Secondly, the recent versions of the ati-drivers, 3.2.0 and 3.2.4, seem to be significantly slower than the 2.9.x versions. I lose over 1000fps in glxgears going from 2.9.13 to 3.2.0, even with FSAA at the lowest setting. Check the output of dmesg for error messages in case something is going wrong, and make sure the output of glxinfo is correct.
| Yuber wrote: | | does anyone else notice that 2D is a lot slower using fglrx over the default "ati" X driver? |
2D seems nice and fast for me, I've never noticed any problems with it. |
Well 3k of a difference is obviously huge, which is why it worries me. War3 is a tad slow in winex3.1 but that's obvious that it would be I guess. When I'm not feeling lazy I'll bench q3a in windows then linux. The 2D thing seems to be like, it takes longer to draw the apps on the screen when i maximize them. I'm using KDE 3.2, but this mainly happens with GTK2 apps. However, if I use the "ati" driver that comes with XFree, it is not NEARLY as slow. Dunno what could be causing this but I remember nvidia drivers having this exact same issue a while back.
I'm stumped and depressed over this. |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Aug 22, 2003 1:49 pm Post subject: |
|
|
What does your XF86Config look like? I can't think of anything that would be causing the slow redraws. I'm using fluxbox, and GTK2 apps work fine.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 1:59 pm Post subject: |
|
|
| Wedge_ wrote: | | What does your XF86Config look like? I can't think of anything that would be causing the slow redraws. I'm using fluxbox, and GTK2 apps work fine. |
| Code: |
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# 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.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out).
#
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
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/usbmouse"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
HorizSync 30-110
VertRefresh 48-170
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 111# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
Option "CenterMode" "off"
# === QBS Support ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === Misc Options ===
Option "UseFastTLS" "1"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
# Option "EnablePrivateBackZ" "yes"
# === FSAA ===
Option "FSAAScale" "1"
BusID "PCI:1:0:0" # vendor=1002, device=4e44
Screen 0
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# oSection "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Server Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.
Screen "Screen0"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
### EOF ###
|
|
|
| Back to top |
|
|
dnix
Apprentice
Joined: 17 Jun 2003
Posts: 271
Location: Italy
|
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Aug 22, 2003 2:21 pm Post subject: |
|
|
I don't see any problems there. Are there any errors in the xfree logfile or in dmesg? Were you using a different kernel and driver version back when you got better fps in glxgears?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 2:36 pm Post subject: |
|
|
| Wedge_ wrote: | | I don't see any problems there. Are there any errors in the xfree logfile or in dmesg? Were you using a different kernel and driver version back when you got better fps in glxgears? |
No errors, and I was using different drivers, the 2.9 series or something. This still doesn't explain why people are thousands of FPS higher than me on lesser system.s |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Fri Aug 22, 2003 2:43 pm Post subject: |
|
|
Going back to the 2.9.x drivers would almost certainly increase your fps, but if your performance is really that bad there must be something else wrong. Have you tried any games that run natively, like Q3, UT, RTCW, TuxRacer etc? What kind of score do you get in fgl_glxgears?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Yuber
Tux's lil' helper
Joined: 08 Jan 2003
Posts: 139
|
| Posted: Fri Aug 22, 2003 2:52 pm Post subject: |
|
|
| Wedge_ wrote: | | Going back to the 2.9.x drivers would almost certainly increase your fps, but if your performance is really that bad there must be something else wrong. Have you tried any games that run natively, like Q3, UT, RTCW, TuxRacer etc? What kind of score do you get in fgl_glxgears? |
No native games yet, and 250fps in fglx gears. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
