Posts by Da Flex

I would like to watch DVD's by using the Raspberry Pi (LibreELEC 8.90.005), which is connected to the TV. Problem: The DVD drive is mounted on my PC (Linux).

I know that VLC can create an A/V stream, which can be received and played by other VLC devices. I already did that with a mobile device, connected to the TV. It is not perfect, because DVD navigation has to be done from the source device, but it's good enough for my needs.

Is it possible to receive local A/V streams created by VLC with LibreELEC?

Is it possible to completely remote control a DVD drive mounted on another PC (including DVD navigation)?

It doesn't takes many reboots to reproduce the bug.

Here is the kodi.log at log level 1, read from MicroSD card right after the crash.

Quote from DaVu

That should enable debug logging but without that annoying overlay on the screen.

Thank you. I will do this.

I created a bug report for this.

Hardware: Raspberry Pi, Model 3B+

Software: LibreELEC 8.90.005

Log File: kodi.log

Bug Appearing: shutdown (from SSH) while playing a video stream, TV HDMI modes are not detected right anymore after shutdown

See this post for details and guisettings.xml.

I created a bug report for this issue.

Hardware: Raspberry Pi, Model 3B+

Software: LibreELEC 8.90.005

Log File: kodi.log

Bug Appearing: reboot or shutdown triggered from LibreELEC menu, does not appear every time

At least two forum users and me got that bug. See this thread for details.

I had that bug pretty often in the meantime with LibreELEC 8.90.005. I hope my log (see above) will help to fix it. If any admin needs more data to create an official bug report, I'll try to deliver.

The bug appeared again.

I am still using the same LibreELEC installation 8.90.005, which had a DVI session before. The first runs after going back to HDMI worked fine: no initial VGA mode, and all HDMI modes detected. I guess my theory is wrong: a DVI session is not the reason for the bug.

The bug appeared after a shutdown while playing a video stream (MLB TV). I guess it breaks the GUI settings, and forces the initial VGA mode on any further boot. I trigger the shutdown (command "shutdown -h now") by using my power button (see python script). Results when shutting down from SSH should be the same.

Here are the desired file contents to do a bug report:

Taken from a running DVI session:

(just to complete the task, I think it doesn't matter for the bug)

guisettings.xml

kodi.log

Taken from a running HDMI session:

(initial VGA mode, not all proper HDMI modes for TV found)

guisettings.xml

kodi.log

I see 2 error lines. The DBus error is normal, I have it on my log file, too. So, it's the last two lines of your log. Having no display connected will not crash a standard Linux desktop. Investigate what the "CApplication" does.

I have a reboot/shutdown problem too.

Raspberry Pi image: LibreELEC-RPi2.arm-8.90.005.img

Log after reboot freeze (taken from MicroSD card after plugging off the device): /storage/.kodi/temp/kodi.log

I can't reproduce the bug with LibreELEC-RPi2.arm-8.90.005.img.

I guess the bug is only on Milhouse builds, and not on the latest stable LibreELEC build.

I don't want to do more tests for now, because a DVI session is not my default scenario.

I made it by using GPIO 3 (Pin 5) and it's opposite Ground Pin 6. Read my thread: Support for the Pi-Desktop Power Button?

If your board must use GPIO 3 and GPIO 17, you can set GPIO 17 to Low (Ground) in the python script ("off-button.py", see link above).

Insert this lines after line 8 of "off-button.py":

ground_pin_number=17
GPIO.setup(ground_pin_number, GPIO.OUT)
GPIO.output(ground_pin_number, False)

I have found a hot fix for this bug, but it's ugly.

The problem is that it always boots in VGA mode after a DVI session. Later on boot process - if you are lucky - it will switch to the selected user HDMI resolution. I think the initial VGA mode is the reason for a bad detection of HDMI modes. Not all possible TV resolutions and/or refresh rates will be found.

A "Soft Reset" or a "Hard Reset" made from the system settings menu will not solve problem - initial VGA mode will stay.

The only solution for me was to rewrite my MicroSD card with a new LibreELEC image. That will make the initial HDMI boot resolution (720p / 50Hz) work again. All possible TV resolutions and refresh rates will be found, too.

Maybe somebody should report this as an official bug.

I had a resolution problem too after using LibreELEC at Raspberry Pi (3B+) for some tests on a DVI monitor. noemin, which hardware do you use?

After a DVI session it had problems to use the (previously found and used) HDMI resolutions. The Raspberry Pi was booting in VGA mode on my HDMI TV. Some reboots, resolution changes and firmware updates (not sure what it was) solved the problem. Now the HDMI resolutions of the TV are detected right again, and it starts with the selected mode.

I think it's a bug on LibreELEC. It doesn't detect the proper resolutions when changing from DVI back to HDMI.

Success! GPIO3 power on/off triggers the expected results now!

Thank you very much, Iridium!

I can use a cheap case now, and install my own power button - problem solved.

Still an error at line 6:

File "/storage/scripts/off-button.py", line 6
    import sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
                          ^
SyntaxError: invalid syntax

Quote from Iridium

This might also help

I followed those instructions and did that:

- set config.txt back to original (no "dtoverlay=gpio-shutdown")

- installed "Raspberry Pi Tools" from repository

- created the "autostart.sh" and "off-button.py"

- set both files as executable (chmod +x)

GPIO3 now still works as power on (it always does), but the next trigger to power off does nothing.

The python script ("off-button.py") looks OK:

- the necessary lib from "Raspberry Pi Tools" exists (/storage/.kodi/addons/virtual.rpi-tools/lib/GPIO.so)

- the pin mode "GPIO.BCM" is correct for my model 3b+ with GPIO3 power button

Any hints?

PS: The command line response when starting from ssh ("sh /storage/.config/autostart.sh") is this:

Traceback (most recent call last):
  File "/storage/scripts/off-button.py", line 6, in <module>
    import syss
ImportError: No module named syss