Go Back   Rage3D » Rage3D Discussion Area » Computing Forums » Operating Systems » Linux
Rage3D Subscribe Register FAQ Members List Calendar Mark Forums Read

Linux Forum to discuss the popular Open Source operating system, plus other *NIX derivatives. Discussions about AMD Catalyst drivers can be had in the relevant subforum.

"
Reply
 
Thread Tools Display Modes
Old Dec 11, 2003, 03:28 AM   #1
Advertisement (Guests Only)

Login or Register to remove this ad
Wolfgang67
Radeon HD 6770
 
Join Date: Dec 2003
Location: Cologne/germany
Posts: 58
Wolfgang67 is still being judged by the masses


Exclamation ati radeon 9800 solution for suse 9.0

OK it works!

Beast tamed

Now for all you VIA KT-400 and KT-400A users out there my solution (only valid for the original ATI drivers ver 328 from www.ati.com and for the suse 9.0 OS):

1. Do all the available "YOU-updates" including the new -144-athlon kernel WITH SOURCES, except the nVidia updates. (reboot after that)

!!!!!!!!!! FROM NOW ON DONT TOUCH YAST AND SAX2 AT ALL, don't even think about it !!!!!!!!!!!!!!!!!!

2. cd /usr/src/linux and type (as root) "make cloneconfig && make dep" (without the marks)
3. cd to the directory where you downloaded the drivers to and type (as root)
rpm -Uvh --force fglrx-glc22-4.3.0-3.2.8.i586.rpm

You will be presented the following error message, don't care about it I will explain how to overcome this:

---------------------------------------------------------------------------------------------------------------------------

Preparing... ########################################### [100%]
1:fglrx-glc22 ########################################### [100%]
*** Trying to install a precompiled kernel module.
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
*** Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.4.21-144-athlon/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
/sbin/ldconfig: File /usr/X11R6/lib/FGL.renamed.libGL.so.1.2 is too small, not c hecked.
Installed: qt3 (gcc 3.2) based control panel application
===
ATI display drivers successfully installed
please run 'fglrxconfig' now
===
XP2800:/home/wolfgang/ati #

------------------------------------------------------------------------------------------------------------------------




Now, if you cd to the path /lib/modules/fglrx/build_mod and if you do ./make.sh like requested above you will be presented the following ERROR:




-----------------------------------------------------------------------------------------------------
Error:
XFree86 drm includes at /lib/modules/2.4.21-144-athlon/build/include/../drivers/ char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
-----------------------------------------------------------------------------------------------------



Now the trick:
You might be happy that someone found that there is a fault within the ATI drivers (or suses directory structure?) and that your X-version is actually ok.



Do the following:

make.sh expects Include-files under /lib/modules/2.4.21-144-athlon/build/drivers/char/drm

But actually the sources are under /usr/src/kernel-modules/drm

So build a directory "char"under /lib/modules/2.4.21-144-athlon/build/drivers
and then do a symbolic link from drm to /usr/src/kernel-modules/drm:

cd /lib/modules/2.4.21-144-athlon/build/drivers
md char
cd char
ln -s /usr/src/kernel-modules/drm

After that the files are visible under
/lib/modules/2.4.21-144-athlon/build/drivers/char/drm




It's not yet over!




cd to /lib/modules/fglrx/build_mod and edit the file agpgart_be.c
Do a search for the string "8377" and change the following section:

{ PCI_DEVICE_ID_VIA_8377_0,
PCI_VENDOR_ID_VIA,
VIA_APOLLO_KT400,
"Via",
"Apollo KT400",
via_kt400_setup }, // AGP v2 !!! (was via_generic_setup before)!!!



Now do:

./make.sh
cd /lib/modules/fglrx
./make_install.sh


The last step is to run fglrxconfig.

Just make sure that you use the internal agpgart!!!

Do another reboot, just restarting X didn't cut it for me...

After this installation my machine worked even with AGP 8x enabled in Bios. Had a tough fight though
for over ten days and would like to thank the thousand people posting here and in other forums for this or that little hint which altogether helped me with that issue. I get some 22.000 - 23.000 fps in glxgears now.

One last: After installation don't try to run fglrxinfo or glxgears as root within a console, just use your standard user account or you will otherwise be presented with this error:

---------------------------------------------------------------------
xp-2800:/home/wolfgang # glxgears
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: couldn't open display (null)
---------------------------------------------------------------------


Best from cologne

Wolfgang

Last edited by Wolfgang67 : Dec 11, 2003 at 06:38 AM.
Wolfgang67 is offline   Reply With Quote
Old Dec 11, 2003, 07:07 AM   #2
Kombatant
K to the max!™
 
Join Date: Nov 2002
Location: Greece Nikaia, Greece
Posts: 16,693
Kombatant knows why the caged bird singsKombatant knows why the caged bird singsKombatant knows why the caged bird singsKombatant knows why the caged bird singsKombatant knows why the caged bird sings


Subscriber
Default

Danke schoen I am sure SuSe users will find this most helpful
__________________
There is no spoon...
Rage3D // Digital Lair // Twitter
Kombatant is online now   Reply With Quote
Old Dec 11, 2003, 07:41 AM   #3
WhO_KnOwS
The lurker mod
 
Join Date: Dec 2002
Location: Slovenia Slovenia, Europe
Posts: 3,227
WhO_KnOwS is still being judged by the masses


Default

Would you mind if I use this info in my ATI Linux HowTo? Your name would be of course added to the credits list.
__________________
  • Intel Core 2 Quad Q6600 @ 3Ghz
  • GigaByte P35-DS4
  • 4 GB OCZ Gold 800Mhz DDR2 Dual Channel
  • XFX GeForce 280 GTX XXX
  • Dell 2407WFP monitor
  • CoolerMaster Cosmos S case


Other hardware: MacBook Pro 2.53GHz 13", Xbox360, iPhone 3GS 32GB
WhO_KnOwS is offline   Reply With Quote
Advertisement (Guests Only)
Login or Register to remove this ad
Old Dec 11, 2003, 07:55 AM   #4
Wolfgang67
Radeon HD 6770
 
Join Date: Dec 2003
Location: Cologne/germany
Posts: 58
Wolfgang67 is still being judged by the masses


Default

Thanks kombatant hopefully it will help others
not to waste so much time as I did



Who_Knows, do whatever you want with it.

Consider it as being licensed under GPL LOL

Of course you should do some lecturing, because I scribbled it down rather hastily and forgot i.e to mention that some commands need to be done as root while others not...


Best from cologne
Wolfgang67 is offline   Reply With Quote
Old Dec 11, 2003, 11:38 AM   #5
WhO_KnOwS
The lurker mod
 
Join Date: Dec 2002
Location: Slovenia Slovenia, Europe
Posts: 3,227
WhO_KnOwS is still being judged by the masses


Default

Just so you know, I will use only the VIA part. That's one thing my HowTo is still missing. What name would you be like to listed under?
__________________
  • Intel Core 2 Quad Q6600 @ 3Ghz
  • GigaByte P35-DS4
  • 4 GB OCZ Gold 800Mhz DDR2 Dual Channel
  • XFX GeForce 280 GTX XXX
  • Dell 2407WFP monitor
  • CoolerMaster Cosmos S case


Other hardware: MacBook Pro 2.53GHz 13", Xbox360, iPhone 3GS 32GB
WhO_KnOwS is offline   Reply With Quote
Old Dec 11, 2003, 12:18 PM   #6
Wolfgang67
Radeon HD 6770
 
Join Date: Dec 2003
Location: Cologne/germany
Posts: 58
Wolfgang67 is still being judged by the masses


Default

I think the most important part is the symbolic link to the right directory (though suse 9 specific)
Without that people will be stuck with the suse rpms and these don't come with the fglrx tools.
(Besides that I couldn't get them to work)


But do what you want... what name? Simply "Wolfgang" I would say, or if you want: Wolfgang Stommel


Best from cologne

Wolfgang
Wolfgang67 is offline   Reply With Quote
Old Jan 7, 2004, 05:35 AM   #7
vero
Newbie
 
Join Date: Jan 2004
Posts: 1
vero is still being judged by the masses


Default fonts for ati radeon 9200 with suse 9.0

Hi everybody,

I recently installed the drivers for ati radeon 9200 with suse 9.0 (thanks to Wolfgang67).
Now it seems that things work but I have only very bad fonts !
I tried to install others using yast. Yast tells me that I have a lot of fonts intalled but I cannot use them !
Does anyone kown how I can manage ?

Below is my XF86Config-4 file.

Also, how can I test if the 3D acceleration works ?

# 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.
#
# 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" # 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"
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/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/CID"
FontPath "/usr/X11R6/lib/X11/fonts/encodings"
FontPath "/usr/X11R6/lib/X11/fonts/truetype"
FontPath "/usr/X11R6/lib/X11/fonts/util"

# 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/100dpi/:unscaled"
# 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" "fr"

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-82
VertRefresh 58-75
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" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
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" "0x06419064"
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" "1"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=5c61
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 "1400x1050" "1280x1024" "1024x768" "800x600"
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 ###
vero is offline   Reply With Quote
Old Jan 8, 2004, 08:27 AM   #8
Mythos
Don't worry - Be happy!
 
Join Date: Oct 2003
Location: Crete, Hellas
Posts: 1,909
Mythos is still being judged by the masses


Default

To see if you have 3d acceleration, just run glxinfo.
If you see something about direct rendering: Yes, then everythng should be ok.
About your fonts don't know if SUSE is doing something different, and since I don't use SUSE and yast can't tell you what the problem is. Maybe posting the output of fc-cache -v -f may help.
Also you should look if SUSE has the truetype fonts somewhere else than /usr/X11R6/lib/X11/fonts/truetype which your config expects...
__________________
Radeon 9500 PRO - Mobility Radeon X700 - fglrx Beta driver - Xorg head CVS
Linux Santorini 2.6.16-rc2
GCC-4.1 CVS Branch
In real life Papadakos Panagiotis
Mythos is offline   Reply With Quote
Old Jan 10, 2004, 03:17 AM   #9
tijy
Radeon HD 6850
 
Join Date: May 2001
Posts: 110
tijy is still being judged by the masses


Default

I installed the fglrx drivers to SuSE 9.0 without any mentioned compiling problems. Also with the earlier drivers, and SuSE 8.2.

Please notice that SuSE itself delivers fglrx rpm packages at: ftp://ftp.suse.com/pub/suse/i386/sup.../suse90/fglrx/.
tijy is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Radeon 9800 pro and suse 10 mike171562 Linux 1 Apr 25, 2006 08:10 PM
Yet another: 9800 pro / Suse 9.2 issues Suthern Drivers 4 Mar 7, 2005 12:19 AM
radeon 9800 pro suse 9.2 3d accel problem zamecca Drivers 4 Feb 27, 2005 09:32 AM
Radeon 9800 and SUSE 9.2 guest Linux 2 Jan 17, 2005 09:37 PM
Best 9800 Pro Cooling Solution? Alphy Radeon Tweaking, Modding, and Overclocking 0 Jun 2, 2003 12:17 PM


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



Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
All trademarks used are properties of their respective owners. Copyright ©1998-2011 Rage3D.com
Links monetized by VigLink