Announcement

Collapse
No announcement yet.

AMD Catalyst 13.3 Beta 3 Available For Linux Users

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Changelog

    Pleasantly surprised to see a changelog!
    I hope it is not just a one-time thing only!
    I hope they continue with it!

    Comment


    • #17
      Originally posted by brent View Post
      I haven't used fglrx in a few months. Is the 2D performance still as bad as it used to be?
      I believe it was 13.1, that fixed some 2d problem for me.

      Now the screen, in Fire fox is as on windows. No flickering.
      Smooth.
      Scrolling a page, no problem. Not anymore......
      Before I only had to move the mouse to know if I was on Linux.
      Now I need to look at the bottom or top of my screen to tell which os I use.

      hd 5750 with phenom II x4 3.2.

      Although I am very happy about this it took them long enough.

      How poor is that code, that on my specs, a webbrower is an issue.

      I hope I sound cynical, but I try to look forward.

      Amd is improving their drivers.

      On team fortress 2 it has improved to a point I need a benchmark to tell if there is a difference between Linux and w7.

      I once did made mods, maps for some other game, the driver problem with SS3, looks obvious to me.
      A problem with semi transparent textures. Textures with alpha mask. grass, leafs on trees, blood splatter.

      alt + enter twice at start screen, solves the flickering problem for me.
      I am currently not running beta drivers.

      Comment


      • #18
        I dont know how much faster your card is but with the autodetected SS3 settings for my HD 5670 the game is much below 25 fps when many enemies are on the screen. Must be something weird going on that slows the game down that much.

        Comment


        • #19
          hang on shutdown

          x crashs again on shutdown with 13.3 on hybrid system (intel/amd gpu) cs condition zero low fps (i played with intel hd 3000 without problems) is more the same, amd canīt do a working or a good perfomance driver for linux or windows. the engenniers from amd are completely stupid or incompetent, i really nedd to sell my laptop i buy one with only intel gpu

          Comment


          • #20
            Originally posted by rikkinho View Post
            x crashs again on shutdown with 13.3 on hybrid system (intel/amd gpu) cs condition zero low fps (i played with intel hd 3000 without problems) is more the same, amd canīt do a working or a good perfomance driver for linux or windows. the engenniers from amd are completely stupid or incompetent, i really nedd to sell my laptop i buy one with only intel gpu
            +1... BACKLIGHT ADJUSTMENT STILL BROKEN ON MY LAPTOP. Last working version was 13.1. Yes I've reported. Yes I've tested every beta since.

            Honestly I'm just waiting for Haswell and I'll never touch AMD graphics again in my life. Glad I've always stayed with nvidia on my desktop machine too.

            Comment


            • #21
              I have a question, what's difference between driver that support kernel version x.y and driver that patched to support kernel version x.y?

              Comment


              • #22
                Originally posted by Shabahang View Post
                I have a question, what's difference between driver that support kernel version x.y and driver that patched to support kernel version x.y?
                A patch only changes the glue code to match the kernel driver API.
                If AMD releases a driver which supports a new kernel release they can, in principle,
                make further changes to the driver code to optimise it for the new kernel.

                Comment


                • #23
                  You live in a fully unrealistic world. The fglrx kernel module is definitely not "optimized" for a new kernel, only build fixes have been applied, thats common practice. In this case you can look at the fix from AMD:

                  http://kanotix.com/files/fix/fglrx.w...8-support.diff

                  And what Debian used:

                  http://kanotix.com/files/fix/fglrx.w...linux-3.7.diff
                  http://kanotix.com/files/fix/fglrx.w...linux-3.8.diff

                  What you see that it is 1:1 the same, just an extra tiny modification thats not needed for Debian because the module build is done differently without that script. That code is standard, nothing that you have to think of long time.

                  Comment


                  • #24
                    Originally posted by Kano View Post
                    You live in a fully unrealistic world. The fglrx kernel module is definitely not "optimized" for a new kernel ...
                    I didn't say that.

                    Comment


                    • #25
                      Originally posted by n3wu53r View Post
                      Correction: Serious Sam 3 is not a Valve game, nor does it use the Source engine. The game is developed by Croteam and uses their in-house engine.
                      Team Fortress 2 is from Valve and does use the source engine.
                      +1
                      Michael, please fix your article!

                      Comment


                      • #26
                        Still doing it wrong.

                        Originally posted by mark45 View Post
                        Linux 3.7 & 3.8 now supported - what does it take to support a new Linux kernel? I mean Linux is backwards compatible, what's the deal exactly?
                        LOL - I had the previous driver on my laptop and when I installed the 3.8.4 kernel, dkms failed during build and said "Unsupported kernel". AMD your still doing it wrong.

                        On the upside this fglrx driver works

                        Comment


                        • #27
                          2D KDE Performance

                          For anyone that has 2D problems with fglrx-catalyst at KDE 4.X environment try using Raster as 2D rendering mode... For me it showed great difference than native Xrender!
                          System Settings -> Desktop effects -> Advanced Tab -> Qt Graphic System that's for KDE 4.10 and 4.9 I think, for older versions it was a separate app in the system settings you had to install manually, Qt 2D something it was called!
                          Also at KDE 4.10 openGL ES 2 interfaces work so use them for Kwin...

                          Comment


                          • #28
                            Originally posted by Kano View Post
                            Now to Serious Sam 3, there is absolutely no working fix, the lastest public beta from SS3 shows the menu correct, but the first logo is with artefacts. When you don't use gfxRestart() while the menu is shown (or via pressing Alt+Enter twice) then serveral textures like trees flicker in the level you start then.
                            The bug fixed in Catalyst 13.3 Beta 3 was:

                            [370253]: Serious Sam 3 - Color of Objects turning into be red when enabling separate shader object

                            It sounds as if you are seeing separate issues. I do agree though that it is disappointing that it's not working right.

                            Comment

                            Working...
                            X