Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • Besides both vaapi and classic vdpau (at least with mpv) works worse then vdpau with NV_vdpau_interop.
    Last edited by dungeon; 24 January 2015, 06:57 AM.

    Comment


    • @oibaf

      After libvdpau update vdpauinfo. That matches usally all vdpau changes.

      Comment


      • Originally posted by oibaf View Post
        I prefer avoiding adding patches that make the packages diverging from upstream unless really necessary. Best you should ask on the bug about the status of the patch.
        OK, thank you.

        Comment


        • Originally posted by oibaf View Post
          I prefer avoiding adding patches that make the packages diverging from upstream unless really necessary. Best you should ask on the bug about the status of the patch.
          Isn't a broken vdpau+vaapi necessary enough?
          ## VGA ##
          AMD: X1950XTX, HD3870, HD5870
          Intel: GMA45, HD3000 (Core i5 2500K)

          Comment


          • Hi! I've noticed LLVM 3.6 finally here. Which is great news for AMD GPUs users like me.

            However it looks like if you've did something wrong. After perfrorming upgrade I'm getting errors like this:
            cannot open file /usr/lib/clc/[name-of-my-GPU].bc - no such file or directory.

            It appears that now package libclc-r600 from your repo only contains .bc files for old VLIW based GPUs but totally lacks any .bc files for GCN-based GPUs. As far as I understand now I have all code generation for my GCN GPU screwed, right? Am I missing something? Or is it some bug?

            Comment


            • Originally posted by darkbasic View Post
              Isn't a broken vdpau+vaapi necessary enough?
              Since this is broken for everyone, not only for this PPA, it should be applied upstream so that everyone could benefit .

              Comment


              • Originally posted by SystemCrasher View Post
                Hi! I've noticed LLVM 3.6 finally here. Which is great news for AMD GPUs users like me.

                However it looks like if you've did something wrong. After perfrorming upgrade I'm getting errors like this:
                cannot open file /usr/lib/clc/[name-of-my-GPU].bc - no such file or directory.

                It appears that now package libclc-r600 from your repo only contains .bc files for old VLIW based GPUs but totally lacks any .bc files for GCN-based GPUs. As far as I understand now I have all code generation for my GCN GPU screwed, right? Am I missing something? Or is it some bug?
                Thanks for reporting, it should be fixed now .

                Comment


                • Guys is someone experiencing low fps in Dota2 settings?

                  I'm building my own Mesa, ddx, xserver and drm but my config is based on oibaf repository, a little bit tuned because I only need radeonSI.

                  I can't figure out why in settings and menus it runs at about 10FPS while when I start a match frames jump to 30FPS (luckly).

                  I'm sure back in November I can run at about 60FPS in settings (but lower than now in game, so it's still an improvement).

                  Comment


                  • Originally posted by lorenzoz View Post
                    Guys is someone experiencing low fps in Dota2 settings?

                    I'm building my own Mesa, ddx, xserver and drm but my config is based on oibaf repository, a little bit tuned because I only need radeonSI.

                    I can't figure out why in settings and menus it runs at about 10FPS while when I start a match frames jump to 30FPS (luckly).

                    I'm sure back in November I can run at about 60FPS in settings (but lower than now in game, so it's still an improvement).
                    Are you sure the hardware acceleration is enabled in your system? Run this command, if you see "VMware" then you are running the software renderer:
                    Code:
                    $ glxinfo | grep render
                    If not, I think you should submit a bug report.
                    IIRC, Mesa 10.5 had a performance problem, but I can't remember more info...

                    Comment


                    • Originally posted by asdfblah View Post
                      Are you sure the hardware acceleration is enabled in your system? Run this command, if you see "VMware" then you are running the software renderer:
                      Code:
                      $ glxinfo | grep render
                      If not, I think you should submit a bug report.
                      IIRC, Mesa 10.5 had a performance problem, but I can't remember more info...
                      Sure I'm running on Gallium.
                      Code:
                      $ glxinfo | grep render
                      direct rendering: Yes
                      ...
                      OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN
                      ...
                      I've already opened a bug but I want to be sure it's not my fault in configuring Mesa.

                      Comment

                      Working...
                      X