LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 08-12-2006, 03:02 PM   #1
qrc
LQ Newbie
 
Registered: Aug 2006
Posts: 2

Rep: Reputation: 0
Atrocious video performance


Hello,

My computer, when it runs Linux, has truly atrocious video performance.

Operating system: Slackware 10.2 (kernel 2.4.31)
Processor: AMD Athlon XP 1500+ -- ~1.3 GHz
Memory: 256 MB RAM
Graphics: NVIDIA GeForce 6600 256MB

I did the best I could to follow your common tutorials to enable 3D acceleration, and I assume I did it correctly because the NVIDIA logo appears when I login. If you need to check my work in editing the xorg.conf, here it is:
Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder3)  Wed Dec 14 16:39:22 PST 2005

# 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/cyrillic"
    FontPath 	"/usr/X11/lib/fonts/TTF"
    FontPath 	"/usr/local/share/fonts"
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"
    Load         "dri"
EndSection

Section "DRI"
    Mode 0666
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"    ""
    Identifier     "Keyboard1"
    Driver         "kbd"
EndSection

Section "InputDevice"

# Identifier and driver
# 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         "Buttons" "5"
    Option         "ZAxisMapping" "4 5"
# On platforms where PnP mouse detection is supported the following
    Option         "Protocol" "IMPS/2"
# 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       31.5 - 50.0
    VertRefresh     40.0 - 90.0
EndSection

Section "Device"

    #VideoRam    4096
    # Insert Clocks lines here if appropriate
    Identifier     "VESA Framebuffer"
    Driver         "nvidia"
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      "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       32
        Modes      "1024x768" "800x600" "640x480"
    EndSubSection
EndSection
The space simulation program Celestia seemed to work fine at one point -- at which time I was using GeForce2 and not the GeForce 6600 I have now -- but it suddenly got slower one day after I had been trying and failing to update KDE (or it might have been trying to install GNOME, but it was a while ago). Now the Celestia program runs slowly, and is choppy.

As I was reading through some tutorials to enable 3D acceleration, I also noticed that people asked you to run glxgears, and if the FPS was >=1000 you did it right. Unfortunately, the tutorials never tell you what to do if your glxgears FPS was around 260 before and after the tutorial that supposedly would increase the FPS.

I am utterly at a loss as to how I could get my graphics card to do its job. After stubbornly refusing to talk to other people about it and instead opting for more tutorial-googling, I've finally given in to just asking... could you help me with my computer problem?

As requested by the "Before you post: What to include in a Hardware question" topic, here is the output of /sbin/lspci:
Code:
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller (rev 14)
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
01:05.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2)

Last edited by qrc; 08-12-2006 at 03:10 PM.
 
Old 08-12-2006, 04:56 PM   #2
J.W.
LQ Veteran
 
Registered: Mar 2003
Location: Boise, ID
Distribution: Mint
Posts: 6,642

Rep: Reputation: 85
Welcome to LQ. Have you installed the current nVidia drivers? Also, could you post the output of the command
Code:
lsmod
which lists which kernel modules have been loaded
 
Old 08-12-2006, 05:18 PM   #3
qrc
LQ Newbie
 
Registered: Aug 2006
Posts: 2

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by J.W.
Welcome to LQ. Have you installed the current nVidia drivers? Also, could you post the output of the command
Code:
lsmod
which lists which kernel modules have been loaded
I remember reading a piece of Slackware-related documentation recommending that I not use the NVIDIA installers provided on NVIDIA's website, but I tried it anyway. The result was an error: "The runtime configuration check failed for the library 'libGL.so.1.0.8762' (expected: '/usr/lib/libGL.so.1', found: '/lib/libGL.so.1'). [...]"

I have to go now, but when I return I will try to fix this problem.

Here is the output of lsmod:
Code:
Module                  Size  Used by    Tainted: P
nvidia               4218688   6
i2c-core               12676   0 (autoclean) [nvidia]
snd-pcm-oss            36736   0
snd-mixer-oss          12376   0 [snd-pcm-oss]
printer                 7648   0
parport_pc             15044   0
parport                22824   0 [parport_pc]
uhci                   24284   0 (unused)
usbcore                59148   1 [printer uhci]
snd-via82xx            13376   0
gameport                1420   0 [snd-via82xx]
snd-ac97-codec         58556   0 [snd-via82xx]
snd-pcm                54344   0 [snd-pcm-oss snd-via82xx snd-ac97-codec]
snd-timer              13764   0 [snd-pcm]
snd-mpu401-uart         3136   0 [snd-via82xx]
snd-rawmidi            12480   0 [snd-mpu401-uart]
snd-seq-device          3812   0 [snd-rawmidi]
snd                    32772   0 [snd-pcm-oss snd-mixer-oss snd-via82xx snd-ac97-codec snd-pcm snd-timer snd-mpu401-uart snd-rawmidi snd-seq-device]
snd-page-alloc          4712   0 [snd-mixer-oss snd-via82xx snd-pcm snd-timer snd-rawmidi snd-seq-device snd]
soundcore               3396   3 [snd]
3c59x                  26576   1
pcmcia_core            39172   0
ntfs                   51232   1 (autoclean)
ide-scsi                9392   0
agpgart                45508   3
 
Old 08-12-2006, 05:42 PM   #4
Electro
LQ Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
I do not know where you read that if you see 1000 or more fps in glxgears, then it is working. This is wrong because I have seen glxgears show between 200 and 300 even when hardware acceleration is on. The reason for this is the Composite module in Xorg an earlier XFree86 versions. The Composite module handles the opaque levels (aka transparencies) of windows. The utility glxgears should NEVER be use as a benchmark tool. glxgears SHOULD ALWAYS be used to show that 3D rendering is working with out any problems. The only way to tell you if you did it correct is type 'glxinfo | grep -i mesa'. If anything comes up, then you did something wrong. Mesa or Mesa3D is a software 3D render. It uses the main processor to render 3D scenes, so you will an fps around 5 to 200 depending on processor and memory bandwidth.

In order to use nVidia module. You will need to load nvidia module (driver) before loading up GUI. In /etc/X11/xorg.conf comment the line that reads Load "dri". Use gtf to help you generate modelines and place them in the monitor section.

The reason why many people do not recommend using the nvidia installer is because they do not backup the files that they are going to overwrite. People think it is toxic waste to use nvidia installer. I have no trouble about this. You can either use a slackware file to install the nvidia modules and libraries or use the nvidia installer to do that for you.
 
Old 08-14-2006, 01:18 AM   #5
ciotog
Member
 
Registered: Mar 2004
Location: Canada
Distribution: Slackware current
Posts: 728
Blog Entries: 2

Rep: Reputation: 43
You could try running "ldd $(which glxgears)" to see which libGL is being used. Perhaps a software GL implementation is superceding the correct one.
 
  


Reply

Tags
graphics, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Video Performance jmsiu Ubuntu 2 09-06-2005 11:44 PM
Sticky Video Performance SML Solaris / OpenSolaris 4 06-20-2005 08:08 AM
video performance taoweijia Linux - General 2 01-08-2004 03:17 AM
how to enhance video performance taoweijia Linux - General 1 01-07-2004 12:13 PM
Poor Video Performance yoink Linux - Newbie 3 12-03-2002 12:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 11:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration