Screen blanking turns off display

Open
#5,591 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

Reproduce the behavior with the provided xset commands on the Raspberry Pi 4 system described, and inspect dmesg while the display blanks. Compare the current Bullseye behavior with the reported Stretch behavior and the hdmi_blanking and disable_dpms settings in /boot/config.txt. Done means the display becomes blank without stopping its signal to the TV.

Written by the indexing model from the issue text.

Description

Describe the bug

On Stretch, I had my Pi configured to blank the display, but still send a display signal. I'm using a TV for a display and if it looses the display signal, it turns off completely and is a pain to get set back up again.

I just installed Bullseye and now, whenever the display is blanked, the display signal stops as well.

Steps to reproduce the behaviour
xset s blank
xset s 5
xset -dpms

Then wait 5 seconds.

I also tried adding:

hdmi_blanking=0
disable_dpms=1

to /boot/config.txt, but it doesn't help.

Device (s)

Raspberry Pi 4 Mod. B

System

pi@workout:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2023-05-03
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 7c750947a959fb626a70c09fd17c65815df192ac, stage4
pi@workout:~ $ vcgencmd version
Mar 17 2023 10:50:39
Copyright (c) 2012 Broadcom
version 82f3750a65fadae9a38077e3c2e217ad158c8d54 (clean) (release) (start)
pi@workout:~ $ uname -a
Linux workout 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

Logs

No output is sent to dmesg when the screen blanks.

Additional context

No response

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.