Posts by Da Flex

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.

https://wiki.libreelec.tv/development/build-basics

Quote from sIRwa2

I can run the gparted live usb? just a fsck i guess?

That's good, so you get the option to repair a partition instantly.

sIRwa2 Thanks for the log. I don't see any errors at the end of it. Usually unmounting a device fails, if it contains errors.

Can you download a tool to check all your internal partitions? (boot start from USB stick or CD)

I also had an empty list on LE 11.0.0 at first. I had to switch to update channel 10, and then back to 11 to fill the list with LE 11.0.1.

I've been informed the developers about that issue, but no reply. I hope it will be fixed at LE 12.

If the LSPCon driver is bad, we can't rely on that device list. Something is fishy on it.

Maybe it's best to open the box, and identify all chips.

I also want to see kodi.log, generated by pastekodi.

Quote from mglae

Da Flex HDMI2 seems to be used not DPx. No DiplayPort-to-HDMI adapter involved.

Yes, but the user only has one VGA, and one HDMI port. This makes me think, a converter like this is involved:

- DisplayPort 1 -> VGA

- DisplayPort 2 -> HDMI

(DiplayPort is the protocol standard here)

It's very likely that your hardware uses a DiplayPort-to-HDMI adapter (LSPCon chip):

14.605] (II) intel(0): Output DP1 has no monitor section
14.605] (II) intel(0): Enabled output DP1
14.606] (II) intel(0): Output HDMI1 has no monitor section
14.606] (II) intel(0): Enabled output HDMI1
14.606] (II) intel(0): Output DP2 has no monitor section
14.606] (II) intel(0): Enabled output DP2
14.606] (II) intel(0): Output HDMI2 has no monitor section
14.606] (II) intel(0): Enabled output HDMI2

Linux drivers for such chips have known issues. My suggestion: garbage.

PS: Maybe it's worth to try the other HDMI ports of your TV.

Congrats! So I was on the right path to test the hardware.

Can you use the first HDMI port for audio again?

Quote from criss28

Hi crisofter13 which model did you buy, 2GB/16GB or 4GB/32GB? I saw that there are some differences in wifi between the two, is the wifi chipset recognized by LE?

heitbaum has just fixed TX6 WiFi on 8822bs and 8822cs chips. This should be available in the next nighly builds.

Nice! So stay with Generic-legacy 11, and one of the next official updates will fix your error message. Problem solved.