[LINUX] HOW-TO use VAAPI HW Acceleration on AMD Zacate (Fusion) platform - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: [LINUX] HOW-TO use VAAPI HW Acceleration on AMD Zacate (Fusion) platform (/showthread.php?tid=99154) |
- WytRaven - 2011-06-16 Hey Robotica I see you updated the first post catalyst install section using the modified instructions I provided. That's great and all except my instructions are for 2.6.39 kernel and I thought your instructions were based on the standard 2.6.38 kernel. That might confuse people as I have no idea if that patch will break the driver if installed on 2.6.38...(you could test I suppose). - Robotica - 2011-06-16 True, but I also update OP with instructions to upgrade to newer kernel... Also check this out, maybe it is usefull: http://phoronix.com/forums/showthread.php?35840-VAAPI-Segmentation-fault-right-after-va_getDriverName() - Rapoza - 2011-06-16 Robotica Wrote:Maybe it is easier to build from GIT instead of using 10. 1 since the patch is included. The fact is perhaps that I don't understand well the instructions on the guide. You mean that here you offered two options? I thought the patch was something that wasn't included on CODE @WytRaven: Yes I'm also using that kernel. But I'm really lost on code order execution. I'll post my execution and perhaps we can make some "compositing". I'm more biased to include all orders in the guide, becouse then there's finally the possibility of making a script. My notes, feel free to blame Code: ##DO A CLEAN INSTALLATION FROM A MINIMAL UBUNTU 11.04 - Rapoza - 2011-06-16 Robotica Wrote:True, but I also update OP with instructions to upgrade to newer kernel... But by now 2.6.39 its the default kernel on natty minimal installations. Thats my objective. Make a minimal running machine with the newer possible os and drivers. Seems that the code post by WytRaven will make my installation finally work. That could be the issue. Now I must see where it goes. I understand that it replaces the entire driver installation section? Tomorrow I'll take the htpc to my desktop and clean-start from what we concret today. If you want me to post the installed kernel, xorg, alsa, mesa, etc versions at some moment, please tell me how to obtain. (Don't make me look at some dist-upgrade text, please) - Robotica - 2011-06-16 Rapoza Wrote:The fact is perhaps that I don't understand well the instructions on the guide. You mean that here you offered two options? I thought the patch was something that wasn't included on CODE Depends on your source: Not included: 10.0, 10.1 Included: Git Rapoza Wrote:But by now 2.6.39 its the default kernel on natty minimal installations.The source I refer to is based on 2.6.38. Where is your source? - Rapoza - 2011-06-16 WytRaven Wrote:If you are like me and using the 2.6.39 kernel then the standard method of installation wont work. Here's a revised version based on Robotica's original format which works for us: Quote:Only if you don't have an /etc/X11/xorg.conf already. Well let's just say that I didn't do an aticonfig and already had an /etc/X11/xorg.conf in place and it worked for me. Its needed when you do minimal install. That was the reason of my first insanity, until I realized that doing a complete ubuntu install creates some configuration files that I was missing (prior of installation of xbmc AND live script) I made a maverick complete and all was nice and clean. So I'm now trying the minimal. @Robotica Errr... The minimal downloads all the packages at the moment. I'm getting that kernel from start. I got it before doing any dist-upgrade. In fact, on all of them it said 0 upgrades. YEES! Its GIT! I tought you recommended. Note that ##--adapter=all## is commented. Only required if you have two gfx adapters. I tried becouse I was getting strange resolution issues without using DVI+HDMI. Also look that I took the maximum possible code from before you can do ssh connection, so people can cutri-paste from putty. Also Python could be later. - Rapoza - 2011-06-16 WytRaven Wrote:But I have not compiled xbmc yet. I'm still playing with mplayer and have no sound and -vo vaapi crashes it every time. I may just go straight for the xbmc build and then start figuring out the issues as I have no idea if the mplayer crash is it's fault or the vaapi libs at this point and I have no intention of using mplayer on this machine beyond this testing I'm doing. Try with XBMC it installs plenty of audio dependencies. I think your scenario would change too much to stay on mplayer first. HAve you already tested disabling composite and unity for the crashes. I saw anything around. - Robotica - 2011-06-16 WytRaven Wrote:But I have not compiled xbmc yet. I'm still playing with mplayer and have no sound and -vo vaapi crashes it every time. I may just go straight for the xbmc build and then start figuring out the issues as I have no idea if the mplayer crash is it's fault or the vaapi libs at this point and I have no intention of using mplayer on this machine beyond this testing I'm doing. Sound problem in linux: http://forum.xbmc.org/showthread.php?tid=103563 Compilation unnecessary - SDM2011 - 2011-06-16 I have an Ubuntu minimal install, I have full video acceleration, and I didn't compile a single package. I really don't think it's necessary in fact. I installed two relevant ppas: lars-opdenkamp/xbmc-pvr, and ubuntu-x-swat/x-updates. I have these packages installed:
Be sure to run this command and pick fglrx: Code: sudo update-alternatives --config gl_conf Be sure that your user is added to audio, video groups. There may be more groups required depending on your install, ie. whether you use pulseaudio like I do, etc. My vainfo: Code: libva: libva version 0.32.0 Others seemed worried that va_openDriver() returning 0 indicated a problem, but that does not seem to be the case for me. I have fully accelerated decoding for 1080p H.264 and VC-1. My installation isn't perfect, but I mainly have to contend with driver bugs, so I imagine the issues are common to every install. [1] The only problem with this is that if the screen is not plugged in or started at boot time, xbmc may start with the wrong resolution. In this case you have to log out and back in. I have the Slim login manager installed, set to auto-login at boot. - Rapoza - 2011-06-16 In fact "returns 0" means no errors. 1=errors. I tried that way the first time but didn't work on natty. thats the reason of the 2nd option in my notes. Can you please post the commands and more important the execution order? THX. - SDM2011 - 2011-06-16 I should also note that there's a missing dependency in the standard xvba-va-driver package which causes it to fail. I'm surprised that this still hasn't been fixed actually. I used the patched package provided by Andrew Hunter. I tried upgrading to the new Catalyst 11.6 release, but it doesn't build against 2.6.39, and downgrading the kernel conflicts with the libva versions bundled elsewhere, and the xvba-video package from splitted-desktop doesn't integrate properly either. You're better off just using the standard packages I listed above, and waiting for Ubuntu maintainers to release updates. As for the specific commands, just use apt-get. As for their order, it shouldn't matter. If you have trouble after having only the above two ppas installed, try apt-get update; apt-get dist-upgrade, then try to install the packages I listed once that's done. - WytRaven - 2011-06-16 Well I decided to give SDM2011's method a go. Started from mini.iso CLI install. I have all the same packages installed that he had via apt-get, with the exception of Catalyst 11.6, which I got built using the patched method I mentioned earlier. (by the way the 2.6.39-3 kernel is in the xorg-edgers/ppa) What I have is a nice XBMC install that I can run around and play with menus in, I even get nice little thumbnails of my music videos but the split second I try to play a video .... instant crash, just like mplayer did on previous install. I have been up all night on this and I really can't be stuffed looking at log files right now. Yay for yet another failed attempt. EDIT: Ok, so I did take a quick peek at logs. Looks like it audio that is failing not the video. I see this in the log "VAAPI - attempting to open codec 28 with profile 77 at level 40 with 2 reference frames" but nothing saying that it didn't work. It then goes on to initialising audio and ultimately fails...however the log suggests that it is gracefully handling the issues with audio...but crashes. - Robotica - 2011-06-16 WytRaven Wrote:Well I decided to give SDM2011's method a go. Started from mini.iso CLI install. I have all the same packages installed that he had via apt-get, with the exception of Catalyst 11.6, which I got built using the patched method I mentioned earlier. (by the way the 2.6.39-3 kernel is in the xorg-edgers/ppa) Damn! Hopefully, I will give it a try this weekend. Will be using XBMC git and try with .38 kernel instead. - htpcero - 2011-06-17 SDM2011 Wrote:I should also note that there's a missing dependency in the standard xvba-va-driver package which causes it to fail. I'm surprised that this still hasn't been fixed actually. I used the patched package provided by Andrew Hunter. Well I tried the recommendations, all of them I think. Latest xvba from Andrew's PPA (which is splitted-desktop's), xbmc-pvr from Lars' PPA, catalyst 11.5 from x-updates, latest libva from x-org-edgers (or was it x-updates), and kernel 2.6.39-3 from xorg-edgers. Exact same disappointing results. XBMC works great as long as vaapi is disabled; when vaapi is enabled, xbmc will crash when attempting to play mpeg4/h264 content. I also tried compiling directly from GIT - as you can guess, I got the same results. This is on 11.04/Natty AMD64, ASUS E35M1-I Deluxe. Acceleration is just not working for me. I'm hoping we will figure this out sometime (soon ! WytRaven Wrote:Well I decided to give SDM2011's method a go. Started from mini.iso CLI install. I have all the same packages installed that he had via apt-get, with the exception of Catalyst 11.6, which I got built using the patched method I mentioned earlier. (by the way the 2.6.39-3 kernel is in the xorg-edgers/ppa) The crash logs in my build with 2.6.39-3 are pretty much the same as they were with 2.6.38. 2.6.39-3: Code: 19:26:34 T:140497501726464 M:1377157120 INFO: ffmpeg[1FAEA700]: Duration: 00:54:15.04, start: 0.000000, bitrate: 1802 kb/s 2.6.38 Code: 19:03:13 T:139919522219776 M:1324822528 INFO: ffmpeg[8D6B4700]: Duration: 00:54:15.04, start: 0.000000, bitrate: 1802 kb/s - Robotica - 2011-06-17 SO XBMC logs tell it crashed. How does your xorg.conf/Xorg.0.log looks like? And aticonfig and glxinfo? And I also think that it is not necessary to compile with VDPAU and ChrystalHD support. I also suggest not using PPA atm, so we all compile the same and have consitent results. |