Black borders with disable_overscan=1

sirvapesalot

Sorry, here is all other relevant info. Please let me know if you need anything else.

Pi Model or other hardware: 4
Power Supply used: CanaKit Raspberry Pi 4 Power Supply (USB-C)
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.6
Built From: Pre made SD Image on RetroPie website, Berryboot.
USB Devices connected: SSD in 3.0 slot and keyboard.
Controller used: Keyboard

I did change from Critical to beta and installed the latest beta to attempt to get boot to SSD going without SD card.

mitu

@sirvapesalot said in Black borders with disable_overscan=1:

Built From: Pre made SD Image on RetroPie website, Berryboot.

Probably that's the reason why the default RetroPie config options are not applied. Try un-commenting the ovescan_scale option and reboot.

sirvapesalot

@mitu

Same issues after using overscan_scale=1 in config.txt. Is it recommended not to use the berryboot?

mitu

It's recommended to install the RetroPie image directly, using Berryboot is not the preferred or supported option.

saccublenda

In my experience disable_overscan=1 does not disable overscan (so ignoring the overscan_xy settings), but instead disables a default overscan of 48 pixels on top, bottom, left and right. So my suggestion is to set disable_overscan=1 and adjust the overscan_left, overscan_right, overscan_top and overscan_bottom settings until the image fits your screen.

sirvapesalot

@saccublenda Hi, I may be confused as I downloaded the retropie 4.6 image and directly from the site and put that on the pi 4 for the install. I do have the set disable_overscan=1 and have adjusted the overscan_left, right, top and bottom to several different settings and rebooted with nothing changing. I am using an HDMI to micro HDMI cable with a new IPS LED monitor. I may mess with it a little longer and if same just start over.

saccublenda

@sirvapesalot Just to be clear: in your /boot/config.txt you have

disable_overscan=1
overscan_scale=1

and changing overscan_left, overscan_right, overscan_top and overscan_bottom has no effect?

sirvapesalot

@saccublenda

That's correct, here is a copy of my latest config.txt after a reboot.

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=-5
overscan_right=-5
overscan_top=-5
overscan_bottom=-5

uncomment to force a console size. By default it will be display's size minus

overscan.

#framebuffer_width=1920
#framebuffer_height=1080

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=2
hdmi_mode=58

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

Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

Uncomment this to enable infrared communication.

#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

Additional overlays and parameters are documented /boot/overlays/README

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

Do you think this has to do with updating bootloader to latest beta to try to test usb ssd 3.0 booting? Maybe I'll downgrade and give that a go.

saccublenda

The only substantial differences that I find with my config are the commented dtoverlay=vc4-fkms-v3d setting, and the hdmi_group=2 and hdmi_mode=58 lines that in my config are hdmi_group=1 and hdmi_mode=16.
Try to uncomment the dtoverlay line first, and if this does not work try to set hdmi_group=1 and hdmi_mode=16.

sirvapesalot

Same issue :( I do see a Welcome to GNU/Linux 10 (buster) or something similar when it boots. I'm not sure if that's related to the version you said may be causing the issue.

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=-5
overscan_right=-5
overscan_top=-5
overscan_bottom=-5

uncomment to force a console size. By default it will be display's size minus

overscan.

#framebuffer_width=1920
#framebuffer_height=1080

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=16

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

Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

Uncomment this to enable infrared communication.

#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

Additional overlays and parameters are documented /boot/overlays/README

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

saccublenda

@sirvapesalot I’m out of ideas. Before trying to reinstall the RetroPie image directly without using Berryboot, you may want to try on another monitor/tv.

sirvapesalot

@saccublenda

I tried editing the /boot/cmdline.txt to remove the pi text and just show retropie logo, but this also doesn't work.

I think maybe it's because I used Andreas Spiess guide on " Boot a Raspberry Pi4 with an SSD to make it reliable and fast". It has to be either that or using the beta bootloader.

saccublenda

Yeah, follow the official documentation and you will be good.

sirvapesalot

@saccublenda thanks for the help 👍

BuZz

If you're using berryboot, that has its own config.txt

Berryboot isn't supported btw, and we don't provide berryboot images for the rpi4. I wasn't sure if you meant above you installed the standard image to test after.