| View previous topic :: View next topic |
| Author |
Message |
Yuusou
Apprentice
Joined: 18 May 2005
Posts: 178
Location: Canada
|
 Posted: Fri Mar 10, 2006 12:52 am Post subject: OpenGL Screensaver issues on ATI Radeon X300 |
 |
|
Okay, I've been trying to fix this since I installed which was months ago and I still haven't figured it out. Here's my specs and history:
-Pentium M 2.13GHz
-ATI Radeon X300
-1 GB RAM
-3 GB Swap
-my hd is 100GB SATA (so don't even think about telling me it's a dma problem -_-) <--unless you're absolutely sure it is a dma problem and you know how to fix it
Okay, now history:
-configured X correctly (version 6.8.2-r6)
-merged and correctly configured ati-drivers (version 8.22.5)
-tried both ati and xorg-x11 OpenGL interfaces (neither makes a difference, they both work the same)
-using KDE 3.5.1
-OpenGL screensavers such as Euphoria and Solar Winds lag immesnely (they don't run smoothly, they skip and don't run nicely)
-command used for configuring the xorg.conf properly with ati-drivers: /opt/ati/bin/aticonfig --initial --input=/etc/X11/xorg.conf
Okay, now for some output and code listings
#/etc/X11/xorg.conf
| Code: |
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# 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 X.Org Foundation 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 X.Org Foundation 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 X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# 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
# **********************************************************************
# **********************************************************************
# 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 xorg.conf 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# **********************************************************************
# 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 "DRI"
# Mode 0666
# EndSection
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 0 "aticonfig Screen 0" 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)
#
#
# FontPath "/usr/share/fonts/CID/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
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 "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
Load "dri"
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"
# 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" "pc105"
# 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 Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "dell"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
# Identifier and driver
# Option "Resolution" "256"
# 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)
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
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 - 79.0
VertRefresh 50.0 - 90.0
EndSection
Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection
Section "Device"
# 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.
# 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
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
EndSection
Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
Option "(null)"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "on"
Option "OverlayOnCRTC2" "0"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1400x1050" "1280x1024"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1400x1050" "1280x1024"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1400x1050" "1280x1024"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig Screen 0"
Device "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
|
#Output of glxgeras
| Code: |
Azel ~ # glxgears
2183 frames in 5.0 seconds = 436.600 FPS
2270 frames in 5.0 seconds = 454.000 FPS
2043 frames in 5.0 seconds = 408.600 FPS
2156 frames in 5.0 seconds = 431.200 FPS
2270 frames in 5.0 seconds = 454.000 FPS
2157 frames in 5.0 seconds = 431.400 FPS
X connection to :0.0 broken (explicit kill or server shutdown).
|
**That kill message was by me btw**
#output of hdparm -tT /dev/sda
| Code: |
Azel ~ # hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 2840 MB in 2.00 seconds = 1419.51 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
Timing buffered disk reads: 116 MB in 3.03 seconds = 38.33 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
|
**Not sure what the inappropriate ioctl messages are about, but whatever, I was told that those hd times are pretty good**
Okay, well that's all I can think of. If you need more info let me know, but any suggestions on what is wrong would be appreciated. Theoretically, it should work, because I know people with older ATI cards that have Euphoria working. Although my one question is this: does it really matter if you use opengl-update or eselect? I know eselect breaks /usr/lib/libGL.la And also KDE functions perfect and games and movies are displayed great, but it's just those OpenGL screensavers that are the issue...and I really want them working. so yeah...any and all help is welcome and appreciated. |
|
| Back to top |
|
 |
antares2001
Guru
Joined: 02 Mar 2004
Posts: 339
Location: Germany
|
| Posted: Fri Mar 10, 2006 1:57 am Post subject: |
|
|
Hi!
You have to take the comments away from
| Code: | # Section "DRI"
# Mode 0666
# EndSection |
in your xorg.conf
Otherwise only root will have acceleration.
_________________
* Toshiba SM30X Notebook, Pentium-M 725 CPU, ATI Radeon 9700, 512MB RAM, 80GB
* Pentium D 820 2,8 GHz (EM64T), Geforce6, 200GB + 40GB ATA, 250GB SATA2, WinFastTV 2000XP, 1,5GB RAM
Gentoo Linux 2006.1 |
|
| Back to top |
|
|
Yuusou
Apprentice
Joined: 18 May 2005
Posts: 178
Location: Canada
|
| Posted: Sat Mar 11, 2006 6:03 am Post subject: |
|
|
| Okay, I did that, and I really don't see a difference. |
|
| Back to top |
|
|
antares2001
Guru
Joined: 02 Mar 2004
Posts: 339
Location: Germany
|
| Posted: Sat Mar 11, 2006 10:40 am Post subject: |
|
|
Post glxinfo's output please.
_________________
* Toshiba SM30X Notebook, Pentium-M 725 CPU, ATI Radeon 9700, 512MB RAM, 80GB
* Pentium D 820 2,8 GHz (EM64T), Geforce6, 200GB + 40GB ATA, 250GB SATA2, WinFastTV 2000XP, 1,5GB RAM
Gentoo Linux 2006.1 |
|
| Back to top |
|
|
Yuusou
Apprentice
Joined: 18 May 2005
Posts: 178
Location: Canada
|
| Posted: Sun Mar 12, 2006 6:27 am Post subject: |
|
|
| I fixed it, I just had to switch back to the ATI OpenGL interface. So it was working perfect, however, now, after a reboot, kdm's init script loads without error it seems although kdm doesn't start. I tried stopping it and using startx with no success, I also checked all my config files and they were fine. I dunno, I'm stumped on this one... |
|
| 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
