Posts by HiassofT

As last year please test with just the TV hat installed.

Also note that the TV hat is running the SPI bus at 50MHz, so adding fancy stacks is likely to cause issues.

so long,

Hias

Please test without the librespot addon and make sure you set the audio output device to ALSA in system->settings->audio.

I suspect pulseaudio (which seems to get enabled by the librespot addon) might be the culprit.

so long,

Hias

Start by replacing the broken 32GB drive

Apr 06 12:51:23.642517 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Apr 06 12:51:23.643238 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Apr 06 12:51:23.643529 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Apr 06 12:51:23.643802 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 95 67 88 00 00 68 00
Apr 06 12:51:23.644082 PiKodi kernel: critical medium error, dev sda, sector 60123016 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

I wouldn't be surprised if the dying drive causes file buffers to increase until the kernel kills tvheadend as the drive cannot keep up with the amount of data that tvheadend wants to write.

so long,

Hias

Yes, this looks fine (OFC replace 0x00000000 with your actual license).

But, for the 3rd time now, please run vcgencmd codec_enabled WVC1 and post the result and a debug log.

so long,

Hias

Of course you need a licence, and if in doubt add the decode... line to /flash/config.txt.

But IIRC for quite a long time (several years) it's fine if you had entered a valid license key once in the lifetime of the RPi, then the firmware mad the activated license "stuck" and you didn't need to add it on new installations.

Anyways, the vcgencmd codec_enabled command will tell you whether the license is enabled or not so please run that before digging further.

so long,

Hias

Any place in the /flash/config.txt should be fine. Actually, once you have entered a license key it should "stick" so you don't need to edit config.txt anymore.

What does vcgencmd codec_enabled WVC1 report on your RPi?

I did a quick test with LE 11.0.6 on my RPi3B+ (without any keys in config.txt) and VC1 playback worked fine, pressing "o" on the keyboard showed that kodi was using the "ff-vc1_v4l2m2m-drm_prime (HW)" decoder and CPU load was quite low.

LibreELEC (official): 11.0.6 (RPi2.arm)
kodi3:~ # vcgencmd codec_enabled WVC1
WVC1=enabled

Please post a debug log if you can't get it working.

Just add the decode... lines to the end of /flash/config.txt

so long,

Hias

FYI: you can adjust udevil mount options in latest LE11 and LE12 images by copying /etc/udevil/udevil.conf to /storage/.config/udevil.conf and then editing the file. After that reboot so the changes take effect.

Note that you'll also have to adjust allowed_options_exfat in addition to default_options_exfat

so long,

Hias

rpi-eeprom-config is included in RPi4 and RPi5 images (not in RPi2 though as RPi2/3 don't have bootloader eeproms)

LibreELEC (official): 11.95.1 (RPi5.aarch64)
xbmc:~ # which rpi-eeprom-config
/usr/bin/rpi-eeprom-config
xbmc:~ # rpi-eeprom-config 
[all]
BOOT_UART=1
POWER_OFF_ON_HALT=1
BOOT_ORDER=0xf21

so long,

Hias

Create a /storage/.config/autostart.sh containing modetest -M vc4 -w "32:Broadcast RGB:1"

eg run:

echo 'modetest -M vc4 -w "32:Broadcast RGB:1"' > /storage/.config/autostart.sh

Then reboot

so long,

Hias

Quote from DavidCNZ

Stupid noob question but how do I reinstall Widevine after upgrading from 11.06

Open the inputstreamhelper addon and choose reinstall.

so long,

Hias

Now it gets confusing, over at the kodi forum you posted that you got it working.

My TV remote suddenly stopped working with Kodi

Quote

Ok, I just rebooted the Pi4 with the HDMI cable already connected to HDMI-0 and it started working.
The thread can be closed.

Please don't double post to different forums as this creates double work (lots of us developers monitor both forums).

If you double post please keep both your threads up-to-date to avoid confusion and unnecessary work for us devs.

so long,

Hias

Create a bootloader recovery SD card using the Raspberry Pi imager https://www.raspberrypi.com/software/ - use a spare SD card and choose the desired bootloader (SD/USB/net boot) in the operating systens -> misc utilities section.

Hard to tell what went wrong when you updated, this is the first report of a failed bootloader update that I have seen.

so long,

Hias

If you are on LE11.0.6 then that is the most recent release you'll get from rpi-eeprom-update -a - the EEPROM firmware files are included in the image so they'll be whatever was current at release time.

Use LE12 nightlies or the LE12 beta (which should be likely released today or tomorrow) to get newer EEPROM or write the latest EEPROM release from https://github.com/raspberrypi/rpi-eeprom/releases here to a spare SD card to manually update the EEPROM to some desired version.

Another option is to download a RPi5 pieeprom file from here https://github.com/raspberrypi/rp…r/firmware-2712 and then run rpi-eeprom-update -f pieeprom-YYYY-MM-DD.bin

so long,

Hias

RPi5 with 4GB RAM or if you want to save a few bucks RPi4 with 4GB.

so long,

Hias

Please test with LE12, it contains VC-1 playback optimizations and lots (but not all) VC-1 files should play fine on RPi4.

so long,

Hias

An easy workaround is to boot your RPi with the LG monitor connected, then ssh in and run "getedid create".

Then your RPi4 will "think" it's always connected to the LG monitor and ignore the broken EDID of your SABA TV.

so long,

Hias

lircd is ancient legacy and nowadays isn't started unless you really want to use it and manually create a lircd.conf file in /storage/.config

LE only use the modern ir-keytable way to handle IR remotes (and eventlircd to route the buttonpresses to kodi - that's another story though) for quite a while now so you won't see lircd running on any LE installation - unless you manually created the lircd.conf file

so long,

Hias