LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Password
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.

Notices


Reply
  Search this Thread
Old 05-19-2004, 12:07 AM   #16
jburns131
LQ Newbie
 
Registered: May 2004
Posts: 1

Rep: Reputation: 0

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.
 
Old 05-24-2004, 05:24 PM   #17
Zurg
LQ Newbie
 
Registered: May 2004
Location: Germany / Weserbergland
Distribution: Mandrake Official 10.0
Posts: 4

Rep: Reputation: 0
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
 
Old 05-26-2004, 12:46 PM   #18
C++Boar
Member
 
Registered: Mar 2004
Location: Denmark
Distribution: Gentoo
Posts: 68

Original Poster
Rep: Reputation: 16
16452 frames in 5.0 seconds = 3290.400 FPS
(when window is full visible - default size (in screen 1024*768 I think) )

AMD XP3200+ with ATI 9600XT so I guess have something like 9800 Pro ?
 
Old 05-26-2004, 03:16 PM   #19
Biased turkey
Member
 
Registered: Jan 2002
Location: Canada
Distribution: redhat7.2
Posts: 169

Rep: Reputation: 30
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.
 
Old 05-27-2004, 01:47 PM   #20
Biased turkey
Member
 
Registered: Jan 2002
Location: Canada
Distribution: redhat7.2
Posts: 169

Rep: Reputation: 30
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.
 
Old 05-29-2004, 07:52 AM   #21
/usr/carlito
LQ Newbie
 
Registered: May 2004
Location: belgium
Distribution: 2.6.10-gentoo-r6
Posts: 17

Rep: Reputation: 0
You're a life saver C++BOAR! Got my 9800pro running fine under mandrake 10.
Great guide!
 
Old 05-30-2004, 06:36 PM   #22
Zurg
LQ Newbie
 
Registered: May 2004
Location: Germany / Weserbergland
Distribution: Mandrake Official 10.0
Posts: 4

Rep: Reputation: 0
There is no longer need for so an complex installation to get your ATI running under MDK 10 !

Download the new fglrx-4.3.0-3.9.0.i386.rpm from ATI

Install it with rpm -Uhv --force fglrx-4.3.0-3.9.0.i386.rpm

When running fglrxconfig say to "use external AGP_Gart" "y"

At last edit
/etc/modprobe.conf
"install fglrx /sbin/modprobe --ignore-install fglrx && { /sbin/modprobe nvidia_agp; /bin/true; }"

/etc/rc.d/rc.modules
"/sbin/modprobe fglrx"

reboot your system (because with init 5 the modprobe.conf & rc.modules will not load new)
 
Old 06-01-2004, 04:38 PM   #23
92fs
LQ Newbie
 
Registered: Jun 2004
Posts: 1

Rep: Reputation: 0
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.
 
Old 06-01-2004, 06:28 PM   #24
Tabby
LQ Newbie
 
Registered: Jun 2004
Distribution: Mandrakelinux 10.0
Posts: 3

Rep: Reputation: 0
Quote:
Originally posted by Zurg
*snipped instructions*
Thank you VERY much! These instructions worked PERFECTLY for me, much appriciated!!
 
Old 06-02-2004, 03:54 PM   #25
fabre
Member
 
Registered: Aug 2003
Location: Vancouver
Distribution: Debian Sid Amd64
Posts: 87

Rep: Reputation: 15
Followed Zurg method

and I have the feeling it didn't install properly

1840 frames in 5.0 seconds = 368.000 FPS in glxgears

With a Radeon 9800 pro

/Edit

Not right for sure

fglrxinfo says it's the mesa driver

Just tried the the ATI way didn't work either.

Anyone got a Radeon 9800 pro to work on a A7N8X-X?
a part from the resolution and refresh rate I used all defaults settings in fglrxconfig.



Last edited by fabre; 06-02-2004 at 08:43 PM.
 
Old 06-02-2004, 11:29 PM   #26
C++Boar
Member
 
Registered: Mar 2004
Location: Denmark
Distribution: Gentoo
Posts: 68

Original Poster
Rep: Reputation: 16
MESA is software rendering, so it is not installed.

C++Boar
 
Old 06-03-2004, 01:57 AM   #27
zupermanz
Member
 
Registered: Jun 2004
Distribution: mdk10
Posts: 35

Rep: Reputation: 15
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!
 
Old 06-03-2004, 02:23 AM   #28
fabre
Member
 
Registered: Aug 2003
Location: Vancouver
Distribution: Debian Sid Amd64
Posts: 87

Rep: Reputation: 15
Sorry I have just been using mandrake for a day now so I am not sure what you meant.

This what I get when I do a: fglrxinfo

display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4

I starting to wonder If I am not doing something wrong in in the fglrxconfig

A part from the agp gart are there other settings I should change from their default in fglrxconfig?
 
Old 06-03-2004, 10:44 AM   #29
C++Boar
Member
 
Registered: Mar 2004
Location: Denmark
Distribution: Gentoo
Posts: 68

Original Poster
Rep: Reputation: 16
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)

You should check what you have the following.

/etc/modprobe.conf
"install fglrx /sbin/modprobe --ignore-install fglrx && { /sbin/modprobe nvidia_agp; /bin/true; }"

/etc/rc.d/rc.modules
"/sbin/modprobe fglrx"

Also check your /etc/X11/XF86Config-4 to verify that you have
Option "UseInternalAGPGART" "no"

and after changes reboot. If that does not work start over.

C++Boar
 
Old 06-03-2004, 11:10 AM   #30
fabre
Member
 
Registered: Aug 2003
Location: Vancouver
Distribution: Debian Sid Amd64
Posts: 87

Rep: Reputation: 15
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).
#

# FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
# FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

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"

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

# Option "XkbDisable"

Option "XkbRules" "xfree86"
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 "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"

# 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 XF86Config 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 "Monitor0"
HorizSync 31.5 - 91.1
VertRefresh 60 - 100
Option "DPMS"

# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync

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

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
BusID "PCI:2:0:0" # vendor=1002, device=4e48
Screen 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 "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

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

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

EndSection

### EOF ###



Then the modprobe.conf

alias eth1 tulip
alias eth0 forcedeth
alias sound-slot-0 snd-intel8x0
install snd-intel8x0 /sbin/modprobe --first-time --ignore-install snd-intel8x0 && { /sbin/modprobe snd-pcm-oss; /bin/true; }
install usb-interface /sbin/modprobe usb-ohci; /sbin/modprobe ehci-hcd; /bin/true
remove snd-intel8x0 { /sbin/modprobe -r snd-pcm-oss; } ; /sbin/modprobe -r --first-time --ignore-remove snd-intel8x0
install fglrx /sbin/modprobe --ignore-install fglrx && { /sbin/modprobe nvidia_agp; /bin/true; }

And finally the rc.modules file

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

/sbin/modprobe fglrx

Last edited by fabre; 06-03-2004 at 11:11 AM.
 
  


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
Slack 10.1, ATI nForce and 2.6 Zarnce Slackware 2 02-09-2005 10:25 AM
ATi Radeon on NVidia NForce Marvelloard Linux - Hardware 10 07-31-2004 06:13 AM
ATi radeon 9800pro, nforce 2 mobo, mandrake 10 cyborg_jt Linux - Hardware 1 07-12-2004 08:13 AM
nforce 2 and ati jag2000 Linux - Hardware 3 06-06-2004 10:52 AM
nforce 2 and Ati jag2000 Linux - Hardware 2 05-25-2004 02:20 PM

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

All times are GMT -5. The time now is 01:52 PM.

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