Pi4 black screen after splash

This is a problem quite similar to a lot of other RPi4 problems, but since it seems all those threads have gone cold, here I am making a new one.
I have an old Panasonic plasma tv, and after the OSMC splash screen, it goes black. This wasn’t always a problem though. When I first got the tv last month, I installed the latest version of OSMC (don’t quite remember which version exactly) and I experienced this issue. After some fiddling with disconnecting the power to the tv and the pi, removing the sd card and randomly plugging in cables I finally got it working and didn’t touch any cables. Ever since then, everything worked fine through updates and restarts.
Recently I disconnected the HDMI cable from the tv however, and it has stopped working again.
OSMC works just fine on other monitors, only this tv seems to be problematic.


Now for the logs
Here’s my get-logs -A output, and here’s the same log on GitHub in case something happens to the first link.
And here’s the output of dmesg shortly after a reboot.
My sounds similar to what’s described in this post by @PapaLazarou, due to the errors with the audio device being spammed into both logs, but none of the fixes there helped me, and the difference is that I never touched any 4k settings. The only thing I changed for this error to appear was disconnecting my HDMI cable and reconnecting it again.

Looking through my logs I have found the same problems as described in the post though:
kodi.log starts out with

2022-11-15 21:55:14.349 T:703      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-11-15 21:55:14.366 T:703      INFO <general>: CAESinkALSA - Unable to open device "sysdefault" for playback
2022-11-15 21:55:14.379 T:703      INFO <general>: CAESinkALSA - Unable to open device "bluealsa" for playback
2022-11-15 21:55:14.382 T:703      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-11-15 21:55:14.383 T:703      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-11-15 21:55:14.384 T:703      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-11-15 21:55:14.385 T:703      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-11-15 21:55:14.385 T:703      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-11-15 21:55:14.385 T:703      INFO <general>: No Devices found - retry: 4

Then it gives up and clogs the log with

2022-11-15 21:56:05.512 T:704      INFO <general>: CActiveAESink::OpenSink - initialize sink
2022-11-15 21:56:05.512 T:704      INFO <general>: CAESinkALSA::Initialize - Attempting to open device "@"
2022-11-15 21:56:05.515 T:704      INFO <general>: CAESinkALSA - Unable to open device "sysdefault" for playback
2022-11-15 21:56:05.516 T:704      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-11-15 21:56:05.516 T:704      INFO <general>: CAESinkALSA - Unable to open device "front" for playback
2022-11-15 21:56:05.516 T:704     ERROR <general>: CAESinkALSA::Initialize - failed to initialize device "@"
2022-11-15 21:56:05.516 T:704     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2022-11-15 21:56:05.516 T:703     ERROR <general>: ActiveAE::InitSink - returned error

I should also note that every time kodi attempts to open a connection or whatever it’s doing in the above, my TV turns on. Even disabling cec on the OSMC side still causes this, so I’m guessing my TV is detecting some attempt at establishing a connection and turns on in response (though it doesn’t change to the HDMI input the Pi is on as it does with my Chromecast :thinking:).

And the output of dmesg contains thousands of lines of

[   40.041812] hdmi-audio-codec hdmi-audio-codec.1.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19

Changing all occurences of vc4-kms-v3d in config.txt with vc4-fkms-v3d makes it boot successfully, but with not audio devices, so I’m pretty sure kodi can’t find my TVs built in speakers anymore.

I also tried running edid-decode on practically every file in /sys/class/drm/ named edid, but all of them failed with the error EDID extract of '/sys/class/drm/[several subfolders]/edid' failed: unknown format.


I’ve tried numerous different config.txt and config-user.txt configurations, all with no luck, and I really don’t see how it could suddenly stop working after being just fine for over a month. I’m out of ideas at this point, so any help is appreciated.

Small update: I tried connecting a speaker through the 3.5 mm audio jack. Starting with vc4-fkms-v3d works fine, it even plays audio through the HDMI port now, but none of my videos want to play. I can also switch the audio device to Headphones to play audio through the audio jack.

Going back to vc4-kms-v3d still shows a black screen, but the logs don’t seems to have any errors anymore, weirdly enough. Here’s the log for that one. I went into the web UI and looked at the available audio devices there, and the only one was Headphones, which was selected by default. dmesg still throws [ 13.294703] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19, but this time it’s only 4 times instead of the previous couple thousand. The dmesg log also shows some failed attempts at loading some sound cards:

[    6.548267] pisound: Reading card info failed: -22
[    6.548312] pisound: pisnd_spi_init failed: -22
...
[    6.657163] vc4_hdmi fef00700.hdmi: Could not register sound card: -517
...
[    6.663315] vc4_hdmi fef00700.hdmi: Could not register sound card: -517

Sound IS working though, using the Kore app to control Kodi I can clearly hear the GUI sounds through the audio jack, so now I’m even more confused.
It seems like the sound device isn’t the main cause of the black screen, so I don’t really now what to make of this. Maybe someone who knows the inner working of fkms vs. kms can explain what exactly the difference here is?

We’ll be updating the kernel version soon. It might be worth waiting for that and seeing if it resolves your issue

Cheers

Sam

1 Like

@sam_nazarko Is there anywhere I can follow the development of this? Like a GitHub issue or something that specifically tracks the kernel update?

You can follow GitHub for commits.