AMD 8.41.7 Display Driver Released -- The Holy Crap Edition!

[mile]

Yes, I can complain. I spent 1500€ for notebook which is not working as I wanted bacause of ATI

And I am in IT bussiness for almost 10 years as programmer, I was also involved wit driver development (ISDN). And we didnt add extra features before basic were stable and tweaked.

So AIXGL for next month...great...leave all problems as they are and add extra functionality. Easier to debug

[Stormking]

Yes there are problems in the new driver, and yes in some cases it's no better than the 8.40
Actually, it's worse than 8.40, which was worse than 8.35, which was worse than 8.20 (the last release that really working for me)!


but stop and ask yourselves this question. If there had been no announcement, if this new driver had come along with no fanfare, would you all still be complaining as much.
No, not that much. But 8.41 was hyped by Phoronix, it was supposed to be a lot better than previous releases, because of the "great new codebase".

And although I would not complain that much if there hasn't been this hype, I still would complain a lot. The "progress" of the driver is simply unacceptable.


What did you expect, every last bug in the tracker fixed?
No, but at least some of them.

or you can submit bug reports early and often so they might get handled in the upcoming release.
As if anyone at AMD cares. There is an unofficial bugzilla at ati.cchtml.com and there have been rumors that the driver developers look at it regularly but since there is absolutely no feedback from AMD on what bugs they are working on, reporting bugs seems senseless. I reported all my problems there years ago and updated the information for every release and they are still not fixed or even added to the "knows issues" list.


If this release has disgusted you so much that you are going to go to NVidia forever, thats great.
I wish I could.

The whole world does not need to hear it.
AMD has to hear it. And since their feedback formular on their web site seems to lead directly to /dev/null, I'm writing here.


You are using one of the most advanced operating systems in the world, it stands to reason everything isin't going to work on the first run.
It isn't the "first run". It's at least the 41th run.

[Thetargos]

Yes, I can complain. I spent 1500€ for notebook which is not working as I wanted bacause of ATI

And I am in IT bussiness for almost 10 years as programmer, I was also involved wit driver development (ISDN). And we didnt add extra features before basic were stable and tweaked.

So AIXGL for next month...great...leave all problems as they are and add extra functionality. Easier to debug

And you were planning to run Linux on it? knowing ATI's problems? Or did you find out after? (lack of research?)

Edit

Again, you pay for Windows with most laptops... No wonder pretty much every Linux laptop seller ships with nVidia + Intel (again, not meaning to bash AMD-ATI, just state of "business")... For several reasons, part the graphics support and performance, part for power consumption and battery life, etc.

[carpman]

From a business standpoint, what choice could you make if you had to choose between supporting your latest chipset and improving speed for the existing chipsets? "Thank you for buying this 2900HD. Linux support will be added just as soon as we bump up the framerates on the 9700 pro." They have to make sure their entire product line has some functionality before they can move on to optimization.

[Michael]

No, not that much. But 8.41 was hyped by Phoronix, it was supposed to be a lot better than previous releases, because of the "great new codebase".

In all of the articles the graphics performance while gaming was looked at (as in most of our graphics articles). If you compare the performance on a working 8.40 and 8.41 system you should see a tremendous performance boost. That is a huge feat compared against no performance improvement over the previous ~16 months. There were no claims in any of the articles made about suspend/resume or other fixes. Now that the codebase is implemented in the 8.41 release that is designed specifically for the R600 series, those additional fixes will come in 8.42 and future driver releases.

As if anyone at AMD cares. There is an unofficial bugzilla at ati.cchtml.com and there have been rumors that the driver developers look at it regularly but since there is absolutely no feedback from AMD on what bugs they are working on, reporting bugs seems senseless. I reported all my problems there years ago and updated the information for every release and they are still not fixed or even added to the "knows issues" list.

AMD developers do pay attention to the BugZilla. It's even linked to from their download page.

AMD is also well aware and paying attention to this thread.

[mile]

And you were planning to run Linux on it? knowing ATI's problems? Or did you find out after? (lack or research?)



unfortunately I found this the hard way during first installation

[phreadom]

*clap* *clap* *clap* *clap* *clap* *clap*

Well spoken. This driver is not the culmination, but rather the beginning for AMD to start focusing on other issues now that they've got at least two milestones in place:


R600 support.
Speed increment in their rendering libraries.


What is left is bug squashing and fine tweaking, a hard and long task that will take several releases to accomplish, but the seed has been sewn. The next milestone, AIGLX will arrive with 8.42 and most likely compatibility with previous generations of products will be there too, hopefully more than a couple bugfixes will also make their way into that release too.

What you fail to address is that while those are nice for people with R600 cards, those are not what we were told about. We were not told "this is only for R600 cards and will likely break everything else and be worse for everyone else. everyone else will have to wait several more months." the most we were told outside of "this will be wonderful for everyone!" is that AIGLX would be delayed for 1 release until 8.42.

I hate when people act like it's a cardinal sin to complain about something, especially when they are valid complaints!

I appreciate Michael's help and his information... but when that information amounts to not only just blowing smoke up people's tailpipes, but to essentially misinformation that leaves people sitting with a driver even worse than the previous one in spite of all the prior claims about how much better it would be for everyone... I think that's a valid cause to gripe a little.

I'd have rather known beforehand not to get my hopes up and that I'd have to wait at LEAST a few more weeks. And even if I'd known NOTHING about this release, I'd still be upset that it's even worse than the prior one for me... not only not fixing ANY problems for me, but actually making things worse.

Unfortunately I gave my 9700pro to my father and I think it would be a little ridiculous to go back to my original GeForce3 card just to get usable 3D on my desktop instead of by some stretch of the imagination the expect that my almost 2 YEAR old card would be able to support 3D, see it's own video memory and simply FUNCTION as an AGP card.

If ATI had simply never support Linux, maybe there wouldn't be room to complain. But they have. For years. And after recent promises of such wonderful improvements in 8.41 to see that it was only for the R600 and went as far to make things worse for others etc... again, I think that's more than valid grounds for a complaint.

[Stormking]

There were no claims in any of the articles made about suspend/resume or other fixes.
Michael, I don't blame you for anything except maybe getting a bit too excited and passing this excitement on to your readers. The articles on Phoronix suggested, that 8.41 would be a really great release and well ... it isn't!


AMD developers do pay attention to the BugZilla. It's even linked to from their download page.

AMD is also well aware and paying attention to this thread.
So listen AMD folks, if XVideo and OpenGL are not working properly on TV-Out next month, you will have lost 5 to 20 more customers. Forever.

[phreadom]

And just to clarify for those that seem to have missed the point... let's contrast the original claims with the current information as of this release...

Prior to this release:
The fglrx 8.41 driver is focused primarily for the R600 series and the 8.42 driver will contain additional fixes and optimizations for the older generation of ATI graphics processors. While the 8.41 release is designed for the R600 series, in our tests with the R300 through R500 series the driver has worked out quite well.

After the release:
The AMD Proprietary Linux driver version 8.41 is recommended for the ATI Radeon HD 2000 family only.

AMD recommends users of cards other than the ATI Radeon HD 2000 family continue to use the currently posted drivers for that product available for download on http://ati.amd.com/

Future releases will return to a unified driver supporting all product
families.

How this affects users:
Using this driver may result in stability issues on non-Workstation products. This driver will not work with any ATI FireGL or ATI FireMV products.

How this affects distribution maintainers and packagers:
This driver is not suitable for inclusion in distributions and is
recommended to not be packaged into any mainstream distribution update. Distribution vendors may repackage and provide experimental packages, but should include the above warning to users.

Is there some reason that hardly anyone is willing to acknowledge the difference between those two statements?

The first says that while it primarily focuses on adding R600 support, that it also has a number of bux fixes and improvements to all the previous products and works great for R300 through R500.

The second says that it's ONLY for the R600 and everyone else has to wait until the next release.

There is a definite difference between those two messages.

[carpman]

So listen AMD folks, if XVideo and OpenGL are not working properly on TV-Out next month, you will have lost 5 to 20 more customers. Forever.

Such a dire ultimatum! Can AMD stand to loose 5 to 20 customers? What will that mean for the bottom line?! Your request probably represents a very small fraction of the user base. Most people seem to be wanting better performance and fewer bugs on their primary channels. Threats like this do no good.

[Xipeos]

I've done some benchmarks now, and it doesn't look good.
Here are the results:
8.40:
doom 3 = 35.7 fps (timedemo demo1 usecache)
nexuiz = (min/avg/max) 5/17/44 fps (-benchmark demos/demo1)

8.41:
doom 3 = 41.7 fps
nexuiz = 8/28/50

Quake 4 still runs in Ultra-Crappy mode, despite any settings that I choose, so a benchmark for it is pointless.

Every benchmark was ran twice, with maximum visual quality except for AA and vsync (ex: Ultra Quality in doom3) at 1280x1024. Nexuiz was ran without VBOs or Offset mapping, in order for it to work on 8.40.

The two games really are more playable when a lot of action is happening on screen, but the performance improvement is really not impressing. I wanted to do some more testing, but, after these two benchmarks, I'm really not going to put any more effort in proving that 8.41 is gold.

I hope x1k and HD users got a lot more from this new code base. I'll just go back to 8.40 (in order to play x2) and wait for the next release...

EDIT: at some point I got the screen "corruption" that a few people were talking about, but a quick switch to tty1 and back fixed it

[adamk]

A quick doom3 comparison with my X850XT...

8.40.4, demo1, 45.7
8.41.7, demo1, 55.6

I'll try with my X1300 next.

The driver does seem to install and run fine here.

Adam

[Stormking]

Such a dire ultimatum!
Add the 20 months since this bug was introduced (and reported by me and others). It appeared between 8.21 and 8.22. Shouldn't be so hard for them to figure out what was changed at this time, should it?


Can AMD stand to loose 5 to 20 customers? What will that mean for the bottom line?! Your request probably represents a very small fraction of the user base.
I don't know and I don't care. What I do know is, that within open source projects of similar complexity, an email to one of the developers is usually enough to get bugs like this fixed within days, if not hours. By people who don't get any money for their work.

[Thetargos]

What you fail to address is that while those are nice for people with R600 cards, those are not what we were told about. We were not told "this is only for R600 cards and will likely break everything else and be worse for everyone else. everyone else will have to wait several more months." the most we were told outside of "this will be wonderful for everyone!" is that AIGLX would be delayed for 1 release until 8.42.
Again, Michael is not to blame here, nor is AMD, for that matter. If you look the at the page, with the official release, they pretty much state there what is the situation, and from the looks of it, they do not lie there. Sure, we (and I include myself here, even though I don't use ATI ATM) got our hopes high, but you gotta stay somewhat skeptic, or at least try and understand that a driver release is no panacea


I hate when people act like it's a cardinal sin to complain about something, especially when they are valid complaints!
Sure they are! I understand your frustration, maybe better than what you think I do (I was really pissed when ATI brought the development from Germany to Canada to further the development of the driver when they had made some really nice advancements in Germany, only to feel that they were starting from 0 again).


I appreciate Michael's help and his information... but when that information amounts to not only just blowing smoke up people's tailpipes, but to essentially misinformation that leaves people sitting with a driver even worse than the previous one in spite of all the prior claims about how much better it would be for everyone... I think that's a valid cause to gripe a little.
On the one hand you have what was actually written, and on the other you have what you make out of that information, interpretation. Again, I don't mean to defend Michael, some times I read his articles a little bit too optimistic, but I know that maybe it is me who is interpreting the writing in an optimistic way ;)

I'd have rather known beforehand not to get my hopes up and that I'd have to wait at LEAST a few more weeks. And even if I'd known NOTHING about this release, I'd still be upset that it's even worse than the prior one for me... not only not fixing ANY problems for me, but actually making things worse.

Unfortunately I gave my 9700pro to my father and I think it would be a little ridiculous to go back to my original GeForce3 card just to get usable 3D on my desktop instead of by some stretch of the imagination the expect that my almost 2 YEAR old card would be able to support 3D, see it's own video memory and simply FUNCTION as an AGP card.
Sadly there's not much I can say about that. I felt pretty much the same back in 2003 about a GeForce2 beating the crap out of my R9500 in Linux. I tried to stay positive, but the only thing I could do was to actually move away, and not complain, as it isn't ATI's obligation to support us, when they've got a much bigger Windows market. Time and time again, Matthew Tippet said that support for Linux was geared towards the Workstation market segment, pretty much consumer support was an added "by product". This release seems to mark a shift in focus towards consumer products... I certainly hope it is.


If ATI had simply never support Linux, maybe there wouldn't be room to complain. But they have. For years. And after recent promises of such wonderful improvements in 8.41 to see that it was only for the R600 and went as far to make things worse for others etc... again, I think that's more than valid grounds for a complaint.
And you have every right to complain... and air out the frustration. I must confess, I'm really interested in these developments, not only for the new code in the drivers and support for the newer generation of cards, but also for the release of the specs. Company policies are not easily changed, and AMD has I'm sure, battled internally quite a bit to get to this point.

Michael, IIRC you published an article a while back about what it takes from ATI-AMD to get to a fglrx release, I don't seem to be able to find it anymore (I suck at teh search :D), actually that article made understand a few things about the drivers and actually stop having too high hopes for each release.

[Michael]

Michael, IIRC you published an article a while back about what it takes from ATI-AMD to get to a fglrx release, I don't seem to be able to find it anymore (I suck at teh search :D), actually that article made understand a few things about the drivers and actually stop having too high hopes for each release.

http://www.phoronix.com/scan.php?page=article&item=735&num=1

[d2kx]

If you try gl2benchmark, you can best see that 8.41 has OpenGL bugs that need to be fixed. Please compare the performance with 8.42 before you make conclusions.

[jackkerouac]

Well, it doesn't work for me. I'm running in Ubuntu Feisty a X1650 Pro and my X won't start.

I have to say, after reading all the glowing reviews on this site and all the talk of performance increases, I'm really not impressed.

I think next time, I am going to go somewhere else for my reviews on ATI releases, as this site obviously has some "fan-boy" issues. And instead of just saying "Okay, maybe we hyped this up a little too much," we get a lot of excuses and complaints about people complaining.

This driver doesn't work for the majority of people, it seems. The impression most people seemed to have gotten from this site's hype is that it would. There is no way to sugar coat that.

Perhaps next time, less hype and more facts.

[Thetargos]

If you try gl2benchmark, you can best see that 8.41 has OpenGL bugs that need to be fixed. Please compare the performance with 8.42 before you make conclusions.

Where can that "gl2benchmark" be downloaded from?

[adamk]

This driver doesn't work for the majority of people, it seems. The impression most people seemed to have gotten from this site's hype is that it would. There is no way to sugar coat that.


Except that, unless you've polled everyone who's installed 8.41, you can't honestly say that it doesn't work for the majority of people. Based on the complaints here, you may get that impression, but most people don't pop on-line to say something works... They pop on-line to bitch and moan when something doesn't work.

Adam

[mile]

I uploaded video about high performance train from ATI to YouTube :)

http://www.youtube.com/watch?v=w2XnuTTV23M

[Michael]

Perhaps next time, less hype and more facts.

Our tests are all facts. I used all of the hardware that was accessible to run these benchmarks and as the graphs show, there are clear performance improvements. I never told you that this would be a bug-free release or anything to that extent. I was reporting on the performance and everything I and others had reported. This remains truly a phenomenal release when it comes to the performance improvements. It's now possible to play Quake 4 or Quake Wars with hardware on previous drivers that would previously choke.

[Xipeos]

I think next time, I am going to go somewhere else for my reviews on ATI releases, as this site obviously has some "fan-boy" issues. And instead of just saying "Okay, maybe we hyped this up a little too much," we get a lot of excuses and complaints about people complaining.


A bold accusation for an user that just pops out of the aether.


This driver doesn't work for the majority of people, it seems.
Say what? :p


The impression most people seemed to have gotten from this site's hype is that it would. There is no way to sugar coat that.

Perhaps next time, less hype and more facts.
The reason Michael gave us is at least plausible ("the driver is geared towards r600"), and I choose to believe him.

The driver does show performance improvement, even though at the moment is not spectacular (NOTE: again, my benchmarks were done on Maximum Visual Quality at 1280x1024, it's only normal the improvement is not titanic).

[carpman]

Well, it doesn't work for me. I'm running in Ubuntu Feisty a X1650 Pro and my X won't start.

Error messages, debuging info? Anything. How do you expect to get help if you don't include any of this?

[jackkerouac]

Except that, unless you've polled everyone who's installed 8.41, you can't honestly say that it doesn't work for the majority of people. Based on the complaints here, you may get that impression, but most people don't pop on-line to say something works... They pop on-line to bitch and moan when something doesn't work.

Read this:

And instead of just saying "Okay, maybe we hyped this up a little too much," we get a lot of excuses and complaints about people complaining.

Our tests are all facts. I used all of the hardware that was accessible to run these benchmarks and as the graphs show, there are clear performance improvements. I never told you that this would be a bug-free release or anything to that extent. I was reporting on the performance and everything I and others had reported. This remains truly a phenomenal release when it comes to the performance improvements. It's now possible to play Quake 4 or Quake Wars with hardware on previous drivers that would previously choke.
Reply With Quote

A truly phenomenal relase? You've got to be kidding.

[adamk]

A quick doom3 comparison with my X850XT...

8.40.4, demo1, 45.7
8.41.7, demo1, 55.6

I'll try with my X1300 next.

The driver does seem to install and run fine here.

Adam

With my X1300:

8.40.4, demo1, 35.7
8.41.7, demo1, 50.4

These are all on medium settings, at 1024x768. No AA or AF.

Adam

[adamk]

Read this:





A truly phenomenal relase? You've got to be kidding.

It is for the majority of users (see, I can pull statistics right out my ass like you).

Adam

[Xipeos]

It's now possible to play Quake 4 or Quake Wars with hardware on previous drivers that would previously choke.

Am I the only one getting Ultra-Crappy visual quality* with Quake 4? :)

* = almost as good as MDK's

EDIT: am I the only one playing quake4? :D

[zittergie]

All you whiners, please download the correct driver @ http://ati.amd.com/support/driver.html.
and choose youre correct graphics card.

You will see that if you don't own an ATI HD 2x00 series that you wont get 8.41 but 8.40 that works fine for the most of us. When, and only when we see 8.41 for the other cards can can start to complain.

It is completely normal that when using an incorrect driver you get unpredictable results.

I'm using a Mobility X700 with the AMD 8.37 (on kUbuntu), and everything that should work, works fine.
Nonetheless i'm looking out for the new driver esp. 8.42 for Compiz.

'BE the difference that makes a difference' - JEWEL

[carpman]

A truly phenomenal relase? You've got to be kidding.

Read this:

With my X1300:

8.40.4, demo1, 35.7
8.41.7, demo1, 50.4

These are all on medium settings, at 1024x768. No AA or AF.

15fps from a driver, yes, thats phenomenal.

[Stormking]

8.40 that works fine for the most of us.
No it doesn't. You just got used to it.

[Stormking]

15fps from a driver, yes, thats phenomenal.
It just shows how much worse (in terms of 3D performance) the older codebase was.

[mile]

All you whiners, please download the correct driver @ http://ati.amd.com/support/driver.html.
and choose youre correct graphics card.

You will see that if you don't own an ATI HD 2x00 series that you wont get 8.41 but 8.40 that works fine for the most of us. When, and only when we see 8.41 for the other cards can can start to complain.

It is completely normal that when using an incorrect driver you get unpredictable results.

I'm using a Mobility X700 with the AMD 8.37 (on kUbuntu), and everything that should work, works fine.
Nonetheless i'm looking out for the new driver esp. 8.42 for Compiz.

'BE the difference that makes a difference' - JEWEL

did you see my video few post back. Do you have any problems like that? Flickering with konqueror while file browsing?

For me it is same with 8.37 - 8.41

[lenrek]

It just shows how much worse (in terms of 3D performance) the older codebase was.

Yes, it is a known issue. However, we have to accept, it is an improvement, finally...

EDIT: I no longer use ATI, so I am not defending ATI, just making a comment.

[carpman]

Michael, any chance you could run the benchmarks from 8.41.6 on 8.41.7 (same hardware, etc.)? To my mind this would kill the "deceptive hype" complaint.

[zittergie]

No it doesn't. You just got used to it.

Maybe that's why i'm using 8.37 :p

I heard 8.40 had some issues with googleearth, and that's such a great timekiller.

Well, If video works fine, planetpinguinracer works fine and googleearth works fine, I'm quite happy.

I've read something about muped64 along the forums, long time that i used that emu. Will give that a try to see how 3d works out.

Anyway, this Ati X700 is way much better than my previous laptop that was a SIS760 :rolleyes:

[Stormking]

Yes, it is a known issue. However, we have to accept, it is an improvement, finally...
When everything that used to work with 8.21 will work again, I will accept that as an improvement. The concept seems twisted but it's really all I ask for, at the moment.

[zittergie]

did you see my video few post back. Do you have any problems like that? Flickering with konqueror while file browsing?

For me it is same with 8.37 - 8.41

No, no problems at all, I will post my config tommorow, because I'm not on my laptop right now.
I had to change the xorg.conf manually, because of the know problem that the driver assigns the DVI-out as the first display.
After that anything worked fine.

If not tried the 8.41, and I probably will not until X700 is among the supported cards.

[lenrek]

Michael, any chance you could run the benchmarks from 8.41.6 on 8.41.7 (same hardware, etc.)? To my mind this would kill the "deceptive hype" complaint.

I think this is irrelevant. Most of what I read here are not complaining about performance, they are mostly about bugs and installation problems. However, from my experience, such issues are typical for ATI drivers.

[werdz]

I've been following this driver closely for the past week, as I've got an X1950XTX in a desktop and an X700 Mobility in a laptop, and it'd be nice to have them actually work properly on linux.

I installed the 8.41 driver earlier on the laptop (X700 Mobility), and after a little tinkering to get ubuntu to actually load it, I'm a little disappointed. Although I do fully understand that its the first release of a new generation of drivers (and even carries a label saying "R600 only", and "Not for Mobility"), so I wasn't expecting miracles.

XGL will no longer load for some reason... glxgears and fgl_glxgears work well. WoW through WINE won't load (it loaded but was unplayable with 8.40).

Not going to install it on my X1950 just yet. And going to revert to 8.40 for the X700.

High hopes for 8.42 and 8.43. To the posters going "OMG WHY DOESNT IT WORK FFFS" I'd just say AMD seem to be really trying with this, and development takes time.

Tbh if they can get suspend/resume working along with AIGLX, I'll consider it perfect.

[zkyez]

well watch the following print screens:

http://florin.sitnet.ro/ati/

so you guys that can`t google for 15 seconds, please shut up. opengl output, x11 and xv output, all 3 work without any problems.

So does powerplay.


HINT: GOOGLE FOR

export LIBXCB_ALLOW_SLOPPY_LOCK=1

[andrig]

Shit, okay, that's a bug in the RPM SPEC file for x86_64 that I overlooked in the packaging script. You can correct it in the packages/Fedora/ SPEC file by adding the line for fglrx_dri.so or by deleting the fglrx_dri.so file after extracting it... I can release new packaging scripts here shortly. fglrx_dri.so was replaced in 8.41 as a dummy file late in the cycle.

I used --keep at the command line so I could look at the files, and modify as you say, but then I'm unsure of how to build the packages after. I have tried to run ati-installer.sh --buildpkg Fedora/F7, but that complains that Fedora/F7 is not supported. After either deleting the fgl_dri.so, or modifying the SPEC file, what script do you run with what arguments?

Thanks.

[Snake]

8.41 works for me (x1400, Core2Duo Lenovo Z61m, 2GB RAM, Gentoo 64-Bit, 2.6.22), and it IS faster with everything I tested so far:

- glxgears (~3100 FPS -> ~4200 FPS)
- fgl_fglxgears (~590 -> ~910 FPS)
- UT2004 Benchmark (50 FPS -> 75 FPS)
- blender (1300 iterations -> 1690 iterations)
- SecondLife ("KTris drawn/sec" ~2100 -> ~3300), plus VBO working, plus no more "1 frame per 5 seconds" when "GL mem" alloc grows bigger than half the phys. video ram size (128 MB, before SL had to be set to 64 MB to work at all), plus no more "turning lag"
- xv works (but not tested on TV-Out yet)

New problems so far:
- Had one "black screen" when switching consoles
- some glesx error when terminating X
- SL does not work in fullscreen anymore

I do not understand all that bashing done here. It was clear to me that 8.41 would be some kind of "beta" quality, because the code actually started to change. But the performance indicates those are *good* changes.

Sadly, setting up 3D on linux is not always easy currently (look at all those "No DRI here" threads everywhere), but there are many possible reasons other than the actual "driver" for this (e.g. with 8.40 I got only half of the "max LFB" as "free LFB" until I removed the "FSAASize"-setting from /etc/ati/admpcsdb)

So, I wonder if some problems discussed here are system / configuration related. I currently have NO special settings in xorg.conf, and a really "bare bones" amdpcsdb, and the system works (has bugs, but works).

So, for me 8.41 is BETTER than 8.40 (performance), and I think 8.42 will be BETTER than 8.41 (bugs, features). And there are open specs now. Things *are* getting better ;-)

[opera]

And you were planning to run Linux on it? knowing ATI's problems? Or did you find out after? (lack of research?)

Edit

Again, you pay for Windows with most laptops... No wonder pretty much every Linux laptop seller ships with nVidia + Intel (again, not meaning to bash AMD-ATI, just state of "business")... For several reasons, part the graphics support and performance, part for power consumption and battery life, etc.

OMG how much you and people like you disgust me. You nullify peoples issues because they "should have known" that ATI sucks? So then it's Ok to suck, and people should stop complaining?
No, whatever history a company has, doesn't make it Ok to give complete crap support to their customers, whatever they say "Linux is small" yada yada.

Fuck that BS. Linux is amazingly big for its enormously powerful enemies who actively make things impossible for open communities by locking in specs from hw providers, and ATI et al keep playing these major sw corps' game. And all you can come up with is "Your laptop was sold with Windows" yada yada...

Eat sh*t.

[opera]

I've done some benchmarks now, and it doesn't look good.
Here are the results:
8.40:
doom 3 = 35.7 fps (timedemo demo1 usecache)
nexuiz = (min/avg/max) 5/17/44 fps (-benchmark demos/demo1)

8.41:
doom 3 = 41.7 fps
nexuiz = 8/28/50

Quake 4 still runs in Ultra-Crappy mode, despite any settings that I choose, so a benchmark for it is pointless.

Every benchmark was ran twice, with maximum visual quality except for AA and vsync (ex: Ultra Quality in doom3) at 1280x1024. Nexuiz was ran without VBOs or Offset mapping, in order for it to work on 8.40.

The two games really are more playable when a lot of action is happening on screen, but the performance improvement is really not impressing. I wanted to do some more testing, but, after these two benchmarks, I'm really not going to put any more effort in proving that 8.41 is gold.

I hope x1k and HD users got a lot more from this new code base. I'll just go back to 8.40 (in order to play x2) and wait for the next release...

EDIT: at some point I got the screen "corruption" that a few people were talking about, but a quick switch to tty1 and back fixed it

Hi there Mr Bitch. Where's my hail? You told me you'd hail me, now since it's clear that the driver sucks...
And don't give me the only-r600 BS. No one was told that this driver would be r600-ONLY. Just that it would be "focused" on one thing, doesn't mean everything else will suck. At least Mr Michael didn't clarify that while praising and hyping this crap driver release.

I consider myself hailed.

[opera]

Just like every other version of the crap ATI driver with a modern kernel, and I'm getting used to it:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48586d]
1: /lib/libc.so.6 [0x2b1dbeae36a0]
2: /usr/bin/X(NumMotionEvents+0x12) [0x447832]
3: /usr/bin/X(CreateConnectionBlock+0x53) [0x439543]
4: /usr/bin/X(main+0x65a) [0x43a08a]
5: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b1dbeacfb44]
6: /usr/bin/X(FontFileCompleteXLFD+0x229) [0x439189]

Fatal server error:
Caught signal 11. Server aborting

[Xipeos]

Hi there Mr Bitch. Where's my hail? You told me you'd hail me, now since it's clear that the driver sucks...
And don't give me the only-r600 BS. No one was told that this driver would be r600-ONLY. Just that it would be "focused" on one thing, doesn't mean everything else will suck. At least Mr Michael didn't clarify that while praising and hyping this crap driver release.

I consider myself hailed.

You deserve no hail, as the driver is not even close to what you predicted. There's obvious improvement (did you miss the part on how "The two games really are more playable when a lot of action is happening on screen" ?).

[carpman]

Fuck that BS. Linux is amazingly big for its enormously powerful enemies who actively make things impossible for open communities by locking in specs from hw providers, and ATI et al keep playing these major sw corps' game. And all you can come up with is "Your laptop was sold with Windows" yada yada...

Eat sh*t.

None of that absolves you from doing research before you buy something. You can complain about it not working, but you also have to remember that you should have checked in the first place as well.

[zkyez]

Just like every other version of the crap ATI driver with a modern kernel, and I'm getting used to it:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48586d]
1: /lib/libc.so.6 [0x2b1dbeae36a0]
2: /usr/bin/X(NumMotionEvents+0x12) [0x447832]
3: /usr/bin/X(CreateConnectionBlock+0x53) [0x439543]
4: /usr/bin/X(main+0x65a) [0x43a08a]
5: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b1dbeacfb44]
6: /usr/bin/X(FontFileCompleteXLFD+0x229) [0x439189]

Fatal server error:
Caught signal 11. Server aborting


Linux florin-laptop 2.6.22.5-12-default #1 SMP 2007/09/04 12:37:49 UTC i686 i686 i386 GNU/Linux

i do not see the error you are reporting.

[carpman]

Just like every other version of the crap ATI driver with a modern kernel, and I'm getting used to it:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48586d]
1: /lib/libc.so.6 [0x2b1dbeae36a0]
2: /usr/bin/X(NumMotionEvents+0x12) [0x447832]
3: /usr/bin/X(CreateConnectionBlock+0x53) [0x439543]
4: /usr/bin/X(main+0x65a) [0x43a08a]
5: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b1dbeacfb44]
6: /usr/bin/X(FontFileCompleteXLFD+0x229) [0x439189]

Fatal server error:
Caught signal 11. Server aborting


What in that backtrace makes you point a finger at AMD?

[Michael]

Opera, stop with your useless arguing with Xipeos and others... I've already warned you.

[zkyez]

it seems that the previous post i posted with a link to screenshots is awaiting moderation. well, gl2, x11, gl and xv video outputs work just fine. just set the environment LIBXCB_ALLOW_SLOPPY_LOCK=1, like

export LIBXCB_ALLOW_SLOPPY_LOCK=1 in .bash_profile, then restart X.

[oliver]

Just want to let whoever cares know, I have both a X1950GT (256MB) and a X1950Pro (512MB) on AGP and both don't work :(

I'm only posting the results here cause some have gotten it to work, whilst others (me) have not. Here is what I get:

Pro: Blank Image, hardlock nothing works anymore.
GT: Segfault, as mentioned earlier by someone, output below.

The Pro actually has only worked with 2 drivers for me so far, and I don't know if that is conciderd to be called 'working'. I'll post a new thread on it however, see what happens.

(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/lib/xorg/modules//glesx.so [0xb5c6ea24]
3: /usr/lib/xorg/modules//glesx.so [0xb5c6809c]
4: /usr/lib/xorg/modules//glesx.so [0xb5bfb3fb]
5: /usr/lib/xorg/modules//glesx.so [0xb5c0d196]
6: /usr/lib/xorg/modules//glesx.so [0xb5bfa3d9]
7: /usr/lib/xorg/modules//glesx.so [0xb5c23c12]
8: /usr/lib/xorg/modules//glesx.so [0xb5c11ebd]
9: /usr/lib/xorg/modules//glesx.so [0xb5c13469]
10: /usr/lib/xorg/modules//glesx.so [0xb5b9a6e3]
11: /usr/lib/xorg/modules//glesx.so [0xb5b8ff88]
12: /usr/lib/xorg/modules//glesx.so [0xb5b90670]
13: /usr/lib/xorg/modules//glesx.so(esutInit+0x74) [0xb5b8f484]
14: /usr/lib/xorg/modules//glesx.so [0xb5b8b17b]
15: /usr/lib/xorg/modules//glesx.so(GlesxExtensionInit+0x9b) [0xb5b8a3fb]
16: /usr/X11R6/bin/X(InitExtensions+0xa2) [0x80f4412]
17: /usr/X11R6/bin/X(main+0x2af) [0x807459f]
18: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d94ebc]
19: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

[jackkerouac]

Maybe that's why i'm using 8.37 :p

I heard 8.40 had some issues with googleearth, and that's such a great timekiller.

Well, If video works fine, planetpinguinracer works fine and googleearth works fine, I'm quite happy.

I've read something about muped64 along the forums, long time that i used that emu. Will give that a try to see how 3d works out.

Anyway, this Ati X700 is way much better than my previous laptop that was a SIS760 :rolleyes:

There is a fix for the google earth problem. Go to this link (http://n01getsout.com/blog/2006/11/26/google-earth-for-linux-freezing-with-ati/) and check it out. It fixed my problem.

[fexx]

Same here:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631]
1: [0xb7f5a420]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxScreenInit+0x505) [0xb791f725]
3: /usr/bin/X(AddScreen+0x1ee) [0x80764be]
4: /usr/bin/X(InitOutput+0x21e) [0x80a7c0e]
5: /usr/bin/X(main+0x27b) [0x8076c6b]
6: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d59050]
7: /usr/bin/X(FontFileCompleteXLFD+0x1ed) [0x80761c1]

Fatal server error:
Caught signal 11. Server aborting

[adamk]

Read this:



15fps from a driver, yes, thats phenomenal.

A 42% increase is pretty phenomenal, at least to some people.

Adam

[Stormking]

well watch the following print screens:

http://florin.sitnet.ro/ati/

so you guys that can`t google for 15 seconds, please shut up. opengl output, x11 and xv output, all 3 work without any problems.
Not for me. XV has the video squeezed to the upper half of the screen, OpenGL fails in MPlayer and in Xine, the video is displayed in the upper left corner of the primary screen.

Did you really try this on a TV in dual head mode?

[Xipeos]

HOWTO: get screen corruption :) (and fix it)

1) open firefox
2) go to a big page (ex: set "show 40 posts per page" in your profile)
3) scroll up& down all the way really fast
<corruption>
4) switch to tty1 (CTRL+ATL+F1) and back (CTRL+ALT+F7) to fix it

Can anyone else try this and confirm? (especially those who complained about the problem before)

[dickeywang]

Just to report that the 8.41.7 works on X1400 Mobility (Ubuntu Feisty). glxgears fps goes up from 2500 to 4800, and I found fps in Sauerbraten improved from 30 to 58. :)

Just one question: fglrxinfo returns a different opengl version number:

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400
OpenGL version string: 2.0.6849 Release <--------------- ???


Shouldn't it be something like 8.41.7?

[enzobelmont]

13% better in glxgears in normal mode er.....

in GLX-compiz it sucks a lot more than 8.40

don't worry, we have an entire mont to think about it.


:D

[carpman]

Shouldn't it be something like 8.41.7?

It's reporting the OpenGL version, not the Radeon driver version.

[d2kx]

But it says 8.40.4 some lines later.

Am I the only one getting Ultra-Crappy visual quality* with Quake 4? :)

* = almost as good as MDK's

EDIT: am I the only one playing quake4? :D

I can confirm these issues. Michael told me he can't, so I thought it's me. It very likely gets fixed with 8.42.

[Xipeos]

HINT: GOOGLE FOR

export LIBXCB_ALLOW_SLOPPY_LOCK=1

--offtopic--

That envvar only works if you've applied the proper patch (most likely your distro did). It's better to compile xcb with -DNDEBUG, so you won't have to worry about exporting a var every time.

--ontopic--

I can confirm these issues. Michael told me he can't, so I thought it's me. It very likely gets fixed with 8.42.
Thanks.

[jackkerouac]

This driver may EVENTUALLY become the bee's knees, but all I'm saying is that I no longer trust this website to give me the straight goods on whether or not it IS right now.

This site hyped up this driver like nobody's business and it's really not that great. For some people it works well, for others it works poorly and for the rest it doesn't work at all.

I happen to be in the latter category, so my opinion is probably biased. But then again, I'm not complaining so much about this crappy drivers, I'm more complaining about the hype Phoronix generated about the driver, a hype it simply did not (or could not?) live up to.

I guess I just expected more from this site. More dispassionate analysis, I guess. And maybe something telling people that unless they were running a 2000 series card, they were going to be screwed this month by ATI.

[Tillin9]

All those people who get seg faults, have you tried quiting X, then going to a terminal, stoping X, /etc/init.d/x11-common stop, unloading the previous fglrx kernel module, rmmod fglrx, then restarting X?

My 8.41 didn't unload the previous driver automatically and seg faulted the first time I switched as well. Some xorg.conf setting will also result in a black screen/ falling back to a terminal. Usually ATI driver updates will screw up on the kernel module, but this just results in 3D being disabled until X is restarted, not X seg faulting.

Also, I might have an idea why I didn't see such a big performance increase while many forum members did. I have tweaked my xorg.conf file to have many of the fglrx performance features enabled. Possibly 8.41 has a more liberal default policy? Here is the relevant excerpt:


# ChipID 0x4E44
Option "AGPMode" "4"
Option "BusID" "PCI:1:0:0" #vendor=1002,device=4e44
Option "AGPFastWrite" "True"
Option "EnablePageFlip" "True"
Option "FSAAEnable" "on"
Option "FSAAScale" "4"
Option "DDCMode" "True"
Option "DMAForXv" "True"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "TexturedVideoSync" "off"

[Thetargos]

OMG how much you and people like you disgust me. You nullify peoples issues because they "should have known" that ATI sucks? So then it's Ok to suck, and people should stop complaining?
No, whatever history a company has, doesn't make it Ok to give complete crap support to their customers, whatever they say "Linux is small" yada yada.

Fuck that BS. Linux is amazingly big for its enormously powerful enemies who actively make things impossible for open communities by locking in specs from hw providers, and ATI et al keep playing these major sw corps' game. And all you can come up with is "Your laptop was sold with Windows" yada yada...

Eat sh*t.
I could answer and argue... But why bother? Is not like you are going to listen, anyway *yawn*

[Xipeos]

AI have tweaked my xorg.conf file to have many of the fglrx performance features enabled. Possibly 8.41 has a more liberal default policy? Here is the relevant excerpt:


# ChipID 0x4E44
Option "AGPMode" "4"
Option "BusID" "PCI:1:0:0" #vendor=1002,device=4e44
Option "AGPFastWrite" "True"
Option "EnablePageFlip" "True"
Option "FSAAEnable" "on"
Option "FSAAScale" "4"
Option "DDCMode" "True"
Option "DMAForXv" "True"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "TexturedVideoSync" "off"


Maybe you should try disabling FSAA? I bet you'll notice a *huge* performance improvement. :p

EDIT: Also your "tweaks" have no effect on fglrx
(WW) fglrx(0): Option "AGPMode" is not used
(WW) fglrx(0): Option "AGPFastWrite" is not used
(WW) fglrx(0): Option "EnablePageFlip" is not used
(WW) fglrx(0): Option "DDCMode" is not used
(WW) fglrx(0): Option "DMAForXv" is not used

[Thetargos]

I thought FSAA was disabled in the driver for this release on all models?

[Xipeos]

I thought FSAA was disabled in the driver for this release on all models?

AA/AF is disabled in the driver for the 8.41 series on R600 components. The support will probably be in 8.42.

Only for r600 apparently.

[Tillin9]

Maybe you should try disabling FSAA? I bet you'll notice a *huge* performance improvement. :p

EDIT: Also your "tweaks" have no effect on fglrx


Honestly, I've never complained about performance. I get 50 FPS in the games I want to play at 4x FSAA. My gripes are more about image quality. Maybe I'm spoiled, but I'm used to 6x FSAA and/ or temporal AA on all my games in Windows.

Wow, you're right. I had left those in from a 8.38 where I'm sure they had an effect since a problem playing Xvid video in high quality made me investigate the fglrx tweaks in the first place. That combination gave the best quality output and increased my OpenGL benchmarks as well. However, a quick look at 8.40 does show they don't seem to be used anymore.

[rolz]

It's working well for me,

had to do some fixing for the kernel i'm running, but I'm used to that.. bleeding edge after all..

But it's phenomenally faster, and the fixes that allow googleearth to work again, are much appreciated.

good work guys.

[Tillin9]

I thought FSAA was disabled in the driver for this release on all models?

A look at my earlier posts shows 8.41 does have FSAA completely disabled. If anyone is getting FSAA with 8.41, please let me know.

That tweaks list was left over from my time optimizing 8.38. When I upgraded to 8.39 and 8.40 I got the same or better performance and didn't bother changing anything. As Xipeos said, they don't do anything now.

Sorry for any confusion.

[dickeywang]

It's reporting the OpenGL version, not the Radeon driver version.

Yes, I know that. But with the 8.40 driver, fglrxinfo gives both the opengl version and the radeon driver version, which looks something like this:

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON 9600/9700 Series
OpenGL version string: 2.0.6650 (8.40.4) <----

[andrig]

I used --keep at the command line so I could look at the files, and modify as you say, but then I'm unsure of how to build the packages after. I have tried to run ati-installer.sh --buildpkg Fedora/F7, but that complains that Fedora/F7 is not supported. After either deleting the fgl_dri.so, or modifying the SPEC file, what script do you run with what arguments?

Thanks.

Okay, I figured out that I also needed to pass in the version number from the driver before the --buildpkg Fedora/F7, and now the ati-installer.sh runs like it should. I still get the same RPM build errors, but maybe I'm interpreting your instructions incorrectly. Do I remove the fglrx_dri.so file from /usr/lib/dri and the symlink from /usr/X11R6/lib/modules/dri?

[Michael]

Do I remove the fglrx_dri.so file from /usr/lib/dri and the symlink from /usr/X11R6/lib/modules/dri?

Yes, you can basically remove those references since fglrx_dri.so is just a dummy file. It was meant to help package maintainers who didn't remove their fglrx_dri.so links in time, but before they announced fglrx_dri.so would temporarily be a dummy, I had already removed all traces of it and then had to go back in and add fglrx_dri.so back and I overlooked the x86_64 package.

[notz]

anybody can help me? why opengl is soo slow on my x1250...


fgl_glxgears -info
Using GLX_SGIX_pbuffer
GL_RENDERER = ATI Radeon X1200 Series
GL_VERSION = 2.0.6849 Release
GL_VENDOR = ATI Technologies Inc.
GL_EXTENSIONS = GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_object GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_KTX_buffer_region GL_NV_blend_square GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_WIN_swap_hint WGL_EXT_swap_control
788 frames in 5.0 seconds = 157.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1010 frames in 5.0 seconds = 202.000 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1004 frames in 5.0 seconds = 200.800 FPS
1014 frames in 5.0 seconds = 202.800 FPS
994 frames in 5.0 seconds = 198.800 FPS
1016 frames in 5.0 seconds = 203.200 FPS
989 frames in 5.0 seconds = 197.800 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS

[Michael]

anybody can help me? why opengl is soo slow on my x1250...


fgl_glxgears -info
Using GLX_SGIX_pbuffer
GL_RENDERER = ATI Radeon X1200 Series
GL_VERSION = 2.0.6849 Release
GL_VENDOR = ATI Technologies Inc.
GL_EXTENSIONS = GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_object GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_KTX_buffer_region GL_NV_blend_square GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_WIN_swap_hint WGL_EXT_swap_control
788 frames in 5.0 seconds = 157.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1010 frames in 5.0 seconds = 202.000 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1004 frames in 5.0 seconds = 200.800 FPS
1014 frames in 5.0 seconds = 202.800 FPS
994 frames in 5.0 seconds = 198.800 FPS
1016 frames in 5.0 seconds = 203.200 FPS
989 frames in 5.0 seconds = 197.800 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS



What results were you getting before with the Radeon X1250? fgl_glxgears and glxgears aren't exactly great benchmarks. Have you tried any other Linux OpenGL benchmarks?

[Xipeos]

anybody can help me? why opengl is soo slow on my x1250...


fgl_glxgears -info
Using GLX_SGIX_pbuffer
GL_RENDERER = ATI Radeon X1200 Series
GL_VERSION = 2.0.6849 Release
GL_VENDOR = ATI Technologies Inc.
GL_EXTENSIONS = GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_object GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_KTX_buffer_region GL_NV_blend_square GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_WIN_swap_hint WGL_EXT_swap_control
788 frames in 5.0 seconds = 157.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1010 frames in 5.0 seconds = 202.000 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1004 frames in 5.0 seconds = 200.800 FPS
1014 frames in 5.0 seconds = 202.800 FPS
994 frames in 5.0 seconds = 198.800 FPS
1016 frames in 5.0 seconds = 203.200 FPS
989 frames in 5.0 seconds = 197.800 FPS
1006 frames in 5.0 seconds = 201.200 FPS
1008 frames in 5.0 seconds = 201.600 FPS
1008 frames in 5.0 seconds = 201.600 FPS



Don't use glxgears as a benchmark. My fps is glxgears dropped from ~70k to just ~7k, and in fgl_glxgears from ~50k to ~5k. This is obviously not a proper measurement, as I got some performance improvement with doom3 & nexuiz (see my post...somewhere in this thread).

[rbmorse]

Opera, stop with your useless arguing with Xipeos and others... I've already warned you.

Michael, I don't have any problem with any of the other people being critical of 8.41, but this guy is over the line. Please make him go away.

[Michael]

Michael, I don't have any problem with any of the other people being critical of 8.41, but this guy is over the line. Please make him go away.

Forum users are free to voice their opinion whether they like a driver or not, but yes Opera has already taken it over the line and was warned and if he does it once more he will be banned.

[mcgreg]

I have tested the 3d performance with ioquake3

with old 8.39.4 and 8.40.4
1280x1024x32 hightest possible quality: demo four : 93fps

with new 8.41.7
1280x1024x32 hightest possible quality: demo four : 145fps

that a +50% improvement!

Also , fgl_glxgears improved from
750fps (8.40.4) to
1000fps (8.41.7)

thats very good work indeed. Thanks you.

Beware:
For those who use wine as well wine (games, applications using 3D/libgl) might not work properly with 8.41.7. I have already contacted wine-devs and reported the problem. It should be already worked on and fixed soon (maybe even until next release)


mcgreg

[container]

I'll give a small report about moving from 8.39.4 to 8.41.7 using a Radeon 9600 Pro (686).

Glxgear readings just went down, but what are they really good for anyway? I now get "2306.167 fps" instead of "3773.463 fps".
Ut2004 Demo didn't seem to improve, but Doom3 demo isn't as bad a slideshow as it used to be. Both are estimates, that is, they weren't benchmarked properly.
Termulous in timedemo mode gave slightly lower fps for a certain demo (Q3 engine). The difference is something like from "301sec 93fps" to "330 sec 8xfps".
I should also note that I didn't notice any new problems in desktop use. I never use anything like tv-out, and probably never will, so that's no matter.
Finally, I suppose people should pay attention to release notes and wait at least for .42 before getting completely disappointed. For me, this latest driver seems to be nothing but an improvement. I also realize that this old box can't get huge performance, no matter what drivers I use.

[Thetargos]

I'll give a small report about moving from 8.39.4 to 8.41.7 using a Radeon 9600 Pro (686).

Glxgear readings just went down, but what are they really good for anyway? I now get "2306.167 fps" instead of "3773.463 fps".
Ut2004 Demo didn't seem to improve, but Doom3 demo isn't as bad a slideshow as it used to be. Both are estimates, that is, they weren't benchmarked properly.
Termulous in timedemo mode gave slightly lower fps for a certain demo (Q3 engine). The difference is something like from "301sec 93fps" to "330 sec 8xfps".
I should also note that I didn't notice any new problems in desktop use. I never use anything like tv-out, and probably never will, so that's no matter.
Finally, I suppose people should pay attention to release notes and wait at least for .42 before getting completely disappointed. For me, this latest driver seems to be nothing but an improvement. I also realize that this old box can't get huge performance, no matter what drivers I use.

Indeed, I wish I could get a dual quad-core system like the one Michael has for the tests... It is almost impossible to be CPU bound in that monster, so the graphics cards actually yield their top most performance.

[opera]

You deserve no hail, as the driver is not even close to what you predicted. There's obvious improvement (did you miss the part on how "The two games really are more playable when a lot of action is happening on screen" ?).

Oh, so a game gets a few more FPS, and that makes it great? Wow. Obviously doesn't take much to satisfy some.

For others, we think that a few more serious bugs needs to be solved, and I predicted them not to have been, and I was right. Unfortunately.
I'm glad you're happy with ATI's amazing progress though.

[notz]

What results were you getting before with the Radeon X1250? fgl_glxgears and glxgears aren't exactly great benchmarks. Have you tried any other Linux OpenGL benchmarks?

the board is rather new (2 days old), but on 8.40.4 i didn't get dri and opengl working:

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

[notz]

What results were you getting before with the Radeon X1250? fgl_glxgears and glxgears aren't exactly great benchmarks. Have you tried any other Linux OpenGL benchmarks?

ok, got it now with 8.40.4. it's better in 8.41.7, but too bad to be useful, nor it's not possible to get textured video over opengl (max texture size: 512 x 512). i think i will give this mainboard back, there will be no video playback possible in the next year....


fgl_glxgears -info
Using GLX_SGIX_pbuffer
GL_RENDERER = ATI Radeon X1200 Series
GL_VERSION = 2.0.6747 (8.40.4)
GL_VENDOR = ATI Technologies Inc.
GL_EXTENSIONS = GL_ARB_multitexture GL_EXT_texture_env_add GL_EXT_compiled_vertex_array GL_S3_s3tc GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_multisample GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_pixel_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ARB_draw_buffers GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_separate_stencil GL_ATI_shader_texture_lod GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_ATI_vertex_streams GL_ATIX_texture_env_combine3 GL_ATIX_texture_env_route GL_ATIX_vertex_shader_output_point_size GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_object GL_EXT_multi_draw_arrays GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_EXT_vertex_shader GL_HP_occlusion_test GL_NV_blend_square GL_NV_occlusion_query GL_NV_texgen_reflection GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays
540 frames in 5.0 seconds = 108.000 FPS
644 frames in 5.0 seconds = 128.800 FPS
668 frames in 5.0 seconds = 133.600 FPS
652 frames in 5.0 seconds = 130.400 FPS
645 frames in 5.0 seconds = 129.000 FPS

[oaul]

Got my 8.41 to work on X700 mobility - libGL.so was old. (Just replaced it with one that was 14 megs).

I think its worth saying that now freespace open works MUUUUUUCH better than it did with 8.40. Just messing around on the last level was about a worst case ~10 fps vs. worst case ~30 for 40 and 41, respectively. Not to mention 40's averages below 30 and and 41's averages above 50. Im thrilled. Stability is an issue. Debian locked out for the first time in years.

[Alistair]

great honkin caveat :

neither of these are real benchmarks - they are only informational


8.40 - ati 9550 card

glxgears:
alistair@ajftl1 ~ $ glxgears
8982 frames in 5.0 seconds = 1796.162 FPS
9357 frames in 5.0 seconds = 1871.383 FPS
9636 frames in 5.0 seconds = 1927.183 FPS
10028 frames in 5.0 seconds = 2005.268 FPS
9740 frames in 5.0 seconds = 1947.983 FPS
9561 frames in 5.0 seconds = 1911.855 FPS
11013 frames in 5.0 seconds = 2202.580 FPS

fgl_flglxgears:
1680 frames in 5.0 seconds = 336.000 FPS
2087 frames in 5.0 seconds = 417.400 FPS
2088 frames in 5.0 seconds = 417.600 FPS
2074 frames in 5.0 seconds = 414.800 FPS
2080 frames in 5.0 seconds = 416.000 FPS
2072 frames in 5.0 seconds = 414.400 FPS
2079 frames in 5.0 seconds = 415.800 FPS



ati 9550 card agp -

driver 8.41.7

glxgears
13674 frames in 5.0 seconds = 2734.762 FPS
13498 frames in 5.0 seconds = 2699.459 FPS
12759 frames in 5.0 seconds = 2551.789 FPS
13083 frames in 5.0 seconds = 2615.906 FPS
12827 frames in 5.0 seconds = 2565.224 FPS
13220 frames in 5.0 seconds = 2643.806 FPS
13568 frames in 5.0 seconds = 2713.531 FPS
13489 frames in 5.0 seconds = 2697.795 FPS


fgl_fglxgears
Using GLX_SGIX_pbuffer
3208 frames in 5.0 seconds = 641.600 FPS
3432 frames in 5.0 seconds = 686.400 FPS
3443 frames in 5.0 seconds = 688.600 FPS
3442 frames in 5.0 seconds = 688.400 FPS
3434 frames in 5.0 seconds = 686.800 FPS
3438 frames in 5.0 seconds = 687.600 FPS
3509 frames in 5.0 seconds = 701.800 FPS

I still however have issues with this driver that are likely to take some work to resolve -

fgl_glxgears has NO texture on the cube on 8.41 -- weird weird weird

wine complains about visual ids when trying to start in opengl mode --

Have yet to make it to the X1650Pro AGP testing ...

This is gentoo - 2.6.22 and Xorg 7.1

The only changes twixt the two above tests are the DRIVER.

[dickeywang]

OK, I have reverted back to 8.40.
The new driver seems to improve the fps under 3D games by as much as 80%, but it breaks my 2D display. There are black lines in the lower right corner of my screen and when switching to a tab in Firefox that contains a lot of flash contents, it takes 2-3 seconds for the tab to display correctly.
Again, this is on a ATI Mobility X1400 (128MB video RAM) in Ubuntu Feisty.
I guess I will just wait until the next driver comes out.

[hobophobe]

There are two camps I'm seeing.

One camp takes the line that this driver is a work in progress and a step in the right direction. They are glad to see it regardless of its current functionality and quick to point out that the future is bright.

The other camp is still frustrated with the state of the driver as it is available to the public today. The bugs and problems have not been addressed. Most of these problems were introduced prior to 8.41 and did not exist at some point in the past. They are regressions that should have been fixed in the release.

A few points just to round out this post:

0. There's not going to be a non-R600 release this month. That breaks a long line of monthly releases by AMD/ATI.

1. As far as I know a rule of software is if release 1.1 introduces a fault then 1.2 should remove it.

2. AMD needs to link the KB articles listed in the release notes. I cannot find the corresponding article for some of them.

3. As it stands today my best graphics option for future computers is to run headless and use my damn imagination.

[h8er]

tested on my ati 9800 pro 128 mb on Kubuntu Feisty Fawn

h8er@ubuntu:~$ glxgears
30536 frames in 5.0 seconds = 6107.166 FPS
30389 frames in 5.0 seconds = 6077.646 FPS

h8er@ubuntu:~$ fgl_glxgears
Using GLX_SGIX_pbuffer
6595 frames in 5.0 seconds = 1319.000 FPS
6600 frames in 5.0 seconds = 1320.000 FPS

h8er@ubuntu:~$ fgl_glxgears -fbo
Using GL_EXT_framebuffer_object
5210 frames in 5.0 seconds = 1042.000 FPS
5190 frames in 5.0 seconds = 1038.000 FPS

with no FSAA but i don't know how to set it i cannot find an option in this new Catalyst Control Center lol there's no 3d sections

http://img166.imagevenue.com/loc1128/th_38619_aticc841_122_1128lo.jpg (http://img166.imagevenue.com/img.php?image=38619_aticc841_122_1128lo.jpg)

[greg]

Now after testing around a bit I can say that the driver works pretty well for me. :)

I'm using an X200M IGP - of course it's very slow and the driver can't do miracles. Before using this driver I had used the free r300 DRI driver, which is still very much in beta stage, at least for this particular card.

* Google Earth ran noticeably more fluid compared to r300
* Nexuiz was playable (it wasn't with the free r300 driver)
* Billiard-GL ran faster than with r300
* I noticed minor graphical artefacts, for example in glxgears
* No change in StepMania compared to r300 driver - nice! (the older fglrx drivers had some problems with it, I don't know why...)
* No 2D problems
* Xv works

Edit:
I just configured a dual-head with the control center. The control center is a little bit buggy, but it worked out and after X restart everything is working. Xv on both screen etc. It's unfortunate that so many people have problems with the driver, but for me it's almost flawless...

[Svartalf]

3. As it stands today my best graphics option for future computers is to run headless and use my damn imagination.

Sad, isn't it?

There's a reason why I've learned not to hold my breath on things- I like the color Blue, it just doesn't look good on my body...

I can only hope AMD can get the technical details out fast enough to make it worth our trouble to do something with their chips. Certainly it won't be with their drivers at this point. One step forward (performance) and two steps backwards (worse stability...). Ah, well, guess you can't have everything- I certainly don't have much more patience with this situation.

[ivanovic]

For me the driver seems to work rather nicely, especially considering that it is the proprietary amd/ati driver (the really bad past) and that it is the first driver based on a completely new codebase (huge rewrites tend to introduce *many* bugs, not always the result afterwards really is better/less buggy than what was there before). It looks like this new driver does not really have more problems than the old one already had of which none do really affect me.
The speed improvements are really great. Just as comparision (yeah, I do know that those are not meant as benchmarks...) some fps numbers from my system (C2D 6400, 1024MB Ram, ATI 9800Pro 128MB AGP, Gentoo Linux, vanialla 2.6.22 kernel):
glxgears:
8.40.4: ~3700fps
8.41.7: ~6670fps

fgl_fglxgears:
8.40.4: ~850fps
8.41.7: ~1400fps

I don't have real benchmarks for UT2004 but I did just play it for about one hour and it runs perfectly on 1600x1200 with everything at least at high details, some things even on a little more. I do get some graphics corruptions at 1920x1200, but with the old ones I did not even dare to try running this...
Another positive thing: The new driver is able to handle my screen correctly so that a 1600x1200 screen (or 1680x1050) does not get stretched somehow but just used the native pixels. Before neither the open r300 driver nor the 8.40.4 driver did so (though I did not test this one very much, I was using the open radeon driver exclusivly for ~1 year).

A rather bad thing about the proprietary driver compared to the open driver:
1) xvideo has to be "handactivated" in xorg.conf, with the open driver it "just works".
2) image quality in tvtime (it does need xvideo to work so that it can run) is not as good at with the open driver. Especially the OSD looks edgy where the radeon driver did provide a really sharp image. And the TV content shown does not look as crisp as with the open driver. I hope xvideo support in general will improve in the next revisions to come.

So far I can only say:
This driver seems to work nicely for me, at least as far as I can say after using it for about 2 hours. Render speed using KDE is no problem either but I can not really compare against the 8.40.4 driver since I was just using it for ~2h to get an impression of it's speed so that I can compare with the new one.
It seems to not render slower than using with the open driver. I am using xaa as render method, composite is turned off and no xgl/beryl/whatever is running. My config for those who want to compare:
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
BusID "PCI:1:0:0"
Screen 0
Option "MonitorLayout" "TMDS, NONE"
Option "AGPMode" "8"
Option "RenderAccel" "on"
Option "AccelMethod" "xaa"
Option "GARTSize" "64"
# needed for fluent usage of tvtime (with radeon *and* fglrx
Option "XAANoOffscreenPixmaps" "true"
# r300 driver options
# Option "EnablePageFlip" "true"
# Option "ColorTiling" "true"
# fglrx options
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "UseInternalAGPGART" "no"
EndSection

PS: It would be nice if someone could tell me how to create a benchmark of UT2k4 comparable to the benchmark results you can get using Windows and the benchmark utility shipped. The only way to create a benchmark that I found is described here:
Playing Unreal Tournament 2004 On Linux (http://www.linuxelectrons.com/features/reviews/playing-unreal-tournament-2004-linux)
And the results aren't really nice, the average fps shows the old driver being faster than the new one, but really crappy settings are being used (low resolution and low quality settings) so that it is only cpu dependant and not really much on the graphics card and its drivers.

EDIT:
I just tested Neverball, seems to work nicely in 1600x1200, too. Even reflections and shadows work nicely (they did not work with the r300 driver). Framerates do never go below 60fps (regarding the numbers shown ingame after pressing one of the F keys (was it F8, not 100% sure...).

[ltmon]

Hi All,

I've had mostly success with x1600 mobility. Desktop features/bugs/performance are pretty much the same, and OpenGL performance -- as noted -- is significantly better. It seems that the "new driver" is more correctly a "new OpenGL subsystem".

In any case, can anyone help me with the following:
1. I can't change any game display settings from within the game. This has occurred with two Q3 based games. Any resolution or other settings change causes a crash.
2. My brightness in each game is really, really low. I can't seem to change it -- the ingame sliders for gamma don't function. I can set my color gamma using amdcccle on the desktop, which fixes this a bit, but the colors are very wonky in that case.

Thanks,

L.

[hoenny]

Yes, you can basically remove those references since fglrx_dri.so is just a dummy file. It was meant to help package maintainers who didn't remove their fglrx_dri.so links in time, but before they announced fglrx_dri.so would temporarily be a dummy, I had already removed all traces of it and then had to go back in and add fglrx_dri.so back and I overlooked the x86_64 package.

if command follow, can i get the pkg?
su
rm -fr /usr/lib/dri/fglrx_dri.so
ln -s /usr/X11R6/lib/modules/dri/fglrx_dri.so /usr/lib/dri/fglrx_dri.so
ati-driver-installer-8.41.7-x86.x86_64.run --extract fglrx_tmp
./fglrx_tmp/packages/Fedora/ati-packager.sh --buildpkg F7

[Michael]

if command follow, can i get the pkg?
su
rm -fr /usr/lib/dri/fglrx_dri.so
ln -s /usr/X11R6/lib/modules/dri/fglrx_dri.so /usr/lib/dri/fglrx_dri.so
ati-driver-installer-8.41.7-x86.x86_64.run --extract fglrx_tmp
./fglrx_tmp/packages/Fedora/ati-packager.sh --buildpkg F7

You would be removing fglrx_dri.so on your local system and then linking to a file that doesn't exist. The problem isn't taking place on your local system but within the ATI package.

[hoenny]

You would be removing fglrx_dri.so on your local system and then linking to a file that doesn't exist. The problem isn't taking place on your local system but within the ATI package.

ok! I will try.
thank Michael.

[mjordan]

I'm having trouble getting the driver to work also. I'm switching from an old nvidia to a HD2600XT. The driver seemed to install but didn't seem to change my xorg.conf. I tried installing fglrx from the repository (I'm in ubuntu feisty) but no dice, then tried to sudo dpkg-reconfigure -phigh xserver-xorg to reset my xorg.conf to fglrx, and again no dice. When X starts I'm getting:

(EE) fglrx(0): === [swlDalHelperPreInit] === DALEnableInstance failed
(EE) fglrx(0): PreInitDal failed
(EE) fglrx(0): PreInit failed
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
KIO: fatal IO error 104 (Connection reset by peer) on X Server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.


also when installing the driver, like i said it seems to work (i don't get any error messages) but all I get after the red "ATI Technologies Linux Driver Installer/Package" is:


Detected configuration:
Architecture: x86_64 (64-bit)
X Server: X.Org 7.1 and later releases 64-bit
Removing temporary directory: fglrx-install.NE9681


I'm assuming this is all it's supposed to do.

Thanks

[Michael]

I'm having trouble getting the driver to work also. I'm switching from an old nvidia to a HD2600XT. The driver seemed to install but didn't seem to change my xorg.conf. I tried installing fglrx from the repository (I'm in ubuntu feisty) but no dice, then tried to sudo dpkg-reconfigure -phigh xserver-xorg to reset my xorg.conf to fglrx, and again no dice. When X starts I'm getting:

(EE) fglrx(0): === [swlDalHelperPreInit] === DALEnableInstance failed
(EE) fglrx(0): PreInitDal failed
(EE) fglrx(0): PreInit failed
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
KIO: fatal IO error 104 (Connection reset by peer) on X Server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
also when installing the driver, like i said it seems to work (i don't get any error messages) but all I get after the red "ATI Technologies Linux Driver Installer/Package" is:


Detected configuration:
Architecture: x86_64 (64-bit)
X Server: X.Org 7.1 and later releases 64-bit
Removing temporary directory: fglrx-install.NE9681
I'm assuming this is all it's supposed to do.

Thanks

To change your xorg.conf you need to run aticonfig --initial

The driver found in the Ubuntu repository is not 8.41 and thus doesn't support the HD 2600XT.

What does your xorg.conf look like? I've never seen that error on an R600 chip.

[container]

"1. I can't change any game display settings from within the game. This has occurred with two Q3 based games. Any resolution or other settings change causes a crash."

Yeah, I can reproduce that, in tremulous (q3 engine), but resolution switching did work in UT2004. While this certainly didn't happen before, I expect that it will be fixed in the next driver version - after all, this release was primarily intended to introduce high-end support, I guess? Or it's a fringe event that only happens with the q3 engine and this new driver base, in which case it might not draw attention. Also, since my last post, I noticed that some 3D games that used to work with Wine now don't... no big loss there.