• 1
  • 53
  • 54
  • 55(current)
  • 56
  • 57
  • 128
Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04
For those that try to build the fix, make sure to pick it up on master - if you want to keep 1.3.2 as a base at least pick: http://cgit.freedesktop.org/vaapi/intel-...626fc0b901 additionally.

Or more easily: http://paste.ubuntu.com/7960845/
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2014-08-05, 14:23)fritsch Wrote: For those that try to build the fix, make sure to pick it up on master - if you want to keep 1.3.2 as a base at least pick: http://cgit.freedesktop.org/vaapi/intel-...626fc0b901 additionally.

Or more easily: http://paste.ubuntu.com/7960845/

fixed libva and i965 driver for trusty are in my vaapi ppa: https://launchpad.net/~wsnipex/+archive/ubuntu/vaapi
Thank you very much!
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
I suddenly get tearing, without any changes. All options are still according to the first post. Only change is that I do not switch the refresh rate, because I always end up with 59 hz. So I pinned it to 50.

Are there any tricks I can try?
How about providing the relevant logfiles?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2014-08-06, 08:41)fritsch Wrote: How about providing the relevant logfiles?

Nice trick !
(2014-08-06, 08:41)fritsch Wrote: How about providing the relevant logfiles?

Here you go:
http://paste.ubuntu.com/7971600/

EDIT:
I forgot to mention that I also had several "crashes" where the picture would freeze but the sound continues (and xbmc/kodi still reacts on keypresses). But I didn't find the time to analyze them... Strange...

EDIT2:
Got a log from the last crash, but I disabled the debugging, maybe it is helpful nontheless. I have to wait for the next 2 crashes to get a full debug log:
http://paste.ubuntu.com/7972796/
wsnipex has built new packages of the libva-driver-intel in his vaapi repository. That fixes the gpu hang with the Joe_Sample.mkv which resulted by non existing support for phantom frames. The new package handles those frames with less artifacts.

Code:
sudo apt-add-repository ppa:wsnipex/vaapi
sudo apt-get update
sudo apt-get dist-upgrade

Thanks very much, again :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Do you have any ideas about the tearing or the crashes? I submitted the gpu crash log to freedesktop.org, as they request.

Thanks in advance...
I cannot reproduce. Try OpenELEC from an USB stick, if that is working it's something on your side. Busy with real work.

Concerning the GPU hang, add the wsnipex vaapi ppa and update your intel-drivers.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2014-08-05, 14:23)fritsch Wrote: For those that try to build the fix, make sure to pick it up on master
I can confirm that the patch fixes the bug:
https://bugs.freedesktop.org/show_bug.cgi?id=81447#c17
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
No, it does not - I just replied you on the bugtracker - you need the relevant ML patch in order to succesfully play that sample till the end. Wsnipex has packaged it within his vaapi ppa.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Sometimes it happens that xbmc just crashes when i am trying to play livetv. I assume that the stream is not very 'clean' at the beginning but before that it has never crashed i am seeing this lately lets say last month.

Here are debug and crashlog:
http://pastebin.com/iD9F8wF9
Crashlog:
http://pastebin.com/BZLc7bas
Don't use tvheadend - if it does not know the screen dimensions it just sends width = height = 0;

You can workaround it by using: https://github.com/FernetMenta/xbmc/issu...t-51034469 - that will most likely crash elsewhere then :-)

Edit: In your case it sends garbage:
Quote:06:30:00 T:140690169038592 ERROR: Previous line repeats 1 times.
06:30:00 T:140690169038592 ERROR: ffmpeg[FB8C8700]: [h264] number of reference frames (0+4) exceeds max (3; probably corrupt input), discarding one
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Now i have another crashlog with iptv simple addon. It crashes even with tvheadend disabled.

http://pastebin.com/LhnSgxiK
  • 1
  • 53
  • 54
  • 55(current)
  • 56
  • 57
  • 128

Logout Mark Read Team Forum Stats Members Help
VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.0416