Raspberry Pi 400 Auto throttling?!

Fragger

I have a strange problem while retro gaming on Batocera.

I use 1080p resolution during gaming, and after about one and a half hours of continuous gaming i get extreme lag.

Until i power off my raspberry pi and wait fifteen minutes, then restart

It can then last about another one and a half hours before the same happens again.

Is there a fix for this or is something wrong with my Raspberry Pi 400?

Thanks.

Atari

This is a known issue.

Unfortunately, the symptom is not that it is auto-throttling. The current causation is unknown and unreproducible by the devs. Add your info to the issue report if you wish, but there isn’t much to say honestly.

The best suggestion is to simply restart the device once every few hours.

Fragger

Atari

OK Thank you for your help!

Xanac_13

It’s not a power management thing is it? I disabled power management on mine in the hope that it gives better performance.

souziago

I thought it was just me. I’m having the same experience with RPI4 4GB.

I tried everything. I had to downgrade to a previous version. The problem is gone. I hope they can fix this.

Linkos

Yo también tengo ese retraso en Raspberry pi 4 y siento como que es un buffer de algo que se satura (desborda) porque también tengo desactivada el ahorro de energía. Ojalá salga pronto una actualización.

Xanac_13

Hmm, I haven’t experienced this. What are the routes to seeing this on the Pi? Does it have to be set to 1080p, as I always set mine to 720p to improve performance. How long before it materialises?

Tbh Batocera 34 is imho the best release yet for the Pi 4(00). Absolutely superb. Even N64, which is mind boggling. If it is doing this I’d like to know the parameters that trigger it. Thanks. :-)

Xanac_13

Apologies. I’ve now seen the open issue on GitHub and it’s related to upgrading rather than fresh install.

Xanac_13

Would really appreciate if someone could point me in the direction of how to reproduce this as I can’t seem to be able to. Does the Pi 4 have to be set to 1080p? Is it because I use a Pi 400?

I have mine set to 720p with a good overclock (2100Ghz CPU, 750 GPU). I’ve been following the GitHub thread for a while and can see many still reporting this issue on the beta for 35, but I can’t even reproduce it on 34. I’ve read the comments and followed their experiences but when I attempt them myself it doesn’t happen. I’ve had the Pi plugged in with two controllers attached, running a heavier Retroarch emulator (lr-flycast), played a bit then left for well over an hour but nothing. The only thing I haven’t done is change the Pi screen resolution to 1080p, but I will try this if it’s a central component of the issue.

Atari

Xanac_13 It does not occur if you use the fkms driver. That could be what you’re using.

Xanac_13

Hmm, don’t think I am but let me know.

config.txt

For more options and information see

# http://rpf.io/configtxt

# Some settings may impact device functionality. See link above for details

# sets the initial CEC name of the device

cec_osd_name=batocera

# uncomment will lead to “safe mode” settings being used to try to boot with maximum HDMI compatibility.

#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible

# and your display can output without overscan

# at 0, it causes flickering on hdmi output

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 the hdmi_group command which defines the HDMI output group to be either…

# 1 use CEA (Consumer Electronics Association, the standard typically used by TVs) or

# 2 use DMT (Display Monitor Timings, the standard typically used by monitors).

# This setting should be used in conjunction with hdmi_mode.

#hdmi_group=2

# uncomment to apply an appropriate CEA or DMT mode for your display

# see the web site below for valid options depending on the hdmi_group setting

# https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

#hdmi_mode=4

# uncomment to force a HDMI mode rather than DVI. This can make audio work in

# DMT (computer monitor) modes

#hdmi_drive=2

# uncomment will remove all other modes except the ones specified by hdmi_mode and hdmi_group from the internal list

# meaning they will not appear in any enumerated lists of modes.

# this option may help if a display seems to be ignoring the hdmi_mode and hdmi_group settings.

#hdmi_force_mode=1

# use this option to allow selection of 4k 60Hz refresh rates.

# note, this will increase power consumption and increase the temperature of the Raspberry Pi.

# it is not possible to output 4Kp60 on both micro HDMI ports simultaneously.

#hdmi_enable_4kp60=1

# forces the EDID content type to a specific value.

# the options are:

# 0 = EDID_ContentType_NODATA, content type none.

# 1 = EDID_ContentType_Graphics, content type graphics, ITC must be set to 1

# 2 = EDID_ContentType_Photo, content type photo

# 3 = EDID_ContentType_Cinema, content type cinema

# 4 = EDID_ContentType_Game, content type game

#edid_content_type=4

# if you plug your tv at the same time as your rpi and that the rpi switches from the hdmi or give a low resolution because tv had no enough time to initialize it

boot_delay=3

# uncomment to enable composite output via 4 pole TRRS (“headphone”) socket.

# note: slightly slows down the entire system on Pi 4 models.

#enable_tvout=1

# uncomment for composite mode.

# 0 Normal NTSC (defult)

# 1 Japanese version of NTSC – no pedestal

# 2 Normal PAL

# 3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

# 16 Progressive scan NTSC

# 18 Progressive scan PAL

#sdtv_mode=2

# uncomment to define the wide aspect ratio for composite video output above.

# 1 4:3 (default)

# 2 14:9

# 3 16:9

#sdtv_aspect=3

# uncomment if you have slow sound issues on composite output

#audio_pwm_mode=0

# uncomment to pretend that all audio formats are supported by the display

# allowing passthrough of DTS/AC3 even when this is not reported as supported.

#hdmi_force_edid_audio=1

# uncomment to pretend that all audio formats are unsupported by the display.

# this means ALSA will default to the analogue audio (headphone) jack.

# hdmi_ignore_edid_audio=1

# uncomment to avoid the firmware parsing the EDID of any HDMI attached display

# that way the Linux video mode system (KMS) will then parse the EDID itself and pick an appropriate mode.

#disable_fw_kms_setup=1

# uncomment for lirc-rpi

#dtoverlay=lirc-rpi

# uncomment if you don’t want the rainbow at startup

disable_splash=1

kernel=boot/linux

initramfs boot/initrd.gz

# enable UART (required for for retroflag)

# affect rpi performances

# enable_uart=1

# 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

# Configure GPU memory based on SDRAM size

# https://www.raspberrypi.org/documentation/configuration/config-txt/memory.md

# Default GPU memory split (do not change if you do not know what you are doing)

gpu_mem=128

# Configure GPU memory based on SDRAM size - overrides above setting

gpu_mem_256=112

gpu_mem_512=160

gpu_mem_1024=256

# Enable audio (loads snd_bcm2835)

dtparam=audio=on

# Optional ‘Fake’ KMS for displays that won’t work with ‘Full’ KMS

#dtoverlay=vc4-fkms-v3d

[DPI]

# Put any DPI required display code here

# i.e. Official 7″ DSI Raspberry Pi Touch Display for ‘Full’ KMS

#ignore_lcd=1

#dtoverlay=vc4-kms-dsi-7inch

[pi02]

# 64-bit mode

arm_64bit=1

start_file=start_x.elf

fixup_file=fixup_x.dat

# Enable DRM VC4 V3D driver on top of the dispmanx display stack

# Preferred ‘Full’ Kernel Mode Setting (KMS)

dtoverlay=vc4-kms-v3d,cma-128

[pi2]

start_file=start_x.elf

fixup_file=fixup_x.dat

# Enable DRM VC4 V3D driver on top of the dispmanx display stack

# Preferred ‘Full’ Kernel Mode Setting (KMS)

dtoverlay=vc4-kms-v3d

[pi3]

# 64-bit mode

arm_64bit=1

start_file=start_x.elf

fixup_file=fixup_x.dat

# Enable DRM VC4 V3D driver on top of the dispmanx display stack

# Preferred ‘Full’ Kernel Mode Setting (KMS)

dtoverlay=vc4-kms-v3d

[pi4]

# 64-bit mode

arm_64bit=1

# Run as fast as firmware / board allows

arm_boost=1

start_file=start4x.elf

fixup_file=fixup4x.dat

# Enable DRM VC4 V3D driver on top of the dispmanx display stack

# Preferred ‘Full’ Kernel Mode Setting (KMS)

dtoverlay=vc4-kms-v3d-pi4

# Ensure only one display output can be used on the Pi4 with batocera

max_framebuffers=1

# custom config

[all]

[Overclock]

over_voltage=6

arm_freq=2100

force_turbo=1

v3d_freq=750

v3d_freq_min=500

Atari

You’re using the

dtoverlay=vc4-kms-v3d-pi4

driver so it’s not fkms.

If the issue is solved by just reflashing then that’s a good sign at least, might just be a silly configuration thing.

billc

i also have the same problem with my ras pi 4. after about an hour or 2 it gets very slow. reboot and its ok for a while. I did a format of the disk and fresh install with ver 34, and i still have the problem.

Xanac_13

billc

I believe this has now been resolved for the upcoming v35.

billc

Xanac_13

awesome! looking forward to that. thanks.