Posts by Da Flex

For the audio problem you should find a setup where it's not out-of-sync (different LE version, different video codec...).

With the current facts it's impossible to find a cause.

Zynth! Generic and Generic-legacy have different repos, so you can't find Chrome at Generic repo.

Switch to Generic-legacy from SSH login:

cd /storage/.update
wget https://releases.libreelec.tv/LibreELEC-Generic-legacy.x86_64-11.0.1.img.gz
reboot

I think sleep should appear before xrandr:

cat >/storage/.config/sleep.d/99-toggle_rate.power <<'EOF'
#!/bin/sh
case "$1" in
    post)
        sleep 2
        xrandr -display :0 --output DP1 --mode 1920x1080 --rate 59.94
        sleep 2
        xrandr -display :0 --output DP1 --mode 1920x1080 --rate 60
        ;;
esac
EOF

Make sure it's executable: chmod +x /storage/.config/sleep.d/99-toggle_rate.power

Congrats!

With that knowledge you can go back to Generic (non-Legacy).

Quote from blueribb

Please read post #20

Thanks . Then it's probably a different directory on RPi.

I think sleep.d is outdated, and sleep.conf.d is used by current LE versions. However, you can try both directories.

Read post #4 again.

• You will need 99-toggle_rate.power. That script does the actual resolution switch.
• xrandr makes no sense, delete it (rm /storage/.config/sleep.conf.d/xrandr).
• I'm not sure whether you need 20-custom-sleep.sh. Try with and without it.

The only difference to post #4 is that you have to edit 99-toggle_rate.power, and replace HDMI1 by DP1. You can use the nano editor for that.

What happens when you start the script manually from SSH terminal?

/storage/.config/sleep.conf.d/99-toggle_rate.power

PS: If not already done, make it executable first:

chmod +x /storage/.config/sleep.conf.d/99-toggle_rate.power

Quote from blueribb

If I try the Generic Legacy (which still contains xrandr), will my script still be there?

Yes. I thought you're already using it.

cd /storage/.update
wget https://releases.libreelec.tv/LibreELEC-Generic-legacy.x86_64-11.0.1.img.gz
reboot

Yep, that looks good. If you're already in the right directory, the file name is enough for cat / nano.

You have to use the full path to the files, so it's:

cat /storage/.config/sleep.conf.d/20-custom-sleep.sh
cat /storage/.config/sleep.conf.d/99-toggle_rate.power

Maybe it's worth to give them explicit execution rights:

chmod +x /storage/.config/sleep.conf.d/20-custom-sleep.sh
chmod +x /storage/.config/sleep.conf.d/99-toggle_rate.power

You can see the file rights by ls -l.

Please check the content of the new files by nano <FILENAME>, or by cat <FILENAME>.

99-toggle_rate.power:

#!/bin/sh
case "$1" in
   post)
     xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 59.94
     xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 60
     ;;
esac

20-custom-sleep.sh:

#!/bin/sh

. /etc/profile

for script in $HOME/.config/sleep.conf.d/*.power; do
  if [ -f $script ]; then
    progress "running custom sleep script $script ($@)..."
    sh $script $@
  fi
done

exit 0

Eventually 20-custom-sleep.sh is not needed, so also try without it:

rm /storage/.config/sleep.conf.d/20-custom-sleep.sh
reboot

You missed the point before config:

Quote

cd /storage/config/sleep.d

Please stay focused.

If needed, create a new directory by mkdir /storage/.config/sleep.conf.d.

Use rm -rf sleep.d to delete the directory and its content.

Quote

LibreELEC:~/.config/sleep.conf.d # cat >/storage/.config/sleep.d/99-toggle_rate.

power <<'EOF'

> #!/bin/sh

> case "$1" in

> post)

> xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 59.94

> xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 60

> ;;

> esac

> EOF

LibreELEC:~/.config/sleep.conf.d # ls

Display More

The first line is obviously wrong, because we want to use sleep.conf.d, and not sleep.d as directory. Please copy & paste correctly.

Instructions:

First go to Settings -> System -> Display -> Resolution, and note down your preferred GUI resolution. You will need it later.

On my Rpi (LE 11.0.1), the directory /storage/.config/sleep.conf.d was pre-installed. So I think that's the right one.

Please check whether you have it:

cd /storage/.config
ls

If you don't have it, create it:

mkdir sleep.conf.d

Then delete /storage/.config/sleep.d:

rmdir sleep.d

Then go into the directory, and look what's inside:

cd sleep.conf.d
ls

I have a README and a sleep.conf.sample file inside. For your purpose, you have to add two more files:

• 99-toggle_rate.power
• 20-custom-sleep.sh

To create 99-toggle_rate.power, copy the following code into your SSH terminal, and hit Enter to execute it. Eventually edit the resolutions first, depending on your preferred GUI resolution (see above). To do so, copy the script into an editor of your local OS, and edit both lines. Then copy the result into your SSH terminal, and hit Enter. In case you're trapped in input mode after this (> sign before cursor), type EOF, and hit Enter.

cat >/storage/.config/sleep.conf.d/99-toggle_rate.power <<'EOF'
#!/bin/sh
case "$1" in
   post)
     xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 59.94
     xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 60
     ;;
esac
EOF

After that you should see the new file:

ls

Result:

Quote

99-toggle_rate.power README sleep.conf.sample

To create 20-custom-sleep.sh, copy the following code into your SSH terminal, and hit Enter to execute it:

cat >/storage/.config/sleep.conf.d/20-custom-sleep.sh <<'EOF'
#!/bin/sh

. /etc/profile

for script in $HOME/.config/sleep.conf.d/*.power; do
  if [ -f $script ]; then
    progress "running custom sleep script $script ($@)..."
    sh $script $@
  fi
done

exit 0
EOF

After that you should see the new file:

ls

Result:

Quote

20-custom-sleep.sh README

99-toggle_rate.power sleep.conf.sample

Reboot, and hope that it works.

So you created the /storage/.config/sleep.d directory, and have the 20-custom-sleep.sh script as content, right?

A developer has replied to me. He says, the unmount error of the screenshot is normal, and has nothing to do with our issue.

Instead it's probably an issue with reboot parameters. I'm trying to figure out, how to edit them...

Quote from sIRwa2

Could it be an ssd thing?

Thanks for checking your drive!

I think you're on the right path with the SSD. The OS partition has no errors, so it could be an SSD trim command, or another SSD-specific command, which can't be executed. Probably the SSD driver doesn't work correctly on AMD Ryzen.

Because I'm not familiar with the SSD shutdown procedure of LE, I've informed developers to have a look. Stay tuned.