Hyperpixel 4.0 black screen after boot since 6.12.30 #6871
Comments
|
Raspberry Pi OS with the kernel from rpi-update (6.12.30 Fri May 23 13:29:06) has just booted fine with a Pi4 and HyperPixel4 (480x800) panel configured. Please check the kernel logs for any errors ( Please provide the full contents of config.txt too so we know how you've enabled the panel. |
|
Unfortunately I don't think I have kmsprint or kmstest and I couldn't find a package with them. |
|
Your logs all say that DPI has been enabled as normal. The only other thing I can think of would be pin muxing. Normally I'd say use |
|
The simplest pinctrl build is just: with an optional The whole thing takes about a minute. |
|
Okay I did compile that, but when I was messing around I actually got the screen to show when pressing ctrl+alt+f1. So what I'm guessing is that for some reason the kernel update makes my setup to start on the second tty which is just black, not cli or anything. But using ctrl+alt+f# here is very unreliable too, it seems to work maybe only when the system is in the lockscreen but also doesn't want to show other ttys before that one works. How can the kernel affect this? |
I don't think this is really relevant anymore but I was working on Arch, so there is no apt, but minor difference anyway. The uncommon setup with the hyperpixel is why I'm finding these weird issues. |
|
vc4 has bound to fb0 as normal I still want to know what DRM has been asked to render. If it is nothing, then it is doing the right thing and this isn't a kernel issue. |
|
It might not be a kernel issue but it is the only variable here. |
|
Debug avenues are limited as it is working fine with Raspberry Pi OS with 6.12.30 from rpi-6.12.y. Do you know the commit hash that your 6.12.30 kernel has been built from? I can try recreating that build, but that's really the end of the line as we don't officially support Arch or EndeavourOS. |
|
Should be 1ec873f archlinuxarm/PKGBUILDs@8ba59eb And it's fine, I appreciate taking a look at this. It's not as big deal as the previous issue. I wonder if any of those flags in the PKGBUILD cause it. There is some DRM stuff right? |
I've tried this on Raspberry Pi OS with kernel 6.12.30 from rpi-update and the screen boots blank (not even boot messages) on my cm5 with a hyperpixel 4.0 square screen. |
|
Here are the outputs: config.txtdmesgKMSXXkmsprintkmstestno output pinctrl
DRI state
|
|
I should perhaps say that for me kmsprint did show the display. And it is definitely detected by the system. I can get the picture to show after seemingly random toggling between ttys with ctrl+alt+f#, it shows at f1 obviously, but others don't show anything before it starts working. It doesn't seem to be strictly time based but just randomly at some point it will work but not by itself. |
|
I tried changing tty, but the display was never showing anything. The issue might be made worse by something else that's different on the rpi5 and rpi4. |
HyperPixel4 Square is a totally different panel driver Please raise a new issue if you have problems with it. |
|
What started to happen now suddenly is that the image is horizontally flipped, even in tty.(sometimes) How did this get so weird... And now it just booted properly without me changing anything as well as mpv hwaccel magically starting to work when it never did before. I don't know man... maybe I should just close this issue because it makes no sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While not the same as #6721 basically the same setup still.
Hyperpixel 4.0 display goes to black screen after boot.(boot text is seen) The display is detected by the OS and otherwise works including touch but no picture, backlight is still on. This happens on 6.12.30, I'm not sure about .29 but .28 works as normal and downgrading to it fixes the issue.
Steps to reproduce the behaviour
Device (s)
Raspberry Pi 400
System
Logs
No response
Additional context
Updated from 6.12.28(works) to 6.12.30(broken) so 6.12.29 status is unknown.
The text was updated successfully, but these errors were encountered: