Lastest build runs at 1080p?
-
This is just a question for anyone here that knows. For my curiosity. I’m running a pi4 and I remember that retro pie used to work like one hdmi port would just display nothing after the boot scroll, and the other would run the highest resolution your tv/monitor would support unless changed. Now the one port does the highest resolution and the other does 1080p.
My question is what configuration is being used to force 1080p as raspiconfig does not allow a change anymore? As I said. Just curious. -
-
Post your
/boot/config.txt
file. -
@mitu I haven’t touched it. It’s brand new build. So whatever the default is that comes in the image.
The only thing that uncommented is this# Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d #overscan_scale=1 hdmi_enable_4kp60=1 enable_uart=1
Just curious what was forcing 1080p. Which is good cause 4K is terrible in performance and my tv only wants to do 30hz with the pi in 4k
-
@lostless said in Lastest bulid runs at 1080p?:
hdmi_enable_4kp60=1
enable_uart = 1Try disabling the options above.
-
@mitu I did a small test. well I’m all confused. I swear you couldn’t change resolution in the raspi config anymore. Guess from the time I used the Kms driver from my last build. Well I went there and it allowed me to set a resolution and set the config.txt. Rebooted, but here’s the kicker. The hdmi port I was on, that booted to 1080p, now booted to a black screen acting as a second screen. And when I switched hdmi ports, to the one that ran at 4K 30hz, it was now displaying at 1080p. Still wondering why I was getting 1080p on the other port before. Guess at this point it doesn’t matter.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.