Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • these drivers are amazing! L4D2 is playing ultra smooth and about 3x as fast as catalyst with no mouse lag, vsync works where it did not before and amazingly AA now works which it did not before and the performance hit is nominal

    however, after about 20 - 40mins of playing i am getting system lock ups. Is there any log i can post on here to help ?

    Comment


    • stats-rebased needs... a rebase.

      Comment


      • hello and thank you very much for your efforts and the great work oibaf.
        I am struggeling for few weeks now with getting hardware acceleration of my AMD HD7850 to work and finally installed your ppa on a fresh ubuntu 13.10 with kernel 3.13.
        beforehand I used fglrx but due to the bad xvba support I decided to switch back to radeon...

        Code:
        ~$ uname -a
        Linux htpc 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:36:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
        unfortunately I am stuck on gallium
        Code:
        $ glxinfo |grep Open
        OpenGL vendor string: VMware, Inc.
        OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
        OpenGL version string: 2.1 Mesa 10.1.0-devel (git-3f3aafb saucy-oibaf-ppa+curaga)
        OpenGL shading language version string: 1.30
        OpenGL extensions:
        my xserver is running but obviously without acceleration
        Code:
        (II) RADEON(0): GPU accel disabled or not working, using shadowfb for KMS
        I would appreciate if you find the problem, I have no more ideas...

        thanks in advance,
        schnappi

        Comment


        • Originally posted by schnappi View Post
          hello and thank you very much for your efforts and the great work oibaf.
          I am struggeling for few weeks now with getting hardware acceleration of my AMD HD7850 to work and finally installed your ppa on a fresh ubuntu 13.10 with kernel 3.13.
          beforehand I used fglrx but due to the bad xvba support I decided to switch back to radeon...

          Code:
          ~$ uname -a
          Linux htpc 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:36:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
          unfortunately I am stuck on gallium
          Code:
          $ glxinfo |grep Open
          OpenGL vendor string: VMware, Inc.
          OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
          OpenGL version string: 2.1 Mesa 10.1.0-devel (git-3f3aafb saucy-oibaf-ppa+curaga)
          OpenGL shading language version string: 1.30
          OpenGL extensions:
          my xserver is running but obviously without acceleration
          Code:
          (II) RADEON(0): GPU accel disabled or not working, using shadowfb for KMS
          I would appreciate if you find the problem, I have no more ideas...

          thanks in advance,
          schnappi
          Did you properly fully remove all of fglrx? Did you remove the xorg.conf in /etc/X11?

          Comment


          • Originally posted by mmstick View Post
            Did you properly fully remove all of fglrx? Did you remove the xorg.conf in /etc/X11?
            I did fresh installation of ubuntu. no fglrx used, no other ppa.
            thanks for advise :-/

            Comment


            • http://cgit.freedesktop.org/mesa/mes...?qt=grep&q=AMD

              The OpenGL 3.3 RadeonSI patches are now live in mesa upstream. All we need is for Oibaf to upgrade to LLVM 3.5 git and update the rest.

              Comment


              • Originally posted by oibaf View Post
                stats-rebased needs... a rebase.
                Done.

                Comment


                • I jknow its not a place to post bugs.
                  But just to let everyone know.
                  INTEL HD3000 + AMD 6450M
                  chrome 100% unusable using acelerated or not.

                  constants crashes...
                  [ 75.162430] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                  [ 597.043197] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                  [ 597.043209] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                  [ 597.415392] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                  [ 597.415403] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                  [ 761.283390] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                  [ 761.283402] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                  [ 761.656967] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                  [ 761.656980] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

                  LAtest 7 days seems very unstable..

                  Not asking for help or otas for nothing.
                  Just a small report.

                  ;-)

                  Comment


                  • and...
                    [ 89.018649] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                    [ 89.018654] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                    [ 342.070463] [drm] stuck on render ring
                    [ 342.070468] [drm] GPU crash dump saved to /sys/class/drm/card0/error
                    [ 342.070470] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
                    [ 342.070471] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
                    [ 342.070473] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
                    [ 342.070474] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
                    [ 342.074617] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x86b000 ctx 0) at 0x86b5a0
                    [ 367.050023] [drm] stuck on render ring
                    [ 367.050073] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x85c000 ctx 0) at 0x85c830
                    [ 624.002572] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                    [ 624.002584] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
                    [ 624.373040] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
                    [ 624.373053] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

                    cat /sys/class/drm/card0/error

                    Num Pipes: 2
                    Pipe [0]:
                    SRC: 077f0437
                    Plane [0]:
                    CNTR: d8004400
                    STRIDE: 00001e00
                    ADDR: 00000000
                    SURF: 02063000
                    TILEOFF: 00000000
                    Cursor [0]:
                    CNTR: 04000027
                    POS: 00b4000f
                    BASE: 01073000
                    Pipe [1]:
                    SRC: 00000000
                    Plane [1]:
                    CNTR: 00004000
                    STRIDE: 00000000
                    ADDR: 00000000
                    SURF: 00000000
                    TILEOFF: 00000000
                    Cursor [1]:
                    CNTR: 00000000
                    POS: 00000000
                    BASE: 00000000
                    CPU transcoder: A
                    CONF: c0000050
                    HTOTAL: 0897077f
                    HBLANK: 0897077f
                    HSYNC: 080307d7
                    VTOTAL: 04640437
                    VBLANK: 04640437
                    VSYNC: 0440043b
                    CPU transcoder: B
                    CONF: 00000000
                    HTOTAL: 00000000
                    HBLANK: 00000000
                    HSYNC: 00000000
                    VTOTAL: 00000000
                    VBLANK: 00000000
                    VSYNC: 00000000

                    Comment


                    • Chrome issue with intel drivers

                      has been fixed. At least in my case (Sandy Bridge). I am not getting the corruptions any more.

                      Comment

                      Working...
                      X