Posts by mglae

There is a thread with a similar issue.

After booting off USB and inserting a SD card please execute:

(dmesg;lsmod;lspci;lsusb)|pastebinit

and post the resulting URL.

The needed driver rtsx_pci_sdmmc is build as module and therefore not available at boot time.

You have to use the USB card reader until the kernel configuration is changed.

I will PR the change and get you informed.

To check if the SD-Card reader is supported in general boot the LE SD card from USB and insert a second SD card to the reader (file system does not matter).

Please post output of dmesg and lsmod.

"Mute" Icon

Quote from apc

There should be an option in Kodi 17 - as there was in 16 - for system-addons-system-dependencies

If you are looking for Manage Dependencies Settings Level has to be Advanced or Expert.

Maybe same joystick/game pad problem:

[SOLVED!] MX3 Air Mouse Remote no functioning

Quote from frankvw

For kodi_crash.log (symlink to kodi_crashlog_20170519182358.log): YXAJ
For kodi_crashlog_20170519182231.log: CgdT

Addon vizualization.wavforhue terminates Kodi:

Thread 1 (Thread 0x74f84000 (LWP 1718)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#1  0x7538d400 in __GI_abort () at abort.c:89
#2  0x66de229c in WavforHue::SaveState(std::string) () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
#3  0x66dee14c in WavforHue_Thread::GetPriorState() () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
#4  0x66ddf418 in Start () from /storage/.kodi/addons/visualization.wavforhue/visualization.wavforhue.so.1.0.0
#5  0x007081c4 in ADDON::CVisualisation::Create(int, int, int, int, void*) ()

Deinstalling the plugin should solve the crashes.

A remote's "devinput KEY_C" event is technically different to a keyboard event.

You need to create your own Lircmap.xml like this:

<lircmap>
<remote device="devinput">
<menu>KEY_C</menu>
...
</remote>
</lircmap>

Quote

I wasn´t able to find out, why only some picons are in the list and some channels without the picons.
Even I don´t understand the system of filenames like e.g. 1_0_1_1_1_9_5A0000_0_0_0.png to research for a solution.

The file names are generated from the channel parameters: vdr-plugin-vnsiserver/vnsiclient.c at master · FernetMenta/vdr-plugin-vnsiserver · GitHub

You can try geting the sources from GitHub - picons/picons-source and generating the picons from your VDR channels.conf. But be warned, I did need some tweaking to get all my DVB-C picons a few months ago.

Try the srp-* file.

Yes, but there are several reports up to Intel Core iX regarding MPEG2 playback like SD Live TV or DVDs.

From the usage view this usually can be solved by disabling the "Use MPEG-2 VAAPI" setting.

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>