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 |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-28-2007, 11:39 AM
|
#1
|
Member
Registered: Sep 2004
Location: Jakobstad Finland
Distribution: Slackware 10
Posts: 42
Rep:
|
radeon problem low fps
I have problem with my mobile radeon 9600.
My configuration is
Slackware 11
kernel 2.6.19
athlon xp64 3000
I have installed the driver and fglrx is loading.
I figure there is something wrong with my xorg.conf because I just get some 150 fps in glxgears.
fgl_glxgears says:
Using GLX_SGIX_pbuffer
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 33
Current serial number in output stream: 33
My xorgconf is
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.
# created by KGamma
Identifier "My Monitor"
HorizSync 31.5 - 57.0
VertRefresh 50.0 - 70.0
Gamma 2.15
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
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"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
#Section "Device"
#VideoRam 65536
# Insert Clocks lines here if appropriate
#Identifier "** ATI Radeon (generic) [radeon]"
#Driver "radeon"
#EndSection
#Section "Device"
# Identifier "aticonfig-Device[0]"
# Driver "fglrx"
#EndSection
Section "Screen"
Identifier "Screen 1"
Device "aticonfig-Device[0]"
Monitor "My Monitor"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Any suggestions?
|
|
|
09-28-2007, 11:56 AM
|
#2
|
LQ Guru
Registered: Nov 2006
Location: Belgium
Distribution: Ubuntu 11.04, Debian testing
Posts: 5,019
Rep: 
|
Check the output of
glxinfo | grep direct
If it's no, that would explain the slowness.
You may have to disable composite to get direct rendering to work. Add these lines at the bottom of xorg.conf:
Section "Extensions"
Option "Composite" "Disable"
EndSection
Then restart X (Ctrl + Alt + backspace)
If it still doesn't give you more fps, then I can only suppose that the driver wasn't installed correctly.
Oh yes, and where is the modules section in your xorq.conf? That may be another explanation.
Last edited by jay73; 09-28-2007 at 11:58 AM.
|
|
|
09-28-2007, 12:19 PM
|
#3
|
Member
Registered: Sep 2004
Location: Jakobstad Finland
Distribution: Slackware 10
Posts: 42
Original Poster
Rep:
|
How should the modules section look like? I have run aticonfig --initial but it just reports
Found fglrx primary device section
Nothing to do, terminating.
should I run aticonfig in a specific way or are there any other scripts for configuring xorg.conf?
|
|
|
09-28-2007, 12:26 PM
|
#4
|
LQ Guru
Registered: Nov 2006
Location: Belgium
Distribution: Ubuntu 11.04, Debian testing
Posts: 5,019
Rep: 
|
Well, I'm afraid that ATI is notorious for its lousy Linux support. Just doing aticonfig should have been enough but it's quite often that people still have to edit xorg.conf manually. As for the modules section, it should be something like this:
Quote:
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection
|
By the way, you can often find out more particulars on any errors by doing
cat /var/log/Xorg.0.log.
Last edited by jay73; 09-28-2007 at 12:27 PM.
|
|
|
All times are GMT -5. The time now is 10:05 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|