XBMC Community Forum
How to Install XBMC PVR Xvba for AMD/Nvidia/Intel GPUs - Printable Version

+- 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: How to Install XBMC PVR Xvba for AMD/Nvidia/Intel GPUs (/showthread.php?tid=116996)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220

- grad - 2011-12-20 19:49

pjohn07 Wrote:I'm wondering if there is something else I need to do for lightdm and to get XBMC to start. I'm fairly well versed in cmd line rhel linux, but all of the ubuntu X-win stuff is very new to me.

I fought a lot with lightdm yesterday when transitioning from 11.04 to 11.10 and found that doing this:

Quote:# echo "/usr/sbin/lightdm" > /etc/X11/default-display-manager
# dpkg-reconfigure lightdm

as root seemed to help for start issues. Your problem maybe totally different, but it's worth a try.

- clank - 2011-12-20 22:57

First of all I would like to thank you for writing up this guide, it's awesome to finally have an AMD build where I can play 24fps vids correctly.

I was just wondering if you could tell me the configure string you use when building the source? As I would like to build this with libcec enabled.

Either that or if you would like to build it with libcec enabled on the PPA?? That would be tops.

- fritsch - 2011-12-20 23:01

clank Wrote:First of all I would like to thank you for writing up this guide, it's awesome to finally have an AMD build where I can play 24fps vids correctly.

I was just wondering if you could tell me the configure string you use when building the source? As I would like to build this with libcec enabled.

Either that or if you would like to build it with libcec enabled on the PPA?? That would be tops.

I think if you nicely ask wsnipex, he will include this :-)

- fritsch - 2011-12-20 23:05

grad Wrote:xorg.conf: http://pastebin.com/H2VwYfnh
xbmc.log: http://pastebin.com/LaWqLN0e
/etc/ati/amdpcsdb: http://pastebin.com/jXph8cTG

There are really a lot of settings in xorg.conf. Could you backup this file an retest with:
sudo aticonfig --initial

For your log I see that you see builds with the Reference Clock Stuff. There are still some bugs, we, Fernetmenta especially, try to track down.

If you use wsnipex ppa packages (not the testing ppa). These are normally more stable, cause they are tested more extensive.

Thanks

- wsnipex - 2011-12-20 23:47

clank Wrote:First of all I would like to thank you for writing up this guide, it's awesome to finally have an AMD build where I can play 24fps vids correctly.

I was just wondering if you could tell me the configure string you use when building the source? As I would like to build this with libcec enabled.

Either that or if you would like to build it with libcec enabled on the PPA?? That would be tops.

When I first started to build the packages, it wouldn't compile with libcec on launchpad, so I disabled it. I might look into it again, when I find time.

Here is the configure line:
--prefix=/usr --docdir=/usr/share/doc/xbmc \
--enable-xvba \
--disable-vdpau \
--disable-crystalhd \
--disable-vdadecoder \
--disable-vtbdecoder \
--disable-tegra \
--disable-profiling \
--enable-joystick \
--enable-xrandr \
--disable-ccache \
--enable-pulse \
--enable-rtmp \
--enable-ffmpeg-libvorbis \
--disable-mid \
--enable-hal \
--enable-avahi \
--enable-asap-codec \
--enable-webserver \
--enable-optical-drive \
--enable-texturepacker \
--enable-nfs \
--disable-libcec \
--enable-afpclient \
--disable-airtunes \
--disable-debug \
--enable-optimizations

- grad - 2011-12-21 00:03

fritsch Wrote:There are really a lot of settings in xorg.conf. Could you backup this file an retest with:
sudo aticonfig --initial

For your log I see that you see builds with the Reference Clock Stuff. There are still some bugs, we, Fernetmenta especially, try to track down.

If you use wsnipex ppa packages (not the testing ppa). These are normally more stable, cause they are tested more extensive.

Thanks

Well I came from the initial aticonfig and added switches when things werent working, cause but I'll try this. As for the build: I am using the std wsnipex ppa! *confused*

- fritsch - 2011-12-21 00:09

grad Wrote:Well I came from the initial aticonfig and added switches when things werent working, cause but I'll try this. As for the build: I am using the std wsnipex ppa! *confused*

Sorry for confusing you. Everything should be okay. Lets see what will happen after --initial.

- grad - 2011-12-21 09:04

fritsch Wrote:Sorry for confusing you. Everything should be okay. Lets see what will happen after --initial.

Thanks for unconfusing me Smile Unfortunately though, things remain the same with --initial. The error is now pretty consistently showing when switching back(!) from the correctly rendered and mode-switched fullscreen to the menu. So the first mode switch works alright, but it doesn't properly switch back. Since I definitely saw the reverse effect at some time also, I'm rather thinking this is some nasty glitch somewhere. (FWIW, I also once tried the xbmc option to insert a pause upon mode switching, but that didn't help either.)

To make my situation worse, I tried the Android remote control app last night and now I'm completely hooked to XBMC. Pure awesomeness :-)

- fritsch - 2011-12-21 09:31

grad Wrote:Thanks for unconfusing me Smile Unfortunately though, things remain the same with --initial. The error is now pretty consistently showing when switching back(!) from the correctly rendered and mode-switched fullscreen to the menu. So the first mode switch works alright, but it doesn't properly switch back. Since I definitely saw the reverse effect at some time also, I'm rather thinking this is some nasty glitch somewhere. (FWIW, I also once tried the xbmc option to insert a pause upon mode switching, but that didn't help either.)

To make my situation worse, I tried the Android remote control app last night and now I'm completely hooked to XBMC. Pure awesomeness :-)

Hard to debug. Let`s see if some setting is wrong somewhere in the deep of the X stuff. Could you try booting with the following Live Image?:
http://xbmcfreak.binkey.nl/XBMCbuntu-v14.zip

It is only to test modesetting issues. If this succeeds, we have to look what software version, etc. you are using.

Bye

Edit: Problem is being worked on - just wait some hours, i think testing the live iso is not needed then.

- wsnipex - 2011-12-21 11:28

grad Wrote:Thanks for unconfusing me Smile Unfortunately though, things remain the same with --initial. The error is now pretty consistently showing when switching back(!) from the correctly rendered and mode-switched fullscreen to the menu. So the first mode switch works alright, but it doesn't properly switch back. Since I definitely saw the reverse effect at some time also, I'm rather thinking this is some nasty glitch somewhere. (FWIW, I also once tried the xbmc option to insert a pause upon mode switching, but that didn't help either.)

To make my situation worse, I tried the Android remote control app last night and now I'm completely hooked to XBMC. Pure awesomeness :-)

This is the same behavior I'm seeing on my system.
for me there are 2 workarounds:
1.) stop the video manually before it ends
2.) toggle to window mode and back