Monitor Power Saving (DPMS) does not work as intended

Open
#4,484 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by comparing the linked Raspberry Pi 3 and Pi 4 Raspinfo logs, then reproduce the reboot, desktop idle, and xset dpms force suspend cases described in the report. Done means displays enter low-power mode and reliably wake after reboot, inactivity, or input on the affected hardware.

Written by the indexing model from the issue text.

Description

Is this the right place for my bug report?
This repository contains the Linux kernel used on the Raspberry Pi. If you believe that the issue you are seeing is kernel-related, this is the right place. If not, we have other repositories for the GPU firmware at github.com/raspberrypi/firmware and Raspberry Pi userland applications at github.com/raspberrypi/userland. If you have problems with the Raspbian distribution packages, report them in the github.com/RPi-Distro/repo. If you simply have a question, then the Raspberry Pi forums are the best place to ask it.

Describe the bug
DPMS Does not work as intended to turn Displays on or off.

To reproduce (Method A):

  • Power on raspberrry pi
  • wait for desktop to appear.
  • open terminal
  • run the command sudo reboot

Expected behavior (Method A):
To have video when the raspberry Pi finishes rebooting.

Actual behavior (Method A):
The Raspberry Pi 4 reboots, and the display goes into low power mode to never return without user interruption on the display.

To reproduce (Method B):
Change any setting requiring a reboot. Examples are any setting under the 'Display' tab of the 'Raspberry Pi configuration' utility.

Expected behavior (Method B):
To have video when the raspberry Pi finishes rebooting.

Actual behavior (Method A):
The Raspberry Pi 4 reboots, and the display goes into low power mode to never return without user interruption on the display. The Raspberry Pi 3 is not effected.

To reproduce (Method C):

  • power on Raspberry Pi
  • wait for Desktop to appear.
  • Leave the system alone at desktop for 15 to 30 minutes.
  • The Monitor should turn on low power mode.
  • Move mouse, and type on keyboard

Expected behavior (Method C):
For the Monitor to enter Low power mode and wake up.

Actual behavior (Method C):
The Monitor enters low power Mode on the Raspberry Pi 4, but does not wake back up. The Raspberry Pi 3 claims it is in low power mode, but the monitor does not turn off as intended.

To reproduce (Method D):

  • power on Raspberry Pi
  • wait for Desktop to appear.
  • Open up terminal.
  • run the command... xset dpms force suspend
  • wait about 5 to 15 minutes. The monitor should enter low power mode.
  • Move mouse, and type on keyboard

Expected behavior (Method D):
For the monitor to enter low power mode, and turn back on when your done.

Actual behavior (Method D):
The Monitor will enter low power mode on the Raspberry Pi 4, and fail to return. The Raspberry PI 3 claims to be in low power mode, but the monitor never enters low power mode.

System
Logs from Raspberry Pi 3:
https://gist.githubusercontent.com/kphillisjr/070c538659e616992b5952885a044f18/raw/9ac299f3f2116c35598819c211bf0d2d3512c633/Raspinfo.rpi3b.txt

Logs from Raspberry Pi 4:
https://gist.githubusercontent.com/kphillisjr/070c538659e616992b5952885a044f18/raw/9ac299f3f2116c35598819c211bf0d2d3512c633/Raspinfo.rpi4b.txt

Note: While not exactly related to this bug, I should probably mention that the Raspberry Pi 4 fails to show any splash screens before showing the desktop.

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.