• 1
  • 132
  • 133
  • 134(current)
  • 135
  • 136
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
(2015-11-09, 08:55)fritsch Wrote:
(2015-11-09, 01:09)ilovethakush Wrote:
(2015-11-09, 00:04)schmoko Wrote: This was a constant flickering. The UI was near unusable and video was unwatchable.

Just to update on this issue (in case anyone else experiences it.) Based on everyone's feedback, I decided this was probably a thermal issue and moved the Chromebox out of the cabinet it was in and away from other electronic devices. This fixed the flickering.

I'm guessing the GPU runs a bit hotter with the VAAPI changes, and hence the issue went away when I rolled back to vanilla OpenElec. I'm willing to keep the box out in the open for better playback and colors.

Fritsch,

If you think that running hotter than normal is unexpected behavior let me know and I can try capturing logs or lmsensors data.

Ian.

Yes I think running hotter than normal is unexpected behavior, but considering you had it locked up in a cabinet, it may not be all that unexpected. Why would you put a computer with fans and air paths in a cabinet?

Just to be clear. I'm running the EGL build and if anything, my box is actually quieter and cooler than it was on previous versions of openelec.

It runs cooler (!) even up to 20 degrees on my passively cooled system. As we do not have to copy the outputsurfaces but can render them directly. What could "heat it up" for you is, that you perhaps did not use Lanczos 3 Optimized for upscaling before, as by default 720p was upscaled via bilinear only ...

Changing the fan settings in bios helped to fix my flickering problems as well. Although temps were within specs it still gave problems. Now it runs 10C cooler at 52-62 degrees during/after movie playback. It could be less if I would move it to another place I think.
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
(2015-11-08, 21:59)fritsch Wrote: No idea ... you are the kernel expert :-)

Try:
OUTPUT=`xrandr -q | sed '/ connected/!d;s/ .*//;q'`
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Full"
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Video 16:235 pass-through"
xrandr -display :0 --output $OUTPUT --off ; xrandr -display :0 --output $OUTPUT --auto
/usr/bin/kodi --standalone
Kind of strange but it seems to work :-)
Thanks! To keep things together I'll put it in the message about my kernel.
Reply
@fritsch - I like to share my experince within Jarvis,
until last weekend I was updating daily and it was based on #1 post of this Thread within Ubuntu 15.04 and Kernel up to 4.1.10
at this stage I was wondering how stable it was running even without the known "full freeze bug" on my BYT and of course within the limitation my Celeron has..

Anyhow I did a complete fresh installation on last saturday again following #1 post and habve now Ubuntu 15.10 & Kernel 4.2.0-17-generic
I faced 2 issues #1 the "Full freeze" hit me asap and frequently & #2 which is new for me is to have a kodi crash log in the middle of the night when kodi was not in use - just idle, unforunately without debug enabled :-(

For #1 - I will test now Kernel v4.3-wily or step back to v4.1.12-wily to compare the stability again
For #2 the last log entry is from 22:19 but the crash log has as timestamp 00:39. there is also a big file at /var/crash/ _usr_lib_kodi_kodi.bin.1000.crash ~17MB

As I know here the mandatory Logs: otherwise = no issue :-)
dpkg -l |grep mesa | pastebinit - http://paste.ubuntu.com/13209966/
DISPLAY=:0 vainfo - http://paste.ubuntu.com/13209973/
kodi.log - http://paste.ubuntu.com/13209980/
crash log - pastebinit - http://paste.ubuntu.com/13209987/
dmesg - http://paste.ubuntu.com/13210001/
AS Rock Beebox * Kodi 17.0-RC2 * Ubuntu 16.04 LTS
Reply
The BYT issue has nothing to do with kodi - nothing at all.

You can try: http://fritsch.fruehberger.net/kernel/?C=M;O=D on top there are two files with -bt1 in name (headers and image) that use a patch to change BYT's way of using the turbo.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
thanks fritsch for fast response - I will test it right now this kernel
AS Rock Beebox * Kodi 17.0-RC2 * Ubuntu 16.04 LTS
Reply
Hi.

I must say, I really enjoy the work that has been put into this, both by you and by Matt to make such an easy and powerful experience setting up the Chromebox with OpenELEC. Many thanks for that.

I do have one issue though. I can't get any sound when playing video's from youtube. There are a few stream's from retrospect that doesn't work and a few that does.
My setup: Chromebox -> CEC-adapter -> Pioneer AVR -> TV using HDMI and CEC all the way.
I have tried all different kinds of settings under the Audio category, using fixed 44.1khz sample rate, optimized and best matched. When gathering the logs I was using Best match and passthrough for all options except AC3 according to the support list from Pioneer.
I couldn't upload vainfo since OpenELEC didn't want to recognise the command and instead throws "-sh: vainfo: not found".

Log files:
dmesg: http://sprunge.us/HRRL
kodi.log: http://sprunge.us/NDOQ
journalctl: http://sprunge.us/LQeS

Just forgot to mention, I installed the Chrombox with OpenELEC 5.0.8, then upgraded to stock 6.0 and it is now running 6.0.95-fritsch and the problem has been there with all versions. I also tried reinstalling the youtube add-on.
Reply
fritsch, have a chromebox user who's seeing high CPU / low FPS when playing back some local 1080p/h264 content. Happened with the official 5.95.5 beta, and still happening with 6.0.0 as well as the 6.0.95 EGL build. I had him do a full reset and verified that all video settings are correct. Debug log below, has lots of ffmpeg errors. Any insight is appreciated Smile

http://pastebin.com/7hQcCDkT
Reply
@MattDevo: In that log a full DB scanning is running - so I don't wonder.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-11-09, 20:49)JBir Wrote: Hi.

I must say, I really enjoy the work that has been put into this, both by you and by Matt to make such an easy and powerful experience setting up the Chromebox with OpenELEC. Many thanks for that.

I do have one issue though. I can't get any sound when playing video's from youtube. There are a few stream's from retrospect that doesn't work and a few that does.
My setup: Chromebox -> CEC-adapter -> Pioneer AVR -> TV using HDMI and CEC all the way.
I have tried all different kinds of settings under the Audio category, using fixed 44.1khz sample rate, optimized and best matched. When gathering the logs I was using Best match and passthrough for all options except AC3 according to the support list from Pioneer.
I couldn't upload vainfo since OpenELEC didn't want to recognise the command and instead throws "-sh: vainfo: not found".

Log files:
dmesg: http://sprunge.us/HRRL
kodi.log: http://sprunge.us/NDOQ
journalctl: http://sprunge.us/LQeS

Just forgot to mention, I installed the Chrombox with OpenELEC 5.0.8, then upgraded to stock 6.0 and it is now running 6.0.95-fritsch and the problem has been there with all versions. I also tried reinstalling the youtube add-on.

Known issue with shitty AVRs since a long time. Be it Pioneer, Yamaha or whatever - the issue is only happening with 44.1 khz and a refreshrate > 30 hz, e.g. 1080p60 - here is the upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=75038

Subscribe and tell them: Ey guys it's not yet fixed for me with kernel 4.3.0

As a shortterm workaround I added a patch to OE some time ago to overrule AudioEngine, put this to /storage/.config/advancedsettings.xml
Code:
<advancedsettings>
<audio>
<minimumsamplerate>48000</minimumsamplerate>
</audio>
</advancedsettings>

Edit: If you see in that bugreport I asked Jani if he can specify which patches fixing this issue. I hope he will come back to us - of not, we need to retest with kernel 4.4 and see if it's working.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Concerning the log of MattDevo: Yeah, that's the pain when running an outdated technology "preview" - this get_buffer error was fixed long ago by Fernet in his master branch .. for what it's worth I picked it.

Edit: https://github.com/fritsch/OpenELEC.tv/c...de31feR209
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Hi fritsch,
tried your EGL Builds and also the official 6.0 on my Haswell Build - G1840 with Asrock B85M-ITX and have one Issue:
No Poweroff after Shutdown every second shutdown:

Image

2015-11-09 - 21:29:35 - OE 6.0 Official - Logfile: log-2015-11-09-20.31.07

#############################################

2015-11-09 - 21:49:00 - OE 6.0.95 fritsch - worked
21:51 - freeze - Logfile: log-2015-11-09-20.52.47

#############################################

OpenELEC Jarvis build #1107: Generic Milhouse
22:12 - ok
22:14 - freeze - Logs: log-2015-11-09-21.19.26
Image

Logs ->

Do you have an Idea what to try or what debugging Options would be useful in this case?

Edit1: Same on 5.0.8 - 1st Shutdown ok, 2nd Freeze
Edit2: Same on 4.2.1 - maybe i shoult try without tevii s471? But the Card worked perfect on OE 4.0.6 on my previous Board DH77EB
| myHTPC |
Reply
(2015-11-09, 10:30)fritsch Wrote: Kernel 4.4 looks promissing. Check what the drm maintainer said when doing the PR :-) it's on lkml.

Ah, I discovered this. Is it what you are referring to?

Once I get everything set up I will let you know how it goes.
Reply
(2015-11-10, 02:28)grantonstar Wrote:
(2015-11-09, 10:30)fritsch Wrote: Kernel 4.4 looks promissing. Check what the drm maintainer said when doing the PR :-) it's on lkml.

Ah, I discovered this. Is it what you are referring to?

Once I get everything set up I will let you know how it goes.

No.
Quote:I also had the accidental misfortune to have access to a Skylake on my
desk for a few days, and I've had to encourage Intel to try harder, which
seems to be happening now

via: http://lkml.iu.edu/hypermail/linux/kerne...00311.html
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-11-09, 23:28)-DDD- Wrote: Hi fritsch,
tried your EGL Builds and also the official 6.0 on my Haswell Build - G1840 with Asrock B85M-ITX and have one Issue:
No Poweroff after Shutdown every second shutdown:

Image

2015-11-09 - 21:29:35 - OE 6.0 Official - Logfile: log-2015-11-09-20.31.07
journalctl http://sprunge.us/RVYK
dmesg http://sprunge.us/QLNG
kodi.old http://sprunge.us/dDAW
vainfo - not found

#############################################

2015-11-09 - 21:49:00 - OE 6.0.95 fritsch - worked
21:51 - freeze - Logfile: log-2015-11-09-20.52.47

#############################################

OpenELEC Jarvis build #1107: Generic Milhouse
22:12 - ok
22:14 - freeze - Logs: log-2015-11-09-21.19.26
Image

Logs -> https://goo.gl/DhdD0v

Do you have an Idea what to try or what debugging Options would be useful in this case?

Edit1: Same on 5.0.8 - 1st Shutdown ok, 2nd Freeze
Edit2: Same on 4.2.1 - maybe i shoult try without tevii s471? But the Card worked perfect on OE 4.0.6 on my previous Board DH77EB

Have seen that once, too on my N3150 - but only when I had connected a flirc USB device. Can you retry with all USB stuff unplugged?

Edit: Btw. the logs you posted are with official OpenELEC - not with my 4.3.0 kernel - so post that issue to the OE forum, please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
There are logs from official oe, yours and milhouse in the goo.gl link.
But i will try later without the k400 usb device, thanks!
| myHTPC |
Reply
  • 1
  • 132
  • 133
  • 134(current)
  • 135
  • 136
  • 342

Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18