LibreELEC 12.0 on Raspberry Pi5

It would be useful to see the system (not Kodi) log when the USB device is attached. And yes "it's only a USB stick" but what is the PSU rated for? .. bad behaviour during boot and device attachment is a common symptom of unstable power.

NTFS is obviously supported, because you can mount it. Things get nasty when an NTFS device has errors on Linux.

Quote from jonos

In this case, the NTFS device does NOT report error with Linux.

Yep, I think that's the issue here. It's not LE-specific.

Only to be sure, do you use a case for your RPi5 like the Argon ONE V3? I'm asking because this case doesn't pass-through the PD information to the RPi5. The case pcb is self a power sink and negotiates the power consumption with the power supply. But the connection RPi5 <-> case pcb doesn't negotiate via PD (power delivery).
The RPi5 relies on that power delivery information, to enable the whole 5A current and additional the USB boot support/max. USB current.

In such case, you need to add this lines to bootloader config /EEPROM:
PSU_MAX_CURRENT=5000

and to your config.txt:
usb_max_current_enable=1

If it's a PSU problem, then it's visible as undervoltage error in the log.

However, I still think it's related to errors at the NTFS file system. Since LE 12, file system check works different. This might lead to the described crash. Read this:

Post

RE: Manage disk partitions on libreelec

Correction: since LE12 file system expansion on first boot is logged to /flash.

fsck on boot is logged to kernel and can be seen with dmesg|grep fsck:. Please note : in default configuration no check is forced as long the file system is clean.

mglae

November 25, 2023 at 9:35 AM

I read the tea=leaves in my cup this morning but it hasn't helped with diagnosis. Sharing the URL from "journalctl | paste" would be more fruitful. We need to system the system log please.

Quote from HarryH

Only to be sure, do you use a case for your RPi5 like the Argon ONE V3? I'm asking because this case doesn't pass-through the PD information to the RPi5. The case pcb is self a power sink and negotiates the power consumption with the power supply. But the connection RPi5 <-> case pcb doesn't negotiate via PD (power delivery).
The RPi5 relies on that power delivery information, to enable the whole 5A current and additional the USB boot support/max. USB current.

In such case, you need to add this lines to bootloader config /EEPROM:
PSU_MAX_CURRENT=5000

and to your config.txt:
usb_max_current_enable=1

Display More

Hi

How to add PSU_MAX_CURRENT=5000 to bootloader config /EEPROM ?

Hi Goood ,

please use the rpi-eeprom-config command with the edit parameter:
rpi-eeprom-config --edit or rpi-eeprom-config -e

Oh ! sorry, I don't understand yet Linux commands

I used a copy/past "sudo -E rpi-eeprom-config --edit" as it recommended in this forum, that don't work. And so, "-E rpi-eeprom-config --edit" that don't work to

Thank you !