Posts by Da Flex

LE uses it's own add-on system to install packages. APT is not supported. Fortunately you don't need APT or an install script for this project.

• install the "Raspberry Pi Tools" add-on (provides Python GPIO lib)
• create the folder /storage/.kodi/userdata/scripts
  
• insert this lines between line 4 and 5 of softshut.py:

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')

• put softshut.py into /storage/.kodi/userdata/scripts
  
• create /storage/.config/autostart.sh with this content:

#!/bin/sh

(
    python /storage/.kodi/userdata/scripts/softshut.py
) &

Some advanced users run GParted to format the card by leaving out bad blocks. That's an option to keep it alive, if you invest the effort.

HiassofT You've been answered faster, that's why I double-posted the same facts.

There is no need to extract the image by yourself. Just let the update script do the job. It updates some files. It doesn't installs the complete tar for the Linux partition. All unneeded data will be deleted after the update. At the end you'll get the same result like on GUI update.

Quote from wylda

But when i compared the image file with KODI log, i wonder, why GUI uses TAR archive instead of above image file??

The image file contains data for two partitions. The tar file is the one that contains the update for the Linux partition. The data for the Windows partition isn't needed in your case, because you don't install LE from scratch.

Add this line to config.txt:

hdmi_force_hotplug=1

PS: I'm not sure whether the buggy kodi.log is related to your issue. The cause of your issue could also be a lack of hardware performance. Do you have options to overclock your device? Read here about HEVC and overclocking on RPi.

INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:767:(parse_card) cannot find card '$CARD'
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:392:(snd_func_concat) error evaluating strings
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_concat returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/confmisc.c:1246:(snd_func_refer) error evaluating name
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4568:(_snd_config_evaluate) function snd_func_refer returned error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5047:(snd_config_expand) Evaluate error: No such device
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5014:(snd_config_expand) Unknown parameters CARD=HDMI,DEV=0
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5014:(snd_config_expand) Unknown parameters CARD=HDMI
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4898:(parse_args) Unknown parameter DEV
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:5031:(snd_config_expand) Parse arguments error: No such file or directory
INFO: CAESinkALSA - ALSA: /var/lib/jenkins/LE/build4/workspace/RK3328/build.LibreELEC-RK3328.arm-9.2.1/alsa-lib-1.1.9/src/conf.c:4898:(parse_args) Unknown parameter DEV

That looks buggy to me.

I've been moved this into our showcase section, because many users had trouble to multi-boot LE. Grub2Win is a nice solution.

Your original thread title was too long, so I was cutting it. You said the boot error appears since your Windows update.

Go into your EFI / BIOS settings and check the boot order of partitions. Some Windows updates change it, but that's not our fault.

pspablo_pl Please edit your post. Only English language is allowed.

PS: Thanks.

Please always use the forum search before starting a thread: results.

Check the microSD for errors before you re-install LE on it.

Maybe the internal Bluetooth broke. Check it with a different Bluetooth device, if you have. An external Bluetooth adapter is a cheep replacement.

• option 1: get a different WiFi adapter
• option 2: become a Linux master and compile your own LE version

Unfortunately I can't give you an advice, which adapter to buy, because I don't use WiFi. Maybe another user can help.

Disable audio pass-through at Settings -> System -> Audio.

Surprise, it's a Realtek:

kernel: usb 1-1.1: New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00
kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-1.1: Product: 802.11ac NIC
kernel: usb 1-1.1: Manufacturer: Realtek
kernel: usb 1-1.1: SerialNumber: 123456

I can't find the chipset anywhere (incl. shop descriptions). That's strange.

PS: I don't trust those "Bros Trend" bros: SerialNumber: 123456

Quote from chewitt

@DaFlex that's running a 64-bit OS in a container (on 32-bit userspace) so not really a solution that works.

Could the opposite, a 32 bit container at 64 bit, work for us?

PS: It seems like it's possible:

Quote from www.balena.io

We’ve created a sample project to demonstrate that for the first time ever, you can now install 64-bit balenaOS on the Raspberry Pi 4, and run a combination of both 32-bit and 64-bit containers together simultaneously; notably the exclusively 64-bit MongoDB image.

Due to the increased RAM usage probably only an option for RPi 4B.