ATi Open drivers are coming of age... :)

[handy]

- deleted redundant data 24-August-10. Added Gallium link 26-October-10. Added Fan Control 15-November-10. Power Management how-to re-added on 22-November-10. Refined the Ubuntu Stuff how-to & updated due to progress on the North Island GPU 13-3-11. Made note of the acceptance of Gallium as the default open-source AMD driver stack, & added link to benchmark & discussion on the topic - 9-June-11. Updated text, added a links which provides detailed Catalyst removal instructions; courtesy of Temüjin - 11-June-11. Over the last couple of months I've picked up about 400fps in (the not a benchmark) glxgears, on my HD2600 Pro, which is nice - 24-August-11.

For anyone interested in seeing just how the open-source support is coming along for the various ATi cores, this is the easiest way to get the picture:

http://www.x.org/wiki/RadeonFeature

The following link is available on the above page but here is the Gallium stuff anyway:

http://www.x.org/wiki/GalliumStatus

[edit:] Now that the Gallium driver stack has taken over, the information on the "Classic Mesa" stack is basically redundant for the many.

Following is a link to a very worthwhile read from the Phoronix site. At the current time of writing, it brings us up to date:

May 2011: Gallium3D vs. Classic Mesa vs. Catalyst

http://www.phoronix.com/scan.php?page=article&item=amd_mesa_mai2011
_________________________


I thought that I probably should put the following information out here in a dedicated thread, for those that aren't aware of what is going on with the AMD/ATi open-source drivers:

Because AMD/ATi's Catalyst drivers have been so unreliable, it has caused & is causing a great deal of work to go into the ATi open-source drivers & associated packages.

The oft neglected reality, is that AMD have been releasing technical info' on the ATi GPUs, & contributing some code. Without AMD having done this, the open-source ATi drivers would not be developing at the rapid rate that they currently are. So in this regard, gratitude to AMD is most certainly in order.

The current open-source ATi GPU drivers are giving many people the best 2D performance they have ever had on their ATi GPU's, I can verify this because I'm one of them. At this stage the 3D is working well but still too slow for games with sophisticated 3D graphics & lots of movement. Though the quake engined games play quite well with the open source packages.

Since AMD released the tech' info' for the Evergreen & now the (current) North Island series of GPUs, work has been moving fast & now at last the open-source support for the current ATi GPUs is starting to manifest.

Ubuntu 11.4. is using the Gallium driver stack, the classic Mesa is now deprecated.
For users that want to use later versions of the kernel &/or the Gallium driver stack, there is a simple how-to in the "Ubuntu Stuff:" section further down the page.
___________________________

I'll continue to put any links that I find to be useful on this topic here:



X.org:

http://www.x.org/wiki/GalliumStatus

http://wiki.x.org/wiki/RadeonFeature

http://wiki.x.org/wiki/RadeonProgram


Arch stuff:

Arch ATi how-to from the wiki, quite informative:

http://wiki.archlinux.org/index.php/Ati#


Ubuntu stuff:
========================================
For Ubuntu users, this is a how-to for upgrading your kernel & the rest of the driver stack so you can use the latest git versions, which usually offer added features & better performance than those supplied in the most current Ubuntu version.

This how-to is now followed by another for getting Power Management working courtesy of a post in this thread by Untitled_No4: :)

Do the following in the order listed:

1. System -> Hardware Drivers -> Deactivate any ATI drivers and restart. (If you need more detailed instructions on this go here (http://wiki.cchtml.com/index.php/Ubuntu_Maverick_Installation_Guide#Removing_Cataly st.2Ffglrx).)

2. Go to http://kernel.ubuntu.com/~kernel-ppa/mainline/
& pick the version of the kernel you want to use, (I am on Arch & using the current kernel .**-git & the -git versions of the other required packages with no problems. So keeping an eye on the last parts of this thread should let you know if there are any current problems).

3. Download and execute the following (in this order, switch to 64 if need be)
- linux-headers...all.deb
- linux-headers..generic..i386.deb
- linux-image....i386.deb

4. Restart

5. Add the xorg-edgers PPA (https://launchpad.net/~xorg-edgers/+archive/ppa)

6. update & upgrade:


sudo apt-get update
sudo apt-get dist-upgrade

7. Reboot.

8. Profit. :)


Power Managment:
========================================

With KMS:
There are two sys-files in /sys/class/drm/card0/device:
power_method: Here you can switch between dynpm and profile method.
power_profile: If you have enabled profile method you can choose between default low, high and auto (select between low and high based on ac/dc state)
For example: echo profile > /sys/class/drm/card0/device/power_method

Without KMS:
In your xorg.conf file, add 2 lines to "Device" Section:
Option "DynamicPM" "on"
Option "ClockGating" "on"
--------
If the two options are enabled successfully, you will see following lines in /var/log/Xorg.0.log:
(**) RADEON(0): Option "ClockGating" "on"
(**) RADEON(0): Option "DynamicPM" "on"
......
Static power management enable success
(II) RADEON(0): Dynamic Clock Gating Enabled
(II) RADEON(0): Dynamic Power Management Enabled
--------
If you desire low power cost, you can add an extra line to "Device" Section of xorg.conf:
Option "ForceLowPowerMode" "on"


Thanks to Perry3D at the Arch forum for the above.
________________________


A Free Way to Cool OFF Your Stock ATi/AMD GPU:

http://forums.amd.com/forum/messageview.cfm?catid=13&threadid=109000&messid=970779&parentid=970616&FTVAR_FORUMVIEWTMP=Single

(thanks to tomazzi & olof_ for bringing the above to my attention :))
____________________


About/identify your AMD/ATi GPU:

http://en.wikipedia.org/wiki/Comparison_of_ATI_graphics_processing_units


This page contains information about Radeon chipset naming, and some other, possibly outdated information:

http://dri.freedesktop.org/wiki/ATIRadeon#head-a2d41d14a2c9b0da964aa1b7226ebab238532abe

[xir_]

i got a new laptop with a hd4330 and the binary drivers are horrid, really just horrid.

i'm considering going back to the open source drivers. but i hear the power management is poorer on these. What are your experiences?

[Barrucadu]

Unfortunately I still have awful performance with the FOSS drivers - OpenGL is completely unusable.

[stwschool]

I'm certainly curious to see where this leads. I've got one NVidia box and an ATI laptop and I have intel machines at work so I want to see excellent drivers on all. At 9.04's release I'd say only NVIDIA was any good. The intel drivers were reliable and you could play Wine games on them but they were slow (and still are).

The ATI situation is interesting though. I downloaded and installed the new drivers directly from ATI and found a massive improvement in quality, reliability and performance, obviously your mileage may vary. Now if that's rocking and the open-source drivers are getting good too then that's a winner for all of us. So, all we need is better intel drivers and we'll have very high quality across all 3 platforms.

[racerraul]

I'll jump ship when things get where they need to be for ATI drivers to provide all the power the HW is capable of...

By then it may be time to upgrade my Nvidia cards.

[handy]

i got a new laptop with a hd4330 and the binary drivers are horrid, really just horrid.

I'm considering going back to the open source drivers. but I hear the power management is poorer on these. What are your experiences?

Sorry man, I'm no expert on the open-source ATi stuff. I don't use a notebook so I can't comment from personal experience. It wouldn't surprise me if the power management wasn't up to par, it is very likely (to my mind anyway) one of the things you would deal with later rather than earlier.

To find out about what is being worked on, on the cutting edge on this subject is not an easy thing to do on the web, if you have a look at this site it may be the easiest solution, if you do I'd head for the last 5 pages or so:

http://bbs.archlinux.org/viewtopic.php?id=57084&p=1


Unfortunately I still have awful performance with the FOSS drivers - OpenGL is completely unusable.

It has very recently got great for 2D for many cards, 3D is just starting to happen for many cards, as those who are using packages from .git are finding. I think it would be a good idea to keep an eye on it Barrucadu as it is changing quickly.



I'm certainly curious to see where this leads. I've got one NVidia box and an ATI laptop and I have intel machines at work so I want to see excellent drivers on all.

Intel see their major market being in Asia, so their graphics hardware is middle of the road at best. Though they are offering better Linux driver support lately.



The ATI situation is interesting though. I downloaded and installed the new drivers directly from ATI and found a massive improvement in quality, reliability and performance, obviously your mileage may vary.

The way it is with the AMD/ATi Catalyst drivers, is that you take pot luck every time a new Catalyst version is released; sometimes they are better, other times they are worse...



Now if that's rocking and the open-source drivers are getting good too then that's a winner for all of us. So, all we need is better intel drivers and we'll have very high quality across all 3 platforms.

The open-source drivers are getting better & really quickly lately. Intel will get better as their perceived market in Asia demands/can afford it.

The bottom line is that people with ATi GPU's should keep an ear to the ground as the FOSS people have got some momentum on for you at the moment.

[CharmyBee]

OpenGL is completely unusable.

Same here. The driver isn't very good if it's treating your card as an expensive 2D overlay. You might as well stick a s3 Trio 64v in there, it's just as good.

[spoons]

It seems to be getting better and better but by the time some decent 3D appears it'll probably be a good 6-12 months before a distro has it, as we have to wait until the next Mesa build and then hope it comes in the Ubuntu right after that.

[Regenweald]

Thanks for the update handy, from what I've been reading on Phoronix, for a next build I'd gamble on a full AMD platform. I could live without 3d for a bit :)

[Barrucadu]

It has very recently got great for 2D for many cards, 3D is just starting to happen for many cards, as those who are using packages from .git are finding. I think it would be a good idea to keep an eye on it Barrucadu as it is changing quickly.

As soon as another kernel (or whatever) upgrade breaks Catalyst again I'll check out the git version :)

[tcturner]

tormod volden ppa is excellent google it

[Firestem4]

I'm not sure why but my ATI 1950Pro 512mb from DaimondMM runs perfectly on Kubuntu 9.04 (performance, KWin effects, etc). Haven't tried any actual games yet because i haven't been able to get sound to work so i didn't wanna do too much to it before I did anything.

(also i have added no extra drivers..did a vanilla install of Kubuntu 9.04 and it works OoTB)

Glad to hear the ATI drivers are improving though as I am a huge ATI fan. With them releasing the specs on so many of their chipsets/GPU's it should help tremendously with the development of ATI drivers.

[Ranax]

I wish I could agree with this, but I find the total opposite to be true. I have been using bleeding edge Radeon OPSO drivers for about 3 months now and they have been pretty bad. They serve 2D ok, but for 3D they are useless. I know this will hopefully improve in the future, but at the minute they may as well just be called Compiz enablers.

[Methuselah]

For a long time I used ATI open drivers and passed on 3D.
When I needed 3D I had no choice but to go with NVidia despite hating binary blobs.
Unfortunately, I would have had to use ATI's blob to get 3D and NVidia's was the lesser of two evils.
This time, I'll wait until ATI's open drivers are ready before going with them again.

[Ranax]

For a long time I used ATI open drivers and passed on 3D.
When I needed 3D I had no choice but to go with NVidia despite hating binary blobs.
Unfortunately, I would have had to use ATI's blob to get 3D and NVidia's was the lesser of two evils.
This time, I'll wait until ATI's open drivers are ready before going with them again.

I can only hope that they improve to a level beyond the horrible Intel linux drivers.

[handy]

I just read over on the Arch forums, that there was an update yesterday to the development drivers & people were commenting on the speed increase in 3D.

They are really happy with just how fast the dev's are working on this stuff.

[kk0sse54]

I've been using the open source driver for the last few months because 1) There's no proprietary ATI driver for FreeBSD and 2) ATI dropped support for my card anyways, but overall I've been quite impressed. I've been getting better video performance with my Fbsd gnome + compiz setup than before with the closed source drivers. Although other than compiz I don't really need 3D as I don't play games or anything else of that nature.

[madjr]

I just read over on the Arch forums, that there was an update yesterday to the development drivers & people were commenting on the speed increase in 3D.

They are really happy with just how fast the dev's are working on this stuff.

how can we try this on ubuntu?

[handy]

how can we try this on ubuntu?

Someone else will have to give you that run down.

Personally, if you can, I'd wait a while, as, as far as 3D support is concerned you will most likely be disappointed; 2D is great, though it is possible that some ATi GPU's aren't supported, on this I can't say for sure.

The best I can do is tell you that I've not heard any complaints in the Arch thread in regard to 2D.

3D seems to be moving along quickly, but that "quickly" is a relative term, as it is closely bound with the perceptions of quality. :)

Some people are far more impatient than others...

The later posts in the link below will give you info' regarding what the Arch guys are using, how you deal with that in Ubuntu is your business, though I do ask, if anyone does apply those packages in Ubuntu, could you please post how you did it, & your experience here in this thread?

http://bbs.archlinux.org/viewtopic.php?id=57084&p=1

[ssri]

how can we try this on ubuntu?

You can check the latest of the latest from obtaining the source from git and compiling yourself

http://ubuntuforums.org/showthread.php?t=1017975&highlight=ati+xserver-video-ati+slow

Tormod Voldon's packages tries to keep up with the latest developments:

https://launchpad.net/~tormodvolden/+archive/ppa

For more stable upstream releases try:

https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates

[rocknrolf77]

Personally, I'm sick of the catalyst driver. 1 month everything works fine and the next nothing works. Why the hell can't they support the newest kernel like nvidia does? Bought an ati card, because amd never let me down earlier and I always support the underdog + you get most bang for your buck with ati cards. Can't afford nvidia's prices.

But it's nice to hear the good news about the open driver these days.

[tom66]

Unfortunately my Mobility Radeon HD 3400 in 3D is only supported for proprietary drivers. Accelerated 2D support is available. But at the rate that development is happening, a working FOSS driver should be available within 1 year.

Edit: Just read some info, it says that they've got 3D support for my hardware but it's very buggy right now... looks like it might be sooner than I thought. :)

[handy]

In future, I'll add any useful sites I come across, regarding this topic, at the bottom of Post_1 (http://ubuntuforums.org/showthread.php?t=1238129) of this thread:

http://wiki.x.org/wiki/RadeonFeature

http://wiki.x.org/wiki/RadeonProgram

http://bbs.archlinux.org/viewtopic.php?id=57084&p=1

http://www.phoronix.com/scan.php?page=category&item=Display%20Drivers

[handy]

Catalyst 9.8, has been quite recently released.

It is working with the .30 kernel, without patches & is behaving much better than it has been lately.

It still has problems of course.

Many think it has been produced for the upcoming Ubuntu release?

[sideaway]

What about us obsolete folk? :(

I'm sitting on an x1400, and they've ditched me, rejected me for the younger model. I feel like an old worn out hoo... Won't go there. Anyways, I want proprietary support! Or atleast open the source code of the drivers so we can get some decent ones.

[handy]

As previously stated in this thread; the open-source ATi driver development is moving fast.

There are links at the bottom of the first post which should hopefully verify that your card has an open-source future dawning soonish...

[ssri]

As previously stated in this thread; the open-source ATi driver development is moving fast.

There are links at the bottom of the first post which should hopefully verify that your card has an open-source future dawning soonish...

If soonish means by next summer, then you are correct. As for TVOut though, it is still unworkable in R500s. That means I have to reboot to winxp in order to make my presentations or watch video from my laptop on my TV.

[handy]

If soonish means by next summer, then you are correct. As for TVOut though, it is still unworkable in R500s. That means I have to reboot to winxp in order to make my presentations or watch video from my laptop on my TV.

I don't personally know when, soonish means what, & for which GPU?

All I know is that it is all in the works, not on the backboard.

I, as does most every other user of a Linux/BSD system endowed with an ATi GPU, live in perpetual hope, that the open-source solutions to our many GPU problems will appear today. :)

[ssri]

I, as does most every other user of a Linux/BSD system endowed with an ATi GPU, live in perpetual hope, that the open-source solutions to our many GPU problems will appear today. :)

I completely agree with you 100%. Although, my hope is tempered by a dash of realism ;). Still, the drivers are undoubtedly improving and have come a long way. Hopefully we ATI users will reach the promise land someday.

[handy]

I completely agree with you 100%. Although, my hope is tempered by a dash of realism ;). Still, the drivers are undoubtedly improving and have come a long way. Hopefully we ATI users will reach the promise land someday.

As previously stated, I no longer rely on the Catalyst drivers, as I don't need 3D on my Arch install, & the open-source drivers now provide me with the snappiest 2D the machine has ever experienced.

That change just happened one day.

I only use the public release packages not the pre-release versions.

The same thing is going to happen with 3D & the open-source drivers, it is already happening for some GPU's using the pre-release packages.

[nomnomnom]

nutkinnz waz ere' init

[yodermk]

Any chance that Karmic will have newer ATi 3D support? (I have a 3200HD.)

I refrained from installing the proprietary blob in Jaunty in hope that open source support would be ready for Karmic. Not sure if I can wait for the L release ...

[handy]

Any chance that Karmic will have newer ATi 3D support? (I have a 3200HD.)

I refrained from installing the proprietary blob in Jaunty in hope that open source support would be ready for Karmic. Not sure if I can wait for the L release ...

I don't know, check out the links at the end of the first post in this thread, you should learn something useful with regard to the open-source drivers & your GPU, there.

Most people find the current Catalyst version 9.8 is reasonably good from what I read.

Quite a few people think that the reason the current Catalyst version is working better, is due the upcoming Ubuntu release.

Use Catalyst if you have to, to meet your 3D needs. Though the day is fast approaching when you won't need Catalyst.

It is wise to temper the above statement with an understanding for the range of various values that people will place on the pertinent variable "fast". :)

[madjr]

Any chance that Karmic will have newer ATi 3D support? (I have a 3200HD.)

I refrained from installing the proprietary blob in Jaunty in hope that open source support would be ready for Karmic. Not sure if I can wait for the L release ...

they better

[BuffaloX]

I'm on Ubuntu 9.04 with a Radeon 4770.
My Nvidia Gforce 7950 GX2 which cost a gazillion burned out, exactly one month after my wifes identical card burned out.
That's two Gazzilions out the windows after only 2½ years of use!
I Didn't want to reward Nvidia by buying more of their defective designs.
So we both went ATI, she use Ubuntu 8.10 because she need realtime Kernel.
With the Nvidia Realtime didn't work unless she used Ubuntu 8.04, Ati was one step up in that regard.

For me I'm very happy, My computer is now almost completely silent, because the Radeon 4770 use very little power the fan doesn't have a lot of work to do. The card was cheap too, and works fine for games in Windows.

I installed latest ATI drivers at the time, and it works fine with Compiz.
I don't do a lot of 3D stuff, but I haven't noticed any problems.

We both wanted to try ATI, especially because we hope the opened specs will help accelerate the development of good open source drivers.

I'm very happy to see this positive thread about it. :)

[racerraul]

... (I have a 3200HD.)


Same here... I have 9.8 on my laptop and Compiz support isn't quite right yet. I have not tried any games on it though since I don't have a need to game on my laptop.

[handy]

Here is a quote from a post by Mazur in the Arch forums that may interest some of you:

I have installed mesa-git with xf86-video-ati-git and other packages and I need to say that I am looking forward to get full 3d support. It works awesome on simple games like supertux etc. but Quake Live still got bugs. I didn't tried Compiz. ANybody know if radeonhd-git works better? I got HD3200.

[toupeiro]

Over the years, I think ATi has proven itself time and time again to have better hardware than NVidia, but crappier drivers. This is true not only in linux space, but windows as well. ATi card owners can enjoy much longer performance lifespans with their cards because as the drivers mature, the cards perform better. At least, in windows, this has always been the case. NVidia's cards have more drastic decline over time in the performance market, and you will be replacing hardware more frequently for the next noticeable performance boost. Better ATI drivers, open or closed, is wonderful news, but even better because the progress is being seen in the open drivers.

[handy]

AMD/ATi have released Catalyst 9.10 for Ubuntu 9.10.

https://lists.ubuntu.com/archives/karmic-changes/2009-September/008022.html

[DougieFresh4U]

AMD/ATi have released Catalyst 9.10 for Ubuntu 9.10.

https://lists.ubuntu.com/archives/karmic-changes/2009-September/008022.html

Using it with my Karmic 64bit. I have the ATI Radeon HD3200 and seems to be running smooth. Played around with compiz some and all was good.
'Hardware Drivers' installed fglrx, rebooted with out any drama.

[Exodist]

On my 4850 the drivers from ATI/AMD website are super fast and rock solid.
The drivers Ubuntu says are proprietary and wants to install after installing ubuntu are complete garbage. IF those drivers are from ATI then they must be old. Very old..

Catalyst drivers from ATI tho, running 9.8 on 2.6.30.5 kernel. Super Fast and Rock Solid!

[handy]

Of late, the versions of kernel & Catalyst have been critical. If you don't have a matching pair you are in trouble, if you do have a matching pair you are in a lot less, just how much less all comes down to the particular pair.

We have been finding that regression is unfortunately far too often a part of the Catalyst progression. :(

Meaning, empirically people are experiencing the situation where a not perfect, but still a happy working situation, can be shot to pieces by the next Catalyst (or kernel, or X.server) upgrade!?

[ELD]

I have as of today done a fresh install of Jaunty with the latest drivers from amd's ati site and so far it seems to be a lot better (before my pc would totaly freeze up half the time, been about 3 hours now and not a single lockup, things are looking up :D). I hope i don't jinx this heh.

I think as someone said before through the hardware drivers manager it must have a quite old version of the ati drivers, i think that is actually what caused my freezing issues before!

[handy]

Catalyst 9.10 leaked, is being installed & tested by some Arch users.

At this early stage it has been found to be better in some areas, worse than 9.8 in others.

[matthew1471]

I wonder if the new Catalyst will work with my 200m.

I don't suppose they'd re-add support for older hardware after they've already removed it.

If they did re-add support, maybe it would fix this odd problem http://ubuntuforums.org/showthread.php?t=1251849

[handy]

I'd certainly be extremely surprised if they add support for something that they have previously stopped supporting.

[handy]

Reportedly Flash is still as bad or worse than it was with Catalyst 9.8.

[racerraul]

I Didn't want to reward Nvidia by buying more of their defective designs.


I don't blame you for being upset with your HW going bad. I would be too.
But unless you have some scientific data to support a known design flaw in a specific product, I wouldn't go rambling around about it.

I think you were a victim of rotten luck for sure. But would question if this is a common trait of the 7950 Gx2 product line or perhaps the outcome of improper cooling or power supply, rather than chucking it up as Nvidia's product somehow being flawed.

I have an Nvidia 4200 (from 2002), a 7600, 9500 & 9600 that are working just fine.

I did have an Nvidia Quadro m135 take a crap on a laptop, but I know for a fact that met its death due to over heating, and I consider that my fault because I noticed too late that the fan for the card was clogged with dust. I've managed to kill a few procs that way as well...

Just a heads up... if you are taking care of all that then, yeah it sucks to have rotten luck... but if you have some concrete proof that Nvidia designs nothing but flawed products... lets have the test data. I genuinely want to see it.

[racerraul]

Reportedly Flash is still as bad or worse than it was with Catalyst 9.8.

I wasn't aware that flash used 3d acceleration.

That said, flash is bad on anything and worse on everything :P

[misfitpierce]

The proprietary ones for ubuntu were giving me trouble in 9.04 but the newest opensource one is quite good... Seen huge improvments in it and its doing great... Cant even really tell difference any more... I give it another 6 months or so and ATI opensource drivers will be amazing. Opensource ATI drivers are coming along very nicely!

[BuffaloX]

I don't blame you for being upset with your HW going bad. I would be too.
But unless you have some scientific data to support a known design flaw in a specific product, I wouldn't go rambling around about it.

I think you were a victim of rotten luck for sure. But would question if this is a common trait of the 7950 Gx2 product line or perhaps the outcome of improper cooling or power supply, rather than chucking it up as Nvidia's product somehow being flawed.

I have an Nvidia 4200 (from 2002), a 7600, 9500 & 9600 that are working just fine.

I did have an Nvidia Quadro m135 take a crap on a laptop, but I know for a fact that met its death due to over heating, and I consider that my fault because I noticed too late that the fan for the card was clogged with dust. I've managed to kill a few procs that way as well...

Just a heads up... if you are taking care of all that then, yeah it sucks to have rotten luck... but if you have some concrete proof that Nvidia designs nothing but flawed products... lets have the test data. I genuinely want to see it.

You gotta be kidding me, Nvidias defective GPUs are a well known fact, a problem that spanned entire lines and generations of GPUs.
Unfortunately many just made it through the warranty period, like mine did, almost 2000$ out the window, my two cards burned out like they were on a clock, and the problem is officially acknowledged.

Just google Nvidia defective, and you get results already on first page about official reports on entire lines of Dell, Sony and HP computers affected by the defective Nvivia GPUs.

On top of that, I actually knew about this problem early on, and I took extra care to keep both coolers clean on each card, monitored temperatures regularly, and both cases are big towers with very good air flow. There is absolutely no good reason these cards should die so soon.

[handy]

Good info' on this page regarding changes to the .31 kernel (& beyond). Of particular interest to the topic of this thread due to changes that relate to the AMD/ATi GPU:

http://www.h-online.com/open/Kernel-Log-Coming-in-2-6-31-Part-2-Graphics-audio-and-video--/news/113958

[PurposeOfReason]

Does anyone know if it is possible to have one monitor in portrait mode and another in landscape for a dual monitor setup.

[handy]

The .31 kernel came out of testing for Arch yesterday.

After installing it, I experienced a regression (slow down in graphic drawing speed) due to the newly incorporated kernel mode-setting (KMS) capacity.

It was easily fixed as follows:

The solution is to disable experimental KMS and fall back to the old behavior. Add the radeon.modeset=0 into the kernel append line in /boot/grub/menu.lst


[Edit:] I probably should mention (again) that I'm using the open-source ATi drivers. There is more detailed info' on this subject for both open & the catalyst drivers to be found here (http://wiki.archlinux.org/index.php/ATI#AMD.2FAti_cards_and_KernelModeSetting_.28KMS.2 9). /edit

[Exodist]

good info.. Many thanks.

[handy]

It looks like Catalyst 9.10 is trying to get out into the wild:

http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.36&lang=English

[edin9]

You gotta be kidding me, Nvidias defective GPUs are a well known fact, a problem that spanned entire lines and generations of GPUs.
Unfortunately many just made it through the warranty period, like mine did, almost 2000$ out the window, my two cards burned out like they were on a clock, and the problem is officially acknowledged.

Just google Nvidia defective, and you get results already on first page about official reports on entire lines of Dell, Sony and HP computers affected by the defective Nvivia GPUs.

On top of that, I actually knew about this problem early on, and I took extra care to keep both coolers clean on each card, monitored temperatures regularly, and both cases are big towers with very good air flow. There is absolutely no good reason these cards should die so soon.

That's true. As much as I dislike ATi, they're stuff lives longer than nVIDIA's.

[MisfitI38]

The .31 kernel came out of testing for Arch yesterday.

After installing it, I experienced a regression (slow down in graphic drawing speed) due to the newly incorporated kernel mode-setting (KMS) capacity.

It was easily fixed as follows:

The solution is to disable experimental KMS and fall back to the old behavior. Add the radeon.modeset=0 into the kernel append line in /boot/grub/menu.lst


[Edit:] I probably should mention (again) that I'm using the open-source ATi drivers. There is more detailed info' on this subject for both open & the catalyst drivers to be found here (http://wiki.archlinux.org/index.php/ATI#AMD.2FAti_cards_and_KernelModeSetting_.28KMS.2 9). /edit

I too experienced a regression in glxgears with KMS+xf86-video-ati vs. without KMS. (~300fps vs ~1200fps.)
However, I have not disabled it, as it is still functional and I quite like the efficient use of my entire monitor's real estate via the framebuffer. X also starts up very quickly. 2d acceleration still works great.
Still waiting.....................

[edin9]

I too experienced a regression in glxgears with KMS+xf86-video-ati vs. without KMS. (~300fps vs ~1200fps.)
However, I have not disabled it, as it is still functional and I quite like the efficient use of my entire monitor's real estate via the framebuffer. X also starts up very quickly. 2d acceleration still works great.
Still waiting.....................

glxgears is not reliable. It gives my laptop on the opensource Radeon drivers 6000+, but on my 8800 SLi it gives 300.

[MisfitI38]

glxgears is not reliable. It gives my laptop on the opensource Radeon drivers 6000+, but on my 8800 SLi it gives 300.

Heh. The old "glxgears is not a benchmark" spiel. (http://bbs.archlinux.org/viewtopic.php?pid=430212#p430212) ;)
It is quite possible to use glxgears scientifically, especially on the same machine with the only difference being the enabling/disabling of KMS.

[handy]

I too experienced a regression in glxgears with KMS+xf86-video-ati vs. without KMS. (~300fps vs ~1200fps.)
However, I have not disabled it, as it is still functional and I quite like the efficient use of my entire monitor's real estate via the framebuffer. X also starts up very quickly. 2d acceleration still works great.
Still waiting.....................

For me, the scrolling of web pages in Firefox was quite jerky, which was the primary problem for me, the moving around of any windows & scrolling in them was also jerky.

So, I'm still waiting too...... :)

[Pasdar]

For me, the scrolling of web pages in Firefox was quite jerky, which was the primary problem for me, the moving around of any windows & scrolling in them was also jerky.

So, I'm still waiting too...... :)

Install Chromium... I never looked back again!

[handy]

Install Chromium... I never looked back again!

I like Firefox, & am dependent on one of its add-ons too.

The problem had nothing to do with Firefox anyway; it is to do with the ongoing development of the open-source support for ATi GPUs.

[handy]

Really positive feedback on the Arch forum regarding the ATi R600 & R700 with the latest open-source drivers, kernel & associated packages.

The best 2D/3D performance ever experienced on this category of ATi GPU!

This is what all of us with ATi GPUs are now patiently standing in line waiting for.

Most excellent news indeed. :guitar:


Here is some how-to info' from the Arch forum, for anyone interested:

http://bbs.archlinux.org/viewtopic.php?id=79509

[handy]

Here is a good link from Phoronix, it is well worth reading:

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

[handy]

I've personally just installed the catalyst 9.10 packages, for no other reason (& it is fortunately a good one :)) than I have started going through the games presented by DJL (http://en.djl-linux.org/) (which is available for Ubuntu in the repo's too I believe).

I now, have a strong desire for 3D, which can not be met (easily, if at all) by any other means at the moment (for my ATi GPU) than by using the catalyst clump.

This is not like a defeat or anything... lol!

What it is, is just exactly what you do whilst waiting for the inevitable, desired solution to manifest. :)

& manifesting it is, it just takes a while to do it for all those that desire it... :D

I certainly take my hat off (that means respect for you young dude's) to ALL of the people that have been involved over the years in creating the wonderful change that we ATi GPU users (& others in the end) are starting to be treated to!!!

Thank you.

[handy]

For anyone who upgrades beyond the standard Ubuntu systems, or uses Arch or similar; it has been found that catalyst 9.10, is not compatible with the newly released xorg 1.7.

So don't upgrade if you want to see anything via X.

There are no patches or anything available, & no catalyst upgrade is expected for some time unfortunately.

[xir_]

thanks for keeping this topic up-to date.

i think that the fglxr driver will start to become redundant from lucid (seeing as there should be a good couple of kernel version between now and then.

Makes sense from the POV of amd, far less work for them if the community is willing to drive development.

[kasm]

How do you enable KMS in Ubuntu?

[handy]

How do you enable KMS in Ubuntu?

It is on by default in the .31 kernel. Which I believe Ubuntu 9.10 is using.

[handy]

Further on the xorg 1.7, catalyst 9.10 incompatibility;- the following site is carrying a working list of the files that need to NOT be allowed to upgrade if you want to maintain compatibility with catalyst 9.10:

http://hpaste.org/fastcgi/hpaste.fcgi/view?id=11386#a11386

From experience, this list is a fully functional workaround, though it is all in all a very clumsy situation.

Bring on the open-source solution so we can be rid of ridiculous situations like this one. :(

[xir_]

Further on the xorg 1.7, catalyst 9.10 incompatibility;- the following site is carrying a working list of the files that need to NOT be allowed to upgrade if you want to maintain compatibility with catalyst 9.10:

http://hpaste.org/fastcgi/hpaste.fcgi/view?id=11386#a11386

From experience, this list is a fully functional workaround, though it is all in all a very clumsy situation.

Bring on the open-source solution so we can be rid of ridiculous situations like this one. :(

i'm currently playing around with the zen .32 kernel from git and am going to try to see if my full-screen video performance is improved by DRII.

To be fair you have to give credit to amd for giving us the specifications, nvidia have stated that they have no intention of doing the same.

[handy]

i'm currently playing around with the zen .32 kernel from git and am going to try to see if my full-screen video performance is improved by DRII.

To be fair you have to give credit to amd for giving us the specifications, nvidia have stated that they have no intention of doing the same.

In this thread I have given AMD credit for that multiple times. Many are very grateful for AMDs help in that regard.

Let us know what happens with your test?

Is it possible in Zen to add an "ignorepkg =" list to your upgrades as in Arch, or does Zen use an individual install type system?

[xir_]

simple as it didn't work. I even compiled messa so that it would support it.

as far as ignorepkg = goes i'm not sure to what you are referring.

I'm using the Zen kernel only inside ubuntu and I'm compiling from source, i felt like trying out their claimed Linux kernel for the desktop, so far its exactly the same.

My hope was that there would be improved drivers in the 32 kernel branch but every time i try to enable compiz it fails.

[togo59]

For anyone who upgrades beyond the standard Ubuntu systems, or uses Arch or similar; it has been found that catalyst 9.10, is not compatible with the newly released xorg 1.7.

So don't upgrade if you want to see anything via X.

There are no patches or anything available, & no catalyst upgrade is expected for some time unfortunately.
Could you clarify what you mean by "beyond the standard Ubuntu"?

(I was just about to install AMD/ATI Catalyst 9:10 (version 8.661) in order to get decent 2D support for my Radeon HD 3400.)

[Pasdar]

Could you clarify what you mean by "beyond the standard Ubuntu"?

(I was just about to install AMD/ATI Catalyst 9:10 (version 8.661) in order to get decent 2D support for my Radeon HD 3400.)

It means dont change major parts of the system... its nothing any normal user should worry about... because many users here have no idea on how to (for example) manually update their kernel or other such things...

[handy]

simple as it didn't work. I even compiled messa so that it would support it.

as far as ignorepkg = goes i'm not sure to what you are referring.

I'm using the Zen kernel only inside ubuntu and I'm compiling from source, i felt like trying out their claimed Linux kernel for the desktop, so far its exactly the same.

My hope was that there would be improved drivers in the 32 kernel branch but every time i try to enable compiz it fails.

My understanding (from what I've read) is that these days, due to the way the kernel is made (which I take to mean an inbuilt efficiency that did not exist in the past), it is uncommon for someone to notice any performance difference after recompiling the kernel to suit their system perfectly.

Those in the know say it is actually a waste of time.



Could you clarify what you mean by "beyond the standard Ubuntu"?

If you are going to start playing with different kernels, .git packages, or going with one of the 2 open-source ATi GPU systems. Or if you are using a system other than Ubuntu, such as Arch for example.



(I was just about to install AMD/ATI Catalyst 9:10 (version 8.661) in order to get decent 2D support for my Radeon HD 3400.)

If you want decent 2D support, you will be best served by the open-source packages, they are far superior to Catalyst in 2D.

The best performance is generally found with the xf86-video-ati package.

You may have to do some research regarding the installation & setup of this on Ubuntu. I can't help you with that, as I have only used it on Arch.

[handy]

AMD Loses Its Linux Core Engineering Manager, Matthew Tippett

AMD's Catalyst Linux driver has improved substantially over the past few years. Years ago the Catalyst Linux driver was in shambles with its performance being utterly poor, it lacked enthusiast-oriented features like CrossFire and OverDrive, and ATI customers had to wait months -- sometimes in excess of a year -- for any driver support in Linux. All of this though has changed with AMD now providing same-day Linux support, a near feature parity to the Windows Catalyst driver, and first-rate performance. Playing a critical role in improving the ATI Linux support has been Matthew Tippett, serving as the engineering manager for Linux Core Engineering since joining ATI Technologies in 2003. To put it in perspective, when Matthew started work at ATI, only the FireGL graphics cards were supported under Linux. However, today will be his last day serving ATI / Advanced Micro Devices.

The rest of this very informative article can be found here:

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

[xir_]

Dont get me wrong the zen kernel is OK (of course i compile for my cpu, might as well), i've got rid of a lot of stuff and am using BFS (which is really nice), but as far as zen vs the bfs kernel available on launchpad, theres none.

i managed to get the radeon drivers working, they are so much better for watching movies on my laptop. i used to get lagg when starting up a video, now i get a real snappy viewing, open arena is a dream to run as well and cairo-dock finally works with opengl.

two thumbs up

[handy]

i managed to get the radeon drivers working,

xf86-video-radeonhd ?

[handy]

Here's an update on the the list of files that we need to prevent from being upgraded to maintain compatibility between catalyst 9.10, & xorg1.7.

The number of files has come down somewhat from the previous list of approx' 60 files that I linked to in a previous post in this thread.

64bit users can use the upgraded lib32-* packages, (I've tested this), if you have a notebook then you will most likely want to add xf86-input-synaptics.

If you were using Arch you would add the following line in /etc/pacman.conf

IgnorePkg = xf86-video-vesa xorg-server xf86-input-evdev xf86-input-keyboard xf86-input-mouse

With the number diminished from 60 to 5 or 6 files that need to be held back from upgrade, this workaround has certainly become far less of a pain to instigate.

[xir_]

xf86-video-radeonhd ?


According to synaptic i only have the radeon driver installed, but now that u mention it i will give the radeonhd a try.

what is the difference (i normally just skip to the binary blobs with installations for compiz).

Do you know which acceleration method is used by default with the radeon drivers (i'm wondering if theres any tweaks i can do for better performance).


One thing to note is that my power consumption has gone up from ~12 watts to 20 watts. this has cut my battery life by two hours. I assume this is down to ati having much more fine grained control over powersettings.

[handy]

My understanding is that with the open-source drivers usually the xf86-video-ati is the better, though some people do find the xf86-video-radeonhd better, but they are definitely in a minority.

I have been using until very recently the xf86-video-ati package, & the 2D performance is actually miles better than that provided by the catalyst package. The desktop, scrolling, movies, everything is the snappiest it has ever been.

I just went back to catalyst the other day, because I've been checking out games provided by the DJL games manager (kind of like steam for Linux) & needed better 3D for some of the games.

So moving back to catalyst, has really made it quite clear that even though the catalyst drivers have better to vastly superior 3D quality over the open-source drivers, their 2D is crap.

I'll give you a link to a method for getting the most out of the open-source drivers in Arch, you may learn some that you can apply in Ubuntu (I've not bothered with the following method as yet, as with Arch I expect that there may be too much upkeep, due to the rolling release, I could be wrong of course:)):

http://bbs.archlinux.org/viewtopic.php?id=79509

If you do manage to get improved results from your endeavours, please post a how-to in the how-to section for other Ubuntu users, I'm sure that quite a few would be very grateful? :)

[handy]

AMD's UVD2-based XvBA Finally Does Something On Linux

For a year now we have been talking about XvBA, which stands for X-Video Bitstream Acceleration and is designed to implement AMD's Unified Video Decoder 2 (UVD2) engine on Linux systems for improving the video decoding and playback process on desktop systems. AMD has been shipping an XvBA library with their ATI Catalyst Linux driver since last year, but they have yet to release any documentation on the XvBA API or any patches to implement the support within any Linux media players. Heck, AMD has not even officially confirmed XvBA with Phoronix being the lone source of information for the past year. Today though, XvBA has finally become useful under Linux. But it is not what you may be thinking...

http://www.phoronix.com/scan.php?page=ar...aapi&num=1

[handy]

Catalyst 9.11 has been leaked.

It doesn't solve the incompatibility with xorg 1.7 though. :(

http://www.phoronix.com/forums/showthread.php?p=99647

http://news.ati-forum.de/index.php/news/34-amdati-grafikkarten/840-download-catalyst-911-fuer-linux-exklusiv

[handy]

kernel .32 is out.

ViOLO has compiled it without KMS & tested it with catalyst. It is of course incompatible.

So those of us who are using catalyst & blocking the upgrade of 5 (or 6 for notebook) packages have to add kernel26 to the list not to be upgraded as well.

[Pasdar]

I just reinstalled kubuntu on my laptop and i'm willing to give the ati open-source drivers a try. Will it work with ATI 4570?

What I would expect of it are that my desktop environment runs fast, that I can enable desktop composition (kwin), and I want to be able to watch my movies/series (divx/dvd/streaming/whatever). Can it deliver the mentioned things?

If yes, I'd like to know where I could download the drivers and also get the latest updates from.

[u.b.u.n.t.u]

I wish the 9.12 drivers would come of age!

Hopefully this month I would think.

[Pasdar]

Stupid AMD has so many people, yet they're unwilling to make propper drivers for linux. Though I'm happy they at least release drivers each month. It would be great if they just supported every kernel update/xorg/etc... ahh... the dreams of an ati user... lol

[handy]

@Pasdar: Have a look at some of the links at the bottom of the first post in this thread.

One of them goes into quite some detail (on the Arch forum) for getting the best 3D out of the open-source drivers.

You will be able to find out whether your GPU is well supported, & you'll also find out which open-source package route you need to follow.

As mentioned often, previously, the 2D is superb for most ATi GPUs, via the open-source drivers, glitch free, 3D, is what we are waiting for. :) AMD are helping by offering technical help where they legally can.

[sdowney717]

i have an x1300 sitting around and cant use it. i need svideo out and they dont offer it on r500 chipset

[rajeev1204]

What exactly is the point of open drivers for 3d ? for example, games use proprietary technologies and the open source driver is incapable of running them.

For example, in id's games, there is a module called s3tc, tc is for texture compression and s3 has the patents for it,so it will never make it to the open source driver.And so, will never run a game with that .

Give me the proprietary drivers anyday.

@handy,which 2d applications are you talking about really? What is this 2D?

Iam sorry to say handy,but many have not probably understood why just opening a driver wont solve anything.

If by 3d you mean compiz, then we dont buy expensive graphics cards with shader model 4 for just that,do we?

good day.Sorry for the harsh post.Just opened my eyes when i reached point of no return with the open source driver.And on top of it,AMD dropped support for older cards so no proprietary drivers for me either.That means no gaming either.

Due to the reasons mentioned above, the drivers can never be fully functional.Will never come of age unless every single app using it and many other things we probably miss out are also open .COuld be hardware,software running on them and other legalese.

rajeev

[forrestcupp]

For example, in id's games, there is a module called s3tc, tc is for texture compression and s3 has the patents for it,so it will never make it to the open source driver.And so, will never run a game with that .

Anything can be reverse engineered with time. The Wine team has reverse engineered most of the features in DirectX, and I doubt if s3tc is more complicated than that.

[Hyporeal]

What exactly is the point of open drivers for 3d ? for example, games use proprietary technologies and the open source driver is incapable of running them.

For example, in id's games, there is a module called s3tc, tc is for texture compression and s3 has the patents for it,so it will never make it to the open source driver.And so, will never run a game with that .

Why can't open source drivers use patented techniques? You can already download the proprietary drivers for free, so there's no issue with fees. The patent publicly describes the technique, so there's no issue with secrecy. Why would S3 care whether ATI's drivers are open source or not, as long as the licensing fees get paid as usual?

[u.b.u.n.t.u]

I think ATI and Nvidia should open source their drivers and work closely with the linux community.

I buy their hardware, and a customer ought to be able to expect a fully working product on linux.

[jrusso2]

Any video card should be able to do excellent 2d. Its 3d performance that counts. I have ten year old cards here that do great in 2d.

[handy]

What exactly is the point of open drivers for 3d ? for example, games use proprietary technologies and the open source driver is incapable of running them.

As mentioned above by forrestcupp, reverse engineering is alive & well in the open-source community. Wireless users may be most aware of this.

The point of having open-source drivers, is that the code is open for all. It can be kept up to date with the kernel, mesa (which is where the GPU open-source is intended to reside & is in the process of being developed now) & the xorg-server.

Those who have been putting up with the terrible ATi driver support over the last years will be free of that burden.



Give me the proprietary drivers anyday.

That is your choice.

Though it is possible in the future that the only drivers provided by AMD for the ATi GPUs used by the distros will only be for their newest GPUs, due to the competition between AMD & nVidia.

I've not read that anywhere, it just seems like good business sense to me.

Time will tell.



@handy,which 2d applications are you talking about really? What is this 2D?

When I run the open-source drivers on my 24" iMac running an HD2600Pro GPU, the refresh speed of everything (opening, closing app's resizing & moving windows, scrolling in intensive graphic screens, the Firefox refresh speed - scrolling - on any site with many tabs open) is near instantaneous. Watching any form of video is perfect, as there is not the slightest hint of lag ever.

Using catalyst there is lag, in all of the above.



Iam sorry to say handy,but many have not probably understood why just opening a driver wont solve anything.

Actually, I think you have the bull by the horns. You will find as time goes by, that the open-source GPU drivers that are currently being worked on will do all & more than the proprietary ones. I know you won't take my word for it, though the proof will be in the pudding as 2010 goes by there will be some serious changes occur re. the support provided by the open-source drivers for many GPUs.

There are people already using the ATi open-source drivers for 3D games, though not the most demanding of them. I have used the open-source drivers & run some 3D, without any graphic aberrations, but with too much lag.



If by 3d you mean compiz, then we dont buy expensive graphics cards with shader model 4 for just that,do we?

I never use compiz or the like, I don't even have icons on my desktop, or a screen background. I personally consider that beyond making things as easy on your eyes as possible, anything else is a waste of resources. I know, there is no accounting for taste. :)



good day.Sorry for the harsh post.Just opened my eyes when i reached point of no return with the open source driver.And on top of it,AMD dropped support for older cards so no proprietary drivers for me either.That means no gaming either.

It is a drag when support disappears. I can't say for sure, hopefully there will be useful open-source support for your GPU?
Everything does reach an age where it is no longer supported though, hopefully your GPU is not there yet.



Due to the reasons mentioned above, the drivers can never be fully functional.Will never come of age unless every single app using it and many other things we probably miss out are also open .COuld be hardware,software running on them and other legalese.

rajeev

I think you will find that you are wrong on this. As I said before, keep an eye on the progress of the open-source ATi drivers over the coming year or so.

All the best.

[handy]

What exactly is the point of open drivers for 3d ? for example, games use proprietary technologies and the open source driver is incapable of running them.

For example, in id's games, there is a module called s3tc, tc is for texture compression and s3 has the patents for it,so it will never make it to the open source driver.And so, will never run a game with that .

I just happened to be poking about on the Neverwinter Nights Linux forum & read about a little Linux tool for handling S3TC:

Quote: Posted 08/11/09 14:02 (GMT) by CainGG

If it's the S3TC issue, you can install a program called driconf that will let you force S3TC to "on" for practically any video system...it worked for my Intel GM45 and it might work for you too.

There are always more than one way to skin a cat, especially in the FOSS world. ;)

[holastickboy]

I have always seemed to have Nvidia cards on my linux pc's because the software just seemed to run much better. I managed to get a video card upgrade the other day to a Ati Radeon 3650 and was appalled about how primitive the ati drivers were, and what a big fuss it was to get my dual screens working properly (and not stretch games across both screens). I hadn't used an ATI card on linux for years, and I thought that in my hiatus that things would have improved, which they have to a small degree. I commend the people working had to make the open source drivers better!

[rajeev1204]

I just happened to be poking about on the Neverwinter Nights Linux forum & read about a little Linux tool for handling S3TC:

Quote: Posted 08/11/09 14:02 (GMT) by CainGG

If it's the S3TC issue, you can install a program called driconf that will let you force S3TC to "on" for practically any video system...it worked for my Intel GM45 and it might work for you too.

There are always more than one way to skin a cat, especially in the FOSS world. ;)

This is good information thanks.And thanks for the replies to my long post,i appreciate that you took it positively.I still dont know how to multiquote so i didnt reply to that post of yours.

BTW,I finally got a brand new AMD RADEON 4850 :D.And the proprietary drivers are working great.

But i have read that Radeon HD open drivers are catching up soon so thats good news.But it still wont solve the s3tc or other issues without a little R and D.

Anyways,lets hope for the best.

T.C.
rajeev

[Nerd King]

So I've been having nightmares with 2.6.31 and tried 2.6.30 with the same problem, my wi-fi kept locking the system. 2.6.32 fixes that, but even better, it gives me open source ATI drivers and lovely 3D with no proprietary driver. Absolutely superb it is too, Compiz is flying around nicely, will test some games later but it feels very snappy. Btw it's not compatible with the proprietary ATI drivers which is why I tried the open ones. I'm glad I did now!

I've run the usual crash conditions and it coped fine so it looks good.

Procedure:
1. System -> Hardware Drivers -> Deactivate any ATI drivers and restart
2. Go to http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.32/)
3. Download and execute the following (in this order, switch to 64 if need be)
- linux-headers...all.deb
- linux-headers..generic..i386.deb
- linux-image....i386.deb
4. Restart
5. Add the xorg-edgers PPA (https://launchpad.net/~xorg-edgers/+archive/ppa (https://launchpad.net/%7Exorg-edgers/+archive/ppa)), update, upgrade.
6. Reboot.
7. Profit.

[SunnyRabbiera]

Yeh I think this might be what most ATI users have been waiting for.
Its about time we got some progress from ATI

[Nerd King]

An hour in, still no sign of a freeze or crash so people on Atheros Wi-Fi getting the lock-up will find 2.6.32 very useful. Rock solid performance on SuperTuxKart, an occasional black band flashing in and out caused by Gnome-Do Docky (resolved by a quick killall 'gnome-do') so it looks like it'll handle 3D games as well.

BTW my hardware is ASUS F81 laptop running a ATI HD4570 card.

[Pasdar]

Could you run what you get from glxgears, I have the same videocard with proprietary drivers installed atm.

[Nerd King]

ryan@ryan-laptop:~$ glxgears
IRQ's not enabled, falling back to busy waits: 2 0
8460 frames in 5.0 seconds = 1691.881 FPS
9108 frames in 5.0 seconds = 1821.436 FPS
9585 frames in 5.0 seconds = 1916.847 FPS
9597 frames in 5.0 seconds = 1919.266 FPS
8473 frames in 5.0 seconds = 1694.577 FPS
9387 frames in 5.0 seconds = 1877.321 FPS
7942 frames in 5.0 seconds = 1588.364 FPS
9333 frames in 5.0 seconds = 1866.436 FPS


Not sure how accurate a measure that is. Compiz was running at the time.

[doorknob60]

I'm eagerly awaiting 2.6.32 to hit [core] in Arch, so I can try it. I don't want to use [testing], that never turns out well :P I'm in no huge hurry though since Catalyst is working well for me right now. I've heard great things about the 3D support in 2.6.32 though :)

[Nerd King]

I'm eagerly awaiting 2.6.32 to hit [core] in Arch, so I can try it. I don't want to use [testing], that never turns out well :P I'm in no huge hurry though since Catalyst is working well for me right now. I've heard great things about the 3D support in 2.6.32 though :)
I thought Arch was supposed to be cutting-edge ;) Only mucking about. Seriously though, you'll be very impressed with the new 3D support, and the obvious advantage of not having to wait for ATI to put out compatible versions of catalyst for every new version of X and the Kernel. Should make Archer's lives much easier.

[Nerd King]

I thought Arch was supposed to be cutting-edge ;) Only mucking about. Seriously though, you'll be very impressed with the new 3D support, and the obvious advantage of not having to wait for ATI to put out compatible versions of catalyst for every new version of X and the Kernel. Should make Archer's lives much easier.
Btw will test some games with Wine when I get home, to see how it copes.

[Pasdar]

Weird but I dont have glxgears, maybe its part of the ubuntu reps and not kubuntu... is there a place to download it?

[Pasdar]

Found it, its in mesa-utils.

:~$ glxgears
9848 frames in 5.0 seconds
10246 frames in 5.0 seconds
10213 frames in 5.0 seconds
10196 frames in 5.0 seconds
9816 frames in 5.0 seconds
10209 frames in 5.0 seconds
10074 frames in 5.0 seconds

The difference could be due to other factors. All in all the free drivers seem like a great alternative.

[Pasdar]

What does
glxinfo | grep version
give you, mine:

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL version string: 2.1.9016
OpenGL shading language version string: 1.40

[AllRadioisDead]

Will this work for my HD 4850?

[Nerd King]

IRQ's not enabled, falling back to busy waits: 2 0
server glx version string: 1.2
client glx version string: 1.4
GLX version: 1.2
OpenGL version string: 1.5 Mesa 7.7-rc1


Can't vouch for the 4850 specifically but mine's a pretty close model so it's worth a try.

[mmix]

yes, getting interesting.

[Nerd King]

Tried Football Manager in wine but no luck. However, at this rate I'm sure it wont be long.

[antenna]

I would be interested in knowing if Quake Live works in full screen ;)

[tom66]

What card you using? Does anyone know if my Mobility Radeon HD 3450 will work?

[Chame_Wizard]

Going to be good.:P

[handy]

... I still dont know how to multiquote so i didnt reply to that post of yours.

There are some more variations than what I'll post here now, but this will get you going with multi-quote. You have to close a quoted section with the following command "[/quote]" (without the inverted commas) this is what I did to break your text above so I could type this.

After which then I copy the persons quote=name line as follows "[QUOTE=rajeev1204;8445398]", (once again without the inverted commas) & place it at the start of the next part of the other person's (in this case your) text that you want to display, as follows:



BTW,I finally got a brand new AMD RADEON 4850 :D.And the proprietary drivers are working great.

That is great news. :)



But i have read that Radeon HD open drivers are catching up soon so thats good news.But it still wont solve the s3tc or other issues without a little R and D.

Anyways,lets hope for the best.

T.C.
rajeev

I do. :)


Just a note on the keyboard shortcuts for copying, cutting & pasting, which is particularly useful when you want to reuse a persons quote=name (as mentioned earlier in this post) to break up their post so as to add your replies.

Drag the mouse cursor with the left mouse button depressed, to highlight the desired text, then manipulate it with the following keyboard shortcuts:

copy = "Ctrl" & "c"
paste = "Ctrl" & "v"
cut = "Ctrl" & "x"

you can of course paste what you have cut. You probably know that stuff, but it is not hard for me to type it & it just might be useful.

All the best. :)

[Nerd King]

Far as I know HD3000 and 4000 series is good but the only way is to try it and see. Maybe install on a flash drive (clean) and run from there, see how it goes. If it plays nice, then try it on your main box. As I say, it's bumped stability right up for me, 32 is a fantastic kernel, and could be a real big deal for linux, the time when all 3 graphics cards have quality driver support.

[Nerd King]

Probably should have posted on this thread but I was excited.. anyway http://ubuntuforums.org/showthread.php?p=8450093#post8450093 for some info on getting 3D under open-source drivers. Tested in Karmic on a ATI HD4570 and I think it'll probably work on anything HD3000/4000 series. Good luck chaps..


Procedure:
1. System -> Hardware Drivers -> Deactivate any ATI drivers and restart
2. Go to http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.32/)
3. Download and execute the following (in this order, switch to 64 if need be)
- linux-headers...all.deb
- linux-headers..generic..i386.deb
- linux-image....i386.deb
4. Restart
5. Add the xorg-edgers PPA (https://launchpad.net/~xorg-edgers/+archive/ppa (https://launchpad.net/%7Exorg-edgers/+archive/ppa)), update, upgrade.
6. Reboot.
7. Profit.

[AllRadioisDead]

Far as I know HD3000 and 4000 series is good but the only way is to try it and see. Maybe install on a flash drive (clean) and run from there, see how it goes. If it plays nice, then try it on your main box. As I say, it's bumped stability right up for me, 32 is a fantastic kernel, and could be a real big deal for linux, the time when all 3 graphics cards have quality driver support.
Maybe I'll get around to testing it on my 4850 sometime soon. Looks promising.

[Ylon]

Unluckly, this don't fix the situation for some legacy ATI.. my [Radeon Mobility 7500] still crashes Googleeart and so, go on (blender&co).

I had to force a revert back to x-retro ppa repository.


Now I've a problem, each time I try a apt-get upgrade it ask me to update all the xorg from ~xorg-edgers repository.
How can I avoid that?

deb http://ppa.launchpad.net/ubuntu-x-swat/x-retro/ubuntu karmic main
#deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu karmic main

These are the ppa lines in my sources.list.

[diaa]

I'd appreciate any info about gaming performance with ATI HD 3xxx, I have ATI HD 3300(not high-end I know) and I'm not satisfied with the performance of ATI's proprietary Linux drivers(FPS is significantly better on Windows using the same card)

[Chame_Wizard]

So I've been having nightmares with 2.6.31 and tried 2.6.30 with the same problem, my wi-fi kept locking the system. 2.6.32 fixes that, but even better, it gives me open source ATI drivers and lovely 3D with no proprietary driver. Absolutely superb it is too, Compiz is flying around nicely, will test some games later but it feels very snappy. Btw it's not compatible with the proprietary ATI drivers which is why I tried the open ones. I'm glad I did now!

I've run the usual crash conditions and it coped fine so it looks good.

Procedure:
1. System -> Hardware Drivers -> Deactivate any ATI drivers and restart
2. Go to http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.32/)
3. Download and execute the following (in this order, switch to 64 if need be)
- linux-headers...all.deb
- linux-headers..generic..i386.deb
- linux-image....i386.deb
4. Restart
5. Add the xorg-edgers PPA (https://launchpad.net/~xorg-edgers/+archive/ppa (https://launchpad.net/%7Exorg-edgers/+archive/ppa)), update, upgrade.
6. Reboot.
7. Profit.

Thanks by the way

[Xbehave]

I need more crack on my cornflakes^H^H^H xorg, is there a way to get mpx on karmic?

BTW is the 2.6.32 important? I'm still struggling with an audio problem (custom kernel, probably my fault), but i get ~100/200FPS on 2.6.31 on an old internal card (RS482 [Radeon Xpress 200M])

[PaulInBHC]

I'm typing this in Windows. I installed and rebooted. I get a boot screen, a very small text error at the bottom, then a black screen.

Guess I'll have to reinstall Ubuntu.

[toupeiro]

I'm sorry, but I think KSM was a MUCH more important addition to this kernel than anything else.


my .02

[Xbehave]

I'm sorry, but I think KSM was a MUCH more important addition to this kernel than anything else.


my .02
KSM has got a lot of hype but the performance difference between 2.6.32 and 2.6.31 for graphics is minimal. KSM is only being used to stopping flickering when you switch to/from xorg (with the downside being an xorg lockup can now lock up your kernel). It's the work being done on the xorg-radeon drivers that makes all the difference. Don't get me wrong ksm is a nice feature but IMHO it's getting way too much hype.

[handy]

Probably should have posted on this thread but I was excited.. anyway http://ubuntuforums.org/showthread.php?p=8450093#post8450093 for some info on getting 3D under open-source drivers. Tested in Karmic on a ATI HD4570 and I think it'll probably work on anything HD3000/4000 series. Good luck chaps..

This is where you should have posted, it is what this thread is all about! :)

The incorporation of the GPU suport into the kernel & mesa started happening in the .31 kernel, & will continue in coming kernels.

Most of us don't know just what results to expect for our ATi GPU until the kernel is released & people like you report on the experience.

Great news. :D

I'll investigate at to whether the 2000 series (which I'm using) has support.

[waynefoutz]

What about us obsolete folk? :(

I'm sitting on an x1400, and they've ditched me, rejected me for the younger model. I feel like an old worn out hoo... Won't go there. Anyways, I want proprietary support! Or atleast open the source code of the drivers so we can get some decent ones.

I'm in the same boat. My laptop has a ATI radeon x1270, RS695 chip. The last version of Catalyst that works is 9.3. Basically, I can't upgrade past Intrepid, or I lose 3d. Anyone have a clue if this new kernel update will let me upgrade to Karmic and have 3d?


Think I found the answer!

this link:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=771fe6b912fca54f03e8a72eb63058b 582775362

scroll down to the bottom and it lists the affected chipsets...Mine is on the list!

[handy]

I've added a couple of links to the others at the bottom of OP in this thread.

Thanks for them. :)

[toupeiro]

KSM has got a lot of hype but the performance difference between 2.6.32 and 2.6.31 for graphics is minimal. KSM is only being used to stopping flickering when you switch to/from xorg (with the downside being an xorg lockup can now lock up your kernel). It's the work being done on the xorg-radeon drivers that makes all the difference. Don't get me wrong ksm is a nice feature but IMHO it's getting way too much hype.

uuhh, KSM is page memory deduplication, which has the ability to exponentially extend the life of similar data types loaded into RAM, which affects EVERYTHING, not just ATi owners.. Thus, it deserves all the hype. For example, Imagine getting 12GB worth of traditional application space into RAM in a 3GB footprint? Do you virtualize at all? Guess what, your memory footprint of identical pages amongst your VM's is now shared. You can recover huge percentages of available memory for other tasks. Overall, IMO, this is vastly more important to the future of Linux based OSes than Open ATI drivers, which I will admit is very important for ATi users.

[handy]

2010, really does look to be shaping up as quite a year for the Linux kernel... =D>

[Xbehave]

uuhh, KSM is page memory deduplication, which has the ability to exponentially extend the life of similar data types loaded into RAM, which affects EVERYTHING, not just ATi owners.. Thus, it deserves all the hype. For example, Imagine getting 12GB worth of traditional application space into RAM in a 3GB footprint? Do you virtualize at all? Guess what, your memory footprint of identical pages amongst your VM's is now shared. You can recover huge percentages of available memory for other tasks. Overall, IMO, this is vastly more important to the future of Linux based OSes than Open ATI drivers, which I will admit is very important for ATi users.
KSM != KMS my bad i miss read your post as the thread was about ATI drivers.

Also AFAIK KSM only affects VMs (possibly only those that make used of KSM), so unless you do lots of virtualisation you wont notice it. I mean i think KSM is great but your average desktop user will not notice it.

[doorknob60]

I just upgraded to [testing] and installed all the new stuff. SOme stuff work, some stuff doesn't. I can't tell whether it's using hardware acceleration or software. World of Goo works normally, but Wine is very very slow. Glxgears works fine in 64 bit and 32 bit. It could be my 32 bit chroot isn't set up right byut my 64 bit is. I installed the same stuff in the chroot as in my 64 bit Arch though. I'll reboot and see if that fixes it :)

EDIT: After restarting and running glxinfo again, it became clear that my stuff is working correctly on 64 bit, but not in my 32 bit chroot (which I need...). With catalyst all I had to do was install the catalyst package in the chroot (the exact same way I installed it in my 64 bit main system), but do I have to do anything special with this?

EDIT2: Oh wait, I forgot to install libdrm-git, good, it should work now :)

EDIT3: Except that it doesn't fix it :/

EDIT4: Fixed, works nice, I'll stick with it unless something gives me problems. So far so good.

[toupeiro]

KSM != KMS my bad i miss read your post as the thread was about ATI drivers.

Also AFAIK KSM only affects VMs (possibly only those that make used of KSM), so unless you do lots of virtualisation you wont notice it. I mean i think KSM is great but your average desktop user will not notice it.

Well, I think what you are seeing is a product of writers using as many top buzzwords as possible. :) Virtualization has been a buzz topic for the last two years, and in storage, deduplication has been a buzzword for quite some time as well. So, when you talk about RAM dedup, one of the first big wins for the technology is DEFINITELY virtualization, but to say that it will only effect virtualization is not true based on what I've read about the technicalities about that technology.

The KSM code scans through memory to find pairs of pages holding identical data; when such pairs are found, they are merged into a single page mapped into both locations. The pages are marked copy-on-write, so the kernel will automatically separate them again should one process modify its data. There is nothing about this that is specific to VM's, but as you can imagine, it would be very highly effective in VM environments, and those environments would most likely be the first to utilize the functionality. Databases. web-services, and intensive work such as Audio and Video production and rendering, Content Streaming, as well as certain types of graphics work will also benefit. I could also see this helping backend gaming services which are run on linux. e.g., World of Warcrafts realm servers.

EDIT: And the thread was about the .32 kernel as well, which was merged with a thread that was strictly ATI drivers, which honestly was a bad merge by whichever mod merged them... :)

[Nerd King]

I'm typing this in Windows. I installed and rebooted. I get a boot screen, a very small text error at the bottom, then a black screen.

Guess I'll have to reinstall Ubuntu.
If you choose an older kernel from grub at bootup you can get back in and undo what you did.

[Nerd King]

Well, I think what you are seeing is a product of writers using as many top buzzwords as possible. :) Virtualization has been a buzz topic for the last two years, and in storage, deduplication has been a buzzword for quite some time as well. So, when you talk about RAM dedup, one of the first big wins for the technology is DEFINITELY virtualization, but to say that it will only effect virtualization is not true based on what I've read about the technicalities about that technology.

The KSM code scans through memory to find pairs of pages holding identical data; when such pairs are found, they are merged into a single page mapped into both locations. The pages are marked copy-on-write, so the kernel will automatically separate them again should one process modify its data. There is nothing about this that is specific to VM's, but as you can imagine, it would be very highly effective in VM environments, and those environments would most likely be the first to utilize the functionality. Databases. web-services, and intensive work such as Audio and Video production and rendering, Content Streaming, as well as certain types of graphics work will also benefit. I could also see this helping backend gaming services which are run on linux. e.g., World of Warcrafts realm servers.

EDIT: And the thread was about the .32 kernel as well, which was merged with a thread that was strictly ATI drivers, which honestly was a bad merge by whichever mod merged them... :)
Actually a good merge as the .32 kernel post (mine) was mostly about how good the support for ATI opensource 3d was. I then realised I should have posted here, posted the procedure, and linked to the thread for anyone who wanted, a mod subsequently did what I should have done in the first place. Mod did good.

[PaulInBHC]

Thanks for the tip. I still have 9.10 installed. I thought about it later and should have tried the recovery mode as well or the LiveCD.

[toupeiro]

Actually a good merge as the .32 kernel post (mine) was mostly about how good the support for ATI opensource 3d was. I then realised I should have posted here, posted the procedure, and linked to the thread for anyone who wanted, a mod subsequently did what I should have done in the first place. Mod did good.

Fair enough. Your opening title to your thread was a bit misleading then. If you didn't care about the other features of the .32 kernel, perhaps it shouldn't have been the first part of your subject line, which would have kept me from talking more about ... the .32 kernel. Please continue your ATi conversations, I'll find another thread about the .32 kernel, and wont post them here anymore.

[Nerd King]

Fair enough. Your opening title to your thread was a bit misleading then. If you didn't care about the other features of the .32 kernel, perhaps it shouldn't have been the first part of your subject line, which would have kept me from talking more about ... the .32 kernel. Please continue your ATi conversations, I'll find another thread about the .32 kernel, and wont post them here anymore.
Not misleading as such. .32 kernel + open drivers produce win. It came with the 32 kernel and the xorg updates to match it, and without the 32 kernel you don't get the ATI coolness. For me it also fixed my wi-fi problem, so it was a story of a good upgrade as such, that turned into a "Wow this open ATI driver rocks" as that was my only way to get the kernel working and it turned out to be a pleasant surprise. Hope that makes sense.

[PaulInBHC]

I did recovery mode and safe-upgrade, all is well now. I'm thinking there may have been another problem not related to this ATI driver.

[handy]

From what I've been reading, the development of the ATi open-source drivers really is moving along much faster than I expected.

People are getting great 2D, very usable (though still slower than catalyst) 3D, using kernel .32, & a combination of .git & testing packages.

Kernel .33 is expected to not only bring increased 3D performance but also the much anticipated & greatly desired by the notebook users in particular, power management.

Just how polished & universal the ATi GPU power management will be in the kernel .33 release is of course something we won't really know until it arrives?

Here is a link on the power management topic:

http://www.phoronix.com/scan.php?page=news_item&px=NzcyNw

[handy]

Here is great graphic representation of just where the xf86-video-ati open-source xf86-video-ati drivers are currently up to. Very impressive:

http://wiki.x.org/wiki/RadeonFeature

[Nerd King]

From what I've been reading, the development of the ATi open-source drivers really is moving along much faster than I expected.

People are getting great 2D, very usable (though still slower than catalyst) 3D, using kernel .32, & a combination of .git & testing packages.

Kernel .33 is expected to not only bring increased 3D performance but also the much anticipated & greatly desired by the notebook users in particular, power management.

Just how polished & universal the ATi GPU power management will be in the kernel .33 release is of course something we won't really know until it arrives?

Here is a link on the power management topic:

http://www.phoronix.com/scan.php?page=news_item&px=NzcyNw
Gotta say that it's holding up brilliantly for me. The 3D is responsive, 2D is fast (World Of Goo is smoother than ever) and it's coping with Linux 3D games just fine. Wine 3D is the next step I guess. Seriously, I'm hugely impressed because I remember when even the proprietary drivers were rubbish.

[handy]

Gotta say that it's holding up brilliantly for me. The 3D is responsive, 2D is fast (World Of Goo is smoother than ever) and it's coping with Linux 3D games just fine. Wine 3D is the next step I guess. Seriously, I'm hugely impressed because I remember when even the proprietary drivers were rubbish.

All of a sudden, there is this sudden building up of excitement within the Linux (& any system that uses X :D) communities with regard to the actual realisation that the ATi open-source drivers, are actually starting to cross the line.

After so long, & so much work, we ARE starting to get the results of this combination of mammoth projects.

It really is finally actually coming together. Many months sooner than I expected, & I follow this stuff daily! (Hmm, shows you how much I know! ;))

I think that kernel .33 has an extremely good chance of allowing most Linux, ATi GPU users to kiss the catalyst drivers goodbye (hopefully) forever.

Which is an awesome achievement. Especially for those of us who have spent years trying to get some sense out of fglrx/catalyst, & having spent so much time being danced about backwards & forwards & then backwards again during that time.

I'm not bitching about AMD, I'm really grateful to them, they have contributed hugely with technical information that has been (I think) absolutely essential to the open-source support actually being realised for the ATi GPUs.

Fantastic!!! :KS

[Nerd King]

Some further info, not sure if this relates to the newer kernel, newer x or the driver, but I dual-screened the open driver today (my laptop+projector) and it was beautifully seamless. Monitors arranged side-by-side, stuff moving accross the two monitors perfectly. It was an absolute piece of cake and worked wonderfully. Whoever's responsible, thank you, I never got the bloody thing working on Catalyst without half-killing my laptop!

[LinuxFanBoi]

I'll jump ship when things get where they need to be for ATI drivers to provide all the power the HW is capable of...

By then it may be time to upgrade my Nvidia cards.

By then your GPU will be able to handle all the processing requirements of your PC.

[Xbehave]

Some further info, not sure if this relates to the newer kernel, newer x or the driver, but I dual-screened the open driver today (my laptop+projector) and it was beautifully seamless. Monitors arranged side-by-side, stuff moving accross the two monitors perfectly. It was an absolute piece of cake and worked wonderfully. Whoever's responsible, thank you, I never got the bloody thing working on Catalyst without half-killing my laptop!
It's the radeon guys, since ATI gave them the spec, they have been working their butts off to get everything working, the kernel is acting as an enabler but it's the radeon guys (i think theres only about a dozen of them) that are ones selling the crack. Next up on their crack stand is power-saving, but that needs KMS to support it, so will require 2.6.33 and the latest version of the xorg ati drivers to take advantage of it.

[Pasdar]

ATI 4570
Hmm, I have a ten fold drop in performance.

$ uname -a
Linux iRUNiX 2.6.32-020632-generic #020632 SMP Thu Dec 3 10:58:45 UTC 2009 i686 GNU/Linux

$ glxinfo | grep version
server glx version string: 1.2
client glx version string: 1.4
GLX version: 1.2
OpenGL version string: 2.1 Mesa 7.7-rc2
OpenGL shading language version string: 1.20

$ glxgears
1258 frames in 5.0 seconds = 251.428 FPS
1304 frames in 5.0 seconds = 260.755 FPS
1304 frames in 5.0 seconds = 260.762 FPS
1307 frames in 5.0 seconds = 261.271 FPS
1305 frames in 5.0 seconds = 260.864 FPS

[Xbehave]

check that
sudo cat /sys/module/radeon/parameters/modeset gives 1
And
glxinfo | grep -i render says you are direct rendering.

If it's still slow it's probably a bug with the xorg your using are you on crack?

[Pasdar]

Are you talking to me?


sudo cat /sys/module/radeon/parameters/modeset
I only have radeontools in /sys/module .... so I cant check this


glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer


I also enabled Xrender for desktop composition because openGL would not work.

[handy]

Check out the first post, & then the last few pages of this thread?

http://bbs.archlinux.org/viewtopic.php?id=79509&p=1

As far as I'm concerned it is where it is all happening...

Though there are certainly some other threads here & there that add some spice to the topic. :)

[handy]

Following is a link to some very interesting info' re. kernel .33, & the ATi open-source support in particular:

http://www.phoronix.com/scan.php?page=news_item&px=Nzc4OQ

[Yvan300]

I can now play urban terror with the open source drivers. A feat that could not be accomplished with the ones packaged with jaunty and ibex.

[Patapalo]

Ati Radeon 9600

With 2.6.31

5864 frames in 5.0 seconds
5979 frames in 5.0 seconds
5805 frames in 5.0 seconds
6312 frames in 5.0 seconds
6303 frames in 5.0 seconds
6297 frames in 5.0 seconds
6325 frames in 5.0 seconds
6321 frames in 5.0 seconds
6307 frames in 5.0 seconds
6359 frames in 5.0 seconds
6338 frames in 5.0 seconds
6308 frames in 5.0 seconds
6332 frames in 5.0 seconds
6313 frames in 5.0 seconds
6309 frames in 5.0 seconds
6312 frames in 5.0 seconds
6328 frames in 5.0 seconds
6277 frames in 5.0 seconds

With 2.6.32

3011 frames in 5.0 seconds
3072 frames in 5.0 seconds
3291 frames in 5.0 seconds
3287 frames in 5.0 seconds
3281 frames in 5.0 seconds
3288 frames in 5.0 seconds
3286 frames in 5.0 seconds
3055 frames in 5.0 seconds
2948 frames in 5.0 seconds
2676 frames in 5.0 seconds
2827 frames in 5.0 seconds
2319 frames in 5.0 seconds

what i do wrong?

[handy]

Patapalo, are both of your fps from using the open-source radeon drivers?

From what I have read, the open-source drivers are still slower than the catalyst drivers in 3D.

[Suky]

I just want to update my result.

ATI xpress 1250 + Kernel 2.6.31-16 ~ 1250 frames in 5.0 second

After upgrade to 2.6.32 ~ 1750 frames in 5.0 second

But when i update by added https://launchpad.net/~xorg-edgers/+archive/ppa to my repository and ran upgrade

my result down to 1250 frames in 5.0 second.

Now, I removed https://launchpad.net/~xorg-edgers/+archive/ppa out and came back to 2.6.31 but the result still around 1250 frames.

:(

[Xbehave]

removing a ppa will not downgrade the packages, you need ppa-purge or pinning or manually downgrading (if ppa is gone they will not upgrade)

I think dri2/later drivers/mesa support more calls so even if it gives less FPS on glxgears you should get better performance out of real world apps.

[kreggz]

I removed my ATI card in disgust with the ATI drivers and I will no longer purchase any ATI cards in the future.
:(

[Suky]

removing a ppa will not downgrade the packages, you need ppa-purge or pinning or manually downgrading (if ppa is gone they will not upgrade)

I think dri2/later drivers/mesa support more calls so even if it gives less FPS on glxgears you should get better performance out of real world apps.


Thanks for your suggestion but i don't know how to downgrade!!! :(

[handy]

I removed my ATI card in disgust with the ATI drivers and I will no longer purchase any ATI cards in the future.
:(

That's your choice of course, but your timing is not too good, as the best is yet to come, & it is happening fast... :)

[Xbehave]

Thanks for your suggestion but i don't know how to downgrade!!! :(
The easiest way is to install ppa-purge

Pinning (not 100% sure if this works exactly as i describe, harder than ppa-purge but lets you keep the repo (just not use anything from it by default)
1) Fine the ppa name (i think you need the ppa installed) apt-cache policy, gives a line like

500 http://ppa.launchpad.net karmic/main Packages
release v=9.10,o=LP-PPA-xorg-edgers,a=karmic,n=karmic,l=Ubuntu,c=main
origin ppa.launchpad.net
2) sudo nano /etc/apt/preferences/00pinning (file name can be anything)
add
Package: *
Pin: release o=LP-PPA-xorg-edgers
Pin-Priority: 50 #default is 500, 50 is lower so other packages will install over it


Manual (trickiest but gives you explicit control)
1) Fire up aptitude (its doable with gui tools, but i know aptitude best)
2) Find the package (/ packacagename or / part of package name ,n until you get the right one), and select it (enter) (see image)
3) scroll to the bottom of the box and install the version you want (+ key)
4) press g to review changes as downgrading may have knock on effects ("fixing breakages" is done using e ! , . but a red bar comes up if you need to do that)
5) press g to apply (it may now prompt for your
password, if you ran aptitude as user, which is a good practice)

btw there is a new version out today which may be better

[Nerd King]

Hopefully this info will interest some. It seems that while performance isn't there yet, overall the implementation is cleaner in this driver than the catalyst driver. I say this as until the last 2 or 3 versions gaming + compiz was impossible, and even now some games work in NVIDIA and not ATI. One example of this is Plants Vs Zombies. On NVIDIA it's flawless, on ATI it's just a mess. With the open drivers it runs perfectly. It's slow, but it's perfect. No rendering issues at all, even with compiz enabled. Overall I'm pretty happy with that, and I can assume the current pace of development will see performance catch up soon enough. So the future of Wine gaming looks to be good for ATI users. Enjoy it, these are exciting times.

[Pasdar]

I see it differently, but I hope I'm wrong.

The proprietary drivers just have annoying bugs that will be fixed in time. Most of these bugs in the latest version will even go unnoticed by many. The performance is top notch. Fixing bugs is just a matter of time.

However the open-source drivers perform below standard, but have no noticeable bugs that I could find. Now I haven't checked the source, so I don't know... however I think this means that the source is too much redundancy, and is simply inefficient... that's why its so slow compared to the proprietary drivers. Fixing an inefficiently written program, will require a complete re-check/re-do, to make it better and will take much more time..

Again, I don't know the source code, im just guessing.

[Grenage]

That's your choice of course, but your timing is not too good, as the best is yet to come, & it is happening fast...

ATI fans have been saying that for years, but the drivers are still junk compared to Nvidia.

[handy]

I see it differently, but I hope I'm wrong.

The proprietary drivers just have annoying bugs that will be fixed in time. Most of these bugs in the latest version will even go unnoticed by many. The performance is top notch. Fixing bugs is just a matter of time.

If you use distro that is not supported by AMD such as Arch, which is a distro that uses a rolling release package management system, which provides very new software, you would find that one (as we are currently experiencing) problem with the Catalyst drivers, is that they don't keep up with the Linux system development. i.e. the last two versions of Catalyst are not compatible with the current version of the xorg-server > 1.6.

Also, the 2D performance of the open-source drivers are vastly superior to that provided by Catalyst. With Catalyst the video tears, & screen refresh lags, scrolling windows lags also.



However the open-source drivers perform below standard, but have no noticeable bugs that I could find. Now I haven't checked the source, so I don't know... however I think this means that the source is too much redundancy, and is simply inefficient... that's why its so slow compared to the proprietary drivers. Fixing an inefficiently written program, will require a complete re-check/re-do, to make it better and will take much more time..

Again, I don't know the source code, im just guessing.

The open-source GPU support system is in the process of being completely rewritten;- it is moving into the kernel & mesa.

I think you should hold your judgement & observe the improvements that are coming in the .32 & beyond kernels, actually kernel .33, is looking particularly good for many ATi GPUs, the 3D speed will just keep on getting better... :)




ATI fans have been saying that for years, but the drivers are still junk compared to Nvidia.

If you spend the time & have a read up on what's happening re, the open-source drivers, you may learn a thing or two?

There are some links at the bottom of the first post in this thread, that would be a good place to start.

[Pasdar]

The 3distro support thing is indeed one of the major flaws of the proprietary drivers, it should definitely be on their list to change that. Its just not at the linux drivers are not anywhere near the top of their priority list unfortunately.

I hope the open-source drivers will one day out-do the proprietary drivers in 3D performance, but I am very skeptical. Its one thing to write drivers to something work, its another to actually outdo the company's own drivers in performance.

[Grenage]

If you spend the time & have a read up on what's happening re, the open-source drivers, you may learn a thing or two?

I've been trying out the proprietary and open drivers as and when new versions come out. Each and every time (across multiple cards), the system has either become unstable or at best given poor performance.

Compared to the Nvidia offerings, there is no contest at the moment. I'd love more competition and choice, but it looks like it's going to be a very long time until ATI get their *** in gear (if they ever do).

[Xbehave]

1) ATI only released the specs for their stuff about a year ago so, it's not years people have been claiming this, but a year.

2) The radeon drivers are in much better shape than the noveu drivers (this is a thread about the open drivers), but if you care more about openness or run a cutting edge setup closed drivers often arn't an option (I switched to radeon because full screen 64_bit flash was tearing)

3)It's not about ATI, the development is mostly done by the opensource community (I think it's something like 2 hobyists, 2 red hat, 2 novell and 2 ATI/AMD, guys).

Regarding perfomance v bugs, needed a ground up rewrite to improve performance is the exception not the rule. Generally you see rewrites only when the project has significantly outgrown itself and become a bit of a mess. As examples of non-rewrites, Firefox has significantly improved since 2.0, kde4 is a lot faster in 4.4 than 4.0, webkit(WebCore) has never had a rewritten since khtml, now things like BTRFS (which at it's core is a rewritten reiserFS) or webkit(JavaScriptCore) do happen but in every case i can think of it's due to the project outgrowing itself. Perhaps I'm biased as I'm mainly interested in python but I'm a fan of getting "everything" working, then optimizing not the other way around.

[aspiredfang]

I'm using the proprietary drivers and have never had a single problem to be honest, maybe it's the specific cards people use which cross the line in terms of reliability I don't know.

Simply slating the development work that has gone in to them is not "cool" though. Imagine how many varieties of Linux there actually are and the different set-ups one package has to work with. I consider it pretty impressive they do work as they do considering how complex GPUs are these days!

On the flip side where people talk about how great the Nvidia ones are, on a media center set up I have, there have been many problems, installation just being one of them. So, what I'm trying to say is chill out :P

Rome wasn't built in a day and we should have some thanks for the open source folks, AMD and Nvidia. Until I come across a problem with the proprietary drivers or read that the open source ones have become mature enough to use across both 2D and 3D (I am no driver dev) this is a stance I will stick to. I can understand them not wanting to give away their "secrets" to the competitor in such a competitive market.

[Grenage]

Don't get me wrong; I appreciate the FOSS driver project and the work that's gone into it. I also want the ATI drivers to be a good option, that's why I keep coming back to try new releases.

It's just my personal opinion that after trying a handful of cards with many driver releases, the performance and stability are terribly lacking compared to Nvidia.

[Kazade]

Now I haven't checked the source, so I don't know... however I think this means that the source is too much redundancy, and is simply inefficient... that's why its so slow compared to the proprietary drivers. Fixing an inefficiently written program, will require a complete re-check/re-do, to make it better and will take much more time..

Again, I don't know the source code, im just guessing.

Nope, it's not the quality of the source that is the problem. Graphics cards are extraordinarily complex, there are many different ways of doing the "same" thing, but some are more efficient than others, but the more efficient stuff that pushes the hardware to it's full potential, tends to be more difficult to do. So performance is only really an issue until the drivers are feature complete. It's the traditional "make it work, then make it fast".

As a simple example, you can render an a 3D model by using "immediate mode" and sending the vertices one at a time (which is fundamentally quite simple), which would render perfectly, it would just be slow as hell. Then you can use "vertex arrays" (store the data in RAM) to speed that up, but "vertex buffer objects" (store the data in VRAM) are even faster. Each of these things need to be implemented, and at the low level, each is more complicated and takes longer to develop than the last. Give it time, it'll get there.

[sdowney717]

http://wiki.x.org/wiki/radeonTV?highlight=%28tv%29|%28out%29

how is the performance of tv out for R500 cards?

[handy]

The 3distro support thing is indeed one of the major flaws of the proprietary drivers, it should definitely be on their list to change that. Its just not at the linux drivers are not anywhere near the top of their priority list unfortunately.

I hope the open-source drivers will one day out-do the proprietary drivers in 3D performance, but I am very skeptical. Its one thing to write drivers to something work, its another to actually outdo the company's own drivers in performance.

AMD are giving the open-source dev team all of the support they legally can. There are some problems due to the GNU license that make it difficult from time to time.

The open-source drivers will be better than the closed ones not only as they already are in 2D, but quite soon in 3D as well.

There are momentous changes in this area well under way. Kernel .32 is already a milestone. There are people getting great results in the R600 & R700 GPU trees now, using combinations of this kernel, & packages in testing & .git.

We are right on the edge of these changes coming into mainstream. :D

[handy]

I've been trying out the proprietary and open drivers as and when new versions come out. Each and every time (across multiple cards), the system has either become unstable or at best given poor performance.

Compared to the Nvidia offerings, there is no contest at the moment. I'd love more competition and choice, but it looks like it's going to be a very long time until ATI get their *** in gear (if they ever do).

You obviously still haven't caught on to what is happening with regard to the enormous amount of change that is currently in progress. The results of which are only really just starting to become worthwhile re. 3D & some of the ATi GPU trees, & again only to people who are prepared to be using packages that are still in development or testing.

As I've previously stated, these changes are on the verge of hitting mainstream, starting with the kernel .32, & dramatically improving in .33, & on. Power management is already available in a limited form via a patch, & will apparently be out in .33 as well.

It's ok not to like the ATi GPUs from your past experience. I own both ATi & nVidia, & having always been an nVidia proponent, it is only inside of the last 4 or 5 months, since I became aware of what is happening with AMD/ATi GPUs & open-source that I realised that ATi had a very different open-source future being created.

It's all good. ;)

[Xbehave]

AMD are giving the open-source dev team all of the support they legally can. There are some problems due to the GNU license that make it difficult from time to time.
Xorg is under the MIT/X11 license (a BSD like license), the problems are simply to do with intellectual property and the fact that ATI don't own all the IP to make their cards but license a lot of it from other companies (something like the Internal+Discrete graphics card in laptops is licensed between at least intel,amd and nvidia, so amd can't release any details without permission from intel and nvidia). Associated with this problem is the fact that AMD aren't actually sure on what they own or what documentation is relevant (because when all they released where binary drivers it didn't matter)

[handy]

Xorg is under the MIT/X11 license (a BSD like license), the problems are simply to do with intellectual property and the fact that ATI don't own all the IP to make their cards but license a lot of it from other companies (something like the Internal+Discrete graphics card in laptops is licensed between at least intel,amd and nvidia, so amd can't release any details without permission from intel and nvidia). Associated with this problem is the fact that AMD aren't actually sure on what they own or what documentation is relevant (because when all they released where binary drivers it didn't matter)

Yep, that's the story I read too.

[bluelamp999]

Hi Handy

Firstly, thanks for your continued posts on this topic - it's heartening to see the advances being made.

I'm saddled with a Mobility Radeon X300 on my Dell laptop and would lurve to finally have some hardware 3D goodness...

Is it best to wait for for .32/.33 kernels or is there some way to jump the gun and get the enhanced GPU functionality now?

Either way, thanks again...

[Xbehave]

Hi Handy

Firstly, thanks for your continued posts on this topic - it's heartening to see the advances being made.

I'm saddled with a Mobility Radeon X300 on my Dell laptop and would lurve to finally have some hardware 3D goodness...

Is it best to wait for for .32/.33 kernels or is there some way to jump the gun and get the enhanced GPU functionality now?

Either way, thanks again...
You can jump the gun, but your system will no longer be supported so you may run into bugs. Also with .32+latest xorg, things are better but 3d is still not great.

add one of the following to /etc/apt/sources.lst
deb http://ppa.launchpad.net/xorg-edgers/radeon/ubuntu karmic main
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu karmic main
I have the latter, so i have no idea what the former does

Then install the latest kernel (2.6.32) either manually or from here (http://kernel.ubuntu.com/~kernel-ppa/mainline/) (there may be a ppa but i just downloaded and installed manually), there are also drm-next and daily build but i wouldn't recomend using them as they are less tested than 2.6.32 (which is pretty untested).

If you choose to do this, it's at your own risk and not my fault if you computer starts to crash more.My computer is running fine following my advice but yours may not.


Yep, that's the story I read too.
It's just that you said "There are some problems due to the GNU license that make it difficult from time to time.", but (as i understand it) the kernel code isn't really affected by ATI IP so GNU/GPL is not the problem. But perhaps i misunderstood the situation/your post.

[bluelamp999]

You can jump the gun, but your system will no longer be supported so you may run into bugs. Also with .32+latest xorg, things are better but 3d is still not great.

add one of the following to /etc/apt/sources.lst
deb http://ppa.launchpad.net/xorg-edgers/radeon/ubuntu karmic main
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu karmic main
I have the latter, so i have no idea what the former does

Then install the latest kernel (2.6.32) either manually or from here (http://kernel.ubuntu.com/~kernel-ppa/mainline/) (there may be a ppa but i just downloaded and installed manually), there are also drm-next and daily build but i wouldn't recomend using them as they are less tested than 2.6.32 (which is pretty untested).

If you choose to do this, it's at your own risk and not my fault if you computer starts to crash more.My computer is running fine following my advice but yours may not.

Wow! Thanks Xbehave!

I've got a stable Karmic install running right now so I probably shouldn't but I doubt I'll be able to resist the temptation...

[handy]

@bluelamp999: I'm far from an expert on this topic, I have just been following it consistently for about 5 months, apart from also putting up with the fglrx/catalyst drivers on Arch (which is constantly upgrading its packages). Because AMD/ATi doesn't support Arch (as it does Ubuntu), Arch ATi users have really had some ups & downs, I've only been on Arch since March 2008, & there has certainly been some fun & games in that period due to the unreliable & too slowly upgraded fglrx/catalyst drivers. At least for Ubuntu users, AMD try to have catalyst working with the 6 monthly Ubuntu release.

You may have seen this page, which is linked to on the first page of this thread:

http://wiki.x.org/wiki/RadeonFeature

Looking at that, should give you hope with regard to your R300 cored GPU I think. :)

I'm using an Radeon HD2600Pro, which uses the R600 core. I know people are getting good results with the R600 & R700 cores right now, due to what I read on this forum thread, the first post of which is basically kept up to date with the software developments:

http://bbs.archlinux.org/viewtopic.php?id=79509&p=1

As you can see by reading the first post on that page; by jumping through hoops you can get the best performance with the open-source solution on Arch.

I'm personally content to wait at least until kernel .32 comes out of [testing] on Arch (any day now) before I even think about starting to fiddle about with the open-source packages from [testing] & .git.
I'm really not in a big hurry, though I do look forward to having the great movie playback that the open-source drivers allowed me, last time I used them. :)

So my recommendation to you would be to continue patiently waiting, the day is coming when it will be an easy install & setup for your open-source ATi GPU solution.

If your hungry to have a go though, there is info' further back in this thread where someone has upgraded their Ubuntu to kernel .32 & installed the open-source packages, it may be worth reviewing, there was a link or two as well from memory.

Good luck. :)

[bluelamp999]

Many thanks for the reply and the advice. You're a star!

[handy]

Many thanks for the reply and the advice. You're a star!

:lolflag: I've been called a lot of things before, but that's a first. Thanks. ;)

[Nerd King]

That would be me then.. easy enough really.

1. http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ download and install headers_all, headers_i386/x64, image_i386/x64.
2. Add PPA xorg-edgers https://launchpad.net/~xorg-edgers/+archive/ppa for details on how.

It's fast and stable for me with linux games and compiz, a little slow on Wine gaming at this stage, but constantly improving it seems.

[handy]

That would be me then.. easy enough really.

1. http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ download and install headers_all, headers_i386/x64, image_i386/x64.
2. Add PPA xorg-edgers https://launchpad.net/~xorg-edgers/+archive/ppa for details on how.

It's fast and stable for me with linux games and compiz, a little slow on Wine gaming at this stage, but constantly improving it seems.

Thanks for popping up again Nerd King, I think I'll put your links in the OP, for a while so we don't loose your very valuable input. :)

[Edit:] I found that I already had a link to your page in the Ubuntu section of this threads OP.

I just added these links from your most recent post anyway, as it may help your truly valuable contribution to the Ubuntu ATi community sink in... :)

[Nerd King]

My contribution is zero. It's the devs who've done amazing things. They are gods whose shrines we should worship every day!

[handy]

My contribution is zero. It's the devs who've done amazing things. They are gods whose shrines we should worship every day!

I agree on both counts, to a point.

If no one communicates about the new changes; or their personal experiences with these changes, then far fewer people learn anything new.

Nor, if we keep following this train; do the people who actually created these changes to start with, get to find out what is wrong with their changes & how they can improve on them.

Your input Nerd King, has been incredibly valuable, particularly for Ubuntu users, as most of my information sources are Arch based or Linux system specific.

[handy]

Read following link for details on a hotfix that has allowed Catalyst 9.12 to work with kernel .32, it also brings openCL support:

http://bbs.archlinux.org/viewtopic.php?pid=673866#p673866

Not compatible with xorg-server 1.7 yet though.

[slonlt]

Hello, I'm running 3ghz dualcore 4gb ram and ati 3600. I want to play warcraft3 but it is very laggy. I'm using 2.6.32.2 kernel(the same was with 2.6.32) with XorgOnTheEdge. I have no lagg in linux games and no problems with compiz.

Maybe someone knows how to fix that lagg in wine(tried both stable and newest release)?

[AllRadioisDead]

Hello, I'm running 3ghz dualcore 4gb ram and ati 3600. I want to play warcraft3 but it is very laggy. I'm using 2.6.32.2 kernel(the same was with 2.6.32) with XorgOnTheEdge. I have no lagg in linux games and no problems with compiz.

Maybe someone knows how to fix that lagg in wine(tried both stable and newest release)?
I'm surprised you can run wine games with the native drivers, I'm impressed actually. When I heard progress was being made I never thought this much was being done.

[Nerd King]

2D Wine games are good, 3D accelerated a little slow. It's a matter of waiting for performance to pick up. Given the pace of development I'd say it'll catch Catalyst in the very near future (ie ready for 10.10).

[slonlt]

How to enable KMS? I want to have opengl 2.0 :)

[Xbehave]

How to enable KMS? I want to have opengl 2.0 :)

run glxgears -info to see if you have it already (it will say DRI2 if you do)

[slonlt]

IRQ's not enabled, falling back to busy waits: 2 0
GL_RENDERER = Mesa DRI R600 (RV635 9598) 20090101 TCL
GL_VERSION = 1.5 Mesa 7.7-rc3
GL_VENDOR = Advanced Micro Devices, Inc.

So no DRI2 :(

[Xbehave]

add this to your kernel line

radeon.modeset=1
e.g it should looks something like


kernel /vmlinuz-2.6.32-020632-generic root=UUID=3541b994-5510-4be5-bbe9-9fef4ffc0a86 ro quiet radeon.modeset=1
(i have grub1 read docs/ask somebody how to do this for grub2 if you need to.

[slonlt]

Done that and now I dont have any 3d acceleration it give me Software Renderer. Why is that?

[Ubuntiac]

I'm trying to get KMS / OGL 2.0 running as well with:

Lucid + xorg-edgers ppa + drm-next (2.6.32.996) + radeon.modeset=1 kernel line + an ATI HD4850

glxgears -info gives me:

do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
GL_RENDERER = Mesa DRI R600 (RV770 9440) 20090101 TCL DRI2
GL_VERSION = 2.0 Mesa 7.8-devel
GL_VENDOR = Advanced Micro Devices, Inc.

Wierd thing is, that all the drm sections of dmesg sound happy:

[ 1.918483] [drm] radeon kernel modesetting enabled.
[ 1.918866] radeon 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.918872] radeon 0000:01:00.0: setting latency timer to 64
[ 1.920616] [drm] radeon: Initializing kernel modesetting.
[ 1.920659] [drm] register mmio base: 0xFE9F0000
[ 1.920660] [drm] register mmio size: 65536
[ 1.921316] ATOM BIOS: Wekiva
[ 1.921322] [drm] Clocks initialized !
[ 1.924029] [drm] Detected VRAM RAM=256M, BAR=256M
[ 1.924033] [drm] RAM width 256bits DDR
[ 1.924143] [TTM] Zone kernel: Available graphics memory: 2029056 kiB.
[ 1.924157] [drm] radeon: 256M of VRAM memory ready
[ 1.924159] [drm] radeon: 512M of GTT memory ready.
[ 1.924202] [drm] Loading RV770 CP Microcode
[ 1.924281] platform radeon_cp.0: firmware: requesting radeon/RV770_pfp.bin
[ 1.926869] platform radeon_cp.0: firmware: requesting radeon/RV770_me.bin
[ 1.929048] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 1.970762] [drm] ring test succeeded in 1 usecs
[ 1.970823] [drm] radeon: ib pool ready.
[ 1.970877] [drm] ib test succeeded in 0 usecs
[ 1.970990] [drm] Radeon Display Connectors
[ 1.970991] [drm] Connector 0:
[ 1.970992] [drm] DVI-I
[ 1.970994] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
[ 1.970995] [drm] Encoders:
[ 1.970996] [drm] DFP1: INTERNAL_UNIPHY
[ 1.970997] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 1.970998] [drm] Connector 1:
[ 1.970999] [drm] DIN
[ 1.971000] [drm] Encoders:
[ 1.971001] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 1.971002] [drm] Connector 2:
[ 1.971003] [drm] DVI-I
[ 1.971004] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c
[ 1.971005] [drm] Encoders:
[ 1.971006] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 1.971007] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
[ 2.146110] [drm] fb mappable at 0xD0141000
[ 2.146112] [drm] vram apper at 0xD0000000
[ 2.146113] [drm] size 7257600
[ 2.146114] [drm] fb depth is 24
[ 2.146115] [drm] pitch is 6912
[ 2.146167] fb0: radeondrmfb frame buffer device
[ 2.146168] registered panic notifier
[ 2.146172] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
[ 2.147228] vga16fb: initializing
[ 2.147230] vga16fb: mapped to 0xffff8800000a0000
[ 2.147260] fb1: VGA16 VGA frame buffer device
[ 2.170460] executing set pll
[ 2.220035] executing set crtc timing
[ 2.220066] [drm] TV-13: set mode 1680x1050 25


Any ideas anyone?

[handy]

Have a look at this thread, as these guys are non-stop working with the cutting edge Linux based open-source ATi software.

On the first post you will get the current stuff as it is kept up to date, on the last 2 or 3 pages, depending on how fast things are moving at the time, you will get nitty-gritty details on just what is happening right now:

http://bbs.archlinux.org/viewtopic.php?id=79509&p=1

[Xbehave]

I'm trying to get KMS / OGL 2.0 running as well with:

Lucid + xorg-edgers ppa + drm-next (2.6.32.996) + radeon.modeset=1 kernel line + an ATI HD4850

glxgears -info gives me:

do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
GL_RENDERER = Mesa DRI R600 (RV770 9440) 20090101 TCL DRI2
GL_VERSION = 2.0 Mesa 7.8-devel
GL_VENDOR = Advanced Micro Devices, Inc.

Wierd thing is, that all the drm sections of dmesg sound happy:
The fact it says dri2 suggests you do have everything running, what sort of FPS do you get? The bug may be because your too cutting edge, do you have a plain old 2.6.32 lying around?


Done that and now I dont have any 3d acceleration it give me Software Renderer. Why is that?
what is the output of

glxgears -info

sudo cat /sys/module/radeon/parameters/modeset

edit: read the last couple of pages of handy's link (hey it's a long thread and i'm lazy) [thx for link]
1) there is an issue with kms and kernel 2.6.32.2
2) somebody has the exact same problem as Ubuntiac, but the post sort of got lost in the thread so i didn't see anything useful

[Ubuntiac]

I just realised that part of my problem was I got mixed up and that dmesg was from when I was in my vanilla .32 kernel, not the drm-next one.

DRM next with the modesetting variable does, infact give me errors about the firmware not being found;


[ 17.590185] [drm] Loading RV770 Microcode
[ 17.590188] platform radeon_cp.0: firmware: requesting radeon/RV770_pfp.bin
[ 17.635441] platform radeon_cp.0: firmware: requesting radeon/RV770_me.bin
[ 17.637929] platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin
[ 17.639727] r600_cp: Failed to load firmware "radeon/R700_rlc.bin"
[ 17.639732] [drm:rv770_startup] *ERROR* Failed to load firmware!

So where does one get this file R700_rlc.bin? I tried doing a find by file name in the package manager, but it didn't turn up anything...

[Xbehave]

http://www.phoronix.com/forums/showpost.php?p=104897&postcount=26

that seams to offer the files and where you have to put them

[Ubuntiac]

Thanks!

I think I'm really close now... I don't see any (EE) errors, although my screen goes black and the kernel seems to hang when X starts if I use radeon.modeset=1 (it's fine without it though)

The only things that look anything like errors are:

[ 0.168010] (II) RADEON(0): Not using mode "1680x1050" (bad mode clock/interlace/doublescan)

[ 0.359177] (II) AIGLX: Screen 0 is not DRI2 capable


and much later:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x46ecf8]
1: /usr/bin/X (0x400000+0x6d6fd) [0x46d6fd]
2: /lib/libpthread.so.0 (0x7f5d36b9a000+0xf190) [0x7f5d36ba9190]
3: /usr/bin/X (0x400000+0x3a04b) [0x43a04b]
4: /usr/bin/X (0x400000+0x3a35b) [0x43a35b]
5: /usr/bin/X (0x400000+0x3aede) [0x43aede]
6: /usr/bin/X (xf86PostMotionEventP+0x87) [0x47a027]
7: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f5d0e85b000+0x53df) [0x7f5d0e8603df]
8: /usr/bin/X (0x400000+0x778c7) [0x4778c7]
9: /usr/bin/X (0x400000+0x10fd24) [0x50fd24]
10: /lib/libpthread.so.0 (0x7f5d36b9a000+0xf190) [0x7f5d36ba9190]
11: /lib/libpthread.so.0 (__open64+0x10) [0x7f5d36ba8940]
12: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f5d0e85b000+0x32d1) [0x7f5d0e85e2d1]
13: /usr/bin/X (0x400000+0x7a577) [0x47a577]
14: /usr/bin/X (NewInputDeviceRequest+0x1ca) [0x47a97a]
15: /usr/bin/X (0x400000+0x10a12a) [0x50a12a]
16: /usr/bin/X (0x400000+0x10a3be) [0x50a3be]
17: /usr/bin/X (config_init+0x9) [0x45f109]
18: /usr/bin/X (0x400000+0x260a5) [0x4260a5]
19: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f5d35b1aadd]
20: /usr/bin/X (0x400000+0x25c99) [0x425c99]
Segmentation fault at address (nil)



Full Xorg.o.log for context is:


This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.7.99.2
Release Date: (unreleased)
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-26-xen x86_64 Ubuntu
Current Operating System: Linux morpheus 2.6.32-996-generic #200912181514 SMP Fri Dec 18 15:19:26 UTC 2009 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-996-generic root=UUID=ac91a2d9-31be-4b85-bf96-9eaf0d87b6b4 ro quiet splash
Build Date: 20 December 2009 12:32:38AM
xorg-server 2:1.7.99.2~git20091220.0cb638dc-0ubuntu0tormod (buildd@)
Current version of pixman: 0.16.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: [ 0.000000] (--) probed, [ 0.000007] (**) from config file, [ 0.000010] (==) default setting,
[ 0.000014] (++) from command line, [ 0.000017] (!!) notice, [ 0.000020] (II) informational,
[ 0.000024] (WW) warning, [ 0.000027] (EE) error, [ 0.000030] (NI) not implemented, [ 0.000033] (??) unknown.
[ 0.000066] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 22 04:22:39 2009
[ 0.000093] (==) Using config file: "/etc/X11/xorg.conf"
[ 0.000134] (==) No Layout section. Using the first Screen section.
[ 0.000139] (**) |-->Screen "Default Screen" (0)
[ 0.000143] (**) | |-->Monitor "<default monitor>"
[ 0.000290] (==) No device specified for screen "Default Screen".
Using the first device section listed.
[ 0.000293] (**) | |-->Device "Default Device"
[ 0.000296] (==) No monitor specified for screen "Default Screen".
Using a default monitor configuration.
[ 0.000309] (==) Automatically adding devices
[ 0.000312] (==) Automatically enabling devices
[ 0.000329] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
[ 0.000359] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[ 0.000362] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 0.000366] (II) Cannot locate a core pointer device.
[ 0.000369] (II) Cannot locate a core keyboard device.
[ 0.000371] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 0.000375] (II) Loader magic: 0x7cb400
[ 0.000378] (II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
[ 0.015323] (--) PCI:*(0:1:0:0) 1002:9440:1002:0502 ATI Technologies Inc RV770 [Radeon HD 4870] rev 0, Mem @ 0xd0000000/268435456, 0xfe9f0000/65536, I/O @ 0x0000c000/256, BIOS @ 0x????????/131072
[ 0.015381] (II) Open ACPI successful (/var/run/acpid.socket)
[ 0.015386] (II) "extmod" will be loaded by default.
[ 0.015389] (II) "dbe" will be loaded by default.
[ 0.015391] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 0.015394] (II) "record" will be loaded by default.
[ 0.015397] (II) "dri" will be loaded. This was enabled by default and also specified in the config file.
[ 0.015399] (II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
[ 0.015403] (II) LoadModule: "glx"
[ 0.015549] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 0.015655] (II) Module glx: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
[ 0.015671] (==) AIGLX enabled
[ 0.015675] (II) Loading extension GLX
[ 0.015684] (II) LoadModule: "dri"
[ 0.015730] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 0.015827] (II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
[ 0.015842] (II) Loading extension XFree86-DRI
[ 0.015846] (II) LoadModule: "dri2"
[ 0.015882] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 0.015926] (II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
[ 0.015939] (II) Loading extension DRI2
[ 0.015942] (II) LoadModule: "extmod"
[ 0.015975] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 0.016042] (II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
[ 0.016057] (II) Loading extension MIT-SCREEN-SAVER
[ 0.016059] (II) Loading extension XFree86-VidModeExtension
[ 0.016061] (II) Loading extension XFree86-DGA
[ 0.016064] (II) Loading extension DPMS
[ 0.016066] (II) Loading extension XVideo
[ 0.016069] (II) Loading extension XVideo-MotionCompensation
[ 0.016071] (II) Loading extension X-Resource
[ 0.016074] (II) LoadModule: "dbe"
[ 0.016111] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 0.016155] (II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
[ 0.016168] (II) Loading extension DOUBLE-BUFFER
[ 0.016171] (II) LoadModule: "record"
[ 0.016214] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 0.016253] (II) Module record: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
[ 0.016266] (II) Loading extension RECORD
[ 0.016269] (II) LoadModule: "ati"
[ 0.016449] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 0.016490] (II) Module ati: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 6.12.99
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
[ 0.016508] (II) LoadModule: "radeon"
[ 0.016663] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 0.016825] (II) Module radeon: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 6.12.99
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
[ 0.016849] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP),
ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Radeon 4800 Series, ATI Radeon 4800 Series, ATI FirePro M7750,
ATI M98, ATI M98, ATI M98, ATI Mobility Radeon HD 4650,
ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
ATI FirePro M5750, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon HD 4350,
ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
ATI Mobility Radeon 4500 Series, ATI FirePro RG220, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon RV710,
ATI Radeon HD 3470, ATI Mobility Radeon HD 3430,
ATI Mobility Radeon HD 3400 Series, ATI Radeon HD 3450,
ATI Radeon HD 3450, ATI Radeon HD 3430, ATI Radeon HD 3450,
ATI FirePro V3700, ATI FireMV 2450, ATI FireMV 2260, ATI FireMV 2260,
ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
ATI Radeon HD 3600 PRO, ATI Mobility Radeon HD 3650,
ATI Mobility Radeon HD 3670, ATI Mobility FireGL V5700,
ATI Mobility FireGL V5725, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3300 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3000 Graphics,
ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI RS880
[ 0.018335] (++) using VT number 7

[ 0.019517] (II) Primary Device is: PCI 01@00:00:0
[ 0.019587] (II) [KMS] drm report modesetting isn't supported.
[ 0.019638] (II) RADEON(0): Built from git commit 6e1f5553c6d7e3b5d089af2e3d587efe95936855
[ 0.019644] (II) RADEON(0): TOTO SAYS 00000000fe9f0000
[ 0.019647] (II) RADEON(0): MMIO registers at 0x00000000fe9f0000: size 64KB
[ 0.019684] (II) RADEON(0): PCI bus 1 card 0 func 0
[ 0.019697] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen" for depth/fbbpp 24/32
[ 0.019701] (**) RADEON(0): Depth 24, [ 0.019704] (--) framebuffer bpp 32
[ 0.019707] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 0.019712] (==) RADEON(0): Default visual is TrueColor
[ 0.019729] (II) Loading sub module "vgahw"
[ 0.019732] (II) LoadModule: "vgahw"
[ 0.019935] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 0.019990] (II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 6.0
[ 0.020013] (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 0.020018] (==) RADEON(0): RGB weight 888
[ 0.020021] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 0.020027] (--) RADEON(0): Chipset: "ATI Radeon 4800 Series" (ChipID = 0x9440)
[ 0.020033] (--) RADEON(0): Linear framebuffer at 0x00000000d0000000
[ 0.020071] (II) RADEON(0): PCIE card detected
[ 0.020087] (II) Loading sub module "int10"
[ 0.020090] (II) LoadModule: "int10"
[ 0.020278] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 0.020336] (II) Module int10: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 6.0
[ 0.020349] (II) RADEON(0): initializing int10
[ 0.025556] (II) RADEON(0): Primary V_BIOS segment is: 0xc000
[ 0.026282] (II) RADEON(0): ATOM BIOS detected
[ 0.026290] (II) RADEON(0): ATOM BIOS Rom:
[ 0.026292] SubsystemVendorID: 0x1002 SubsystemID: 0x0502
[ 0.026296] IOBaseAddress: 0xc000
[ 0.026299] Filename: B3B50701.100
[ 0.026301] BIOS Bootup Message:
Wekiva RV770 B50701 Board

[ 0.026307] (II) RADEON(0): Framebuffer space used by Firmware (kb): 20
[ 0.026310] (II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffec
[ 0.026313] (II) RADEON(0): AtomBIOS requests 20kB of VRAM scratch space
[ 0.026316] (II) RADEON(0): AtomBIOS VRAM scratch base: 0x7ffec
[ 0.026319] (II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory instead
[ 0.026331] (II) RADEON(0): Default Engine Clock: 750000
[ 0.026334] (II) RADEON(0): Default Memory Clock: 900000
[ 0.026337] (II) RADEON(0): Maximum Pixel ClockPLL Frequency Output: 1200000
[ 0.026340] (II) RADEON(0): Minimum Pixel ClockPLL Frequency Output: 0
[ 0.026342] (II) RADEON(0): Maximum Pixel ClockPLL Frequency Input: 16000
[ 0.026345] (II) RADEON(0): Minimum Pixel ClockPLL Frequency Input: 6000
[ 0.026348] (II) RADEON(0): Maximum Pixel Clock: 400000
[ 0.026350] (II) RADEON(0): Reference Clock: 100000
[ 0.026380] drmOpenDevice: node name is /dev/dri/card0
[ 0.028745] drmOpenDevice: open result is 11, (OK)
[ 0.031066] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 0.031099] drmOpenDevice: node name is /dev/dri/card0
[ 0.033404] drmOpenDevice: open result is 11, (OK)
[ 0.033455] drmOpenByBusid: drmOpenMinor returns 11
[ 0.033467] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 0.035791] (II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module version 1.31.0
[ 0.035826] (==) RADEON(0): Page Flipping disabled on r5xx and newer chips.

[ 0.035840] (II) RADEON(0): Will try to use DMA for Xv image transfers
[ 0.035847] (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K (PCI BAR=262144K)
[ 0.035851] (--) RADEON(0): Mapped VideoRAM: 262144 kByte (128 bit DDR SDRAM)
[ 0.035856] (II) RADEON(0): Color tiling disabled
[ 0.035862] (II) Loading sub module "ddc"
[ 0.035864] (II) LoadModule: "ddc"
[ 0.035876] (II) Module "ddc" already built-in
[ 0.035879] (II) Loading sub module "i2c"
[ 0.035881] (II) LoadModule: "i2c"
[ 0.035886] (II) Module "i2c" already built-in
[ 0.035906] (II) RADEON(0): PLL parameters: rf=10000 rd=12 min=60000 max=120000; xclk=40000
[ 0.035928] (II) RADEON(0): Output DVI-1 has no monitor section
[ 0.035936] (II) RADEON(0): I2C bus "DVI-1" initialized.
[ 0.035940] (II) RADEON(0): Output DVI-0 has no monitor section
[ 0.035943] (II) RADEON(0): I2C bus "DVI-0" initialized.
[ 0.035947] (II) RADEON(0): Port0:
XRANDR name: DVI-1
Connector: DVI-I
CRT2: INTERNAL_KLDSCP_DAC2
DFP1: INTERNAL_UNIPHY
DDC reg: 0x7e60
[ 0.035969] (II) RADEON(0): Port1:
XRANDR name: DVI-0
Connector: DVI-I
CRT1: INTERNAL_KLDSCP_DAC1
DFP2: INTERNAL_KLDSCP_LVTMA
DDC reg: 0x7e20
[ 0.035996] (II) RADEON(0): I2C device "DVI-1:ddc2" registered at address 0xA0.
Dac detection success
[ 0.046204] (II) RADEON(0): Output: DVI-1, Detected Monitor Type: 0
Unhandled monitor type 0
finished output detect: 0
[ 0.046221] (II) RADEON(0): I2C device "DVI-0:ddc2" registered at address 0xA0.
[ 0.048117] (II) RADEON(0): I2C device "DVI-0:DDC control interface" registered at address 0x6E.
[ 0.101665] (II) RADEON(0): EDID for output DVI-0
[ 0.101669] (II) RADEON(0): Manufacturer: SAM Model: 30c Serial#: 1296380466
[ 0.101672] (II) RADEON(0): Year: 2007 Week: 41
[ 0.101675] (II) RADEON(0): EDID Version: 1.3
[ 0.101677] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 0.101684] (II) RADEON(0): Sync: Separate Composite SyncOnGreen
[ 0.101692] (II) RADEON(0): Max Image Size [cm]: horiz.: 47 vert.: 30
[ 0.101697] (II) RADEON(0): Gamma: 2.20
[ 0.101707] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
[ 0.101712] (II) RADEON(0): First detailed timing is preferred mode
[ 0.101715] (II) RADEON(0): redX: 0.644 redY: 0.333 greenX: 0.286 greenY: 0.603
[ 0.101721] (II) RADEON(0): blueX: 0.152 blueY: 0.079 whiteX: 0.313 whiteY: 0.329
[ 0.101727] (II) RADEON(0): Supported established timings:
[ 0.101729] (II) RADEON(0): 720x400@70Hz
[ 0.101732] (II) RADEON(0): 640x480@60Hz
[ 0.101734] (II) RADEON(0): 640x480@67Hz
[ 0.101737] (II) RADEON(0): 640x480@72Hz
[ 0.101739] (II) RADEON(0): 640x480@75Hz
[ 0.101741] (II) RADEON(0): 800x600@56Hz
[ 0.101743] (II) RADEON(0): 800x600@60Hz
[ 0.101746] (II) RADEON(0): 800x600@72Hz
[ 0.101748] (II) RADEON(0): 800x600@75Hz
[ 0.101750] (II) RADEON(0): 832x624@75Hz
[ 0.101753] (II) RADEON(0): 1024x768@60Hz
[ 0.101755] (II) RADEON(0): 1024x768@70Hz
[ 0.101758] (II) RADEON(0): 1024x768@75Hz
[ 0.101760] (II) RADEON(0): 1280x1024@75Hz
[ 0.101762] (II) RADEON(0): 1152x864@75Hz
[ 0.101765] (II) RADEON(0): Manufacturer's mask: 0
[ 0.101767] (II) RADEON(0): Supported standard timings:
[ 0.101769] (II) RADEON(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 0.101772] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 0.101775] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 0.101778] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 0.101781] (II) RADEON(0): Supported detailed timing:
[ 0.101784] (II) RADEON(0): clock: 119.0 MHz Image Size: 474 x 296 mm
[ 0.101790] (II) RADEON(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
[ 0.101795] (II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
[ 0.101799] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
[ 0.101809] (II) RADEON(0): Monitor name: SyncMaster
[ 0.101812] (II) RADEON(0): Serial No: HVCPA10751
[ 0.101815] (II) RADEON(0): EDID (in hex):
[ 0.101819] (II) RADEON(0): 00ffffffffffff004c2d0c033232454d
[ 0.101824] (II) RADEON(0): 291101030e2f1e782ad515a455499a27
[ 0.101828] (II) RADEON(0): 145054bfef80b30081808140714f0101
[ 0.101832] (II) RADEON(0): 0101010101017c2e90a0601a1e403020
[ 0.101836] (II) RADEON(0): 3600da281100001a000000fd00384b1e
[ 0.101841] (II) RADEON(0): 510e000a202020202020000000fc0053
[ 0.101845] (II) RADEON(0): 796e634d61737465720a2020000000ff
[ 0.101849] (II) RADEON(0): 00485643504131303735310a20200009
[ 0.101853] (II) RADEON(0): Output: DVI-0, Detected Monitor Type: 1
[ 0.101856] (II) RADEON(0): EDID data from the display on output: DVI-0 ----------------------
[ 0.101859] (II) RADEON(0): Manufacturer: SAM Model: 30c Serial#: 1296380466
[ 0.101862] (II) RADEON(0): Year: 2007 Week: 41
[ 0.101864] (II) RADEON(0): EDID Version: 1.3
[ 0.101867] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 0.101872] (II) RADEON(0): Sync: Separate Composite SyncOnGreen
[ 0.101880] (II) RADEON(0): Max Image Size [cm]: horiz.: 47 vert.: 30
[ 0.101885] (II) RADEON(0): Gamma: 2.20
[ 0.101888] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
[ 0.101893] (II) RADEON(0): First detailed timing is preferred mode
[ 0.101895] (II) RADEON(0): redX: 0.644 redY: 0.333 greenX: 0.286 greenY: 0.603
[ 0.101901] (II) RADEON(0): blueX: 0.152 blueY: 0.079 whiteX: 0.313 whiteY: 0.329
[ 0.101906] (II) RADEON(0): Supported established timings:
[ 0.101908] (II) RADEON(0): 720x400@70Hz
[ 0.101911] (II) RADEON(0): 640x480@60Hz
[ 0.101913] (II) RADEON(0): 640x480@67Hz
[ 0.101915] (II) RADEON(0): 640x480@72Hz
[ 0.101917] (II) RADEON(0): 640x480@75Hz
[ 0.101920] (II) RADEON(0): 800x600@56Hz
[ 0.101922] (II) RADEON(0): 800x600@60Hz
[ 0.101924] (II) RADEON(0): 800x600@72Hz
[ 0.101927] (II) RADEON(0): 800x600@75Hz
[ 0.101929] (II) RADEON(0): 832x624@75Hz
[ 0.101931] (II) RADEON(0): 1024x768@60Hz
[ 0.101933] (II) RADEON(0): 1024x768@70Hz
[ 0.101936] (II) RADEON(0): 1024x768@75Hz
[ 0.101938] (II) RADEON(0): 1280x1024@75Hz
[ 0.101940] (II) RADEON(0): 1152x864@75Hz
[ 0.101943] (II) RADEON(0): Manufacturer's mask: 0
[ 0.101945] (II) RADEON(0): Supported standard timings:
[ 0.101948] (II) RADEON(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 0.101950] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 0.101953] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 0.101956] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 0.101959] (II) RADEON(0): Supported detailed timing:
[ 0.101961] (II) RADEON(0): clock: 119.0 MHz Image Size: 474 x 296 mm
[ 0.101966] (II) RADEON(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
[ 0.101971] (II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
[ 0.101975] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
[ 0.101979] (II) RADEON(0): Monitor name: SyncMaster
[ 0.101982] (II) RADEON(0): Serial No: HVCPA10751
[ 0.101984] (II) RADEON(0): EDID (in hex):
[ 0.101988] (II) RADEON(0): 00ffffffffffff004c2d0c033232454d
[ 0.101992] (II) RADEON(0): 291101030e2f1e782ad515a455499a27
[ 0.101997] (II) RADEON(0): 145054bfef80b30081808140714f0101
[ 0.102001] (II) RADEON(0): 0101010101017c2e90a0601a1e403020
[ 0.102005] (II) RADEON(0): 3600da281100001a000000fd00384b1e
[ 0.102009] (II) RADEON(0): 510e000a202020202020000000fc0053
[ 0.102013] (II) RADEON(0): 796e634d61737465720a2020000000ff
[ 0.102017] (II) RADEON(0): 00485643504131303735310a20200009
finished output detect: 1
finished all detect
before xf86InitialConfiguration
Dac detection success
[ 0.112213] (II) RADEON(0): Output: DVI-1, Detected Monitor Type: 0
Unhandled monitor type 0
[ 0.112227] (II) RADEON(0): EDID for output DVI-1
[ 0.167633] (II) RADEON(0): EDID for output DVI-0
[ 0.167637] (II) RADEON(0): Manufacturer: SAM Model: 30c Serial#: 1296380466
[ 0.167640] (II) RADEON(0): Year: 2007 Week: 41
[ 0.167643] (II) RADEON(0): EDID Version: 1.3
[ 0.167645] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 0.167651] (II) RADEON(0): Sync: Separate Composite SyncOnGreen
[ 0.167658] (II) RADEON(0): Max Image Size [cm]: horiz.: 47 vert.: 30
[ 0.167664] (II) RADEON(0): Gamma: 2.20
[ 0.167669] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
[ 0.167674] (II) RADEON(0): First detailed timing is preferred mode
[ 0.167676] (II) RADEON(0): redX: 0.644 redY: 0.333 greenX: 0.286 greenY: 0.603
[ 0.167682] (II) RADEON(0): blueX: 0.152 blueY: 0.079 whiteX: 0.313 whiteY: 0.329
[ 0.167687] (II) RADEON(0): Supported established timings:
[ 0.167690] (II) RADEON(0): 720x400@70Hz
[ 0.167692] (II) RADEON(0): 640x480@60Hz
[ 0.167694] (II) RADEON(0): 640x480@67Hz
[ 0.167697] (II) RADEON(0): 640x480@72Hz
[ 0.167699] (II) RADEON(0): 640x480@75Hz
[ 0.167701] (II) RADEON(0): 800x600@56Hz
[ 0.167704] (II) RADEON(0): 800x600@60Hz
[ 0.167706] (II) RADEON(0): 800x600@72Hz
[ 0.167708] (II) RADEON(0): 800x600@75Hz
[ 0.167711] (II) RADEON(0): 832x624@75Hz
[ 0.167713] (II) RADEON(0): 1024x768@60Hz
[ 0.167715] (II) RADEON(0): 1024x768@70Hz
[ 0.167718] (II) RADEON(0): 1024x768@75Hz
[ 0.167720] (II) RADEON(0): 1280x1024@75Hz
[ 0.167722] (II) RADEON(0): 1152x864@75Hz
[ 0.167725] (II) RADEON(0): Manufacturer's mask: 0
[ 0.167727] (II) RADEON(0): Supported standard timings:
[ 0.167730] (II) RADEON(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 0.167732] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 0.167735] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 0.167738] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 0.167741] (II) RADEON(0): Supported detailed timing:
[ 0.167744] (II) RADEON(0): clock: 119.0 MHz Image Size: 474 x 296 mm
[ 0.167749] (II) RADEON(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
[ 0.167753] (II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
[ 0.167758] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
[ 0.167762] (II) RADEON(0): Monitor name: SyncMaster
[ 0.167765] (II) RADEON(0): Serial No: HVCPA10751
[ 0.167767] (II) RADEON(0): EDID (in hex):
[ 0.167771] (II) RADEON(0): 00ffffffffffff004c2d0c033232454d
[ 0.167776] (II) RADEON(0): 291101030e2f1e782ad515a455499a27
[ 0.167780] (II) RADEON(0): 145054bfef80b30081808140714f0101
[ 0.167784] (II) RADEON(0): 0101010101017c2e90a0601a1e403020
[ 0.167788] (II) RADEON(0): 3600da281100001a000000fd00384b1e
[ 0.167792] (II) RADEON(0): 510e000a202020202020000000fc0053
[ 0.167797] (II) RADEON(0): 796e634d61737465720a2020000000ff
[ 0.167801] (II) RADEON(0): 00485643504131303735310a20200009
[ 0.167804] (II) RADEON(0): Output: DVI-0, Detected Monitor Type: 1
[ 0.167806] (II) RADEON(0): EDID data from the display on output: DVI-0 ----------------------
[ 0.167809] (II) RADEON(0): Manufacturer: SAM Model: 30c Serial#: 1296380466
[ 0.167812] (II) RADEON(0): Year: 2007 Week: 41
[ 0.167814] (II) RADEON(0): EDID Version: 1.3
[ 0.167817] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 0.167822] (II) RADEON(0): Sync: Separate Composite SyncOnGreen
[ 0.167829] (II) RADEON(0): Max Image Size [cm]: horiz.: 47 vert.: 30
[ 0.167835] (II) RADEON(0): Gamma: 2.20
[ 0.167838] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
[ 0.167843] (II) RADEON(0): First detailed timing is preferred mode
[ 0.167845] (II) RADEON(0): redX: 0.644 redY: 0.333 greenX: 0.286 greenY: 0.603
[ 0.167850] (II) RADEON(0): blueX: 0.152 blueY: 0.079 whiteX: 0.313 whiteY: 0.329
[ 0.167859] (II) RADEON(0): Supported established timings:
[ 0.167861] (II) RADEON(0): 720x400@70Hz
[ 0.167863] (II) RADEON(0): 640x480@60Hz
[ 0.167866] (II) RADEON(0): 640x480@67Hz
[ 0.167868] (II) RADEON(0): 640x480@72Hz
[ 0.167870] (II) RADEON(0): 640x480@75Hz
[ 0.167873] (II) RADEON(0): 800x600@56Hz
[ 0.167875] (II) RADEON(0): 800x600@60Hz
[ 0.167877] (II) RADEON(0): 800x600@72Hz
[ 0.167880] (II) RADEON(0): 800x600@75Hz
[ 0.167882] (II) RADEON(0): 832x624@75Hz
[ 0.167884] (II) RADEON(0): 1024x768@60Hz
[ 0.167887] (II) RADEON(0): 1024x768@70Hz
[ 0.167889] (II) RADEON(0): 1024x768@75Hz
[ 0.167891] (II) RADEON(0): 1280x1024@75Hz
[ 0.167894] (II) RADEON(0): 1152x864@75Hz
[ 0.167896] (II) RADEON(0): Manufacturer's mask: 0
[ 0.167898] (II) RADEON(0): Supported standard timings:
[ 0.167901] (II) RADEON(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 0.167904] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 0.167907] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 0.167909] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 0.167912] (II) RADEON(0): Supported detailed timing:
[ 0.167915] (II) RADEON(0): clock: 119.0 MHz Image Size: 474 x 296 mm
[ 0.167920] (II) RADEON(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
[ 0.167924] (II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
[ 0.167928] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
[ 0.167932] (II) RADEON(0): Monitor name: SyncMaster
[ 0.167935] (II) RADEON(0): Serial No: HVCPA10751
[ 0.167937] (II) RADEON(0): EDID (in hex):
[ 0.167942] (II) RADEON(0): 00ffffffffffff004c2d0c033232454d
[ 0.167946] (II) RADEON(0): 291101030e2f1e782ad515a455499a27
[ 0.167950] (II) RADEON(0): 145054bfef80b30081808140714f0101
[ 0.167954] (II) RADEON(0): 0101010101017c2e90a0601a1e403020
[ 0.167958] (II) RADEON(0): 3600da281100001a000000fd00384b1e
[ 0.167963] (II) RADEON(0): 510e000a202020202020000000fc0053
[ 0.167967] (II) RADEON(0): 796e634d61737465720a2020000000ff
[ 0.167971] (II) RADEON(0): 00485643504131303735310a20200009
[ 0.167977] (II) RADEON(0): EDID vendor "SAM", prod id 780
[ 0.168010] (II) RADEON(0): Not using mode "1680x1050" (bad mode clock/interlace/doublescan)
[ 0.168015] (II) RADEON(0): Printing probed modes for output DVI-0
[ 0.168019] (II) RADEON(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz)
[ 0.168025] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 0.168030] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
[ 0.168035] (II) RADEON(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 0.168040] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 0.168045] (II) RADEON(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 0.168051] (II) RADEON(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
[ 0.168056] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 0.168061] (II) RADEON(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 0.168066] (II) RADEON(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 0.168071] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 0.168076] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 0.168084] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 0.168089] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 0.168094] (II) RADEON(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 0.168099] (II) RADEON(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
[ 0.168105] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 0.168110] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 0.168116] (II) RADEON(0): Output DVI-1 disconnected
[ 0.168119] (II) RADEON(0): Output DVI-0 connected
[ 0.168123] (II) RADEON(0): Using exact sizes for initial modes
[ 0.168126] (II) RADEON(0): Output DVI-0 using initial mode 1680x1050
[ 0.168136] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 0.168145] (==) RADEON(0): DPI set to (96, 96)
[ 0.168148] (II) Loading sub module "fb"
[ 0.168150] (II) LoadModule: "fb"
[ 0.168265] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 0.168376] (II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
[ 0.168390] (II) Loading sub module "ramdac"
[ 0.168393] (II) LoadModule: "ramdac"
[ 0.168400] (II) Module "ramdac" already built-in
[ 0.168404] (==) RADEON(0): Will attempt to use R6xx/R7xx EXA support if DRI is enabled.
[ 0.168407] (II) Loading sub module "exa"
[ 0.168409] (II) LoadModule: "exa"
[ 0.168605] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 0.168659] (II) Module exa: vendor="X.Org Foundation"
compiled for 1.7.99.2, module version = 2.5.0
ABI class: X.Org Video Driver, version 6.0
[ 0.168768] (!!) RADEON(0): MergedFB support has been removed and replaced with xrandr 1.2 support
[ 0.168778] (--) Depth 24 pixmap format is 32 bpp
[ 0.168810] (II) RADEON(0): RADEONScreenInit d0000000 0 0
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
[ 0.277662] (II) RADEON(0): Dynamic Power Management Disabled
[ 0.277673] (==) RADEON(0): Using 24 bit depth buffer
mc fb loc is 00ef00d0
[ 0.277684] (II) RADEON(0): RADEONInitMemoryMap() :
[ 0.277686] (II) RADEON(0): mem_size : 0x20000000
[ 0.277689] (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0
[ 0.277692] (II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
[ 0.277694] (II) RADEON(0): Depth moves disabled by default
[ 0.277704] (II) RADEON(0): Allocating from a screen of 262080 kb
[ 0.277708] (II) RADEON(0): Will use 32 kb for hardware cursor 0 at offset 0x00b7c000
[ 0.277711] (II) RADEON(0): Will use 32 kb for hardware cursor 1 at offset 0x00b80000
[ 0.277714] (II) RADEON(0): Will use 11760 kb for front buffer at offset 0x00000000
[ 0.277755] (II) RADEON(0): Will use 64 kb for PCI GART at offset 0x0fff0000
[ 0.277758] (II) RADEON(0): Will use 11760 kb for back buffer at offset 0x00b84000
[ 0.277761] (II) RADEON(0): Will use 11760 kb for depth buffer at offset 0x01700000
[ 0.277764] (II) RADEON(0): Will use 112640 kb for textures at offset 0x0227c000
[ 0.277766] (II) RADEON(0): Will use 114128 kb for X Server offscreen at offset 0x0907c000
[ 0.277789] drmOpenDevice: node name is /dev/dri/card0
[ 0.280129] drmOpenDevice: open result is 11, (OK)
[ 0.282457] drmOpenDevice: node name is /dev/dri/card0
[ 0.284814] drmOpenDevice: open result is 11, (OK)
[ 0.287117] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 0.287150] drmOpenDevice: node name is /dev/dri/card0
[ 0.289456] drmOpenDevice: open result is 11, (OK)
[ 0.289486] drmOpenByBusid: drmOpenMinor returns 11
[ 0.289497] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 0.289524] (II) [drm] DRM interface version 1.3
[ 0.289558] (II) [drm] DRM open master succeeded.
[ 0.289572] (II) RADEON(0): [drm] Using the DRM lock SAREA also for drawables.
[ 0.289576] (II) RADEON(0): [drm] framebuffer handle = 0xd0000000
[ 0.289598] (II) RADEON(0): [drm] added 1 reserved context for kernel
[ 0.289608] (II) RADEON(0): X context handle = 0x1
[ 0.289631] (II) RADEON(0): [drm] installed DRM signal handler
[ 0.300742] (II) RADEON(0): [pci] 32768 kB allocated with handle 0x1152e900
[ 0.300795] (II) RADEON(0): [pci] ring handle = 0x2b7ff000
[ 0.300811] (II) RADEON(0): [pci] Ring mapped at 0x7f5d37738000
[ 0.300816] (II) RADEON(0): [pci] Ring contents 0x00000000
[ 0.300820] (II) RADEON(0): [pci] ring read ptr handle = 0x1b800000
[ 0.300824] (II) RADEON(0): [pci] Ring read ptr mapped at 0x7f5d37737000
[ 0.300828] (II) RADEON(0): [pci] Ring read ptr contents 0x00000000
[ 0.300832] (II) RADEON(0): [pci] vertex/indirect buffers handle = 0x2b800000
[ 0.300847] (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0x7f5d22e1f000
[ 0.300854] (II) RADEON(0): [pci] Vertex/indirect buffers contents 0x00000000
[ 0.300858] (II) RADEON(0): [pci] GART texture map handle = 0x2b801000
[ 0.300863] (II) RADEON(0): [pci] GART Texture map mapped at 0x7f5d2119f000
[ 0.300935] (II) RADEON(0): [drm] register handle = 0x2fff8000
[ 0.300955] (II) RADEON(0): [dri] Visual configs initialized
[ 0.301038] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 0.301041] (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x001f0000
[ 0.301046] (II) RADEON(0): MC_AGP_LOCATION : 0x003f0000
[ 0.311147] (==) RADEON(0): Backing store disabled
[ 0.311173] (II) RADEON(0): [DRI] installation complete
[ 0.346779] (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
[ 0.346801] (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
[ 0.346816] (II) RADEON(0): [drm] dma control initialized, using IRQ 18
[ 0.346820] (II) RADEON(0): [drm] Initialized kernel GART heap manager, 29884416
[ 0.346836] (WW) RADEON(0): DRI init changed memory map, adjusting ...
[ 0.346839] (WW) RADEON(0): MC_FB_LOCATION was: 0x00ef00d0 is: 0x00ef00d0
[ 0.346842] (WW) RADEON(0): MC_AGP_LOCATION was: 0x003f0000 is: 0x00030000
[ 0.346848] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 0.346851] (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x00ef00d0
[ 0.346853] (II) RADEON(0): MC_AGP_LOCATION : 0x00030000
[ 0.346859] (II) RADEON(0): Direct rendering enabled
[ 0.346867] (II) RADEON(0): Setting EXA maxPitchBytes
[ 0.346886] (II) EXA(0): Offscreen pixmap area of 116867072 bytes
[ 0.346894] (II) EXA(0): Driver registered support for the following operations:
[ 0.346897] (II) Solid
[ 0.346899] (II) Copy
[ 0.346901] (II) Composite (RENDER acceleration)
[ 0.346903] (II) UploadToScreen
[ 0.346905] (II) DownloadFromScreen
[ 0.346916] (II) RADEON(0): Acceleration enabled
[ 0.346921] (==) RADEON(0): DPMS enabled
[ 0.346926] (==) RADEON(0): Silken mouse enabled
[ 0.346968] (II) RADEON(0): Set up textured video
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Mode 1680x1050 - 1840 1080 9
[ 0.351103] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 0.351106] (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x00ef00d0
[ 0.351109] (II) RADEON(0): MC_AGP_LOCATION : 0x00030000
before 11900
after 11900
ffreq: 119000.000000
best_freq: 119000
best_feedback_div: 83.3
best_ref_div: 7
best_post_div: 10
[ 0.351147] (II) RADEON(0): crtc(0) Clock: mode 119000, PLL 119000
[ 0.351150] (II) RADEON(0): crtc(0) PLL : refdiv 7, fbdiv 0x53(83), fracfbdiv 3, pdiv 10
Set CRTC 0 PLL success
Set CRTC Timing success
Set CRTC 0 Overscan success
Not using RMX
scaler 0 setup success
Set CRTC 0 Source success
crtc 0 YUV disable setup success
Output DAC1 setup success
Output CRT1 enable success
Enable CRTC 0 success
Enable CRTC memreq 0 success
Unblank CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
[ 0.354235] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Mode 1680x1050 - 1840 1080 9
[ 0.354395] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 0.354398] (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x00ef00d0
[ 0.354401] (II) RADEON(0): MC_AGP_LOCATION : 0x00030000
before 11900
after 11900
ffreq: 119000.000000
best_freq: 119000
best_feedback_div: 83.3
best_ref_div: 7
best_post_div: 10
[ 0.354430] (II) RADEON(0): crtc(0) Clock: mode 119000, PLL 119000
[ 0.354433] (II) RADEON(0): crtc(0) PLL : refdiv 7, fbdiv 0x53(83), fracfbdiv 3, pdiv 10
Set CRTC 0 PLL success
Set CRTC Timing success
Set CRTC 0 Overscan success
Not using RMX
scaler 0 setup success
Set CRTC 0 Source success
crtc 0 YUV disable setup success
Output DAC1 setup success
Output CRT1 enable success
Enable CRTC 0 success
Enable CRTC memreq 0 success
Unblank CRTC 0 success
[ 0.354837] (--) RandR disabled
[ 0.354843] (II) Initializing built-in extension Generic Event Extension
[ 0.354846] (II) Initializing built-in extension SHAPE
[ 0.354849] (II) Initializing built-in extension MIT-SHM
[ 0.354851] (II) Initializing built-in extension XInputExtension
[ 0.354853] (II) Initializing built-in extension XTEST
[ 0.354855] (II) Initializing built-in extension BIG-REQUESTS
[ 0.354858] (II) Initializing built-in extension SYNC
[ 0.354860] (II) Initializing built-in extension XKEYBOARD
[ 0.354862] (II) Initializing built-in extension XC-MISC
[ 0.354864] (II) Initializing built-in extension SECURITY
[ 0.354866] (II) Initializing built-in extension XINERAMA
[ 0.354868] (II) Initializing built-in extension XFIXES
[ 0.354871] (II) Initializing built-in extension RENDER
[ 0.354873] (II) Initializing built-in extension RANDR
[ 0.354875] (II) Initializing built-in extension COMPOSITE
[ 0.354877] (II) Initializing built-in extension DAMAGE
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
[ 0.359177] (II) AIGLX: Screen 0 is not DRI2 capable
[ 0.359190] drmOpenDevice: node name is /dev/dri/card0
[ 0.359205] drmOpenDevice: open result is 12, (OK)
[ 0.359216] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 0.359219] drmOpenDevice: node name is /dev/dri/card0
[ 0.359225] drmOpenDevice: open result is 12, (OK)
[ 0.359228] drmOpenByBusid: drmOpenMinor returns 12
[ 0.359233] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 0.367580] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 0.367593] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 0.367596] (II) AIGLX: enabled GLX_texture_from_pixmap with driver support
[ 0.367615] (II) AIGLX: Loaded and initialized /usr/lib/dri/r600_dri.so
[ 0.367618] (II) GLX: Initialized DRI GL provider for screen 0
[ 0.367822] (II) RADEON(0): Setting screen physical size to 444 x 277
[ 0.381112] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[ 0.382092] (II) config/udev: Adding input device "Power Button" (/dev/input/event1)
[ 0.382106] (II) LoadModule: "evdev"
[ 0.382186] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 0.382250] (II) Module evdev: vendor="X.Org Foundation"
compiled for 1.7.2, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
[ 0.382279] (**) "Power Button": always reports core events
[ 0.382284] (**) "Power Button": Device: "/dev/input/event1"
[ 0.423455] (II) "Power Button": Found keys
[ 0.423467] (II) "Power Button": Configuring as keyboard
[ 0.423481] (II) XINPUT: Adding extended input device ""Power Button"" (type: KEYBOARD)
[ 0.423490] (**) Option "xkb_rules" "evdev"
[ 0.423497] (**) Option "xkb_model" "pc105"
[ 0.423502] (**) Option "xkb_layout" "us"
[ 0.423789] (II) config/udev: Adding input device "Power Button" (/dev/input/event0)
[ 0.423805] (**) "Power Button": always reports core events
[ 0.423809] (**) "Power Button": Device: "/dev/input/event0"
[ 0.483441] (II) "Power Button": Found keys
[ 0.483452] (II) "Power Button": Configuring as keyboard
[ 0.483459] (II) XINPUT: Adding extended input device ""Power Button"" (type: KEYBOARD)
[ 0.483463] (**) Option "xkb_rules" "evdev"
[ 0.483469] (**) Option "xkb_model" "pc105"
[ 0.483474] (**) Option "xkb_layout" "us"
[ 0.483792] (II) config/udev: Adding input device "Logitech USB-PS/2 Optical Mouse" (/dev/input/event4)
[ 0.483806] (**) "Logitech USB-PS/2 Optical Mouse": always reports core events
[ 0.483809] (**) "Logitech USB-PS/2 Optical Mouse": Device: "/dev/input/event4"
[ 0.563455] (II) "Logitech USB-PS/2 Optical Mouse": Found 12 mouse buttons
[ 0.563466] (II) "Logitech USB-PS/2 Optical Mouse": Found scroll wheel(s)
[ 0.563469] (II) "Logitech USB-PS/2 Optical Mouse": Found relative axes
[ 0.563471] (II) "Logitech USB-PS/2 Optical Mouse": Found x and y relative axes
[ 0.563474] (II) "Logitech USB-PS/2 Optical Mouse": Configuring as mouse
[ 0.563481] (**) "Logitech USB-PS/2 Optical Mouse": YAxisMapping: buttons 4 and 5
[ 0.563484] (**) "Logitech USB-PS/2 Optical Mouse": EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 0.563490] (II) XINPUT: Adding extended input device ""Logitech USB-PS/2 Optical Mouse"" (type: MOUSE)
[ 0.563526] (**) "Logitech USB-PS/2 Optical Mouse": (accel) keeping acceleration scheme 1
[ 0.563532] (**) "Logitech USB-PS/2 Optical Mouse": (accel) acceleration profile 0
[ 0.563540] (II) "Logitech USB-PS/2 Optical Mouse": initialized for relative axes.
[ 0.563912] (II) config/udev: Adding input device "Aiptek" (/dev/input/event6)
[ 0.563929] (**) "Aiptek": always reports core events
[ 0.563932] (**) "Aiptek": Device: "/dev/input/event6"

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x46ecf8]
1: /usr/bin/X (0x400000+0x6d6fd) [0x46d6fd]
2: /lib/libpthread.so.0 (0x7f5d36b9a000+0xf190) [0x7f5d36ba9190]
3: /usr/bin/X (0x400000+0x3a04b) [0x43a04b]
4: /usr/bin/X (0x400000+0x3a35b) [0x43a35b]
5: /usr/bin/X (0x400000+0x3aede) [0x43aede]
6: /usr/bin/X (xf86PostMotionEventP+0x87) [0x47a027]
7: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f5d0e85b000+0x53df) [0x7f5d0e8603df]
8: /usr/bin/X (0x400000+0x778c7) [0x4778c7]
9: /usr/bin/X (0x400000+0x10fd24) [0x50fd24]
10: /lib/libpthread.so.0 (0x7f5d36b9a000+0xf190) [0x7f5d36ba9190]
11: /lib/libpthread.so.0 (__open64+0x10) [0x7f5d36ba8940]
12: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f5d0e85b000+0x32d1) [0x7f5d0e85e2d1]
13: /usr/bin/X (0x400000+0x7a577) [0x47a577]
14: /usr/bin/X (NewInputDeviceRequest+0x1ca) [0x47a97a]
15: /usr/bin/X (0x400000+0x10a12a) [0x50a12a]
16: /usr/bin/X (0x400000+0x10a3be) [0x50a3be]
17: /usr/bin/X (config_init+0x9) [0x45f109]
18: /usr/bin/X (0x400000+0x260a5) [0x4260a5]
19: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f5d35b1aadd]
20: /usr/bin/X (0x400000+0x25c99) [0x425c99]
Segmentation fault at address (nil)

Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

[ 0.723443] (II) "Power Button": Close
[ 0.723466] (II) UnloadModule: "evdev"
[ 0.803441] (II) "Power Button": Close
[ 0.803461] (II) UnloadModule: "evdev"
[ 0.963444] (II) "Logitech USB-PS/2 Optical Mouse": Close
[ 0.963460] (II) UnloadModule: "evdev"
[ 0.963494] (II) AIGLX: Suspending AIGLX clients for VT switch
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
[ 0.971244] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 0.971247] (II) RADEON(0): MC_FB_LOCATION : 0x001f0000 0x00ef00d0
[ 0.971250] (II) RADEON(0): MC_AGP_LOCATION : 0x00000000
[ 0.981333] (II) RADEON(0): avivo_restore !
Enable CRTC 0 success
Enable CRTC memreq 0 success
Unblank CRTC 0 success
ddxSigGiveUp: Closing log

[handy]

This is where they are up to in Arch with this lot; I though that it may help someone with version compatibility here:

With the recent release of Mesa 7.7 and some new package entering testing, I wonder what packages are now required to be build from git?


As far I know :
* kernel26 from testing is 2.6.32.2 and breaks KMW so we need either 2.6.32.1 or 2.6.33-rc1
* libdrm in testing is 2.4.17 and it's enough (at least) for my need (KMS, compositing with Kwin)
* xf86-video-ati in testing is 6.12.99.git20091221-1, and that's ok too

so it left :
* glproto : extra version is 1.4.10 so we need to compile it from git I believe
* dri2proto : 2.1 in extra, same as above
* mesa: 7.6 in extra but 7.7 is released (today), so we need to wait for it to enter testing I guess
* libgl: 7.6 in extra but should become 7.7 with mesa
* ati-dri: same as above

That left us to compile the last five from git for now but soon only glproto and dri2proto?


Moving along beautifully eh! :)

[Xbehave]

xorg requirements are met by xorg-edgers (https://launchpad.net/~xorg-edgers/+archive/ppa) ppa:
libdrm = 2.4.17+git20091221
mesa = 7.7.0~git20091221
xserver-xorg video-ati =6.12.99+git20091222 (do you know which git revision? is needed because the standard karmic one is 20090929)

For the kernel I know 2.6.32 (.nothing) as provided here (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/) works fine (radeon.modeset=1 may be required), however 2.6.31/2.6.33-* should work fine as long as radeon.modeset=1 is specified.

If you want to compile from git this guide (http://turqee.tumblr.com/post/230394871/dri2-for-radeon-r600-700-chipsets-on-ubuntu-9-10) covers xorg and kernel, I played about and had mesa from git for a while but something went wrong on an update, so now I'm back, i think performance was slightly better with mesa 7.8 but that's speculative as i didn't do benchmarks (which IMO are often stupid for mesa because your feature set is changing).

[JeMaCheHi]

Hi there...
I'm new in this great forum and this is my first post. I'd been in ubuntu since 8.10 but I'm new in graphic acceleration cause I never needed. I've reading this thread, but my english isn't the best in the world and I can't understand everything... -.-'
My question is: I have installed karmic with an ATI Radeon X1600PRO (512MB). I tried to install the proprietary drivers but envy says that isn't compatible. I don't know if the open driver enables 3D acceleration. Am I in the correct thread?
So sorry if I asked stupid questions...
Thanks and greetings

[handy]

Apparently xf86-video-ati 6.12.99.git20091221-1 is fine.

kernel 2.6.32.2 is no good .31 & .33-rc1 are ok.

[Xbehave]

Hi there...
I'm new in this great forum and this is my first post. I'd been in ubuntu since 8.10 but I'm new in graphic acceleration cause I never needed. I've reading this thread, but my english isn't the best in the world and I can't understand everything... -.-'
My question is: I have installed karmic with an ATI Radeon X1600PRO (512MB). I tried to install the proprietary drivers but envy says that isn't compatible. I don't know if the open driver enables 3D acceleration. Am I in the correct thread?
So sorry if I asked stupid questions...
Thanks and greetings
ATI open drivers support some 3D acceleration but they are generally slower than envy drivers (I can run desktop effects but some are slow and i don't think you can do 3d gaming, but these may be due to my card being rubbish)
The open drivers are installed by default but can be a bit slow if the version installed is old.
The latest version is a bit tricky to get working and you may run into problems, but if you want it, you need to use this ppa (https://launchpad.net/~xorg-edgers/+archive/ppa) and enable KMS.

To enable KMS add radeon.modeset=1 to your kernel line in grub (you will need a recent kernel >= 2.6.31 (but not 2.6.32), the default one in 9.10 should be new enough), then check it is enabled after a reboot run

sudo cat /sys/module/radeon/parameters/modeset
1 means its working, 0 means it's not

to find out if you have DRI working run glxgears -info
it will return something like

GL_RENDERER = Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI2 #KMS is working
GL_RENDERER = Mesa DRI R300 (RS400 5975) 20090101 NO-TCL DRI #KMS is not working but you have some hardware acceleration
GL_RENDERER = Software rasterising #KMS is not working and you have no hardware acceleration

[handy]

Hi there...
I'm new in this great forum and this is my first post. I'd been in ubuntu since 8.10 but I'm new in graphic acceleration cause I never needed. I've reading this thread, but my english isn't the best in the world and I can't understand everything... -.-'
My question is: I have installed karmic with an ATI Radeon X1600PRO (512MB). I tried to install the proprietary drivers but envy says that isn't compatible. I don't know if the open driver enables 3D acceleration. Am I in the correct thread?
So sorry if I asked stupid questions...
Thanks and greetings

Welcome to the forum JeMaCheHi, I hope it serves you well. :)

In addition to what Xbehave said; in case you are unaware, your X1000 series is using the R520 core, which is usually referred to as the R500 (& sometimes X500). It may help you to know that when you look at something like the following table, which I think you will find quite encouraging:

http://wiki.x.org/wiki/RadeonFeature

Due to the speed of development of the open-source support for ATi GPUs in particular at the moment, if you do find that the 3D speed you are getting is not good enough, or it just won't work for your card; please be patient, as it won't be too long & it will be easy to set up, as well as the speed is (almost) consistently increasing every week. :)

The open-source ATi 2D has for months been vastly superior to the 2D offered by Catalyst. 3D will do the same in the coming months. For many of the ATi GPUs.

[JeMaCheHi]

I runned glxgears -info and it returned this:


GL_RENDERER = Mesa DRI R300 (RV530 71C2) 20090101 TCL
GL_VERSION = 1.5 Mesa 7.6
GL_VENDOR = DRI R300 Project

(I don't understand anything... -.-')
I've got kernel 2.6.31-9-rt as default cause I need it to use jackd :guitar:
Handy, I don't understand what must do with the R500 core... Sorry but I'm an ignorant
Oh, and thanks for the welcome

[Ubuntiac]

Ola JeMaCheHi!

If you're using Ubuntu... and JACK... and you're able to speak more than one language... and you're asking questions here politely... then you are *not* ignorant *or* stupid.

You're learning, just like everyone in the community. Be nice to yourself. One of the things that unites nearly every person here is that we're all enjoying learning more. I'm learning, like you, how to get open source 3d on my ATI card. I'll be so excited when I get there. I've been dreaming of this for years!

Anyway, just ask a lot of questions and help anyone who's learning what you know, and most importantly HAVE FUN! :)



Cheers

Ubuntuiac

[Ubuntiac]

Where do most people actually get the 2.6.33-rc1 kernel from, or is this the same as the 2.6.32.996 one in DRM-Next ppa?

I'm wondering if this might be the cause of my segfault as all the kernel options I'm starting are either 2.6.32 or 2.6.32.996...

[handy]

...
Handy, I don't understand what must do with the R500 core... Sorry but I'm an ignorant
Oh, and thanks for the welcome

Just know that, R500 core (http://en.wikipedia.org/wiki/Radeon_R520) is what you have, as you will see reference to various core series,particularly on technical sites like X.org.

Here is more info on the ATi Rxx core's:

http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units

The link I included in my previous post to you is a really good example, as you scroll down you will see all of the core numbers running from left to right, find the R500 column & then as you scroll down you will see what has been accomplished so far by the part of the X.org team that are working on the open-source ATi GPU driver support.

[handy]

Where do most people actually get the 2.6.33-rc1 kernel from, or is this the same as the 2.6.32.996 one in DRM-Next ppa?

I'm wondering if this might be the cause of my segfault as all the kernel options I'm starting are either 2.6.32 or 2.6.32.996...

Being an Arch user I access packages in a very different way than you do in Ubuntu.

You'll find your Ubuntu kernels here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

[Edit:] Are you aware of this post from Nerd King?:

http://ubuntuforums.org/showpost.php?p=8450155&

[handy]

I decided it's about time that I gave the open-source drivers another go, as I think they are now more than good enough for my needs, as I use a HD2600 Pro, which is based on the R600 core which is not particularly fast 3D wise when using the currently "stable" open-source support.

By using kernel26-2.6.33-rc1 & other recent versions of packages it is possible to get a worthwhile improvement in the 3D performance.

So I have just deleted the Catalyst packages on my Arch box, edited the pacman.conf to allow the upgrading of xorg-server after having had to keep it limited to ver 1.6 for Catalyst.

I also modified my xorg.conf in preparation for the xf86-video-ati (The radeon driver). I don't think I can do away with xorg.conf on my system yet.

I upgraded my system the Arch way, then started the installation - compilation of kernel26-2.6.33-rc1

It is a time consuming process requiring the downloading of both the .32 kernel source & the .33-rc1 patch source, (the downloading is the quick part) then .32 has to be patched to bring it up to .33-rc1 & then the compilation process which is certainly the most time consuming part of the process. Having used Arch for so long, I'm not used to having to wait like this. ;)

Hopefully my system has no problems with .33-rc1, & I can then move onto the next step of installing the other 7 (I think) packages, 5 of which will also need to be compiled, but they are all tiny in comparison to the kernel. :)

I'll post an update when I get a chance to move on...:-\"

[Edit:] I had to install the kernel .32 firmware before .33-rc1 would install, which it has done without problem thus far... as in it has rebooted. :)

[handy]

Following is a slightly modified version of what I posted in the Arch forum:


I've finally got around to following Perry's great guide (http://bbs.archlinux.org/viewtopic.php?id=79509&p=1) (many thanks Perry :)) in the OP of this thread, with the following results:

Hardware:
24" 2007 iMac
GPU: HD 2600 Pro

Packages:
kernel26-2.6.33-rc1
all installed in order re, threads OP, using mesa-full also.


I don't call HAL in the rc.conf DAEMON line; as I use the Worker dirutil & handle devices using commands from inside of Worker, hopefully HAL is only required if I wanted to do without an xorg.config? I actually have hotplugging turned off in xorg.conf.

Prior to beginning installation I had prepared my xorg.conf (see bottom of post) prior to the installation & removed Catalyst & utils, organised pacman.conf to now be able to upgrade the X.org stuff also.

After installation, I found that 2D performance was brilliant in colour, definition & refresh speed, but glxgears failed to work, spitting out an error.

So I turned on KMS in menu.lst as I had turned it off in the past, turning KMS on again certainly made some changes:

Now I had laggy 2D refresh & glxgears now worked.

After running glxgears multiple times each time after at least a restart of X, the speeds were slow as 150fps & once was into the 300fps, mostly around 230fps, but with quite some inconsistency in the speed of its performance per session.

Then I set KMS for early start. During the process there was an error that fbcon could not be found? I let it go considering to possibly be a bug due to the cutting edge nature of the packages.

After having set KMS to early start my glxgears speeds are now very consistent & somewhat higher, as follows:

2195 frames in 5.0 seconds = 438.920 FPS

The system in 2D is fine, .mp4 & such play perfectly (as only the open-source drivers can do :))

I get the following error, which the wiki says (if I understand it correctly) means that KMS is not working even though since I implemented the KMS early start, the performance of both 2D/3D have dramatically improved.



handy ~ $ dmesg | egrep "drm|radeon"
Command line: root=/dev/sda3 ro ##radeon.modeset=0 turn off KMS if slow display refresh problem
Kernel command line: root=/dev/sda3 ro ##radeon.modeset=0 turn off KMS if slow display refresh problem
Unknown boot option `##radeon.modeset=0': ignoring
[drm] Initialized drm 1.1.0 20060810
[drm] radeon default to kernel modesetting.
[drm] radeon kernel modesetting enabled.
radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
radeon 0000:01:00.0: setting latency timer to 64
[drm] radeon: Initializing kernel modesetting.
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL
radeon 0000:01:00.0: PCI INT A disabled
radeon: probe of 0000:01:00.0 failed with error -22


Dramatic may sound like a big word for such a small gain in glxgears (around 200fps) but that 200fps really made the 2D side better than it has ever been with catalyst, whereas before that 200fps it certainly was not.

I've posted some details below in the hope that someone will pick up something that I'm unaware of that could bring me some more 3D speed. In the past glxgears would run well over 3000fps on catalyst.

Not that I'm impatient ;) I'm absolutely stoked with what the dev' team has accomplished so far with ATi GPU support, & I have complete confidence that the open-source solution will blow the catalyst 3D performance away, as it already has done with the 2D. :D


Here is some more info:



handy ~ $ glxinfo |grep -i opengl
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.8-devel
OpenGL shading language version string: 1.20
OpenGL extensions:

I've pulled the errors out of xorg.0.log, the first one I'm sure is due to my recent editing of xorg.conf, the 2nd is also inconsequential with regard to the topic at hand:



(EE) Failed to load module "freetype" (module does not exist, 0)

(EE) Failed to load module "record" (module does not exist, 0)

(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM

(EE) RADEON(0): Acceleration initialization failed

Here is my roughly edited xorg.conf, sorry for the mess, its a work in progress:



#Section "ServerLayout"

## PS/2 Mouse not detected
## Serial Mouse not detected
# Identifier "Xorg Configured"
# Screen 0 "aticonfig-Screen[0]" 0 0
# InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "USB Mouse" "CorePointer"
#EndSection

#Section "Files"

## Additional fonts: Locale, Gimp, TTF...
## FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
## FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
## True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
## FontPath "/usr/share/fonts/Type1"
## RgbPath "/usr/share/X11/rgb"
# ModulePath "/usr/lib/xorg/modules"
# FontPath "/usr/share/fonts/misc:unscaled"
# FontPath "/usr/share/fonts/misc"
# FontPath "/usr/share/fonts/75dpi:unscaled"
# FontPath "/usr/share/fonts/75dpi"
# FontPath "/usr/share/fonts/100dpi:unscaled"
# FontPath "/usr/share/fonts/100dpi"
# FontPath "/usr/share/fonts/PEX"
# FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/fonts/ttf/western"
# FontPath "/usr/share/fonts/ttf/decoratives"
# FontPath "/usr/share/fonts/truetype"
# FontPath "/usr/share/fonts/truetype/openoffice"
# FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
# FontPath "/usr/share/fonts/latex-ttf-fonts"
# FontPath "/usr/share/fonts/defoma/CID"
# FontPath "/usr/share/fonts/defoma/TrueType"
#EndSection

Section "Module"

# Load "type1"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "freetype"
Load "record"
Load "drm" # this one was added for OPEN ATi driver support
EndSection

Section "ServerFlags"
Option "AutoAddDevices" "False" # this turns off hotplugging which needs HAL to work
Option "AllowMouseOpenFail" "true"
EndSection

#Section "InputDevice"
# Identifier "Keyboard0"
# Driver "keyboard"
# Option "CoreKeyboard"
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
## Option "XkbVariant" ""
#EndSection

#Section "InputDevice"
# Identifier "USB Mouse"
# Driver "mouse"
# Option "Device" "/dev/input/mice"
# Option "SendCoreEvents" "true"
# Option "Protocol" "IMPS/2"
# Option "ZAxisMapping" "4 5 6 7"
# Option "Buttons" "5"
#EndSection

#Section "Monitor"
# Identifier "aticonfig-Monitor[0]"
# Option "VendorName" "iMac-24" ## for open driver, may not be needed?
# Option "VendorName" "ATI Proprietary Driver"
# Option "ModelName" "Generic Autodetecting Monitor"
# Option "DPMS" "true"
#EndSection

Section "Device"
## Identifier "aticonfig-Device[0]" # ATi's closed driver
## Driver "fglrx" # ATi's closed driver
Identifier "iMacRadeon" # Handy's alias for OPEN ATi driver
Driver "radeon" # Handy's installed OPEN ATi driver - radeon NOT radeonhd
Option "DRI" "on"
Option "DynamicPM" "on" # Dynamic powersaving.
Option "ClockGating" "on" # Assisting option for powersaving.
Option "AccelMethod" "EXA" # EXA should fit most cases.
Option "EXAVSync" "on" # EXAVSync is explained above.
Option "RenderAccel" "on" # Optional. It should be enabled by default.
Option "AGPMode" "8" # Sets AGP speed may help speed up even non AGP systems
Option "ColorTiling" "on" #
## Option "AccelDFS" "on" #Optional. See the man page.
## Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.
## Option "AccelMethod" "EXA"
## Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.
## Option "ScalerWidth" "2048" # That should fix some very rare bugs.
BusID "PCI:1:0:0"
EndSection

#Section "Screen"
# Identifier "aticonfig-Screen[0]"
# Device "aticonfig-Device[0]"
# Monitor "aticonfig-Monitor[0]"
# DefaultDepth 24
# SubSection "Display"
# Viewport 0 0
# Depth 24
# EndSubSection
#EndSection

#Section "DRI"
# Group "video" # commented out for OPEN driver
# Mode 0666 # remove when using OPEN driver instructions, though may possibly be userful, time will tell?
#EndSection

[handy]

I have a DRM problem, which is pretty obvious to anyone who knows what they are doing, even me, once its pointed out. ;)

So I'm installing a different version of libdrm & building it all on top of that, which should be quicker now, because all the packages are in my cache at least.

[Ubuntiac]

ZOMG! I just noticed that without changing *anything* for the last couple of days, that I now seem to have compositing in Kwin! I think it must have been an update to Xorg-Edgers or something.

I missed it because I alternate between using a stable Karmic+FGLRX and an experimental Lucid+Radeon install and I assumed I was on Karmic because of the desktop effects. It all seems to work perfectly other than a rare odd patch of colour around some windows when they pop up.

All I've done is boot to the drm-next kernel (2.6.32.996) with Xorg-edgers PPA and no radeon.modeset done at all.

Nice!

[Xbehave]

ZOMG! I just noticed that without changing *anything* for the last couple of days, that I now seem to have compositing in Kwin! I think it must have been an update to Xorg-Edgers or something.
Are you using kde4.4 betas if so there was a bug in 4.4b1 that was fixed in 4.4b2 , it is impressive that radeon drivers now support desktop effects, but i think your change is a kde improvement.

handy, did you manage to get it working? your setup is so different to mine (hal + binary installs) that I can't really suggest any help other than the stuff that stands for ubuntu
1) test modesettings via sysfs to know if it's on
2) test xorg once you know KMS is setup, dri1 = KMS support, dri2 = KMS, software = radeon drivers messed up
3) If you know KMS is working on all kernels, try switch kernels when you run into an xorg bug just to make sure it's not kernel related.

[spoons]

How nicely do the open drivers play with WINE?

[handy]

handy, did you manage to get it working? your setup is so different to mine (hal + binary installs) that I can't really suggest any help other than the stuff that stands for ubuntu
1) test modesettings via sysfs to know if it's on
2) test xorg once you know KMS is setup, dri1 = KMS support, dri2 = KMS, software = radeon drivers messed up
3) If you know KMS is working on all kernels, try switch kernels when you run into an xorg bug just to make sure it's not kernel related.

From the feedback I'm getting on the Arch forum, it would seem like the problem is very likely the .33-rc kernel.

I set everything bar kernel .33-rc back to versions that were in testing or core repo's last night before I went to bed, & still had identical performance. So that kind of makes the .33-rc kernel look even more likely.

This morning I'll change to the kernel .32.1, which seems to be the best for the job at the moment & I'll build all the other packages from .git & see how it goes.

The amount of time that goes into organising this stuff when you have to compile (kernels especially) is why have been holding off from going down the cutting edge path. But I have the bit between my teeth now. :lolflag:
Really it isn't hard, it is just time consuming waiting for compilation. I'm glad I'm not using a 386! ](*,)

P.S. Something else I found out about last night that you have to include firmware with kernel .33-rc, "radeon_ucode" I added the firmware but it made no difference.

[handy]

How nicely do the open drivers play with WINE?

I can't speak for Ubuntu, but there are people who have been getting their 2D/3D working very well over on the Arch forum, say Wine is not working well, due the lib32-mesa-git to be upgraded, as they can only get software rasterizer currently when using Wine, though they have full hardware 3D when out of Wine.

I'm sure it won't take long to sort that one out. The above may only apply to people who are using cutting edge versions of packages, I really don't know for sure.

[Edit:]
Perhaps Nerd King or Xbehave, will be able to tell you what the story is re. Ubuntu, Wine & the OSS support for the ATi GPUs?

[handy]

With kernel26-2.6.32.2-1 & using no .git packages, only those from [testing] & the standard repo's, I'm still getting the following error (as expected, this kernel doesn't work properly with 3D, but the .32.1 kernel does):

OpenGL renderer string: Software Rasterizer

But my glxgears speeds are consistent & up around the following speed:

3388 frames in 5.0 seconds = 677.430 FPS

I think I'll hang where I am & wait for an improvement in the kernel that will hopefully open the door to decent 3D speeds for my machine.

As it is 2D is great for everything; the desktop & movies are vastly superior to catalyst. 3D is not really good enough to play World of Goo. But I can live without that for a while yet. :)

I could battle it out some more & get 2 or 3 times the 3D speed I am getting now; but really don't have a pressing need at the moment. I expect that the kernel will fix the problem for me inside a month, & I'm a patient person, usually... ;)

My foray into the cutting edge was educational, I have learned some more about my beloved Arch. I really like how I can totally mess it up, & then just spend the time undoing & modifying the mess in varieties of ways. Sometimes not undoing at all but making it even worse.

Then when things get really bad, (due to compiling strange kernels) you boot the Arch install disk, chroot, then /etc/rc.d/network restart, & then get in there & kick some package RRRs! lol

I've had a lot of fun over the last couple of days with this stuff. But I'm over it now. Bring it down from upstream I say, & let my system now be at peace again... lol

[Xbehave]

[Edit:]
Perhaps Nerd King or Xbehave, will be able to tell you what the story is re. Ubuntu, Wine & the OSS support for the ATi GPUs?
Don't do gaming here but this may help:
http://wiki.x.org/wiki/RadeonProgram


P.S. Something else I found out about last night that you have to include firmware with kernel .33-rc, "radeon_ucode" I added the firmware but it made no difference.
by default a kernel will not compile any firmware, this may be why just adding the firmware didn't help

[handy]

...
by default a kernel will not compile any firmware, this may be why just adding the firmware didn't help

In Arch you just have to install the firmware package for it to become part of & available to the system.

I'm thinking I might have another go with the 32.1 kernel. If I can't get the best results out of it, then I'll just wait for the kernel .33 to get its act together.

[Ubuntiac]

Has anyone tried the new .33-beta2 kernel with Radeon yet?

[handy]

Has anyone tried the new .33-beta2 kernel with Radeon yet?

I tried 33-rc1 yesterday, on Arch, it didn't work. Occasionally it works, it seems that there exists a kernel problem at this point.

32.1 seems to be the preferred kernel (most likely to work) with the Arch users at this point.

I'm currently in the process of recompiling it in the hope that I will get the best performance out of the open-source solution.

If I fail, I'll just wait for more kernel development & try again then.

[Ubuntiac]

Thanks Handy,

I was actually wondering about the second beta that was just released.

[handy]

Thanks Handy,

I was actually wondering about the second beta that was just released.

No word on the Arch threads as yet, they are probably sleeping off a day of over indulgence... :lolflag:

[Ubuntiac]

No rest for the wicked! None! ;)

[handy]

Thanks to the user aline over on the Arch forum, I think I now understand why my past 2 attempts at using the kernel26-vanilla-2.6.32.2, & modifying the PKGBUILD so it would download the source & a patch & build the .32.1 kernel, failed to boot.

After both attempts, the install went without error, but when I tried to boot, I was stopped directly after the GRUB menu with a file not found error.

So I was forced to boot with the Arch install CD, get a bash prompt, chroot, get network with /etc/rc.d/network restart then install the .32.2 kernel that is still in the Arch [testing] repo.

The reason for all of this time being wasted (twice!) was because I didn't go into the /boot/grub/menu.lst & change the name of the kernel from this:


kernel /boot/vmlinuz26 root=/dev/sda3 ro
initrd /boot/kernel26.img


To this:


kernel /boot/vmlinuz26-vanilla root=/dev/sda3 ro
initrd /kernel26-vanilla.img
.

Makes perfect sense once you know about it eh! <palm to forehead!>

So, I guess I will just have to do it a third time...

At least for the next attempt I won't have to compile the kernel, as I've kept the .pkg.tar.gz packages in my cache for the kernel & firmware.

I've also got the libdrm-git, mesa-full (which is a variety of .git packages in .pkg.tar.gz format, so if I don't stuff up somewhere along the line I could save many hours in the next install. (I think)

Fingers & toes crossed. ;)

[handy]

Some good news here on the kernel26-2.6.33:

http://www.phoronix.com/scan.php?page=news_item&px=NzgyMQ

More that is relevant to the .33 & beyond kernels - KMS Page-Flipping Ioctl:

http://www.phoronix.com/scan.php?page=news_item&px=NzY5OA

[shane2peru]

ok, this is like the ATI master thread! I have Radeon HD3100 ATI card, in my Toshiba Satellite laptop. I installed the proprietary driver trying to find some relief for this card. It overheats at the drop of a hat, and it isn't the ventilators, or fans, it has everything to do with ATI drivers. So my question is, I have proprietary drivers installed, and want to return to the open source drivers and try them. How can I do that safely, or semi-safely?

Shane

[Ubuntiac]

uninstall everything that has fglrx in the packagename and if you have a /etc/X11/xorg.conf file make sure driver "fglrx" is changed to driver "ati"

You may just beable to open restricted driver manager from the start menu and deactivate from there though.

[shane2peru]

ok, I got it. That is what I did. Got rid of everything fglx then installed libgl1-mesa stuff and radeonhd thing, and removed my xorg.conf file (it had ati stuff in it) and all works fine. I suppose I'm working the open source drivers now, and they have been greatly improved from when I first tried them. Thanks!

Shane

[Ubuntiac]

I suppose I'm working the open source drivers now, and they have been greatly improved from when I first tried them. Thanks!

You're welcome! (From someone who'd love to live in Peru one day!) Love the ogg video on your site. :)

[handy]

ok, I got it. That is what I did. Got rid of everything fglx then installed libgl1-mesa stuff and radeonhd thing, and removed my xorg.conf file (it had ati stuff in it) and all works fine. I suppose I'm working the open source drivers now, and they have been greatly improved from when I first tried them. Thanks!

Shane

You could try using the radeon (xf86-video-ati) driver as opposed to the radeonhd, as it is usually the best choice, it is the one that is getting most of the development work done on it.

Also power-management is being worked on & from memory will begin to be incorporated in kernel .33. There is actually a patch available that some are using.

[Edit:] I went back some pages & found the link that discusses the power-management situation some:

http://www.phoronix.com/scan.php?page=news_item&px=NzcyNw

[handy]

I've just done a daily upgrade on Arch, (not using the [testing] repo) & due to the versions of the kernel & other packages that are now in the [core] & [extra] repo's I now have the best results ever from using the open-source packages, & ALL from stable packages like kernel26-2.6.32.2-2:

handy ~ $ glxinfo |grep -i opengl
IRQ's not enabled, falling back to busy waits: 2 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV630 9583) 20090101 TCL
OpenGL version string: 1.5 Mesa 7.7
OpenGL extensions:
handy ~ $ glxgears
IRQ's not enabled, falling back to busy waits: 2 0
6757 frames in 5.0 seconds = 1351.209 FPS
6755 frames in 5.0 seconds = 1350.827 FPS
6754 frames in 5.0 seconds = 1350.612 FPS
6754 frames in 5.0 seconds = 1350.800 FPS
6758 frames in 5.0 seconds = 1351.450 FPS


The GPU 3D hardware is working & my glxgears are over twice as fast as the best I had been able to manage previously (OpenGL renderer string: Software Rasterizer).

KMS is turned off by default but it easy to turn on, which I have done.

To test some new features (for example: irq support = tear free opengl) you have to update some packages & go down the .git path.

The 3D performance is just going to keep on improving as the kernel, mesa & the other associated packages continue to be developed.

Today (well yesterday actually) is a great day for open-source ATi GPU 3D support; it is happening & it has gone mainstream. You don't have to get into the testing repo's & .git, it is starting to be easily available for general users. Unfortunately not all radeon core's (http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units) are supported yet, I think that the R500 is, I know that the R600 & R700 are.

P.S. World of Goo now works great. :)

A great end to the year for the team that has been working so hard on this for us for so many months.

My hearty congratulations & gratitude to them all.=D>

[handy]

Here is a little more on the kernel26-2.6.32.2 & the KMS in particular:

http://www.archlinux.org/news/477/

[Nerd King]

Just tested out 2.6.33-rc2 and 2D speed is flying obviously. 3D compiz is good, 3D in wine is a little buggy compared to 32 as one would expect of a rc, but speed does seem to be faster, so presuming that the bugs will be fixed, 33 should be a nice release.

[handy]

There was a nice xmas (22-12-09) present from AMD, they released 362 pages; the Evergreen shader documents.

This info' is required for the open-source drivers to be able to give great 2D/3D for the current series of ATi GPUs.

Great news again for the ATi open-source driver scene:

http://www.phoronix.com/scan.php?page=news_item&px=NzgzMg

Because as it stands, next to nothing has been able to be done for the Evergreen series of GPUs:

http://wiki.x.org/wiki/RadeonFeature

& now it can be. :)

[Nerd King]

Coolness :) I'm starting to like AMD.

[Ubuntiac]

Coolness :) I'm starting to like AMD.

After getting desktop effects running with an all open-source graphics stack more easily than the proprietry drivers on my Nvidia card... I'm loving AMD! I wish more FOSS peeps would start supporting them. They made a crap proprietry driver, but dang, if they're not treating the community right, now.

[phredbull]

Well unfortunately, I'm using a laptop w/a Radeon 7500 card. I'm using drivers from xorg/edgers and 2.6.32 kernel. I had previously tweaked my xorg.conf settings, but have since trashed it. (Is it still necessary to generate an xorg.conf and to tweak it?)

Since updating my kernel, Open Arena is now playable, so that's an obvious improvement in my 3d performance, but in Firefox, scrolling is dragging. I feel like 2d performance in Firefox is better when I boot into XP.

I was hoping that as the drivers matured, all that would be needed is the correct kernel, and drivers themselves. Am I missing something?

[handy]

Well unfortunately, I'm using a laptop w/a Radeon 7500 card. I'm using drivers from xorg/edgers and 2.6.32 kernel. I had previously tweaked my xorg.conf settings, but have since trashed it. (Is it still necessary to generate an xorg.conf and to tweak it?)

I still have to use an abbreviated xorg.conf. It seems to depend on the hardware you are using.



Since updating my kernel, Open Arena is now playable, so that's an obvious improvement in my 3d performance, but in Firefox, scrolling is dragging. I feel like 2d performance in Firefox is better when I boot into XP.

I find the open-source 2D performance to be really snappy, miles ahead of what I experience when I use Catalyst.

As far as comparisons with XP are concerned, I can't help you, as I haven't used it for over 4 years. :)



I was hoping that as the drivers matured, all that would be needed is the correct kernel, and drivers themselves. Am I missing something?

I think the only thing that you are missing, is the understanding that the open-source drivers are far from mature. They are still in their infancy, & will continue to improve with each kernel, mesa & associated packages, release. (With the occasional regression I'm sure. :))

[Edit:] I've added my xorg.conf in the hope it may save you some time:



Section "Module"
# Load "type1"
Load "ddc"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap"
Load "freetype"
Load "record"
Load "drm" # this one was added for OPEN ATi driver support
EndSection

Section "Device"
## Identifier "aticonfig-Device[0]" # ATi's closed driver
## Driver "fglrx" # ATi's closed driver
Identifier "iMacRadeon" # Handy's alias for OPEN ATi driver
Driver "radeon" # Handy's installed OPEN ATi driver - radeon NOT radeonhd
Option "DRI" "on"
Option "DynamicPM" "on" # Dynamic powersaving.
Option "ClockGating" "on" # Assisting option for powersaving.
Option "AccelMethod" "EXA" # EXA should fit most cases.
Option "EXAVSync" "on" # EXAVSync is explained above.
Option "RenderAccel" "on" # Optional. It should be enabled by default.
Option "AGPMode" "8" # Sets AGP speed may help speed up even non AGP systems
Option "ColorTiling" "on" #
## Option "AccelDFS" "on" #Optional. See the man page.
## Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.
## Option "AccelMethod" "EXA"
## Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.
## Option "ScalerWidth" "2048" # That should fix some very rare bugs.
BusID "PCI:1:0:0"
EndSection

The layout tabbing is a bit messy, but that's easily sorted out. ;)

[handy]

Just out of interest, I started running the HAL daemon again (after well over a year of not) & renamed my xorg.conf.bak & tested & I found I don't currently need to use an xorg.conf.

I didn't include it in the previous post's xorg.conf but I have had to use the following firstly due to a bug, (which is now long gone) & secondly because I haven't been using HAL:


Section "ServerFlags"
Option "AutoAddDevices" "False" # this turns off hotplugging which needs HAL to work
Option "AllowMouseOpenFail" "true"
EndSection

Anyhow, I'll play with HAL again for a while & see how we get on these days... ;)

[markbuntu]

hal has been deprecated in favor of udev so don't bother.

[Techsnap]

2.6.32 + Mesa 7.7 has given GREAT results with my HD4850, I'm very impressed, I'm getting usable 3D which is good enough for kwin compositing and games.

I've tried it on Arch, but Slackware -current doesn't have Mesa 7.7 yet, so I'll either wait for it to be updated in the package tree or compile it.

[Frak]

Thank you AMD for being cool and stuff.