Posts by Da Flex

You have to use the username root to successfully login.

Generally spoken, whenever safe mode appears, login by SSH, and enter the reboot command.

Hopefully everything runs fine after that reboot.

Then grab available log files from /storage/.kodi/temp to find the cause of the crash.

The interesting log files after reboot are kodi.old.log and kodi_crashlog_<your_current_date>.log.

Read here about logging on LE.

Your current log says, you have an NFS error:

2019-12-15 12:17:16.452 T:140247249708800   ERROR: Failed to open(//Seagate_Expansion_Drive_2_3/Kodi addons/Logo/) opendir call failed with "NFS: Lookup of /Seagate_Expansion_Drive_2_3/Kodi addons/Logo failed with NFS3ERR_NOENT(-2)"
2019-12-15 12:17:16.452 T:140247249708800   ERROR: GetDirectory - Error getting nfs://10.0.0.60/nfs/Seagate_Expansion_Drive_2_3/Kodi addons/Logo/
2019-12-15 12:17:16.459 T:140247249708800   ERROR: Failed to open(//Seagate_Expansion_Drive_2_3/Kodi addons/Logo/) opendir call failed with "NFS: Lookup of /Seagate_Expansion_Drive_2_3/Kodi addons/Logo failed with NFS3ERR_NOENT(-2)"
2019-12-15 12:17:16.459 T:140247249708800   ERROR: GetDirectory - Error getting nfs://10.0.0.60/nfs/Seagate_Expansion_Drive_2_3/Kodi addons/Logo/

Quote from liam666

Then everything Worked!. (Irserver needed to be started Before LCDProc)

BUT.... The Remote seems abit slow, when im Navigating up, down left or right in menus , and say press down 2 times fast, kodi would only register one key press? on windows OS, it didnt do this?

LCDProc shows errors at the log. Do you get better IR response if you disable LCDProc?

Thanks. Read here about log files. Post the link to the log.

You can't expect answers if you don't give answers. That's a fair game in my eyes.

At least a log file is needed to say anything.

I had a similar issue on my RPi 3B+: The picture was darker than regular TV. After switching to a better PSU, the picture is as bright as TV. This is still a mystery to me, because HDMI is digital, and digital has no strong and weak signals. Probably it's about signals before HDMI.

Tell us details about your hardware.

Which PC / NUC do you use?

Which IR receiver do you use? (adapter or built-in)

What's the complete model name of your remote control?

Does the remote control work with other OS'es, like Windows?

Suggested solution: Buy an HDMI audio splitter, and go audio-only (optical S/PDIF) from splitter to AVR.

Looks like HDMI does the negotiation for the signal chain, and chooses the best mode for all devices.

If you hardcode the mode, it will have no effect, because you have one device, which is not compatible to the selected HDMI mode.

Quote from liam666

Ive been using LibreElec 8.0.1 as used in the thread (in an attempt to follow it exactly)

Please update to LE 9.2, and try again. So you can be sure that older issues have been fixed, and we get a common starting point to solve open issues.

Using config.txt is the right way to hardcode a resolution. Please verify this values:

Quote from Ack3r

hdmi_group=1

hdmi_mode=97

According to this, the values might be wrong.

Probably possible, but not a good idea. Read here.

I never heard about this issue from other users, so my guess is missing wattage for the adapter. Try a different PSU solution for your system, like explicit adapter powering.

The kodi.old.log is the one you should post after crash and reboot. Read here about logging on LE.

Where is the movie located, local or server?

How do you play the movie, by using Mediathekview add-on?

Has Mediathekview an installation dependency to the MySQL connector add-on?

Which settings have you made at the Mediathekview add-on?

Which settings have you made at the MySQL connector add-on?

PS: Don't forget to provide a complete log.

What do you do on LE to trigger those MySQL calls?

Quote from peter0815

So I guess that some forgotten edid is not the problem.

I was expecting such result. You're right, the log doesn't write facts about the crash.

Kodi had issues with ION before, and maybe they have to do the same fix for LE 9.2 again. Read here.

So it's probably a problem at the kernel, and I can't help on that level of developement. Write a bug report.

Quote from peter0815

But maybe some of this information left inside my installation.

You can use EDID commands to go back to vanilla state.