Posts by HiassofT

If the card doesn't have an eeprom with the dtoverlay (so it's automatically enabled) you could try adding this to your config.txt (remove the old dtoverlay=hifiberry... line first)

dtoverlay=allo-digione

so long,

Hias

There's not much info about the VS1838 except for a chinese datasheet and some posts stating that the Vishay (TSOP) receivers perform better.

One thing you should check is that you have proper filitering on the IR receiver's VCC pin. The datasheet shows a 100uF capacitor in parallel to a 100nF - which usually should be soldered very near to the receiver. A 100 ohm series resistor can further help reducing noise on the VCC line. From the datasheet it's not clear if this is needed, but as noise on the VCC line can impact performance it won't hurt if you added that filtering.

Personally I have only used Vishay parts so far, the well known TSOP34438 should do fine. I'm currently using the older TSOP34138 receivers here, which uses an older AGC version (1 instead of 4, the latter is recommended by Vishay for NEC and RC-5/6 remotes).

So far I didn't have VCC noise issues with these receivers. The receivers are connected via approx. 0.5m long shielded cable and I haven't soldered filtering caps to the receiver.

so long,

Hias

The issue seems to be a race condition in the ethernet driver when shutting down the network interface. This class of issues is one of the nastiest as it depends on exact timing if you hit the issue or not - and for that reason they can be extremely hard to reproduce.

Simply speaking: it's rather random of the issue shows up or not.

You don't need to spend more time on that, I managed to find out what's happening and why.

A possible solution for the issue is already on the horizon, but it could take a bit until the fix is finished and added to the driver.

Details of my analysis are in this RPi kernel issue: oops in lan78xx_delayedwork on kernel 4.9 when rebooting · Issue #2467 · raspberrypi/linux · GitHub

so long,

Hias

If you used the keys from another (older) RPi this won't work, the codec licenses are tied to the RPi's serial number.

You can order license keys directly from RPi: Raspberry Pi Store

They had a few issues with their shop about 2 weeks ago but IIRC they are resolved now.

so long,

Hias

I've seen this happen 2 or 3 times as well but it was rather hard to reproduce - most of the time reboot worked just fine.

I just managed to reproduce it and capture the kernel output - it seems to be a bug in the RPi3B+'s ethernet driver which let's the kernel crash.

I'll try to dig into that a bit and see if it's a general problem with the RPI3B+'s ethernet driver or something specific to LibreELEC.

so long,

Hias

grael

Do you get the same issue when using the newer firmware on 8.2.3 builds?

Do you have Resample Qualtiy set to "GPU accelerated" in Settings->System->Audio (settings level must be advanced or expert to see/change that)?

Does it go away when changing Resampling Quality to Medium or High?

so long,

Hias

This is because the RPi3B+ didn't exist when LE 8.2.3 (and older) were released and these versions don't include the necessary changes to run on an RPi3B+.

You need LE 8.2.4 or Milhouse testbuilds after the RPi3B+ release date (March 14th) for the RPi3B+.

so long,

Hias

Wow, thanks a lot David, this must have been the most detailled bug report I've received here so far! And it contained more than enough info to reproduce and understand the issue.

The problem stems from the combination of using a Sharp remote with an ite-cir receiver. The Sharp IR remote messages are rather long (about 86ms in the sample you provided) and the default idle timeout of the ite-cir driver is also rather high (200ms). So what is happening is that when you release the button (no matter if it's a short or a long button press) the sum of that - 286ms - exceeds the default kernel "key release" timeout of 250ms - and the last message (which is delayed to the timeout) is seen as another button press.

With other remotes, like for example MCE remotes, this does not occur because the sum of message time (about 40ms in case of rc-6 MCE) and 200ms timeout is just below that magical 250ms limit.

I've recently discussed these issues with long timeouts with the kernel developer and hopefully there'll be a good solution in the future - it could take a bit, though, it's all a bit tricky.

Fortunately, there's an easy workaround you can use for now, you can manually configure the driver to use a lower timeout. The minimum timeout of ite-cir is 100ms, I'd use that and if that causes other problems I'd try a bit longer values (125-150ms).

You can set the timeout with ir-ctl -t TIMEOUT, but keep in mind that ir-ctl expects the value to be in microseconds, not milliseconds. So use eg "ir-ctl -t 100000" to set a 100ms timeout. You can either add that to autostart.sh or add an udev rule for that. I've posted info how to do that in the Amlogic IR remote thread here: LE9.0 remote configs ir-keytable Amlogic devices (replace "meson-ir" with "ite-cir" to make this work).

With the rather long messages you could run into key repeat more easily, you can change that with "ir-keytable -D DELAY" - that's the delay before repeat starts, default is 500ms. Ah, and here the delay is in milliseconds, so use eg "ir-keytable -D 700" to use a slightly longer delay.

so long,

Hias

Could you please test if you get the same crackling if you use the firmware from 8.2.4 on the working 8.2.3 builds?

Details how to install the newer firmware (and go back to the original one) are here: LibreELEC 8.2.4 causes Slice 3 to hang

so long,

Hias

Could you please post the output of "ir-keytable" and then run "ir-ctl -r", press a button and post the output you got on the console (a sequence of "pulse" and "space" lines).

so long,

Hias

If you are using NOOBS you have to update NOOBS as well.

Unfortunately NOOBS doesn't seem to have an auto-updater so you have to do it manually.

I've posted instructions how to do this here:

Changing from RPi 2/3 to RPi 3B+, FIRST upgrade to 8.2.4 (including NOOBS instructions)

so long,

Hias

There is be a problem if you are using NOOBS. Updating LibreELEC is not enough, you also have to update NOOBS before the SD card will boot in a RPi 3B+.

I've found instructions how to update NOOBS here Updating Raspbian on your microSD for the Raspberry Pi 2 – The Pi Hut and successfully tested this with a NOOBS 2.4 installation.

1. Download NOOBS LITE v2.7 (not the full version, the LITE one) from Download NOOBS for Raspberry Pi
2. Extract the ZIP file and copy all files EXCEPT recovery.cmdline to the first partition of the SD card

You can either do this on your PC or with the following commands from within LibreELEC:

mkdir noobs
cd noobs
wget -O noobs-lite.zip https://downloads.raspberrypi.org/NOOBS_lite_latest
mkdir extract
unzip -d extract noobs-lite.zip
rm extract/recovery.cmdline
mkdir part1
mount /dev/mmcblk0p1 part1
cp -r extract/* part1/
umount part1
cd ..
rm -rf noobs

so long,

Hias

Quote from bubblegum57

He's using Raspbian

No. Read the original post again

so long,

Hias

The firmware is included and updated with LibreELEC updates and usually there's no need to do that independently from that.

If you really want you can update the firmware files manually, at your own risk:

Download bootcode.bin, start_x.elf and fixup_x.dat from the RPi firmware github repository, rename start_x.elf to start.elf and fixup_x.dat to fixup.dat and copy the 3 files to the /flash partition.

You can also easily do that from Windows/Mac/Linux (can be helpful if you messed it up) as the /flash partition is FAT formatted.

so long,

Hias

Wireless will always be prone to interference, a problem which you won't have with a wired ethernet connection. So it's a general recommendation to use wired network, especially for high bitrate files. Buffering can work around short dropouts, but has it's limits.

If wireless works fine for you than use it. But if you get occasional stuttering this can be due to interference and switching to wired should solve it.

so long,

Hias

bcmstat output of non-overclocked 3+:

HW Block: |   ARM   |  Core  |  H264  |    SDRAM    |
Min Freq: |  600MHz | 250MHz |   0MHz |    500MHz   |
Max Freq: | 1400MHz | 400MHz | 300MHz |    500MHz   |

so long,

Hias

To use lircd instead of in-kernel decoding you just need to create an empty .config/rc_maps.cfg file, and enable lirc in LE settings, as outlined in the wiki.

It's odd though that your remote suddenly starts lagging. My first guess is that kodi is busy and can't immediately process the remote events. I've been experiencing this on my RPi1 when kodi is updating addons after startup - top shows kodi.bin using all CPU resources and after a minute or so when addons have been updated things (CPU usage and remote response) are back to normal.

To narrow things down run the following command when your remote started lagging:

irw /run/lirc/lircd

This let's you monitor the remote events as they reach kodi. Press a few buttons on the remote and check how long it takes until they show up. If they show up almost immediately here but navigation in kodi is delayed it must be something in kodi. If they are delayed here as well, it's something in the kerne/lirc area.

so long,

Hias

Quote from Schreibwaise

I'm so glad I finally found this post! In the past (10 years ago or so) you had to use setserial /dev/ttyS0 uart none, but now the correct parameter is unknown. The annoying thing is that the systemlog will tell you the wrong parameter when trying to load serial_ir. And the module still will load without prior correct setserial!

The kernel message in the log isn't wrong, with the setserial program you typically find on Linux installations you have to use the parameter "none".

LibreELEC doesn't use this setserial program but the setserial implementation from busybox and there you have to use "unknown".

so long,

Hias