Posts by slim0287

    OK, I am sorry it took some time to get back to this issue. My Pi5, in fact the new one I referenced earlier, now has a similar problem: When I switch to a different HMDI input on the TV, after some time when I switch back the display is no longer present. I need to reboot the Pi5 through ssh to get it back.

    I've already taken the steps outlined above,forced hotplug in cmdline.txt and created a new EDID file. But I have the same problem-- after a reboot it works fine, but when I switch to a different HDMI port and then switch back after some time (my most recent test was a 5 minute delay), there is no longer a display and I need to reboot.

    I followed Da Flex instructions and created a log through ssh:

    https://paste.libreelec.tv/true-malamute.log


    Any help is appreciated.

    My problem was that HDMI0 stopped working. It was flaky at first and often required a reboot to get a display output. Then it simply stopped working. I switched to HDMI1 and now have video output. I swapped between Raspberry PI OS and LibreELEC a few times during the diagnosis of this, as well as adding vc4.force_hotplug=1 and sometimes video=HDMI-A-1:4096x2160@60D to my cmdline.txt (neither cmdline.txt modifications were important). I admit I ought to have tried swapping ports sooner but cie la vie!


    I handle the hardware carefully so I am surprised I had this problem. I've had perhaps ten or so Pis over the years and don't recall having the hardware fail on me. This Pi5 clearly isn't very old so the hardware issue is disappointing.


    Thanks for the advice Da Flex , I appreciate your help.

    I have another Pi5 that I am using and is currently working per your suggestions.

    In the interests of helping the community, I'll try again with the original Pi5 that is experiencing the display issues and produce the log you are asking for. However, I have no display output so I cannot use the GUI as you suggest in step 1 for enabling the debug log mode. I'll go through the wiki and look for a command line approach for enabling the debug log mode. This may take me a few days because I have some other projects around the house to get to plus I'd like to have some fun this weekend.

    Oh thanks for the reference. I had forgotten to write earlier that I tried force hotplug but I was using config,txt and did not know it had moved to cmdline.txt since LE10.


    I'm now having all kinds of problems getting that Pi5 to display no matter what OS I put on it. The machine does boot up and I can SSH into it, but whether it is libreelec, Raspberry Pi OS, or dietpi, I get no display. I'll work to get this sorted out so I can try your suggestion.

    I've done a clean install on my RPI5. It works great in terms of installing addons, setting up wireguard, and watching programs. However when I either reboot the Pi or I turn the TV off, the Pi no longer outputs an HMDI signal. I can log in remotely and head /sys/class/drm/*/status shows me the HDMI is connected however there is no signal, as reported by the TV. I've tried systemctl restart kodi and getedid create but they don't help, I've tried different TVs, different HDMI cables, and plugging into the other HDMI port on the Pi but nothing helps.


    Andy advice?

    Thanks chewitt. There are three errors:


    Code
    2023-01-05 04:46:55.722 T:1014    ERROR <general>: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
    
    
    2023-01-05 04:46:56.857 T:1029    ERROR <general>: SQL: [Textures13.db] SQLite error SQLITE_ERROR (no such table: version)
                                                       Query: SELECT idVersion FROM version
    
    
    2023-01-05 04:46:56.858 T:1029    ERROR <general>: Process error processing job 

    There are also three warnings but all look inconsequential. The final two errors above are the final entries in the log file while the first one occurs earlier. I know just enough to be dangerous with Linux, so while I understand DBus is a logging system and SQLite is a database system I have a hard time interpreting the errors. You mention it may be a corrupted DB file; do these errors change your advice for a path forward or should I still do what you explained?

    Thanks

    I have LE 10.0.3 running on an RPi4 and have been using the same configuration for a few years (updating through various LE versions). I rebooted the RPi4 yesterday and am now stuck on the Kodi screen-- the one that comes after the "LibreElec Just enough OS for Kodi" screen. I attached a picture below so I'm clear. SSH into the RPi4 works, it has an internet connection as measured through response pings to external sites, and it has a proper wireguard connection to a VPN service. I have tried rebooting a few times, and executed a shutdown and power up. Same result, I am at stuck at the Kodi screen.

    Any advice you have for interrogating and/or resolving my situation are gladly appreciated.