Posts by Samui

hi dtech,

thank you very much for your fast response.

Here the link in the forum with a basic discussion about how to compile the addon

[SOLVED] Building MakeMkv within LE

The makemkv addon was already in times of openelec generated. In the makemkv forum there is a howto posted.

Escalade, 5Schatten and several others built it already for Krypton and older Leia Releases of Libreelec. Unfortunately this addons are not working with the newer releases anymore.

Makemkv for arm based devices is available.

MakeMKV on Raspberry PI (ARM) - Page 2 - www.makemkv.com

Hi dtech,

your image is working great on my Mecool KII Pro - thank you very much for your work!

Would it be possible for you to compile the makemkv addon to this release.

I connected my external BDROM to the box for use it as BD Player also, but many of my original BDs

are protected.

It's a very nice image but unfortunately the same issue with the PVR - VDR VNSI Client again. When the service is activated the continious reboot into Kodi is starting and after several tries Retroelec is booting into the safe mode. By the way, the FFMPEG addon is also not working. Same error code which means 'Error 127'. Seems the FFMPEG binary cannot get executed.

Hi Escalade,

i noticed another thing with the generic image. The addon ffmpeg-tools is not working if i try to use the ffmpeg binary inside.

The error code is 127.

Yes Sir - fantastic!

escalade

Upgraded my RPI4 right now with your latest image.

Thank you very much!

@AN

It's never a good idea to mix up two different distributions. Just make a clean fresh install, maybe on another storage device.

What you can do is to copy the files from inside kodi afterwards to the new installation. But not the language files, the skin and the "packages" directory - kodi will otherwise boot into the safe mode.

You are absolutely right, i am so sorry about the wrong logfiles. That was my fault!

But right now i installed your latest release. With this one it is suddenly working!! You are the BEST!!

But there must be a difference between this Image now - RetroELEC-Generic.x86_64-9.2-devel-20200424193105.img -

and the other 2 images. Because they are crashing!!

Also the release for the RPI4 before this one - RetroELEC-RPi4.arm-9.2-devel-20200423233226.img - crashed,

when i activated the VDR VNSI Client. By the same way like the generic images before.

Unfortunately i had no time until now to install and check this actual - RetroELEC-RPi4.arm-9.2-devel-20200423233226.img - release

on my RPI 4 now but will do it tomorrow.

Attached the complete needed logfiles from the working and the crashing image.

EDIT:

Installed right now the latest image for my RPI4 and enabled the VDR VNSI CLIENT for connect to my Asrock with your

latest - working - Generic Image. Some seconds after enabled the client, the system is crashing and restarting Kodi in a loop.

After disabled the client again, no trouble anymore. Maybe you can insert the changes like in the new generic image if possible there, too?

Hi Escalade,

I also installed your newest generic build right now, too. It's really fantastic with the additional desktop mode.

Because i asked the question before and provided the logfiles also, i would like to ask you again. In your older releases were the dvb drivers included. Are they still in the actual builds or what else could be the reason for the issues i am having now with the TVHeadend and VDR?

escalade

i am using an ASROCK J4105 with your generic image, too.. There is a DVB-S2 card installed. With the dmesg command i can see that my card is recognized.

With the VDR addon, the system is crashing and rebooting in a loop, because the VDR VNSI Client cannot connect to the Backend.

It shows connect - disconnect continious and after several tries the system is crashing. If i am installing the TVHeadend, i even cannot

access it with my browser via the port 9981.

Maybe you can give me a little support for this issue? Attached some logfiles.

@JA

This is the same problem happened to me. When i checked the file system on the sdcard in Linux, the F2FS partition was shown with an exclamation mark. There was no way to extend it. So i deleted the partition and replaced it with the standard ext4 partition and replaced the given UUID in the config file. After this the system was booting well.

Edit: Installed the F2FS Tools in Linux and formated the partition again. Also had to replace the UUID again.

escalade

Thank you very much for your very fast reply with the solution for my small problem

Dear Escalade,

right now i installed your last image for my RPI 4. It's really awsome! Thank you very much for your hard work since so many years!

Btw there are 2 things i found

1. The installation procedure doesn't create the Storage Partition correctly. So i had to delete the unfinished partition on my sdcard and create it by myself. After this i had to correct the UUID in the relating init file. After this everything was working like a charme.

2. In the desktop mode i am not able to change the sound output for my device. In Kodi the sound is working very well.

Well done - installed right now - thx a lot

No problem. Better making it one time right - could you please send me the link to the release before or the last beta?

Thx a lot - your support is great and fast as always waiting for can download your new build, otherwise no TV tonight

LibreELEC:~ # dmesg |paste

http://ix.io/1x8i

LibreELEC:~ #

--> no any error message during booting up

Sorry, but i still have the same problem. With this build, my soundcard is not found anymore.

Here is what i tried for solving that issue with the Putty console, but still no success

login as: root

[email protected]'s password:

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

# LibreELEC 9.0 Reborn Remix #

# https://goo.gl/temeuw #

# based on LibreELEC – Just enough OS for KODI #

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

LibreELEC (5schatten): RR-201852-52323f1 (Generic.x86_64)

LibreELEC:~ # aplay -L

null

Discard all samples (playback) or generate zero samples (capture)

LibreELEC:~ # ^C

LibreELEC:~ # pulseaudio --start

W: [pulseaudio] main.c: This program is not intended to be run as root (unless - -system is specified).

LibreELEC:~ # pulseaudio --check

LibreELEC:~ # lsmod | grep snd

snd_hda_codec_realtek 94208 0

snd_hda_codec_generic 73728 1 snd_hda_codec_realtek

snd_hda_intel 40960 0

snd_soc_skl 98304 0

snd_soc_hdac_hda 24576 1 snd_soc_skl

snd_hda_ext_core 24576 2 snd_soc_hdac_hda,snd_soc_skl

snd_hda_codec 106496 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_code c_realtek,snd_soc_hdac_hda

snd_hda_core 69632 7 snd_hda_codec_generic,snd_hda_intel,snd_hda_ext_ core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl

snd_soc_skl_ipc 53248 1 snd_soc_skl

snd_soc_acpi_intel_match 24576 1 snd_soc_skl

snd_soc_sst_dsp 28672 1 snd_soc_skl_ipc

snd_soc_sst_ipc 20480 1 snd_soc_skl_ipc

snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_soc_skl

snd_hwdep 16384 1 snd_hda_codec

LibreELEC:~ # dmesg | egrep -i "(alsa|sound)"

[ 0.703776] Advanced Linux Sound Architecture Driver Initialized.

[ 2.123457] ALSA device list:

[ 2.123458] No soundcards found.

LibreELEC:~ # aplay --list-devices

aplay: device_list:272: no soundcards found...

After installation of your newest release based on Kernel 4.20 i realized, that there is only the Audio Option Bluetooth Audio (Pulseaudio) on my Asrock J4205 possible. So i have no more sound over HDMI means no more sound at all.