Display garbled when running SDL2 OpenGL apps on Raspberry Pi5 using TTY
System information
System:
Host: raspberrypi Kernel: 6.1.0-rpi7-rpi-2712 arch: aarch64 bits: 64
compiler: gcc v: 12.2.0 Desktop: LXDE v: 0.10.1 wm: Openbox dm: LightDM
Distro: Debian GNU/Linux 12 (bookworm)
CPU:
Info: quad core model: N/A variant: cortex-a76 bits: 64 type: MCP
arch: ARMv8 rev: 1
Speed (MHz): avg: 2400 min/max: 1000/2400 cores: 1: 2400 2: 2400 3: 2400
4: 2400 bogomips: 432
Features: Use -f option to see features
Graphics:
Device-1: bcm2712-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A
chip-ID: brcm:107c701400
Device-2: bcm2712-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A
chip-ID: brcm:107c706400
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
compositor: xcompmgr driver: X: loaded: modesetting unloaded: fbdev dri: vc4
gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Gigabyte M27Q res: 1920x1080
dpi: 82 diag: 684mm (26.9")
API: OpenGL v: 3.1 Mesa 23.2.1-1~bpo12+rpt2 renderer: V3D 7.1
direct-render: Yes
Describe the issue
OpenGL apps seem to display garbage when running from the TTY. Tested 2 separate apps, but can easily be duplicated with Quake3e using the opengl1
renderer.
Both apps are using SDL2 in the kmsdrm
backend...SDL2 should default to it when your switched over to the TTY.
Regression
Not sure if it worked on the Pi5 previously, but it does work on the Pi4 w/o issues.