I built my second volumio with a bit untypical 2.8" MIPI display, as a part of my desk console.
Everything is working fine except wrong orientation of Volumio startup logo, it is strange, because even startup log (visible for short time during startup) is shown in right orientation, only logo is rotated and it is a bit annoying.
I just got my 480x1920 DSI display installed and it’s doing the same thing. I know it’s not a big deal…but…
The reason the Volumio Plymouth boot splash does not rotate properly on DSI MIPI displays under Volumio (Buster-based) lies in how Plymouth handles rendering and framebuffer rotation in early boot stages.
config.txt (e.g., display_lcd_rotate=2) or kernel DRM overlays./dev/dri/card0 with hardware-accelerated modes.volumio-logo.png) – this is crude and hardcoded, but works if rotation is static.This is a known limitation of Plymouth on Debian Buster. While the DSI display is physically and electrically working fine, the Plymouth theme renderer does not rotate the splash even if other parts of the boot process appear in the correct orientation. This is due to the Plymouth version lacking rotation support for DRM backends on Buster.
If you’re building custom Volumio images, the only realistic workaround on Buster is to rotate the logo image file manually to match the expected orientation.
Kind Regards,
I tried, even by removing whole content of folder with files for original logo (/usr/share/plymouth/themes/volumio-player/sequence), then I put there my own logo (just rotated original logo) and modified script volumio-player.script by removing whole part for creating animation, instead I wrote as follow:
#------------------------------------------------- LOGO -------------------------------------------------
# Load the logo image (change 'volumio-logo.png' to your own logo image filename)
logo_image = Image("/usr/share/plymouth/themes/volumio-player/sequence/volumio-logo.png");
# Create a sprite for the logo
logo_sprite = Sprite();
# Center the logo on the screen (horizontally and vertically)
logo_sprite.SetX(Window.GetWidth() / 2 - logo_image.GetWidth() / 2);
logo_sprite.SetY(Window.GetHeight() / 2 - logo_image.GetHeight() / 2);
# Set the image for the sprite
logo_sprite.SetImage(logo_image);
Result? Still the same, animated logo. It has to be hardcoded deeper?
Hey @Jarek_P,
The reason your rotated logo changes aren’t taking effect is because the initial splash screen is rendered from volumio.initrd, not from the root filesystem (/usr/share/plymouth/themes/...). This initrd is loaded during early boot, before / is mounted, and contains a minimal Plymouth setup with embedded theme assets and scripts.
Even if you modify volumio-player.script or replace assets on the live system, those changes do not affect the splash shown during initrd execution.
/boot/volumio.initrdvolumio-player.script inside the embedded Plymouth themeNote: This must be redone after each kernel/initrd update.
build/common/initramfs-overlay/usr/share/plymouth/themes/volumio-player/This ensures your rotation fix is persistent across updates and is ideal for custom hardware setups using rotated MIPI or DSI displays.
Rotation via config.txt or kernel KMS settings is not honored by Plymouth during initrd, as it initializes its own DRM/fb session independently. Only direct modification of assets in the initrd can resolve this.
Note: This limitation is specific to the current Buster-based Volumio.
The Bookworm-based Volumio (internal alpha in progress, no public ETA) may include updated Plymouth and KMS handling that resolves this cleanly without needing manual patching. If you’re not distributing hardware, consider waiting for that release.
Kind Regards,
This must be redone after each kernel/initrd update.
And this is also a good reason to stop this discussion at this point. It might just be easier to get used to it, especially since the rotated logo only appears for 2–3 seconds.
A small, very humble request to the Volumio developers: it’s probably obvious that people use all sorts of displays, mounted in all sorts of orientations. Ideally, orientation settings should be applied consistently across the whole system.
And maybe consider allowing users to import their own logo? It could appear after the original one, or even alongside it, if the original logo is needed as a well-deserved credit to the creators of the system (which is understandable). But let’s also give proud users a chance to personalize their own copy.
Hi @nerd, we have the bookworm version now, is there a solution implemented?
Kind Regards
It (assuming you mean rotation of the splash screen) was fixed many versions of V4 ago.
Also see:
So why do I get the startup logo in portrait on my 1280 x 400 display?
Hey @arkimede,
If this is not too much to ask - details of your screen like model, manufacturer, or perhaps link to the tech-specs may hold some clues about required setup? In the entire community - you are the only person who holds the details of your setup.
Kind Regards,
volumioconfig.txt
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
dtparam=nvme
dtparam=pciex1_gen=2
[all]
arm_64bit=0
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
force_eeprom_read=0
userconfig.txt
disable_fw_kms_setup=1
arm_64bit=1
disable_overscan=1
display_autodetect=1
dtoverlay=vc4-kms-v3d
max_framebuffers=2
[cm5]
dtoverlay=dc2,dr_mode=host
display_lcd_rotate=3
display_hdmi_rotate=3
config.txt
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
dtoverlay=
dtoverlay=hifiberry-dacplus,slave
include volumioconfig.txt
include userconfig.txt
cmdline.txt
splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=serial0,115200 console=tty1 imgpart=UUID=7f0c0e47-027d-47ad-bd0c-5159b014252e imgfile=/volumio_current.sqsh bootpart=UUID=10D8-1DF5 datapart=UUID=307f8728-204c-4df1-9dcc-f9fb9dec6fbe uuidconfig=cmdline.txt pcie_aspm=off pci=pcie_bus_safe rootwait bootdelay=7 logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa= snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 loglevel=0 nodebug use_kmsg=no
Hey @arkimede,
I asked directly for your screen details - manufacturer, model, or a link to the tech-specs. You responded with configuration files only.
Without knowing what hardware you actually have, I cannot help. Configuration files tell me what you configured - not what display is connected, how it connects, or what parameters it actually requires.
Required information:
A 1280x400 resolution could be dozens of different displays with completely different configuration requirements. Guessing is not troubleshooting.
No screen details, no Pi details, no log - no help.
Kind Regards,
Totally makes sense - knowing your exact screen & interface (HDMI/DSI/SPI) really helps narrow down what rotation settings you should use, because each display type can behave very differently. Without that info it’s mostly guesswork. If you can share the display model + connection type + logs from volumio.local/dev, folks here can give way more specific advice.
Dear friends, thank you very much for your help, but I have the feeling you were making it too difficult. I dug around and found the new (?) volumio.adaptive script in the plymouth folder, a name that says it all… By the way, there are the instructions inside (which I followed), just add plymouth=270 to cmdline.txt and everything was fine.
Thanks again, happy listening.
I for one wont make that mistake again, friend.
Hey @arkimede,
Well, it does not matter really how you get to the finishing line. You must like the hard way.
Should you choose to read previously posted by @Wheaten link to the rotation research you will find this right away, without need to diving into the theme script itself:
Should you click further in the same shared link you would find this too:
Either “white on black” or “black on white”. I can not imagine to make these details easier to find than presented over a red carpet on a silver tray…
Well, like I wrote before, these will not produce full result with Waveshare 7.9", reasons of which have been explained in relevant guides. Sharing a link to these guides will not help since even now, no one but you knows which hardware you have.
Kind Regards,
Sorry, but I don’t understand. I think I’ve read all the posts in this thread, and there’s no mention of the cmdline parameter. It just says you can directly modify the bitmap or, as you said, wait for the release of bookworm, which should fix the problem. Bookworm is out, so I asked (and you very kindly answered) if we had a solution at this point. I don’t think I chose the difficult solution… I just looked in the script, saw what parameter to set, and set it… For me, this is the easiest solution 