New AMD Catalyst Beta Supports Linux 3.8, TF2 Fixes

[Gps4l]

I'm still confused:

Is this really a new Cat 13.3 beta3 binary with new bugfixes (compared to 13.3b3 from mid March?).
Hard to believe...

I do not see any difference. But that does not mean allot.

[Gps4l]

May it be possible that you run 64 bit Linux and have used the option to create a package for your distro in the installer?
I had a similar problem on Slackware 64 and found that the driver installs 32 bit compatibility libraries only if you install directly, without creating a package.

Slackware, the mommy of my distro.

I tried to build an rpm, but could not find it, so I gave up, and did it directly.

There is something weird though, I have mesa and mesa 32 bit installed.
Today also install wine 32bit.

Still glxinfo says direct rendering is not enabled.

[entropy]

I'm still confused:

Is this really a new Cat 13.3 beta3 binary with new bugfixes (compared to 13.3b3 from mid March?).
Hard to believe...

[Vim_User]

May it be possible that you run 64 bit Linux and have used the option to create a package for your distro in the installer?
I had a similar problem on Slackware 64 and found that the driver installs 32 bit compatibility libraries only if you install directly, without creating a package.

[Gps4l]

I today installed latest beta. I was able to solve the flash issue, and the screen tearing.

The flash issue was solved with checking a box in the system setting ( or is it kde ? )

Disable desktop effects when an application runs in full screen.

Enable V sync in amd controll center solved the tearing.

I do some to have a new problem though.

After allot of searching and installing about every 32bit mesa lib I could find, steam still complains.

The output of glxinfo proofs steam right.
I opened a topic on openSUSE forum about this, hope they can help.

name of display: :0
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
display: :0  screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: ATI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:

[ayandon]

If you going to play games - it's better to install most newer driver from web-site instead of old builds available in repository. Catalyst 13.1 or Catalyst 13.3 Beta: http://support.amd.com/us/gpudownloa...eon_linux.aspx
http://wiki.cchtml.com/index.php/Ubu...allation_Guide

Thanks for the guides.
Beta or Stable ?

[RussianNeuroMancer]

Which "Addition Driver" should I installed ?

If you going to play games - it's better to install most newer driver from web-site instead of old builds available in repository. Catalyst 13.1 or Catalyst 13.3 Beta: http://support.amd.com/us/gpudownloa...eon_linux.aspx

http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide

[ayandon]

Which "Addition Driver" should I installed ?

I have recently installed a AMD/ATi HD 6670 Graphics card for my 2nd PC.
I am using Ubuntu 12.4 LTS and Steam.


Which "Addition Driver" should I installed ?
It has lots of ATI related items without any clear version information

[Decebal]

Support tactics

Ahh, you mean a feel-good platitude disconnected from reality. I guess we could do that but it's not the way we like to operate. Besides, I would rather use a script for mindless responses... when we have extra $$ to spend we try to spend it on engineering folks.

>> I suppose it's bash or some other linux shell... (one could do it under windows but surely would need a steady hand) ... it's great it just works on a console, no fancy graphics here sir - no problems !

The point is that the developers do *not* have time to look at every bug individually in real time. That's why we don't tell people that we will.

>> Come on, we all know (well, maybe not quite all...) it's not like watching a movie... real time is for kernels, not humans

The devs look for clusters of problems indicating areas that need some urgent attention, and patterns which might suggest possible solutions. You'll find this is the case at every vendor although the degree may vary.

>> This is reminding me of my support days... when fetching 20 or about there e-mails in the morning and looking quickly through them to see what was in the day for me. Most of them where quick fixing problems with 2-3, sometimes maybe more 'heavy' ones. So, to avoid a pile up never stop growing problems, I allocated 2-3 hours for fixing the easier ones and after that took my time to solve the big issues. Of course, it was routine to get calls from the 'owners' of the big issues asking to fix their issues right there right then. I got used to be yelled at. But none the less, I followed my tactics because otherwise the pile would simply grow and grow and I would get 20*N calls or about there from really pissed up guys. Well, from what I can observe, your team is in the process of building a large pile, so something is wrong... I suppose your problems are way more complicated but maybe, just maybe, it would be a better idea to fix the little and more mundane problems first, just to make those big mouths that are in the numbers happy (us, the minions who happened to buy AMD hw). Then, your guys could go on and be stellar and write patches that fix multiple issues simultaneous, etc... or even greater things. Again, I suppose in case of another vendor this degree is varying toward my approach since the mouths of their customer aren't so vocal and so in numbers...

[Gps4l]

My guess is you got a Mesa/DRM update through YaST. I think Catalyst installs its own version of one of the libraries, and as that file was overwritten by the YaST update, the installation program couldn't find its own.
Next time you have this issue, as someone else suggested, delete the Xorg.conf file, then reinstall the same Catalyst version that you had already installed to get the library back. Then uninstall and upgrade as usual.
BTW I usually install Catalyst from a tty, with Xorg shutdown (init 3).

I used to do it that way (init 3) Maybe I should still do it that way. ( at least for the beta drivers )

I like your idea about deleting xorg and then re install the same catalyst version. That probably would have solved my problem.

I am currently not very happy, but filed a bug at the amd dev forums.

After install of opensuse, I had no screen tearing ( with firefox on forums, when scrolling a page ) and flash vid full screen, were 100% fluently.

After install of the catalyst 13.1 though, the screen tearing is back, and flash vids freeze for a sec, quit frequently.
( exactly like with the 13.2 beta 3 )