Posts by HiassofT

gpio-ir-receiver, gpio-ir-tx and pwn-ir-tx are available on all platforms and included in the official linux kernel.

See eg here linux/Documentation/devicetree/bindings/leds/irled at master · torvalds/linux · GitHub and here linux/gpio-ir-receiver.txt at master · torvalds/linux · GitHub for the devicetree bindings and here linux/drivers/media/rc at master · torvalds/linux · GitHub for the source code.

Amlogic, Rockchip, Allwinner etc unfortunately don't support device tree overlays yet, like the RPi does so it'll be a bit tricky to include the device tree fragment needed to activate the driver on the correct GPIO pin. I think you'd need to patch the dtb file ATM.

Ah, and these drivers are rather new, you need to use a late 4.x or a 5.x kernel to get them - LE10 Amlogic builds will be new enough. Also not sure if the IR transmitter drivers are included in LibreELEC kernel configs, that could be changed quite easily though.

These rc-core IR drivers completely replace the old lirc drivers and have the huge benefit that they can use in-kernel IR decoding. The old lirc drivers needed userspace lircd to do the decoding. In the meanwhile the kernel supports generic decoders using BPF programs so it can handle almost every protocol that lircd supported.

so long,

Hias

Anything overclocking-related is quite tricky and you are pretty much on your own if you need/want to do that.

Achievable overclock settings are highly dependent on the silicon in your specific RPi and allowed/stable settings may also change with firmware versions as they often modify internal voltage/clock switching logic (eg to reduce power consumption/temperature).

so long,

Hias

Thanks, the linked datasheet contained a schematic and confirmed what I thought:

The one with the dual-LED should be fine, the single LED one not so much as it's missing the transistor.

so long,

Hias

Phew, hard to say. The second board (with the 2 LEDs) seems to have a transistor on it so that might work. Can't spot a transistor on the first board (with 1 LED) though.

Do you have any links to datasheets or schematics for these boards?

so long,

Hias

Actually it might be better to just post logs from a plain LE/kodi installation - that won't have any personal info and will rule out issues due to setting changes as well.

If you have a spare SD card write LE 9.2.3 to it, if not simply stop kodi, rename the .kodi folder to .kodi-bak and start kodi again (and later remove the newly created plain .kodi folder and move .kodi-bak in place again - with kodi stopped).

Edit: to create the logs, enable debug logging and kodi and then power off the pi, then start up again - that should make sure the CEC connection is started completely "fresh" (at least from the RPi side).

so long,

Hias

Thanks for the info, I did some more testing with LE 8.2.x.

Since the Mar 13 2018 firmware (which went into LE 8.2.4) the H264 block is clocked at the officially documented frequency (250MHz) - see Overclocking options in config.txt - Raspberry Pi Documentation

In the Mar 9 2018 firmware (and lots of earlier firmwares) the H264 block was overclocked at 300MHz by default - this is what makes the difference between working and non-working 1080p60.

Simply do a slight H264 overclock to 300MHz, this worked fine here both on LE 8.2.4/5 and 9.2.3

h264_freq=300
h264_freq_min=300

so long,

Hias

How are you testing this?

Just tried that firmware on LE 9.2.3 and kodi didn't even start (which I was expecting as that firmware is ancient and not matching what current kernel/kodi expects).

so long,

Hias

You need to overclock your RPi2 if you want to play 1080p60 videos. H264 is specced at max 1080p30 on RPi1 and 2. RPi3 and newer run the H264 block at higher clocks per default, so 1080p60 works out of the box there.

See also this old thread: Pi 2 1080p@60fps videos out of sync with omxplayer and Kodi - Raspberry Pi Forums

so long,

Hias

ah, and it would also be interesting to see the full kodi debug log and journal after the stuck notification appeared.

ssh in, then run pastekodi and post the URL.

so long,

Hias

CEC is working fine here, too (RPi4, LG TV), and I haven't spotted any CEC related changes between 9.2.1 and 9.2.3 yet.

nvdias could you try replacing start.elf and fixup.dat in /flash with the files from 9.2.1 and test if this makes a difference?

so long,

Hias

Looks like we got a fix for the kodi lockup / kernel oops issue [le92] ffmpeg: update RPi HEVC patch to latest version by HiassofT · Pull Request #4411 · LibreELEC/LibreELEC.tv · GitHub , quick test on RPi3B+ with latest firmware went fine.

The fix will be included in the next LE release, for now please use the firmware revert workaround.

so long,

Hias

bleep42 I did some more testing and the issue seems to be firmware (not kernel) related.

Could you test LE 9.2.3 again and replace the firmware files in /flash with the contents from this ZIP? rpi-firmware-9e3c23c.zip

This reverts the RPi firmware to the April 15 version, with that your sample files played fine on RPi3.

so long,

Hias

Thanks for testing!

I could reproduce the issue with your samples on RPi3, it seems to be a kernel bug. I've pinged popcornmix and pointed him to this thread.

so long,

Hias

bleep42 did you overclock your Slice? If yes it might be worth testing with all overclock settings removed from config.txt.

There were changes to the RPi firmware regarding clock/voltage handling so overvoltage/overclock settings in config.txt may need to be adjusted.

so long,

Hias

Quote from harun-cuk17

Sd card in an usb reader will that faster boot up LE instead of sd card in the sd slot?

Probably not, because USB enumeration will take a bit. I haven't done any speed / time tests, just checked if my USB2 SD card reader (which probably isn't too fast anyways) worked.

so long,

Hias

Quote from Mario77

HiassofT

Fresh install works fine..but if I update from 9.2.1 it doesn't start...

journalctl

cat /proc/cpuinfo

Thanks for the info - nothing unusual in the logs, except you voided warranty due to overclocking

Have you tried updating 9.2.1 with stock config.txt? There were quite a lot overclocking/overcurrent settings in there...

It would be good to rule out any issues that could be caused by overclock, marginal power supply or dying SD cards (which still are the most common issues with RPi).

Also some more testing with your stock 9.2.3 installation would be interesting.

so long,

Hias

Mario77 it's very puzzling that a fresh install of 9.2.3 worked but then failed after restoring the backup.

Could you try installing 9.2.3 fresh again and then ssh in and post the output of

journalctl -a | pastebinit
cat /proc/cpuinfo | pastebinit

Also try using 9.2.3 with stock configuration for a bit (eg play local media, reboot) and see how that works.

Testing with another SD card may also be worth a try, maybe the one you were using is starting to fail (that would explain why boot failed after restoring backup).

so long,

Hias

Quote from PANiCnz

Does this release include the latest firmware required for USB boot?

LE 9.2.3 ships with the May 27 RPi firmware which has initial support for USB boot.

Note however that RPi4 USB boot is in early beta testing stage and you also need the beta bootloader EEPROM update which is not included in LE.

So while it may be possible to boot LE 9.2.3 from USB (it worked for me with the LE SD card in a USB cardreader) it's not something we support ATM or even encourage you to try.

If you run into issues it's best to test with the Raspberry Pi OS (former Raspbian) instead of LibreELEC - chances are high that there are issues with several USB devices/adapters. Check the instructions in the USB boot thread on the RPi forum USB-MSD boot EEPROM update - 2020-05-28 - Raspberry Pi Forums and report issues there.

so long,

Hias