, after some investigation it seems that the Z890 chipset has a fault, in some circumstances you need to "disable" internal graphics
No. LE is only supporting a single GPU. If there are more than one the first configured wins the race. Unfortunately both GPUs may have been configured in parallel causing a crash.
Look for "xorg-configure" lines in your log.
LE13 RPi4 nightly build.
It seems that Wifi isn't connecting, so when it boots it goes into a loop of not connecting to the video database, and then back, and never boots.
Has anyone else seen this? Might be because I am using a network database for all my systems.
Getting logs is going to be a pain, because of the lack of network!
K22 has some basic DB connection handling, so if an SQL database is configured Kodi will make a number of connection attempts until the connection is available; and after X attempts it fails and restarts. On restart .. rinse/repeat.
K21 and earlier tries once and if the DB is not accessible it fails and falls back to the local DB (usually blank).
The "wait for network" setting can be increased in the LE settings add-on, but that won't ever fix the underlying issue of there being no network connection; that's what needs to be fixed.
The "wait for network" setting can be increased in the LE settings add-on, but that won't ever fix the underlying issue of there being no network connection; that's what needs to be fixed.
Thanks. I'll look into it over the weekend.
My RPi5 is using the same version, and that works fine with the SQL database, but it's on a wired connection.
My RPi5 [snip] works fine with the SQL database, but it's on a wired connection
QED 
QED
Yep, but (at least in principle) my network is fine and the Pi was connecting to it before.
This may be one of those cases when once I've configured it, it will be fine. But for an update or a new connection, to not boot rather than reverting to an empty database does feel like a regression.
Anyway, I'll do some troubleshooting over the weekend and report back.
It seems that Wifi isn't connecting, so when it boots it goes into a loop of not connecting to the video database, and then back, and never boots.
I had a similar issue where the rpi5 would boot (image:20250828 12.2) and nothing would happen, screen stayed black, but i could still ssh into it. (and this was after a couple of days working just fine). So I forced an update (same image) and the problem disappeared. Until I read your post I thought it was a one off. So I figured to at least mention it here just in case.
There are several K22 database API version bumps in recent time, so depending on what version you are updating from and to; the system may run a database upgrade in the background on boot. In theory Kodi should be showing the splash screen with a status message when that happens, but I can't put hand on heart and say that I've always seen it. So if you see a black screen, SSH in and check the kodi.log to see whether that's happening (or not) before forcing an update.
So if you see a black screen, SSH in and check the kodi.log to see whether that's happening (or not) before forcing an update.
Yeah, I think I jumped the gun there. However there was no splash and I've seen the db migration take place over the years and afaict that should happen during the first boot of a newer version. I upgraded a few days earlier and it worked just fine, then all of a sudden hung on the black screen one day.
I checked that its not the hardware nor the sdcard . I use them industrial cards because they are speedy for reading and writing, they're cheap and the occasional restore is really really fast (for micro sdcards that is).
Other than a dirty write I have no clue what could have caused it.
Yep, but (at least in principle) my network is fine and the Pi was connecting to it before.
This may be one of those cases when once I've configured it, it will be fine. But for an update or a new connection, to not boot rather than reverting to an empty database does feel like a regression.
Anyway, I'll do some troubleshooting over the weekend and report back.
Moved it to my desk. Plugged the wired network in. Everything worked fine. Then I went into the settings and saw that it was using wifi not wired. Moved it back to its normal place. Still working.
I do find that live/recorded TV doesn't work well on this one, so it may be that wifi signal isn't great at that place.
