If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The watermark problem. AMD is still figuring out how this can be fixed.

Well, I just installed the 8.39.4 driver on Ubuntu using this script, and it's working without any problems like annoying logos. When I ran the script, it said something like "brutally patched to remove the logo", well anyway - it works, and now even videos are played correctly in Ubuntu without inverted colors and such things

who knows, maybe somebody slipped a beta version instead of a normal one.

seeing a new fglrx in the middle of the month is really odd =]

I believe I called it: "Brown Paper Bag Version"...

<*sigh*> I'm so glad I'm mostly NVidia or old DRI driver based now. I've only got a smattering of the fglrx driven hardware now, and it's more for testing purposes for LGP work, etc.

Keep in mind- this is really due to their NOT throwing much of any resources at this up to this point. As it stands, they've got open req's for about a half dozen or more developers for the Shanghai, Toronto, Orlando AND Marlborough offices for Linux developers for OpenGL ES 1.1/2.X and OpenGL 2.X driver developers. Not enough, in comparison, to what they really need, but it IS a start in the right direction...IF they can find people to fill the slots. I know I'm not going to be interested for some time to come (As I'm QUITE busy with other consulting jobs and I have little desire to relo to any of those locations save maybe Orlando...)

well, any doubt about this fake monthly release schedule is removed. The lack of testing of course was already obvious, this simply confirms that their methods are flawed. But this type of error is really funny, almost comical.

At some point hopefully they will realize that this nonsense of scheduled monthly releases is just an invitation to further error and inefficient use of resources, and go back to a more sane model, like: release a beta, get feedback, fix problems, then release final when it's solid. I realize this is a radical notion in software development, but why not give it a try, be on the cutting edge of software engineering, pioneer new and untested methods such as the above.... obviously someone in charge at ATI Linux fglrx driver development must be the very epitomy of the pointy headed boss making bad decisions for bad reasons, Dilbert style.

Anyway, I definitely appreciate the tone of these reviews and articles, at least now it's clear right away that problems exist, so I have to give phoronix credit for that, I get the news I need in the way I need it, so thanks.