Posts by dannyzee

Quote from dannyzee

LE display freezes at the "Just enough OS for KODI" screen, when connected through my Pioneer VSX-32 Surround amp. Other devices, like my old WD boxes have no such issue. This issue started with my old Pi4, but, I just gave up on it. Now I have a new 8GB Pi5. Installed LE on an SSD, does the exact same thing (display freezes at the splash screen) If I connect the other HDMI out to another monitor, or to the LG TV, it boots fine, but the TV connected to the VSX-32 will just show a blank screen. This is very annoying, as I cannot use my Surround system, unless I hook one HDMI (from the PI)to the surround system (for the sound output) and the other HDMI directly to the TV for the video stream.

Like I said, if I bypass the surround system, LE works fine, but fefuses to go beyond the splash screen(The system is running, I can generate UI sounds, just can't see what I am doing)

Log File: https://pastebin.com/sb0DWDMc

This is a Brand new Untouched image file from https://releases.libreelec.tv/LibreELEC-RPi5…4-12.0.1.img.gz

TIA for any insight!!

Display More

Sorry, I wish to add, I tried to look at the log, and there appears to be at least 2 startups in the log? The initial startup failed to get past a black screen with "LibreELEC (official) 12.0.1" in the top left of the display. (This, even though I was hooked directly to a computer monitor, bypassing my AVR).

A re-boot (some number of hours later) connected directly to a 1080P Monitor, and LE started up. I enabled Debug Logging, shut down, connected LE to my Pioneer VSX-32 AVR, rebooted, and captured the Log file mentioned in the first post. (Also, in the quoted text)

LE display freezes at the "Just enough OS for KODI" screen, when connected through my Pioneer VSX-32 Surround amp. Other devices, like my old WD boxes have no such issue. This issue started with my old Pi4, but, I just gave up on it. Now I have a new 8GB Pi5. Installed LE on an SSD, does the exact same thing (display freezes at the splash screen) If I connect the other HDMI out to another monitor, or to the LG TV, it boots fine, but the TV connected to the VSX-32 will just show a blank screen. This is very annoying, as I cannot use my Surround system, unless I hook one HDMI (from the PI)to the surround system (for the sound output) and the other HDMI directly to the TV for the video stream.

Like I said, if I bypass the surround system, LE works fine, but fefuses to go beyond the splash screen(The system is running, I can generate UI sounds, just can't see what I am doing)

Log File: https://pastebin.com/sb0DWDMc

This is a Brand new Untouched image file from https://releases.libreelec.tv/LibreELEC-RPi5…4-12.0.1.img.gz

TIA for any insight!!

So, to be clear, I have the Official KODI Repo installed, and tha A4KSubtitle repo installed(Which is not blacklisted) and somehow that supposedly includes Banned add-ons?

I did have Zomboided installed, so I could use OpenVPN, but, had to uninstall VPN to make the debug log size smaller, was having trouble getting log small enough.

I am a new user, so, this will be moderated, feel free to not post it, but, maybe reply what I have that is banned?

Quote from chewitt

LE is almost certainly not "freezing at the splash screen" .. but something prevents it from being able to correctly setup an output display device and thus the boot splash is never overwritten by the Kodi desktop appearing. I have a hunch this is related to EDID data on the HDMI connection (or lack thereof) but a debug log from the RPi will normally allow us to see if that's the issue.

So, I look in the log, I see " error <general>: [display-info] Error parsing EDID:"

What can I do about this?

Ok, Here it is, (I think?)

https://paste.libreelec.tv/enormous-pony.log

Or, this one ran a minute or so longer

https://paste.libreelec.tv/happy-toad.log

Thanks

You make the pastebin thing seem easy, but the log needs to be split in two, or it exceeds the file size limit, and after I split it, I get this from pastebin

"Pastebin’s SMART filters have detected potentially offensive or questionable content in your Paste.
The content you are trying to publish has been deemed potentially offensive or questionable by our filters, because of this you’re receiving this warning.
This Paste can only be published with the visibility set to "Private"."

What can I do, as you can not likely see private pastes?

Like the title says, LE freezes at the "Just enough OS for KODI" screen, when connected through my Pioneer VSX-32 Surround amp. Other devices, like my old WD boxes have no such issue. This issue started with my old Pi4, but, I just gave up onit. Now I have a new 8GB Pi5. pup LE on an SSD, does the exact same thing (freezes at the splash screen) If I connect the other HDMI out to another monitor, or to the LG TV, it boots fine, but the TV connected to the VSX-32 will just show a blank screen. This is very annoying, as I cannot use my Surround system, unless I hook one HDMI (from the PI)to the surround system (for the sound output) and the other HDMI directly to the TV for the video stream.

Like I said, if I bypass the surround system, LE works fine, but fefuses to go beyond the splash screen(The system is running, I can generate UI sounds, just can't see what I am doing)

So, I thought I would just run KODI installed on Rasbian bookworm. It will run in a window, but will refuse to run fullscreen. (Just shows a black screen)

I think this might be related to the display driver, (as it seems to be not functioning no matter how I try to run it.) I have also tried XBian, it gets past the splash, to the KODI screen, then locks as well.

I read this on Raspberry Pi forum"Kodi on the Raspberry Pi 4 will only function if you are using the Open Source drivers! This is the "GL (Fake KMS) OpenGL desktop driver with fake KMS" on raspi-config, which is currently the default on the Raspbian images for the RPi 4. If you select the Broadcom/Legacy driver, it won't work!"

I can see that I am using the broadcom driver, but, have no idea how to change it, or, if changing it is a good idea? (That post was about the Pi4, but, I did have this exact issue on the Pi4 as well)

TIA for any insight!!