The Cost Of ATI Kernel Mode-Setting On Fedora 12

[AdamW]

ufaogros: they never said it was news. They said they were benchmarking it.

Phoronix: looking whether you get the graphical boot or progress bar is not the perfect test for KMS, as it also depends on Plymouth being able to find the graphical splash. If KMS is enabled but Plymouth has some problem displaying the graphical splash, it'll fall back to the progress bar but *at native resolution*. The resolution's the key - if you see boot at native resolution, either graphical splash or progress bar, KMS is enabled. If you see boot as the progress bar at console resolution (720x400, the resolution used for POST and DOS and stuff like that), KMS is disabled.

[hybridr6]

Hmm yet another fact finding failure, we do ship r600 with kms by default.

3D isn't but thats easy to get working.

Ok good, thought I was the only one that noticed KMS was on by default...

[lordmozilla]

just a note :

The line for KMS FC12 is red for the entire article. Then suddenly when you only have 2 OSs (FC12 KMS and FC12 UMS) the OS that has been the red line for the whole article changes...

Makes it look confusing.

[logic]

RS690M (ie. onboard Radeon X1200-series) is still totally unusable with KMS as shipped with Fedora, unfortunately. Terrible artifacts start showing up as soon as GDM makes an appearance, and it degrades from there until the system is rebooted, or the desktop locks up and has to be kicked over the network.

[bugmenot]

What is the actual *reason* that it is slower?

Will color tiling be enabled with an update?

Thanks devs, you are doing an awesome job by the way.

[blindfrog]

Use latets packages F12 from koji and you see that lots of those issues are already fixed and they will end up as updates in time. KDE4.3.3 works now perfectly with kms on 4850 (kwin effects on) )) no more glitches also ut2k4 and nexuiz works great now. Just today updated latest xorg-x11-drv-ati package and got a nice performance bump.

It's amazing how quickly this stuff improves

[Kano]

Well you will see that you need video decode accelleration

[rvdboom]

If you use a file that needs 100% CPU just to be decoded, you won't see the difference between the different graphic paths, will you?

[ufaogros]

This isn't news. I have filled bugs against this issue (https://bugzilla.redhat.com/show_bug.cgi?id=533244 and https://bugzilla.redhat.com/show_bug.cgi?id=466695, to mention some). I always start with no modeset because the performance hit is absurd.

[Kano]

Well H264 with 33% is very low bitrate, i would not even call that a needed test. Use something that really hits 100%.