pastekodi -c >my.log
no chance but
"journalctl | paste"
worked.
I don't know if it makes a difference if the TV is off during boot but as I switched it on, no image was coming up, so I booted it again with the TV on for a short while.
if there is nothing in the logs that tells something I continue with #12
no chance but
Error message visible? No my.log file created? Empty my.log file created?
Original RPi HDMI Adapter and Power Supply
^ is this a PSU for the original RPi, i.e. 1st/2nd/3rd gen, or an original RPi4 PSU? .. there's an error in the kernel log which looks like a firmware crash, and one possible cause for that kind of thing is an inadequate power supply. No guarantees that's the issue with video output, but low-spec PSUs surface all kinds of odd problems and RPi4 needs a PSU that delivers more amps than earlier models.
Can you post output of "vcgencmd log msg" (e.g. piped through paste if that working).
Can you confirm you have no custom settings (like overclock) in config.txt?
If you have access to another pi4, then trying it with your sdcard, power supply etc may be useful.
I'd also be interested if RPiOS works correctly? It could be a hardware issue, but I'd expect that to affect other distributions.
Would the output from dmesg show any instance of an under voltage condition.
Would the output from dmesg show any instance of an under voltage condition.
Ideally it should. But the log shows:
Feb 02 15:29:50 LibreELEC kernel: Firmware transaction timeoutwhich means firmware isn't responding to requests (it has likely crashed).
And as the firmware checks for under-voltage, it may be impossible to get that information into kernel log.
At this stage it would be simpler to start over again as I suggested above. Just the bare metal keyboard/mouse and HDMI screen attached to the RPI4 and boot from there.
Best trying from fresh instead of going to any additional expense if you don’t have to. I will suggest trying a different HDMI cable during the process if you have one. As you know all HDMI cables are not created equally. Don’t forget to use the HDMI connector nearest the power outlet on the RPI4 too. I suffered similar symptoms and in my case a replacement HDMI cable did the trick.
t trying a different HDMI cable
I have to buy it first, as I have only one cable, as I use my Raspis headless
Could you borrow one or use one from another appliance you already have connected up.
Could you borrow one or use one from another appliance you already have connected up.
I have to check in office tomorrow, I could be lucky
Error message visible? No my.log file created? Empty my.log file created?
creates only a file pastekodi.log with a single line:
System log output for: LibreELEC (official): 10.0.3
Can you post output of "vcgencmd log msg" (e.g. piped through paste if that working).
vcgencmd log msg >vcgencmd.log creates an empty file named vcgencmd.log
Can you confirm you have no custom settings (like overclock) in config.txt?
nothing done, all default
Ideally it should. But the log shows:
Code Feb 02 15:29:50 LibreELEC kernel: Firmware transaction timeoutwhich means firmware isn't responding to requests (it has likely crashed).
that exists log is here: Ubuntu Pastebin
that exists log is here: Ubuntu Pastebin
More words would be useful. Can you confirm that you installed Ubuntu on your pi that has problems with libreelec,
and it produces that error in dmesg?
To rule out any impact from connected devices, can you boot the pi with as little as possible connected (no usb devices, no hat, no hdmi).
Just Pi, power and ethernet (so you can ssh in and get dmesg log). Does the dmesg have that error in? If so I'd say it's a hardware problem with that pi.
Doing a swap test (with a different pi4) could also confirm this.
More words would be useful.
it did the thing just before I went to bed, sorry, I just want to keep the stone rolling. I don't know in which time zone you are located, I'm in CET.
"failed" is mentioned eight times in Ubuntu Pastebin (I used in Ubuntu's service as I could not register at PasteBin) in addition to timeouts
[ 0.123750] raspberrypi-firmware soc:firmware: Attached to firmware from 2022-10-05T15:52:04, variant start_x
[ 0.127087] raspberrypi-firmware soc:firmware: Firmware hash is 6c57d97fa8066929a2fee6e4fac6d64ad62506c9
...
[ 5.722785] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 6.826628] ------------[ cut here ]------------
[ 6.826639] Firmware transaction timeout
[ 6.826687] WARNING: CPU: 0 PID: 32 at rpi_firmware_property_list+0x1ec/0x26c
[ 6.826689] Modules linked in: brcmfmac brcmutil cfg80211 bcm2835_isp(C+) rpivid_hevc(C) bcm2835_codec(C+) videobuf2_dma_contig bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common videodev rfkill mc bcm2835_gpiomem nvmem_rmem fuse
[ 6.826726] CPU: 0 PID: 32 Comm: kworker/0:1 Tainted: G C 5.10.110 #1
[ 6.826728] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
[ 6.826736] Workqueue: events get_values_poll
...
[ 6.826863] hwmon hwmon0: Failed to get throttled (-110)
...
[ 9.519968] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-v3d frequency: -110
...
[ 12.559984] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 18446744073709551506 (-34)
[ 13.573300] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-core frequency: -110
[ 32.053290] cam-dummy-reg: disabling
[ 185.531482] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=1)
[ 185.531551] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=1)
[ 185.531614] : Unregister from media controller
[ 185.531620] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531624] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531628] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531631] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.532540] bcm2835-codec bcm2835-codec: Removing bcm2835-codec, encode
[ 185.532699] bcm2835_mmal_vchiq: mmal-vchiq: VCHIQ close failed
[ 185.533009] bcm2835-codec bcm2835-codec: Removing bcm2835-codec, decode
[ 185.533114] bcm2835_mmal_vchiq: mmal-vchiq: VCHIQ close failed
[ 2689.839524] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 2689.839546] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2689.855354] 8021q: 802.1Q VLAN Support v1.8Can you confirm that you installed Ubuntu on your pi that has problems with libreelec,
and it produces that error in dmesg?
I took the Pi out of the box and used LibreELEC USB-SD Creator, as that failed, I opened this thread, nothing else, no modification etc.
I took the SD Card with "Raspberry Pi OS using Raspberry Pi Imager" from my running Pi 4 8 GB. That booted and was usable.
Afterwards, I tried OSMC (OSMC Installer), which runs well.
I can try to boot it up with Ubuntu if you like.
Doing a swap test (with a different pi4) could also confirm this
I should be able to do this tomorrow (maybe tonight, childcare is on me tonight)
I can try to boot it up with Ubuntu if you like.
Ah - the link was labelled "Ubuntu pastebin" which I assumed you had named as a failed dmesg from an Ubuntu log.
But I see now that was just a default label as the paste site was hosted by Ubuntu. Don't worry about the Ubuntu boot.
A swap test will be more useful.
creates only a file pastekodi.log with a single line:
System log output for: LibreELEC (official): 10.0.3
Thanks. From this thread I assume the following vcgencmd command is stopping the pastekodi script.
Did you try a fresh install and swap out the HDMI cable or are you still at the same install with the original setup.
I could borrow a Pi 4B 4GB, it is around the same age. I included that in my tests
Test #1
Same SD-Card, used in different PIs. During each test run, each Pi were only connected to the network by wire and my HP Screen:
As it worked with the 1 and 2, I installed Librespot addon - Add-on Support - LibreELEC Forum
Test #2:
Booting the borrowed Pi 4B 4 GB but being connected to my Panasonic Viera Plasma TV (TX-P55VT30J
TV is showing Kodi 
even after booting it again and again, so it is stable
That hardware defect is bizarre as Pi OS and OSMC don't mind that defect.
Anyway, the warranty claim is filled.