Raspberry Pi 5 overscan, CRT component video

Peeteris

Hello!
I'm fully aware that Retropie doesn't still support Raspberry Pi 5 at the moment, but I'm pretty exhausted trying to understand where should I look and what should I look for.

I got Raspberry Pi 5, 4GB model, solderet AV cable to it, connected to 4:3 CRT, installed Raspberry Pi OS 64-bit Desktop. On top of that installed Retropie with default packages.
Everything's cool except composite video output.

Apparently Raspberry Pi 5 (and 4) uses new video driver and it ignores everything related to overscan and tv mode settings that I usually put in configs file.

When I leave only this in config.txt

dtoverlay=vc4-kms-v3d,composite=1

the screen in retropie looks too small, there's too much overscan from all of the sides.

When I add this to cmdline.txt

video=Composite-1:720x480@60ie

the video is now a bit too large and cuts out. I tired to use margin codes like margin_left=32, but they didn't change a thing either.

For Raspberry Pi 3 I used these settings:

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

# uncomment for composite PAL
enable_tvout=1
sdtv_mode=1
sdtv_aspect=1

overscan_scale=1

And it looked perfect. But new Raspberry Pi 5 ignores everything. Even already included disable_overscan=1 code doesn't change a thing.

Also Emualtionstation and retroach runs at not so smooth 30 fps, even though desktop enviroment and kodi runs at 60 fps.
I can't quite understand what's going on.

I'm lost and don't know what to do. I just want to browse emulationstation at 480i@60 and play games at 240p@60 resolutions. Maybe anyone have suggestions or ideas?

Thank you very much!

windg

In Pi Os bookworm, overscan settings they have removed for now due to issues.

Peeteris

@windg Any information if it is planned to be fixed?
I gathered information and understand that every problem with all of this is because of the new video driver KMS that's going to be standart.

So, as far as I have gathered, Pi5 and Bookworm requires KMS driver and FKMS is not supported anymore.

KMS doesn't have a way to change between 480i Emulationstation and 240p in emulators, change overscan settings and all the nice options that FKMS had?

So, if you have a CRT TV, then Raspberry Pi 5 is a paperweight? 🫠

mitu

@Peeteris said in Raspberry Pi 5 overscan, CRT component video:

So, as far as I have gathered, Pi5 and Bookworm requires KMS driver and FKMS is not supported anymore.

Yes, althought the change happened for all Pi models since RaspiOS Bullseye - almost 3 2 years ago .

KMS doesn't have a way to change between 480i Emulationstation and 240p in emulators, change overscan settings and all the nice options that FKMS had?

Not even fkms had this reliably, like in the non-KMS scenarious where tvservice was working reliably.

So, if you have a CRT TV, then Raspberry Pi 5 is a paperweight? 🫠

No, but don't expect the same level of support as for digital HDMI. You should post your questions in the RPI forums, you'd get better answers there.

Peeteris

Hello!

I'm struggling with setting retropie retroarch resolution.
I left emulationstation on resolution 704x432, but I want retroarch to always start with resolution 720x240.
No matter how I try to save this resolution in retroarch.cfg, it doesn't load on start.

What should I do for retroarch to always start with resolution 720x240?
With tvservice I had onstart and onend codes, but I don't know and can't find what codes work for KMS.

mitu

What should I do for retroarch to always start with resolution 720x240?

Is this your current resolution ? You can't just pick an arbitrary resolution if it's not supported by the current video driver.

FWIW runcommand is responsible for switching/setting the resolution and will save it to /dev/shm/retroarch.cfg and then pass it on to RetroArch.

With tvservice I had onstart and onend codes, but I don't know and can't find what codes work for KMS.

There are none, there's no tvservice-like utility for KMS/DRM, each application has to implement video resolution

Peeteris

@mitu It's a supported resolution. I can change to it in retroarch settings. The problem is that there's no option (as fas as I can find) in Retropie to determine different resolutions for emulationstation and retroarch.

I'll try to make it more clear - i want emulationstation to use one supported resolution, and retroarch cores to use another. Automatic switching between resolutions on start and on end of games.

mitu

@Peeteris said in Raspberry Pi 5 overscan, CRT component video:

The problem is that there's no option (as fas as I can find) in Retropie to determine different resolutions for emulationstation and retroarch.

Not an option per-se, but the runcommand launch menu allows you to choose from one of the supported resolutions - so RetroArch can run in a different resolution than the (default) one used by EmulationStation. Have you tried doing that ?

Peeteris

@mitu for some reason there are no resolution options in runcommand options. Pi5 through composite supports 8 resolutions, which are also available in retroarch and other platforms like Recalbox.
Can I add those supported resolutions to runcommand manually, so I can choose them?

mitu

@Peeteris said in Raspberry Pi 5 overscan, CRT component video:

@mitu for some reason there are no resolution options in runcommand options. Pi5 through composite supports 8 resolutions, which are also available in retroarch and other platforms like Recalbox.

This means they're not detected by runcommand. I guess that's one of the things that needs looked over for PI5 support.

Peeteris

@mitu is there any solution for now? ☺️

mitu

@Peeteris said in Raspberry Pi 5 overscan, CRT component video:

@mitu is there any solution for now? ☺️

Try to manually add an override for the resolution from RetroArch's menu and save it, see if it gets applied and overrides the resolution set by runcommand.

Peeteris

@mitu Thank you! Core overrides did work. :)

mitu

@Peeteris Glad it works. There may be a solution for the overscan margins being ignored - see https://github.com/raspberrypi/linux/pull/5845 - so check again when a new kernel shows up during regular updates with apt.

Peeteris

@mitu thank you very, very much for the help and information about kernel. :)