I'm new to libreelec and kodi. where do i find the config.txt file to add the commands to allow the pi 4 8gb to display on my yamaha receiver and samsung tv. It's blank but the pi 4 works here on my desktop via hdmi. Thanks
See here Raspberry Pi Config.txt [LibreELEC.wiki]
If you have display problems please search the forum and create a separate thread if necessary.
so long,
Hias
Do you know if the rest of the ram is usable? Can Librelec even make use of that much ram? I have Librelec running on the Pi4 8gig, but doubt that much ram even does any good..
Linux can use the full RAM for filesystem cache/buffers and background programs / docker containers etc can make use of it. I wouldn't recommend though to run too much stuff on the RPi, it's CPU is still a lot slower than current gen Intel/AMD CPUs.
If you just want to run Kodi then 8GB is overkill. All programs are compiled as 32bit, so each process can use max 3GB (and Kodi won't even need that). 2 or 4GB will do just fine.
so long,
Hias
Please try to replace the firmware files on the FAT partition of a LE 9.2.3 installation with the ones from this ZIP rpi-firmware-9e3c23c.zip - you can do that eg on a windows (or linux/mac) PC.
See also this thread RPi3 Updade to 9.2.3 ending in Black Screen
It's a rather rare issue on RPi3s, but it's the reason why we haven't enabled auto-update to 9.2.3 yet. LE 9.2.4 will ship with the same firmware files as the one in the ZIP - so far this fixed all RPi3 boot issues.
so long,
Hias
The latest nightly build from here Index of / (ATM LibreELEC-RPi4.arm-9.80-nightly-20200621-7864ad7.img.gz) contains current state of RPi4 development.
Hardware H264 decoding is currently disabled by default (as it causes crashes when seeking or stopping), if you're willing to take the risk you can enable it in player settings. 4k HEVC hardware decoding works fine, though.
The KMS driver doesn't support 4k output yet, so it'll be limited to 1080p. HBR, HDR aren't implemented either and proper multichannel output is also missing ATM.
So, you have been warned, test it at your own risk.
so long,
Hias
Ah, seems the imx6 change was incomplete, it missed to disable the optional dvb drivers (which aren't compatible with the current 5.7 kernel and disabled in most other projects). I'll ping our imx6 maintainer again 
You can easily fix that yourself, just set DRIVER_ADDONS_SUPPORT="no" in ~/.libreelec/options. You can also change that in projects/NXP/options but if you don't need these drivers disabling globally is easier (and saves a bit of build time).
Whenever you change DRIVER_ADDONS_SUPPORT you have to rebuild kodi (just scripts/clean kodi before the build), otherwise kodi may end in a crash-loop.
so long,
Hias
Please post your full samba.conf. And also please post full logs to a paste site and snippets as inline code - dealing with screenshots is a PITA.
You will get the incompatible/old style message in journal if you removed the line which says "do not remove":
# samba.conf v4 (do not remove)You'll also get that (or similar warnings) in journal if you use a have an old .config/samba.conf created on earlier libreelec versions which shipped with samba3.
That line is used by the config script to check if the config file matches the currently used samba version, and if it's missing or on the wrong version the file will be ignored.
so long,
Hias
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 1see 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:
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