Posts by Da Flex

Quote from peter0815

Is it possible to update to v9.2 and go back to v9.02 via the LibreElec update dialog?

I did a downgrade from LE 9.1.x to 9.0.2 once by using the GUI. No problems. Should work with 9.2, too.

2019-12-03 18:48:34.848 T:140645189416704   DEBUG: CAESinkALSA - HDMI device "hdmi:CARD=NVidia,DEV=0" may be unconnected (no ELD data)
2019-12-03 18:48:34.875 T:140645189416704   DEBUG: CAESinkALSA - HDMI device "hdmi:CARD=NVidia,DEV=2" may be unconnected (no ELD data)
2019-12-03 18:48:34.888 T:140645189416704   DEBUG: CAESinkALSA - HDMI device "hdmi:CARD=NVidia,DEV=3" may be unconnected (no ELD data)

Does it crash when you have no HDMI devices connected?

We have good reasons to ask for complete logs only.

Read here to learn how to provide a link to a log.

Especially the end of the log might help. The snippet doesn't tell the story to me.

Do you have the shared data on an external drive? If yes, then probably your file manager will not follow symlinks. LE creates symlinks for each external drive to generate Linux mount points.

Quote from bite_your_idols

I don't know what setting I toggled or what happened but now netflix videos have very poor quality... but surprise! hyperion works ok with them... I disabled resolution limit in both netflix and inputstream addons but still very low quality video stream...

Pardon the interruption. Your team mate HiassofT came up with a solid theory about missing RAM. That would explain your issues.

Using the HDMI splitter might be easier, but that's your choice. In the digital world there should be no weak and strong signal, so I guess it's a timing issue. I wish we had a tool to explicitly send HDMI commands from LE. Then you could send a wake-up-from-suspend signal, and see what happens.

Use command line (ssh root@<LIBRE_ELEC_IP>) or PuTTY instead.

Quote from blueribb

Oh well. I'm in a phone queue waiting for a return call from Yamaha Tech Assistance.

I know such situation - global phenomene.

If they have no answer, go the NUC -> TV way again, and add an HDMI audio splitter. It should split HD audio (optical) for your new receiver, and it's not expansive.

Quote from blueribb

I'm going to call Yamaha Tech Support to see if they have a fix.

Good idea. Especially because your old receiver was Yamaha, too, so you can name an in-house reference device.

I don't think LE has options to solve this. Can you change the HDMI cabling to NUC -> TV? That's my setup, too, with optical S/PDIF audio from TV to receiver.

Could you describe your HDMI cabling please?

If it's NUC -> receiver -> TV, then your new receiver might block (don't update) HDMI communication after suspend.

2019-11-29 12:31:15.857 T:2858812272   ERROR: ffmpeg[AA660370]: [matroska,webm] EBML header parsing failed
2019-11-29 12:31:15.857 T:2858812272   ERROR: Open - Error, could not open file smb://ben/mass2/Video/jaun.mkv
2019-11-29 12:31:15.857 T:2858812272   ERROR: ExtractThumb - Error creating demuxer

Maybe the source file has errors, and re-encoding it by ffmpeg fixes it. Go into analysis of the source file.

OK, if it's reproducable, then feel free to write a bug report.

Write step-by-step until you reach the bug, and provide all other necessary data.

I never had this bug on my RPi 3B+.

I don't think it's a bug. Most people simply forget to use root as their user name. Do ssh root@<YOUR_LIBREELEC_IP> from console.

I assume you haven't found any fitting add-on.

Some people run Java on LE, and then you could run jNut. Or use docker, which might be more efficient.

Untested, but try this variant:

#/bin/sh

IDLE_SHUTDOWN_ALLOWED_LAST_STATE=-1

while true
do
    KODI_RUNNING=`ps -A | grep kodi.bin | grep -v grep | wc -l`

    if [ 1 == $KODI_RUNNING ] ; then
        SSH_ACTIVE=`netstat -tnpa | grep 'tcp.*:22.*ESTABLISHED.*' | wc -l`
        NFS_ACTIVE=`netstat -tnpa | grep 'tcp.*:111.*ESTABLISHED.*' | wc -l`
        SMB_ACTIVE=`netstat -tnpa | grep 'tcp.*:445.*ESTABLISHED.*' | wc -l`  
        [ $SSH_ACTIVE -gt 0 -o $NFS_ACTIVE -gt 0 -o $SMB_ACTIVE -gt 0 ] && IDLE_SHUTDOWN_ALLOWED=1 || IDLE_SHUTDOWN_ALLOWED=0 

        if [ $IDLE_SHUTDOWN_ALLOWED_LAST_STATE != $IDLE_SHUTDOWN_ALLOWED ] ; then
            IDLE_SHUTDOWN_ALLOWED_LAST_STATE=$IDLE_SHUTDOWN_ALLOWED
            kodi-send --action="AllowIdleShutdown"
            if [ 0 == $IDLE_SHUTDOWN_ALLOWED ] ; then
                kodi-send --action="InhibitIdleShutdown(false)"
            else
                kodi-send --action="InhibitIdleShutdown(true)"
                IDLE_SHUTDOWN_ALLOWED_LAST_STATE=-1
            fi
        fi
    fi
    sleep 60
done

Sorry for my misunderstanding of virtualization technology and virtual machine.

Quote from robmcc83

Think I'll have a play with some bios settings for now see if anything changes.

Good idea. Check the audio options, too.

Quote from robmcc83

virtualization is what VM has something to do with which stands for virtual machine.

So you use a virtual machine to run LE. I don't use VM, but there is a chance that it does an encapsulation of hardware / software, which may lead to the "system mode" (see above).

I think LE programming will stay as close as possible on hardware level to get max. performance, so I don't expect a fix by update.

If you have more than one OS (LE + X), try Grub boot manager, and don't use VM for LE anymore.

Quote from robmcc83

Ive done a little research on these 2 and appears 1 is related to the amd vega 8 graphics that is built into my amd ryzen 3 2200g, and the other is related to VM.

What does VM mean, and which error triggers it?