Hi everyone,
I’m looking for guidance or confirmation around local HDMI display support in Volumio 4, specifically with non-standard / bar-type HDMI panels.
Background / context
This is part of a long-term, integrated build, not a bench test.
• Raspberry Pi 4
• Custom chassis with internal power supplies and DAC
• Historically ran Volumio 2.x with a different (non-Waveshare) local display, which worked reliably using Volumio’s older display driver
I’m now attempting to migrate the system forward to Volumio 4.x and a new display.
Current display under test
• Waveshare 8.8” HDMI IPS bar display
• Native resolution: 480×1920 (portrait)
• Connected via HDMI to the port closest to USB-C power
• Panel confirmed working on:
• Raspberry Pi OS
• macOS
• Windows
What works
• Display functions perfectly on Raspberry Pi OS
• Panel, cable, and power are all confirmed good
What does not work
• On Volumio 4.x, the display never lights:
• no backlight
• no flicker
• no partial image
What I’ve tested on Volumio 4
I’ve tried to rule out configuration issues thoroughly:
• Clean /boot/cmdline.txt (no video= or drm.edid_firmware= overrides)
• Firmware HDMI configuration via /boot/userconfig.txt
• Both KMS and FKMS (vc4-kms-v3d and vc4-fkms-v3d)
• Firmware EDID injection (hdmi_edid_file=1 using EDID extracted from Pi OS)
• Kernel EDID override (drm.edid_firmware)
• Standard DMT modes (e.g. 1280×480)
• Custom HDMI timings (1920×480 @ 60 Hz)
• Correct HDMI port targeting confirmed
Under FKMS, Volumio reports:
• /sys/class/drm/card1-HDMI-A-1 → connected
• modes reports FIXED_MODE 1920x480
• Firmware config confirms HDMI forcing and timings are applied
Despite this, the panel never lights on Volumio 4.
Observation
This feels less like an EDID or timing issue and more like a change in Volumio 4’s display initialization behavior compared to Volumio 2 — possibly that the framebuffer is never committed for non-standard HDMI panels, even when DRM reports a valid mode.
Question
Is local HDMI output for non-standard / portrait / bar-type displays still expected to work in Volumio 4?
• Is this a known limitation or regression?
• Is there an officially supported path for local displays beyond standard landscape monitors?
• Or should Volumio 4 be considered effectively headless except for conventional displays?
Happy to provide logs or test further if helpful — I mainly want to understand whether this is something I should keep pursuing or treat as unsupported going forward.
Hopefully, I am not posting this in the wrong spot, as I usually do!
Thanks,
John