Raspberry Pi 4 no HDMI output after plymouth boot screen
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, raspberry-pi
- Domain
- embedded-iot, operating-systems
Research direction
Start with the reproduction steps using config.txt and the listed Raspberry Pi OS, firmware, and kernel versions. Compare HDMI output before and after the Plymouth boot screen, then check whether tvservice -e "DMT 27 HDMI" restores it. Done means the configured hdmi_group=2 and hdmi_mode=27 settings keep producing a signal after Plymouth without the manual tvservice command.
Written by the indexing model from the issue text.
Description
Describe the bug
When specifying hdmi_group=2 and hdmi_mode=27 the raspberry pi outputs a signal of the correct resolution during boot but stops to do so after showing the plymouth boot screen. Forcing an output using tvservice -e "DMT 27 HDMI" however fixes this.
To reproduce
- Burn a fresh image to an sd card
- Add the following to config.txt
hdmi_force_hotplug=1 hdmi_group=2 hdmi_mode=27 hdmi_drive=2 - Boot the raspberry pi
- (Optionally update and retry)
- Login via ssh and execute
tvservice -e "DMT 27 HDMI"
Expected behaviour
Raspberry Pi boots and outputs a signal.
Actual behaviour
Raspberry Pi boots, outputs a signal (of the correct resolution and refresh rate) until it shows the plymouth boot screen. After that no signal is output.
System
- Raspberry Pi Model: RPi4B
- Display: Beetronics 7TS4
- Which OS and version (
cat /etc/rpi-issue)?Raspberry Pi reference 2019-07-10 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 175dfb027ffabd4b8d5080097af0e51ed9a4a56c, stage4 - Which firmware version (
vcgencmd version)?Aug 15 2019 12:03:51 Copyright (c) 2012 Broadcom version 9f8431fb7839c7f00f52b81f5822ddab2b31d0db (clean) (release) (start) - Which kernel version (
uname -a)?Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux
Additional context
EDID data from the display:
edid.zip
- Dominant language
- No language data
- Stars
- 5.6k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/firmware
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2042 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/firmware#2040 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
raspberrypi/firmware#2039 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
raspberrypi/firmware#2038 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2037 · 4 comments ·
All issues in raspberrypi/firmware
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-iot-solution#786 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100