如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

系统安装、升级讨论
版面规则
我们都知道新人的确很菜,也喜欢抱怨,并且带有浓厚的Windows习惯,但既然在这里询问,我们就应该有责任帮助他们解决问题,而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享,以人为本,这正是Ubuntu的精神所在。
回复
头像
ziymin
帖子: 12
注册时间: 2009-11-04 13:34

如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#1

帖子 ziymin » 2010-11-18 0:24

百度空间里找到一篇文章介绍到可以用libva来让mplayer来支持vaapi,从而开启硬件高清加速(看地址链接)
http://hi.baidu.com/liuweigang525/blog/ ... bf7ec.html
小弟试了,可是是中间就出错了,ATI驱动已经安装好,接下来安装libva(http://www.splitted-desktop.com/~gbeauchesne/libva/
我选择了最前的libva_0.31.1-1+sds4.tar.gz 13-Jul-2010 17:25 785K )解压完 又./configure 过后,要make install的时候,
出现下面的错误,最后一句应该是说差什么XEXT环境来的,
小弟菜鸟啊,此环境在软件中心里查找安装后,还是不能进一步make install安装编译, :em26
高手们,指点一下小弟吧,下面是编译过程:

root@Raikii-desktop:/tmp/libva-0.31.1# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for X11... yes
checking for XEXT... configure: error: Package requirements (xext) were not met:

No package 'xext' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XEXT_CFLAGS
and XEXT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

root@Raikii-desktop:/tmp/libva-0.31.1# make install
make: *** 没有规则可以创建目标“install”。 停止。
root@Raikii-desktop:/tmp/libva-0.31.1#
头像
kedacheng
帖子: 103
注册时间: 2008-08-03 14:12

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#2

帖子 kedacheng » 2010-11-18 12:09

A卡令人望而却步,现在钟爱集显了 :em06
头像
ziymin
帖子: 12
注册时间: 2009-11-04 13:34

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#3

帖子 ziymin » 2010-11-18 23:33

kedacheng 写了:A卡令人望而却步,现在钟爱集显了 :em06
:em04 小弟用的就是集显哈,ba210的板,集成hd4200,呵呵,就是上面的问题啊,烦~~~有解么?
头像
jarryson
帖子: 4002
注册时间: 2005-08-14 19:53

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#4

帖子 jarryson » 2010-11-19 2:12

缺少libxext的头文件。当然你不仅仅只是需要这一点头文件,你需要什么支持就需要提前安装好相应头文件,也就是很多-dev包。多使用google搜索一下ubuntu下编译mplayer。

ubuntu下编译就是麻烦。还有我不推荐你在linux下硬解,mplayer软解效率也不错,硬解一定省电,而且格式还有很多限制。

而且ATI的硬解是不能开启compiz的。
上次由 jarryson 在 2010-11-19 2:15,总共编辑 1 次。
delectate
帖子: 18311
注册时间: 2008-01-09 22:41

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#5

帖子 delectate » 2010-11-19 2:14

vdpau轻松,试试vlc
ryoohki
帖子: 3249
注册时间: 2008-10-28 20:18

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#6

帖子 ryoohki » 2010-11-22 19:22

人家又不是N卡,让人家用Vdpau , A卡表示压力很大
头像
速腾1994
论坛版主
帖子: 17379
注册时间: 2008-11-01 20:43
系统: Arch+gnome

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#7

帖子 速腾1994 » 2010-11-22 21:10

xp :em03
头像
midworld
帖子: 42
注册时间: 2010-10-16 22:36
来自: 在路上

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#8

帖子 midworld » 2010-12-02 10:11

通过apt命令安装XEXT试试(x11proto-xext-dev?)
OS: Ubuntu 10.04 + VirtualBox(Windows XP, Mac OS X 10.6)
CPU: AMD 64 X 2 4000+
RAM: 2G 800MHz DDR
Displayer: 索泰GT240 DDR5 512M
Hard Disk: .....
secowu
帖子: 308
注册时间: 2006-07-06 18:25

Re: 如何用使buntu10.04-i386 ATI显卡硬件实现高清加速,让mplayer来支持vaapi?

#9

帖子 secowu » 2010-12-02 22:01

我也是ATI的,X1250
回复