Posts by mglae
-
-
Disable VAAPI MPEG2 acceleration in Settings->Player->Videos, you may have to increase the settings level to "Expert" to be able to do this.
-
You still need NFS/iSCSI/NBD for mounting /storage, I don't see the use case for an additional method.
-
Sorry, /storage/.config/sleep.d/ seems not to be created by default. Start with mkdir -p /storage/.config/sleep.d
Edit: 20-custom-sleep.sh is still installed an should work. Your link is three years old.
-
-
Yes, that was more brainstorming ...
It look like that toggling the refresh rate does initialize the audio driver again, Let's try to automate this.
If this script works, then what would happen to the pop-up question ?
The script is returning to the original refresh rate, there is no need to save anything new.
Please post the output of xrandr after a clean boot.
-
Then a work around may be to find the matching xrandr parameters. A most likely on your device not working sample is:
Code/usr/bin/xrandr -display :0 --output HDMI-0 --mode 1920x1080 --rate 50 /usr/bin/xrandr -display :0 --output HDMI-0 --mode 1920x1080 --rate 60
and add them to the "post" section of a /storage/.config/sleep.d/*.power script.
-
can this also be done as a squashfs file without nfs share(export)
No, the feature Is not implemented.
-
Try disabling VAAPI MPEG2 acceleration, you may have to increase the settings level to "Expert" to be able to do this.
-
systemctl status ssh
reports: Unit ssh.service could not be found.
The service name is sshd.
[...] however it's not accepting the default SSH password [...]
Add fextmode again.
-
-
Have you already tried a Custom EDID?
-
-
-
There is no code change between 9.1.502 and 9.2.
"sed: write error" is printed because /dev/kmsg refuse to been written with more than 1024 bytes at once (more than 4500 in your case).
The error is harmless, just as the fsck error. I see two options:
- Ignore the error and wait for 9.2.1
- Boot another Linux system (i.e. from USB stick) and use fsck.fat to fix the error on file system UUID=5DDB-A25D
-
The message is from here.
Please post the output of paste /dev/fsck.log
-
Just a hint but no solution: looks like a network configuration issue. There is only a link local address detected first and it takes 95 seconds to get the real one.
CodeApr 11 12:28:40 LibreELEC connmand[460]: eth0 {newlink} index 2 operstate 6 <UP> [...] Apr 11 12:29:25 LibreELEC connmand[460]: eth0 {add} address 169.254.145.126/16 label eth0 family 2 [...] Apr 11 12:30:15 LibreELEC connmand[460]: eth0 {del} address 169.254.145.126/16 label eth0 Apr 11 12:30:15 LibreELEC connmand[460]: eth0 {del} route 169.254.0.0 gw 0.0.0.0 scope 253 <LINK> Apr 11 12:30:15 LibreELEC connmand[460]: eth0 {add} address 192.168.1.4/24 label eth0 family 2 [...]
-
Adding textmode to your command line will result in booting to a shell. You can use it to check for any errors.