+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Linux and Live support (/forumdisplay.php?fid=52)
+---- Thread: [LINUX] HOW-TO use VAAPI HW Acceleration on AMD Zacate (Fusion) platform (/showthread.php?tid=99154)
- macer - 2011-06-14 20:02
h0tzen Wrote:thank you very much for that HowTo.
please excuse the dumb question, but what does PVR stand for in xbmc-pvr?
PVR is Personal Video Recorder. When you have, for example, DVB-T tuner, you can watch live tv in xbmc-pvr
- devil103 - 2011-06-14 20:20
PVR = personal video recorder. The PVR build is more geared towards capturing live tv.
- WytRaven - 2011-06-15 04:01
Good to hear you have had success devil103 that gives me new hope too. I have now tested my hardware using the nemek custom live-cd so I can confirm that it can work on my hardware too.
Another note on the Realtek 8111E driver issue with the ASUS E35M1-I Deluxe board. I can now confirm that using the Realtek driver (r8168 version 8.024.00) with the 2.6.39 kernel is solid. I have had it transferring solidly at gigabit speeds (100MB/s+) for over 7 hours now transferring my blu-ray collection from old system to new. That says solid to me.
One gotcha with the driver replacement was making sure to blacklist the old r8169 module to prevent it being loaded again and then update initramfs. Here is basically what I did (all performed as root via "sudo su"):
Code:
--- Installed 2.6.39 kernel from ppa:kernel-ppa/ppa and booted up with new kernel
add-apt-repository ppa:kernel-ppa/ppa
apt-get update
apt-get install linux-headers-2.6.39-0 linux-headers-2.6.39-0-generic linux-image-2.6.39-0-generic --fix-missing
reboot
---- Downloaded driver archive from http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
tar xvfs r8168-8.024.00.tar.bz2
cd r8168-8.024.00
./autorun.sh
--- added the following two lines to /etc/modprobe.d/blacklist.conf
# Replaced by r8168 v8.024.0 for the NIC RTL8111E
blacklist r8169
--- Update initramfs
update-initramfs -u
reboot
--- At this point you should be able to run the following command and see the loaded driver as r8168 and not r8169
lspci -vI know the NIC stuff is a little off topic for this thread but as it is related directly to hardware that people may have that are reading this thread I figure it is valid it being here. However I do not yet know if kernel 2.6.39 can be successfully used with XBMC VAAPI but I have heard others state they have achieved it
- peterk2005 - 2011-06-15 11:38
WytRaven Wrote:Good to hear you have had success devil103 that gives me new hope too. I have now tested my hardware using the nemek custom live-cd so I can confirm that it can work on my hardware too.
How about 24p accelerated playback with vsync on? Does it work for you?
libva issue?! - dafrog - 2011-06-15 13:41
Hi there,
I am following this thread for a while as I have the same ASUS E35M1-I Deluxe board as "WytRaven". Some of the problems sound familiar to me. Thanks for NIC hint by the way...
I installed my system the way "devil103" suggested without bigger issues. The XBMC has been installed from here using the Unstable-Blueray release.
In my xbmc-video-settings the VAAPI is enables and VPDAU is disabled with the result that every time I am trying to play a video I get the following "error msg" crashing the application:
Code:
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.32
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8.pre1
vainfo: Supported profile and entrypoints
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
[b]Segmentation fault[/b]Code:
-rw-r--r-- 1 root root 17888 2011-02-24 12:33 dummy_drv_video.so
lrwxrwxrwx 1 root root 17 2011-06-15 01:31 fglrx_drv_video.so -> xvba_drv_video.so
-rw-r--r-- 1 root root 121488 2011-02-26 04:23 xvba_drv_video.soWhat is this "Segmentation fault" about? Could this be a fix? I am not a linux beginner but it would save me some time if somebody already tried that. Here is another info - maybe I am using a broken vainfo?!
In a lot of posts I saw "libva: va_openDriver() returns 0" - is this a issue or a warning? "OpenDriver" normaly sounds important
The normal playback with VAAPI & VDPAU disabled works - but with the known restrictions...
Any ideas?
Regards Fabian
- Robotica - 2011-06-15 20:54
Updated OP with most above info. Hopefully, someone can share an updated (kernel, ati drivers, etc) Nemek build.
Please also post all driver-problems related to LAN, WLAN, Sound, etc in this topic together with your hardware.
- jbo87 - 2011-06-16 08:19
ATI Catalyst 11.6 has been released. I have no changelog though.
http://www2.ati.com/drivers/linux/ati-driver-installer-11-6-x86.x86_64.run
- Rapoza - 2011-06-16 12:25
Robotica Wrote:Updated OP with most above info. Hopefully, someone can share an updated (kernel, ati drivers, etc) Nemek build.
Please also post all driver-problems related to LAN, WLAN, Sound, etc in this topic together with your hardware.
Take care with the current rexbron/catalysthacks xvba patches. They have incompatibility with the splitted-desktop libva and xbmc-pvr that jumps when installing xbmc or updating, and then there's no back-turn. I found out the hard way.
Follow:
http://ubuntuforums.org/showthread.php?t=1677477&page=2
http://forum.xbmc.org/printthread.php?t=81286&pp=40&page=5
Seems to me that rexbron could be based on catalysthacks as also shared the bug.
My vaapi installation on natty (cli), note new version:
Code:
cd ~/; mkdir vaapi; cd vaapi/
wget http://www.splitted-desktop.com/~gbeauchesne/libva/pkgs/amd64/libva1_0.32.0-1+sds2_amd64.deb
wget http://www.splitted-desktop.com/~gbeauchesne/libva/pkgs/amd64/libva-dev_0.32.0-1+sds2_amd64.deb
sudo apt-get install -y libkms1 libdrm-dev pkg-config
sudo dpkg -i libva1_0.32.0-1+sds2_amd64.deb libva-dev_0.32.0-1+sds2_amd64.deb
wget http://www.splitted-desktop.com/~gbeauchesne/xvba-video/xvba-video_0.8.0-1_amd64.deb
sudo dpkg -i xvba-video_0.8.0-1_amd64.debMy driver installation lines, note the two first:
Code:
sudo apt-get install -y build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases
sudo apt-get install -y ia32-libs
cd ~/; mkdir catalyst11.5; cd catalyst11.5/
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
chmod +x ati-driver-installer-11-5-x86.x86_64.run
sudo sh ./ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i fglrx*.deb
sudo aticonfig --initial -f ##--adapter=all##
sudo rebootFor ASUS e35m1-i deluxe owners, as me, take into account that there applies the bug in the driver where the gfx card seems to be not supported.
Best results on Maverick, using the vaapi versions 0.32+0.7.8 and 11.5 catalyst driver using the following patches:
Code:
##UNSUPPORTED HARDWARE WATERMARK
cd ~/catalyst11.5/
#IF NOT PRESENT
sh ati-driver-installer-11-5-x86.x86_64.run --extract driver
sudo mv /etc/ati/control ~/control.bak
sudo cp driver/common/etc/ati/control /etc/atiIts also required the DRI patch:
Code:
sudo nano /etc/X11/xorg.conf
## ADD ON MODULE:
## Load "dri"
## Change DPMS to false (energy saving)I have it working on Maverick, only have some slight tearing and HD content not supported.
Natty don't wan't to use the vaapi, drivers or anything. Don't know why.
vainfo shows unknow error and fglrxinfo can't access the device.
I also noticed that pvr xbmc does weird things with subtitles, and only shows embedded ones.
If anyone interested I could share my complete command list+xorg.conf so we can make a working Natty + ASUS e35m1-i deluxe installation.
Best regards,
Sergio.
- wobu - 2011-06-16 12:51
the splitted desktop vaapi libs become open source
http://www.phoronix.com/scan.php?page=news_item&px=OTU2Ng
- Rapoza - 2011-06-16 12:53
Robotica Wrote:Build XBMC:
// include this patch.
I know I'm a complete nerd, but please robotica, can you include the steps to do this?
Another question: If you include the Ubuntu-X rep (for open driver), then the vaapi changes to version 1.x.x on the first dist-upgrade. Are those preferible over gbeauchesne?
**I ate you, now I have to do another clean install