Hey @changheelee,
Thank you for the detailed report and log file. Iâve found a bit of free time, analyzed your issue and can provide technical explanation for both problems youâre experiencing.
Second OLED Display Issue (OLED2)
The second display connects via SPI protocol using GPIO10 (DATA), GPIO11 (CLK), GPIO24 (RESET), and GPIO27 (DC). According to the hardware datasheet, this display requires the Volumio distribution to drive it using Python with the LUMA library.
Your report shows the Audiophonics Evo Sabre plugin (version 2.0.1) is installed and the hardware is detected correctly (Audiophonics I-Sabre ES9028Q2M in audio configuration).
In my customized EVO-SABRE kit I have tested the same plugin on both CM5 and Pi5 with Volumio 4.062, where both OLED displays work correctly across all storage types (MicroSD, NVMe, USB boot). I will re-test with a Raspberry Pi 4B once I have time to swap the board in my kit to confirm whether this is Pi4B-specific.
My System Information
System Information
OS info
Version of Volumio: 4.062
Hostname: pi5aud
Kernel: 6.12.47-v8+
Governor: conservative
Uptime: 0 days, 0 Hrs, 18 Minutes, 35 Seconds
Network info
Interface: eth0
IP Address: 192.168.30.205
MAC Address: 2c:cf:67:d8:a7:ba
Type: wired
Speed: 1Gb/s
Audio info
Hw audio configured: Audiophonics I-Sabre ES9028Q2M
Mixer type: Hardware
Number of channels:
Supported sample rate:
Board info
Manufacturer:
Model: Raspberry Pi Compute Module 5 Lite Rev 1.0
Version: d041a0
Firmware Version: 2025/05/08 15:13:17 Copyright (c) 2012 Broadcom
CPU info
Brand: BCM2712
Speed: 1.5 GHz
Family: Cortex-A76
Model: 1
Number of cores: 4
Physical cores: 4
Average load: 28%
Temperature: 58°C
Memory info
Memory: 8146996 Ko
Free: 7080600 Ko
Used: 1066396 Ko
Software info
Mpd version: Music Player Daemon 0.24.6 (b6f106b+)
Storage info
INTERNAL storage - Size: 475238Mo
Used: 237Mo
Available for storage: 450789Mo (95%)
Power Management Issue - Critical Understanding
This is where the hardware architecture becomes very important. According to the EVO Sabre datasheet:
- The Raspberry Pi is powered BY the EVO module via the GPIO connector
- The Pi does NOT control the DAC power state
- Power flows one direction: EVO module pcb powers the Pi via 40-pin header power pins
When you press the hardware power button or use the IR remote On/Off function, the datasheet explicitly warns: âthe power shut will be immediate and may interrupt any operations in progress.â
What happens during your reboot sequence:
The UI Reboot function reboots the Raspberry Pi only - it does NOT perform a power cycle of the entire kit. The EVO module remains powered throughout the Pi reboot process.
- You click Reboot in Volumio UI
- Pi begins reboot sequence
- EVO module continues supplying power via GPIO
- Pi only restart while EVO module stays active
Your reported behavior:
You mentioned that after attempting UI Reboot, the system would not boot again - even after a cold boot (hardware power cycle). This suggests the Pi4B may be getting into an undefined state during the reboot process that persists even after power cycling.
Correct shutdown procedure:
The datasheet states: âPrefer a software power off on the application to shut down your Pi properly before using this function.â
For full power cycle of the kit:
- Use âShutdownâ from Volumio UI
- Wait for Pi to complete full shutdown (monitor via SSH or system activity LED)
- THEN use hardware power button to cut power to the entire kit
- Wait 10 seconds
- Press power button to restart
Recommendations:
-
For the OLED2 issue: I will test with Pi4B to confirm if this is board-specific behavior and report back. @olivier_audiophonics may need to investigate further based on those results.
-
For the reboot issue: Can you test whether UI Shutdown followed by hardware power cycle works reliably? This will help determine if the problem is specific to the Pi reboot sequence or a broader power management issue.
-
If you need to restart: SSH access allows you to monitor shutdown completion before power cycling.
Question for you:
When the system failed to boot after your reboot attempts - did you try multiple cold boot cycles, or did it fail to boot on the first power cycle after the failed reboot?
Kind Regards,