Have tried
video=DSI-1:720x1280M@60,rotate=270
As per your post.
Doesn’t change anything…
Ralf
Hey @rkorell,
Not sure what the issue could be.
Please share config.txt, volumioconfig.txt and userconfig.txt from /boot
Will try to reproduce over this weekend.
Kind Regards,
hI!
I have same setup and I only put this in my userconfig, nothing else. No other changes in other files.
[all]
display_auto_detect=1
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=270
Regards/ C
Dear @nerd ,
thanks.
userconfig already above but posted herein again.
volumio@korellmusik:~$ cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.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]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-dacplus-pro
volumio@korellmusik:~$ cat /boot/volumioconfig.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
# dtparam=uart0_console # Disabled by default
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
display_auto_detect=1
volumio@korellmusik:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
# Power-LED und Status LED vom Raspberry Pi abschalten
dtparam=pwr_led_trigger=default-on
dtparam=pwr_led_activelow=off
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off
dtparam=eth_led0=4
dtparam=eth_led1=4
[all]
display_auto_detect=1
#display 7Zoll
# raspi 4
#dtoverlay=vc4-kms-v3d-pi4,nohdmi
#dtoverlay=vc4-kms-dsi-ili9881-7inch
#Raspi 5:
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotate=90
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=1
display_hdmi_rotate=1
volumio@korellmusik:~$
Regards,
Ralf
Hey @rkorell,
Something worth investigation. On Raspberry Pi 5 there are two physical DSI connectors. Can you access and confirm, which one is coupled with the DSI ribbon?
Kind Regards,
DSI-port 1.
(I’ve even tried to use video=DSI-2:720x1280M@60,rotate=270 in cmdline.txt.)
Hi Back from holiday I have tested 0.62 and the hotspot still doesn’t work. I see that you have released 0.63 while I was away. I’ll try that tomorrow. Best Regards
Log file reference http://logs.volumio.org/volumio/9rNko56.html
v0.065 – Alpha Kernel Release
Pi Kernel: 6.12.27
x86 Kernel: 6.12.28
These are uncharted waters - anything may break here. This release updates core kernel components across platforms and may affect:
- DACs and HATs
- LAN and Wi-Fi adapters
- Screens and input devices (touch panels, GPIO triggers, etc.)
- Boot sequence and graphics stack
- USB and power management
What To Test
Please report anything broken or unexpectedly fixed. Your feedback helps us stabilize the platform.
Suggested test areas:
- Audio Devices: Check playback, control, and compatibility.
- Networking: LAN stability, Wi-Fi pairing, hotspot behavior.
- Displays: HDMI, DSI, SPI. Confirm boot splash, resolution, rotation.
- Touch Input: Capacitive and resistive screens, multi-touch, cursor alignment.
- GPIO HATs: Buttons, rotary encoders, relays, IR receivers.
- Power States: Reboot, shutdown.
If you’re unsure whether something is kernel-related, report it anyway. We’ll trace the cause.
No Plymouth or splash changes in this build - see v0.063 for boot calibration.
We are heading toward public BETA, and this phase is critical.
Test everything, post often, and log like your life depends on it - we know most of it’s noise, but we’re strangely addicted to it.
Kind Regards,
Update to V0.065 via OTA fine here with my simple setup:-
Pi 5
Waveshare PCIe To M.2 Adapter With PoE Function
USB into Cambridge Dacmagic 200m
Great work as always Nerd
Steve UK
Hey @Steve1,
Thanks for confirming the OTA to v0.065 went smoothly - and great to hear your Pi 5 setup with the Dacmagic 200M is running well.
Just a reminder though - this is still a team effort. Everyone testing and reporting back here is part of that team, and the progress we’re making on Bookworm is thanks to all of you.
Let’s keep the feedback flowing.
Kind Regards,
Hey @rkorell,
Please check tests results:
Hardware
- VolumioOS 0.063, 0.065
- Raspberry Pi 5 16GB
- Raspberry Touch Screen 2
- SanDisk Extreme Pro 256GB
CAM/DISP 0
/boot/userconfig.txt
[all]
dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0,rotation=90
CAM/DISP 1
/boot/userconfig.txt
[all]
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=90
Rotation
No other changes. Perhaps you could start with simple entries in userconfig.txt and add your custom parameters one at the time.
Kind Regards,
1 Like
Setup: Pi4B, Official 7" screen, Topping D10s USB DAC
Fresh install to v0.065 (I was on a much earlier alpha)
Hotspot & 1st login ok
Splash screen upside down (normal for first start)
Login to MyVolumio
Test Web Radio - OK
Enable plugin test mode
Install plugins: Spotify, Bandcamp, Touch Display - all OK and working
Started to install IR-Remote plugin then lost wifi connection. I can see Volumio using a network app, says the networking is ok, but I can’t connect to it via a browser (phone and laptop, tried clearing cache). No log possible.
Powered off and restarted - network app still sees Volumio, but my browsers won’t connect to it.
Hardware:
- Model: Raspberry Pi 4 Model B Rev 1.4 Raspberry Pi / 4B - 1.4 /
- Version: d03114 / 4B - 1.4
- SanDisk Corp. Ultra Fit 15GB
- 4.3inch Capacitive Touch Display for Raspberry Pi, DSI Interface, 800×480
- iFi Zen DAC V2
- KGuss DAC-K3
- Argon one V2 + (Fan/Powerbutton script)
Installation:
- Configured via iPhone connected to Hotspot
- Configured WiFi during intial setup
- Able to connect via browser and Volumio App on WiFi without reboot
Testing:
- Audio OK (Tested with Spotify)
- Touchscreen OK (capacitive)
- IR- Controller GPIO23 OK
- System Info OK
- Spotify OK
- Touch Display OK
- Network NAS mapping OK
- FusionDSP OK
- Powerbutton GPIO4 OK
1 Like
Hardware:
- Model: Raspberry Pi 5 Model B Rev 1.0
- Version: d04170
- SanDisk Corp. Ultra Fit 15GB
- 7inch Capacitive Touch Display for Raspberry Pi, MIPI DSI Port
- iFi Zen DAC V2
- KGuss DAC-K3
- HifiBerry DAC Plus
Installation:
- Configured via iPhone connected to Hotspot
- Configured WiFi during intial setup
- Able to connect via browser and Volumio App on WiFi without reboot
Testing:
- Audio OK (Tested with Spotify)
- Touchscreen OK (capacitive)
- IR- Controller GPIO23 OK
- System Info OK
- Spotify OK
- Touch Display OK
- Network NAS mapping OK
- FusionDSP OK
- Rotary Encoder GPIO17,27 (volume) OK
- MPD_OLED (SH1106) OK (needs a reboot on a first time install)
1 Like
RPi4, HDMI, no HAT
1.3840x2160 (userconfig empty - displays as 1920x1280??)
2.1920x1080 (userconfig with monitor data. If it is empty it does not fill the entire screen)
installed: touch, Peppymeter basic, now playing, info system
1 Like
Hey @SimonE,
Thanks for the detailed report - especially noting the point of failure around IR-Remote plugin install.
From what you describe, it’s very likely that the IR hardware ambiguity caused the plugin to misconfigure the GPIO stack or trigger a udev-level input device clash. That could disrupt system responsiveness and block the web UI, even if the device still answers on the network.
Could you clarify:
- Are you using an IR receiver via GPIO, or is this a USB-based IR device?
- Was the IR hardware already connected when you enabled the plugin?
It would help to rule out whether this is a plugin-side misdetection or a system-level regression.
If you can get in via SSH, grab logs with:
volumio livelog
Edited for benefit of the community…
dmesg > dmesg.txt
Attach dmesg.txt to your response or
cat dmesg.txt
Edited end…
journalctl -b -0 --no-pager | grep -Ei 'ir|lirc|gpio|udev'
This will extract relevant log lines from the current boot and may show if lircd or gpio-ir triggered something unexpected.
Also helpful:
lsmod | grep ir
And:
cat /proc/bus/input/devices
If no SSH is possible anymore, a fresh repro with logging enabled would be the fallback.
Let’s pin this down - IR plugins can be tricky if the hardware layer is unclear.
Kind Regards,
Hey @Gelo5,
Thanks for the details and photos. A few notes to clarify what you’re seeing:
- Our calibration background image is currently 800x800, and it’s primarily designed for embedded panels like KMS/DSI/SPI displays - not full-screen scaling over HDMI.
- On HDMI displays, especially high-res ones like 3840x2160, the UI may default to a fallback mode or misreport resolution if EDID is incomplete or if no resolution is forced via
userconfig.txt. - When
userconfig.txtis empty, the display service likely defers to a lower fallback resolution (e.g., 1920x1280) and fills what it can. Once you explicitly set a modeline or force a mode, the screen area behaves as expected.
We’re evaluating a responsive background layer for HDMI displays - especially with touchscreen plugins - but for now it’s expected behavior on high-res external screens.
Kind Regards,
It’s an IR receiver via GPIO pin 25. Yes the hardware was attached. I can’t SSH in. Weird that it’s pingable.
I’ll try a new flash and only install that plugin. I know how to create/send a log, but how do I enable logging?
Hey @SimonE,
Thanks for confirming it’s a GPIO-based IR receiver on pin 25 - that definitely helps. It’s very possible the IR plugin’s install process caused a conflict at boot, especially if the GPIO wasn’t properly exported or lircd failed to bind correctly.
Since you can’t SSH in right now, here’s how to enable it for next time:
Option 1: Before first boot
- After flashing the image to your microSD, mount the boot partition on your computer.
- Create an empty file named
ssh(no extension). - On first boot, SSH will be enabled automatically.
Option 2: From the UI (if accessible)
- Open
http://<volumio-ip>/dev - Set SSH: TRUE
Once you’ve done a fresh flash and enabled SSH, try reproducing the problem with just the IR plugin installed - and grab logs.
Let’s pin this down. If needed, we’ll trace it through lircd and device tree overlays.
Kind Regards,