FYI: OpenSuse does not power off the system as well.
Posts by Skeeve
-
-
I see. The message only appears after an incomplete shutdown, so I never had this.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL linkThe logging does not work. You see… I think you'd need the power-off logs which seem to be lost when powering on again.
But you may give it a try: https://ix.io/4kb7I tried to run the two log file commands manually and then shutting down. So additionally you might see something in these two logs:
http://ix.io/4kbb -
I haven't had the time yet to debug - sorry.
-
I do not call it. It's a vanilla generic installation I have here.
As far as I understood on other pages, the /storage/.config/shutdown.sh is called by default by the shutdown process, so this error / warning should be expected.
My assumption is: The wyse needs some special shutdown no one knows about So there is no machine-specific shutdown procedure in LibreElec's kernel. I also assume that it's safe, but yet annoying, to power it down manually when the "Power Down" message appears.
-
Too bad…
I have the same issue but didn't see this thread until after I posted: LibreElec on Wyse 5010 does not properly shut down
Just found this: LE 9.95.2 Generic X86_64 error on startup/shutdown
but it's no help either…
-
I installed LibreElec 10.0.2 (previously 9.something) on my Wyse 5010 Thin Client.
Everything seems to work okay except for the shutdown. The system does not power off.
It hangs with:
Code(LibreELEC (official): 10.0.2 242.7689931 [12531: Failed to unmount /flash: Device or resource busy [ 242.7713681 systemd-shutdownt11: Failed to finalize file systems, loop devices, ignoring. 242.9591521 reboot: Power down
I tried journalctl -f via ssh but it doesn't give me a clue what's going wrong. Can anybody please give me some guidance?
journalctl output
Code
Display More-- Journal begins at Sat 2022-12-24 16:13:57 UTC. -- Dec 24 16:14:11 KodiWyse kernel: snd_hda_intel 0000:00:01.1: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: VA-API version 1.11.0 Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: Trying to open /usr/lib/dri/r600_drv_video.so Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: Found init function __vaDriverInit_1_11 Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: va_openDriver() returns 0 Dec 24 16:14:30 KodiWyse systemd[1]: systemd-hostnamed.service: Succeeded. Dec 24 16:16:16 KodiWyse connmand[330]: eth0 {del} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE> Dec 24 16:16:17 KodiWyse connmand[330]: eth0 {add} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE> Dec 24 16:16:25 KodiWyse connmand[330]: eth0 {del} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE> Dec 24 16:17:25 KodiWyse sshd[1195]: Accepted publickey for root from 192.168.192.20 port 54359 ssh2: RSA SHA256:BVwzxOq1/0xWmkucmaDi9a2Xpmq7FyecMMo6+FXkjF4 Dec 24 16:17:50 KodiWyse systemd-logind[317]: System is powering down. Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-modprobe.slice. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Kodi Mediacenter Interface. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target RPC Port Mapper. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Sound Card. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target System Time Synchronized. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target System Time Set. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Timers. Dec 24 16:17:50 KodiWyse systemd[1]: systemd-tmpfiles-clean.timer: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Daily Cleanup of Temporary Directories. Dec 24 16:17:50 KodiWyse systemd[1]: Starting Save random entropy at shutdown... Dec 24 16:17:50 KodiWyse systemd[1]: cpufreq.service: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Set CPU frequency governor and its tunables. Dec 24 16:17:50 KodiWyse systemd[1]: Stopping Kodi Media Center... Dec 24 16:17:50 KodiWyse systemd[1]: ledfix.service: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped LEDfix Service. Dec 24 16:17:50 KodiWyse systemd[1]: Stopping RPC Bind... Dec 24 16:17:50 KodiWyse systemd[1]: Stopping Udevil mount service... Dec 24 16:17:50 KodiWyse systemd[1]: wait-time-sync.service: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Wait for Kernel Time Synchronisation. Dec 24 16:17:50 KodiWyse systemd[1]: [email protected]: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped configure Xorg Server for radeon. Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-xorg\x2dconfigure.slice. Dec 24 16:17:50 KodiWyse systemd[1]: var-media-PHOTOTANK.mount: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Unmounted /var/media/PHOTOTANK. Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 4+0 records in Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 4+0 records out Dec 24 16:17:50 KodiWyse systemd[1]: rpcbind.service: Succeeded. Dec 24 16:17:50 KodiWyse udevil[1205]: udevil: success running umount as current user Dec 24 16:17:50 KodiWyse systemd[1]: Stopped RPC Bind. Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 2048 bytes (2.0KB) copied, 0.000479 seconds, 4.1MB/s Dec 24 16:17:50 KodiWyse systemd[1]: Finished Save random entropy at shutdown. Dec 24 16:17:50 KodiWyse systemd[1]: [email protected]: Succeeded. Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Udevil mount service. Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-udevil\x2dmount.slice. Dec 24 16:17:53 KodiWyse systemd[1]: kodi.service: Succeeded. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi Media Center. Dec 24 16:17:53 KodiWyse systemd[1]: intel-fullrange.service: Succeeded. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped intel switch to full range. Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Kodi user autostart script... Dec 24 16:17:53 KodiWyse systemd[1]: kodi-cleanlogs.service: Succeeded. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi clean debug logs. Dec 24 16:17:53 KodiWyse systemd[1]: Starting Kodi poweroff script... Dec 24 16:17:53 KodiWyse systemd[1]: kodi-autostart.service: Succeeded. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi user autostart script. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped target Graphical Interface. Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Fluxbox Window Manager... Dec 24 16:17:53 KodiWyse sh[1230]: /bin/sh: can't open '/storage/.config/shutdown.sh': No such file or directory Dec 24 16:17:53 KodiWyse systemd[1]: Finished Kodi poweroff script. Dec 24 16:17:53 KodiWyse systemd[1]: windowmanager.service: Succeeded. Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Fluxbox Window Manager. Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Xorg Server... Dec 24 16:17:53 KodiWyse xorg-launch[1109]: (II) Server terminated successfully (0). Closing log file. Connection to kodiwyse closed by remote host. Connection to kodiwyse closed.
-
-
Hi.
I've read about booting a Raspberry Pi from a hard drive.
I followed the steps for allowing boot from USB, changing the power limit for the usb drive and increasing the timeout.
Unfortunately my Raspberry won't boot from my 500GB Hard drive. Booting from a USB stick otoh works.
What can I do to troubleshhot my problem?
You did see that ^^?
I already boot from USB stick fine. -
I have, according to cpuinfo: Raspberry Pi 3 Model B Rev 1.2
The LED on the drive lights up. I can also access it when I connect it after booting LibreElec from a usb stick.
-
Hi.
I've read about booting a Raspberry Pi from a hard drive.
I followed the steps for allowing boot from USB, changing the power limit for the usb drive and increasing the timeout.
Unfortunately my Raspberry won't boot from my 500GB Hard drive. Booting from a USB stick otoh works.
What can I do to troubleshhot my problem?
-
How does this configuration end up here:
Why it's gpio 5 & 6? How could I set my own gpio pins?
It's not gpio 5&6 it's GPIO 3 and ground which happens to be pins 5 & 6 iirc.
Why it's key id 61662 - I have no clue. Must be the work of the devil. It's 3 times the 6
Just kidding. But I really have no clue. I googled and ended up with that solution.
-
Hi!
Is there any chance I can get ScummVM to work on my RasPi 3B with LibreElec Leia?I installed it using the Addon Browser. But when starting I just get the message that it failed to start for unknownreason.
Any hints, tipps, suggestions or information I can provide to find out why it fails?
-
I just gave the Leia Game AddOn some tries, but failed each time.
Scummvm didn‘t even start.
DOS BOX started and left me with a black screen.
Vice 64 (Using IAGL) also started but hung with the loading message.
-
"dtoverlay=gpio-shutdown" on LE 8.95.002 will let the shutdown menu appear, when pressing the power button. Instant off only works by the described scripting.
Thanks to your post and the one by @Iridum I found the solution. Changing the key which is sent helps. See above…
-
If you have the time, could you test gpio-shutdown on the latest LE alpha build Here Tnx.
I did and it works. Here is what I did:
ssh-ed to the system and remounted /flash so that I can change config.txt
Then using my favourite editor (vi) to add the below line to /flash/config.txt below the shown comment.
Code################################################################################ # End of default configuration ################################################################################ dtoverlay=gpio-shutdown
Then I've created the file /storage/.kodi/userdata/keymaps/keyboard.xml to contain:
Finally I did a reboot.
That's it. A button connecting pins 5 & 6 will now shut down your libreelec.
-
This thread is a bit old, but maybe you come back and this will help you: gpio-shutdown alternative for LibreElec 8.2.5
-
Update: Starting with LibreELEC (Leia) v8.95.2 BETA it is possible to use dtoverlay=gpio-shutdown. See further down.
Hi! I felt this area is the most appropriate for what I want to contribute.
I was searching for a way to shut down my libreelec-Raspberry with the touch of a button wired to pins 5 & 6, as I do for my other raspberrys. Unfortunately the same approch, setting dtoverlay=gpio-shutdown in config.txt didn't work.
Another solution I found, invoving autostart and a shutdown.sh yielded very strange results in a not-booting raspberry.
The following approach, seems to work though. Maybe It's not correct so please tell me if I did something wrong.
First create a file "/storage/.config/gpio-shutdown" with the following content:
Bash
Display More#!/bin/bash # monitor GPIO pin X for shutdown signal # export GPIO pin X and set to input with pull-up GPIOPIN=3 echo "$GPIOPIN" > /sys/class/gpio/export echo "in" > /sys/class/gpio/gpio$GPIOPIN/direction # wait for pin to go low while [ true ] ; do if [ "$(cat /sys/class/gpio/gpio$GPIOPIN/value)" == '0' ] ; then echo "Raspberry Pi Shutting Down!" shutdown -h now exit 0 fi sleep 1 done
Make it executable with
Then create a file "/storage/.config/autostart.sh" (or adjust its content accordingly)
Make it also executable, then reboot
How does it work?
The autostart.sh is invoked every time libreelec is booted. It will then start "gpio-shutdown" in the background. This script will check every second whether or not the GPIO3 is connected to GND. As soon as this is dicovered, a "shutdown -h now" is executed and the raspberry will shut down. You'll see the usuall 10 blinks after which you can disconnect.
Another touch of the button which connects GPIO3 to GND will boot up your libreelec.