Raspberry-Pi-OS-64bit icon indicating copy to clipboard operation
Raspberry-Pi-OS-64bit copied to clipboard

Blank screen after boots to desktop

Open broken613 opened this issue 4 years ago • 16 comments

I lose video within 30 seconds of booting to the desktop. This is on a new install of Raspberry OS 64bit. This device was running with no issues on 32bit. The issue seems to come from the updates. If I don't tell the Pi to update software during setup then the issue is not present.

Steps to reproduce:

  1. Install RPi OS 64 bit on SD Card
  2. Power on device
  3. Setup device and choose to update software during setup
  4. Once the software is installed, the device will restart
  5. The device will boot to the desktop and then within 30seconds it will lose video
  6. I am unable to SSH into the device so it may have just crashed

Troubleshooting:

  1. Restarted but as soon as it boots to the desktop I lose video.
  2. Formatted SD card and reinstalled OS, issue persists
  3. Chose not to update software during setup, this resolved the issue.

I am not sure what's updating during the setup but something is causing the issue

broken613 avatar Oct 05 '21 22:10 broken613

Do you have a different display / monitor / TV that you can test with?

lurch avatar Oct 06 '21 12:10 lurch

Tested another display and there was no issue. As soon as I connected back to the original display the issue returned. Of course if I just don't update software during setup then it does work on the original display.

The original display is a 1080p monitor The test display was a 720p tv

Not sure what is being updated that breaks the video signal. This display works just fine with other devices and it was working fine when I was running RPi OS 32 bit.

broken613 avatar Oct 06 '21 21:10 broken613

I believe the graphics-system in RPi OS 64-bit is different to that in RPi OS 32-bit, so perhaps there's something "strange" about the EDID reported by your non-working display that's causing no signal to be output after updating RPi OS 64-bit ? Ping @6by9 and @popcornmix in case they can offer additional debugging advice.

lurch avatar Oct 06 '21 23:10 lurch

It's more likely to be a kms vs fkms issue than 32-bit vs 64-bit.

Just to confirm, @broken613, do you have dtoverlay=vc4-kms-v3d in config.txt? Does changing it to dtoverlay=vc4-fkms-v3d help?

popcornmix avatar Oct 07 '21 14:10 popcornmix

Changing "dtoverlay=vc4-kms-v3d" to "dtoverlay=vc4-fkms-v3d" resolved the issue.

broken613 avatar Oct 07 '21 19:10 broken613

I had the same issue with the official raspberry pi 7"-touch screen. Changing to dtoverlay=vc4-fkms-v3d helped.

btemperli avatar Oct 26 '21 16:10 btemperli

There have been some fixes for KMS, the Pi DSI display should now work reliably under KMS. The changes should be in apt.

JamesH65 avatar Oct 26 '21 18:10 JamesH65

And to use the 7" panel under KMS currently requires adding dtoverlay=vc4-kms-dsi-7inch in addition to dtoverlay=vc4-kms-v3d.

6by9 avatar Oct 26 '21 18:10 6by9

thank you @6by9 for the additional hint, I will give that a try!

btemperli avatar Oct 27 '21 04:10 btemperli

@6by9 Is that a fix only required for 64-bit Raspberry Pi OS, or does it apply to all KMS users? Is it something that ought to be added to https://www.raspberrypi.com/documentation/accessories/display.html and/or https://www.raspberrypi.com/documentation/computers/config_txt.html ?

lurch avatar Oct 27 '21 11:10 lurch

It applies to all KMS users currently. There is a firmware patch in the pipeline that can make it be automatically added, but it's not the current default. It's unrelated to the original issue though.

6by9 avatar Oct 27 '21 11:10 6by9

Tested another display and there was no issue. As soon as I connected back to the original display the issue returned. Of course if I just don't update software during setup then it does work on the original display.

The original display is a 1080p monitor The test display was a 720p tv

Not sure what is being updated that breaks the video signal. This display works just fine with other devices and it was working fine when I was running RPi OS 32 bit.

Its work, thank you my friend.

Mate0427 avatar Dec 09 '22 15:12 Mate0427

It's more likely to be a kms vs fkms issue than 32-bit vs 64-bit.

Just to confirm, @broken613, do you have dtoverlay=vc4-kms-v3d in config.txt? Does changing it to dtoverlay=vc4-fkms-v3d help?

This resolved my issue too. Raspberry PI 4, Raspbian OS September 2022 release

alkhachatryan avatar Apr 26 '23 16:04 alkhachatryan

Just wanted to chime in and say that adjusting dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d also fixed the issue for me trying to output to analog video on RPi OS 64-bit. It was the only way to get it to stop booting to a black screen after the rainbow splash. Thanks!

yllekz avatar Apr 28 '23 23:04 yllekz

@yllekz after an apt upgrade, can you switch back to kms driver? I think there is a kms kernel fix that is in apt, but not yet in the sdcard release your display may need.

popcornmix avatar Apr 30 '23 10:04 popcornmix

@yllekz after an apt upgrade, can you switch back to kms driver? I think there is a kms kernel fix that is in apt, but not yet in the sdcard release your display may need.

Sorry for the delay. I tried switching back to dtoverlay=vc4-kms-v3d after sudo apt update && sudo apt upgrade but it still doesn't work. The workaround is what works.

yllekz avatar Aug 24 '23 22:08 yllekz