Posts by HiassofT

The clue is in the kernel log:

Apr 11 16:28:38 LibreELEC kernel: Under-voltage detected! (0x00050005)

You need to fix your power supply issues - the official RPi power supplies are known to work fine.

so long,

Hias

The nightly images have the githash they were built from appended at the end of the name eg LibreELEC-RPi4.arm-9.80-nightly-20201020-dc19933.tar

Use that githash (eg dc19933 in the example) to look up changes on LE github.

You can also use the github compare function to see what has changed between two githashes. eg Comparing ec1292b...dc19933 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

You can download the most recent addons for nightly builds from here Index of /addons - always look there if the ones from the LibreELEC repository don't work.

This would be the latest inputstream.adaptive addon for Generic: 9.80.6-Generic-x86_64-inputstream.adaptive-2.6.0.1.zip

Edit: ah, wait a sec, this version is still too old, it was built shortly before the kodi update that's in your image went in. Please check again in a day, then the updated addon should be available.

so long,

Hias

This is a known issue - wifi configuration is broken in LibreELEC settings since the update to python 3.8. This needs a larger rework.

so long,

Hias

The fix is merged, please give tomorrow's build (20201016) a try.

so long,

Hias

Just PR'ed a fix, it should hopefully be merged soon systemd: backport cache timestamp fixes from master by HiassofT · Pull Request #4605 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

Thanks for reporting the issue, I can reproduce that here. Without network plugged in LE will hang forever on NMB startup. I'll have a look at it.

so long,

Hias

The hang is caused by multi-user.target getting an After= dependency on your service, in addition to the Wants=.

You can avoid that by setting DefaultDependencies=no and manually specifying Before, After and Conflicts. eg:

DefaultDependencies=no
After=time-sync.target
Before=shutdown.target
Conflicts=shutdown.target

Then multi-user.target will only get the Wants= which pulls in your service but not the After= which delays multi-user.target.

so long,

Hias

The service file looks fine, you should change the Type to "oneshot" though (simple is for programs continuously running in the background, eg if you want to do regular updates in a loop in your script).

For scripts that should be only run once after startup you should also set "RemainAfterExit=yes" in addition to "Type=oneshot".

so long,

Hias

Create a oneshot systemd service and order it after time-sync.target.

so long,

Hias

Most likely you have to connect the DVD drive via a powered USB hub.

Maximum USB current on RPis is 1.2A - for all 4 ports combined. If you exceed that (eg if the DVD drive or a USB HDD needs more when spinning up) you'll get the symptoms you described (USB reset, devices "falling off the bus").

See also the RPi FAQ FAQs - Raspberry Pi Documentation

Quote

From the Raspberry Pi B+ onwards, 1.2A is supplied to downstream USB peripherals. This allows the vast majority of USB devices to be connected directly to these models, assuming the upstream power supply has sufficient available current.

Very high-current devices, or devices which can draw a surge current such as certain modems and USB hard disks, will still require an external powered USB hub.

so long,

Hias

Just use the latest LE release (9.2.4), it already includes all fixes. I removed the temporary test build from my server a long time ago.

so long,

Hias

keep GPU mem as it is (76MB) - that's not needed with the new driver and only wastes memory.

Only H264 HW decoder needs GPU mem and 76MB should be plenty for it. New driver needs CMA memory (which we already default to 384MB ATM).

so long,

Hias

If you updated from an older version please replace your config.txt with the one in /usr/share/bootloader/config.txt - some important settings have changed and the file isn't automatically updated/replaced yet.

as for remote.xml: please provide a kodi debug log.

so long,

Hias

Are you using Wifi? If yes try a wired connection, badly shielded USB3 devices are known to interfere with 2.4GHz wifi usb3-frequency-interference-papers.pdf

so long,

Hias

You seem to have linked to the wrong image, for RPi4 you have to use the RPi4 images - eg LibreELEC-RPi4.arm-9.80-nightly-20200924-4722b9e.img.gz

4k support isn't implemented in the driver yet, that's being worked on and will come later when it's finished.

We are currently testing kernel 5.9 with a newer version of the display driver and changed the config a bit so you won't get a black screen with hdmi_enable_4kp60=1 in config.txt. With current nightly test images you could add disable_fw_kms_setup=1 to config.txt to avoid that issue - see linux (RPi): update to 5.9 by HiassofT · Pull Request #4562 · LibreELEC/LibreELEC.tv · GitHub

Not sure about the remote.xml issue, you'll have to post a kodi debug log. ./userdata/... looks wrong though, that should be /storage/.kodi/userdata/...

so long,

Hias

There are no separate docs for LE, just have a look at the official RPi docs linked here GitHub - raspberrypi/rpi-eeprom: Installation scripts and binaries for the closed sourced Raspberry Pi 4 EEPROMs - there's also a ton of threads about how to use rpi-eeprom-update / rpi-eeprom-config on the RPi forums (or just call these scripts without parameters and you'll get the usage info).

Only difference on LE is that you don't need to run these programs with sudo as you're already logged in as root.

BTW: probably the easiest way to get the latest eeprom / VL805 firmwares is to boot the eeprom recovery image from SD card - this'll give you the Sep 03 bootloader version as well. Either use RPi imager on your PC or the recovery image from here Release rpi-boot-eeprom-recovery-2020-09-03-vl805-000138a1 · raspberrypi/rpi-eeprom · GitHub

so long,

Hias

Yes, correct.

so long,

Hias