Posts by ghtester

Quote from Ralph91

so people will stop giving stupid replies.

A stupid question ---> stupid reply... Sorry...

Google is your friend: Four Ways to get Instant Access to a Terminal in Linux

To make sure the file is executable, run the command: chmod +x LibreELEC.USB-SD.Creator.Linux-64bit.bin

It's possible your SD card is bad and turned out to 'read-only mode'.

If possible, test it under Windows machine with SD card reader, use DISKPART in command line ( How to use DiskPart to clean and format drive not working on Windows 10 | Windows Central ), reformat it with single NTFS partition and copy some files there. Then eject the SD card safely and put it again to test if it's working (the new files are still there) or not.

You may also use an USB key to install and run LE on RPi 4B instead of SD card.

I can't test on LE 9.2.6 anymore as I am running LE 10 Nightly for a long time but I did not have any Audio issues on official LE 9.2.6 build for RPi 4B in past. And the error messages from aplay are strange. The piano2.wav plays without issue on my LE 10 and this is what you should see (and hear the melody of course):

# aplay piano2.wav

Playing WAVE 'piano2.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo

So it looks to me that your LE installation is still corrupted - it might be due to improper / unofficial installation image used or an issue with your SD card etc... Use only official builds from here: Raspberry Pi 4 – LibreELEC or a latest LE 10 Nightly build from here: LibreELEC-RPi4.arm-10.0-nightly-20210604-f6b7711.img.gz

You may also try to install LE to USB key instead of SD card to eliminate possible incompatibility (it may also depend on the bootloader version you are running - see here for details: RE: Boot from SSD instructions )

So what's the result of aplay the .wav file now?

It looks you screwed up the LE installation with some bad plugin / Add-on installed.

Try to install the LE from scratch without any suspicious plugins / Add-ons and the Audio should work properly.

Try from SSH console (hopefully the file exists on LE version you are using - if not, search for some .wav):

systemctl stop kodi

aplay /var/media/root/usr/share/scratch/Media/Sounds/Instruments/SpookyString.wav

systemctl start kodi

Use another external drive, properly powered.

Try to install the latest LE 10 nightly: LibreELEC-RPi4.arm-10.0-nightly-20210604-f6b7711.img.gz

Did you reboot RPi afterwards?

Kodi does not search for latest available RPi's firmware releases so it depends on LE build you have installed. If you use a stable but old LE release (9.2.6), also the RPi bootloader offered is obsolete.

See for instance here:

Post

RE: Boot from SSD instructions

Nothing special should be necessary if your RPi 4B does not have a very obsolete bootloader.

Just write a LE image to your external SSD, connect it to RPi 4B and try to boot.

if it won't work, try the same with SD card ( this should definitely work ), then check the VL805 USB firmware & RPi bootloader versions and upgrade them to latest available (check the release notes here).

How to check the CURRENT versions: rpi-eeprom-update

VL805 release should be: 00138a1

BOOTLOADER should be: Thu Apr 29…

ghtester

April 3, 2021 at 3:20 PM

Quote from dippes

Yes everything up to date.

No it is NOT - at least your bootloader is a bit outdated, the latest stable release is dated 2021-04-29 and beta 2021-05-19 (rpi-eeprom/release-notes.md at master · raspberrypi/rpi-eeprom · GitHub).

It looks your portable SSD is not detected, it could be due to incompatibility with RPi's bootloader or due to insufficient power.

Please note that RPi 4B has a quite low power limit on USB ports (even though you have a good power supply) so an external power for attached external disks is a good option.

Also try connecting the SSD to USB 2 ports.

Try to connect the dongle(s) with an USB extension cable(s) or with an USB hub. Perhaps there's a high-frequency noise from RPi (or from the USB3 key) which breaks the dongle's wireless communication so it may be better if you move them as far as possible from RPi's board. Also try to replace batteries with fresh ones.

OK, so it looks that OpenVPN does not set the variables as expected by the update-resolv-conf.sh script or the script does not see the enviroment's variables. So you need to check the OpenVPN documentantion if the expected variables are still valid and set:

foreign_option_1

foreign_option_2

foreign_option_3

foreign_option_4

script_type

I suppose if you put at start of the update-resolv-conf.sh script something like that:

echo $foreign_option_1 > /tmp/testfile.txt

echo $foreign_option_2 > /tmp/testfile.txt

echo $script_type >> /tmp/testfile.txt

Then try to connect VPN and then check the /tmp/testfile.txt, it will be perhaps empty and you need to discover why.

Maybe the first line of script should be #!/usr/bin/env sh instead of #!/usr/bin/env bash ?

As I don't use OpenVPN and don't have installed that Add-on, I can't test nor say more...

Also check this thread, maybe the solution is there: Creating "update-resolv-conf.sh" equivalent to plug openvpn DNS leaks

Quote from svenfoo

Could the decoding artifacts be caused by under-voltage?

In your case it's not likely (if the all facts described earlier are true). I suppose it's the driver issue.

OK, it's a bit complex for me to understand what's wrong with the script. But you may try to edit the update-resolv-conf.sh to this simplified form below and give it a try.

#!/usr/bin/env bash
# Parses DHCP options from openvpn to update resolv.conf
# To use set as 'up' and 'down' script in your openvpn *.conf:
# up  /storage/.kodi/userdata/addon_data/service.vpn.manager/update-resolv-conf.sh
# down  /storage/.kodi/userdata/addon_data/service.vpn.manager/update-resolv-conf.sh

# Licensed under the GNU GPL.  See /usr/share/common-licenses/GPL.
# Example envs set from openvpn:
# foreign_option_1='dhcp-option DNS 193.43.27.132'
# foreign_option_2='dhcp-option DNS 193.43.27.133'
# foreign_option_3='dhcp-option DOMAIN be.bnc.ch'
# foreign_option_4='dhcp-option DOMAIN-SEARCH bnc.local'
resolvpath=/run/connman

case $script_type in
up)
  mv $resolvpath/resolv.conf /tmp/.
  for optionname in ${!foreign_option_*} ; do
    option="${!optionname}"
    part1=$(echo "$option" | cut -d " " -f 1)
    if [ "$part1" == "dhcp-option" ] ; then
      part2=$(echo "$option" | cut -d " " -f 2)
      part3=$(echo "$option" | cut -d " " -f 3)
      if [ "$part2" == "DNS" ] ; then
         echo nameserver $part3 >> $resolvpath/resolv.conf
      fi
      if [ "$part2" == "DOMAIN" ] ; then
         echo domain $part3 >> $resolvpath/resolv.conf
      fi
      if [ "$part2" == "DOMAIN-SEARCH" ] ; then
         echo search $part3 >> $resolvpath/resolv.conf
      fi
   fi
  done
  ;;
down)
  mv /tmp/resolv.conf $resolvpath/.
  ;;
esac
exit 0

This is just a part of the file which does not say much. Put the whole file to pastebin.com and share a link here.

With LE 10 Nightly (Index of /) when the display is connected only to HDMI1 on RPi 4B, both audio & video works fine on it.

The same happens when the display is connected only to HDMI0.

When both HDMI0 and HDMI1 ports are occupied (by active HDMI devices), Kodi displays video on HDMI0 only and audio can be switched to any HDMI output.