Thanks for that description, though it has not much to do with the howto I was giving here :-) which is based on a minimal Ubuntu setup. If it works for you, everything is fine.
The "Tear Free" Option causes harm to the way kodi / xbmc syncs - so if you see random effects, disable that again.
(2015-02-06, 09:28)fritsch Wrote: [ -> ]Thanks for that description, though it has not much to do with the howto I was giving here :-) which is based on a minimal Ubuntu setup. If it works for you, everything is fine.
The "Tear Free" Option causes harm to the way kodi / xbmc syncs - so if you see random effects, disable that again.
Oh sorry. I read the last 10 pages but not the first page
Actually I meant to post in the dedicated Chromebox thread but somehow got it confused with this. Anyways I did read someone mentioning Kodibuntu so I thought I'd chime in with my experience. I have not experienced any problems using the tear free option, and I need to have this enabled for netflix and other videos in google chrome/normal desktop session.
Hello,
I've recently installed my NUC I3 with KODIBUNTU
Could you tell me which Settings or packages i can install un order to get the best experience in image quality ?
All steps in first page or just a subset?
Thanks in advance
just the settings from 1st post. Everything else is already done in kodibuntu
Was the Intel GPU hang fix included in OE 5.0? It uses Kernel 3.17.7.
If so, then it is still broken. Prefer VAAPI render method is unchecked.
Code:
[10872.414354] ------------[ cut here ]------------
[10872.414373] WARNING: CPU: 1 PID: 758 at drivers/gpu/drm/i915/intel_display.c:3361 intel_crtc_wait_for_pending_flips+0xd9/0x130()
[10872.414377] Modules linked in: fuse rtsx_usb_ms snd_hda_codec_hdmi rtsx_usb_sdmmc memstick snd_hda_codec_realtek snd_hda_codec_generic intel_powerclamp intel_rapl snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm
[10872.414403] CPU: 1 PID: 758 Comm: Xorg Not tainted 3.17.7 #1
[10872.414407] Hardware name: ZOTAC ZBOX-BI320/ZBOX-BI320, BIOS B239P102 05/19/2014
[10872.414411] 0000000000000006 ffffffff81789568 0000000000000000 ffffffff81031956
[10872.414417] ffffffff81488da2 ffff8802162da000 0000000000000000 ffff8800d7338150
[10872.414422] ffff8800d72f8800 ffffffff81488da2 ffffffff00000000 ffff88020a6916e0
[10872.414428] Call Trace:
[10872.414439] [<ffffffff81789568>] ? dump_stack+0x41/0x51
[10872.414449] [<ffffffff81031956>] ? warn_slowpath_common+0x6f/0x84
[10872.414456] [<ffffffff81488da2>] ? intel_crtc_wait_for_pending_flips+0xd9/0x130
[10872.414461] [<ffffffff81488da2>] ? intel_crtc_wait_for_pending_flips+0xd9/0x130
[10872.414470] [<ffffffff81054c8d>] ? finish_wait+0x5d/0x5d
[10872.414477] [<ffffffff8148e97e>] ? intel_crtc_disable_planes+0x28/0x119
[10872.414483] [<ffffffff8148f529>] ? haswell_crtc_disable+0x41/0x24f
[10872.414489] [<ffffffff8148aae8>] ? __intel_set_mode+0x725/0x11b5
[10872.414497] [<ffffffff812ea370>] ? idr_get_empty_slot+0x1bd/0x2cf
[10872.414504] [<ffffffff814910ce>] ? intel_set_mode+0xb/0x22
[10872.414510] [<ffffffff81491d45>] ? intel_crtc_set_config+0x7b6/0xaaa
[10872.414519] [<ffffffff81397fe6>] ? drm_mode_set_config_internal+0x4d/0xb8
[10872.414526] [<ffffffff8139aa98>] ? drm_mode_setcrtc+0x3a6/0x44e
[10872.414534] [<ffffffff81390374>] ? drm_ioctl+0x331/0x3be
[10872.414540] [<ffffffff8139a6f2>] ? drm_mode_setplane+0x15a/0x15a
[10872.414549] [<ffffffff810cb699>] ? do_vfs_ioctl+0x34b/0x3fd
[10872.414556] [<ffffffff810c0e1a>] ? __sb_end_write+0x24/0x52
[10872.414564] [<ffffffff810600b2>] ? rcu_eqs_exit_common.isra.46+0x10/0xb7
[10872.414570] [<ffffffff810cb784>] ? SyS_ioctl+0x39/0x55
[10872.414577] [<ffffffff81791589>] ? tracesys+0xd0/0xd5
[10872.414582] ---[ end trace 78aa802331cc4953 ]---
That's something else - the "cut here" was not for us ... Pastebin the full dmesg.
Better: Directly go to bugs.freedesktop.org and open a new bug under DRM/Intel and provide the dmesg and describe how you did that.
The "Prefer VAAPI Render" can be turned on again. This bug was really fixed.
(2015-02-08, 21:54)fritsch Wrote: [ -> ]Better: Directly go to bugs.freedesktop.org and open a new bug under DRM/Intel and provide the dmesg and describe how you did that.
It happened while streaming live tv from the internet. So it's basically non-reproducible. But the symptoms were similar to the old Intel GPU hang - audio keeps going while video freezes.
Hardware was a Chromebox clone that supports Windows - Zotac BI320 using 2957U.
Seems like there are other folks over in the Chromebox install/script support thread also reporting GPU hangs.
Do you think it's worthwhile to file a bug if I don't have steps to reproduce it? Otherwise, I'll keep an eye on it and report back if I see it again on local media.
The old GPU hang was something really special, with a totally different trace. Your issue really has absolutely nothing to do with the gpu hang - there is not even a gpu hang in your kernel log.
Hi there, what are the best settings on the latest OE on NUC DN2820 for Live TV deinterlacing? Since 5.0 I see some options in deinterlacing are gone and there new ones.And from Acceleration menu SW Filter is gone too..
Why not just read the first page? It's all mentioned there.
Baytrail:
Deinterlacing: Auto
Deinterlacing-Method: Bob or VAAPI-BOB
Scaling: Bilinear.
(2015-02-09, 22:47)fritsch Wrote: [ -> ]Why not just read the first page? It's all mentioned there.
Baytrail:
Deinterlacing: Auto
Deinterlacing-Method: Bob or VAAPI-BOB
Scaling: Bilinear.
Because as you told me before 2820 gpu is even weaker then other bailtrails and I wasnt sure the settings from the first page applies to this NUC.
Should i also use this settings :
System ->Video->Acceleration:
Enable HQ Scalers for scaling above: 20%
Allow hardware acceleration (VDPAU): off
Allow hardware acceleration (VAAPI): On
Use Mpeg-2 VAAPI: Yes
Use Mpeg-4 VAAPI: if you like
UseVC-1 VAAPI: off (this causes vc1 interlaced to segfault, when on)
Adjust Refreshrate to match video: On
Thanks again