Public Beta Test: Audio Without Compromise - Refining the Future of Volumio on Bookworm

Volumio Development Volumio Beta Testing
, ,
550

Hello @nerd !

Is there much left to do, test and program before we can have a release candidate up and running? I think many of us users are really looking forward to it. Thank you very much for your work!

kind regards / C

551

Hey @ClaesM,

Good question. Right now the biggest blocker is the metadata update race condition that causes issues in multiroom, UPnP and queue handling. This needs to be fully understood and fixed before we can declare a release.

Apart from that, the heavy lifting is done. The Bookworm backend, kernel, drivers, and plugins are largely stable, with remaining work focused on polish, regression checks, and edge-case handling. Once the race condition is resolved and regression-tested across platforms, we can move towards a release.

However @volumio has the final say.

Kind Regards,

1 Like
552

Hey @Shlee,

Thanks for the clear report. The reason that no one has replied to your questions yet: to triage this properly I need a few concrete details:

  • One fresh log link captured right after the crash: open http://<volumio_ip>/dev then copy-paste the generated URL here.
  • Hardware and setup: storage type (microSD or SSD), power supply model, whether the Official Touch Display 2 is on DSI or HDMI, and its rotation or custom resolution if set.
  • Plugin state: was the Touch Display plugin enabled when the crash happened, or does it also crash with the plugin disabled after a reboot.
  • Browser UI check: when using a phone or PC browser, does album art render correctly and stay stable while playback continues.
  • Repro steps: from cold boot to crash, what exact sequence produces it and about how long until chromium dies.
  • Any third party plugins enabled, even if unrelated, and whether the issue persists with all plugins disabled except the core ones.
  • If you changed anything under /boot/userconfig.txt or display settings in the Volumio UI, list those edits.

Once we have the log URL and the above, we can pinpoint whether this is chromium kiosk state, GPU memory, or a UI asset load timing issue.

Kind Regards,

553

Blockquote Right now the biggest blocker is the metadata update race condition that causes issues in multiroom, UPnP and queue handling. This needs to be fully understood and fixed before we can declare a release.

Ok, I understand. Then I just can hope that everobody involved in Volumio development @volumio will work hard to solve and fix this.

Regards / C

555

Hey @Edrian_Lois_Villanue

VolumioOS ver. Debian base
v2.xxx Jessie
v3.xxx Buster
v4.xxx Bookworm
v5.xxx (TBD) Trixie (prototyping phase)

Kind Regards,

1 Like
556

I can’t make my new Waveshare 11.9 DSI touch display work with 4.022 in my RPi 4 rev 1.5 with 2 GB. It works with last 3.832, it works with Raspberry OS, and it works with RPi5 and 4.022 without problems, but I haven’t been able to see absolutely nothing with RPi 4 and 4.022. Not even backlighting. Tested everything I found in the forum, but without any success.

Device: Raspberry Pi 4B Rev. 1.5 2GB
Storage: MicroSD (eMMC 32GB)
Volumio version: 4.022
Log link: http://logs.volumio.org/volumio/w5jUcKi.html
Problem: Waveshare 11.9 Touch Display not working. It works on 3.832, it works wit Raspberry OS and it works with 4.022 and RPi 5, but not with RPi 4 and 4.022

Display device: https://www.waveshare.com/wiki/11.9inch_DSI_LCD

I don’t know what else I can provide. I’ve seen the Xorg.0.log and both the HDMI and the DSI displays appear as connected (nothing is connected to any HDMI), so I disabled HDMI in userconfig.txt and the log changed to:


[    38.956] (II) modeset(0): Output DSI-1 using monitor section DSI-1
[    38.956] (**) modeset(0): Option "Rotate" "normal"
[    38.986] (II) modeset(0): EDID for output DSI-1
[    38.989] (II) modeset(0): Printing probed modes for output DSI-1
[    38.989] (II) modeset(0): Modeline "320x1480"x60.2   50.00  320 380 440 500  1480 1540 1600 1660 (100.0 kHz eP)
[    38.989] (II) modeset(0): Output DSI-1 connected
[    38.989] (II) modeset(0): Using exact sizes for initial modes
[    38.989] (II) modeset(0): Output DSI-1 using initial mode 320x1480 +0+0
[    38.989] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    38.989] (==) modeset(0): DPI set to (96, 96)

But still nothing in the display.

Thanks for this great piece of software. Best regards.

Edit. Another Waveshare DSI display (7inchC) works perfectly with the same RPi4 and 4.022

557

Hey @aluisperezh,

Your log shows repeated touchscreen I2C errors from the Waveshare driver:
ws_touchscreen 10-0045: I2C write failed: -5.
That points to a touch connectivity or power issue on I2C bus 10 at address 0x45, not to KMS mode setting itself.
Config looks correct for this panel on Pi 4:
dtoverlay=vc4-kms-dsi-waveshare-panel,11_9_inch plus vc4-kms-v3d,nohdmi is present.

Please collect the following exactly, on the failing Pi 4 + 4.022:

  1. Targeted dmesg slice

    sudo dmesg -T | grep -i -e ws\_touchscreen -e dsi -e panel -e drm -e backlight

  2. I2C bus 10 probe for the touch IC

    sudo i2cdetect -y 10
sudo i2cdump -y 10 0x45 b 2>/dev/null | head -n 32

  3. DRM and backlight state

    ls -l /sys/class/drm
cat /sys/class/drm/card0-DSI-1/status
for f in /sys/class/backlight/\*; do echo \$f; cat \$f/brightness; cat \$f/max\_brightness; cat \$f/bl\_power 2>/dev/null; done

  4. Xorg modes detection

    sed -n "1,260p" /var/log/Xorg.0.log

  5. Physical hookup confirmation

  • Confirm ribbon orientation and connector used on the Pi 4. The touch FPC for this Waveshare must be fully seated and the correct DSI port used. Any photo is helpful.

Rationale for asking this:

  • The -5 I2C writes usually indicate NACK or no device on that address, which aligns with a loose touch FPC, wrong connector, or missing panel 3.3 V to the touch controller. We need to see whether 0x45 appears on bus 10 and whether the DSI-1 connector is lit and exposed a backlight sysfs node.

Post these and we will continue.

Kind Regards,

558

Hi @nerd, thank you for answering my question that already deleted.
However, I’d just want to try this bookworm which you’d said before on my previous concern regarding with lcd display issue.
My question is which bookworm version should i tried first? Should i try now the latest bookworm? Does bookworm also supported nvme boot ( install to disk).?

Thank you and regards,

559

Thanks for answering. Here are the results of your commands:
1 Targeted dmesg slice:

[Sat Sep 20 10:03:00 2025] /soc/cprman@7e101000: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:00 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 10:03:00 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/cprman@7e101000
[Sat Sep 20 10:03:00 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:00 2025] /soc/cprman@7e101000: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:00 2025] /soc/cprman@7e101000: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:00 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 10:03:00 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/cprman@7e101000
[Sat Sep 20 10:03:00 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:02 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 10:03:02 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 10:03:02 2025] v3d fec00000.v3d: [drm] Transparent Hugepage support is recommended for optimal performance on this platform!
[Sat Sep 20 10:03:02 2025] [drm] Initialized v3d 1.0.0 for fec00000.v3d on minor 0
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:03 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:03 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:03 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:12 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:12 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:12 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:13 2025] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[Sat Sep 20 10:03:13 2025] systemd[1]: modprobe@drm.service: Deactivated successfully.
[Sat Sep 20 10:03:13 2025] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fe700000.dsi (ops vc4_dsi_ops [vc4])
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
[Sat Sep 20 10:03:14 2025] [drm] Initialized vc4 0.0.0 for gpu on minor 1
[Sat Sep 20 10:03:14 2025] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:14 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:16 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:16 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:39 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 10:03:39 2025] ws_touchscreen 10-0045: I2C write failed: -5
  1. I2C bus 10 probe for the touch IC
  • sudo i2cdetect -y 10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
  • sudo i2cdump -y 10 0x45 b 2>/dev/null | head -n 32
No results displayed!

If I disable error redirection to null (i.e. “sudo i2cdump -y 10 0x45 b | head -n 32”) the result is:

Error: Could not set address to 0x45: Device or resource busy
  1. DRM and backlight state
  • ls -l /sys/class/drm
total 0
lrwxrwxrwx 1 root root    0 Jan  1  1970 card0 -> ../../devices/platform/v3dbus/fec00000.v3d/drm/card0
lrwxrwxrwx 1 root root    0 Sep 20 11:41 card1 -> ../../devices/platform/gpu/drm/card1
lrwxrwxrwx 1 root root    0 Sep 20 10:10 card1-DSI-1 -> ../../devices/platform/gpu/drm/card1/card1-DSI-1
lrwxrwxrwx 1 root root    0 Sep 20 10:10 card1-Writeback-1 -> ../../devices/platform/gpu/drm/card1/card1-Writeback-1
lrwxrwxrwx 1 root root    0 Jan  1  1970 renderD128 -> ../../devices/platform/v3dbus/fec00000.v3d/drm/renderD128
-r--r--r-- 1 root root 4096 Sep 20 11:42 version
  • cat /sys/class/drm/card0-DSI-1/status
cat: /sys/class/drm/card0-DSI-1/status: No such file or directory
  • cat /sys/class/drm/card1-DSI-1/status
connected
  • for f in /sys/class/backlight/*; do echo $f; cat $f/brightness; cat $f/max_brightness; cat $f/bl_power 2>/dev/null; done

This command fails, don’t understand why. “ls -l /sys/class/backlight” gives this:

lrwxrwxrwx 1 root root 0 Sep 20 10:10 10-0045 -> ../../devices/platform/soc/fe205000.i2c/i2c-22/i2c-10/10-0045/backlight/10-0045

If I “cd” there, I have this:

total 0
-r--r--r-- 1 root root  4096 Sep 20 11:47 actual_brightness
-rw-rw-rw- 1 root root  4096 Sep 20 10:10 bl_power
-rw-rw-rw- 1 root video 4096 Sep 20 11:41 brightness
lrwxrwxrwx 1 root root     0 Sep 20 11:47 device -> ../../../10-0045
-r--r--r-- 1 root root  4096 Sep 20 11:47 display_name
-r--r--r-- 1 root root  4096 Sep 20 10:10 max_brightness
drwxr-xr-x 2 root root     0 Sep 20 11:45 power
-r--r--r-- 1 root root  4096 Sep 20 11:47 scale
lrwxrwxrwx 1 root root     0 Sep 20 10:10 subsystem -> ../../../../../../../../../class/backlight
-r--r--r-- 1 root root  4096 Sep 20 10:10 type
-rw-r--r-- 1 root root  4096 Sep 20 10:10 uevent

And the requested values are:

brigthness -> 255
max_brightness -> 255
bl_power -> 4
  • Xorg modes detection
[    40.300]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[    40.300] Current Operating System: Linux volumio.casa 6.12.34-v7l+ #1889 SMP Mon Jun 23 11:08:21 BST 2025 armv7l
[    40.300] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:640x480M@60D numa=fake=1 system_heap.max_order=0 smsc95xx.macaddr=E4:5F:01:EB:43:1E vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  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=ttyS0,115200 console=tty1 imgpart=UUID=cc40bcae-8e5b-4465-a1d2-022efc5b5ed0 imgfile=/volumio_current.sqsh bootpart=UUID=CB70-A442 datapart=UUID=c824eb1e-6c2b-4cc1-a030-f182645bbe25 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
[    40.300] xorg-server 2:21.1.7-3+rpt3+deb12u10 (https://www.debian.org/support)
[    40.300] Current version of pixman: 0.44.0
[    40.300]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    40.300] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    40.300] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 20 11:41:31 2025
[    40.315] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    40.315] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    40.328] (==) No Layout section.  Using the first Screen section.
[    40.328] (==) No screen section available. Using defaults.
[    40.329] (**) |-->Screen "Default Screen Section" (0)
[    40.329] (**) |   |-->Monitor "<default monitor>"
[    40.329] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    40.329] (**) Option "Debug" "dmabuf_capable"
[    40.329] (==) Automatically adding devices
[    40.329] (==) Automatically enabling devices
[    40.329] (==) Automatically adding GPU devices
[    40.329] (==) Automatically binding GPU devices
[    40.333] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    40.335] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    40.335]    Entry deleted from font path.
[    40.338] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[    40.338] (==) ModulePath set to "/usr/lib/xorg/modules"
[    40.338] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    40.338] (II) Loader magic: 0x215080
[    40.338] (II) Module ABI versions:
[    40.338]    X.Org ANSI C Emulation: 0.4
[    40.338]    X.Org Video Driver: 25.2
[    40.338]    X.Org XInput driver : 24.4
[    40.338]    X.Org Server Extension : 10.0
[    40.343] (--) using VT number 2

[    40.343] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    40.351] (II) xfree86: Adding drm device (/dev/dri/card1)
[    40.351] (II) Platform probe for /sys/devices/platform/gpu/drm/card1
[    40.375] (II) xfree86: Adding drm device (/dev/dri/card0)
[    40.375] (II) Platform probe for /sys/devices/platform/v3dbus/fec00000.v3d/drm/card0
[    40.375] (**) OutputClass "vc4" setting /dev/dri/card1 as PrimaryGPU
[    40.376] (II) LoadModule: "glx"
[    40.383] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    40.451] (II) Module glx: vendor="X.Org Foundation"
[    40.451]    compiled for 1.21.1.7, module version = 1.0.0
[    40.451]    ABI class: X.Org Server Extension, version 10.0
[    40.451] (II) Applying OutputClass "vc4" to /dev/dri/card1
[    40.451]    loading driver: modesetting
[    40.451] (II) Applying OutputClass "vc4" to /dev/dri/card1
[    40.451]    loading driver: modesetting
[    40.451] (==) Matched modesetting as autoconfigured driver 0
[    40.451] (==) Matched fbdev as autoconfigured driver 1
[    40.451] (==) Assigned the driver to the xf86ConfigLayout
[    40.451] (II) LoadModule: "modesetting"
[    40.452] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    40.792] (II) Module modesetting: vendor="X.Org Foundation"
[    40.792]    compiled for 1.21.1.7, module version = 1.21.1
[    40.792]    Module class: X.Org Video Driver
[    40.792]    ABI class: X.Org Video Driver, version 25.2
[    40.792] (II) LoadModule: "fbdev"
[    40.793] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    40.810] (II) Module fbdev: vendor="X.Org Foundation"
[    40.810]    compiled for 1.21.1.3, module version = 0.5.0
[    40.810]    Module class: X.Org Video Driver
[    40.810]    ABI class: X.Org Video Driver, version 25.2
[    40.810] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    40.810] (II) FBDEV: driver for framebuffer: fbdev
[    40.839] (II) modeset(0): using drv /dev/dri/card1
[    40.839] (WW) Falling back to old probe method for fbdev
[    40.839] (II) Loading sub module "fbdevhw"
[    40.839] (II) LoadModule: "fbdevhw"
[    40.839] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    40.840] (II) Module fbdevhw: vendor="X.Org Foundation"
[    40.840]    compiled for 1.21.1.7, module version = 0.0.2
[    40.840]    ABI class: X.Org Video Driver, version 25.2
[    40.841] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    40.841] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    40.841] (II) Applying OutputClass "vc4" options to /dev/dri/card1
[    40.841] (II) Applying OutputClass "vc4" options to /dev/dri/card1
[    40.841] (==) modeset(0): RGB weight 888
[    40.841] (==) modeset(0): Default visual is TrueColor
[    40.841] (II) Loading sub module "glamoregl"
[    40.841] (II) LoadModule: "glamoregl"
[    40.841] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    40.905] (II) Module glamoregl: vendor="X.Org Foundation"
[    40.905]    compiled for 1.21.1.7, module version = 1.0.1
[    40.905]    ABI class: X.Org ANSI C Emulation, version 0.4
[    41.221] (II) modeset(0): glamor X acceleration enabled on V3D 4.2.14.0
[    41.221] (II) modeset(0): glamor initialized
[    41.221] (==) modeset(0): VariableRefresh: disabled
[    41.221] (==) modeset(0): AsyncFlipSecondaries: disabled
[    41.222] (II) modeset(0): Output DSI-1 using monitor section DSI-1
[    41.222] (**) modeset(0): Option "Rotate" "normal"
[    41.295] (II) modeset(0): EDID for output DSI-1
[    41.298] (II) modeset(0): Printing probed modes for output DSI-1
[    41.298] (II) modeset(0): Modeline "320x1480"x60.2   50.00  320 380 440 500  1480 1540 1600 1660 (100.0 kHz eP)
[    41.298] (II) modeset(0): Output DSI-1 connected
[    41.298] (II) modeset(0): Using exact sizes for initial modes
[    41.298] (II) modeset(0): Output DSI-1 using initial mode 320x1480 +0+0
[    41.298] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    41.298] (==) modeset(0): DPI set to (96, 96)
[    41.298] (II) Loading sub module "fb"
[    41.298] (II) LoadModule: "fb"
[    41.298] (II) Module "fb" already built-in
[    41.298] (II) UnloadModule: "fbdev"
[    41.298] (II) Unloading fbdev
[    41.298] (II) UnloadSubModule: "fbdevhw"
[    41.298] (II) Unloading fbdevhw
[    41.794] (==) modeset(0): Backing store enabled
[    41.794] (==) modeset(0): Silken mouse enabled
[    41.818] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    41.819] (==) modeset(0): DPMS enabled
[    41.819] (WW) modeset(0): Option "PrimaryGPU" is not used
[    41.819] (II) modeset(0): [DRI2] Setup complete
[    41.819] (II) modeset(0): [DRI2]   DRI driver: vc4
[    41.819] (II) modeset(0): [DRI2]   VDPAU driver: vc4
[    41.819] (II) Initializing extension Generic Event Extension
[    41.819] (II) Initializing extension SHAPE
[    41.820] (II) Initializing extension MIT-SHM
[    41.820] (II) Initializing extension XInputExtension
[    41.825] (II) Initializing extension XTEST
[    41.825] (II) Initializing extension BIG-REQUESTS
[    41.826] (II) Initializing extension SYNC
[    41.827] (II) Initializing extension XKEYBOARD
[    41.827] (II) Initializing extension XC-MISC
[    41.828] (II) Initializing extension SECURITY
[    41.828] (II) Initializing extension XFIXES
[    41.829] (II) Initializing extension RENDER
[    41.829] (II) Initializing extension RANDR
[    41.847] (II) Initializing extension COMPOSITE
[    41.848] (II) Initializing extension DAMAGE
[    41.848] (II) Initializing extension MIT-SCREEN-SAVER
[    41.849] (II) Initializing extension DOUBLE-BUFFER
[    41.849] (II) Initializing extension RECORD
[    41.858] (II) Initializing extension DPMS
[    41.859] (II) Initializing extension Present
[    41.859] (II) Initializing extension DRI3
[    41.860] (II) Initializing extension X-Resource
[    41.861] (II) Initializing extension XVideo
[    41.861] (II) Initializing extension XVideo-MotionCompensation
[    41.861] (II) Initializing extension SELinux
[    41.861] (II) SELinux: Disabled on system
[    41.861] (II) Initializing extension GLX
[    42.101] (II) AIGLX: Loaded and initialized vc4
[    42.101] (II) GLX: Initialized DRI2 GL provider for screen 0
[    42.101] (II) Initializing extension XFree86-VidModeExtension
[    42.102] (II) Initializing extension XFree86-DGA
[    42.103] (II) Initializing extension XFree86-DRI
[    42.103] (II) Initializing extension DRI2
[    42.122] (II) modeset(0): Damage tracking initialized
[    42.122] (II) modeset(0): Setting screen physical size to 84 x 391
[    52.748] (II) modeset(0): Disabling kernel dirty updates, not required.
  1. Physical hookup confirmation
    Confirmed ribbon. Even changed ribbon for a shorter one. No difference.
    IMG_20250920_122937
    IMG_20250920_1229371920×1080 165 KB

    IMG_20250920_122726
    IMG_20250920_1227261920×1080 164 KB

Thanks again for your support. Regards.

560

Hey @aluisperezh,

Next checks:

  • Your data confirms the panel is detected on DSI-1 and X sets 320x1480, but the Waveshare touch chip on I2C-10 at 0x45 keeps erroring with I2C write failed -5. That aligns with what we saw in the original log.
  • Backlight sysfs exists under 10-0045 and shows bl_power = 4. Value 4 means the backlight is powered off, which explains the totally dark panel even though DRM reports connected.

Please run these exact commands and paste outputs:

  1. Try to unblank the backlight
  • sudo sh -c ‘echo 0 > /sys/class/backlight/10-0045/bl_power’
  • cat /sys/class/backlight/10-0045/actual_brightness
  • cat /sys/class/backlight/10-0045/bl_power
  1. Sanity on brightness limits
  • cat /sys/class/backlight/10-0045/max_brightness
  • cat /sys/class/backlight/10-0045/brightness
  • sudo sh -c ‘echo 255 > /sys/class/backlight/10-0045/brightness’
  • cat /sys/class/backlight/10-0045/actual_brightness
  1. Panel and backlight registration in dmesg
  • sudo dmesg -T | grep -i -e backlight -e pwm -e regulator -e ws_touchscreen -e panel
  1. Temporarily stop the ws_touchscreen driver to see if it is holding backlight off
  • sudo dmesg -T | grep -i ws_touchscreen | tail -n 50
  • lsmod | grep ws_touchscreen
  • if it is loaded, try: sudo rmmod ws_touchscreen
  • then repeat step 1 unblank commands
  1. Confirm DSI pipeline is active at DRM
  • cat /sys/class/drm/card1-DSI-1/enabled
  • cat /sys/class/drm/card1/uevent

If step 1 brings bl_power to 0 and actual_brightness becomes nonzero, we will know the fix is to ensure the backlight is not forced off by the touch driver during boot. If unblank fails or flips back to 4, the ws_touchscreen errors are likely asserting a shutdown path and we will try a minimal overlay parameter or driver blacklist next to let the panel light while we sort touch.

Kind Regards,

561

Hey @Edrian_Lois_Villanue,

Good timing. Since you already tested everything possible on Volumio 3 (Buster), the next logical step is to move to the Volumio 4.xxx Bookworm Beta branch. That’s where the Raspberry Pi 5 is fully supported and where the video=HDMI-A-1:400x1280M@60,rotate=270 syntax works as intended.

  • Always use the newest Bookworm Beta image from the download part of this beta-test thread. Earlier 4.0xx builds had rough edges, the newest ones include fixes for Pi 5 HDMI, USB, and touchscreens.
  • Yes, Bookworm supports NVMe boot on Raspberry Pi 5. You can flash the image directly to your NVMe drive (via USB adapter) or install to microSD and then clone to NVMe. The Pi 5 firmware handles NVMe just like Raspberry Pi OS.

So short answer:

  • Try the newest Volumio 4.xxx Bookworm Beta.
  • NVMe boot is supported on Pi 5 under Bookworm.

Also, please spend some time on reading opening posts, which already include this information an more.

Kind Regards,

1 Like
562

Hi again @nerd.

First thing I found is that /sys/class/backlight/10-0045/bl_power is 0 when the system boots. A few seconds after the “BOOT COMPLETED” message, the " ws_touchscreen 10-0045: I2C write failed: -5" is displayed again (3x) in the logs and then bl_power changes to 4. The “ws_touchscreen…” message is not shown again in the logs. I waited until bl_power changed to 4 before executing your commands.

  1. Try to unblank the backlight:
volumio@volumio:~$ sudo sh -c 'echo 0 > /sys/class/backlight/10-0045/bl_power'
volumio@volumio:~$ cat /sys/class/backlight/10-0045/actual_brightness
255
volumio@volumio:~$ cat /sys/class/backlight/10-0045/bl_power
0
  1. Sanity on brightness limits
volumio@volumio:~$ cat /sys/class/backlight/10-0045/max_brightness
255
volumio@volumio:~$ cat /sys/class/backlight/10-0045/brightness
255
volumio@volumio:~$ sudo sh -c 'echo 255 > /sys/class/backlight/10-0045/brightness'
volumio@volumio:~$ cat /sys/class/backlight/10-0045/actual_brightness
255
  1. Panel and backlight registration in dmesg
volumio@volumio:~$ sudo dmesg -T | grep -i -e backlight -e pwm -e regulator -e ws_touchscreen -e panel
[Sat Sep 20 18:47:48 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 18:47:48 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 18:47:48 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 18:47:48 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 18:47:49 2025] pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulator
[Sat Sep 20 18:47:49 2025] pci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulator
[Sat Sep 20 18:47:49 2025] pci_bus 0000:01: supply vpcie12v not found, using dummy regulator
[Sat Sep 20 18:47:50 2025] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/panel_disp1@45
[Sat Sep 20 18:47:50 2025] /soc/i2c0mux/i2c@1/panel_disp1@45: Fixed dependency cycle(s) with /soc/dsi@7e700000
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:51 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:51 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:47:51 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:00 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:00 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:00 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] Goodix-TS 10-0014: supply AVDD28 not found, using dummy regulator
[Sat Sep 20 18:48:02 2025] Goodix-TS 10-0014: supply VDDIO not found, using dummy regulator
[Sat Sep 20 18:48:02 2025] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
[Sat Sep 20 18:48:02 2025] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:04 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:04 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:26 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:26 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:03:31 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:03:31 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:05:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:05:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
  1. Temporarily stop the ws_touchscreen driver to see if it is holding backlight off
volumio@volumio:~$ sudo dmesg -T | grep -i ws_touchscreen | tail -n 50
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:02 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:04 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:04 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:26 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:48:26 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 18:50:30 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:03:31 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:03:31 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:05:50 2025] ws_touchscreen 10-0045: I2C write failed: -5
[Sat Sep 20 19:05:50 2025] ws_touchscreen 10-0045: I2C write failed: -5

volumio@volumio:~$ lsmod | grep ws_touchscreen
volumio@volumio:~$
  1. Confirm DSI pipeline is active at DRM
volumio@volumio:~$ cat /sys/class/drm/card1-DSI-1/enabled
enabled

volumio@volumio:~$ cat /sys/class/drm/card1/uevent
MAJOR=226
MINOR=1
DEVNAME=dri/card1
DEVTYPE=drm_minor

After all these tests, bl_power is still 0, and nothing has appeared in the screen nor backlight has turned on.

Best regards.

563

Hey @aluisperezh,

Based on everything you verified, you have enough to take this up with Waveshare. Please open a ticket with their support and include the details from our tests so they can reproduce and advise a firmware or driver fix.

Given that another identical screen works with the same Pi 4 and the non-working screen does work on Pi 5, this points to a device- or firmware-specific init quirk exposed only on Pi 4 with this kernel/userspace. We believe Waveshare is best positioned to advise the correct overlay or driver changes.

Kind Regards,

564

Thank you again for your support. I’ll try to find out something with Waveshare.

Best regards.

565

Hi everyone,

OTA update from 4.022 to 4.023 → OK
Rpi 4, boot on SD with official Touch Display 2 and allo DigiOne Signature
Plugins : Touch Display // Radio Paradise // SqueezeLite MC

Logs if useful for developers
Regards
Benoit

566

OTA from 4.022 to 4.023
Pi4B, SD boot, Topping D10S USB DAC

Tested and working:
Tidal and Tidal Connect playback
Playing local files
Web Radio

Log http://logs.volumio.org/volumio/kEJ2Fiw.html

Super stable for me the last few versions.

567

Seamless OTA Update: 4.022 → 4.023
Just completed the over-the-air update from 4.022 to 4.023—flawless execution.
Running on Pi5 with NVME boot and Cambridge Audio DacMagic 200M via USB. Everything working perfectly.

568

Dear Volumionauts,

Today marks a truly significant milestone in the Volumio journey:

The Volumio Bookworm Beta is officially entering its pre-release phase.
This is the final stretch. The system has reached feature completeness and is now on the formal path toward release readiness.

This is not just a version bump. This is the result of months of coordinated work across:

  • A complete OS base migration from Debian Buster to Bookworm
  • Full platform coverage for Raspberry Pi and x86_64, with more ports coming
  • Major reworks to the audio pipeline, Bluetooth stack, driver layers, and core plugin system
  • Plugins aligned with the Bookworm libraries resulted in substantial code rewrite.
  • Careful regression testing, metadata fixes, connectivity improvements, and service stabilizations
  • Kernel upgrades, CD audio rewrites, and new firmware bundles

None of this would have been possible without the incredible support and dedication of our community.

From developers submitting patches and logs, to testers hammering early builds, to those reporting obscure edge cases and helping us track down hardware-specific regressions - you have made this possible.

To everyone who contributed, gave feedback, tested builds, rebuilt packages, or simply stayed patient while the system matured: Thank you.

Now, as we move into final qualification:

  • Every remaining hiccup will be triaged
  • All edge cases are reviewed
  • Risk will be weighed carefully for each pending change

The qualifying beta is now under formal evaluation for stable release.

Let’s keep the momentum going.
Fingers crossed - we’re almost there.

Kind Regards,

16 Likes
569

Hi @nerd, thank you for always helping me with my concerns. Finally, made it worked!

570

Does this mean that Volumio Primo V1 (Thinkerboard based) will be upgradeable to this new version?