A Guide: Enabling 3D Acceleration in X11

Alien_Hominid · 05-21-2007, 01:39 AM

Ok. Try this:

Code:

cd /usr/X11R6/bin
ldd glxgears

Post the table.

gtludwig · 05-21-2007, 07:41 AM

Code:

gtl@omicron:/usr/X11R6/bin$ ldd glxgears
        linux-gate.so.1 =>  (0xffffe000)
        libGL.so.1 => /usr/lib/libGL.so.1 (0xb7ea6000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xb7e98000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xb7dcb000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7db9000)
        libm.so.6 => /lib/tls/libm.so.6 (0xb7d96000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7c67000)
        libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0xb72f4000)
        libnvidia-tls.so.1 => /usr/lib/tls/libnvidia-tls.so.1 (0xb72f2000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0xb72ee000)
        /lib/ld-linux.so.2 (0xb7f55000)
gtl@omicron:/usr/X11R6/bin$

Alien_Hominid · 05-21-2007, 08:50 AM

Mine:

Code:

bash-3.1# ldd glxgears
        linux-gate.so.1 =>  (0xffffe000)
        libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0xb7eff000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xb7ef1000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xb7e24000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7e12000)
        libm.so.6 => /lib/tls/libm.so.6 (0xb7def000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7cc0000)
        libXxf86vm.so.1 => /usr/X11R6/lib/libXxf86vm.so.1 (0xb7cba000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0xb7cb6000)
        /lib/ld-linux.so.2 (0xb7f78000)

Interesting what these libXxf86vm.so.1 and libnvidia-tls.so.1 do. Maybe new driver somehow differently responds to glxgears, which decreases performance. It's strange that fx5500 gives such low fps.
What kernel and xorg are you using?
Maybe somebody also uses this card and could give reply? Do you get Direct Rendering now?

H_TeXMeX_H · 05-21-2007, 11:40 AM

Quote:

Originally Posted by gustaveiras

There was improvement, very little, though.

NvAGP is nVidia's built-in AGP driver. Usage (for driver 1.0-9755) detailed here.

I wouldn't trust NvAGP. Turn it off right after you build AGPGART as a module. I have GeForce4 Ti 4600 with 1.0-9631 drivers and using AGPGART, and I get:

Code:

24076 frames in 5.0 seconds = 4815.046 FPS
24282 frames in 5.0 seconds = 4856.320 FPS
24299 frames in 5.0 seconds = 4859.740 FPS
24179 frames in 5.0 seconds = 4834.867 FPS

You should be getting at least 4000 FPS I think.

cwwilson721 · 05-21-2007, 11:43 AM

NvAGP is only for Nvidia chipset motherboards, where the Nvidia chipset is controlling the AGP slot.

Otherwise, use what the kernel wants you to use

jnsg · 05-21-2007, 04:30 PM

EDIT: I started a new thread about this, as 3D acceleration isn't the issue.

I did some searching on ATI Big Desktop and got very little, so I thought I'd pose my issues here. I had gotten the free radeon driver to work for me, including MergedFB with acceleration et al. However, Unreal Tournament 2004 (as well as other modern games, as far as I can tell) uses S3 Texture Compression, which is only in the proprietary driver. I was noticing performance issues which I attributed to this fact, so now I'm trying to get where I was with fglrx.

With clone mode (i.e. nothing special, but with both monitors plugged in) UT2004 works fine. Under Big Desktop, however, input seems sluggish. In the menus, the mouse has about a half second delay in all movements. In game, about half the time any keyboard/mouse input has a similar delay. Rendering seems to be OK. I really don't want to restart X under a different configuration just to run games (note I haven't tried any other than UT2004). Is this a known issue? When running the full-screen game, even under Big Desktop it goes into clone mode. The sluggishness is apparent in windowed mode as well.

My other issue is that my monitors are switched. My DVI output is treated as secondary, and VGA is primary. Once I've started X I can run aticonfig --swap-monitor and everything's fine, but the setting doesn't stick (it doesn't add anything to xorg.conf like many of the aticonfig options do). Other than physically switching my monitors (I'd rather not, as I'd like my DVI to be primary) or putting the command in .xinitrc or something, is there a way to make the outputs stay swapped?

Radeon 9200 128MB DVI+VGA
Slackware 11.0
Kernel 2.6.17.13 (modified huge26)
fglrx 8.28.8

gtludwig · 05-21-2007, 05:31 PM

Ok, I've (re)compiled the kernel-2.6.20 and started X (X11R6.9.x) and got these FPS:

Code:

gtl@omicron:~$ glxgears
10624 frames in 5.0 seconds = 2124.761 FPS
11192 frames in 5.0 seconds = 2238.204 FPS
11194 frames in 5.0 seconds = 2238.731 FPS
11174 frames in 5.0 seconds = 2234.653 FPS
11187 frames in 5.0 seconds = 2237.221 FPS
10646 frames in 5.0 seconds = 2129.070 FPS
gtl@omicron:~$

AGPGART is now built as module:

Code:

root@omicron:~# lsmod
Module                  Size  Used by
nvidia               6829444  22
amd64_agp               9480  1
agpgart                25904  2 nvidia,amd64_agp
root@omicron:~#

and lspci:

Code:

root@omicron:~# lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)
root@omicron:~#

I'm really running out of ideas here! How can I help you guys help me?

Thanks!

Something struck me... poking around I found this in dmesg:

Code:

NVRM: loading NVIDIA UNIX x86 Kernel Module  1.0-9755  Mon Feb 26 23:21:15 PST 2007
NVRM: loading NVIDIA UNIX x86 Kernel Module  1.0-9755  Mon Feb 26 23:21:15 PST 2007
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
NVRM: loading NVIDIA UNIX x86 Kernel Module  1.0-9755  Mon Feb 26 23:21:15 PST 2007
NVRM: loading NVIDIA UNIX x86 Kernel Module  1.0-9755  Mon Feb 26 23:21:15 PST 2007
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode

Alien_Hominid · 05-21-2007, 06:02 PM

gustaveiras, did you disable NvAGP?
do you get DRI now?

gtludwig · 05-21-2007, 06:28 PM

NvAGP is commented out in /etc/X11/xorg.conf

and glxinfo gives me this:

Code:

glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4

and a lot more!

H_TeXMeX_H · 05-21-2007, 06:29 PM

Please post all of your xorg.conf.

gtludwig · 05-21-2007, 06:44 PM

ok, here goes /etc/X11/xorg.conf

Code:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder3)  Mon Feb 26 23:38:46 PST 2007

# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************
# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#
# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# Some examples of extended input devices
# 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# 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"
# option.
# **********************************************************************
# 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
# 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.  In this example, screen 2 is located to the
# right of screen 1.
# 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".
    Identifier     "Simple Layout"
    Screen         "Screen 1" 0 0
    InputDevice    "Mouse1" "CorePointer"
    InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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).
# 
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
#    ModulePath "/usr/X11R6/lib/modules"
    RgbPath         "/usr/X11R6/lib/X11/rgb"
    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/CID/"
    FontPath        "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath        "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath        "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath        "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
    Load           "dbe"  	# Double buffer extension
    SubSection     "extmod"
        Option         "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load           "type1"
    Load           "freetype"
    #Load        "speedo"
    Load           "glx"
EndSection

Section "InputDevice"

# 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"
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
#    Option     "AutoRepeat"    "500 5"
# Specifiy 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 European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# 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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc101"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""
#    Driver         "kbd"
    Identifier     "Keyboard1"
    Driver         "keyboard"
    Option         "XkbRules" "xorg"
    Option         "XkbModel" "abnt2"
    Option         "XkbLayout" "br"
    Option         "XkbVariant" "abnt2"
    Option         "XkbOptions" "abnt2"
EndSection

Section "InputDevice"

# Identifier and driver
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
#    Option     "Protocol"      "Auto"
# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"
# 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"
    Identifier     "Mouse1"
    Driver         "mouse"
    Option         "Protocol" "IMPS/2"
    Option         "ZAxisMapping" "4 5"
# The mouse device.  The device is normally set to /dev/mouse,
    Option         "Device" "/dev/mouse"
#   Option "Device"      "/dev/psaux"
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
    Identifier     "My Monitor"
    HorizSync       30.0 - 71.0
    VertRefresh     50.0 - 160.0
EndSection

Section "Device"

    VideoRam    262144
    # Insert Clocks lines here if appropriate
    Identifier     "VESA Framebuffer"
    Driver         "nvidia"
#    Option         "NvAGP" "1"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
#   DefaultDepth 8
#   DefaultDepth 16
#   DefaultDepth 32
# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
    Identifier     "Screen 1"
    Device         "VESA Framebuffer"
    Monitor        "My Monitor"
    DefaultDepth    24
    SubSection     "Display"
        Depth       8
        Modes      "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       16
        Modes      "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       24
        Modes      "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       32
        Modes      "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

#Section "DRI"
#    Group      "video"
#    Mode       0666
#EndSection

H_TeXMeX_H · 05-21-2007, 09:35 PM

First, get rid of this

Code:

VideoRam    262144

no need for it.

Also, these two seem awfully high

Code:

    HorizSync       30.0 - 71.0
    VertRefresh     50.0 - 160.0

I would run 'xorgsetup' and let it autodetect these, then change the driver to 'nvidia' when it's done.

If not, then typical values are:

Code:

    HorizSync       28.0 - 65.0
    VertRefresh     57.0 - 63.0

So at least lower that VertRefresh max from 160 to 70 or so.

gtludwig · 05-21-2007, 10:23 PM

I just restarted X after killing it and running

Code:

# xorgsetup

Screen came up at 1024x768 (I was using 1280x1024) I opened a terminal and this came out:

Code:

gtl@omicron:~$ glxgears
10651 frames in 5.0 seconds = 2130.123 FPS
11253 frames in 5.0 seconds = 2250.599 FPS
11244 frames in 5.0 seconds = 2248.795 FPS
12721 frames in 5.0 seconds = 2544.116 FPS

17515 frames in 5.0 seconds = 3502.953 FPS
17640 frames in 5.0 seconds = 3527.911 FPS
17634 frames in 5.0 seconds = 3526.630 FPS
17296 frames in 5.0 seconds = 3459.045 FPS

25764 frames in 5.0 seconds = 5152.654 FPS
28744 frames in 5.0 seconds = 5748.757 FPS
28741 frames in 5.0 seconds = 5748.162 FPS
28742 frames in 5.0 seconds = 5748.308 FPS

gtl@omicron:~$

The first four calculations of glxgears were made with the pop-up gear animation on top of the Konsole (I use KDE 3.5.6). The second four FPS group took place when the gear animation was half covered by Konsole and the third group, the 5k+s, happened with the animation minimized.

I understand there should be some difference, but a question comes to mind: what are you running to get the numbers you get? Here I just started X after xorgsetup. 3D accel is worth if you really see a result!

On a side note, I always thought those gears spinning faster. Maybe I just shoot a little video, post it at Youtube and place the link here!

Anyway, looking foward for comments on those figures, I'm off to fix screen size!

Back with a sad constation I need to change my monitor... Perhaps a 19" LCD... just dreaming!!

H_TeXMeX_H · 05-21-2007, 11:06 PM

Well, you should not resize that glxgears window, just drag it to a place where it is not covered by anything. I mean, basically it tests 3D rendering to the screen. If it is covered or resized, it won't give accurate data.

Also, if you ran 'xorgsetup', remove the line that says something like:

Code:

BusID       "PCI:1:0:0"

The nvidia installer usually removes this line, because it may cause issues.

gtludwig · 05-21-2007, 11:24 PM

Line removed!

I did not run the nvidia installer after running xorgsetup. Should I do so?