https://bugs.freedesktop.org/show_bug.cgi?id=56865

Andreas Boll andreas.boll.dev@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Attachment #69689|text/plain |image/png mime type| |

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #2 from Marek Olšák maraeo@gmail.com --- Did you turn on MLAA? If yes, turn it off. It can blur your desktop too.

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #4 from ka.nick@mail.ru --- Created attachment 69758 --> https://bugs.freedesktop.org/attachment.cgi?id=69758&action=edit Glxinfo output

https://bugs.freedesktop.org/show_bug.cgi?id=56865

ka.nick@mail.ru changed:

What |Removed |Added ---------------------------------------------------------------------------- Attachment #69758|application/octet-stream |text/plain mime type| |

https://bugs.freedesktop.org/show_bug.cgi?id=56865

Alex Deucher agd5f@yahoo.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTABUG Component|Drivers/DRI/Radeon |Drivers/Gallium/r600

--- Comment #7 from Alex Deucher agd5f@yahoo.com --- I suspect you weren't getting MLAA under mesa 8.x since IIRC the way drirc options were handled by gallium drivers changed between 8.x and 9.x.

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #9 from Michel Dänzer michel@daenzer.net --- (In reply to comment #8)

MLAA worked for me in 8.0 and it seems to be a regression in 9.0.

Comment #7 explained that MLAA may not actually have been enabled with 8.0.

(How) Did you verify that it was?

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #11 from ka.nick@mail.ru --- (In reply to comment #9)

MLAA may not actually have been enabled with 8.0. (How) Did you verify that it was?

I did not, but the first impression was the font rendering has changed a little bit, but I'm not 100% sure. Probably it did not. At least I can say "MLAA" never appeared in Xorg log, but I'm not sure if it had to... I may perform a dumb check if it is important: compile 8.0.4 back then switch MLAA on and off via driconf to see if there is any real difference... or you may suggest a smarter way...

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #13 from Andreas Boll andreas.boll.dev@gmail.com --- You could attach your driconf. Then we could see if MLAA was enabled in mesa-8.0.4 or not.

P.S: Your Evergreen card uses the r600g (gallium) driver and not radeon classic.

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #14 from ka.nick@mail.ru --- Created attachment 69769 --> https://bugs.freedesktop.org/attachment.cgi?id=69769&action=edit Current drirc configuration suitable for mesa 9.0

Until today both pp_jimenezmlaa and pp_jimenezmlaa_color were set to 8

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #16 from ka.nick@mail.ru --- (In reply to comment #13)

You could attach your driconf. Then we could see if MLAA was enabled in mesa-8.0.4 or not.

This discussion has shown me that I was naive enough to think that things would work being switched on and that it's not always true)))

So if you guys are interested in getting more info, I'll do further experiments. In this case I'd like to know if there are any reliable means to make sure MLAA is really working or not (besides blur and 300x slowdown, of course. This was quite obvious) to give you a proper feedback. If you got enough, I'll experiment on my own to find out what is more suitable for me for the moment not involving you anymore - I got enough info. Now I got mesa 9 working more or less and you are aware that MLAA is not working properly in my case. Anyways, thank you for your help with the case as well as for you efforts in keeping improving Linux graphics.

P.S: Your Evergreen card uses the r600g (gallium) driver and not radeon classic.

I'm aware that classic drivers were removed in favor of Gallium. Thank you.

https://bugs.freedesktop.org/show_bug.cgi?id=56865

--- Comment #18 from ka.nick@mail.ru --- (In reply to comment #17)

I suspect that it works as intended though it's not what one might expect comparing to similar options in proprietary drivers.

I think you're completely right. In my case the issue was provoked by two things: first, the program I use (GTK driconf o.9.1) suggests MLAA to be set to 8 as default value (however, resets it to 0 by default), and second, that it did not actually work for me in mesa 8.0. So I was misled a little bit after I installed mesa 9...

As far as I understand, expected usage of MLAA with Mesa is to enable it only for the applications where you want it (games etc) with either app-specific drirc settings or environment variables.

It is probably so. A **huge** problem for me is a common lack of documentation. I'm okay with English and not too lazy to read but I could hardly find what to read, though. I mean - relevant while not obsolete. Things usually work in default configuration, which may not be optimal for some cases, and if I want to do something about it - this is where troubles begin - for me and maybe for developers who have to answer my sometimes stupid questions. All this video stuff looks so complicated and chaotic for me due to lack of documentation... I even did not comprehend if mesa is commonly responsible only for 3D rendering how comes erroneously enabled MLAA blurs fonts, too. Fonts currently are rendered by DDX driver, aren't they?

So I don't think it's a bug, though perhaps it would be nice to make Mesa behave more like other drivers.

Or at least, make things documented somehow. Currently the tuning knobs are spread across three areas: drirc (which is created somehow, or not, often beyond the user control); environment variables (hardly documented), Xorg.conf. Oh yes, there is fourth: USE flags/.configure options. A little bit to complicated...

Just the same, thank you guys for what you do.

https://bugs.freedesktop.org/show_bug.cgi?id=56865

GitLab Migration User gitlab-migration@fdo.invalid changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |MOVED

--- Comment #20 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/425.