No picture after logo on Rpi4

isen · 28 December 2021 14:18

Yesterday I upgraded OSMC on my Rpi4 to the december update. After the reboot, I saw the blue OSMC logo, then nothing. The TV says no input signal. I tried:

Adding hdmi_safe=1 to config-user-txt.
Commenting out everything in config-user.txt.
Another SD-card with fresh image (november release, which worked before). Boots and installs but after reboot no image.
Same SD-card with two other RPi4:s. Here’s a strange thing; They boot up exactly as they should, and everything looks fine. When I reboot, then black screen again. The same thing happened on both the additional RPis.

I can access it by ssh.

The log gets filled (repeatedly) with the following. I don’t know if that’s the culprit…

INFO <general>: CAESinkALSA - Unable to open device "default" for playback
ERROR <general>: CAESinkALSA::Initialize - failed to initialize device "default"
ERROR <general>: CActiveAESink::OpenSink - no sink was returned
ERROR <general>: ActiveAE::InitSink - returned error

Note, this is not like Raspberry Pi 4 shuts off screen shortly after OSMC logo, which has similar symptoms, but I have a 3A supply and no ext HD.

Log: https://paste.osmc.tv/igovixekif.xml

UPDATE
I installed the August release and it worked. I’ll stick with that a while.

sam_nazarko · 30 December 2021 03:25

Without full logs, it’s hard to speculate as to the issue

Cheers

Sam

isen · 30 December 2021 11:41

Ok, I see. As I couldn’t get any picture, it was impossible to get the logs out from MyOSMC, as preferred. I have saved the original SD-card, perhaps there is some other log stored there than the one I posted (kodi.log).
However, as I now have a running system, albeit not the latest version, I will not dive deeper in this at the moment. When I get the time I will clone my SD and upgrade.

Have a nice new year, and thanks for a great OS!
/Chris

sam_nazarko · 30 December 2021 14:08

You can get logs via the command line if you are able to login via SSH.

isen · 30 December 2021 14:10

Ah, that would be nice. you mean the same full log as MyOSMC yields? How do I do that?

sam_nazarko · 30 December 2021 14:12

Yes – just run grab-logs -A

ActionA · 30 December 2021 14:12

Details regarding how to access the command line interface can be found here on our Wiki: Accessing the command line - General - OSMC

Command to obtain logs from command line is grab-logs -A

isen · 30 December 2021 14:16

Thanks, that was really useful information!
I’ll fire up the faulty instance soon and post the logs.

retroresolution · 30 December 2021 18:46

Hi,

I have a Pi 4 which was previously running a build of Libreelec with a workaround for H265 hardware decoding.

I’ve installed the December 2021 OSMC Pi 4 image on the device today, and run into various issues related to the OP (TV displaying ‘no signal’ following initial setup).

Initially I had the Pi connected to a monitor via DVI; whilst the display worked during and after setup, neither H265 or X264 playback appeared to use hardware decoding. I located a forum post which suggested that connecting to a standard TV via HDMI resolved the issue.

I reinstalled the December 2021 Pi 4 image, connected the Pi to the 1080p HDMI TV, and ran into the same issue as noted in the OP.

I tried using the August 2021 image, as noted in an update on the original post, but for me this didn’t resolve the issue - during the initial setup the display is fine, but after the system reboots, the OSMC logo is briefly displayed, then the TV shows ‘no signal’.

Any solutions gratefully received!

isen · 3 January 2022 06:44

Ok, here are the logs:
https://paste.osmc.tv/qoyipifidu
/Chris

retroresolution · 15 January 2022 20:49

Does anyone have any insight into the display problem on the raspberry pi 4?

I’ve been wondering if there’s any connection to the relocation of certain firmware to on-board eeprom storage, rather than keeping everything on the SD card?

This is something I’ve tried researching, but not had any success with.

sam_nazarko · 15 January 2022 20:49

You could use the Raspberry Pi OS to update that – but I don’t think that will be an issue.

PapaLazarou · 5 February 2022 18:05

This happened to me as well on a RPi 4 with the latest OSMC. I found a way to get Kodi back, but then it stopped working the next day, so I edited this post with further changes. I think the easiest way for me to explain is to post what happened from start to finish, the changes I made near the end may work for you as well.

OSMC worked fine for a good couple of weeks in 1080p so I started playing with getting 4K output using the Whitelist option ([HowTo] Guide to the Kodi whitelist function and related settings). Amongst other things, I think I selected a few resolutions/refresh rates that the TV could not do. 4K playback worked fine, then I turned off the TV and when I came back to it later and turned it on the screen was black.

Things I tried that didn’t work:

I tried to send a 1080p YouTube file to Kodi using Yatse on my phone hoping the resolution would change to 1080p and the display would return on the TV, but no luck.
I rebooted using Yatse and no dice either, splash screen then black screen.
So I set /boot/config-user.txt to this:

[HDMI:0]
hdmi_ignore_cec=1
hdmi_group=1
hdmi_mode=16
hdmi_drive=2

After rebooting again using ssh (from this point on Yatse wouldn’t work any more) I could see the info in the corner of the TV screen showing 1080p / 60 Hz for a brief moment, then the splash screen appeared followed by the screen going black. However I left the file like that.

I changed the following line in /boot/config.txt:

dtoverlay=vc4-kms-v3d,cma-512

to

dtoverlay=vc4-fkms-v3d,cma-512

The output was very low resolution and the GUI was slow. This wasn’t very good at all, so I didn’t even try to play anything and I changed it back.

I stopped Kodi using “sudo systemctl stop mediacenter”, renamed my hosed .kodi folder to something else and restored a backup taken from just after first run (I took a backup shortly after installing OSMC on the RPi 4 and before migrating RPi3 OSMC installation), rebooted, and after the splash screen Kodi appeared (with vc4-kms-v3d in /boot/config.txt).
So something in the hosed .kodi folder is causing problems. I checked kodi.log and found it starts going wrong here:

2022-02-05 00:34:10.705 T:605      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-02-05 00:34:10.728 T:605      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:34:10.729 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-02-05 00:34:10.729 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-02-05 00:34:10.730 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:34:10.731 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:34:10.732 T:605      INFO <general>: No Devices found - retry: 4
2022-02-05 00:34:12.237 T:605      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-02-05 00:34:12.256 T:605      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:34:12.257 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-02-05 00:34:12.258 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-02-05 00:34:12.259 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:34:12.259 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:34:12.259 T:605      INFO <general>: No Devices found - retry: 3
2022-02-05 00:34:29.920 T:605      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-02-05 00:34:29.939 T:605      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:34:29.940 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-02-05 00:34:29.940 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-02-05 00:34:29.941 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:34:29.942 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:34:29.942 T:605      INFO <general>: No Devices found - retry: 2
2022-02-05 00:34:31.448 T:605      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-02-05 00:34:31.466 T:605      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:34:31.467 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-02-05 00:34:31.467 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-02-05 00:34:31.468 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:34:31.469 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:34:31.469 T:605      INFO <general>: No Devices found - retry: 1
2022-02-05 00:34:32.975 T:605      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2022-02-05 00:34:32.993 T:605      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:34:32.994 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi0" for playback
2022-02-05 00:34:32.995 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi0,DEV=0" for playback
2022-02-05 00:34:32.995 T:605      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:34:32.996 T:605      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:34:32.996 T:605      INFO <general>: Found 0 Lists of Devices
2022-02-05 00:34:32.996 T:606      INFO <general>: CActiveAESink::OpenSink - initialize sink
2022-02-05 00:34:32.996 T:606     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2022-02-05 00:34:32.996 T:605     ERROR <general>: ActiveAE::InitSink - returned error

And later on this gets spammed to the log repeatedly:

2022-02-05 00:34:34.498 T:606      INFO <general>: CActiveAESink::OpenSink - initialize sink
2022-02-05 00:34:34.498 T:606     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2022-02-05 00:34:34.498 T:605     ERROR <general>: ActiveAE::InitSink - returned error

Whereas the working .kodi folder has this in kodi.log:

2022-02-05 00:45:13.306 T:600      INFO <general>: CAESinkALSA::EnumerateDevice - device default description 
2022-02-05 00:45:13.308 T:600      INFO <general>: CAESinkALSA::EnumerateDevice - device @ description 
2022-02-05 00:45:13.308 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround71" for playback
2022-02-05 00:45:13.309 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround51" for playback
2022-02-05 00:45:13.309 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround71" for playback
2022-02-05 00:45:13.310 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround40" for playback
2022-02-05 00:45:13.310 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround51" for playback
2022-02-05 00:45:13.310 T:600      INFO <general>: CAESinkALSA - Unable to open device "surround71" for playback
2022-02-05 00:45:13.335 T:600      INFO <general>: CAESinkALSA - Unable to open device "btaudio" for playback
2022-02-05 00:45:13.336 T:600      INFO <general>: CAESinkALSA::EnumerateDevice - device sysdefault:CARD=vc4hdmi0 description vc4-hdmi-0, MAI PCM i2s-hifi-0
                                                   Default Audio Device
2022-02-05 00:45:13.338 T:600      INFO <general>: CAESinkALSA::EnumerateDevice - device hdmi:CARD=vc4hdmi0,DEV=0 description vc4-hdmi-0, MAI PCM i2s-hifi-0
                                                   HDMI Audio Output
2022-02-05 00:45:13.339 T:600      INFO <general>: CAESinkALSA - Unable to open device "sysdefault:CARD=vc4hdmi1" for playback
2022-02-05 00:45:13.340 T:600      INFO <general>: CAESinkALSA - Unable to open device "hdmi:CARD=vc4hdmi1,DEV=0" for playback
2022-02-05 00:45:13.340 T:600      INFO <general>: Found 1 Lists of Devices
2022-02-05 00:45:13.340 T:600      INFO <general>: Enumerated ALSA devices:
2022-02-05 00:45:13.340 T:600      INFO <general>:     Device 1
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_deviceName      : @
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_displayName     : Default (vc4-hdmi-0 MAI PCM i2s-hifi-0)
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_displayNameExtra: 
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_deviceType      : AE_DEVTYPE_PCM
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_channels        : FL, FR
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_sampleRates     : 32000,44100,48000
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_dataFormats     : AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_streamTypes     : No passthrough capabilities
2022-02-05 00:45:13.340 T:600      INFO <general>:     Device 2
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_deviceName      : sysdefault:CARD=vc4hdmi0
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_displayName     : vc4-hdmi-0
2022-02-05 00:45:13.340 T:600      INFO <general>:         m_displayNameExtra: MAI PCM i2s-hifi-0
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_deviceType      : AE_DEVTYPE_PCM
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_channels        : FL, FR
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_sampleRates     : 32000,44100,48000
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_dataFormats     : AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_streamTypes     : No passthrough capabilities
2022-02-05 00:45:13.341 T:600      INFO <general>:     Device 3
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_deviceName      : hdmi:CARD=vc4hdmi0,DEV=0
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_displayName     : vc4-hdmi-0
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_displayNameExtra: MEI Panasonic-TV on HDMI
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_deviceType      : AE_DEVTYPE_HDMI
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_channels        : FL, FR
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_sampleRates     : 32000,44100,48000
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_dataFormats     : AE_FMT_RAW,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_U8,AE_FMT_RAW
2022-02-05 00:45:13.341 T:600      INFO <general>:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD
2022-02-05 00:45:13.341 T:601      INFO <general>: CActiveAESink::OpenSink - initialize sink
2022-02-05 00:45:13.341 T:601      INFO <general>: CAESinkALSA::Initialize - Attempting to open device "@"
2022-02-05 00:45:13.345 T:601      INFO <general>: CAESinkALSA::Initialize - Opened device "sysdefault"
2022-02-05 00:45:13.346 T:601      INFO <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2022-02-05 00:45:13.346 T:601      INFO <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE3

Next I checked dmesg and found sound card errors - two lines matching “Could not register sound card: -517” and two lines matching “ASoC: error at snd_soc_dai_startup on i2s-hifi: -19” were highlighted in red. https://pastebin.com/BAms4HxA

Changes that nearly fixed it:

Seemed like something’s going wrong with the sound. Just to try something I set hdmi_drive=1 (disabling sound over HDMI) in /boot/config-user.txt, rebooted, and got Kodi back.

Then in Kodi I found that Settings / System / Display / Resolution was resolution was set to 4096x2160 / 30Hz with overscan, labelled by the TV as V Full for some reason (I guess it means it’s bigger than the normal 3840x2160 / 30Hz) and GUI Resolution Limit was Unlimited. So as a temporary fix I re-set Resolution to 1920x1080, GUI Resolution Limit to 1080, and made sure the Whitelist was disabled in Kodi, set hdmi_drive=2 again in /boot/config-user.txt, rebooted, Kodi appeared again with UI sounds, and now I’m back to where I was before experimenting with 4K.

It looks like a lot of the settings were reset back to defaults. Checking .kodi/userdata I saw that guisettings.xml, profiles.xml, and upnpserver.xml were all re-written. Maybe some kind of attempt from Kodi to start in a safe mode. This also stopped Yatse from working after the first reboot because I don’t use Kodi’s default settings for remote control.

But the next day it stopped working again so I made more changes:

I checked the edid and saw that somehow resolutions like 4096x2160@60Hz are there but I know for a fact the TV will only display 4K at a maximum of 30Hz (checked using an Intel NUC with HDMI output running Windows 10 - when I set the refresh rate too high the screen goes black as well, but then the display control panel restores the previous refresh rate after 15 seconds and it comes back). https://pastebin.com/rrmPXWqc

So I changed my /boot/config-user.txt to ignore the edid:

[HDMI:0]
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16
hdmi_pixel_encoding=2
hdmi_drive=2

And I edited the whitelist and selected 1920x1080p at 24, 25, 30, 50, and 60Hz and 3840x2160p at 24, 25, and 30Hz.

Why did it happen?

I stumbled across the following issue on GitHub:

github.com/raspberrypi/firmware

RPi4B/Kodi goes to black screen with vc4-kms-v3d after commit 19272ccd69049aaf42c78a235a0bf37dbabd5ea7

opened 10:13PM - 09 Nov 21 UTC

mkreisl

Close within 30 days

This commit leads to a black screen (TV says no signal) after Kodi is started. …This occurs with all tested kernel versions (5.10.60 - 5.10.75 and 5.14.14) and with both Kodi 19 and Kodi 20. In dmesg the messages appear: ``` [ 113.892587] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 113.892713] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out [ 124.128612] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 124.128920] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:91:plane-6] commit wait timed out [ 134.368625] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 134.368995] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit [ 144.608695] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out [ 154.848659] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 154.849120] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out [ 165.088657] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 165.089117] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:91:plane-6] commit wait timed out [ 175.328649] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 175.329113] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit [ 185.568601] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out [ 188.481021] init: passwd-change main process (5796) terminated with status 1 [ 190.432635] cec-vc4: message ff 84 20 00 06 timed out [ 192.736595] cec-vc4: message ff 87 00 15 82 timed out [ 195.040635] cec-vc4: message f0 timed out [ 197.344605] cec-vc4: message f0 timed out [ 199.136617] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 199.136926] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] commit wait timed out [ 199.648658] cec-vc4: message f0 timed out [ 201.952655] cec-vc4: message f0 timed out [ 204.256584] cec-vc4: message 11 timed out [ 206.560662] cec-vc4: message 11 timed out [ 208.864603] cec-vc4: message 11 timed out [ 209.376644] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 209.376953] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:91:plane-6] commit wait timed out [ 211.168584] cec-vc4: message 11 timed out [ 213.472618] cec-vc4: message 22 timed out [ 215.776619] cec-vc4: message 22 timed out [ 218.080648] cec-vc4: message 99 timed out [ 219.616604] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 219.616874] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit [ 220.384652] cec-vc4: message 99 timed out [ 222.688572] cec-vc4: message ff 84 20 00 01 timed out [ 224.992583] cec-vc4: message ff 87 00 15 82 timed out [ 227.296649] cec-vc4: message 10 timed out [ 229.600630] cec-vc4: message 10 timed out [ 229.856628] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out [ 231.904602] cec-vc4: message 10 timed out [ 234.208649] cec-vc4: message 10 timed out ``` If I **use vc4-fkms-v3d** (which I have always used so far) this problem no longer occurs This means the firmware files that are present in /boot, not the kernels itself Until one commit before the one above, the problem does not occur, so it must definitely be the commit **arm_loader: Add message to release firmware framebuffer 19272ccd69049aaf42c78a235a0bf37dbabd5ea7** My /boot/config is ``` initramfs initramfs.gz followkernel gpu_mem=224 [pi4] gpu_mem_1024=70 [all] initial_turbo=1 hdmi_force_hotplug=0 hdmi_ignore_hotplug=0 hdmi_ignore_cec_init=1 hdmi_ignore_cec=0 disable_overscan=1 disable_splash=1 max_usb_current=1 dtparam=audio=on dtoverlay=gpio-ir [pi4] dtoverlay=vc4-kms-v3d,cma-384 dtoverlay=rpivid-v4l2 max_framebuffers=2 ```

As someone says here the problem seems to be intermittent for 4K displays.

If this happens again then it seems that the next steps I could try as suggested in this issue are:

Editing /boot/cmdline.txt and adding " video=HDMI-A-1:D video=HDMI-A-2:D" to the end. (Edit: Probably not the best choice, see post below for a better version.)
Editing /boot/config.txt and changing “dtoverlay=vc4-kms-v3d” to “dtoverlay=vc4-kms-v3d-pi4”. (Edit: Probably won’t do anything useful, OSMC has the proper overlay files.)

If neither of these fixes is reliable or they have their own problems as well then it seems to me that a fix that could be done by OSMC in the next release is use an earlier RPi 4 firmware version without this problem.

retroresolution · 7 February 2022 13:55

Superbly detailed, thank you.

My system is connected to a 1080p monitor. I switched to an ancient 1080p TV, but the problem persisted.

Full reinstallations didn’t help.

When I have the time, patience, and clarity of mind (chemo-fog is an absolute nightmare), I shall try some of the settings and processes you’ve listed.

Thanks for this impressive post

PapaLazarou · 7 February 2022 23:06

Thanks!

After reading a bit more and trail and error, I finally put this at the end of /boot/cmdline.txt:

video=HDMI-A-1:1920x1080M@60

And this in /boot/config-user.txt:

[HDMI:0]
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16
hdmi_pixel_encoding=2
hdmi_drive=2

So now, when booting the Pi starts up in 1920x1080 (config-user.txt), the Linux kernel selects this same resolution (cmdline.txt), and Kodi also chooses this resolution for the GUI but will switch to 4K if it needs to when playing videos (Kodi settings). I rebooted several times while trying to fix a different problem with CEC and so far there hasn’t been any black screen.

As this is a problem booting the Pi with a 4K resolution, your problem might be down to something else, if it is maybe the things I checked could give you an idea of where to look and what you could change.

sodovkar · 15 August 2022 13:46

These changes helped me to fix the power issues!