Posts: 235
Joined: May 2012
Reputation:
3
so do you suggest we stay on xbmc-xvba or should we go with xbmc-xvba-frodo?
Posts: 235
Joined: May 2012
Reputation:
3
xbmc-xvba has been really nice and stable but if it isn't updated anymore I should probably go with the frodo one right?
What is the new things in gotham so far anyhow?
Posts: 23,376
Joined: Aug 2011
Reputation:
1,089
fritsch
Team-Kodi Developer
Posts: 23,376
We will continue to update it - currently we have planned to do it before every new merge window.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 235
Joined: May 2012
Reputation:
3
is the plan to move xvba into gotham general release during the dev cycle or will it stay seperate?
Posts: 387
Joined: Dec 2011
Reputation:
5
2013-03-20, 21:17
(This post was last modified: 2013-03-20, 21:25 by tutu.)
I've just done a sudo apt-get update and sudo apt-get upgrade (using xbmc-xvba) and now lightdm is not starting xbmc (last time I updated was about christmas)
I have checked the guide and all the previous config files are present?
Don't know if this is relevant. There is no xbmc log
/home/xbmc$ sudo cat .xsession-errors
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Syslog:
syslog:Jan 9 20:40:56 phoenix kernel: [ 478.972448] INFO: task xbmc.bin:1253 blocked for more than 120 seconds.
syslog:Jan 9 20:40:56 phoenix kernel: [ 478.972453] xbmc.bin D ffff88022fc939c0 0 1253 1 0x00000004
syslog:Jan 9 20:40:56 phoenix kernel: [ 478.972786] INFO: task xbmc.bin:1452 blocked for more than 120 seconds.
syslog:Jan 9 20:40:56 phoenix kernel: [ 478.972788] xbmc.bin D ffff88022fc939c0 0 1452 1 0x00000004
syslog:Jan 19 12:03:50 phoenix kernel: [ 49.958917] xbmc.bin[1272]: segfault at 74 ip 00007f3ccd4c60ff sp 00007fffaa3a7b30 error 4 in libfreetype.so.6.9.0[7f3ccd4b0000+96000]
syslog:Jan 19 12:10:48 phoenix kernel: [ 32.528255] xbmc.bin[1248]: segfault at 74 ip 00007f7429e260ff sp 00007fff4f739cb0 error 4 in libfreetype.so.6.9.0[7f7429e10000+96000]
syslog:Feb 2 15:09:10 phoenix kernel: [ 34.766959] xbmc.bin[1296]: segfault at 74 ip 00007f4b2281e0ff sp 00007fff3cdb1940 error 4 in libfreetype.so.6.9.0[7f4b22808000+96000]
System is Ubuntu 12.10 with AMD Trinity on AMD Catalyst 13.1. I have removed my .xbmc folder with settings in it so that is not it.
Posts: 464
Joined: Dec 2011
Reputation:
0
Hi,
I'm atm using the standard xbmc builds from the ppa - will I have advantages with hwaccel for my Intel iGPU if using the xvba build over the standard build ?
In the first post it's all about AMD GPUs, but since the thread is called "XBMC Xvba for .. /Intel GPUs" I thought it could be useful for Intel iGPUs too ?!?
Greetz
LastCoder
Posts: 7,650
Joined: Jun 2011
Reputation:
287
it is. Besides Xvba and a complete VDPAU rewrite, this branch features player buffering, proper X support(multi screen, xrandr) and some other improvements. Although its the least noticeable on intel, there are still improvements.
Posts: 13
Joined: Jul 2010
Reputation:
0
Hello and thank you for this wonderful piece of software!
I've followed the guide and have my E350 setup up and running git builds. Only issue I have currently:
After some idle time, when my TV (connected via hdmi) goes to sleep, xbmc goes to 100% cpu usage (for 1 core).
Unfortunately this causes high temps in my fanless setup and a lot of power consumption. Any ideas what might be causing this?
Thanks.
Posts: 23,376
Joined: Aug 2011
Reputation:
1,089
fritsch
Team-Kodi Developer
Posts: 23,376
Please read back and make sure you are running:
xorg 1.12 (inlcluding Ubuntu Precise): fglrx 12.10
xorg 1.13 (starting with Ubuntu Quantal): fglrx 12.9Quantal Edition.
Every driver newer than those cause 100% CPU load on one core.
Try to change the screensaver to the black one.
As you are running git builds - make sure you rebuild, fernetmenta has found an important fix two days ago concerning the beloved ASIC hang.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.