Posts by mglae

There seem to be issues with mpeg2 acceleration on Intel VAAPI.

Try activating "Expert" Settings Level and disabling "Use MPEG-2 VAAPI" in "Player" - "Videos" settings.

When still not working you can test disabling VAAPI acceleration completely.

This results mostly from different unit prefixes of HDD manufacturers and operating systems.

8TB = 8 * 10^12 B ~ 7.28 * 2^40 B = 7.28TiB

Quote from CGarces

But I get the same results.

What are the "same results"? A constant value or changing low temperatures?

You can install the System Tools addon from the LibreELEC repo and use sensors to have a user friendlier view to the /sys/class/hwmon device values.

Quote from snixel

Only issue I have now is that when I view videos with a width and height of 1920x1080 pixels and aspect ratio 16:9 (shown in MediaInfo) I get black bars on the right and left.

Maybe this?

Quote from LastStarDust

• Then I copied the patch file in the packages/linux/patches folder

• It compiled correctly but still no WOL support as if the patch wasn't applied during compiling.

Maybe I am putting the patch in the wrong folder or the patch is in the wrong format ... could you tell?

The build system is surprisingly pedantic in patch file naming in some cases. For the main kernel patch directory the mask is linux-*.patch

[...]
[ 8.695605] DDBridge: probe of 0000:01:00.0 failed with error -1
[ 8.698407] BUG: unable to handle kernel paging request at ffffc90001062a50
[ 8.698454] IP: [<ffffffff8119a694>] sysfs_kf_seq_show+0x14/0x120
[ 8.698488] PGD 216c14067
[ 8.698503] PUD 216c15067
[ 8.698516] PMD 215b94067
[ 8.698524] PTE 0
[ 8.698534]
[ 8.698544] Oops: 0000 [#1] SMP
[ 8.698561] Modules linked in: ddbridge(O) imon(O+) intel_powerclamp snd_hda_codec_realtek(+) intel_rapl snd_hda_codec_generic dvb_core(O) snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep nuvoton_cir(O) rc_core(O)
[ 8.698674] CPU: 1 PID: 246 Comm: systemd-journal Tainted: G O 4.9.8 #1
[ 8.698711] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H67M-GE, BIOS P2.10 04/27/2012
[ 8.698758] task: ffff88021446a580 task.stack: ffff8802154a0000
[ 8.698787] RIP: 0010:[<ffffffff8119a694>] [<ffffffff8119a694>] sysfs_kf_seq_show+0x14/0x120
[...]

IMO you need to eliminate the kernel oops before examining any other errors.

I can only guess the cause, but the first oops occurs directly after the failed ddbridge driver initialization ...

Digital devices cards are supported with CvH's digital devices image. Give it a try.

Any errors in /storage/.kodi/temp/kodi.log?

You can get more information by enabling debug logging in /storage/.kodi/userdata/advancedsettings.xml:

<advancedsettings>
<loglevel hide="true">1</loglevel>
</advancedsettings>

Quote from Nicolas

I am using TVHeadend but, the problem is in LE7 that was working flawlessly.
So my guess is that's a problem not dedicated to vdr or TVHeadend it's a general fault/issue?

Yes, it is an issue of current Kodi 17 code. LE7 includes Kodi 16.1 that calls setwakeup.sh correctly.

Quote from Nicolas

So that's another/different problem?
Kodi is shutting down before a timer is getting set?

Yes, according to your log kodi seems to be hanging on shutdown while/after disconnecting VNSI and is killed finally. This is behaviour by design of the LibreELEC kodi SIGTERM implementation.

Kodi will even fail when going further and trying to set the timer because it cannot read its own settings any more.

Quote

Does setting a timestamp (using setwakeup.sh date '+%s' -d '+ 10 minutes') works on your system?
I am getting an error but there is always a timer 5 minutes ahead.
So could you try with 10 minutes pls?

Busybox's "date" does not accept parameters like "+ 10 minutes". You have to use something like

setwakeup.sh $(($(date +%s)+600))

There is not the expected message

DEBUG: CSettingsManager: requested setting (pvrpowermanagement.enabled) was not found.

in your log because Kodi seems to be killed before exit completes.

The functionality can be restored using this Kodi patch. I do create a bug report the next days so it can be fixed upstream.

Quote from de_doener

Kodi Log: gPhY

Thanks for the log. Unfortunately in this special case the shutdown needs to be logged. Please post a full /storage/.kodi/temp/kodi.old.log

Quote from csimai

So here's what I did: 1) copy over the contents of /storage to the flash drive, 2) replace contents of cmdline.txt, and 3) reboot:

Code

# systemctl stop kodi
# rsync -rtv /storage/ /var/media/TV-201702/
# mount -o remount,rw /flash
# nano /flash/cmdline.txt

Unfortunately your rsync line does not copy all content, i.e. symlinks are skipped.

I recommend wiping the USB disk and retry with

rsync -a /storage/ /var/media/TV-201702/

cp /usr/lib/systemd/system/kodi.service /storage/.config/system.d/

and add

Environment=MALLOC_MMAP_THRESHOLD_=32768

No further ideas.

If you are curious enough you may do a binary search on Milhouse's LE Testbuilds to find the starting build with the issue.

Krypton adds dithering to video processing causing higher CPU load.

In worst case you may get 100% CPU load and video stuttering on slower CPUs.

Dithering is enabled by default, your settings level has to be "Expert" to be able to disable it.

You need the build with official Digital Devices drivers: thread-130-post-31085.html#pid31085

If this only occurs in SD mpeg2 videos you my work around the issue by activating expert settings level and disable VAAPI mpeg2 only.

The CPU can easily decode mpeg2 and VAAPI is still used for HD video.

Quote from marc.bau

I'm running tvheadend 4.0 server and tvheadend pvr in this htpc with a digital devices cine s2 card. MB is an zotac atom with nvidia card.

You may try CvH's build with Digital Devices drivers: thread-130-post-31085.html#pid31085