LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-14-2007, 10:35 PM   #1
corbintechboy
Member
 
Registered: Sep 2003
Location: Kentucky
Posts: 480
Blog Entries: 1

Rep: Reputation: 51
ATI radeon probs


Hello,

I am using slack 10.2 with stock kernel. I installed a Radeon 9250 and have played with it until I got over the black screen. It is a PCI card and I have read here on these forums the average FPS is around 500, I am nowhere near that. Here is results from glxgears running small:

root@darkstar:~# glxgears
885 frames in 5.0 seconds = 177.000 FPS
700 frames in 5.0 seconds = 140.000 FPS
849 frames in 5.0 seconds = 169.800 FPS
700 frames in 5.0 seconds = 140.000 FPS
840 frames in 5.0 seconds = 168.000 FPS

Here is copy of 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.
# **********************************************************************
#
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 font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"

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)
# 
# 

    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"

# 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><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# 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	"kbd"

# 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"    "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"

    Option "XkbRules"	"xorg"
    Option "XkbModel"	"pc101"
    Option "XkbLayout"	"us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "IMPS/2"
    Option "Device"      "/dev/mouse"
    Option "ZAxisMapping"   "4 5"
# Mouse-speed setting for PS/2 mouse.

#    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)

#    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 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

Section "Monitor"

    Identifier  "My 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   31.5 - 57.0

#    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.

    VertRefresh 50-90

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
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "ATI"
    Driver      "fglrx"
    Option      "EnablePageFlip" "on"
    Option      "AGPMode" "4"
    Option      "VBERestore"    "true"
    Option      "AGPFastWrite"  "true"
    VendorName  "ATI Technologies Inc"
    BoardName   "RV280 [Radeon 9200 PRO]
#    BusID       "PCI:1:0: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"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "ATI"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1024x768"
        ViewPort    0 0
    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  "Simple 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.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "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".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Section "DRI"
    Mode 0666
EndSection
I am loading the fglrx driver before I startx. Anyone have any Ideas?

Last edited by corbintechboy; 07-14-2007 at 10:36 PM.
 
Old 07-15-2007, 02:46 AM   #2
veritas
Member
 
Registered: Aug 2003
Location: Dallas,TX
Distribution: Ubuntu Server, Slackware, Red Hat 6.1
Posts: 241

Rep: Reputation: 30
You are probably getting low frame rate because you don't have hardware acceleration working. Type
Code:
glrxinfo | grep rendering
If it says no, then you don't. But according to this http://ati.amd.com/products/catalyst/linux.html#2 they don't support PCI cards, just PCI express and AGP. I wasted a lot of time trying to get fglrx working with my PCI 9200SE, but I never could get acceleration on. Maybe they added PCI support since my last attempt? Your best bet would be to use the open source 'radeon' driver instead of fglrx
 
Old 07-15-2007, 03:16 AM   #3
corbintechboy
Member
 
Registered: Sep 2003
Location: Kentucky
Posts: 480
Blog Entries: 1

Original Poster
Rep: Reputation: 51
Quote:
Originally Posted by veritas
You are probably getting low frame rate because you don't have hardware acceleration working. Type
Code:
glrxinfo | grep rendering
If it says no, then you don't. But according to this http://ati.amd.com/products/catalyst/linux.html#2 they don't support PCI cards, just PCI express and AGP. I wasted a lot of time trying to get fglrx working with my PCI 9200SE, but I never could get acceleration on. Maybe they added PCI support since my last attempt? Your best bet would be to use the open source 'radeon' driver instead of fglrx

Thanks for the reply. I did not read where the PCI is not supported. I used to have a radeon 7000 that worked on the PCI with direct rendering. Oh, well, I guess all hope is lost for anything 3d.

I have a NVidia FX5500 AGP that works fine in linux but I am afraid the card might be going bad, I had some tearing in games in windows, in linux it works fine. A friend told me to watch that if it went it could take other hardware with it. Even though it works in linux that scares me. Is there a good howto on how to get dri on the radeon driver? I enabled it and still no dri.

Thanks for the help!
 
Old 07-15-2007, 07:54 AM   #4
hutyerah
Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware
Posts: 40

Rep: Reputation: 16
A good place for DRI troubleshooting is this article... funnily enough
 
Old 07-20-2007, 10:54 AM   #5
amd0freak
LQ Newbie
 
Registered: Jul 2007
Distribution: slackwarez 12.0
Posts: 24

Rep: Reputation: 15
I feel bad for you. ATI linux support is not that good. I am sorry i cannot help. have you resolved this issue?
 
Old 07-24-2007, 05:24 AM   #6
sanitynotvanity
Member
 
Registered: Jul 2007
Location: UK
Distribution: LFS 6.8, Android, Ubuntu 10.10, XP, 7 (HB,HP,Ultimate)
Posts: 41

Rep: Reputation: 15
hi corbintechboy,

i am by far a newbie with linux, so take my advice with a 'pinch of salt' however - i would suggest that you check that 'vertical Sync' is turned on in windows.

i suspect that you are merely experiencing frame tearing due to the frame rate of your graphics card being faster that the refresh rate of your monitor. ( fingers crossed i got that bit right). either way, its most common in LCD/TFT screen monitors.

so try that.
 
Old 07-26-2007, 05:58 PM   #7
the3dfxdude
Member
 
Registered: May 2007
Posts: 563

Rep: Reputation: 239Reputation: 239Reputation: 239
Guys,

Even IF ATI added PCI support to fglrx in the future, they no longer support 9250. Use DRI/R200. Your PCI Radeon 7000 only could have worked with DRI anyway (fglrx never supported 7000).
 
Old 08-15-2007, 03:21 AM   #8
Ntweat
LQ Newbie
 
Registered: Aug 2007
Posts: 1

Rep: Reputation: 0
well i was migrating from windows to Ubuntu 7.04 .... I have ATI Radeon 9250 128 MB PCI card... but on trying to install Ubuntu the xserver dint get loaded so i installed it using my on board intel graaphic accelarator... it worked perfectly fine... then i installed envy driver for ati but still no use as the xserver wont start....

Please help as i realy like using my graphics card....


This is the config of my system:

IBM Pc

Intel 915 motherboard

Intel media graphic accelarator

PCI ATI Radeon graphic 9250

736 MB RAM
 
Old 08-16-2007, 12:58 AM   #9
the3dfxdude
Member
 
Registered: May 2007
Posts: 563

Rep: Reputation: 239Reputation: 239Reputation: 239
Quote:
Originally Posted by Ntweat View Post
then i installed envy driver for ati but still no use as the xserver wont start....
Do you mean every driver for ati? Well as for fglrx, they don't support your chip anymore, and fglrx doesn't support pci either from what I understand. You need to install r200/DRI.
 
Old 08-16-2007, 10:57 PM   #10
markmlinux
LQ Newbie
 
Registered: Jun 2007
Location: San Diego
Distribution: Slackware 11.0
Posts: 13

Rep: Reputation: 0
Hello,

I just ... and finally got my AMD/ATI Radeon Xpress 200M - fglrx driver working. Don't ask me what mode.
I used the new 28July07 ati- driver, set up a tmpfs (formerly module SHM) its in my 2.6.21.5-smp kernel for my uniprocessor but Intel EMT64 Toshiba A135-S2376 which has the M520 1.6Ghz Intel proc. Pay close attention to the readme's on the AMD/ATI site. There are software configuration prerequisites as well. Oh KDE is working fine - haven't tried the reboot, yet.
Basically also let the ati driver install having a fresh X11 setup on the drive. Then run aticonfig --initial but try to run
aticonfig --uninstall to be on the save side. I also set the VideoRam to 153600(Mbytes) - 4 Mb for Mplayer which previous inspection of /var/log/Xorg.logs(.8) gave. Also lcpci -v | more, scanpci -v ... more info.

With the fresh xorg.conf and aticonfig (new! replacing fglrxconfig or such) and aticonfig --unistall (do a aticonfig --help)
then do a aticonfig --initial. I used the statement 'X :0' to help in troubleshooting the mouse problem. The X will not load until the mouse driver was correct. Then of course xwmconfig to pick my windowing system of choice. The driver balnked the screen and was real slow to come up - but finally whala! :> :> :>

I also am using the SMP Kernel as I finally ran into the unsure statements that this was correct for the M520 Processor as well (uniprocessor) - I was surprised to see the Hyperthreading Module in my new ./config ~~~~ not happy I missed this with the non-smp ./config.



I still want to use the synaptics driver with synclient and syndaemon.
Anybody know how to load those with X11 ? Xorg.conf.
 
Old 08-17-2007, 10:35 AM   #11
the3dfxdude
Member
 
Registered: May 2007
Posts: 563

Rep: Reputation: 239Reputation: 239Reputation: 239
Quote:
Originally Posted by markmlinux View Post
Hello,

I just ... and finally got my AMD/ATI Radeon Xpress 200M - fglrx driver working.
Your the first person I've heard that got Xpress 200M working with fglrx. Three weeks ago, I got my Xpress 200M working finally..... with the r300/DRI driver
 
  


Reply


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
2 probs on etch: orinoco wlan and ati radeon new2deb Linux - Hardware 3 06-07-2007 01:53 PM
ATI Driver Installation probs in SuSE 10.0 with Radeon 9600 Fluux Linux - Hardware 2 12-18-2005 01:16 AM
ATI Radeon Probs Gitzo645 Mandriva 2 02-08-2005 11:15 AM
hardware probs: ati radeon 9600 and sb audigy mokojin SUSE / openSUSE 5 02-07-2005 10:39 AM
redhat 8 and ATI Radeon agp 320m (aka Radeon Mobility U1) nelsonnery Linux - Hardware 11 11-06-2003 06:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:49 AM.

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