Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • Originally posted by artivision View Post
    Can you build Mesa with the D3D9 state tracker? It will be appreciated be many.
    If someone could donate a patch that would be a huge step forward.

    Comment


    • More updates

      You may have noticed I added mesa, libdrm and libclc packages also for Ubuntu 14.10/utopic in the PPA.

      Also, I looked into adding to mesa package the Gallium D3D9 state tracker (gallium-nine). It works fine, however since it has many changes, merging this git tree into mesa master breaks frequently (as of this writing it still has merge conflicts) and I cannot add it in the main PPA which is automatically updated twice a day. So, I set up a test PPA where you can find a mesa snapshot including it here.

      Comment


      • Originally posted by oibaf View Post
        You may have noticed I added mesa, libdrm and libclc packages also for Ubuntu 14.10/utopic in the PPA.

        Also, I looked into adding to mesa package the Gallium D3D9 state tracker (gallium-nine). It works fine, however since it has many changes, merging this git tree into mesa master breaks frequently (as of this writing it still has merge conflicts) and I cannot add it in the main PPA which is automatically updated twice a day. So, I set up a test PPA where you can find a mesa snapshot including it here.
        Note: avoid leaving the test PPA enabled since I use it for various stuff that may break things.

        Comment


        • Right -- time to follow up.

          I ended up reverting to the stock Ubuntu kernel (3.13.0-32-generic) and keeping the oibaf packages from a few days ago (10.3~git1407291930) frozen. I'm pleased to report that things have been perfectly stable for me with this setup so far, knocking on wood. This leads me to suspect that my problems came from the DRI driver in the updated kernel, and not Mesa.

          As an added bonus, the rendering glitches in Civilization 5 are gone -- thanks to a recent patch in Mesa, AFAICT -- and the Steam beta FINALLY shipped a new, LLVM-3.5 compatible runtime.

          Thank you all for your pointers, and special thanks to Oibaf for the PPA. I hope everything will stay fast and stable for the time being.

          Comment


          • Originally posted by oibaf View Post
            You may have noticed I added mesa, libdrm and libclc packages also for Ubuntu 14.10/utopic in the PPA.

            Also, I looked into adding to mesa package the Gallium D3D9 state tracker (gallium-nine). It works fine, however since it has many changes, merging this git tree into mesa master breaks frequently (as of this writing it still has merge conflicts) and I cannot add it in the main PPA which is automatically updated twice a day. So, I set up a test PPA where you can find a mesa snapshot including it here.
            Did I ever tell you that I love you?

            Comment


            • Actually gallium-nine merges properly, so I added it to the main PPA.

              Comment


              • Originally posted by oibaf View Post
                Actually gallium-nine merges properly, so I added it to the main PPA.
                Wow, this is absolutely great! Thanks for your great work!

                Comment


                • Originally posted by oibaf View Post
                  Actually gallium-nine merges properly, so I added it to the main PPA.


                  Thanks for all you done for as.

                  Comment


                  • Originally posted by oibaf View Post
                    Actually gallium-nine merges properly, so I added it to the main PPA.
                    We're not worthy!

                    Comment


                    • Originally posted by oibaf View Post
                      @0xBADCODE
                      Make sure to report the bugs, maybe they can be fixed before final llvm 3.5.
                      I'm not even sure it is bug in LLVM. Could be some kernelside issue or so. I can see heavy activity related to memory management patching in Linux kernel, etc. Any hints from AMD guys? After all it shouldn't be too hard to launch clinfo or bfgminer --scrypt --benchmark and then get idea what exactly crashed? I believe AMD ppl could be way better than me at identifying faulty component(s).

                      Comment

                      Working...
                      X