MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
I'm realy excited that you have taken the time to condense this information. I almost have the same setup as you, but I am using grub instead of lilo. I made it to the part where I have to "edit \etc\lilo.conf so your new kernel is the one that is booted with." Is there any way you might be able to give directions on how to do that with grub. I've been looking through the grub docs, and I just feel lost. I'm a new linux user also, and I'm not sure how to find out what the new kernel is named. If you or anyone else out there could help out I realy appritiate it.
Many thanks C+ +Boar & Erol you helped me with your Threads
Instead of radeon-20040208.i386.tar.bz2 i used the newer radeon-20040524.i386.tar.bz2.
I don´t know what you mean with "this might give a problem with libGL.so.1.2 " , with the newer version i don´t get any error message.
The only error message i´ve got was if installing the fglrx-4.3.0-3.7.6.i386.rpm driver
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2246: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2264: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2271: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2278: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2287: warning: initialization from incompatible pointer type
LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
but it´s running.
glxgears
18778 frames in 5.0second = 3756 FPS its good ?
System:
Shuttle SN45G / AMD XP 3400+ (2500+) / Radeon 9700 Pro
I don't want to hijack the thread but I have the following situation:
Aopen Nforce2 mobo, Radeon 8500 LE and was having no 3D acceleration problem with Fedora core1 2.4 Kernel.
Just installed fedora, Nforce2 drivers, ATI RPM drvers, run fglrxconfif and voila.
Last weekend I installed mandrake10.0 ( from the DVD enclosed with Linux Format magazine ) and I noticed the improvements brought to the Nforce2 chipset using the new 2.6 Kernel: the NIC chip and onboard sound detected and running out of the box. But no 3d acceleration with the Rad8500 after installing the ATI RPMs drivers.
I tried with intarnal or external agpgart but it doesn't make any difference.
So my question is: Do I have in order to have my Rad8500 working with Mandrake 10 follow the ( well detailed ) procedure suggested by C++Boar using on of the r200-xxxxxxxx-linux.i386.tar.bz2 file instead of a radeon-xxxxxx-linux.i386.tar.bz2 file at http://www.freedesktop.org/~dri/snapshots/ ?
I'm following that post with the greatest attention because I ordered a 9600XT and should receive it in a few days.
tia for any suggestion.
I'm surprised the Rage3d.com that is supposed to be the "official Linux ATI forum" doesn't has any post about Mandrake10 and ATI graphic boards.
Yesterday evening I tried the whole process for my rad8500 using the DRI r20.......i386.tar.bz2 but that didn't work.
I just saw that ATI 3.9.0 rpm driver was issued 2 days ago. I'll have a swirl at it.
C++Boar, excellent guide! I'm getting 13841 frames in 5.0 seconds = 2768.200 FPS in glxgears and 2474 frames in 5.0 seconds = 494.800 FPS in fgl_glxgears. Thanks for your help.
i have an ati9600 pro but i am not able to install the drivers
I have tried rpm -Uhv --force fglrx-4.3.0-3.9.0.i386.rpm (downloaded the newest)
but when i ./make.sh i get an error message (dont have permission)...why?
Please help!
zupermanz - are you root when compilering ? (su before compilering?) - what errors are shown ?
fabre - you do not have working hardware-accelration, but a software driver (MESA).
So your install has failed ... or you have changed some hardwaresettings since your install (if you use mandrake 10CE)
Aplology for the long post but I am really starting to loose my mind
Please have a look and see what I did wrong, Thank you
I am using the Mdk 10.0 Official and I have a nforce 2 board
Here is my XF86Config
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.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.
# **********************************************************************
# **********************************************************************
# 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"
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 "Keyboard"
# 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"
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".
#!/bin/sh
# (c) MandrakeSoft, Chmouel Boudjnah <chmouel@mandrakesoft.com>
# $Id: rc.modules,v 1.3 2003/07/21 11:46:19 flepied Exp $
# description: launch modules specified in /etc/modules inspired by a
# Debian idea.
if modprobe -V 2> /dev/null | grep -q -m 1 module-init-tools; then
MODULES=/etc/modprobe.preload
else
MODULES=/etc/modules
fi
[ -f $MODULES ] || exit 0
# Loop over every line in /etc/modules.
(cat $MODULES; echo) | while read module args
do
case "$module" in
\#*|"") continue ;;
esac
initlog -s "Loading module: $module"
modprobe $module $args >/dev/null 2>&1
done
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.