Posts by mglae

Please check file name again.

Put mt7662_rom_patch.bin into /storage/.config/firmware and reboot. It will be automatically linked to /var/lib/firmware.

You may have to rename mt7662u_rom_patch.bin from linux-firmware if there is no other firmware file.

Please type journalctl|paste and post the link after a fresh reboot and authentication try.

Missing firmware, try

mkdir -p /storage/.config/firmware/mediatek
wget -P /storage/.config/firmware/mediatek https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/mt7610u.bin

and reboot.

Audio quickstart guide - Official Kodi Wiki

Use TV (AC3) and add DTS.

yubby  Meganiekje Sorry, wrong thread. LE 8.2.5/Kodi 17 do not support VAAPI on AMD.

Add the radeon.lockup_timeout=xxxxx kernel parameter, see this post.

To create a USB stick installation just type "run" on first boot of the installer image (or select the grub menu entry on EFI32 devices).

I expect a Grub boot menu.

But the shift key detection is not implemented in LE, my fault.

With the BIOS being activated by <esc> finding the right timing for pressing the key may be difficult.

Creating a LE 9 installation stick and booting from USB looks like the easiest test environment to use.

I see. timeout=0, the boot menu is not visible by default. Try to hold the <shift> key at boot or press the <Esc> key to activate it.

Navigate to the boot entry and press <e> to edit. The changes are not stored.

Or create an installation stick and boot from USB.

Quote from elliottmc

So it looks as though the code in this commit has been removed at some point and for some reason.

The code is still there.

Furthermore the update does not alter the existing boot configuration. You can try to <e>dit the boot entry from the grub boot menu and replace "quiet" with "debug textmode" to see boot messages.

These tools are available:

# ls /storage/.kodi/addons/virtual.dvb-tools/bin/
azap          dvblast       dvbtraffic    szap          tzap
blindscan-s2  dvbnet        femon         szap-s2       w_scan
czap          dvbscan       mumudvb       t2scan        zap
dvbdate       dvbsnoop      scan          tune-s2

In the LE file system usually everything below /storage is writable.

Please use your favorite web search, it's long ago that I did use one of these tools.

Try the *zap* tools from dvb-tools addon matching your DVB system.

Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
Apr 28 05:47:03 LibreELEC kernel: SQUASHFS error: squashfs_read_data failed to read block 0x73a23cf

Exchange your SD card.

nslookup = name server lookup- the tool is only querying DNS servers.

Use getent hosts <name> to query NSS.

Thanks. So it can theoretical generate errors anywhere when building 8.2.5.

I first thoughed it's only an openssl issue because of creating the wrong LD_LIBRARY_PATH while compiling, i.e. makefile.shared#l98

Quote from vpeter

I assume some change come with host system updates. Because 8.2.5 was build without a problem when it was current.

Yes, but misusing LD_LIBRARY_PATH in openssl 1.0.* makefiles is the error.

Looking at the official openssl.spec you see they are aware of the issue:

LD_LIBRARY_PATH=`pwd` make
LD_LIBRARY_PATH=`pwd` make rehash
LD_LIBRARY_PATH=`pwd` make test

BTW: I don't understand why your fix is working, IMO LD_LIBRARY_PATH must not be empty.

Starting with openssl 1.1.0 the bug is fixed so LibreELEC master is safe.

But LE 9.0* is still using openssl 1.0.2X and the failure can pop up any time without LD_LIBRARY_PATH work around.