HOW-TO: ATI fglrx driver 8.16.20

[mlomker]

The fglrx driver supports Radeon 8500+ and the X-series cards. Note that the 9100 IGP cards and the Mobility 9000 M7 LW (laptop chipset) are not supported for 3D.

When running the dpkg-reconfigure commands you can accept the defaults whenever you aren't sure.

Remove the 8.16.20 driver if it is already installed (not working)


sudo apt-get remove xorg-driver-fglrx
sudo apt-get remove linux-restricted-modules-$(uname -r)
sudo dpkg-reconfigure xserver-xorg #Select the ATI driver


Reboot--necessary to get the restricted modules out of memory.


(Re)Installing the driver

All Platforms:

sudo apt-get install xorg-driver-fglrx
sudo apt-get install linux-restricted-modules-$(uname -r) #Okay if it is already installed
sudo dpkg-reconfigure xserver-xorg #Select the fglrx driver


64-bit users:

You have to downgrade to an older version of libdri.a due to an incompatilbity with the ATI drivers. Download it here (http://mail3.mpr.org/mlomker/libdri.a.gz).

Change to download directory:

gunzip libdri.a.gz
sudo cp /usr/X11R6/lib/modules/extensions/libdri.a libdri.a.old
sudo cp libdri.a /usr/X11R6/lib/modules/extensions/


If you wish to revert to any non-fglrx driver you will need to copy the libdri.a.old file back over the fglrx version.

Reboot.


Confirm that it works

mlomker@mlomkernote:/$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)


Troubleshooting

Resolution Problem:
The driver is installed but you are at 1024x768. The installer may have defaulted to that setting--I know that it didn't prompt me during my install. Either manually edit the xorg.conf file (if you know how) using nano /etc/X11/xorg.conf or run sudo dpkg-reconfigure xserver-xorg.

If you have updated the xorg.conf but your widescreen display is still stuck at 1024x768 then it is probably the bug in the 8.16.20 driver that was fixed in 8.18.6. That driver is harder to install but I have a how-to (http://ubuntuforums.org/showthread.php?p=423589).

General Troubleshooting:
You can look through the /var/log/Xorg.0.log and kern.log file for troubleshooting most problems.

xf86_EINVAL and MTRR errors (http://ubuntuforums.org/showthread.php?t=115104)


64-bit users:

You may get this error message when you go to restart:


Duplicate symbol rol_long in /usr/X11R6/lib/modules/drivers/fglrx_drv.o
Also defined in /usr/X11R6/lib/modules/linux/libint10.a


You can fix this by editing your xorg.conf file and commenting out the libint10.a line:


sudo nano /etc/X11/xorg.conf



Section "Module"
# Load "int10"
EndSection


Ctrl-W, Y, Enter to save.

[Olav]

The fglrx driver supports Radeon 8500+ and the X-series cards.

Installing the driver that comes with Breezy:


sudo apt-get install fglrx-control
sudo apt-get install xorg-driver-fglrx
sudo apt-get install linux-restricted-modules-2.6.12
sudo fglrxconfig


Okay, using that at least I get functional TV output [EDIT to be clear: I mean watching TV from my TV-card in a program called TVTime]. This was my second biggest problem. The biggest-biggest problem was all the terrible random crashes and hangups I got with both "ati" and "radeon" standard drivers. That seems to be fixed now, too.

But 3D is terribly slow. I tried glxgears of course, it's beyond bad. Just to see how a game would perform I installed Planet Penguin (was: Tux Racer). Where normally our brave and sleek Linux mascot goes whoooosh down the hill, it looks now like you have to kick the fat lazy bird forward, just half a meter at a time ;)

I guess this is the only alternative. I had the same thing going on in Hoary, and I never lost sleep over it. I was just hoping it would get better. Have to keep on doing that, or so it seems.

I blame this situation entirely on ATI, by the way.

[jecos]

Okay, using that at least I get functional TV output [EDIT to be clear: I mean watching TV from my TV-card in a program called TVTime]. This was my second biggest problem. The biggest-biggest problem was all the terrible random crashes and hangups I got with both "ati" and "radeon" standard drivers. That seems to be fixed now, too.

But 3D is terribly slow. I tried glxgears of course, it's beyond bad. Just to see how a game would perform I installed Planet Penguin (was: Tux Racer). Where normally our brave and sleek Linux mascot goes whoooosh down the hill, it looks now like you have to kick the fat lazy bird forward, just half a meter at a time ;)

I guess this is the only alternative. I had the same thing going on in Hoary, and I never lost sleep over it. I was just hoping it would get better. Have to keep on doing that, or so it seems.
I blame this situation entirely on ATI, by the way.
It would help if you would actually state what card you are using and what your xorg.conf looks like.. 'ati' and 'radeon' drivers are open source, 'fglrx' is ati's proprietary driver for radeon 8500 and up.. Its a work in progress..

[mlomker]

I guess this is the only alternative. I had the same thing going on in Hoary, and I never lost sleep over it.

What is the output of glxgears -iacknowledgethatthistoolisnotabenchmark and fglrxinfo for you? If it says ATI and you're over 1k fps then you've got what you got.

[Olav]

What is the output of glxgears -iacknowledgethatthistoolisnotabenchmark and fglrxinfo for you? If it says ATI and you're over 1k fps then you've got what you got.
Here it is:
olav@dinges:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
olav@dinges:~$
olav@dinges:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

How do I get output from that crazy glxgears command? It doesn't say a thing.

[SilverTab]

Here it is:
olav@dinges:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
olav@dinges:~$
olav@dinges:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

How do I get output from that crazy glxgears command? It doesn't say a thing.


Mesa = no good....

same problem for me...I installed via synaptic, I ran fglrxconfig....

restarted....nothing will work...

[mlomker]

OpenGL vendor string: Mesa project: www.mesa3d.org


That crazy command is what you need for glxgears to give you fps output in Breezy. How else did you test your machine? The fgl_glxgears test is ATI-specific and gives lower numbers.

If you see 'Mesa' from fglrxinfo it meant that the drivers were not installed properly and your performance is a 1/10th of what it should be. Try rerunning the apt-get commands and put a --reinstall after the 'install' keyword.

[Olav]

It would help if you would actually state what card you are using and what your xorg.conf looks like.. 'ati' and 'radeon' drivers are open source, 'fglrx' is ati's proprietary driver for radeon 8500 and up.. Its a work in progress..
I am fully aware that it is a work in progress, but unless ATI is going to really open up their chip specs and drivers I' m still going to blame them :p

Anyway, the card is (according to device Management) a Radeon R200 QL [Radeon 8500 LE], OEM Vendor: Hercules.

And this is the xorg.conf, as created by fglrxconfig, I admit I don't understand a lot of what' s in there:

# File: xorg.conf
# File generated by fglrxconfig (C) ATI Technologies, 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"

# 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 "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" "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" "pc105"
Option "XkbLayout" "en_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/input/mice"

# 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"
# === 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" "(null)"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "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" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=514c
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" "1024x768" "800x600" "640x480"
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 ###

[SilverTab]

Here's my result for glrxgears:
973 frames in 5.2 seconds = 186.916 FPS
960 frames in 5.5 seconds = 176.115 FPS


display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1


:(

[Olav]

That crazy command is what you need for glxgears to give you fps output in Breezy. How else did you test your machine?
By just running glxgears of course, without the crazy command.

The fgl_glxgears test is ATI-specific and gives lower numbers.

If you see 'Mesa' from fglrxinfo it meant that the drivers were not installed properly and your performance is a 1/10th of what it should be. Try rerunning the apt-get commands and put a --reinstall after the 'install' keyword.
Will do in a minute ;)

[mlomker]

By just running glxgears of course, without the crazy command.


Then you don't have the Breezy version of the file, unless they changed it today. I haven't been able to run an update since the formal release...the servers just time out.

[SilverTab]

Ok I just did a clean install of Ubuntu Breezy...

What would be your suggestion mlomker???
what would be the safest way to install the driver on a fresh install?

That way I know nothing I did before will cause a conflict!

[SilverTab]

Note: The EASIEST way....i.e. 8.16.20....no need for the latest version...any working version will do!

[mlomker]

Note: The EASIEST way....i.e. 8.16.20....no need for the latest version...any working version will do!

That's what the first post of this thread was for.

[Olav]

Then you don't have the Breezy version of the file, unless they changed it today. I haven't been able to run an update since the formal release...the servers just time out.
Okay, I' m back. Back to VESA, that is :(

First, there is nothing wrong with the glxgears utility. Turned out I never let it run long enough to actually come up with an FPS rate. Yes, it was that slow.

Second, I did exactly what you told me, reinstalled the packages you named. Must warn you however, there is actually no package called linux-restricted-modules-2.6.12, look:

olav@dinges:~$ apt-cache search linux-restricted-modules-2.6.12
linux-restricted-modules-2.6.12-9-386 - Non-free Linux 2.6.12 modules on 386
linux-restricted-modules-2.6.12-9-386-nvidia-legacy - Non-free Linux 2.6.12 NVIDIA legacy module on 386
linux-restricted-modules-2.6.12-9-686 - Non-free Linux 2.6.12 modules on PPro/Celeron/PII/PIII/PIVlinux-restricted-modules-2.6.12-9-686-nvidia-legacy - Non-free Linux 2.6.12 modules on PPro/Celeron/PII/PIII/PIV
linux-restricted-modules-2.6.12-9-686-smp - Non-free Linux 2.6.12 modules on PPro/Celeron/PII/PIII/PIV SMP
linux-restricted-modules-2.6.12-9-686-smp-nvidia-legacy - Non-free Linux 2.6.12 modules on PPro/Celeron/PII/PIII/PIV SMP
linux-restricted-modules-2.6.12-9-k7 - Non-free Linux 2.6.12 modules on AMD K7
linux-restricted-modules-2.6.12-9-k7-nvidia-legacy - Non-free Linux 2.6.12 modules on AMD K7
linux-restricted-modules-2.6.12-9-k7-smp - Non-free Linux 2.6.12 modules on AMD K7 SMP
linux-restricted-modules-2.6.12-9-k7-smp-nvidia-legacy - Non-free Linux 2.6.12 modules on AMD K7 SMP


Of those, I took linux-restricted-modules-2.6.12-9-k7 which also matches the kernel I' m running.

I did the fglrxconfig and shut down X with Ctrl+Alt+BS, but no joy. Then I rebooted, and it was almost like Eureka! Perfect FPS on glxgears, and the info in fglrxinfo showed ATI as vendor...

Then I was almost finished typing a message, telling you what a great guru you really are :) (I still do not doubt that)

But old problems started again, causing the screen to freeze completely except for the mouse cursor.

I have tried several things, while being logged in from another machine with ssh to keep an eye on top. And it puzzles me completely. The screen does not necessarily freeze when I'm running "heavy" stuff like glxgears. Even after a fresh reboot, after logging in and using only gedit and Firefox it goes STOP.

In fact, when that happens, X takes almost 100% CPU usage and only because I have the ssh login I can kill -9 the sucker and return more or less to normal. Took me a couple of reboots though, to test it through.

So. the only driver that seems capable of giving me video overlay for TVTime and good 3D performance, is actually preventing me from doing anything for longer than a few minutes...

I need to go to bed now. In fact, I needed to go to bed 3-4 hours ago. I appreciate all the cooperation here and I do hope that this thing gets sorted out during the weekend. This is going to be quite the learning experience :D

[SilverTab]

That's what the first post of this thread was for.


ok ill follow the instructions closely (again)...and make sure I didnt miss anything....

i'll report back!... *fingers crossed*

[Olav]

Note: The EASIEST way....i.e. 8.16.20....no need for the latest version...any working version will do!
That's what the first post of this thread was for.
Yes, and while I agree that it should work, it is not working for everybody - alas!

[souled]

How do I find out which kernel I'm running?

[Téragone]

type uname -a

[SilverTab]

nah.,..nothing will do...

I followed your exact instructions on a clean install and it wont work (and It was working in hoary :( )

Do you think the online xorg.conf tools you posted in your original thread might help?

[mlomker]

Yes, and while I agree that it should work, it is not working for everybody - alas!

Nothing works for everyone and it took weeks to refine the last how-to. The problem is that they were making major changes in Breezy up until the last minute and I wouldn't be surprised to see big updates for a bit yet. I wasn't even using Ubuntu when Hoary was released, so I'm not sure if it was the same story then.

[Jujimufu]

After going through the nightmare which was Hoary ATI drivers, this was just breezy (no pun intended, okay maybe).

Worked fine for me. Thanks!

[mlomker]

Do you think the online xorg.conf tools you posted in your original thread might help?

Sort of. The problem is that they moved the font directory in Breezy under /usr/share and I also had a problem with the int10a module loading. Every release of Ubuntu becomes less like Debian...for better or for worse.

I've heard reports that people have had luck with sudo dpkg-reconfigure xserver-xorg.

It's hard to write an ATI how-to because everybody gives me feedback about what worked and didn't and the next guy says the opposite...I get to the point where all I can do is list things to try. I only have one PC, myself, and it's a laptop with a 9700 and that's old news by desktop standards even though it's a new laptop...

[mlomker]

there is actually no package called linux-restricted-modules-2.6.12, look:


That's right. My Hoary how-to probably has gone through 50 edits. If you write a good one I'll put it in the sticky for you. ;)

But old problems started again, causing the screen to freeze completely except for the mouse cursor.

Well, I do my best helping people with the drivers but hardware problems and poorly written software...that's a taller order.

This is going to be quite the learning experience :D

For all of us! As soon as we get up to speed the six months have passed and Draper will be here.

I'll be working on the 8.18.6 drivers, myself...it fixes my misdetected resolution problem but no 3D so far. :(

[SilverTab]

I get to the point where all I can do is list things to try. I only have one PC, myself, and it's a laptop with a 9700 and that's old news by desktop standards even though it's a new laptop...


hey no worries, I appreciate your help A LOT, I'm sure you're doing the best you can and every reply is greatly appreciated! ;)

I just don't understand why the sudden problem with this driver since it always worked in the past...and seeing people who got it to work without any problems (like it did for me in hoary) is kinda frustrating :P especially with a clear and easy to follow how-to like this one...

I know I did nothing wrong....if it can help though... when I did the last 2 apt-get
(linux-restricted and xconf-driver) I was told that the latest version of the two is already installed...

[mlomker]

especially with a clear and easy to follow how-to like this one...


You haven't detailed what you're getting. You getting a desktop but ending up with Mesa or a more dramatic error message?

The usual diagnostics:


lsmod | grep fglrx
dmesg | grep fglrx
gksudo gedit /var/log/Xorg.0.log


I've also run across people that swear there's something wrong with Breezy's built-in drivers. You might end up trying to remove all of the previously installed packages and then download the driver from ATI like we did with Hoary. The very latest driver, 8.18.6 seems to not work at the moment, but that doesn't mean that 8.16.20 wouldn't.

You have a clean system right now, so no loss if you bork it while trying things.

[SilverTab]

You haven't detailed what you're getting. You getting a desktop but ending up with Mesa or a more dramatic error message?

The usual diagnostics:


lsmod | grep fglrx
dmesg | grep fglrx
gksudo gedit /var/log/Xorg.0.log


I've also run across people that swear there's something wrong with Breezy's built-in drivers. You might end up trying to remove all of the previously installed packages and then download the driver from ATI like we did with Hoary. The very latest driver, 8.18.6 seems to not work at the moment, but that doesn't mean that 8.16.20 wouldn't.

You have a clean system right now, so no loss if you bork it while trying things.


lsmod | grep fglrx gave the following result:
fglrx 245412 0
agpgart 32328 2 fglrx,intel_agp


dmesg | grep fglrx gave the following result:
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4295579.350000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4295579.350000] [fglrx] module loaded - fglrx 8.16.20 [Aug 16 2005] on minor 0
[4295579.364000] [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
[4295579.365000] [fglrx] Internal AGP support requested, but kernel AGP support active.
[4295579.365000] [fglrx] Have to use kernel AGP support to avoid conflicts.
[4295579.365000] [fglrx] Kernel AGP support doesn't provide agplock functionality.
[4295579.365000] [fglrx] AGP detected, AgpState = 0x1f004a1b (hardware caps of chipset)
[4295579.366000] [fglrx:firegl_unlock] *ERROR* Process 9683 using kernel context 0


The result of Xorg.0.log is more than 2000lines long, not sure if I should post it here?

[mlomker]

[4295579.364000] [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
[4295579.366000] [fglrx:firegl_unlock] *ERROR* Process 9683 using kernel context 0

The result of Xorg.0.log is more than 2000lines long, not sure if I should post it here?

You can attach text files to posts here, no problem. There's no need, though...these are 'good' errors.

Take a look at this thread (http://www.rage3d.com/board/showthread.php?threadid=33736241), though it is a little old. ATI's forums aren't Ubuntu-specific, but obviously a great resource for ATI driver problems. You could do some searches on these errors and see what comes up.

[SilverTab]

You can attach text files to posts here, no problem. There's no need, though...these are 'good' errors.

Take a look at this thread (http://www.rage3d.com/board/showthread.php?threadid=33736241), though it is a little old. ATI's forums aren't Ubuntu-specific, but obviously a great resource for ATI driver problems. You could do some searches on these errors and see what comes up.


mmm I followed the guide...however I only get 1 of the 2 errors mentioned....I still decided to read on...it says to open menu.lst (from /boot/grub)
and look for the kernel line....now here is the suggested modification:
There you should find something like:

kernel /boot/vmlinuz root=/dev/hda1 video=vesafb:ywrap,mtrr,vga=0x31X <---- here you need to add the code found below.


however, this is what my entry looks like....there's no "video" entry in my grub config... :(
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda6 ro quiet splash

[SilverTab]

mlomker: just out of curiosity, what do you get when you do
cat /proc/mtrr

??

[SilverTab]

oh well I tried posting on the rage3d forum...hopefully someone there will be able to help me out! :(

mlomker: I would like to thank you for all your help and your patience! again, its really appreciated! :)

one last thing... when I do cat /proc/mtrr, the only thing showing up is:

reg00: base=0x00000000 ( 0MB), size=984064MB: write-back, count=1

which is my ram....I see no entry for video memory...

[Cloud[01]]

Allright everything is working great, except from the Resolution.
I'm on a widescreen, so my best resolution would be:
1280x800
But all I can get is 1024x768 which is pretty bad because it stretches everything
my xorg.conf:

...
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
Modeline "1280x800@60" 83.91 1280 1312 1624 1656 800 816 824 841
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Radeon Mobility 9600/9700 M10/M11 (RV350 NP)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
...

So I don't know why it doesn't use this resolution. Any hint?

By the way, the real test to get fps with the drivers installed correctly is:

fgl_glxgears

(I got a:

2808 frames in 5.0 seconds = 561.600 FPS
3767 frames in 5.0 seconds = 753.400 FPS
4079 frames in 5.0 seconds = 815.800 FPS
4058 frames in 5.0 seconds = 811.600 FPS
)
For the control panel

fireglcontrol


ciop ciop

[zupermanz]

I've just made a clean kubuntu install and did what the how to said...exept the part linux-restricted-modules-$(uname -r) but no 3d acceleration . I still have mesa. Any ideas? I have AMD64 3200,via chipset and ati 9600 pro


I did --reinstall linux-restricted-modules-$(uname -r) from the sepositories and non the cd... Rebooting and......

[mlomker]

But all I can get is 1024x768 which is pretty bad because it stretches everything

That's a known bug with the 8.16.20 driver and certain displays. My own laptop is one of them, unfortunately.

I'm going to try getting the new 8.18.6 driver installed and write a how-to for it. It solves that detection problem, but I had no luck getting it installed yesterday.

[mlomker]

I've just made a clean kubuntu install and did what the how to said...exept the part linux-restricted-modules-$(uname -r) but no 3d acceleration..

You need the restricted modules for the fglrx.ko file (the kernel driver). I just did a clean 32-bit install and updated the how-to again. It looks like it's best to sudo dpkg-reconfigure xserver-xorg rather than using ATI's fglrxconfig.

[zupermanz]

sudo dpkg-reconfigure xserver-xorg[/b] rather than using ATI's fglrxconfig.
I did that and x couldnt start... it froze on checking battery status.....
i copied the old xconf to restart x again.
i apt-get the modules..reseting.. brb.

[zupermanz]

Nope that didnt do it eather!
I stall have mesa!

[mlomker]

I did that and x couldnt start

Attach a copy of the xorg.conf and your /var/log/Xorg.0.log (from the failed startup) and we'll take a look.

[hackyou]

That's a known bug with the 8.16.20 driver and certain displays. My own laptop is one of them, unfortunately.

I'm going to try getting the new 8.18.6 driver installed and write a how-to for it. It solves that detection problem, but I had no luck getting it installed yesterday.

That's my problems tooooooooo!
I hope you'll make it works, if you need any help just ask.

[TheRay1987]

$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9550 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)

$ fgl_glxgears
1528 frames in 5.0 seconds = 305.600 FPS
1639 frames in 5.0 seconds = 327.800 FPS
2145 frames in 5.0 seconds = 429.000 FPS
2144 frames in 5.0 seconds = 428.800 FPS
1771 frames in 5.0 seconds = 354.200 FPS
1838 frames in 5.0 seconds = 367.600 FPS
1579 frames in 5.0 seconds = 315.800 FPS
1641 frames in 5.0 seconds = 328.200 FPS
1604 frames in 5.0 seconds = 320.800 FPS

I had installed my driver using a howto guide on these forums before breezy came out. It included chaging a bunch of stuff in my xorg.conf file. And just a reminder, ALWAYS MAKE A BACKUP BEFORE CHANGING YOUR xorg.conf. Here is my xorg.conf file (/etc/X11/xorg.conf):
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands:
#
# cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom
# sudo sh -c 'md5sum /etc/X11/xorg.conf >/var/lib/xfree86/xorg.conf.md5sum'
# sudo dpkg-reconfigure xserver-xorg

Section "Files"
FontPath "unix/:7100" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "GLcore"
Load "glx"
Load "dri"
# Load "extmod" but omit DGA extension - this must be included as is if you want to change resolution on the fly
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "freetype"
Load "int10"
Load "record"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI"
Driver "fglrx" # this is the important bi
# If X refuses to use the screen resolution you asked for,
# uncomment this; see "Bugs and Workarounds" for details.
#Option "NoDDC"

# === 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"
# === Use internal AGP GART support? ===
# If OpenGL acceleration doesn't work, try using "yes" here
# and disable the kernel agpgart driver.
Option "UseInternalAGPGART" "no"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "SONY HMD-A20"
Option "DPMS"
HorizSync 30-70
VertRefresh 48-120
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI"
Monitor "SONY HMD-A20"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

[zupermanz]

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
# Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 30-65
VertRefresh 50-75
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection


This is mine .... i cant understand why i still have mesa!

[zupermanz]

when i do sudo apt-get install linux-restricted-modules-$(uname -r
i get
Reading package lists... Done
Building dependency tree... Done
linux-restricted-modules-2.6.12-9-amd64-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

Is this ok?

[Téragone]

This package is installed by default, so if you don't have removed it it's normal.

[ilans]

After a lot of experiments (includ the "how-to" manual) I realized that
my ATI Radeon 9550 card is not recognize in my Ubuntu kernel

lspci |grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4153
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 4173

This is the reason of my non 3D acceleretaion.
BUT HOW I CAUSE MY KERNEL TO RECOGNIZE MY CARD ???

[SilverTab]

After a lot of experiments (includ the "how-to" manual) I realized that
my ATI Radeon 9550 card is not recognize in my Ubuntu kernel

lspci |grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4153
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 4173

This is the reason of my non 3D acceleretaion.
BUT HOW I CAUSE MY KERNEL TO RECOGNIZE MY CARD ???


im right there with you!...

weird thing is that, it was working in hoary...with an older kernel! :(

[zupermanz]

fglrxinfo
libGL error: drmMap of framebuffer failed
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)



is the libGL the problem?

[remmelt]

lspci |grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
0000:01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)

$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)


For me. Used to work under Hoary, after the dist-upgrade X didn't come back up and when I followed this guide it did. Not the right driver though, and the GUI seems sluggish, especially when using Firefox.

[GaryG]

Would this work on my laptop (ATI Radeon Mobility)?

[zupermanz]

I think that it must be a 64bit problem because with 32 bits i didnt had a problem...

[remmelt]

Following the other thread:

change your xorg.conf so that the driver isn't "ati" but "fglrx", restart X and presto:

fgl_glxgears
1648 frames in 5.0 seconds = 329.600 FPS
2016 frames in 5.0 seconds = 403.200 FPS
1978 frames in 5.0 seconds = 395.600 FPS
2017 frames in 5.0 seconds = 403.400 FPS
2010 frames in 5.0 seconds = 402.000 FPS

[zupermanz]

nope i had already tried that but nothing Here is my xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
# Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 28-64
VertRefresh 43-60
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

[GameManK]

Following the other thread:

change your xorg.conf so that the driver isn't "ati" but "fglrx", restart X and presto:

fgl_glxgears
1648 frames in 5.0 seconds = 329.600 FPS
2016 frames in 5.0 seconds = 403.200 FPS
1978 frames in 5.0 seconds = 395.600 FPS
2017 frames in 5.0 seconds = 403.400 FPS
2010 frames in 5.0 seconds = 402.000 FPS


THANK YOU

this worked, ... i thought "ati" sounded more like the generic driver..

[zupermanz]

do you have 64 or 32 bit?

[mlomker]

Would this work on my laptop (ATI Radeon Mobility)?

Yes, that's what I have. The drivers support the 8500+.

[GaryG]

Thanl you mlomker

[eightysix]

Well, after failing to the 8.18.6 driver to work, I tried modifying 8.16.20 instead. For the most part, I got my video card to use the "fglrx" driver by commenting out folders that didn't exist in the filesystem in the first place!

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
# FontPath"/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
# FontPath"/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
# FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
# FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

But, fglrxinfo is still broken. :mad:

eightysix@hikaru:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)


I'm assuming that this is an AMD64 related problem since the people who are having trouble getting to work are using it (including myself).

Edit: Scratch that. I had to change back to using the "ati" driver since the "fglrx" driver would crash my xorg configuration.

[toujours]

Allow me to join this thread as I too am experiencing the similar problems : AMD64,
ATI drivers installed with restricted modules as suggested, you get the picture...


fglrxinfo
libGL error: drmMap of framebuffer failed
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

[jamesford]

hmm, i got 3D working just fine, but whats wrong with the 2D performance? like moving a window sideways or playing a fullscreen movie uses almost all of my cpu, while it used next to nothing before i installed the fglrx stuff...

[mlomker]

I just got a post to another thread from a developer. There is a patch for ATI's 8.18.6 installer that is supposed to fix all of the problems with installing that package.

Look here. (http://ati.cchtml.com/show_bug.cgi?id=198)

I can't test it, myself, without doing a clean reload. Someone please let me know if it works. If so then I hope we can find someone to put the .deb files on a web server.

[toujours]

I just got a post to another thread from a developer. There is a patch for ATI's 8.18.6 installer that is supposed to fix all of the problems with installing that package.

Look here. (http://ati.cchtml.com/show_bug.cgi?id=198)

I can't test it, myself, without doing a clean reload. Someone please let me know if it works. If so then I hope we can find someone to put the .deb files on a web server.

Ewwww..... :confused: :(

If that's what it takes I'll just wait until I can use Synaptic to download it...

[Anchovie]

I just got a post to another thread from a developer. There is a patch for ATI's 8.18.6 installer that is supposed to fix all of the problems with installing that package.

Look here. (http://ati.cchtml.com/show_bug.cgi?id=198)

I can't test it, myself, without doing a clean reload. Someone please let me know if it works. If so then I hope we can find someone to put the .deb files on a web server.

How do you do a clean reload? If you can give me the instructions on a clean reload I can test it out, since I'm still struggling with mine.

[mlomker]

How do you do a clean reload?

I was referring to reinstalling Ubuntu from CD and starting over. Once you install a package manually it is almost impossible to get back to a clean system, which you really need in order to write a workable how-to for others. A freshly loaded system and then creating a .deb file with the patch is the only clean way to test things. I'm thinking about buying another PC that I'll use just for that, but right now I only have one PC.

[Anchovie]

I was referring to reinstalling Ubuntu from CD and starting over. Once you install a package manually it is almost impossible to get back to a clean system, which you really need in order to write a workable how-to for others. A freshly loaded system and then creating a .deb file with the patch is the only clean way to test things. I'm thinking about buying another PC that I'll use just for that, but right now I only have one PC.

Okay that's fine, I wouldn't mind doing that, I'll post back here as soon as I get the result and whatever the troubleshooting steps I have to go through in order to get it to work.

[remmelt]

I was referring to reinstalling Ubuntu from CD and starting over. Once you install a package manually it is almost impossible to get back to a clean system, which you really need in order to write a workable how-to for others. A freshly loaded system and then creating a .deb file with the patch is the only clean way to test things. I'm thinking about buying another PC that I'll use just for that, but right now I only have one PC.
Ha! But you wouldn't shoot yourself in the foot and buy ATI again, would you? ;)


To add something on-topic to this thread: I have an AMD64 processor, but I'm running 32 bit Ubuntu.

[mlomker]

Ha! But you wouldn't shoot yourself in the foot and buy ATI again, would you?

Yeah, I just ordered a box with an X300 minute ago. Somebody has to help people with ATI cards on here. ;)

To add something on-topic to this thread: I have an AMD64 processor, but I'm running 32 bit Ubuntu.

So do I and haven't had any trouble, personally, with 32-bit. My new desktop will be Pentium-D.

[TLE]

First of all my specs are:
AMD 64 3200+
ATI Radeon X800XL
(If you need anything else)

I've been following this thread, and did as the howto said. When I get to the "restricted modelus" part i'm told that it is already installed, but I understand that is not a problem. When i've done the configuration I get the same result as a lot of the other people here, I cant start up i X, and it's working fine except for the 3D acc. which is still running under Mesa.

I was sort of expecting trouble and since I have plenty of harddrive space I used a rescueCD with partimage to make a image of my Ubuntu partition, with an absolutely clean install. (Which also for me, means that it won't start X).

So this means that I can "reload" an absolutly clean install in about 25 min. So i'm ready to try anything you(mlorker) can think of. But i'm an intermediate Linux so i'm might going to need a little guidance.

I'm thinking if you are interesseted maybe we should do it off forum, not to clogg this thread up. So, I have a few questions to the patch, but i'll postpone posting them until I know if anynody will assist me.

Regards TLE

[TLE]

Sorry.
"I cant start up i X"
It is of course supposed to read
"I CAN start up in X"

[mlomker]

I cant start up i X, and it's working fine except for the 3D acc. which is still running under Mesa.


I'm going to assume that you are running 32-bit Ubuntu (k7 kernel). The 64-bit version is a lost cause right now. I spent an entire day and couldn't get it to work and so have a number of other advanced but non-developer users. Something's broke there.

Boot up with the built-in fglrx drivers (I assume you've already created an xorg.conf using the dpkg reconfigure). Find your fglrxinfo and do an ldd against it.


sudo updatedb
locate libGL.so.1

whereis fglrxinfo
ldd /somepath/fglrxinfo
cat /etc/ld.so.conf

[TLE]

Sorry about the misunderstanding, but I'm actually using the 64 bit version. I wasn't aware that It was a "lost cause". I thought a read posts from other 64-bit users. My bad.

I'll try the 32 bit version, as soon as I can get It downloaded. But anyway the offer still stands. I have a lot of harddrive space for partition images, (and fall vacation for the next week) so I can can do "fresh installs" by the snap of my fingers, almost. So I wouldn't mind helping out if I can, also with the 64 bit version later, I can just install both a 64 bit version and a 32, just let me know.

I'll post a soon as i've tried the how to on the 32 bit version

[mlomker]

Sorry about the misunderstanding, but I'm actually using the 64 bit version.

A few days before Breezy's release they repackaged Xorg into many smaller packages, many of them for video drivers. At the moment there is no known way of getting rid of Mesa on 64-bit. I had the built-in 8.16.20 drivers working in 3D but my box was seriously modded that it wasn't a good example...I'm the only one that I know of who has gotten the Breezy drivers to work on 64-bit.

Since I was going to do a clean reload anyway, I decided to go 32-bit so that I can use multimedia and my winmodem and all that jazz.

[ilans]

MLOMKER I need your help:
I generated the 5 new patched debs files (using the patch):
fglrx-control_8.18.6-1_i386.deb
fglrx-kernel-source_8.18.6-1_i386.deb
fglrx-sources_8.18.6-1_i386.deb
xorg-driver-fglrx_8.18.6-1_i386.deb
xorg-driver-fglrx-dev_8.18.6-1_i386.deb
(I CAN ZIP AND SEND THEM VIA YOUSENDIT)

And I did (successfully) these steps:

1. sudo apt-get remove xorg-driver-fglrx
sudo apt-get remove fglrx-control
sudo apt-get remove linux-restricted-modules-$(uname -r)
Than I rebooted (before change correctly xorg.conf in order to launce to gnome)

2. I install the 5 new patched debs files :
fglrx-control_8.18.6-1_i386.deb
fglrx-kernel-source_8.18.6-1_i386.deb
fglrx-sources_8.18.6-1_i386.deb
xorg-driver-fglrx_8.18.6-1_i386.deb
xorg-driver-fglrx-dev_8.18.6-1_i386.deb

3. I untar /usr/src/fglrx.tar.bz2

4. I have a problem in the folowing step:
"generate the kernel module for your current kernel"

I tried both:

1. sudo module-assistant a-i fglrx
(I installed module-assistant and linux-header)

I get this message:
/usr/bin/make -C /usr/src/linux-headers-2.6.12-9-386
SUBDIRS=/usr/src/modules/fglrx modules
/usr/src/linux-headers-2.6.12-9-386/scripts/gcc-version.sh: line 11:
gcc-3.4: command not found
/usr/src/linux-headers-2.6.12-9-386/scripts/gcc-version.sh: line 12:
gcc-3.4: command not found
make[1]: gcc-3.4: Command not found

2. sudo sh make.sh

I get this message:
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make.sh: line 843: cd: 2.6.x: No such file or directory
/bin/sh: gcc-3.4: command not found
/bin/sh: gcc-3.4: command not found


I DONT UNDERSTAND WHY I HAVE GOT AN ERROR ON GCC 3.4 WHILE I HAVE BEEN USING GCC 4.0 !!!

[arjun]

Hi. My problem is very similar to most of the ones described here, however, I think I can add another significant problem to the list. As well as fglrx using mesa as the driver as opposed to openGL, the transfer type is PCI. My card is plugged into an AGP slot and with the 8.13.14 drivers in hoary, AGP was recognized and the driver worked without a hitch (4000 rpm in glxgears). I've tried the driver in the repo (with fglrx module) and ATI's giant sh installer- both yield the same terrible results. I'm using Power Colour Radeon 9600 SE and the 686-SMP kernel. Kernel Headers are also installed...

[nbx909]

okay i have a radeon 9600 pro on an amd xp 2000+ machine... i get this when i run fglrxinfo
michael@mikeubuntu:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

michael@mikeubuntu:~$

So i tried doing sudo echo "/usr/X11R6/lib" >> /etc/ld.so.conf
but i get
michael@mikeubuntu:~$ sudo echo "/usr/X11R6/lib" >> /etc/ld.so.conf
bash: /etc/ld.so.conf: Permission denied

any ideas?

[mlomker]

bash: /etc/ld.so.conf: Permission denied
any ideas?

That means that you already have a file there. I've done two clean installs today and that file doesn't exist on either box. Is yours an upgrade from Hoary or the 64-bit version?

Try editing it with nano.


sudo nano /etc/ld.so.conf


Ctrl-W, Y, Enter to save.

[eudemon]

Hello,
Just another person who cannot seem to get 3d acceleration working. I just followed the instructions to install on a clean installation of breezy. I have a similar system to you, mlomker: 64 bit amd cpu laptop, running 32 bit breezy, with a radeon 9700 mobile card.

I've tried xorg.conf files generated by fglrx-control, dpkg-reconfigure xserver-xorg, and simply modifying the original to replace the string "ati" with "fglrx". So far nothing has worked.

I was able to get acceleration consistently working under hoary by using this hack: http://ubuntuforums.org/showpost.php?p=77060&postcount=54. Otherwise, no dice.

Thanks for your help.

[Anchovie]

Hm... I tried to follow the steps located at http://ati.cchtml.com/show_bug.cgi?id=198, but I got stuck on step 4, I got an error "bash: ./ati-installer: No such file or directory" when trying to run "./ati-installer 8.18.6 --buildpkg Ubuntu/breezy", anybody have any ideas? No error occured from the previous steps.t

[ilans]

Hm... I tried to follow the steps located at http://ati.cchtml.com/show_bug.cgi?id=198, but I got stuck on step 4, I got an error "bash: ./ati-installer: No such file or directory" when trying to run "./ati-installer 8.18.6 --buildpkg Ubuntu/breezy", anybody have any ideas? No error occured from the previous steps.t

Dont work so hard.
Here is the 5 pached deb files (I managed to create them) but I'm stuck
in updating the kernel with the new module
http://s46.yousendit.com/d.aspx?id=29UM2H2HFBNF02HU7CROE0919E

[deepspring]

Edit: See this post instead:

http://www.ubuntuforums.org/showpost.php?p=575778&postcount=224

[Anchovie]

Dont work so hard.
Here is the 5 pached deb files (I managed to create them) but I'm stuck
in updating the kernel with the new module
http://s46.yousendit.com/d.aspx?id=29UM2H2HFBNF02HU7CROE0919E

I thought that's the purpose of step 4, to create the five deb packages... How did you created them? When you said using the "patch to generate 5 new deb files" in post 74, do you mean using the "update the Ubuntu packages scripts in the ati installer patch"? Or was it something else.

[arjun]

Hi. Further elaborating on the 8.16.20 drivers; it looks as if my libraries are not linked correctly and I can't change them. When typing "ldd /usr/bin/glxinfo", one of the entries is: libGL.so.1 => /usr/lib/libGL.so.1. From what I understand, that library in particular out of all the other ones displayed is crucial for OpenGL and has to be linked to a lib in /usr/X11R6/lib. Now that the problem is identified, I cannot fix it. When I type: "sudo echo /usr/X11R6/lib >> /etc/ld.so.conf" I get a permission denied error. When I wanted to check out ld.so.conf, it does not exist. Do I have to create it?

[Anchovie]

Hi. Further elaborating on the 8.16.20 patch; it looks as if my libraries are not linked correctly and I can't change them. When typing "ldd /usr/bin/glxinfo", one of the entries is: libGL.so.1 => /usr/lib/libGL.so.1. From what I understand, that library in particular out of all the other ones displayed is crucial for OpenGL and has to be linked to a lib in /usr/X11R6/lib. Now that the problem is identified, I cannot fix it. When I type: "sudo echo /usr/X11R6/lib >> /etc/ld.so.conf" I get a permission denied error. When I wanted to check out ld.so.conf, it does not exist. Do I have to create it?

Yes, ld.so.conf is the file you'll have to create.

[comradevik]

sory for the n00b type question.. but how do i find out what videocard i get.. cuz the info says mesa.. which by now i know is bad.. i followe all the instructions but nothing worked... i suspect its an ATI but i got no idea ... i have an HP pavilion 753n and it doesnt say what graphics card i have anywhere except it says 64 mb DDR SDRAM inegrated intel extreme graphics with up to 64 mb shared video memory

[mlomker]

Option "UseInternalAGPGART" "no" # <= Disables internal AGPgart driver


That won't do anything. If you look at the output of dmesg | grep fglrx after booting you'll see this:


Internal AGP support requested, but kernel AGP support active.
Have to use kernel AGP support to avoid conflicts.


In other words, the driver ignores that line if the internal AGP Gart is built into the kernel, which it is on a Ubuntu kernel. Perhaps there was a conflict with your card, but it doesn't make sense. Have you tried adding it back and starting up? If it's consistent then that's interesting.

[mlomker]

i suspect its an ATI but i got no idea


lspci | grep VGA

[comradevik]

victor@ubuntu:~$ lspci | grep VGA
0000:00:02.0 VGA compatible controller: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
victor@ubuntu:~$


what's that mean.. should i go and buy a video-card?

[mlomker]

what's that mean.. should i go and buy a video-card?

LOL. If you play games you should!

You're using the integrated Intel video card and it's going to be very slow. I'd recommend an Nvidia if you're buying a new card. People say that they are less trouble under linux...then again, I don't read those threads. ;)

[comradevik]

i dont play games .... they run slow :-D

i work in blender.... and that depends on ram i think.. at least i haven't had problems with it

under windows it run just as slow with some games... and some games worked fine (cs was perfect while american army was slow) but i dont play as much so i gave it up anyways.

[eudemon]

I just followed the instructions for removing and reinstalling, and at the reboot step X failed to start. Simply went back and did an apt-get install for everything that I removed, changed xorg.conf to have "fglrx" again, and X could start up again. But still no hardware acceleration.

Checked my linked libs using ldd, and the correct libraries from the X11R6 directory are being used.

I'm starting to get really frustrated. I know that it is not the Ubuntu devs fault, but I'm going to have to go back to windows (blech) if I can't get this working soon. What really gets me is that it worked under Hoary, albeit in a hacked fashion.

[arjun]

I've created ld.so.conf but I can't do anything to it. I get permission denied even if I try to chmod it. Is a fresh install justified?

[mlomker]

I've created ld.so.conf but I can't do anything to it. I get permission denied even if I try to chmod it. Is a fresh install justified?

You have to use sudo to do anything with that file, but further experimentation this morning leads me to believe that the problem isn't in there anyway.

[mlomker]

"fglrx" again, and X could start up again. But still no hardware acceleration.

It's too late now for me to speculate on that. It's possible that you've made enough library changes that you won't be able to use the ATI driver anymore.

What really gets me is that it worked under Hoary, albeit in a hacked fashion.

Did you do an upgrade from Hoary or a clean install? I'd definitely try a clean install first. That being said, you can always reinstall Hoary...it's not like there was anything wrong with Hoary.

[eudemon]

It's too late now for me to speculate on that. It's possible that you've made enough library changes that you won't be able to use the ATI driver anymore.

Did you do an upgrade from Hoary or a clean install? I'd definitely try a clean install first. That being said, you can always reinstall Hoary...it's not like there was anything wrong with Hoary.

When Breezy became available, I did a clean install as soon as I had it downloaded, then followed the instructions in the first post. Then, when that failed to work, I went back and did the removal and reinstallation bit. That's where I hit this snag described in the previous post. It wouldn't be a big deal to do another clean install at this point, as I haven't done much in the way of setting up stuff under my new system.

I've found that in the past, if I install xorg-driver-fglrx, then remove it, X will fail to start properly until I put it back, even though it wasn't there to begin with. :confused:

I could go back to Hoary, and I may do that. I'd really like to get this working though; it seems like everyone but me can accomplish it.

Are there still issues with the fglrx driver and the k7 kernel? I seem to recall that being a problem in the past.

[souled]

Ok, after removing the restricted kernel thing and rebooting, I installed the fglrx-control and I just put in sudo apt-get install linux-restricted-modules-$(uname -r). It's asking me to insert the Breezy Badger CD. Is this supposed to happen?

[mlomker]

I've found that in the past, if I install xorg-driver-fglrx, then remove it, X will fail to start properly until I put it back, even though it wasn't there to begin with. :confused:

In working with a few other people today I discovered that installation of that file renames the Mesa library and moves it to a backup directory. I should think that the removal would copy it back, but maybe that doesn't always go so well. I'm going to buy a 2nd PC so that I have one to test things on...probably with an X300 card since they are cheap.

I'd really like to get this working though; it seems like everyone but me can accomplish it.

I wish that were true. I'm trying to help a lot of people. It seems like anyone with a 9550-series card can't get them working right now. I've only talked to one person that has.

Are there still issues with the fglrx driver and the k7 kernel? I seem to recall that being a problem in the past.

Naw, that's what I'm running. 32-bit Kubuntu with a Mobility 9700 card and the 8.18.6 driver. The newer driver took some work to get going but the included one was easy.

I think it really depends on your system board/card combination as to whether or not things are easy. If you're going to reload then you could give the newer driver (http://ubuntuforums.org/showthread.php?p=411503) a shot. I don't recommend it unless people are having trouble, but you're having trouble. :)

[eudemon]

Naw, that's what I'm running. 32-bit Kubuntu with a Mobility 9700 card and the 8.18.6 driver. The newer driver took some work to get going but the included one was easy.

I've got the same video card, and an amd64 cpu running 32-bit Ubuntu on my laptop. I've never had an easy time getting DRI working, with any version of the driver or of Ubuntu. I might try the newer driver, just to see what happens, but I doubt it'll be any better than previous versions. Experience has made me a pessimist unfortunately :???: .

I don't know enough about the hardware involved, but editing the driver source so that it thinks the kernel has no mtrr capabilities has gotten DRI working for me before. That didn't work under Breezy before, but I might try it again, with both 8.16.20 and 8.18.6.

Btw, thanks for the thread, and all the work you've put into getting the fglrx driver working for people. I'm sure everyone really appreciates how much of your own time you've put into getting other people's systems working.

[mlomker]

I don't know enough about the hardware involved, but editing the driver source so that it thinks the kernel has no mtrr capabilities has gotten DRI working for me before.

There are some commands related to mtrr that you can pass to the kernel in grub's /boot/grub/menu.lst file. There's a thread here (http://www.rage3d.com/board/showthread.php?threadid=33736241) discussing that.

It sounds like we have very similar hardware. I'm running an amd64 3400+ with 32-bit Kubuntu and the k7 kernel.

You're welcome! I hope we can come up with a solid how-to soon.

[eudemon]

There are some commands related to mtrr that you can pass to the kernel in grub's /boot/grub/menu.lst file. There's a thread here (http://www.rage3d.com/board/showthread.php?threadid=33736241) discussing that.

It sounds like we have very similar hardware. I'm running an amd64 3400+ with 32-bit Kubuntu and the k7 kernel.

You're welcome! I hope we can come up with a solid how-to soon.
Thanks, I saw that thread before, but I'll take a closer look. This looks like it might be able to help me.

EDIT:

Okay, on a hunch, I opened up my laptop and removed one of my two 512 mb ram chips. I rebooted, and 3D acceleration worked like a charm. Put it back in, rebooted again, and no 3D acceleration. I'm gonna try removing te other ram chip to see what happens. Can't believe this was my problem for the past 8 months.

[eudemon]

So, as long as I only have one of my two 512mb ram chips installed, hardware acceleration works beautifully. Put them both in though, and there's an error that causes DRI to fail. Something with mtrrs I guess. Like I said, I don't know enough about the hardware to provide any useful info, but maybe someone else can make something of my situtation. Maybe having both chips causes all my mtrrs to be used up, leaving none for my vram? :confused:

[souled]

Ok, I've tried this HOWTO and the 8.18.6 HOWTO, and no dice. I have a Radeon 9200, AMD Athlon XP 2500+. I got the drivers working on Hoary, but can't get them working on Breezy. I'm reinstalling Breezy right now, any ideas?

[mlomker]

Maybe having both chips causes all my mtrrs to be used up, leaving none for my vram?

That's really weird because that mtrr business refers to the video ram, which is totally separate memory on a 9700 from your system memory. I have 1 Gig in my machine and the memory is different brands and different speeds.

Your box is fairly new so the BIOS should be up-to-date. Have you made many changes in there? I'd start poking around the BIOS looking for settings if I were you.

[eudemon]

I'll take a look. It's been a while since I looked at my BIOS on this machine, but I remember that it was exremely limited.

[eudemon]

Yeah, my BIOS offers no options on ram, just says how much there is. Once I get home tonight I can open up my box again, and see what the BIOS does when I have both chips in, but for now at least, halving my ram isn't a bad trade-off to have 3D acceleration. :smile:

EDIT:

So looking at my ram a little closer, its the same brand, same speed, with slightly different model numbers. Strange that it would cause problems to use both chips.

[gelse]

any solution yet about the resolution bug in 8.16.20 ?

reason: cant use the 8.18 driver, because it just doesnt work in some applications (ok, in games. ok in ONE game. wow - but as its the ONLY reason i need 3D-acceleration, and its the only game i play anyway, its critical...)

what would help me too, is a way to get the 8.14.13 to compile with GCC4.

[clp]

What about mtrr errors?

This is my error's log in dmesg...

[fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)

This thread...

(http://www.rage3d.com/board/showthread.php?threadid=33736241)
Don't resolve anything (April 2004)

I have test 8.18 driver but I get the same error.

My "cat /proc/mtrr"
reg00: base=0x00000000 ( 0MB), size=983552MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size=983296MB: write-back, count=1
reg02: base=0xd8000000 (3456MB), size=983104MB: write-combining, count=1

Any suggestion?

Sorry for my poor english...

[mlomker]

What about mtrr errors?


The mtrr and firegl_unlock errors are a problem for some people but it's a bug and not an installation issue, so I can't help you. There is a link for bugzilla at the top of every page and that's the only way to communicate with the developers about those sort of problems.

[hounddog32]

I have followed the howto (upgraded to breezy, 32-bit kernel, Radeon 9100 integrated graphics) and have a problem not mentioned in this thread. I've looked elsewhere on the forum but most of it is hoary stuff that is mixing me up a bit.

When I run fglrxinfo it tells me that the vendor is ATI, as it should be. xorg.conf has fglrx as the driver to use, all good.

When I run glxgears or fg_glxgears, the window opens, black background and the computer locks - i have to do a hard reset. I've not tried a game, but I can guess what it'll be.

[mlomker]

i have to do a hard reset. I've not tried a game, but I can guess what it'll be.

I've seen a few other threads with similar results. I gather that it is the 9200 and older that most often see the problem.

[cyberkode]

Hey I was wondering how I would go about getting 3d acceleration for my video card in my laptop. It is a ATI Rage Mobility 32.

Thanks,

Mike

[Baf]

I followed the guide by mlomker and it didn't work. Then I tried remmelt's suggestion which was replacing 'ati' with 'fglrx' in the xorg.conf driver. That worked. I rebooted and ran fglrxinfo and got what I wanted.

However, I'm still having problems. I cant open up Totem to play an mp3 or a video clip. It says: The video output is in use by another application. Please close other video applications, or select another video output in the Multimedia Systems Selector.

No, I don't have any other video apps open. I took a look at the Multimedia Systems Selector in System>Preferences and I just don't know which option to choose.

I haven't installed any codecs which I was thinking was the problem, but before I installed the ati drivers I could listen to mp3's with Totem. Also, when I run glxgears the window pops up with the gears and it appears they are moving at the speed they should be. But it doesn't display the fps and time in the terminal and my computer becomes really slow.

EDIT: I just ran fgl_glxgears and I actually got results. My computer didn't become as slow and it outputted the fps, which was mostly in the eight hundreds. Like I said above, glxgears is really choppy and doesn't display output. I left it on for ten minutes, came back and it still didn't print anything.

[mlomker]

I followed the guide by mlomker and it didn't work. Then I tried remmelt's suggestion which was replacing 'ati' with 'fglrx' in the xorg.conf driver. That worked. I rebooted and ran fglrxinfo and got what I wanted.

That's what the dpkg-reconfigure does, so I have to assume that you skipped it.

display output. I left it on for ten minutes, came back and it still didn't print anything.

Look here. (http://ubuntuforums.org/showpost.php?p=412040&postcount=2)

[Baf]

I didn't skip it, I don't think. I could have by mistake, but I have been trying to get the video drivers to work for some time now so I was careful. Does it matter anyway, I got the ATI output after running fglrxinfo? I really hope not.

I did just add that alias to the bash.bashrc file and now I got it to over a thousand. But my computer is still slow when running it. Is that normal? I wouldn't think so, but I don't know.

Any suggestions on the other things? mlomker, thanks for the help and the guide. It must be very time consuming and I thank you for your efforts.

[mlomker]

Does it matter anyway, I got the ATI output after running fglrxinfo? I really hope not.

mlomker, thanks for the help and the guide. It must be very time consuming and I thank you for your efforts


It might not matter with your install but I want a how-to that always works (if that's possible).

I did just add that alias to the bash.bashrc file and now I got it to over a thousand. But my computer is still slow when running it. Is that normal? I wouldn't think so, but I don't know.

I don't know, either. You could try running top in a terminal to see what is taking up memory and processor time.

[Septor]

Just a heads up to all: A new fglrx 8.18.8 has been released. This should include the native Ubuntu package scripts, so no more patches should be necessary to build the Ubuntu .debs.

Cheers.

[Leopard]

That's what the dpkg-reconfigure does, so I have to assume that you skipped it.[/URL]
Is that all it does? I went through I don't know how many reconfiguration questions and all I needed to do was change a single entry in xorg.conf? :confused: Do'h!
Just a heads up to all: A new fglrx 8.18.8 has been released. This should include the native Ubuntu package scripts, so no more patches should be necessary to build the Ubuntu .debs.

Cheers.
I hope this means a simplfied install of ATI drivers for AMD64 users is in the pipeline! Please!

Thanks for all your help guys :D

[Septor]

Is that all it does? I went through I don't know how many reconfiguration questions and all I needed to do was change a single entry in xorg.conf? :confused: Do'h!

I hope this means a simplfied install of ATI drivers for AMD64 users is in the pipeline! Please!

Thanks for all your help guys :D

Unfortunately no. the ATI drivers are built against the latest DRI, however Ubuntu includes a patch which breaks compatability. So you will be stuck copying a different libdrm.a until the Ubuntu changes make it into DRI cvs. I guess it is possible ATI will build a separate module against the patches DRI, but I doubt it.

Edit: I take that back. The change is in DRI CVS, so 64bit should be okay on Xorg 6.9/70... whenever X7.0 makes it into Ubuntu though I don't know.

[wakeboarder]

mlomker: great HowTo!
After installing Breezy I too got the vendor=Mesa from fglrxinfo
so I decided to switch to fglrx.
Everything seems to work nice and fast. However when I use suspend my laptop it freezes in resume, which never happend before.
Any suggestions?

[mlomker]

Everything seems to work nice and fast. However when I use suspend my laptop it freezes in resume, which never happend before.


Yup. fglrx does not support power management. ATI states that in their FAQ's. You'll have to choose.

[jd_]

Just a note about the Mesa bug :
as suggested in the first page, I did a sudo apt-get install --reinstall needed_packages (note the --reinstall) and it worked fine : no more Mesa but
jd@Bibi:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Pro Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)
which is actually better ;)

Thanks.

[Baf]

I have the ATI drivers installed properly... atleast thats what running fglrxinfo tells me. I can run Unreal Tournament fine, actually probably smoother than in Windows.
However, when I am doing normal things on the desktop it still seems choppy. Like, minimizing a screen I can see the trails. It makes it slower, or makes it seem that way.
Let me know if any of you have any suggestions.

[Septor]

I have the ATI drivers installed properly... atleast thats what running fglrxinfo tells me. I can run Unreal Tournament fine, actually probably smoother than in Windows.
However, when I am doing normal things on the desktop it still seems choppy. Like, minimizing a screen I can see the trails. It makes it slower, or makes it seem that way.
Let me know if any of you have any suggestions.

This is a common/known problem with fglrx. The 2D part of the driver seems to be slower in some cases when compared with the open source Radeon driver. As always, it has improved over time, but still seems to be slower in a few cases. I noticed on my laptop that the screen-fade when logging out is smooth with the radeon driver but only has 3-5 chunky "steps" with the fglrx driver... right now I don't care... I rather have 3D and slow 2D than fast 2D and no 3D at all :)

[Baf]

This is a common/known problem with fglrx. The 2D part of the driver seems to be slower in some cases when compared with the open source Radeon driver. As always, it has improved over time, but still seems to be slower in a few cases. I noticed on my laptop that the screen-fade when logging out is smooth with the radeon driver but only has 3-5 chunky "steps" with the fglrx driver... right now I don't care... I rather have 3D and slow 2D than fast 2D and no 3D at all :)

Geesh, that blows. But yeah, I'd rather 3d.

[sciurus]

This partially worked for me. I have a Radeon 9800 AIW Pro on a 19" Dell P991 Epox ERDA3+ with a Athlon XP 2600 and 2x512mb RAM. glxgears reports more than 4000 fps, but my resolution and refresh rate won't go past 1024x768 and 60Hz.

If I decide high resolution is more important than 3d acceleration, can I safely go back to my old xorg.conf without making any other changes?

My current /etc/X11/xorg.conf is

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "dbe"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Radeon 9800 AIW"
Driver "fglrx"
BusID "PCI:2:0:0"
EndSection

Section "Monitor"
Identifier "DELL P991"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Radeon 9800 AIW"
Monitor "DELL P991"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection


The part of x's log that looks relevant

(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): Connected Display1: CRT on primary DAC
(II) fglrx(0): No EDID information available.
(WW) fglrx(0): Specified desktop setup not supported: 8
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000004
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 9 modes found for primary display.
(--) fglrx(0): Virtual size is 1024x768 (pitch 1024)
(**) fglrx(0): *Mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806
(**) fglrx(0): Default mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 43.0 Hz
(II) fglrx(0): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 772 817 +hsync
(**) fglrx(0): *Mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): *Mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525 -hsync -vsync
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 600 601 605 742 -hsync
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 480 491 493 525 -hsync
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 400 457 459 524 -hsync -vsync
(==) fglrx(0): DPI set to (75, 75)

[Septor]

This partially worked for me. I have a Radeon 9800 AIW Pro on a 19" Dell P991 Epox ERDA3+ with a Athlon XP 2600 and 2x512mb RAM. glxgears reports more than 4000 fps, but my resolution and refresh rate won't go past 1024x768 and 60Hz.

If I decide high resolution is more important than 3d acceleration, can I safely go back to my old xorg.conf without making any other changes?

My current /etc/X11/xorg.conf is

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "dbe"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Radeon 9800 AIW"
Driver "fglrx"
BusID "PCI:2:0:0"
EndSection

Section "Monitor"
Identifier "DELL P991"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Radeon 9800 AIW"
Monitor "DELL P991"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection


The part of x's log that looks relevant

(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): Connected Display1: CRT on primary DAC
(II) fglrx(0): No EDID information available.
(WW) fglrx(0): Specified desktop setup not supported: 8
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000004
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 9 modes found for primary display.
(--) fglrx(0): Virtual size is 1024x768 (pitch 1024)
(**) fglrx(0): *Mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806
(**) fglrx(0): Default mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 43.0 Hz
(II) fglrx(0): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 772 817 +hsync
(**) fglrx(0): *Mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): *Mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525 -hsync -vsync
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 600 601 605 742 -hsync
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 480 491 493 525 -hsync
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 400 457 459 524 -hsync -vsync
(==) fglrx(0): DPI set to (75, 75)



It appears that the driver can't find EDID information for your monitor. Either this is because you hit the monitor bug in 8.16 or you have a really old monitor. Try upgrading to 8.18 if you feel brave, or simple set the horizontal and vertical refresh values in your monitor section (man xorg.conf). Make sure you use the actual values for your monitor though (check the manual or the manufacturer's homepage)!

[mlomker]

my resolution and refresh rate won't go past 1024x768 and 60Hz.

You should install 8.18.8. (http://ubuntuforums.org/showthread.php?t=78466) Certain newer LCD's don't 'talk' to the driver properly.


If I decide high resolution is more important than 3d acceleration, can I safely go back to my old xorg.conf without making any other changes?


Yes.

[sciurus]

It appears that the driver can't find EDID information for your monitor. Either this is because you hit the monitor bug in 8.16 or you have a really old monitor. Try upgrading to 8.18 if you feel brave, or simple set the horizontal and vertical refresh values in your monitor section (man xorg.conf). Make sure you use the actual values for your monitor though (check the manual or the manufacturer's homepage)!

Thanks, that was the problem! I thought I had specified those setting when I reconfigured X, and somehow I didn't notice that they weren't in the configuation file. Running fine at 1600x1200 now.

[Cufishing]

Wow! This was pretty strenous for a Newb. But, hey I was able to follow along and make it happen. Went FPS went through the roof.

fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 XT Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)

glxgears -iacknowledgethatthistoolisnotabenchmark
15804 frames in 5.0 seconds = 3160.638 FPS
15774 frames in 5.0 seconds = 3154.685 FPS

fgl_glxgears
2737 frames in 5.0 seconds = 547.400 FPS

Thank you.

[mlomker]

Wow! This was pretty strenous for a Newb. But, hey I was able to follow along and make it happen. Went FPS went through the roof.

:cool: Linux takes a little more determination but it is also rewarding to learn new things.

[lukeweb]

Thank you for this very simple but so far effective guide. It's gone better than the pre-Breezy days...
However, this has caused a number of oddities that I would appreciate some help with.
My overall system performance has become extremely erratic. There will be a massive delay when trying to perform a task - opening a terminal, executing a command, changing focus, etc. then a quick burst where lots will happen. I'm having a lot of programs sitting in the taskbar indicating they're loading ('Starting Terminal...'), but taking quite a long time. This wasn't happening before. In it's current state it's fairly unusable, but I certainly count this as progress.
AFAIK I'm using the right driver now...
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Pro Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)

glxgears is all over the place. In another test, it was ranging from <100 to 3000+.
glxgears -iacknowledgethatthistoolisnotabenchmark
1302 frames in 6.3 seconds = 207.895 FPS
503 frames in 10.7 seconds = 46.975 FPS
514 frames in 7.2 seconds = 70.900 FPS
3548 frames in 8.0 seconds = 443.211 FPS
1014 frames in 9.1 seconds = 111.780 FPS
483 frames in 10.9 seconds = 44.492 FPS

I've noticed with both glxgears and fgl_glxgears there is a burst of regular fast FPS which lasts a very short time before bursts of fairly slow, static, fairly slow, static etc. I should also point out that actually running those programs takes about 15s when previously that was near-instant.
Any ideas what's up? I should be able to provide more information on request - I haven't edited the conf file that was output, but could this all be down to one wrong setting in the reconfigure wizard?
Really appreciating the help though - getting acceleration for this card sorted would certainly dilute my Windows use even more :)

EDIT
Ok, ok - someone slap me PLEASE.
I be very stupid, but I should probably preserve this gem of stupidity in case someone falls in the same trap as me (not likely)
I had only restarted X when I hit those problems, but restarting my whole PC made it go SWIMMINGLY


glxgears -iacknowledgethatthistoolisnotabenchmark
20776 frames in 5.0 seconds = 4155.054 FPS
22579 frames in 5.0 seconds = 4515.663 FPS
22586 frames in 5.0 seconds = 4517.159 FPS



fgl_glxgears
3048 frames in 5.0 seconds = 609.600 FPS
4210 frames in 5.0 seconds = 842.000 FPS
4211 frames in 5.0 seconds = 842.200 FPS


Beautiful, isn't it? :)
Thanks SOOOO much to the OP for making me a mega-happy bunny :D

[mlomker]

Thanks SOOOO much to the OP for making me a mega-happy bunny :D

Around the IT department we call that Dr. Reboot. He makes housecalls and fixes all kinds of weird problems. :cool:

[foxy123]

Does fglrx driver still not support composite and dri together? If I put
Section "Extensions"
Option "Composite" "Enable"
EndSection

option in my xorg.conf, dri disappear and fglrxinfo gives me:
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

[mlomker]

Does fglrx driver still not support composite and dri together?

I've read in other threads that it doesn't, but that'd be a question better asked on ATI's forum. (www.rage3d.com/board/forumdisplay.php?f=88)

[Cufishing]

Mlomker, I totally destroyed my Ubuntu attempting to install an chipset driver.
I rebuilt with Ubuntu, and could NOT get your guide to work the second time. I also decided to try Kbuntu, again could not get it to work.
However, reading through this forum, I followed your link to the 8.18.8 driver. It worked perfectly for me, on this clean install of Kubuntu. I do have a newer LCD 19" panel, if that helps. And it locked right into 1280x1024 @60 'native'.

drew@OSS:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 XT Generic OpenGL version string: 1.3.5395 (X4.3.0-8.18.8)

drew@OSS:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
16084 frames in 5.0 seconds = 3216.704 FPS
16038 frames in 5.0 seconds = 3207.506 FPS
20331 frames in 5.0 seconds = 4066.150 FPS

drew@OSS:~$ fgl_glxgears
Using GLX_SGIX_pbuffer
2423 frames in 5.0 seconds = 484.600 FPS
2995 frames in 5.0 seconds = 599.000 FPS
2976 frames in 5.0 seconds = 595.200 FPS
3002 frames in 5.0 seconds = 600.400 FPS
Did not realize how much effect moving the mouse had on this test.
Again, Thank You. :D

Now, could you build a how to on installing nvidia nforce 2 chipset update install? :razz:

[mlomker]

Now, could you build a how to on installing nvidia nforce 2 chipset update install? :razz:

I've thought about buying a desktop with an Nvidia card but I'm saving up for a Caribbean cruise this Winter. :p

[zachtib]

thanks, boosted my glxgears score by almost 300

[Cuppa-Chino]

But old problems started again, causing the screen to freeze completely except for the mouse cursor.


Yup. fglrx does not support power management. ATI states that in their FAQ's. You'll have to choose.

Those two in any way related? I also have freezes. Furthermore I sometimes seem to have power management problems with P4 2.4GHz C 800MHz FSB, Asus P4P800 & Ati Radeon 9500 (sometimes @9700 - but that does not matter to freezes)

Any idea how to turn power management off to fix the ATI issue....

[mlomker]

Any idea how to turn power management off to fix the ATI issue....

I was referring to hibernation on laptops. I doubt that is the problem that you are having. You can disable power management in your system's BIOS (usually F10 or DEL at boot-up).

[Grimlock]

I have installed the new drivers, but when I do fglrxinfo I get this?

richienation@richie:~$ fglrxinfo
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual!

This is my xorg.conf


# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "dbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Driver "fglrx"
BusID "PCI:1:0:0"
VideoRam 256000
Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "L1715S"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Radeon 9600 (R300 AP)"
Monitor "L1715S"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"


Anyone got any ideas??

[Septor]

I have installed the new drivers, but when I do fglrxinfo I get this?

richienation@richie:~$ fglrxinfo
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual!

This is my xorg.conf


Section "Module"
Load "dbe"
EndSection

Anyone got any ideas??


You need to load modules "glx" and "dri" in your xorg.conf Modules section.

[Grimlock]

Thank you, that's sorted the problem.

[sciurus]

When I first installed Breezy, xorg.conf included the following:

Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

When I reconfigured after installing fglrx, I wasn't sure what modules to include. I went with the ones listed below based on their inclusion in the ouput of an online tool for generating xorg configurations using fglrx:

Section "Module"
Load "dbe"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "type1"
EndSection

My problem is that xvimagesink no longer works. Could this be caused by my current module configuration? I can't find enough documentation online to tell what each module does, so I don't know what to add or remove. For now I changed my video output in the multimedia systems selector to XWindows(no xv), but it's unusably slow.

[mlomker]

Mine is this, but I'm not familiar with your application. You might wish to start another thread for your question.


Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

[fonkypij]

Hi guys... Nice tutorial but... I still got a weird problem with this fglrx stuff. How come Planet Penguins runs ssloooooww (so slow that I just couldn't click on the quite button) although I got both fglrx and direct rendering? :

fonkypij@delpij:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON X700 Generic
OpenGL version string: 1.3.5395 (X4.3.0-8.18.8)

fonkypij@delpij:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
[...]

Any idea? This is kinda special... I also tryed Atunnel GL screensaver from Xscreensaver... And it runs at about 0.8 fps! WoOow :???: Is there a fix for this?

[mlomker]

Any idea? This is kinda special... I also tryed Atunnel GL screensaver from Xscreensaver... And it runs at about 0.8 fps! WoOow :???: Is there a fix for this?

glxgears is the only tool that I've used for benchmarking. You should make a post to one of the gaming forums where more people will see it.

[jsteidl]

Hello There!

I was running my r300-card with mesa and had defntl NO fun with tuxracer .. erm sorry ... planet-penguin-racer (what sick name is that btw? ;))

anyway, it works now good with fglrx and i can play that sick-named game with good framerates.

only problem is: i tried to open totem after setting up fglrx and it gave me an error. so i went to the gnome-configuration-dialog for the multimedia system and picked another sink. okay. totem started. only problem is: movies that worked fine before are now out of sync and jerky... the problem with the non-starting totem was mentioned here (http://ubuntuforums.org/showpost.php?p=445582&postcount=109)
but i didnt saw anybody reply to that problem... so is there a way to please totem with a working sink, because i am using ximagesink at the moment.. but that does not please me.

another problem with mplayer.. the program says that it was unable to find /dev/3dfx

any ideay?

thanks for the manual btw!! :)

[BoneyOne]

Ok, I'm at a loss here.

I'm running on an AMD64 system with the X800XL using PCI-E.

Obviously it is not detected normally so I'm using the vesa driver to startx.
I've loaded the 8.19.10_amd64 drivers and used the above process (page1).

After several attempts I finally got all the way through the process without any errors....or so I though. When I restarted X...no card/monitor found.

Had to go back to the vesa drivers...

Any ideas?

Oh, guess I should tell everyone I'm a linux newb as well.

[fonkypij]

Hello,

Try the latest drivers install @ http://ubuntuforums.org/showthread.php?t=78466

Then pay attention to the monitor configuration. Sometimes it is all about frequency.

Could you show us the bottom of your error's output?

[andars]

Thanks for the great guide, I just changed Driver from "ati" to "fglrx" and it works great.


anders@server-llama:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X800 XT Platinum Edition Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)


anders@server-llama:~$ glxgears
53889 frames in 5.0 seconds = 10777.697 FPS
53822 frames in 5.0 seconds = 10764.339 FPS
51874 frames in 5.0 seconds = 10374.663 FPS

[mlomker]

any errors....or so I though. When I restarted X...no card/monitor found.

Then your xorg.conf file is wrong. Try the dpkg-reconfigure thing again.

[mlomker]

another problem with mplayer.. the program says that it was unable to find /dev/3dfx


I only use amaroK...I'm a KDE guy. You should start another thread after searching to see if there is an existing one. It's probably a problem with the driver and not the installation...I can't do anything about that.

[BLTicklemonster]

mloker: thanks. Now I have to reinstall Ubuntu again. yet again, I was stuck at the black screen of white letters de la morte. sudo nano dpkg-reconfigure did no good again.

I think I'll just get everybody in the house nvidia cards for christmas and take a pair of needle nose pliers to the ati cards.


No wait, didn't ati cards work in hoary? If so, I wonder where I can download it?

[yarbys]

Hi. I have a Radeon X850XT PE, and I can't get the fglrx module to load. lsmod doesn't list it.

dmesg:
$ dmesg | grep fglrx
[4295426.667000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4295426.669000] [fglrx] Maximum main memory to use for locked dma buffers: 929 MBytes.
[4295426.669000] [fglrx:firegl_init] *ERROR* Device not found!

lspci:
$ lspci | grep -i ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4b4c
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 4b6c

[BLTicklemonster]

mloker: thanks. Now I have to reinstall Ubuntu again. yet again, I was stuck at the black screen of white letters de la morte. sudo nano dpkg-reconfigure did no good again.

I think I'll just get everybody in the house nvidia cards for christmas and take a pair of needle nose pliers to the ati cards.


No wait, didn't ati cards work in hoary? If so, I wonder where I can download it?


Finally got it working. I followed the how to (again) but this time from a fresh install and paid attention to detail and found out some things that weren't right. Once I corrected them (see my post in the discussion thread) it installed nicely. Finally!

Thanks in the above post wasn't meant like "thanks, you made me blah blah blah" it was meant like thanks for not screaming at me lol.

[souled]

Once I corrected them (see my post in the discussion thread) it installed nicely. Finally!


Where is this discussion thread might I ask?

[jecos]

mloker: thanks. Now I have to reinstall Ubuntu again. yet again, I was stuck at the black screen of white letters de la morte. sudo nano dpkg-reconfigure did no good again.

I think I'll just get everybody in the house nvidia cards for christmas and take a pair of needle nose pliers to the ati cards.


No wait, didn't ati cards work in hoary? If so, I wonder where I can download it?
because you can't modify xorg.conf in a command line..your gonna reinstall *sigh* You should never have to re-install unless you mess up your grub conf. then you can just boot a live cd and fix it.
"sudo nano -w /etc/X11/xorg.conf" change driver to "ati" for safe mode then "fglrx" when you have fglrx installed.

[BLTicklemonster]

because you can't modify xorg.conf in a command line..your gonna reinstall *sigh* You should never have to re-install unless you mess up your grub conf. then you can just boot a live cd and fix it.
"sudo nano -w /etc/X11/xorg.conf" change driver to "ati" for safe mode then "fglrx" when you have fglrx installed.
Easy for you to *yawn* say.

"have to" and "rather just do that than beat my head against the wall for 5 minutes longer looking for information on how to save 5 minutes"....

[BLTicklemonster]

Where is this discussion thread might I ask?

How to:
http://ubuntuforums.org/showpost.php?p=423584

Discussion:
http://ubuntuforums.org/showthread.php?t=76116

[jecos]

Hi. I have a Radeon X850XT PE, and I can't get the fglrx module to load. lsmod doesn't list it.

dmesg:
$ dmesg | grep fglrx
[4295426.667000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4295426.669000] [fglrx] Maximum main memory to use for locked dma buffers: 929 MBytes.
[4295426.669000] [fglrx:firegl_init] *ERROR* Device not found!

lspci:
$ lspci | grep -i ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4b4c
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 4b6c


check out rage3d.com linux forums theres a fix you add a line to your xorg.conf

[jecos]

Easy for you to *yawn* say.

"have to" and "rather just do that than beat my head against the wall for 5 minutes longer looking for information on how to save 5 minutes"....

That time taken to properly learn a simple command line will save you in the long run...unless you want to never learn anything. Linux is about learning. Its free but sometimes at the cost of usability(works but isn't point and click)

[BLTicklemonster]

That time taken to properly learn a simple command line will save you in the long run...unless you want to never learn anything. Linux is about learning. Its free but sometimes at the cost of usability(works but isn't point and click)


I'm feelling very enlightened now, thank you. So is this what all newcomers to linux are to be told? If it doesn't work, learn how to make it work? Then why did arnieboy make Automatix? Why is there ubuntu? But yes, in the meantime, commands are to be learned, and I have a gazillion of them in my pm box back at the legion so I can reference them whenever I need to.

I just tried this again here at work with a machine we had sitting around, and it totally failed. Guess what? I'm going to reinstall again!!! And do you want to know why? Because of the same reason I did it last night; I don't have time to sit and nit pick. While UB is installing, I can be doing other things, but if I hunt and peck and search through tons of cryptic gobbledygook, I will totally waste time. Same here, I can sit here and spam a- er post in the forum and look for other stuff I'm working on besides UB while the machine is back there getting itself back into it's pristine state. I spent 9 HOURS last night getting the other machine working. And don't go off on me about learning, look at my post, and tell me I would have figured any of that out if I weren't learning.

Thank you.

[jc87]

Noob question :

sudo dpkg-reconfigure xserver-xorg #Select the ATI driver

How do i write this code exactly:???: .

For example i tryed :

sudo dpkg-reconfigure xserver-xorg #fglrx-8.16.20

sudo dpkg-reconfigure xserver-xorg fglrx-8.16.20

is any of theese correct? if not what is the correct one ?

And still no 3d acelaration , before i check the xorg.conf file i would like to see if the command im doing is right:eek:

[BLTicklemonster]

Just type

sudo dpkg-reconfigure xserver-xorg

and follow the instructions, don't let it choose the graphic card, choose it yourself.

[mlomker]

And still no 3d acelaration , before i check the xorg.conf file i would like to see if the command im doing is right:eek:

The # and everything after it is just a comment. If you typed it in that way then the system would ignore the comment and execute the command normally. All of the commands are entered at a terminal prompt.

[souled]

WOW, I just tried this Howto again and it worked... I've tried it before and it didn't work. This time, I did sudo apt-get clean before I download the files... Don't know if that really made a difference though. About that color problem I had before... I think it was fixed when I enabled this Option "UseFBDev" "true" Can't remember what option it was in the dpkg reconfigure thing but that's the entry in my xorg.conf. Yay, I'm all back to normal now. Thanks for all the work you do mlomker!

[Robocoastie]

System: Dell Dimension 5100
CPU: Pentium4 HT EM64T 2.8GHz
Ram: 1.6 GB Video Card: ATI Radeon X300 with 128MB memory
Ubuntu 5.10 64bit

Problem: after install X won't start
References to solve: this thread, ATI instructions and ATI driver:
ati-driver-installer-8.19.10-x86_64.run and Ubuntu FAQ 4.3 "How do I Install 3D ATI video card driver?"

I've walked through all these steps with limited success. The instructions at Ubuntur FAQ 4.3 resulted in the same x server crash.

A combination of the original post and ATI's instructions however gets me into Gnome at least but fglrxinfo reveals the same mesa driver that others in this thread keep getting:

rob@dell5100:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
rob@dell5100:~$

also the kernel is seeing the card:

rob@dell5100:~$ lspci | grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5b60
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 5b70
rob@dell5100:~$

I installed the .deb's that sudo sh ./ati-* creates:
fglrx-control_8.19.10-1_amd64.deb, fglrx-kernel-source_8.19.10-1_amd64.deb
fglrx-sources_8.19.10-1_amd64.deb
xorg-driver-fglrx_8.19.10-1_amd64.deb
xorg-driver-fglrx-dev_8.19.10-1_amd64.deb

(of course the fglrx-control one has to be last to be installed)

I then ran fglrxconfig and accepted all the defaults ---could the problem be with the options such as DRI ?? I know when an nvidia card is installed that needs to be commented out but what about with this?

grrr I want to include the xorg.0.log file and my xorg.conf but I keep getting "too big" errors when I try to attach.

****edit/Update***
ok it gets weirder... I tried the "Easy multimedia installer" I learned about from: http://ubuntuforums.org/showthread.php?t=84742
and I noticed that DRI wasn't selected, - as instructed I left it alone and used all defaults. A reboot resulted in x server crash.
I then figured the problem was the Load "init10" line so I commented that out and rebooted again. That fixed the x crash and low and behold my desktop was actually at 1280x1024! But relax... still stuck at mesa3d see:

rob@dell5100:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

rob@dell5100:~$

[mlomker]

System: Dell Dimension 5100


Did you replace the libdri.a file, as in my how-to? If not, then none of the drivers are going to work on 64-bit.

It's more useful to look at /var/log/kern.log and Xorg.0.log than the others.

[Robocoastie]

aye I replaced the libdri.a

all my steps were done from command line, I had jotted down the web addy from your link and used wget.

I was just reading the conversation thread regarding this and some other people mentioned needing to install headers (why aren't these installed in the first place?) and one person said on the steps during the fglrxconfig process that they said Y to "do you want to initialize xfree86-dga (i had used default n) and said yes to "do you want to use the external AGP GART module (i had used default n).

Since my rig is PCIExpress video though wasn't the "n" for AGP GART the correct answer?

thanks,
Rob

edit/add: oh I wanted to attach the log but I keep getting the message that its too big to attach. I'm not sure what parts can be excluded, I'll post it to my web site in a minute and just link to it...

[BLTicklemonster]

Question, herr mmloker, oh wise one:

if I go changing video cards, xserver will fail, and I just reconfigure, right? then install the correct drivers?

[Robocoastie]

ok I'm now working from a clean install. Same thing happens with x server crash so I'm working from command line strictly here.

when i attempt to remove old fglrx driver it fails saying there is no fglrx installed. (hence the x server crash after install I imagine). So I move right along and am able to remove linux-restricted-modules-$(uname -r). performing sudo dpkg-reconfigure xserver-xorg and selecting ATI I didn't bother with because I still got a x server crash the last time so skipped that.


I then apt-get install fakeroot debhelper build-essential make gcc-3.4 libstdc++5
which seemed to work, but just as last time I got an error message when I tried to apt-get install build-essential saying "Package module-assistant is not available But is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source." (same message later when I tried to sudo module-assistant prepare) Also I did apt-get install linux-headers-2.6.12-9 and apt-get install linux-headers-2.6.12-9-amd64-generic.

I then followed the steps you gave for libdri.a and ran fglrxconfig all defaults but said y to initialize xfree86-dga and external AGP GART module (again, I don't know if this is right or what to select for these parts really).

Rebooted - which got me into gnome but at 1024x768 and fglrxinfo said mesa graphics again (no surprise).

Been at this so many times now my brains fried heh.

Oh, while I'm at it which kernel header files for sure should I be d/loading? Does the *amd64-generic one have smp compiled in?

thanks,

[BLTicklemonster]

I caved in and put my son's windows hd back in. I'll get him an nvidia card for christmas, this isn't worth keeping him from having fun on his machine. I'm sure it will all be fixed later on.


(again I ask, wasn't hoary better with ati than breezy?)

[mlomker]

other people mentioned needing to install headers (why aren't these installed in the first


Not for Breezy's 8.16.20. You need them to compile the newer ones. moduel-assistant in my how-to for the latest driver will do that for you.

Since my rig is PCIExpress video though wasn't the "n" for AGP GART the correct answer?

It doesn't matter what you select for that. Ubuntu has the built-in gart and the driver will use it. I assume it doesn't matter at all with PCI-E, as you said. I have an older card, so I'm speculating there.

[mlomker]

if I go changing video cards, xserver will fail, and I just reconfigure, right? then install the correct drivers?

Sure. You could make the change before you power down to swap the card. I'd probably just pick 'vesa' because it works with almost all cards (it isn't 3D but gets you a desktop). You can switch to another driver after you install the other card.

[mlomker]

Oh, while I'm at it which kernel header files for sure should I be d/loading? Does the *amd64-generic one have smp compiled in?


I'm not sure why we're discussing the latest drivers in the thread for Breezy's included drivers. You need to apt-get install module-assistant. That will download the proper headers when you do the prepare step.

This is the how-to (http://ubuntuforums.org/showthread.php?t=78466) and the other discussion thread is linked at the top of it.

[Robocoastie]

Hi mloker,


I'm not sure why we're discussing the latest drivers in the thread for Breezy's included drivers. You need to apt-get install module-assistant. That will download the proper headers when you do the prepare step.

the reason was that I couldn't I got an error when I tried to apt-get module-assistant so it wasn't included for me for some reason. So I thought I was going to have to build it the mepis way which involves mucking with the linux kernel.

At any rate I have this partially working now. Here's what I did different from previously described:

1. clean installed 32bit version instead of 64
2. switched to 686-smp kernel and d/loaded headers for that
3. again I was able to get to the desktop at least but stuck with mesa drivers still but that let me enable the universe repositories and then was able to apt-get module-assistant.
4. I was then able to follow your kernel driver steps with success. ran aticonfig --initial
5. ran fglrxconfig BUT I'm not sure what to choose for:
Do you want to initialize xfree86-dga (y/n)? [n]
Do you want to use the external AGP GART module (y/n)? [n]
(my card is PCIExpress further confusing me on this)
Do you want to enable "AGP Locked User Pages" (y/n)? [y]
Which storage method do you want to use? [0]

In any case I chose the defaults for these.

glxgears however is running turtle slow though which sets an alarm off in my head. Painfully slow one can count the revolutions by hand its that slow. But I am running at 1280x1024 at least, so it all seems to be working other than that. Next I'll try it with 64bit on my other partition.


enable AGP GART?,

[mlomker]

The defaults should work fine. Are you using glxgears -printfps? What is the result? fglrxinfo will also tell you if it is working. If it's not then you'll need to look at /var/log/kern.log and Xorg.0.log for errors.

[BLTicklemonster]

Sure. You could make the change before you power down to swap the card. I'd probably just pick 'vesa' because it works with almost all cards (it isn't 3D but gets you a desktop). You can switch to another driver after you install the other card.

Great, because I'm going to try the ati on my machine, it's a better motherboard, so it may handle the card better, and put the nvidia on his machine. Thanks tons, dude.

[Robocoastie]

The defaults should work fine. Are you using glxgears -printfps? What is the result? fglrxinfo will also tell you if it is working. If it's not then you'll need to look at /var/log/kern.log and Xorg.0.log for errors.

well I'll be a bat in a bellry! talk about appearances can be deceiving! I didn't know about the -printfps I'd always just killed it after a few seconds and then saw what it printed. Here's my -printfps result (minus many lines that averaged the same)

rob@dell5100:~$ glxgears -printfps
6468 frames in 5.0 seconds = 1292.478 FPS
7052 frames in 5.0 seconds = 1410.223 FPS
7043 frames in 5.0 seconds = 1408.574 FPS
7043 frames in 5.0 seconds = 1408.549 FPS
7044 frames in 5.0 seconds = 1408.726 FPS
7043 frames in 5.0 seconds = 1408.533 FPS
7044 frames in 5.0 seconds = 1408.651 FPS
7043 frames in 5.0 seconds = 1408.512 FPS
7044 frames in 5.0 seconds = 1408.615 FPS
7043 frames in 5.0 seconds = 1408.588 FPS
7043 frames in 5.0 seconds = 1408.458 FPS
7043 frames in 5.0 seconds = 1408.495 FPS


And my fglrxinfo:


rob@dell5100:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X300/X550 Series Generic
OpenGL version string: 1.3.5461 (X4.3.0-8.19.10)

rob@dell5100:~$


So it appears its all working afterall! Hurray! 3 cheers for mlomker! hip hip hurray!
This also proves that walking away and sleeping on a problem helps - it was only after I did that finally (2am'ish) that I saw on linuxquestions that others had the same problem finding module-assistant which led me to deduce (sp?) that the other repositories needed to be enabled. And walla! it became apt-get'able

[mlomker]

that the other repositories needed to be enabled. And walla! it became apt-get'able

That's a good point. I could add something about that to the how-to.

[windowsguy]

I get this error when I try to remove xorg-driver-fglrx.

I have everything working and my card was detected until I upgraded my kernel to k7 version. Now I cant even use the fglrxinfo command.

Thanks for the help,
Robert


windowsguy@windowsguy:~$ sudo apt-get remove xorg-driver-fglrx
Password:
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
xorg-driver-fglrx
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 19.3MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 125506 files and directories currently installed.)
Removing xorg-driver-fglrx ...
dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'
dpkg: error processing xorg-driver-fglrx (--remove):
subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
xorg-driver-fglrx
E: Sub-process /usr/bin/dpkg returned an error code (1)
windowsguy@windowsguy:~$

[mlomker]

dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'


AFAIK Breezy's driver doesn't have a diversion. Did you have 8.16.20 or a newer version installed? You could always sudo apt-get --force-yes remove but that's the sledgehammer approach.

[masingerz]

I have a radeon x300se and when I tried to use fglrx I found myself with no gui, (luckyly fglrx made a backup), and an error message that gdm was not configured appropriatly, so i had to "sudo killall gdm" and "sudo mv xorg.conf.bak xorg.conf" and then "sudo gdm" and it worked: I have a gui now, I still want to have good display, but i do not want to suffer so much.

(the actual backup was called xorg.conf.2005101021213, but i put xorg.conf.bak for illustration purpose)

[Hellaxe]

I Couldn't find the answer to my problem.
I've followed the how-to but x server doesn't start.
I attach the xorg.0.log to see if anyone can tell me what am i doing wrong.
My video card is a Mobility M7 LW from the IBM Thinkpad R51. The laptop says it's a 9000.

[mlomker]

I attach the xorg.0.log to see if anyone can tell me what am i doing wrong.
My video card is a Mobility M7 LW from the IBM Thinkpad R51. The laptop says it's a 9000.

I didn't see anything in there but that wasn't the complete log. You'll also want to look in /var/log/kern.log for messages relating to the fglrx module loading.

Are any error messags printed to the screen when it fails? You should be able to Ctrl-Alt-F2 and run startx from the prompt. At least when it crashes you should see some errors on the screen.

[Hellaxe]

This is the second part of the log. Sorry but i'm still a noob and can't undertand the ati stuff.The other log íll see it tomorrow. bed time now. thanks

II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga
(II) R128: Driver for ATI Rage 128 chipsets:
ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP),
ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI),
ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP),
ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP),
ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP),
ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP),
ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP),
ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI),
ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI),
ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP),
ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP),
ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP),
ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP),
ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP),
ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP),
ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP),
ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP),
ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
ATI Rage 128 Pro ULTRA TU (AGP?)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330/340/350 (A4) 4137,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP),
ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP),
ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835, ATI Radeon 9100 PRO IGP 7834,
ATI Radeon Mobility 9200 IGP 7835, ATI Radeon 9200PRO 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP),
ATI FireGL RV360 AV (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI RADEON 9650,
ATI Radeon 9800SE AH (AGP), ATI Radeon 9800 AI (AGP),
ATI Radeon 9800 AJ (AGP), ATI FireGL X2 AK (AGP),
ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE),
ATI Radeon Mobility X600 (M24) 3150 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireGL D1100 (RV370) 5B65 (PCIE),
ATI Radeon Mobility M300 (M22) 5460 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI RADEON XPRESS 200 Series,
ATI RADEON XPRESS 200M Series, ATI RADEON XPRESS 200 Series,
ATI RADEON XPRESS 200M Series, ATI RADEON XPRESS 200 Series,
ATI RADEON XPRESS 200M Series, ATI RADEON XPRESS 200 Series,
ATI RADEON XPRESS 200M Series, ATI FireGL V5000,
ATI MOBILITY FireGL V5000, ATI MOBILITY FireGL V5000,
ATI MOBILITY RADEON X700, ATI MOBILITY RADEON X700,
ATI RADEON X700 PRO, ATI RADEON X700 XT, ATI RADEON X700,
ATI RADEON X700 SE, ATI RADEON X700 SE,
ATI Radeon X800 (R420) JH (AGP), ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800XT (R420) JP (AGP), ATI RADEON X800 SE,
ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI FireGL V7200 (R423) UQ (PCIE), ATI FireGL V5100 (R423) UR (PCIE),
ATI FireGL V7100 (R423) UT (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE), ATI FireGL V7100,
ATI MOBILITY FireGL V5100, ATI MOBILITY RADEON X800,
ATI MOBILITY RADEON X800 XT, ATI RADEON X800, ATI RADEON X800 XL,
ATI RADEON R430 SE, ATI RADEON R430 XTP, ATI RADEON R480 4P,
ATI RADEON R480 GL 16P, ATI RADEON R480 SE, ATI RADEON X850 PRO,
ATI RADEON X850 XT, ATI RADEON X850 XT Platinum Edition,
ATI RADEON X850 PRO, ATI RADEON X850 SE, ATI RADEON X850 XT,
ATI RADEON X850 XT Platinum Edition
(II) Primary Device is: PCI 01:00:0
(II) ATI: Candidate "Device" section "ATI Technologies, Inc. Radeon Mobility 9000 (M7 LW)".
(--) Chipset ATI Radeon Mobility M7 LW (AGP) found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xc0214000 - 0xc0214fff (0x1000) MX[B]
[6] -1 0 0xc0200000 - 0xc020ffff (0x10000) MX[B]
[7] -1 0 0xc0220000 - 0xc023ffff (0x20000) MX[B]
[8] -1 0 0xc0210000 - 0xc0213fff (0x4000) MX[B]
[9] -1 0 0xc0215000 - 0xc02157ff (0x800) MX[B]
[10] -1 0 0xc0000800 - 0xc00008ff (0x100) MX[B]
[11] -1 0 0xc0000c00 - 0xc0000dff (0x200) MX[B]
[12] -1 0 0x20000000 - 0x200003ff (0x400) MX[B]
[13] -1 0 0xc0000000 - 0xc00003ff (0x400) MX[B]
[14] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[15] -1 0 0xc0100000 - 0xc010ffff (0x10000) MX[B](B)
[16] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B)
[17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[18] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[19] -1 0 0x00008000 - 0x0000803f (0x40) IX[B]
[20] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]
[21] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]
[22] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]
[23] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]
[24] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[25] -1 0 0x00001860 - 0x0000186f (0x10) IX[B]
[26] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[27] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[28] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]
[29] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B)
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) Module radeon: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 4.0.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
(II) resource ranges after probing:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xc0214000 - 0xc0214fff (0x1000) MX[B]
[6] -1 0 0xc0200000 - 0xc020ffff (0x10000) MX[B]
[7] -1 0 0xc0220000 - 0xc023ffff (0x20000) MX[B]
[8] -1 0 0xc0210000 - 0xc0213fff (0x4000) MX[B]
[9] -1 0 0xc0215000 - 0xc02157ff (0x800) MX[B]
[10] -1 0 0xc0000800 - 0xc00008ff (0x100) MX[B]
[11] -1 0 0xc0000c00 - 0xc0000dff (0x200) MX[B]
[12] -1 0 0x20000000 - 0x200003ff (0x400) MX[B]
[13] -1 0 0xc0000000 - 0xc00003ff (0x400) MX[B]
[14] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[15] -1 0 0xc0100000 - 0xc010ffff (0x10000) MX[B](B)
[16] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B)
[17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[21] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[22] -1 0 0x00008000 - 0x0000803f (0x40) IX[B]
[23] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]
[24] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]
[25] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]
[26] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]
[27] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[28] -1 0 0x00001860 - 0x0000186f (0x10) IX[B]
[29] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[30] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[31] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]
[32] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B)
[33] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[34] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) RADEON(0): MMIO registers at 0xc0100000
(II) RADEON(0): PCI bus 1 card 0 func 0
(**) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon Mobility M7 LW (AGP)" (ChipID = 0x4c57)
(--) RADEON(0): Linear framebuffer at 0xe0000000
(--) RADEON(0): VideoRAM: 32768 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Reloading /usr/X11R6/lib/modules/libi2c.a
(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): Legacy BIOS detected
(II) RADEON(0): Connector0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-4
(II) RADEON(0): Connector1: DDCType-3, DACType-0, TMDSType--1, ConnectorType-2
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0):
(II) RADEON(0): Primary:
Monitor -- LVDS
Connector -- DVI-D
DAC Type -- TVDAC/ExtDAC
TMDS Type -- Internal
DDC Type -- DVI_DDC
(II) RADEON(0): Secondary:
Monitor -- NONE
Connector -- VGA
DAC Type -- Primary
TMDS Type -- NONE
DDC Type -- VGA_DDC
(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=35000; xclk=18300
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Panel ID string: Samsung LTN150P1-L02
(II) RADEON(0): Panel Size from BIOS: 1400x1050
(II) RADEON(0): BIOS provided dividers will be used.
(II) RADEON(0): Total number of valid DDC mode(s) found: 0
(II) RADEON(0): Valid mode using on-chip RMX: 1400x1050
(II) RADEON(0): Total number of valid FP mode(s) found: 1
(--) RADEON(0): Virtual size is 1400x1050 (pitch 1408)
(**) RADEON(0): *Mode "1400x1050": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1400x1050" 108.00 1400 34208 34320 1688 1050 1052 1055 1063
(**) RADEON(0): Default mode "640x350": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "640x350" 108.00 640 34208 34320 1688 350 1052 1055 1063
(**) RADEON(0): Default mode "640x400": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "640x400" 108.00 640 34208 34320 1688 400 1052 1055 1063
(**) RADEON(0): Default mode "720x400": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "720x400" 108.00 720 34208 34320 1688 400 1052 1055 1063
(**) RADEON(0): Default mode "640x480": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "640x480" 108.00 640 34208 34320 1688 480 1052 1055 1063
(**) RADEON(0): Default mode "800x600": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "800x600" 108.00 800 34208 34320 1688 600 1052 1055 1063
(**) RADEON(0): Default mode "1024x768": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1024x768" 108.00 1024 34208 34320 1688 768 1052 1055 1063
(**) RADEON(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1152x864" 108.00 1152 34208 34320 1688 864 1052 1055 1063
(**) RADEON(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1280x960" 108.00 1280 34208 34320 1688 960 1052 1055 1063
(**) RADEON(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1280x1024" 108.00 1280 34208 34320 1688 1024 1052 1055 1063
(**) RADEON(0): Default mode "832x624": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "832x624" 108.00 832 34208 34320 1688 624 1052 1055 1063
(**) RADEON(0): Default mode "1280x768": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1280x768" 108.00 1280 34208 34320 1688 768 1052 1055 1063
(**) RADEON(0): Default mode "1280x800": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1280x800" 108.00 1280 34208 34320 1688 800 1052 1055 1063
(**) RADEON(0): Default mode "1152x768": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.2 Hz
(II) RADEON(0): Modeline "1152x768" 108.00 1152 34208 34320 1688 768 1052 1055 1063
(++) RADEON(0): DPI set to (100, 100)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
Skipping "/usr/X11R6/lib/modules/libfb.a:fbmmx.o": No symbols found
(II) Module fb: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(II) RADEON(0): AGP Fast Write disabled by default
(II) RADEON(0): Depth moves disabled by default
(II) Loading sub module "shadowfb"
(II) LoadModule: "shadowfb"
(II) Loading /usr/X11R6/lib/modules/libshadowfb.a
(II) Module shadowfb: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) RADEON(0): Page flipping disabled
(!!) RADEON(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xc0100000 - 0xc010ffff (0x10000) MX[B]
[1] 0 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B]
[2] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[3] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[7] -1 0 0xc0214000 - 0xc0214fff (0x1000) MX[B]
[8] -1 0 0xc0200000 - 0xc020ffff (0x10000) MX[B]
[9] -1 0 0xc0220000 - 0xc023ffff (0x20000) MX[B]
[10] -1 0 0xc0210000 - 0xc0213fff (0x4000) MX[B]
[11] -1 0 0xc0215000 - 0xc02157ff (0x800) MX[B]
[12] -1 0 0xc0000800 - 0xc00008ff (0x100) MX[B]
[13] -1 0 0xc0000c00 - 0xc0000dff (0x200) MX[B]
[14] -1 0 0x20000000 - 0x200003ff (0x400) MX[B]
[15] -1 0 0xc0000000 - 0xc00003ff (0x400) MX[B]
[16] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[17] -1 0 0xc0100000 - 0xc010ffff (0x10000) MX[B](B)
[18] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B)
[19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
[20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
[21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
[22] 0 0 0x00003000 - 0x000030ff (0x100) IX[B]
[23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[24] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[25] -1 0 0x00008000 - 0x0000803f (0x40) IX[B]
[26] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]
[27] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]
[28] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]
[29] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]
[30] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[31] -1 0 0x00001860 - 0x0000186f (0x10) IX[B]
[32] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[33] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[34] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]
[35] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B)
[36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[37] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(==) RADEON(0): Write-combining range (0xe0000000,0x2000000)
(II) RADEON(0): Dynamic Clock Scaling Disabled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) RADEON(0): [drm] DRM interface version 1.2
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0d63000
(II) RADEON(0): [drm] mapped SAREA 0xe0d63000 to 0xb5c71000
(II) RADEON(0): [drm] framebuffer handle = 0xe0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x3340; Card 0x1002/0x4c57]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xd0000000
(II) RADEON(0): [agp] Ring mapped at 0xb5b70000
(II) RADEON(0): [agp] ring read ptr handle = 0xd0101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0xb5b6f000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xd0102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb596f000
(II) RADEON(0): [agp] GART texture map handle = 0xd0302000
(II) RADEON(0): [agp] GART Texture map mapped at 0xb548f000
(II) RADEON(0): [drm] register handle = 0xc0100000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1408,5957)
(II) RADEON(0): Reserved area from (0,1050) to (1408,1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 4905
(II) RADEON(0): Will use back buffer at offset 0xb70000
(II) RADEON(0): Will use depth buffer at offset 0x1114000
(II) RADEON(0): Will use 9472 kb for textures at offset 0x16c0000
(II) RADEON(0): Render acceleration enabled
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
15 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 4902
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 11
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Generic Keyboard: XkbModel: "pc105"
(**) Option "XkbLayout" "pt"
(**) Generic Keyboard: XkbLayout: "pt"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 5
(II) Synaptics touchpad driver version 0.13.6
(--) Synaptics Touchpad auto-dev sets device to /dev/input/event2
(**) Option "Device" "/dev/input/event2"
(**) Option "HorizScrollDelta" "0"
(--) Synaptics Touchpad synaptics touchpad found
(**) Option "SendCoreEvents" "true"
(**) Synaptics Touchpad: always reports core events
(II) XINPUT: Adding extended input device "Synaptics Touchpad" (type: MOUSE)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
Synaptics DeviceInit called
SynapticsCtrl called.
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
(--) Synaptics Touchpad synaptics touchpad found
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0

[joshuapurcell]

I've looked through the log file, and everything looks great except for these things:

The EDID portion of /var/log/Xorg.0.log, where it eventually says "desktop setup not supported":(II) fglrx(0): Connected Display1: DFP on internal TMDS
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: SAM Model: bb Serial#: 1312960825
(II) fglrx(0): Year: 2003 Week: 38
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 38 vert.: 30
(II) fglrx(0): Gamma: 2.60
(II) fglrx(0): DPMS capabilities: Off; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.635 redY: 0.345 greenX: 0.295 greenY: 0.600
(II) fglrx(0): blueX: 0.140 blueY: 0.080 whiteX: 0.310 whiteY: 0.330
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) fglrx(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) fglrx(0): Monitor name: SyncMaster
(II) fglrx(0): Serial No: HCHW906010
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Specified desktop setup not supported: 8
(II) fglrx(0): Primary Controller - DFP on internal TMDS
(II) fglrx(0): Internal Desktop Setting: 0x00000004
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 21 modes found for primary display.
(--) fglrx(0): Virtual size is 1280x1024 (pitch 1280)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066

Also this warning in the same file:(WW) Ignoring request to load module GLcore

Here are the FPS printouts from glxgears and fgl_glxgears. From these numbers it seems everything is fine, but when I run these commands my processor goes to 97-99% useage every time:jeremy@breezy:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
26450 frames in 5.0 seconds = 5289.871 FPS
jeremy@breezy:~$ fgl_glxgears
5163 frames in 5.0 seconds = 1032.600 FPS

Here's some more info from the kernel log:jeremy@breezy:~$ more /var/log/kern.log | grep fglrx
Dec 5 22:24:20 localhost kernel: [ 2092.420660] [fglrx] Internal AGP support requested, but kernel AGP support active.
Dec 5 22:24:20 localhost kernel: [ 2092.420667] [fglrx] Have to use kernel AGP support to avoid conflicts.
Dec 5 22:24:20 localhost kernel: [ 2092.420673] [fglrx] AGP detected, AgpState = 0x1f000a1a (hardware caps of chipset)
Dec 5 22:24:20 localhost kernel: [ 2092.421288] [fglrx] AGP enabled, AgpCommand = 0x1f000312 (selected caps)
Dec 5 22:24:21 localhost kernel: [ 2092.500979] [fglrx] free AGP = 54800384
Dec 5 22:24:21 localhost kernel: [ 2092.500984] [fglrx] max AGP = 54800384
Dec 5 22:24:21 localhost kernel: [ 2092.500987] [fglrx] free LFB = 116387840
Dec 5 22:24:21 localhost kernel: [ 2092.500989] [fglrx] max LFB = 116387840
Dec 5 22:24:21 localhost kernel: [ 2092.500992] [fglrx] free Inv = 134217728
Dec 5 22:24:21 localhost kernel: [ 2092.500994] [fglrx] max Inv = 134217728
Dec 5 22:24:21 localhost kernel: [ 2092.500996] [fglrx] total Inv = 134217728
Dec 5 22:24:21 localhost kernel: [ 2092.500998] [fglrx] total TIM = 0
Dec 5 22:24:21 localhost kernel: [ 2092.501000] [fglrx] total FB = 0
Dec 5 22:24:21 localhost kernel: [ 2092.501002] [fglrx] total AGP = 16384

I have an Athlon64 3400+, 1GB RAM, and an ASUS Radeon 9800 XT. Could my processor alone give me these numbers? Is there anything I need to do about the unsupported desktop setup error? Why do I get the "Ingoring request to load module GLcore" warning?

Thanks for the helpful guide.

EDIT: While I'm posting, I thought I'd ask about this (since the kernel log above reminded me of it). Would adding this option to the device section of my xorg.conf file help? Option "UseInternalAGPGART" "no"
The above line isn't there now, but I'm not sure if it is useful to me or not... guess I'll try and find out.

[mlomker]

Could my processor alone give me these numbers?

No, MESA tops out at 500 fps on my box. If you're getting over 1k then the drivers are doing their thing.

Why do I get the "Ingoring request to load module GLcore" warning?

Some of the error messages in those logs are normal.

The above line isn't there now, but I'm not sure if it is useful to me or not... guess I'll try and find out.

It won't do anything on Ubuntu due to the way that the kernel is built.

The rest of your questions you'll have to ask on the Rage3D board. I'm not a programmer, I just try to keep the installation how-to's up to date.

[Hellaxe]

Hello people. A little help is welcome :)

[DarthFrog]

I'm Canadian and bought an ATI Radeon 9800 Pro because ATI is Canadian. Bad mistake! I *cannot* get it to do direct rendering in Breezy Kubuntu.

I'm running kernel 2.6.12-10-k7 (Athlon Mobile 2800+ CPU) and an Acer AL1914 LCD monitor.

In /var/log/Xorg.0.log, I get:
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP

and from dmesg, I see:
[4294724.498000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4294724.504000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4294724.504000] [fglrx] module loaded - fglrx 8.19.10 [Nov 9 2005] on minor 0
[4294724.539000] [fglrx] ACPI power management is initialized.
[4294771.877000] [fglrx] Internal AGP support requested, but kernel AGP support active.
[4294771.877000] [fglrx] Have to use kernel AGP support to avoid conflicts.
[4294771.877000] [fglrx] Kernel AGP support doesn't provide agplock functionality.
[4294771.877000] [fglrx] AGP detected, AgpState = 0x1f004e0b (hardware caps of chipset)
[4294771.878000] [fglrx:firegl_unlock] *ERROR* Process 7373 using kernel context 0
[4322061.643000] [fglrx:firegl_unlock] *ERROR* Process 16011 using kernel context 0
[4400624.678000] [fglrx:firegl_unlock] *ERROR* Process 11669 using kernel context 0
[4415135.119000] [fglrx:firegl_unlock] *ERROR* Process 17447 using kernel context 0

Kernel modules fglrx, agpgart and sis_agp are loaded.

According to ATI, the error "xf86_ENODEV" is not an issue with their fglrx driver, rather a problem with agpgart.

I'm a competent enough sysadmin but I'm damned if I can figure out what to do to get 3D hardware acceleration going with this ATI card. I've read the entire 19 pages :) of this thread with no joy.

I'm definitely missing something, I think. Can anyone offer guidance?

--
Cheers,
Rob

[mlomker]

According to ATI, the error "xf86_ENODEV" is not an issue with their fglrx driver, rather a problem with agpgart.

That's what I found in my searches as well...the fglrx driver uses a motherboard-specific AGP driver as its interface. Basically Ubuntu isn't playing quite right with your motherboard. Other than reading through the posts regarding that error on the Rage3D board, I'd also search for your motherboard model here and on there to see if there are known issues.

My laptop uses the sis_agp module:


mlomker@mlomkernote:/$ lsmod | grep agp
sis_agp 8644 0
amd64_agp 12296 1
agpgart 34888 3 fglrx,sis_agp,amd64_agp

[mlomker]

Hello people. A little help is welcome :)

You posted a log that is using the Radeon driver, which doesn't help us. You'll need to get the log from the failed bootup. Did you see post 182? Once you've gone over to another prompt you'll need to either examine the log file or copy it somewhere so you can post it later.

If you haven't figured out the command-line then I'd recommend you just put the video-driver thing on hold for a day or two and learn your way around linux first. Here's a command-line tutorial (http://linuxcommand.org/learning_the_shell.php) that I like.

[croken254]

here is a sample of the results, Awesome job guy's thanks...


10678 frames in 5.0 seconds = 2135.503 FPS
9546 frames in 5.0 seconds = 1909.029 FPS
10677 frames in 5.0 seconds = 2135.251 FPS
10600 frames in 5.0 seconds = 2119.991 FPS
kendall@ubuntu1:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)

[tedddee]

I'm having the same problems as HellAxe, laptop with the Mobility M7

http://s87055070.onlinehome.us/ted/Xorg.0.log

[soc]

it seems that i already tried thousands of different methods to install the newest fglrx, but since 8.20.8 the problem appeared that the screen turns black immediately after i click on log off/shutdown/reboot/...
i searched in different forums which proposed everytime different things.
i would be glad if somebody could answer me these questions:
1. in xorg.conf:
UseInternalAGPGART
YES or NO???
2. when configuring my kernel (2.6.15_rc4_ck1)
Device Drivers -> Charakter Devices -> /dev/agpgart (AGP Support)
i got told that i should set it to NO, but i can only build it into the kernel or as a module! what should i do?
3. Device Drivers -> Charakter Devices -> Direct Rendering Manager
should i choose MODULE or NO???
i would prefer a small and fast kernel with working 3d acceleration, so what should i do??
on linux-militia it is said
"In order to use the fglrx internal AGP support, you have to make sure that the kernel agpgart support is not active, i.e. it is not compiled into the kernel and the kernel modules are not loaded. If the fglrx kernel module detects that the kernel agpgart support is active, it will automatically use that even if its internal AGP support is requested in order to avoid conflicts that can cause problems under some circumstances."
so what?? is it important? which agp support should it use by the way? some say UseInternalAGPGART yes, other no!!
thanks in advance for all your help!
soc

[mlomker]

it seems that i already tried thousands of different methods to install

You should really be talking to the guys on Rage3D (www.rage3d.com/board/forumdisplay.php?f=88) if you are going to build a custom kernel.

It doesn't matter what you pick for the gart config on a Ubuntu kernel because it's built in and will use it regardless of setting.

[mlomker]

I'm having the same problems as HellAxe, laptop with the Mobility M7


Well, your Xorg.0.log file contains this line:


(--) PCI:*(1:0:0) ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] rev 0, Mem @ 0xf0000000/27, 0xef000000/16, I/O @ 0xd800/8, BIOS @ 0xeffe0000/17


The fglrx driver supports 8500+. Your laptop may be fairly new but IBM is famous for being conservative and therefore they use ancient video cards.

[tedddee]

ok, thanks for the reply :)

are there any other drivers i could use? or just stick with the default ati/mesa thingy?

[mlomker]

are there any other drivers i could use? or just stick with the default ati/mesa thingy?

I think that's the best that you can do. You're going to be very unhappy if you are a game player but you really don't need a fancy video card for everyday things (email, surfing, etc).

[tedddee]

was thinking of toying with quake2 on the laptop, but dont really need to i guess :)

leave that for the desktop

[Toontwnca]

I've seen a few other threads with similar results. I gather that it is the 9200 and older that most often see the problem.

Right. I have 9000 on a Toshiba notebook.
Locks up tighter than a drum. ](*,)

[mlomker]

Right. I have 9000 on a Toshiba notebook.
Locks up tighter than a drum.

Lock-ups are usually a hardware problem (Ctrl-Alt-F2 doesn't work). I think most cards from that era use shared memory and that could be a part of it.

Have you tried the latest driver (http://ubuntuforums.org/showthread.php?t=78466) yet? If that doesn't work then you could file a bug report.

[Toontwnca]

Lock-ups are usually a hardware problem (Ctrl-Alt-F2 doesn't work). I think most cards from that era use shared memory and that could be a part of it.

Have you tried the latest driver (http://ubuntuforums.org/showthread.php?t=78466) yet? If that doesn't work then you could file a bug report.

Yes I tried the new drivers as per your howto.
The install went smoothly; but no difference
on restart.

I did notice something odd in /etc/X11/xorg.conf:
that being two sections for drivers, one said 'ati'
the other said 'fglrx'.

On a side note; it is shared memory.
Computer only a year and a half old.
Similar to your IBM reference; new
computer, old card.
Will know better next time.:rolleyes:

[flabdablet]

This post on the Rage3D forum (http://www.rage3d.com/board/showpost.php?p=1333981360&postcount=18) nailed it for me.

If you've worked through the OP Howto, you still have the mesa driver active, and the result of

cat /proc/mtrr

looks like

reg00: base=0x00000000 ( 0MB), size=984064MB: write-back, count=1

with a similarly outrageously large size= value, it will probably nail it for you too (no size under /proc/mtrr should ever be larger than the amount of mainboard RAM you have).

mlomker, perhaps you could link to this in your troubleshooting section.

Razzafrazzin crabblfranchin garbage BIOS. I'm off to look for a flash upgrade...

[flabdablet]

For those who might be curious about what this particular failure looks like, here is the relevant part of my /var/log/Xorg.0.log:


(II) fglrx(0): [drm] loaded kernel module for "fglrx" driver
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xf8c5c000
(II) fglrx(0): [drm] mapped SAREA 0xf8c5c000 to 0xb7b5d000
(II) fglrx(0): [drm] framebuffer handle = 0xd0000000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.16.20
(II) fglrx(0): Date: Aug 16 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.12-10-686
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0xf9000000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xf8c5c000 at 0xb7b5d000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xd0000000 FBMappedSize: 0x08000000
(WW) fglrx(0): Failed to set up write-combining range (0xd0000000,0x8000000)
(II) fglrx(0): FBMM initialized for area (0,0)-(1152,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1152,864) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using hardware cursor (scanline 864)
(II) fglrx(0): Largest offscreen area available: 1152 x 7323
(**) Option "dpms"
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled



and my dmesg:


[4294731.756000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4294731.761000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4294731.761000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[4294731.761000] [fglrx] module loaded - fglrx 8.16.20 [Aug 16 2005] on minor 0
[4294731.776000] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
[4294731.776000] [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
[4294731.777000] [fglrx] Internal AGP support requested, but kernel AGP support active.
[4294731.777000] [fglrx] Have to use kernel AGP support to avoid conflicts.
[4294731.777000] [fglrx] Kernel AGP support doesn't provide agplock functionality.
[4294731.777000] [fglrx] AGP detected, AgpState = 0x1f004a1b (hardware caps of chipset)
[4294731.777000] mtrr: type mismatch for f0000000,8000000 old: write-back new: write-combining
[4294731.777000] [fglrx:firegl_unlock] *ERROR* Process 8342 using kernel context 0
[4294731.844000] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining


Here's the entire output of "cat /proc/mtrr":


reg00: base=0x00000000 ( 0MB), size=984064MB: write-back, count=1


It looks like the fglrx driver is trying to set up a couple of memory type range register entries that specify how to deal with the video memory, and can't do it because there's already an entry there that covers that address range. That entry is bogus (984064MB is just stupidly huge), and according to the the posting linked above (http://www.rage3d.com/board/showpost.php?p=1333981360&postcount=18) is caused by the system BIOS telling lies. It's in no way ATI's fault, all you nVidia boosters :) - what the driver is trying to do is quite reasonable.

That posting shows you how to set up a much more useful mtrr entry for your system RAM, covering only the RAM you actually have installed. This allows fglrx to set up its own entries without conflicts, and on my box at least gives me fully working 3D without needing to do anything terribly clever with drivers and without needing to hand-edit xorg.conf.

It's still a bit beyond Aunt Tillie though. Perhaps somebody with more Debian-fu than me (i.e. almost anybody) can make this problem go away with an automatic update.

[executer]

when i type "fglrxinfo" i get an error:

extension "XFree86-DRI" missing on display ":0.0".

What does it mean?

My hole output looks like this:

executer@executer:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

I am just trying to get 3ddesktop to work :)

[foxy123]

when i type "fglrxinfo" i get an error:

extension "XFree86-DRI" missing on display ":0.0".

What does it mean?

My hole output looks like this:

executer@executer:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

I am just trying to get 3ddesktop to work :)
means that you do not have ati drivers installed...

[executer]

I followed the how-to step-by-step.. Any idea why they are not installed?

[foxy123]

I followed the how-to step-by-step.. Any idea why they are not installed?
could you post your xorg.conf?

[executer]

Here it is:

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "no"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9500 Pro (R300 AD)"
Driver "ati"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "SyncMaster"
Option "DPMS"
Modeline "1280x800@60" 83.91 1280 1312 1624 1656 800 816 824 841
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Radeon 9500 Pro (R300 AD)"
Monitor "SyncMaster"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

[executer]

Another problem im having is that ubuntu start, and i get to the login screen. My
monitor goes black and says: Video mode not supported. So I have to do ctrl+alt+num+up to get another screen rezolution, which looks like crap.
Then I login, and everything is ok, running 1280x1024 resolution.

Is there a way to put the standard screen resolution on startup? Is that in the xorg.conf file, or?

[foxy123]

Here it is:

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9500 Pro (R300 AD)"
Driver "ati"
BusID "PCI:1:0:0"
EndSection

The driver here should be fglrx... You can try to change it manually if you know how to to change it back from the command line it it does not work....

[executer]

The driver here should be fglrx... You can try to change it manually if you know how to to change it back from the command line it it does not work....

So I set the "ati" to "fglrx". And no, how do I change it back from the command line if it does not work?

[executer]

I edited the xorg.conf to driver "fglrx" and then run:
sudo dpkg-reconfigure -phigh xserver-xorg
to update file.

But my fglrxinfo still looks like this:

Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

[foxy123]

So I set the "ati" to "fglrx". And no, how do I change it back from the command line if it does not work?
There is another tool which can help you to configure your xorg.conf, but I have never used it. Look through this and other ATI topics to find out how to do it.

If you decide to try to do it manually, then first make a backup of you current xorg.conf:
cd /etc/X11
sudo cp xorg.conf xorg.backup
then do the change.
If it does not work and you can't boot in graphic mode than login in text mode and do the reverse to what you have already done:
cd /etc/X11
sudo cp xorg.backup xorg.conf

you can either to reboot or run startx, I guess...

[foxy123]

I edited the xorg.conf to driver "fglrx" and then run:
sudo dpkg-reconfigure -phigh xserver-xorg
to update file.

But my fglrxinfo still looks like this:

Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
take a look at your xorg.conf if "fglrx2 is still there... I am not sure I know what dpkg-reconfigure does (never used it)...

[executer]

No, now its set back to "ati".

So this line error: Xlib: extension "XFree86-DRI" missing on display ":0.0".
means my ATI drivers are not installed u said?

[mlomker]

mlomker, perhaps you could link to this in your troubleshooting section.


Will do.

[foxy123]

No, now its set back to "ati".

So this line error: Xlib: extension "XFree86-DRI" missing on display ":0.0".
means my ATI drivers are not installed u said?
Try the howto from the beginning... I do not use this dpkg-reconfigure tool, frankly speaking so I do not know why you need it. I guess if you have the driver installed you just need to change ati to fglrx in your xorg.conf. However, if it's not then you'd better repeat the whole routine again starting with removing a possible driver....

[mlomker]

means that you do not have ati drivers installed...

You didn't provide enough details:


General Troubleshooting:
You can look through the /var/log/Xorg.0.log and kern.log file for troubleshooting most problems.

[foxy123]

You didn't provide enough details:
you're right...

[mlomker]

Is there a way to put the standard screen resolution on startup? Is that in the xorg.conf file, or?

Yes. You posted your xorg.conf in an earlier post and you had every possible resolution in it, by the looks of things. I only have one resolution in mine because I never change it.


SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection

[nelposto]

Hmm...

So I just compiled my own kernel based on 2.6.14, and tried to follow this guide to install the drivers.

fglrxinfo reports correctly my ATI card, glxgears performs wonderfully, but when I try to test with ppracer, it says it can't find a matching GLX visual.

Given that fglrxinfo gives the correct details and glxgears is fine, I'm not sure whether the problem is with my driver setup or ppracer....

I tried uninstalling the driver and then re-installing it under 2.6.12-10, successfully, but prracer gave the same error.

Any ideas?

[flabdablet]

Blarg. Nothing is ever easy :)

mlomker: when you post that link to the workaround, you'll need to tell people to name the symlink /etc/rcS.d/S03fix_mtrr instead of /etc/rcS.d/S02fix_mtrr. This is because /etc/rcS.d/S02mountvirtfs is already there, and if fix_mtrr also has an S02 prefix they race; mountvirtfs only wins some of the time, so fix_mtrr sometimes tries to write to regular file /proc/mtrr in the root filesystem (which is still mounted readonly) and generates errors instead of fixing problems (whew).

Bug 18506 (https://bugzilla.ubuntu.com/show_bug.cgi?id=18506) covers the bogus mtrr issue that affected me, and Bug 17644 (https://bugzilla.ubuntu.com/show_bug.cgi?id=17644) covers a related one.

[flabdablet]

executer: For more clues, have a look in /var/log/Xorg.0.log and see if there are any lines in there that start with (EE) or (WW). Also, try looking in /var/log/messages for lines containing [fglrx] and any nearby lines that look like error messages.

[mlomker]

I tried uninstalling the driver and then re-installing it under 2.6.12-10, successfully, but prracer gave the same error.


I'd recommend asking the question in the gaming forum. glxgears is as far as I go with the drivers...I don't play games.

[deepspring]

This is how I get my PCIE Radeon X600 Pro to behave itself and run properly, without lockups, usind the fglrx agpgart kernel driver, not the mainboard "intel_agp" agpgart kernel driver.

Firstly I backed up my files (important!)...

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
sudo cp /etc/modules /etc/modules.backup
sudo cp /etc/hotplug/blacklist /etc/hotplug/blacklist.backup

Then I did this...

sudo apt-get update
sudo apt-get install msttcorefonts
sudo fc-cache -f -v
sudo apt-get install xorg-driver-fglrx fglrx-control
sudo apt-get install linux-restricted-modules-$(uname -r)
sudo cat "fglrx" >> /etc/modules
sudo cat "intel_agp" >> /etc/hotplug/blacklist

Then I used the "sudo fglrxconfig" wizard to create a new xorg.conf file. I selected "No" for the option that reads something like "Use External AGP Driver", and selected "Yes" for the option that reads something like "Enable User Locked IO Pages".

When the wizard finished, it created a rather "raw" xorg.conf file, which lacked important things like font paths (bad!). So I opened both the backup xorg.conf file and the new xorg.conf file in gedit ("sudo gedit /etc/X11/xorg.conf /etc/X11/xorg.conf.backup").

I deleted the entire "Files" section from the new xorg.conf and copied the entire "Files" section from the backup copy of xorg.conf to the new one. I also added this entry to the section...

FontPath "/usr/share/fonts/truetype/msttcorefonts"

I also tweaked my display and monitor settings. Anyway... here is a copy of my new xorg.conf file (minus some of the rubbish):

# ************************************************** ********************
# DRI Section
# ************************************************** ********************
Section "dri"
Mode 0666
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).
#

FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
FontPath "/usr/share/fonts/truetype/msttcorefonts"

# The module search path. The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# ************************************************** ********************
# Server flags section.
# ************************************************** ********************

Section "ServerFlags"

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" "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" "pc104"
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/input/mice"

EndSection


# ************************************************** ********************
# Monitor section
# ************************************************** ********************

# Any number of monitor sections may be present

Section "Monitor"
Identifier "Monitor0"
HorizSync 30-96
VertRefresh 50-160
Option "DPMS"
DisplaySize 423 317 # 1600x1200

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"
VideoRam 262144
# ### 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" "(null)"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "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" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=5b62
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 "1600x1200"
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 ###

After rebooting my computer, my system was flying along without any problems...

See the attached text file if you need proof.

[mlomker]

This is how I get my PCIE Radeon X600 Pro to behave itself and run properly, without lockups, usind the fglrx agpgart kernel driver, not the mainboard "intel_agp" agpgart kernel driver.


The fonts aren't needed by the driver and you don't need fglrx in /etc/modules because it gets called out of the xorg.conf. You might want to specify /truetype instead of /truetype/msttcorefonts, since there are probably other fonts in that directory as well.

I do find it interesting that blacklisting the gart worked for you. I had tried it before by renaming the modules themselves and 3D fails to function without them. Perhaps it just works on your particular motherboard (or just Intel). I have an AMD64 and it uses two in its interface:


mlomker@mlomkernote:/etc/X11$ lsmod | grep fglrx
fglrx 438496 7
agpgart 34888 3 fglrx,sis_agp,amd64_agp


Following your instructions:


mlomker@mlomkernote:/etc/init.d$ dmesg | grep fglrx
[4294735.782000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4294735.782000] [fglrx] module loaded - fglrx 8.20.8 [Dec 6 2005] on minor 0
[4294735.814000] [fglrx] ACPI power management is initialized.
[4294736.361000] [fglrx] Failed to load fglrx_agp module
[4294736.361000] [fglrx] Error code 256
[4294736.361000] [fglrx] Failed to load ATI module agpgart
[4294736.361000] [fglrx] Fallback to internal agpgart module
[4294736.361000] [fglrx] Initialization of built-in AGP-support failed (ret=-19).
[4294736.362000] [fglrx:firegl_unlock] *ERROR* Process 7599 using kernel context 0
mlomker@mlomkernote:/etc/init.d$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)


I believe your results, but I won't add something to a how-to unless it works fairly universally...starting with my own laptop! :)

Thanks.

[deepspring]

The fonts aren't needed by the driver and you don't need fglrx in /etc/modules because it gets called out of the xorg.conf. You might want to specify /truetype instead of /truetype/msttcorefonts, since there are probably other fonts in that directory as well.

Actually, I found that some older applications became a little more responsive and the fonts appeared to be a lot smoother (especially websites and wine apps that required Arial or Tahoma) after adding the FontPaths from the original xorg.conf to the fglrxconfig generated xorg.conf.

But thats probably just me.

I do find it interesting that blacklisting the gart worked for you. I had tried it before by renaming the modules themselves and 3D fails to function without them. Perhaps it just works on your particular motherboard (or just Intel). I have an AMD64 and it uses two in its interface:


mlomker@mlomkernote:/etc/X11$ lsmod | grep fglrx
fglrx 438496 7
agpgart 34888 3 fglrx,sis_agp,amd64_agp


Following your instructions:


mlomker@mlomkernote:/etc/init.d$ dmesg | grep fglrx
[4294735.782000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4294735.782000] [fglrx] module loaded - fglrx 8.20.8 [Dec 6 2005] on minor 0
[4294735.814000] [fglrx] ACPI power management is initialized.
[4294736.361000] [fglrx] Failed to load fglrx_agp module
[4294736.361000] [fglrx] Error code 256
[4294736.361000] [fglrx] Failed to load ATI module agpgart
[4294736.361000] [fglrx] Fallback to internal agpgart module
[4294736.361000] [fglrx] Initialization of built-in AGP-support failed (ret=-19).
[4294736.362000] [fglrx:firegl_unlock] *ERROR* Process 7599 using kernel context 0
mlomker@mlomkernote:/etc/init.d$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)


I believe your results, but I won't add something to a how-to unless it works fairly universally...starting with my own laptop! :)

Thanks.

Sadly, I don't own an AMD64 system or a laptop for that matter to test it on, and I don't have a system with an onboard ATI IGP chipset either. We probably wont know if I'm the only one it works for unless others on different setups give it a shot.

However, in your case I'm willing to accept that it is going to be tricky to get it to work perfectly. I noticed that you didn't blacklist any of the other AGPgart drivers (??). You should be able try various configurations without harming your setup (*crossing fingers*).

Anyways, I have tried other config variations, such as...

I was greeted with terrible 3D performance for this configuration: No blacklisting of "intel_agp", no loading "fglrx" in "/etc/modules", disabled the "fglrx" builtin AGPgart in the xorg.conf file (option "UseInternalAGPGART" "no").

I was greeted with random lockups, as well as poor 3D performance with this configuration: blacklisting "intel_agp", no loading "fglrx" in "/etc/modules", enabled the "fglrx" builtin AGPgart in the xorg.conf file (option "UseInternalAGPGART" "yes").

I was greeted with lockups as soon as Gnome loaded with this configuration: no blacklisting "intel_agp", no loading "fglrx" in "/etc/modules", enabled the "fglrx" builtin AGPgart in the xorg.conf file (option "UseInternalAGPGART" "yes").

I was greeted with lockups as soon as Gnome loaded with this configuration: no blacklisting "intel_agp", loading "fglrx" in "/etc/modules", enabled the "fglrx" builtin AGPgart in the xorg.conf file (option "UseInternalAGPGART" "yes").

Others might have differing results.

I also found that 3D performance went up a notch or two when I specified how much memory my video card has in the xorg.conf file (VideoRam 262144).

That said my next video card is going to be an nVidia. :D

[mlomker]

I noticed that you didn't blacklist any of the other AGPgart drivers (??). You should be able try various configurations without harming your setup (*crossing fingers*).

Sure I did. The lsmod output was the 'before' picture. I tried disabling them individually and then both. sis_agp doesn't seem to affect anything when it is missing but the amd64 one will cause the driver to not work at all (as the output showed).

That said my next video card is going to be an nVidia. :D

They definitely have the upper-hand in performance right now, but I've talked to my counterparts that maintain the Nvidia how-to's and they tell me that it's just as bad. The video card wasn't the deciding factor for me--I'm an AMD fan and AMD laptops with Nvidia cards don't seem that common.

[deepspring]

Sure I did. The lsmod output was the 'before' picture. I tried disabling them individually and then both. sis_agp doesn't seem to affect anything when it is missing but the amd64 one will cause the driver to not work at all (as the output showed).

Well, I said it would be tricky.

The amd64_agp is probably some form of 64bit emulation driver or an instructional interface for other 32bit agpgart drivers.

You could try leaving the sis_agp driver blacklisted (not renamed), keep the amd64_agp driver loaded, add fglrx to "/etc/modules", modify your xorg.conf to use fglrx's internal agpgart.

If you get lockups or poor 3D performance, then you can just change things back...

They definitely have the upper-hand in performance right now, but I've talked to my counterparts that maintain the Nvidia how-to's and they tell me that it's just as bad. The video card wasn't the deciding factor for me--I'm an AMD fan and AMD laptops with Nvidia cards don't seem that common.

I have seen a few notebooks around with AMD processors and GeForce Go graphics chipsets. But these have always been really crap notebooks.

[eXSBass]

Does this guide work for the latest 8.19.10 drivers? If so do I need to change anything?

Thanks

[mlomker]

Does this guide work for the latest 8.19.10 drivers? If so do I need to change anything?


Nope. 8.20.8 is the latest. Use this. (http://ubuntuforums.org/showthread.php?t=78466)

[deepspring]

Didn't realise you had a howto for the latest drivers. I just installed and tested them using my config above (http://ubuntuforums.org/showpost.php?p=575778&postcount=224) , and so far they are working brilliantly...

scott@lazerus:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X600 PRO Generic
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)

scott@lazerus:~$ fgl_glxgears
Using GLX_SGIX_pbuffer
2004 frames in 5.0 seconds = 400.800 FPS
2423 frames in 5.0 seconds = 484.600 FPS
2404 frames in 5.0 seconds = 480.800 FPS
2429 frames in 5.0 seconds = 485.800 FPS
2421 frames in 5.0 seconds = 484.200 FPS
2415 frames in 5.0 seconds = 483.000 FPS
2366 frames in 5.0 seconds = 473.200 FPS

scott@lazerus:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
12504 frames in 5.0 seconds = 2500.649 FPS
12470 frames in 5.0 seconds = 2493.964 FPS
12471 frames in 5.0 seconds = 2494.178 FPS
12470 frames in 5.0 seconds = 2493.830 FPS
12472 frames in 5.0 seconds = 2494.313 FPS
12470 frames in 5.0 seconds = 2493.890 FPS
12471 frames in 5.0 seconds = 2494.136 FPS

scott@lazerus:~$ lsmod | grep agp
agpgart 34792 1 fglrx

scott@lazerus:~$ dmesg | grep fglrx
[4294683.464000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4294683.466000] [fglrx] Maximum main memory to use for locked dma buffers: 930 MBytes.
[4294683.466000] [fglrx] module loaded - fglrx 8.20.8 [Dec 6 2005] on minor 0
[4294683.488000] [fglrx] ACPI power management is initialized.
[4294707.608000] [fglrx] free PCIe = 54804480
[4294707.608000] [fglrx] max PCIe = 54804480
[4294707.608000] [fglrx] free LFB = 108908544
[4294707.608000] [fglrx] max LFB = 108908544
[4294707.608000] [fglrx] free Inv = 134217728
[4294707.608000] [fglrx] max Inv = 134217728
[4294707.608000] [fglrx] total Inv = 134217728
[4294707.608000] [fglrx] total TIM = 0
[4294707.608000] [fglrx] total FB = 0
[4294707.608000] [fglrx] total PCIe = 16384

scott@lazerus:~$ dmesg | grep agp
[4294683.389000] Linux agpgart interface v0.101 (c) Dave Jones

scott@lazerus:~$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1

scott@lazerus:~$ cat /var/log/Xorg.0.log | grep fglrx
(II) LoadModule: "fglrx"
(II) Loading /usr/X11R6/lib/modules/drivers/fglrx_drv.o
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(II) fglrx(0): pEnt->device->identifier=0x82128f0
(II) fglrx(0): === [R200PreInit] === begin, [s]
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "NoAccel" "no"
(**) fglrx(0): Option "NoDRI" "no"
(**) fglrx(0): Option "Capabilities" "0x00000000"
(**) fglrx(0): Option "CapabilitiesEx" "0x00000000"
(**) fglrx(0): Option "GammaCorrectionI" "0x00000000"
(**) fglrx(0): Option "GammaCorrectionII" "0x00000000"
(**) fglrx(0): Option "OpenGLOverlay" "off"
(**) fglrx(0): Option "VideoOverlay" "on"
(**) fglrx(0): Option "DesktopSetup" "(null)"
(**) fglrx(0): Option "HSync2" "unspecified"
(**) fglrx(0): Option "VRefresh2" "unspecified"
(**) fglrx(0): Option "ScreenOverlap" "0"
(**) fglrx(0): Option "UseInternalAGPGART" "yes"
(**) fglrx(0): Option "Stereo" "off"
(**) fglrx(0): Option "StereoSyncEnable" "1"
(**) fglrx(0): Option "UseFastTLS" "0"
(**) fglrx(0): Option "BlockSignalsOnLock" "on"
(**) fglrx(0): Option "ForceGenericCPU" "no"
(**) fglrx(0): Option "CenterMode" "off"
(**) fglrx(0): Option "FSAAScale" "1"
(**) fglrx(0): Option "FSAAEnable" "no"
(**) fglrx(0): Option "FSAADisableGamma" "no"
(**) fglrx(0): Option "FSAACustomizeMSPos" "no"
(**) fglrx(0): Option "FSAAMSPosX0" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY0" "0.000000"
(**) fglrx(0): Option "FSAAMSPosX1" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY1" "0.000000"
(**) fglrx(0): Option "FSAAMSPosX2" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY2" "0.000000"
(**) fglrx(0): Option "FSAAMSPosX3" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY3" "0.000000"
(**) fglrx(0): Option "FSAAMSPosX4" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY4" "0.000000"
(**) fglrx(0): Option "FSAAMSPosX5" "0.000000"
(**) fglrx(0): Option "FSAAMSPosY5" "0.000000"
(**) fglrx(0): Option "PseudoColorVisuals" "off"
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(**) fglrx(0): Gamma Correction for I is 0x00000000
(**) fglrx(0): Gamma Correction for II is 0x00000000
(==) fglrx(0): Buffer Tiling is ON
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(**) fglrx(0): Option "mtrr" "off"
(--) fglrx(0): Chipset: "RADEON X600 (RV380 5B62)" (Chipset = 0x5b62)
(--) fglrx(0): (PciSubVendor = 0x147b, PciSubDevice = 0x0002)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xe0000000
(--) fglrx(0): MMIO registers at 0xf1000000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 2.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI RV380
(II) fglrx(0): VESA VBE OEM Software Rev: 1.0
(II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: V380
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): Video RAM override, using 262144 kB instead of 262144 kB
(**) fglrx(0): VideoRAM: 131072 kByte, Type: DDR SGRAM / SDRAM
(II) fglrx(0): PCIE card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) fglrx(0): Connected Display1: CRT on primary DAC
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: GSM Model: 4a5b Serial#: 4671
(II) fglrx(0): Year: 2002 Week: 11
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) fglrx(0): Signal levels configurable
(II) fglrx(0): Sync: Separate Composite
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 36 vert.: 27
(II) fglrx(0): Gamma: 2.76
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): First detailed timing not preferred mode in violation of standard!(II) fglrx(0): redX: 0.638 redY: 0.326 greenX: 0.279 greenY: 0.602
(II) fglrx(0): blueX: 0.142 blueY: 0.063 whiteX: 0.282 whiteY: 0.298
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 720x400@88Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@87Hz (interlaced)
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) fglrx(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) fglrx(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) fglrx(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) fglrx(0): #5: hsize: 2048 vsize 1536 refresh: 60 vid: 16609
(II) fglrx(0): #6: hsize: 1600 vsize 1200 refresh: 70 vid: 19113
(II) fglrx(0): #7: hsize: 1600 vsize 1200 refresh: 75 vid: 20393
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 157.5 MHz Image Size: 350 x 262 mm
(II) fglrx(0): h_active: 1280 h_sync: 1344 h_sync_end 1504 h_blank_end 1728 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1072 v_border: 0
(II) fglrx(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 98 kHz, PixClock max 270 MHz
(II) fglrx(0): Monitor name: 900B
(II) fglrx(0): Monitor name:
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Specified desktop setup not supported: 8
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000004
(II) fglrx(0): POWERplay version 3. 4 power states available:
(II) fglrx(0): 1. 405/257MHz @ 50Hz [enable load balancing, overdrive]
(II) fglrx(0): 2. 304/257MHz @ 50Hz [enable load balancing, overdrive]
(II) fglrx(0): 3. 419/257MHz @ 50Hz [overclocked, enable load balancing, overdrive]
(II) fglrx(0): 4. 432/257MHz @ 50Hz [overclocked, enable load balancing, overdrive]
(**) fglrx(0): Qbs disabled
(==) fglrx(0): FAST_SWAP disabled
(**) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(**) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 49 modes found for primary display.
(--) fglrx(0): Virtual size is 1600x1200 (pitch 1600)
(**) fglrx(0): *Mode "1600x1200": 202.5 MHz (scaled from 0.0 MHz), 93.8 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250
(**) fglrx(0): Default mode "1600x1200": 162.0 MHz (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1600x1200" 162.00 1600 1664 1856 2160 1200 1201 1204 1250
(**) fglrx(0): Default mode "1280x1024": 157.5 MHz (scaled from 0.0 MHz), 91.1 kHz, 85.0 Hz
(II) fglrx(0): Modeline "1280x1024" 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
(**) fglrx(0): Default mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024" 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 119.7 MHz (scaled from 0.0 MHz), 77.1 kHz, 85.0 Hz
(II) fglrx(0): Modeline "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 +hsync
(**) fglrx(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864" 96.77 1152 1224 1344 1536 864 865 868 900 +hsync
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 +hsync
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 64.68 1152 1208 1328 1504 864 865 868 915 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 58.29 1152 1200 1320 1488 864 865 868 911 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 143.5 MHz (scaled from 0.0 MHz), 91.5 kHz, 100.0 Hz
(II) fglrx(0): Modeline "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 +hsync
(**) fglrx(0): Default mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 85.0 Hz
(II) fglrx(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808
(**) fglrx(0): Default mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
(**) fglrx(0): Default mode "1024x768": 78.4 MHz (scaled from 0.0 MHz), 57.7 kHz, 72.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 +hsync
(**) fglrx(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 772 817 interlace
(**) fglrx(0): Default mode "1024x768": 113.3 MHz (scaled from 0.0 MHz), 81.4 kHz, 100.0 Hz
(II) fglrx(0): Modeline "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 +hsync
(**) fglrx(0): Default mode "1024x768": 100.2 MHz (scaled from 0.0 MHz), 72.8 kHz, 90.0 Hz
(II) fglrx(0): Modeline "1024x768" 100.19 1024 1088 1200 1376 768 769 772 809 +hsync
(**) fglrx(0): Default mode "800x600": 56.2 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.0 Hz
(II) fglrx(0): Modeline "800x600" 56.25 800 832 896 1048 600 601 604 631
(**) fglrx(0): Default mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
(II) fglrx(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625
(**) fglrx(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
(II) fglrx(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625 +hsync
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): Default mode "800x600": 84.0 MHz (scaled from 0.0 MHz), 77.2 kHz, 120.0 Hz
(II) fglrx(0): Modeline "800x600" 83.95 800 856 944 1088 600 601 604 643 +hsync
(**) fglrx(0): Default mode "800x600": 68.2 MHz (scaled from 0.0 MHz), 63.6 kHz, 100.0 Hz
(II) fglrx(0): Modeline "800x600" 68.18 800 848 936 1072 600 601 604 636 +hsync
(**) fglrx(0): Default mode "800x600": 60.1 MHz (scaled from 0.0 MHz), 56.9 kHz, 90.0 Hz
(II) fglrx(0): Modeline "800x600" 60.06 800 840 928 1056 600 601 604 632 +hsync
(**) fglrx(0): Default mode "640x480": 36.0 MHz (scaled from 0.0 MHz), 43.3 kHz, 85.0 Hz
(II) fglrx(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 72.8 MHz (scaled from 0.0 MHz), 84.3 kHz, 160.0 Hz
(II) fglrx(0): Modeline "640x480" 72.85 640 680 752 864 480 481 484 527 +hsync
(**) fglrx(0): Default mode "640x480": 52.4 MHz (scaled from 0.0 MHz), 61.8 kHz, 120.0 Hz
(II) fglrx(0): Modeline "640x480" 52.41 640 680 744 848 480 481 484 515 +hsync
(**) fglrx(0): Default mode "640x480": 43.2 MHz (scaled from 0.0 MHz), 50.9 kHz, 100.0 Hz
(II) fglrx(0): Modeline "640x480" 43.16 640 680 744 848 480 481 484 509 +hsync
(**) fglrx(0): Default mode "640x480": 37.9 MHz (scaled from 0.0 MHz), 45.5 kHz, 90.0 Hz
(II) fglrx(0): Modeline "640x480" 37.89 640 672 736 832 480 481 484 506 +hsync
(**) fglrx(0): Default mode "640x400": 28.1 MHz (scaled from 0.0 MHz), 33.7 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x400" 28.07 640 696 736 832 400 413 415 449
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525
(**) fglrx(0): Default mode "512x384": 19.7 MHz (scaled from 0.0 MHz), 31.1 kHz, 75.0 Hz
(II) fglrx(0): Modeline "512x384" 19.68 512 528 576 632 384 384 385 416
(**) fglrx(0): Default mode "400x300": 24.8 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 24.75 400 408 448 528 300 601 602 625 doublescan
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 300 601 605 742 doublescan
(**) fglrx(0): Default mode "320x240": 15.8 MHz (scaled from 0.0 MHz), 37.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 15.75 320 328 360 416 240 481 482 501 doublescan
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 240 491 493 525 doublescan
(**) fglrx(0): Default mode "320x200": 13.1 MHz (scaled from 0.0 MHz), 31.5 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(**) fglrx(0): Display dimensions: (423, 317) mm
(WW) fglrx(0): Probed monitor is 360x270 mm, using Displaysize 423x317 mm
(**) fglrx(0): DPI set to (96, 96)
(**) fglrx(0): NoAccel = NO
(==) fglrx(0): HPV inactive
(==) fglrx(0): FSAA enabled: NO
(**) fglrx(0): FSAA Gamma enabled
(**) fglrx(0): FSAA Multisample Position is fix
(**) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/X11R6/lib/modules/linux/libfglrxdrm.a
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
(II) fglrx(0): Depth moves disabled by default
(**) fglrx(0): Capabilities: 0x00000000
(**) fglrx(0): CapabilitiesEx: 0x00000000
(**) fglrx(0): cpuFlags: 0x8000001d
(**) fglrx(0): cpuSpeedMHz: 0x00000ae9
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(**) fglrx(0): UseFastTLS=0
(**) fglrx(0): BlockSignalsOnLock=1
(==) fglrx(0): EnablePrivateBackZ = NO
(II) fglrx(0): UMM Bus area: 0xe0954000 (size=0x0769c000)
(II) fglrx(0): UMM area: 0xe0954000 (size=0x0769c000)
(II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 6.8.2.0
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xf8d32000
(II) fglrx(0): [drm] mapped SAREA 0xf8d32000 to 0xb7a7f000
(II) fglrx(0): [drm] framebuffer handle = 0xe0000000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.20.8
(II) fglrx(0): Date: Dec 6 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.12-10-686
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0xf1000000
(II) fglrx(0): [pcie] 65536 kB allocated with handle 0xdeadbeef
(II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 28672
(II) fglrx(0): [drm] texture shared area handle = 0xf8ea4000
(II) fglrx(0): shared FSAAScale=1
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xe0000000 FBMappedSize: 0x00954000
(II) fglrx(0): FBMM initialized for area (0,0)-(1600,1528)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1600,1200) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor (scanline 1200)
(II) fglrx(0): Largest offscreen area available: 1600 x 320
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x00000001
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled


Update:

After running stable for several days without incident, my video card finally started playing up. Basicly, Xorg would display nothing but a white screen whenever I went to shutdown, this was happening at random and I couldn't even switch to a text terminal.

I am yet to find out what is causing this issue (nothing is showing up in the logs) and why it just started happening all of a sudden. So, as a precaution I have changed back to using mlomkers recommendations of...

- Leaving "fglrx" out of "/etc/modules"
- Leaving "intel_agp" out of "/etc/hotplug/blacklist"
- Disabling "fglrx" built-in AGPGart controller in "/etc/X11/xorg.conf"

If anyone else starts having these problems after trying my earlier posts configuration recommendations, I would recommend doing the same...

[amohanty]

Just a note, the Ctrl-Alt-Backspace thingy did not reload X for me, Had to do a reboot to get it to work.

But aside from that it has worked beautifully.

AM

[Masteroc]

Will this driver work for a ATI Rage 128 card??

[mlomker]

Will this driver work for a ATI Rage 128 card??

No.

[Masteroc]

then what can i use if i want to install an ati rage 128?

[veloct]

Nope. 8.20.8 is the latest. Use this. (http://ubuntuforums.org/showthread.php?t=78466)

That worked for me.

eddie@ubuntu:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9550 Generic
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)

Thanks.

[Masteroc]

Is there a driver for the Rage 128 pro, or can i just use the driver with ubuntu?

[littlered]

Well, I just tried to install xorg-driver-fglrx for my AIW Radeon 8500DV and I thought it was working, but as it turns out it would freeze on me after logging in within a few minutes, usually just a couple... I've poked around a bit to no avail, and I'm not sure where to go from here... If anyone else has had a similar problem solved, I'd love to hear about it, though. :)

Edit: After following the directions from this page:

http://wiki.cchtml.com/index.php/Ubuntu_Installation_Guide

Uninstalling the default driver and making the packages for the current ATI driver and such, it's working. Woohoo!

Except, the "sudo aticonfig --initial" at the end part didn't edit the file properly and created a new section in xorg.conf the computer wasn't reading. So then I just did dpkg-reconfigure xserver-xorg and there it went.

Thanks,

x

[mlomker]

Is there a driver for the Rage 128 pro, or can i just use the driver with ubuntu?

AFAIK the only option is to use the ATI driver that comes with Ubuntu. It's open-source and provides software 3D using MESA. The Rage cards are so slow that you wouldn't get any performance improvement from an ATI-written driver anyway (that's probably why ATI doesn't write one).

[whitesox]

Hi, I have an old-ish toshiba laptop, with an old graphics card, the radeon m6 9000. But when I installed the ati drivers without a hitch, xserver will not start. When the driver is set to "ati" it works fine, although 3d does not work, but when I set it to "fglrx", i get this error:

"(II) ATI Radeon/FireGL: The following chipsets are supported:
RADEON 9000/9000 PRO (RV250 4966), RADEON 9000 LE (RV250 4967),
MOBILITY FireGL 9000 (M9 4C64), MOBILITY RADEON 9000 (M9 4C66),
RADEON 9000 PRO (D9 4C67), RADEON 9250 (RV280 5960),
RADEON 9200 (RV280 5961), RADEON 9200 SE (RV280 5964),
MOBILITY RADEON 9200 (M9+ 5C61), etc...
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.20.8
(II) ATI Proprietary Linux Driver Release Identifier: LGDr8.20g1
(II) ATI Proprietary Linux Driver Build Date: Dec 6 2005 20:05:53
(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.20.1-driver-lnx-232334
(EE) No devices detected.
:

Mine is not listed! why is it not listed? It should work, unless somehow the 9000 is before the 8500. And also, this is the ONLY error I get.

[mlomker]

the radeon m6 9000.

That's a case of misleading labeling. It's actually a 7500 chip (http://ubuntuforums.org/showthread.php?t=26148).

[whitesox]

Yup thats it. Oh well.

[Masteroc]

sry for the double or triple post, but i really need to get my ATI Rage 128 pro card working with ubuntu. I am not sure wheather to just replace the current card (Trident 3D image) with it, or do i need to first install a driver or change some text in my x11\...\xconfig file?

Any help at all would be appreciated

[mlomker]

sry for the double or triple post, but i really need to get my ATI Rage 128 pro card working with ubuntu.

Start a new thread in the Video & Sound forum.

[Masteroc]

k, thanks, ill do that

[thava]

I follow the ATI fglrx driver 8.16.20 installation guide. After the succesfully instalation of my ATI driver, i can't open my emacs in normal view. :(

The warning msg i got:


thava@local ~
$ emacs
Warning: Cannot convert string "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Warning: Cannot convert string "-*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1" to type FontStruct


And my tvout is also not working.
Sse my xorg.conf is attach here:

Thanks
/ Thava

[Randomskk]

I'm running and AMD64 3200+ system, with 2gig of ram and an ATI Radeon X800XT PE.
First install of Ubuntu, this guide went fine, and I tried the darwinia demo, ran perfect.
However, I had to wipe that install and start over, and having done so, while the install went OK, Darwinia has 1FPS.

Not sure what's causing this...

adam@random:~$ fgl_glxgears
7791 frames in 5.0 seconds = 1558.200 FPS
7769 frames in 5.0 seconds = 1553.800 FPS
7702 frames in 5.0 seconds = 1540.400 FPS
7789 frames in 5.0 seconds = 1557.800 FPS
7710 frames in 5.0 seconds = 1542.000 FPS
7895 frames in 5.0 seconds = 1579.000 FPS
7875 frames in 5.0 seconds = 1575.000 FPS
7757 frames in 5.0 seconds = 1551.400 FPS
7718 frames in 5.0 seconds = 1543.600 FPS
7804 frames in 5.0 seconds = 1560.800 FPS
7987 frames in 5.0 seconds = 1597.400 FPS
7992 frames in 5.0 seconds = 1598.400 FPS


adam@random:~$ glxgears -iacknowledgethatthistoolisnotabenchmark
29745 frames in 5.0 seconds = 5930.314 FPS
25402 frames in 5.1 seconds = 5028.870 FPS
26425 frames in 5.1 seconds = 5201.108 FPS
26458 frames in 5.0 seconds = 5247.279 FPS


adam@random:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X800 XT Platinum Edition Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)



display: :0.0 screen: 1
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON X800 XT Platinum Edition Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)


adam@random:~$ lspci |grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4a5 0
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 4a70


adam@random:~$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=2
reg02: base=0xe8000000 (3712MB), size= 128MB: write-combining, count=14


adam@random:~$ lsmod | grep fglrx
fglrx 277304 14


# File: xorg.conf
# File generated by fglrxconfig (C) ATI Technologies, 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"

# 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 "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" "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" "pc104"
Option "XkbLayout" "gb"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/mice"

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

# this is from the old file, it's for scroll wheel to work
Option "ZAxisMapping" "4 5"

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


Section "Monitor"
Identifier "Monitor1"
# === 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 connector 0"
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" "(null)"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "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" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4a50
Screen 0
EndSection

Section "Device"
Identifier "ATI Graphics Adapter connector 1"
Driver "fglrx"
BusID "PCI:1:0:0" # vendor=1002, device=4a50
Screen 1
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 connector 0"
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

Section "Screen"
Identifier "Screen1"
Device "ATI Graphics Adapter connector 1"
Monitor "Monitor1"
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

# ************************************************** ********************
# 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"
Screen "Screen1" RightOf "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 ###


Thanks for any help, I'd really like to get 3d games working nicely here.


edit: I just noticed that I think I installed the latest driver instead of this one last time, I'll try following the latest driver install tomorrow and see if it helps :)

[deepspring]

Option "UseFastTLS" "0"
Option "UseInternalAGPGART" "yes"


Try changing the above to...


Option "UseFastTLS" "2"
Option "UseInternalAGPGART" "no"


And then restart...

[onesojourner]

I have a 7500 radeon. will this driver screw things up?

[animated]

Thanks mlomker for the great unofficial guide to setting up Ubunto for ATI at:
http://wiki.cchtml.com/index.php/Ubuntu_Installation_Guide

It took a lot of reading to figure out that the official guide doesn't
work.


I have an HP-a1250n and it has the following

Athlon64 x2 processor
Motherboard: MSI MS-7184, Socket 939, Northbridge ATI RS482,
Southbridge ATI SB400, HP name: AmethystM or
AmethystM-GL6E
250GB SATA drive
ATI Radeon Xpress 200 Series integrated video

I was getting the DRIScreenInit Failed and Disabling DRI messages from the
ATI card. I also got the "libGL error: drmMap of sarea failed". But the
libdri.a fix worked for this.

I am a Linux newbie, and documented the problems I had setting up the HP-a1250n here http://www.geocities.com/dcblaha/articles/hp-a1250nLinux.htm.