Can't get retropie 4.1 to boot in 720p

G-Member

I'm sorry, i didn't mean to be rude ,i'm a bit frustrated not understanding everything what is mentioned in the read me first post....

Here's the copy/past from the config.txt and i did nothing to it yet......this is from a the original untouched image from the official page.

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

Grtz,

Ruben

Beretta9

What image are you running?
What Pi are you using?

G-Member

Retropie 4.1
Running on a RPI3

G-Member

Do i need to remove the # for this?

uncomment to force a console size. By default it will be display's size minus
overscan.
#framebuffer_width=1280
#framebuffer_height=720

I read this in another forum, uncomment = remove the # for changes take effect.

Could this be what i'm missing?

EDIT: guas not, after removing the # and rebooting still the same only filemanager gets cropped

Dochartaigh

I changed this last night on my Raspbery Pi Zero and it went to 720P mode. Change:

#hdmi_mode=1

to:

hdmi_mode=4

Save, then reboot.

There's a chart HERE which has the different HDMI_MODE's.

G-Member

Yes that did the trick!!
Thnx, now i got everything running beautifully ;)

RickyTan

@G-Member my screen still flashes on/off after making that change

Ashpool

@Dochartaigh Not as criticism, but as an advice: Whence providing a hdmi_mode, good practice is to also provide hdmi_group (especially if hdmi_force_hotplug is also set (so there's no need in switching on the display first, ie. good for headless starts for accessing the pi via ssh and if one may decide to switch the display on later)), as mode 4 for group 1 (CEA) is 720p 60Hz, but for group 2 (DMT) it would be 640x480 60Hz [And I know of at least one Samsung(?) TV that is offering both CEA and DMT Modes] [Edit: And maybe with a pi4 the hdmi port it is meant for].

YFZdude

@RickyTan
As this thread was approaching 6 years old before you replied, it is best to open a new thread and fill out the information requested in https://retropie.org.uk/forum/topic/3/read-this-first

Then you can get specific help for your issue.

EDIT: And the user to whom you replied also hasn't been online since they posted that comment.

Ashpool

@YFZdude Yikes - That one sliped my awareness....

@mitu I am not sure whether it was here or another forum, but I know that some fora warn the user whence replying to older topics. Is it possible to activate such a function here (please ignore if this forum actually is already warning the user about it) ?

BuZz

@Ashpool Yeah, the forum already warns when replying to an old topic.

mitu

@Ashpool said in Can't get retropie 4.1 to boot in 720p:

. Is it possible to activate such a function here (please ignore if this forum actually is already warning the user about it) ?

It is activated, but the warning was probably shown to @RickyTan, your reply was later.