Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • The performance is really good. Installed it on my Intel m380 2.5Ghz laptop with Radeon HD 6370M. I'm also on oibaf's PPA so open source drivers are no problem. Max resolution on my laptop is 1360X768 so that's what I run. Most of the settings are max except for AA and anisotropic. There's no AA and little anisotropic. The mouse is a bit fast with a mouse pad even at lowest setting but I will plug in a real mouse and see how that works.

    Comment


    • That post wasn't meant for here. It was for Borderlands 2.

      Comment


      • NEWS

        Mesa:
        • built again on utopic, disabling opencl due to llvm bug;
        • added vaapi gallium driver.


        MPV 0.6 on utopic, latest intel-vaapi-driver, libva and libvdpau on both trusty and utopic.

        Comment


        • Originally posted by oibaf View Post
          Mesa:
          • built again on utopic, disabling opencl due to llvm bug;
          • added vaapi gallium driver.


          MPV 0.6 on utopic, latest intel-vaapi-driver, libva and libvdpau on both trusty and utopic.
          How do i "see" vaapi with a dedicated amd card? DRI_PRIME=1 vainfo only shows me the intel driver:

          DRI_PRIME=1 vainfo
          libva info: VA-API version 0.36.0
          libva info: va_getDriverName() returns 0
          libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
          libva info: Found init function __vaDriverInit_0_36
          libva info: va_openDriver() returns 0
          vainfo: VA-API version: 0.36 (libva 1.4.0)
          vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 1.4.0
          vainfo: Supported profile and entrypoints
          VAProfileMPEG2Simple : VAEntrypointVLD
          VAProfileMPEG2Simple : VAEntrypointEncSlice
          VAProfileMPEG2Main : VAEntrypointVLD
          VAProfileMPEG2Main : VAEntrypointEncSlice
          VAProfileH264ConstrainedBaseline: VAEntrypointVLD
          VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
          VAProfileH264Main : VAEntrypointVLD
          VAProfileH264Main : VAEntrypointEncSlice
          VAProfileH264High : VAEntrypointVLD
          VAProfileH264High : VAEntrypointEncSlice
          VAProfileH264MultiviewHigh : VAEntrypointVLD
          VAProfileH264MultiviewHigh : VAEntrypointEncSlice
          VAProfileH264StereoHigh : VAEntrypointVLD
          VAProfileH264StereoHigh : VAEntrypointEncSlice
          VAProfileVC1Simple : VAEntrypointVLD
          VAProfileVC1Main : VAEntrypointVLD
          VAProfileVC1Advanced : VAEntrypointVLD
          VAProfileNone : VAEntrypointVideoProc
          VAProfileJPEGBaseline : VAEntrypointVLD
          VAProfileH264MultiviewHigh : VAEntrypointVLD
          VAProfileH264MultiviewHigh : VAEntrypointEncSlice
          VAProfileH264StereoHigh : VAEntrypointVLD
          VAProfileH264StereoHigh : VAEntrypointEncSlice

          DRI_PRIME=1 vdpauinfo shows me the correct info:

          DRI_PRIME=1 vdpauinfo
          display: :0 screen: 0
          API version: 1
          Information string: G3DVL VDPAU Driver Shared Library version 1.0

          Video surface:

          name width height types
          -------------------------------------------
          420 16384 16384 NV12 YV12
          422 16384 16384 UYVY YUYV
          444 16384 16384 Y8U8V8A8 V8U8Y8A8

          Decoder capabilities:

          name level macbs width height
          -------------------------------------------
          MPEG1 0 9216 2048 1152
          MPEG2_SIMPLE 3 9216 2048 1152
          MPEG2_MAIN 3 9216 2048 1152
          H264_BASELINE 41 9216 2048 1152
          H264_MAIN 41 9216 2048 1152
          H264_HIGH 41 9216 2048 1152
          VC1_ADVANCED 4 9216 2048 1152
          MPEG4_PART2_SP 3 9216 2048 1152
          MPEG4_PART2_ASP 5 9216 2048 1152

          Output surface:

          name width height nat types
          ----------------------------------------------------
          B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8
          R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8
          R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8
          B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8

          Bitmap surface:

          name width height
          ------------------------------
          B8G8R8A8 16384 16384
          R8G8B8A8 16384 16384
          R10G10B10A2 16384 16384
          B10G10R10A2 16384 16384
          A8 16384 16384

          Video mixer:

          feature name sup
          ------------------------------------
          DEINTERLACE_TEMPORAL y
          DEINTERLACE_TEMPORAL_SPATIAL -
          INVERSE_TELECINE -
          NOISE_REDUCTION y
          SHARPNESS y
          LUMA_KEY -
          HIGH QUALITY SCALING - L1 -
          HIGH QUALITY SCALING - L2 -
          HIGH QUALITY SCALING - L3 -
          HIGH QUALITY SCALING - L4 -
          HIGH QUALITY SCALING - L5 -
          HIGH QUALITY SCALING - L6 -
          HIGH QUALITY SCALING - L7 -
          HIGH QUALITY SCALING - L8 -
          HIGH QUALITY SCALING - L9 -

          parameter name sup min max
          -----------------------------------------------------
          VIDEO_SURFACE_WIDTH y 48 2048
          VIDEO_SURFACE_HEIGHT y 48 1152
          CHROMA_TYPE y
          LAYERS y 0 4

          attribute name sup min max
          -----------------------------------------------------
          BACKGROUND_COLOR y
          CSC_MATRIX y
          NOISE_REDUCTION_LEVEL y 0.00 1.00
          SHARPNESS_LEVEL y -1.00 1.00
          LUMA_KEY_MIN_LUMA y
          LUMA_KEY_MAX_LUMA y

          using your ppa, build from today (after the libva 1.4.0 and mesa build with vaapi gallium support).

          any help will be greatly appreciated

          keep up the good work...

          Comment


          • What the point to use hardware decoder of your dGPU if you have VA-API on iGPU?

            Comment


            • Originally posted by groo_pcd View Post
              How do i "see" vaapi with a dedicated amd card?
              Code:
              DRI_PRIME=1 LIBVA_DRIVER_NAME=gallium vainfo
              libva info: VA-API version 0.36.0
              libva info: va_getDriverName() returns 0
              libva info: User requested driver 'gallium'
              libva info: Trying to open /usr/lib64/dri/gallium_drv_video.so
              libva info: Found init function __vaDriverInit_0_36
              libva info: va_openDriver() returns 0
              vainfo: VA-API version: 0.36 (libva 1.4.1.pre1)
              vainfo: Driver version: mesa gallium vaapi
              vainfo: Supported profile and entrypoints
                    VAProfileMPEG2Simple            : VAEntrypointVLD
                    VAProfileMPEG2Main              : VAEntrypointVLD
                    VAProfileMPEG4Simple            : VAEntrypointVLD
                    VAProfileMPEG4AdvancedSimple    : VAEntrypointVLD
                    VAProfileVC1Advanced            : VAEntrypointVLD
                    VAProfileH264Baseline           : VAEntrypointVLD
                    VAProfileH264Main               : VAEntrypointVLD
                    VAProfileH264High               : VAEntrypointVLD

              Comment


              • [email protected]:~$ vainfo
                libva info: VA-API version 0.36.0
                libva info: va_getDriverName() returns 0
                libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
                libva info: va_openDriver() returns -1
                vaInitialize failed with error code -1 (unknown libva error),exit

                Comment


                • Now that the binutils bug is fixed I added again opencl support.

                  About va driver not found, it's because mesa is not generating links as it happens with other state trackers (vdpau, DRI, ...). It should probably be fixed in mesa.

                  Comment


                  • I was under the impression that radeon didn't support VA-API directly, but had to have it wrapped through VDPAU (which, last I checked was pretty bad)?

                    Comment


                    • Originally posted by Espionage724 View Post
                      I was under the impression that radeon didn't support VA-API directly, but had to have it wrapped through VDPAU (which, last I checked was pretty bad)?
                      That was only true until they added the VAAPI state tracker into Mesa. (Which happened very recently)

                      Comment

                      Working...
                      X