Linux - HardwareThis 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.
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.
Cant make sanse of this so here goes .............
ive installed the ATI proprietry drivers ( ati-driver-installer-8.18.6-i386.run ) onto my machine which has a Saphire ATI 9600Pro but i just cant get glxgears to get me an FPS above 150 !! whats not making sense is that when i had FC3 on this same machine some time ago, the proprietry drivers then installed without a problem ( ati-driver-installer-8.16.20-i386.run ) and Doom3 ran beautifully.
is there anything i should know about FC4 and ATI?? any guidence would really help me get off my feet!
Type fglrxinfo in a terminal window. Chances are it's still using the mesa drivers. You have to look through the error log made during the driver install to see if the driver actually was installed correctly. If it is, make sure the xorg.conf file is using the fglrx driver. If none of this works, then search through the forums. ATI can't seem to make a driver for linux that works right.
thanx, illl try that out once im home but for the moment i was wondering maby the sollution is to reinsall the drivers fresh ! in that case how do i uninstall the original ati drivers so i can install the propritiery ones again ?
well, ive checked and found that the ATI drivers dint install cos the Mesa drivers are still the defaults. Ive checked the xorg.conf file a few times but i still cant figure out what to chenge in it so heres a copy.
thanx for any help mate.
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# 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 Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
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)
#
# 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).
#
# 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><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).
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"
# 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" "pc102"
# 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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# 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
# installed.
# 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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
# 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 "Server 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.
Screen "Screen0"
# 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".
The xorg.conf file you gave me is fine, so the drivers didn't install right. To uninstall, type rpm -e fglrx as root. Installing is a bit more complex.
Become root using su.
Type rpm -ivh --force name of the driver rpm
Type init 3
(init 3 will bring you to console. In the next steps the actual driver is made, and it won't work right if you are in graphical mode)
Type cd /lib/modules/fglrx/build_mod
Type sh make.sh
Type cd /lib/modules/fglrx
Type sh make_install.sh
Type modprobe fglrx
Type lsmod | grep fglrx
(This will see if the driver has loaded)
Type init 5
(This should bring you back into graphical mode)
Open up a terminal window and type fglrxinfo
It should say a whole lot about ATI. The forum I got all this information from can be found here.
Well, to say more abt ATI, that too doesnt work. when i started doing it this is what i got
[root@localhost build_mod]# ./make.sh
ATI module generator V 2.0
==========================
initializing...
kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
[root@localhost build_mod]#
it just returns without doing nothing. i checked and that "linux" folder doesnt seem to exist !!
any suggestions mate ?
This is why I don't like ATI anymore. A little backround as to how this driver works. The installer creates what's called a kernel module. All kernel modules require a compiled kernel source tree in order to work. If you happen to have red hat enterprise or SuSe, then they have already done this work for you. Since you use FC4, no precompiled modules exist in the package, so it says kernel module mismatch.
If you don't have Suse or red hat enterprise, it compiles a module specifically for your system. If it can't find a compiled kernel source tree, then it can't compile and fails. This explains the no kernel module build environment error.
I think this is why people are so mixed on the driver. Some can make it fine right away, but others struggle for reasons no one can figure out.
You pretty much have two options. The first is to install the kernel source, then compile it. This takes awhile, and it will take over 300 mb (for ubuntu anyway). Also, it's a little complicated. the second option is to look for a precompiled module for FC4. Fortunately, I found a place that has that.
This webstie has precompiled modules for ATI under Fedora. Follow the instructions and it should work. Before you can use yum (which is what the driver is installed with) you need to configure yum. That is also on the website here.
I apologize for assuming you had the source installed, since most people do not.
I'm having similar problems with my 9500PRO and the prop. ATI drivers in that fglrxinfo reports mesa drivers. However, I'm using ubuntu and couldn't follow once the discussion reached 'rpm'...
The only thing the install seems to have done is add an ATI icon in the Applications menu that does nothing but a system sound.
How would the steps in post 5 differ for an ubuntu bloke, and where is a good place I could download the source from? The ATI site doesn't seem to have it available.
Hold on! If you're using ubuntu, then there already is a precompiled fglrx module for you. Go into synaptic package manager, and look for the package xorg-driver-fglrx. Install it, edit the xorg.conf file (changing the driver from radeon to fglrx), restart, and you should have the drivers installed.
hmm, u know what doesnt make sense here, why was it that the ATI drivers installed properly on Fedira core 3 and dint require a compiled module ? is it simply ATI not keeping up with the times ? or is it a lacking on fedora core 4's part ?
i was visiting this website : http://forum.americasarmy.com/viewtopic.php?t=181470 and i came accross someone saying that the one can install the "kernal-devel" rpm using yum and then the ATI drivers will be able to install on FC4. do you think it is possible to do that ? if so, what would be the yup command ?
I would go ahead and try it. I think the kernel devel package just gives you the non-proprietary source code, but I know that some programs require you to have devel packages in order to compile them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.