Raspberry PI 4 blank screen after splash screen

I have the same problem, but I managed to ssh into the box.

doing a grep hdmi on dmesg gives:

$ dmesg |grep hdmi
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=DC:A6:32:85:29:60 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait quiet osmcdev=rbp4
[    6.263422] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present!
[    6.265393] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])
[    6.266754] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present!
[    6.274930] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])
[   10.575918] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   10.592009] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   10.592594] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   10.593539] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   10.594128] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   12.101063] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   12.118246] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   12.118840] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   12.121177] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   12.121782] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   13.627067] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   13.641916] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   13.642495] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   13.643543] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   13.644146] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   15.149424] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   15.164232] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   15.164815] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   15.165716] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   15.166275] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   16.671529] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   16.686387] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   16.686967] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19
[   16.687913] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   16.688519] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

I can provide additional logs if required.

I’m not sure this applies to you, since “the same problem” could cover several possible cases, but there was a partial workaround provided a few days ago for devices that aren’t connected to HDMI: Headless Pi boot failure - #3 by fzinken

It’s partial in the sense that it only works for (no-HDMI) headless devices where the Kodi GUI isn’t required.

Not sure if this reply was intended for me, but my pi4 is connected by HDMI to a monitor and is intended to be used always connected to a screen/TV. I can ssh to it, so would be happy to access it and paste any logs that are necessary to identify the problem.

Yes, it was for you. Since you can SSH to the box, please run grab-logs -A and post the URL it returns.

The generated log was about 37Mb because of a lot of repeated lines in the Kodi Old Log section. So I deleted about 30k repeating lines and uploaded it manually :
https://paste.osmc.tv/asoviwazux

[ the following section was repeated and I deleted the lines between Aug 25 and Aug 26:

2021-08-25 13:33:28.334 T:482      INFO <general>: CActiveAESink::OpenSink - initialize sink
2021-08-25 13:33:28.334 T:482     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2021-08-25 13:33:28.334 T:481     ERROR <general>: ActiveAE::InitSink - returned error
2021-08-26 08:47:26.645 T:482      INFO <general>: CActiveAESink::OpenSink - initialize sink
2021-08-26 08:47:26.645 T:482     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2021-08-26 08:47:26.645 T:481     ERROR <general>: ActiveAE::InitSink - returned error

]

TBH, the log shows no EDID information, so it’s probably the same issue as others have been seeing, though the use of a monitor has confused the issue a bit.

Sam has produced a kernel fix that you might wish to try out.

I’d suggest you wait a bit until the gateway 502 problem has been fixed.

This is fixed.

Still no hdmi output (I get a blue screen with the OSMC logo at boot and then everything goes blank. The monitor then complains of no signal on HDMI input).

Here are the new logs:
https://paste.osmc.tv/kiwojuquhe

It looks like something – probably the “fix” – is causing the kernel to panic.

This one needs to be passed back to @sam_nazarko

Any update on this? My rpi4 is a spare one so I can test things out if needed. Would be happy to run test builds and so on - though at the moment I don’t have the setup to compile osmc myself.

It looks like an upstream issue still.

hi sam I did kernel fix.

now there is no internet access it is fully stuck as far as I can tell, there is no way to ssh in the pi now to get an updated log

this was before the crash and the fix
https://paste.osmc.tv/ojiqegawox

I have Rpi3B+, new OSMC installation and try get it working with composite video. The blue OSMC logo displays fine as some startup texts, but then display turns black (if unplug AV-cable get ‘No signal’, so it’s actually sending black). On HDMI cable it works just fine. I did the buster-devel update instructed above, it installed 5.10.60-2-osmc. I can connect with SSH, tvservice reports PAL display which is correct. I can also connect with web-browser on HTTP-address. My logs at: https://paste.osmc.tv/nexahireco

What would you instruct me to look at?

tvservice -s
state 0x80001 [PAL 4:3], 720x576 @ 50.00Hz, interlaced


Sep 30 20:02:58 osmc kernel: checking generic (3ea65000 195000) vs hw (0 ffffffff)
Sep 30 20:02:58 osmc kernel: fb0: switching to vc4drmfb from simple
Sep 30 20:02:58 osmc kernel: Console: switching to colour dummy device 80x30
Sep 30 20:02:58 osmc kernel: raspberrypi-firmware soc:firmware: Request 0x00030066 returned status 0x80000001
Sep 30 20:02:58 osmc kernel: vc4-drm soc:gpu: [drm] Couldn’t stop firmware display driver: -22
Sep 30 20:02:58 osmc kernel: vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])

I burn older OSMC version “2020.11-1” to SD-card, and now composite video works fine (otherwise the same setup). Only had to set sdtv_mode=2 (European PAL).

Hi Everybody,

Long time user/lurker of OSMC - thanks to Sam and the team for everything they do! Just tried to install the latest Pi4 image and I’m getting the blank screen/no HDMI output issue as other folks. Is there any update on this?

I have not been able to SSH onto my device, but I put the drive into another Linux machine I have and pulled off the kodi.log - hope it helps…

Cheers

Tim

kodi.log

I’d suggest 1) trying another display; 2) confirming if you can see the installer come up.

Sam

Hi Sam,

Yes I do see the installer upon first run and I’ve also tried with a computer monitor with the same results :pensive:

Cheers

Tim

Are you using the latest version on the Download page?

I think so - I selected 2021.11-2 from the options given by the OSMC installer/imager.

Yes – that’s the latest version.

You say you can’t SSH. Just to clarify, you’re using a Wired Ethernet connection?

Sam