rk3576: Fix black screen on first boot#3016
Open
felixjones wants to merge 1 commit into
Open
Conversation
felixjones
force-pushed
the
fejones/rk3576/blackscreen
branch
from
July 11, 2026 17:10
24e760a to
b6f8d14
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
I noticed recently that whenever I flashed a new image the first boot (after all the setup boots) would halt on a black screen, requiring a press of the reset button.
After a whole bunch of logging, it looks like on that first boot the GPU powers down after a failed graphics driver startup, and when the second attempt to starts it's like "huh no GPU anymore" and black screens
I set
regulator-always-on;in the dts just to test the theory, and that fixed the problem.I fully admit, I don't know the consequences of
regulator-always-on;, I assume we generally want to use the GPU for 100% of the device's operation so my assumption is that we wantregulator-always-on;and it makes little sense to not have it always on, but again this is a case of "this seems to fix the problem"Testing
Tested with and without the patch multiple fresh image-installs, and it's a 100% repro and 100% fix rate
Additional Context
This issue does seem to be a regression on the
nextbranch, for some reason it's only recently started happeningI have not performed a bisect to figure out the regressing commit
AI Usage
NO