Posts by HiassofT
-
-
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
-
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
-
LibreELEC 9.2.3 is working fine here on my 8GB RPi4.
Just tested with a fresh installation on an SD card using the official Raspberry Pi Imager tool from here Raspberry Pi Downloads - Software for the Raspberry Pi - choose LibreELEC -> LibreELEC (RPi4)
Edit: just noticed a glitch in Kodi's Settings -> System Info screen, it only shows ~3.6GB total memory. Running "free" or "top" show correct numbers.
so long,
Hias
-
Thanks for the edid file, I could reproduce the issue with it.
It looks like your projector has a broken edid, edid-decode throws up a lot of "Unknown tag 0" errors and a "Broken CTA audio block length 13" error.
RPi firmwares up to a year ago (Jun 10 2019 to be more specific) coped better with it, but later firmwares trip over that. I've flagged that to the RPi devs.
so long,
Hias
-
You can still get the HP branded MCE remotes for about 10 USD (or about 20 USD including an MCE USB receiver) on ebay.
These are "real" MCE remotes and will work out of the box without needing to configure anything in LibreELEC.
Be careful when searching for "MCE" remotes, a lot of cheap remotes from asia use that term in their description though they use completely different protocols and receivers which are in general a huge pain to set up - don't buy these.
Another alternative is to use CEC if it's supported by your TV. In general that works quite well, too, and you don't need a separate remote to control LE.
so long,
Hias
-
-
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