-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDMI output stuck at 640x480 due to `hdmi_safe=1' #30
Comments
PR's are welcome |
So for my specific usecase I just added the overlay options to completely override the config.txt and instead of the If we want these SBC's to work just like any other PC I'm thinking this is what should be the default, and I could add a PR to that effect. However, adding these options when calling out to the factory for the image is fairly trivial. The current defaults are at least very likely to always work, even if the resolution is limited. And there might be other constellations like compute boards etc that might behave differently . Thus, my vote is actually on keeping this defensive default as is. For any late adventurers finding this in the future, what I did was just creating this overlay config:
Throwing it at the factory: |
Over here we are setting:
Which according to RPIconfig means:
Specifically this the
hdmi_mode=4
causes the resolution to be fixed at640x480
. Is this intentional if not could we change this to instead use the expanded options but drop thehdmi_ignore_edid
,hdmi_group
andhdmi_mode
to let the monitor an the pi figure this out on their own?The text was updated successfully, but these errors were encountered: