Posts by HiassofT

Your .config/samba.conf will only be picked up if you restart the samba-config systemd service before restarting the samba systemd services. Or just reboot LE.

so long,

Hias

If you want to move to a USB/SSD only setup later it'd be best to partition the SSD with a 512MB VFAT as #1 (this will become the "/flash" boot partition later) and then the remaining space as an ext4 partition for storage.

just copy the data from the ext4/storage partition on the SD card to the ext4/storage partition on the SSD and then change the disk=UUID=.... parameter in cmdline.txt (in the FAT partition of your SD card) to the UUID of the ext4 partition of the SSD (use "blkid" to get the UUID values).

so long,

Hias

1366x768 is a know problematic resolution on the RPi4 and there doesn't seem to be some offical fix for it yet.

If you search the RPi forums you'll find a lot of reports and also proposed workarounds.

eg one suggestion is to try this

hdmi_group=2
hdmi_mode=87
hdmi_cvt=1366 768 60 3 0 0 1

see Rpi 4 not working at 1366x768 - Raspberry Pi Forums

so long,

Hias

throttled= 0x80000 means that the RPi3B+ went over the soft temperature limit of 60°C and throttled the CPU down from 1400 to 1200MHz at some time in the past. Your power supply is fine.

See Raspberry Pi Documentation and Raspberry Pi Documentation

so long,

Hias

Thanks a lot for reporting the issue!

If you are not sure about config.txt just attach it here and I'll have a look

In general I add settings at the end of config.txt as that makes sure they override any previous settings.

BTW: it could be that one of the other config.txt settings I mentioned helps with your RPi, please test those, too (try only one of them at a time).

And please tell us which RPi you are using (2B, 3B, 3B+) and post a logfile of LE 9.2.3 running with the replaced firmware files. Go to Settings -> LibreELEC -> System and select "Upload latest Kodi log and configs, and view the short URL", then post the URL you got.

so long,

Hias

I think I now know what's going on, you probably have to override 4 trip points instead of two.

There were two cooling zones added before the previously existing ones at slower fan rotation speeds.

So try adding temp2 and temp3 as well, like in the github discussion, I guess that should work.

so long,

Hias

This sounds a bit like you may be running into the config.txt line-length limit. Try to break up the dtoverlay line as described here Reduce noise from rpi poe hat fan by Learath · Pull Request #3493 · raspberrypi/linux · GitHub

so long,

Hias

RPi engineer 6by9 had a go at your edid file and manually fixed it.

Can you test if it works?

Just extract the ZIP, store panasonic-pt-ae5000e_edited.bin as edid.dat on the flash partition and set hdmi_edid_file=1 in config.txt.

so long,

Hias

Thanks for confirming!

This is very likely a bug in the firmware, the one in the zip is from Apr 15, before RP0-3 and RPi4 firmwares were merged. I've pinged the Raspberry Pi devs.

Could you install 9.2.3 again (to get the latest firmware) and then try to add one of the following lines to config.txt (only try one setting at a time) and check if that lets your RPi boot:

• over_voltage=2
• core_freq=250
• force_turbo=1

so long,

Hias

Staying on 9.0 is probably the easiest solution for now.

Another possibility would be fixing the edid, if you add hdmi_edid_file=1 to config.txt the RPi will read edid.dat from the /flash partition. Unfortunately I can't help much with fixing the edid, I'm not really familiar with the edid editor programs.

Anyways, we'll keep you posted if we got something to test!

so long,

Hias

Thanks for testing!

Unfortunately the output looks pretty normal.

I strongly suspect though that the missing CONFIG_INPUT_UINPUT option in imx6 kernel config is responsible for the eventlircd issue - eventlircd requires /dev/uinput to be present.

I've pinged our imx6 maintainer lrusak and asked him to add this missing option.

so long,

Hias

Thanks for testing!

Could you replace the firmware files on the /flash / FAT partition of a LE 9.2.3 installation with the ones from this ZIP rpi-firmware-9e3c23c.zip and test if it boots now?

so long,

Hias

please do the tests with 9.2.1 and 9.2.0 and run the journalctl command on 9.0.2.

so long,

Hias

Can you please test the following things:

- does the RPi boot with 9.2.3 (after the reboot hang) if you disconnect and reconnect power?

- do LE 9.2.1 and 9.2.0 show the same behaviour? LibreELEC-RPi2.arm-9.2.1.img.gz LibreELEC-RPi2.arm-9.2.0.img.gz

- have you tested with a different SD card?

If 9.0.2 works can you please ssh in and post the output of journalctl -a | pastebinit

so long,

Hias

This sounds like eventlircd is not running/starting.

Make sure you haven't masked/disabled the eventlircd systemd service and that you don't have any udev overrides for 98-eventlircd.rules.

Also please post the output of systemctl status eventlircd and journalctl -a | pastebinit, after a fresh boot, that should give some more hints.

so long,

Hias

Quote from harun-cuk17

Rpi does not recogneze cards above 32gb. To do this you need to use a tool which will make the exfat to fat32.

Current RPis will happily accept cards larger than 32gb. And when using an image writer fat vs exfat doesn't matter at all as it will write the (v)fat partition as contained in the image. Exfat was mainly issue when using NOOBS.

so long,

Hias

This is what I meant. The updater needs to uncompress the image. That needs additional space and takes longer than updating with a tar - but it works the same.

so long,

Hias

The update system in LibreELEC supports updating both from a tar file and and img.gz one - you can just copy it into the .update folder, reboot, and it'll get picked up.

The /storage (ext4/linux) partition is unchanged, the updater will only replace files in the /flash (vfat/windows) partition.

The difference between the tar file and the img.gz file is that the tar file contains the files that need to be updated in /flash in a more suitable format. The img.gz is a compressed raw disk image with a 512MB vfat partition and an empty ext4 partition that will get resized when first booted. When updating with it this image file needs to be uncompressed first and then scanned for partitions to get to the actual files in the vfat partition.

So, while both variants work and have the same end result, doing that with an img.gz takes longer (due to the uncompressing overhead).

so long,

Hias