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 pro