ATI Proprietary Linux x86 Driver Version: 8.10.19 (released 2/16/2005) discussion

redsolar · Feb 16, 2005, 07:59 PM

Please discuss any issues you are having with the driver in this thread.

If you want to rate this driver, use this thread.

If you need information on where to get the latest Linux drivers, please use this thread.

BulletFx · Feb 16, 2005, 08:14 PM

i'm trying these new drivers with wine on suse 9.2 . Should I wait for the suse drivers????

redsolar · Feb 16, 2005, 09:32 PM

Wait for SuSE drivers. They usually folow within a week or less.

Grizzlie · Feb 16, 2005, 09:59 PM

This release has fixed the problem of crashing when exiting X to a blank screen for me...

good work ATI!

Moshroum · Feb 16, 2005, 10:02 PM

Please help to update the bugzilla. If it possible then check the list of bugs, try if the bug is still present or was removed with the new driver and post a comment to the bug (with Informations about CPU, Kernel, X Server Version, Video Card).

LinuxWarrior · Feb 17, 2005, 12:15 PM

I would like to know if I can use the radeonfb (Framebuffer) with this new drivers and the latest kernels.

I would love to have a nice splash screen and a 1024*768 framebuffer at 85Hz!!!

Thanks in advance

HeLLfire · Feb 17, 2005, 02:13 PM

Well, i'm running FB on the older drivers, (Gentoo 2.6.9) so i would assume it's ok.

UberLord · Feb 17, 2005, 02:50 PM

Quote:

Originally Posted by HeLLfire

Well, i'm running FB on the older drivers, (Gentoo 2.6.9) so i would assume it's ok.

But he asked for radeonfb which is a custom fb driver only for radeons - fb by itself I would presume to be the generic vesafb driver.

Fatal0E · Feb 17, 2005, 03:39 PM

I had the 8.8.25 drivers working
I removed them and installed this new version
I ran the sh make.sh and sh make_install.sh

but 3D quit working and I have the following in the X 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 0xf8bbb000
(II) fglrx(0): [drm] mapped SAREA 0xf8bbb000 to 0xb7cf5000
(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.8.25
(II) fglrx(0): Date: Jan 14 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(WW) fglrx(0): Kernel Module version does *not* match driver.
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xf8bbb000 at 0xb7cf5000
(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): ********************************************* *

any suggestions?

UberLord · Feb 17, 2005, 04:09 PM

Did you reboot or rmmod the old fglrx module?

Fatal0E · Feb 17, 2005, 04:12 PM

i did the

rpm -e fglrx*.*.*-*.*.i386.rpm

and that worked

then did rpm -Uh --force fglrx*.*.*-*.*.i386.rpm

from console, without X running

that seemed to work

rebooted, got the message in the log

so i did the make.sh and make_install.sh

same

ran fglrxconfig to make a new config file (backed up old one, fglrxconfig was worthless last time)

same thing

redsolar · Feb 17, 2005, 04:58 PM

Quote:

Originally Posted by Fatal0E

i did the

rpm -e fglrx*.*.*-*.*.i386.rpm

and that worked

then did rpm -Uh --force fglrx*.*.*-*.*.i386.rpm

from console, without X running

that seemed to work

rebooted, got the message in the log

so i did the make.sh and make_install.sh

same

ran fglrxconfig to make a new config file (backed up old one, fglrxconfig was worthless last time)

same thing

Distro?

LinuxWarrior · Feb 17, 2005, 06:06 PM

I've asked about the radeonfb. Because these, afaik, are the only ones capable on getting decent refresh rates in framebuffer... and the only one wich I have interest

Fatal0E · Feb 18, 2005, 02:11 AM

PCLinuxOS 8, kernel 2.6.9

UberLord · Feb 18, 2005, 09:23 AM

Quote:

Originally Posted by LinuxWarrior

I've asked about the radeonfb. Because these, afaik, are the only ones capable on getting decent refresh rates in framebuffer... and the only one wich I have interest

I don't actually know if it's been fixed or not - I don't use the fb on my AMD64 box as it causes MTRR error's which I cannot fix. And yes I've read the thread about it over at Rage3D

Grizzlie · Feb 19, 2005, 05:42 AM

fatal...
you could still have teh old module loaded and that's what the problem is.

from a console outside of x
rpm -e fglrx*.*.*-*.*.i386.rpm
modprobe -r fglrx
rpm -ihv --force fglrx*.*.*-*.*.i386.rpm
cd /lib/modules/fglrx/build_mod
sh make.sh
cd ..
sh make_install.sh
modprobe fglrx
fglrxconfig
reboot

sometimes there is a problem with libGL.so.1 not pointing to libGL.so.1.2 correctly...
to correct this
cd /usr/X11R6/lib
rm libGL.so.1
ln -s libGL.so.1.2 libGL.so.1

good luck

Eman Resu · Feb 20, 2005, 11:14 PM

Yep. After installing the new drivers under gentoo, and starting xorg, I have lost DDC and DPMS, both linux and windows. My monitor is no longer detected, and after booting with the monitor plugged in the secondary vga adapter, it worked in linux till I booted linux again. Now it doesn't work anymore and Catalyst hangs the whole computer, and everything is screwd in linux. Nice drivers. Btw, I'd like a solution, couse my card is useless in it's current state.

driverdummy · Feb 21, 2005, 02:14 PM

Hello!

I got the new drivers up and running with Suse9.2 (X-Org, Kernel 2.6.8), I´m using the kernel-built in "external" AGPGART module. At first, Doom3 always crashed (bad memory access in fglrx_umm_info) after showing the "initializing menus" screen. Eventually I could fix that. I am not 100% sure, but I think I achieved that by turning off the "REGPARM" option in the kernel and rebuilding it. I hope, this will hint some of the people, suffering from the same problem, in the right direction.
Also, the SMP detection in the make.sh script does not seem to work 100% correct. On my machine it detected SMP though my kernel is not compiled with it. The false detection of SMP occured when checking for it in /proc/kallsyms. I removed that detection manually and got rid of SMP :-) [color=#004080]
[/color]

RIV@NVX · Feb 22, 2005, 03:02 PM

I don't know about other distros, but Fedora Core 3 still won't boot after using fglrxconfig generated xorg.conf. I don't know why, but it hangs at "Configuring kernel parameters:", same as it did in 8.8.25 if I renamed XFree86Config-4 to xorg.conf.

My card is Sapphire Atlantis 9600 Pro (or something like that).

mooninite · Feb 22, 2005, 04:53 PM

RIV@NVX, you should look at this bug.

http://ati.cchtml.com/show_bug.cgi?id=82

It seems a certain version of the 9600 (sometimes called mobility) is not supported - for some reason. Report your concern and hopefully ATi will get you a fix in the next release.

willhunter · Feb 25, 2005, 05:31 AM

Hi,

I just installed new 64 bit driver on my laptop. It's FC3 and kernel version is 2.6.10-1.766_FC3.

I installed driver with yum, installation was flawless, but after rebooting, its still using old mesa driver. Output of fglrxinfo is as:
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.1)

Why its not using new ati driver??

any pointers?

expecting tons of replies.

Thank you in advance

Anirudha

HsuGotaQ · Mar 2, 2005, 06:54 AM

Now this is a tad funny. I wanted to try ATI's drivers on Suse 9.2 instead of the packaged one's by Suse. To make everything work I only had to move the "xorg.conf" to "XF86Setup" in /etc/X11 and it worked off the bat. I had hoped to fix my crashing in both Wine and Cedega, but no success here. The drivers work since native games like Enemy Territory, UT2004 and Tux Racer work perfectly (and faster than previous 8.8.25).

Hardware Specs
CPU: AMD XP 3200+
RAM: 1 GB PC-3200
VIDEO: ATI 9600 Pro

Sofware Specs
Distro: Suse 9.2
Kernel: 2.6.8-24.11
ATI Drivers: fglrx_6_8_0-8.10.19-1.i386.rpm
X.org: 6.8.1-15.1

RIV@NVX · Mar 2, 2005, 12:53 PM

Quote:

Originally Posted by mooninite

RIV@NVX, you should look at this bug.
It seems a certain version of the 9600 (sometimes called mobility) is not supported - for some reason. Report your concern and hopefully ATi will get you a fix in the next release.

I doubt that's the case. I think that the problem is in xorg.conf that ATI generates, however I'm not sure what part exactly.
This is the ATI generated xorg.conf, that won't work:

Code:

# File: xorg.conf
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.

# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
	Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
#	Group 100	# users
#	Mode 0660
EndSection

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

	Load		"dbe"	 # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
	SubSection  "extmod"
	  Option	"omit xfree86-dga"   # don't initialise the DGA extension
	EndSubSection

# This loads the Type1 and FreeType font modules
	Load		"type1"
	Load		"freetype"

# This loads the GLX module
	Load		"glx"   # libglx.a
	Load		"dri"   # libdri.a

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# 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"	"pc101"
	Option "XkbLayout"	"us"

EndSection


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

Section "InputDevice"

# Identifier and driver

	Identifier	"Mouse1"
	Driver "mouse"
	Option "Protocol"   "ImPS/2"
	Option "ZAxisMapping"   "4 5"
	Option "Device"	 "/dev/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"
	HorizSync   30-110
	VertRefresh (null)
	Option "DPMS"

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

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
	Identifier  "Standard VGA"
	VendorName  "Unknown"
	BoardName   "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#	Chipset	 "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

	Driver	  "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# installed.

#	BusID	   "PCI:0:10:0"

#	VideoRam	256

#	Clocks	  25.2 28.3

EndSection

RIV@NVX · Mar 2, 2005, 12:54 PM

(continued from previous post)

Code:

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

This one works, a combination of ATI's xorg.conf and a default one:

Code:

# XFree86 4 configuration created by pyxf86config
  
  Section "ServerLayout"
  	Identifier	 "Default Layout"
  	Screen	  0  "Screen0" 0 0
  	InputDevice	"Mouse0" "CorePointer"
  	InputDevice	"Keyboard0" "CoreKeyboard"
  EndSection
  
  Section "Files"
  
  # RgbPath is 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.
  # Multiple FontPath entries are allowed (they are concatenated together)
  # By default, Red Hat 6.0 and later now use a font server independent of
  # the X server to render fonts.
  	RgbPath	  "/usr/X11R6/lib/X11/rgb"
  	FontPath	 "unix/:7100"
  EndSection
  
  Section "Module"
  	Load  "dbe"
  	Load  "extmod"
  	Load  "fbdevhw"
  	Load  "glx"
  	Load  "record"
  	Load  "freetype"
  	Load  "type1"
  	Load  "dri"
  EndSection
  
  Section "InputDevice"
  
  # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
  #	Option	"Xleds"		"1 2 3"
  # To disable the XKEYBOARD extension, uncomment XkbDisable.
  #	Option	"XkbDisable"
  # 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"
  # Or if you just want both to be control, use:
  #	Option	"XkbOptions"	"ctrl:nocaps"
  #
  	Identifier  "Keyboard0"
  	Driver	  "kbd"
  	Option		"XkbModel" "pc105"
  	Option		"XkbLayout" "hr"
  EndSection
  
  Section "InputDevice"
  	Identifier  "Mouse0"
  	Driver	  "mouse"
  	Option		"Protocol" "IMPS/2"
  	Option		"Device" "/dev/input/mice"
  	Option		"ZAxisMapping" "4 5"
  	Option		"Emulate3Buttons" "yes"
  EndSection
  
  Section "Monitor"
  	Identifier   "Monitor0"
  	VendorName   "Monitor Vendor"
  	ModelName	"Samsung SyncMaster 900NF"
  	DisplaySize  360	270
  	HorizSync	30.0 - 110.0
  	VertRefresh  50.0 - 160.0
  	Option		"dpms"
  
  # === mode lines based on GTF ===
  # VGA @ 100Hz
  Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
  # SVGA @ 100Hz
  Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
  # XVGA @ 100Hz
  Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
  # 1152x864 @ 60Hz
  # Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
  # 1152x864 @ 85Hz
  # Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
  # 1152x864 @ 100Hz
  Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
  # 1280x960 @ 75Hz
  # Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
  # 1280x960 @ 100Hz
  # Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017  +hsync +vsync
  # SXGA @ 100Hz
  Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
  # SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
  # Modeline "GDM-1950"  109.62  1280 1336 1472 1720  1024 1024 1026 1062 -hsync -vsync
  # 1600x1000 @ 60Hz
  # Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
  # 1600x1000 @ 75Hz
  # Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
  # 1600x1000 @ 85Hz
  # Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
  # 1600x1000 @ 100Hz
  # Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
  # 1600x1024 @ 60Hz
  # Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
  # 1600x1024 @ 75Hz
  # Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
  # 1600x1024 @ 76Hz
  # Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
  # 1600x1024 @ 85Hz
  # Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
  # 1920x1080 @ 60Hz
  # Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
  # 1920x1080 @ 75Hz
  # Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
  # 1920x1200 @ 60Hz
  # Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
  # 1920x1200 @ 75Hz
  # Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
  # 2048x1536 @ 60
  # Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
  # 2048x1536 @ 60
  # Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
  # 1400x1050 @ 60Hz M9 Laptop mode 
  # ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
  # 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
  # Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
  # 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
  # Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
  
  EndSection
  
  Section "Device"
  	Identifier  "Videocard0"
  	Driver	  "fglrx"
  # VendorName  "Videocard vendor"
  # BoardName   "ATI Radeon 9600"
  # ### generic DRI settings ###
  # === disable PnP Monitor  ===
#Option							 "NoDDC"
  # === disable/enable XAA/DRI ===
	Option "no_accel"				 "no"
	Option "no_dri"					 "no"
  # === misc DRI settings ===
	Option "mtrr"					 "off" # disable DRI mtrr mapper, driver has its own code for mtrr
  # ### FireGL DDX driver module specific settings ###
  # === Screen Management ===
	Option "DesktopSetup"			 "0x00000000" 
	Option "MonitorLayout"			 "AUTO, AUTO"
	Option "IgnoreEDID"				 "off"
	Option "HSync2"					 "unspecified" 
	Option "VRefresh2"				 "unspecified" 
  	Option "ScreenOverlap"			  "0" 
  # === TV-out Management ===
	Option "NoTV"					 "yes"	 
	Option "TVStandard"				 "NTSC-M"	 
	Option "TVHSizeAdj"				 "0"	 
	Option "TVVSizeAdj"				 "0"	 
	Option "TVHPosAdj"				 "0"	 
	Option "TVVPosAdj"				 "0"	 
	Option "TVHStartAdj"			 "0"	 
	Option "TVColorAdj"				 "0"	 
  	Option "GammaCorrectionI"		   "0x00000000"
  	Option "GammaCorrectionII"		  "0x00000000"
  # === OpenGL specific profiles/settings ===
	Option "Capabilities"			 "0x00000000"
  # === Video Overlay for the Xv extension ===
  	Option "VideoOverlay"			   "on"
  # === OpenGL Overlay ===
  # Note: When OpenGL Overlay is enabled, Video Overlay
  #	   will be disabled automatically
  	Option "OpenGLOverlay"			  "off"
  # === Center Mode (Laptops only) ===
	Option "CenterMode"				 "off"
  # === Pseudo Color Visuals (8-bit visuals) ===
  	Option "PseudoColorVisuals"		 "off"
  # === QBS Management ===
	Option "Stereo"					 "off"
  	Option "StereoSyncEnable"		   "1"
  # === FSAA Management ===
	Option "FSAAEnable"				 "no"
	Option "FSAAScale"				 "1"
  	Option "FSAADisableGamma"		   "no"
  	Option "FSAACustomizeMSPos"		 "no"
	Option "FSAAMSPosX0"			 "0.000000"
	Option "FSAAMSPosY0"			 "0.000000"
	Option "FSAAMSPosX1"			 "0.000000"
	Option "FSAAMSPosY1"			 "0.000000"
	Option "FSAAMSPosX2"			 "0.000000"
	Option "FSAAMSPosY2"			 "0.000000"
	Option "FSAAMSPosX3"			 "0.000000"
	Option "FSAAMSPosY3"			 "0.000000"
	Option "FSAAMSPosX4"			 "0.000000"
	Option "FSAAMSPosY4"			 "0.000000"
	Option "FSAAMSPosX5"			 "0.000000"
	Option "FSAAMSPosY5"			 "0.000000"
  # === Misc Options ===
	Option "UseFastTLS"				 "0"
  	Option "BlockSignalsOnLock"		 "on"
  	Option "UseInternalAGPGART"		 "yes"
  	Option "ForceGenericCPU"			"no"
  	BusID "PCI:1:0:0"	# vendor=1002, device=4150
  	Screen 0
  EndSection
  
  Section "Screen"
  	Identifier "Screen0"
  	Device	 "Videocard0"
  	Monitor	"Monitor0"
  	DefaultDepth	 24
  	SubSection "Display"
  		Viewport   0 0
  		Depth	 16
  		Modes	"800x600@100" "640x480@100"
  	EndSubSection
  	SubSection "Display"
  		Viewport   0 0
  		Depth	 24
		Modes	"1152x864@100" "1024x768@100" "800x600@100" "640x480@100"
  #			    Virtual	 1280 1024
  	EndSubSection
  EndSection
  
  Section "DRI"
  	Group		0
  	Mode		 0666
  EndSection

redsolar · Mar 2, 2005, 03:06 PM

Quote:

Originally Posted by willhunter

Hi,

I just installed new 64 bit driver on my laptop. It's FC3 and kernel version is 2.6.10-1.766_FC3.

I installed driver with yum, installation was flawless, but after rebooting, its still using old mesa driver. Output of fglrxinfo is as:
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.1)

Why its not using new ati driver??

any pointers?

expecting tons of replies.

Thank you in advance

Anirudha

Did you check and see if you had all these packages installed before you installed the drivers?

davedude · Mar 6, 2005, 08:05 AM

Quote:

Originally Posted by RIV@NVX

I don't know about other distros, but Fedora Core 3 still won't boot after using fglrxconfig generated xorg.conf. I don't know why, but it hangs at "Configuring kernel parameters:", same as it did in 8.8.25 if I renamed XFree86Config-4 to xorg.conf.

My card is Sapphire Atlantis 9600 Pro (or something like that).

I get the exact same thing, but ONLY when I select DUAL HEAD Extended desktop or Dual Head Seperate Desktops. Clone Desktops or single monitor modes work great. I have a ATI RADEON 9600 SE with dual monitors hooked up.

I would love to know what exactly is causing it to stop at "Configuring kernel parameters". I've tried about every setting in the xorg.conf I can think of. I'm even running xorg 6.8.2 with the ATI 8.10.19 driver in Fedora Core 3 2.6.9-1 kernel. I guess I should be happy it works with just one monitor or clone mode but I REALLY want an extended dual head desktop!

LinuxWarrior · Mar 9, 2005, 04:56 PM

well after some testing... I've found that the new driver is incompatible with radeonfb

...

when I try to swithc from X to console and then swith to X I have a corrupted screen and sometimes a X hang...

I think that this should be fixed ASAP...

mooninite · Mar 10, 2005, 03:07 AM

Quote:

Originally Posted by LinuxWarrior

well after some testing... I've found that the new driver is incompatible with radeonfb

...

when I try to swithc from X to console and then swith to X I have a corrupted screen and sometimes a X hang...

I think that this should be fixed ASAP...

Yes, it is a known issue that the fglrx driver cannot be used in conjunction with a frame buffer driver. As for your restart bug, it is covered here: http://ati.cchtml.com/show_bug.cgi?id=37

Septor_ · Mar 10, 2005, 03:04 PM

If you want to use a framebuffer driver, use the vesafb one. It doesn't cause problems like the radeonfb driver. Sure it isn't accelerate, but who cares really? Either you are using X most of the time, or FB most of the time. The former case would benefit from using fglrx, the latter from radeonfb. The majority of people who complain about radeonfb and fglrx not working well together just log in and type startx right away 99% of the time anyways

LinuxWarrior · Mar 10, 2005, 03:26 PM

well first of all people buy the cards for use it without any restritions, well at least in theory.
Second we shouldn't talk about the usage that other people make, there's a bug or a malfunction so it needs to be solved.
That's my point of view.

Feb 16, 2005, 07:59 PM	#1
redsolar Off duty Join Date: Jul 2003 Location: Las Vegas, USA Posts: 1,242 Rep Power: 0 System Specs	ATI Proprietary Linux x86 Driver Version: 8.10.19 (released 2/16/2005) discussion Please discuss any issues you are having with the driver in this thread. If you want to rate this driver, use this thread. If you need information on where to get the latest Linux drivers, please use this thread. __________________ Real_Men_Do_Not_Use_Space_Bar Main rig: Intel Core i7 930 @ 4.0 Ghz \| Corsair H50 Push/Pull \| 12GB OCZ DDR3 \| ASUS Radeon HD 5850 \| 3x 1TB Samsung F3 RAID5 on Dell PERC 5i SAS + 1TB Hitachi \| MSI X58 Pro-e \| 850W Antec Truepower Quattro \| RocketFish by Lian Li Full Tower Case \| Gateway XHD3000 30" LCD \| Dell 2408WFP 24" LCD \| Dell 2407WFP 24" LCD \| Logitech Z-5500 Speakers \| Windows 7 Ultimate x64 Laptop: Samsung x360-34P \| Core 2 Duo SU9400 1.4 GHz \| 4GB DDR3 \| 128GB Samsung SSD \| Intel 4500M w/ HDMI \| WiFi \| Bluetooth \| 13.3" WLED 1280x800 \| Windows 7 Professional x64

Feb 16, 2005, 08:14 PM	#2
BulletFx DriverHeaven Junior Member Join Date: Sep 2004 Posts: 32 Rep Power: 0	i'm trying these new drivers with wine on suse 9.2 . Should I wait for the suse drivers???? Last edited by BulletFx; Feb 16, 2005 at 08:43 PM.

Feb 16, 2005, 09:32 PM	Thread Starter #3
redsolar Off duty Join Date: Jul 2003 Location: Las Vegas, USA Posts: 1,242 Rep Power: 0 System Specs	Wait for SuSE drivers. They usually folow within a week or less. __________________ Real_Men_Do_Not_Use_Space_Bar Main rig: Intel Core i7 930 @ 4.0 Ghz \| Corsair H50 Push/Pull \| 12GB OCZ DDR3 \| ASUS Radeon HD 5850 \| 3x 1TB Samsung F3 RAID5 on Dell PERC 5i SAS + 1TB Hitachi \| MSI X58 Pro-e \| 850W Antec Truepower Quattro \| RocketFish by Lian Li Full Tower Case \| Gateway XHD3000 30" LCD \| Dell 2408WFP 24" LCD \| Dell 2407WFP 24" LCD \| Logitech Z-5500 Speakers \| Windows 7 Ultimate x64 Laptop: Samsung x360-34P \| Core 2 Duo SU9400 1.4 GHz \| 4GB DDR3 \| 128GB Samsung SSD \| Intel 4500M w/ HDMI \| WiFi \| Bluetooth \| 13.3" WLED 1280x800 \| Windows 7 Professional x64

Feb 17, 2005, 04:09 PM	#10
UberLord A Legend in Underwear Join Date: May 2002 Location: Unknown Posts: 5,255 Rep Power: 0	Did you reboot or rmmod the old fglrx module? __________________ Gentoo Linux - Developer (baselayout) Read my blog "I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours." Stephen Roberts

Feb 19, 2005, 05:42 AM	#16
Grizzlie DriverHeaven Newbie Join Date: Feb 2005 Posts: 15 Rep Power: 0	fatal... you could still have teh old module loaded and that's what the problem is. from a console outside of x rpm -e fglrx..-..i386.rpm modprobe -r fglrx rpm -ihv --force fglrx..-..i386.rpm cd /lib/modules/fglrx/build_mod sh make.sh cd .. sh make_install.sh modprobe fglrx fglrxconfig reboot sometimes there is a problem with libGL.so.1 not pointing to libGL.so.1.2 correctly... to correct this cd /usr/X11R6/lib rm libGL.so.1 ln -s libGL.so.1.2 libGL.so.1 good luck Last edited by Grizzlie; Feb 19, 2005 at 06:21 PM.

Feb 16, 2005, 09:59 PM	#4
Grizzlie DriverHeaven Newbie Join Date: Feb 2005 Posts: 15 Rep Power: 0	This release has fixed the problem of crashing when exiting X to a blank screen for me... good work ATI!

Feb 16, 2005, 10:02 PM	#5
Moshroum DriverHeaven Newbie Join Date: Jan 2005 Posts: 11 Rep Power: 0	Please help to update the bugzilla. If it possible then check the list of bugs, try if the bug is still present or was removed with the new driver and post a comment to the bug (with Informations about CPU, Kernel, X Server Version, Video Card).

Feb 17, 2005, 12:15 PM	#6
LinuxWarrior DriverHeaven Newbie Join Date: Feb 2005 Posts: 7 Rep Power: 0	I would like to know if I can use the radeonfb (Framebuffer) with this new drivers and the latest kernels. I would love to have a nice splash screen and a 1024*768 framebuffer at 85Hz!!! Thanks in advance

Feb 17, 2005, 02:13 PM	#7
HeLLfire DriverHeaven Newbie Join Date: Jan 2003 Location: Norway Posts: 5 Rep Power: 0	Well, i'm running FB on the older drivers, (Gentoo 2.6.9) so i would assume it's ok.

Feb 17, 2005, 03:39 PM	#9
Fatal0E DriverHeaven Junior Member Join Date: Jan 2003 Posts: 29 Rep Power: 0	I had the 8.8.25 drivers working I removed them and installed this new version I ran the sh make.sh and sh make_install.sh but 3D quit working and I have the following in the X 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 0xf8bbb000 (II) fglrx(0): [drm] mapped SAREA 0xf8bbb000 to 0xb7cf5000 (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.8.25 (II) fglrx(0): Date: Jan 14 2005 (II) fglrx(0): Desc: ATI FireGL DRM kernel module (WW) fglrx(0): Kernel Module version does not match driver. (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work (II) fglrx(0): [drm] removed 1 reserved context for kernel (II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xf8bbb000 at 0xb7cf5000 (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): ********************************************* * any suggestions?

Feb 17, 2005, 04:12 PM	#11
Fatal0E DriverHeaven Junior Member Join Date: Jan 2003 Posts: 29 Rep Power: 0	i did the rpm -e fglrx..-..i386.rpm and that worked then did rpm -Uh --force fglrx..-..i386.rpm from console, without X running that seemed to work rebooted, got the message in the log so i did the make.sh and make_install.sh same ran fglrxconfig to make a new config file (backed up old one, fglrxconfig was worthless last time) same thing

Feb 17, 2005, 06:06 PM	#13
LinuxWarrior DriverHeaven Newbie Join Date: Feb 2005 Posts: 7 Rep Power: 0	I've asked about the radeonfb. Because these, afaik, are the only ones capable on getting decent refresh rates in framebuffer... and the only one wich I have interest

Feb 18, 2005, 02:11 AM	#14
Fatal0E DriverHeaven Junior Member Join Date: Jan 2003 Posts: 29 Rep Power: 0	PCLinuxOS 8, kernel 2.6.9

Feb 20, 2005, 11:14 PM	#17
Eman Resu Blues man Join Date: Jul 2003 Location: In front of my computer Posts: 35 Rep Power: 0	Yep. After installing the new drivers under gentoo, and starting xorg, I have lost DDC and DPMS, both linux and windows. My monitor is no longer detected, and after booting with the monitor plugged in the secondary vga adapter, it worked in linux till I booted linux again. Now it doesn't work anymore and Catalyst hangs the whole computer, and everything is screwd in linux. Nice drivers. Btw, I'd like a solution, couse my card is useless in it's current state.

Feb 21, 2005, 02:14 PM	#18
driverdummy DriverHeaven Newbie Join Date: Feb 2005 Posts: 1 Rep Power: 0	Hello! I got the new drivers up and running with Suse9.2 (X-Org, Kernel 2.6.8), I´m using the kernel-built in "external" AGPGART module. At first, Doom3 always crashed (bad memory access in fglrx_umm_info) after showing the "initializing menus" screen. Eventually I could fix that. I am not 100% sure, but I think I achieved that by turning off the "REGPARM" option in the kernel and rebuilding it. I hope, this will hint some of the people, suffering from the same problem, in the right direction. Also, the SMP detection in the make.sh script does not seem to work 100% correct. On my machine it detected SMP though my kernel is not compiled with it. The false detection of SMP occured when checking for it in /proc/kallsyms. I removed that detection manually and got rid of SMP :-) [color=#004080] [/color]

Feb 22, 2005, 03:02 PM	#19
RIV@NVX Freedom is a feature. Join Date: Jul 2002 Location: Croatia, Rijeka Posts: 4,476 Rep Power: 0 System Specs	I don't know about other distros, but Fedora Core 3 still won't boot after using fglrxconfig generated xorg.conf. I don't know why, but it hangs at "Configuring kernel parameters:", same as it did in 8.8.25 if I renamed XFree86Config-4 to xorg.conf. My card is Sapphire Atlantis 9600 Pro (or something like that). __________________ -- Vedran

Feb 22, 2005, 04:53 PM	#20
mooninite DriverHeaven Newbie Join Date: Feb 2005 Posts: 3 Rep Power: 0	RIV@NVX, you should look at this bug. http://ati.cchtml.com/show_bug.cgi?id=82 It seems a certain version of the 9600 (sometimes called mobility) is not supported - for some reason. Report your concern and hopefully ATi will get you a fix in the next release.

Feb 25, 2005, 05:31 AM	#21
willhunter DriverHeaven Newbie Join Date: Feb 2005 Posts: 2 Rep Power: 0	Problem with new x86_64 ATI driver Hi, I just installed new 64 bit driver on my laptop. It's FC3 and kernel version is 2.6.10-1.766_FC3. I installed driver with yum, installation was flawless, but after rebooting, its still using old mesa driver. Output of fglrxinfo is as: 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.1) Why its not using new ati driver?? any pointers? expecting tons of replies. Thank you in advance Anirudha

Mar 2, 2005, 06:54 AM	#22
HsuGotaQ Hydrogenated Dumbass Join Date: May 2002 Location: Canuckland Posts: 755 Rep Power: 0	Now this is a tad funny. I wanted to try ATI's drivers on Suse 9.2 instead of the packaged one's by Suse. To make everything work I only had to move the "xorg.conf" to "XF86Setup" in /etc/X11 and it worked off the bat. I had hoped to fix my crashing in both Wine and Cedega, but no success here. The drivers work since native games like Enemy Territory, UT2004 and Tux Racer work perfectly (and faster than previous 8.8.25). Hardware Specs CPU: AMD XP 3200+ RAM: 1 GB PC-3200 VIDEO: ATI 9600 Pro Sofware Specs Distro: Suse 9.2 Kernel: 2.6.8-24.11 ATI Drivers: fglrx_6_8_0-8.10.19-1.i386.rpm X.org: 6.8.1-15.1 Last edited by HsuGotaQ; Mar 2, 2005 at 07:01 AM.

Mar 9, 2005, 04:56 PM	#27
LinuxWarrior DriverHeaven Newbie Join Date: Feb 2005 Posts: 7 Rep Power: 0	well after some testing... I've found that the new driver is incompatible with radeonfb... when I try to swithc from X to console and then swith to X I have a corrupted screen and sometimes a X hang... I think that this should be fixed ASAP...

Mar 10, 2005, 03:04 PM	#29
Septor_ DriverHeaven Newbie Join Date: Feb 2005 Location: Lost in Japan Posts: 6 Rep Power: 0	If you want to use a framebuffer driver, use the vesafb one. It doesn't cause problems like the radeonfb driver. Sure it isn't accelerate, but who cares really? Either you are using X most of the time, or FB most of the time. The former case would benefit from using fglrx, the latter from radeonfb. The majority of people who complain about radeonfb and fglrx not working well together just log in and type startx right away 99% of the time anyways

Mar 10, 2005, 03:26 PM	#30
LinuxWarrior DriverHeaven Newbie Join Date: Feb 2005 Posts: 7 Rep Power: 0	well first of all people buy the cards for use it without any restritions, well at least in theory. Second we shouldn't talk about the usage that other people make, there's a bug or a malfunction so it needs to be solved. That's my point of view.