Vangelis 2606 BETA Image is released. You SHOULD download & install!

Software Updates
121

I was was sure I had tried to get into webconf before and could not but now I can. So I configured everything as I usually do for Vangelis Bookworm and the UI still does not start if I run zynthian.sh i get -

(venv) root@zynthian:/zynthian/zynthian-sys/sbin# zynthian.sh

X.Org X Server 1.21.1.16
X Protocol Version 11, Revision 0
Current Operating System: Linux zynthian 6.18.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.34-1+rpt1 (2026-06-09) aarch64
Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=32 numa=fake=8 system_heap.max_order=0 iommu_dma_numa_policy=interleave smsc95xx.macaddr=2C:CF:67:62:D7:B4 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 root=PARTUUID=e249d476-02 rootfstype=ext4 fsck.repair=yes rootwait console=tty1 logo.nologo modules-load=dwc2,libcomposite
xorg-server 2:21.1.16-1.3+rpt1+deb13u2 ( Debian -- User Support )
Current version of pixman: 0.46.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: “/var/log/Xorg.0.log”, Time: Sat Aug 1 00:07:42 2026
(==) Using config directory: “/etc/X11/xorg.conf.d”
(==) Using system config directory “/usr/share/X11/xorg.conf.d”
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

122

Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices

This is the key part.
Are you using Pi4 or Pi5?

Regards

123

This seems to have fixed the problem *Pi5"

This error occurs on the Raspberry Pi 5 running Debian Trixie (or equivalent rolling/testing builds) because Xorg struggles to identify the primary GPU out of the box on the Pi 5’s upgraded RP1 southbridge architecture. The kernel creates two devices (/dev/dri/card0 and /dev/dri/card1), causing Xorg to get confused and default to a broken framebuffer mode. [1, 2, 3]

You can fix this without needing a manual BusID by forcing Xorg to correctly map the vc4 display driver. [1, 2]

https://www.google.com/search?q=Fatal+server+error%3A+(EE)+Cannot+run+in+framebuffer+mode.+Please+specify+busIDs+for+all+framebuffer+devices&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBBzc4M2owajmoAgawAgHxBQJRzBGijp7r&sourceid=chrome&ie=UTF-8&udm=50&fbs=ABfTbFVyMZGZf1hfvX9uKjN_-G8cxpBkeIeqYwoCbfNVc4vKE9OqRMKGD2T9lFDfEKBBAAmgw9gjb3JGnW1mggl7S6ExEtG8TqIF5H2MOmQV3DWnsbSluP59kn4tGoZpGspo9veYKbF1LUoTNSiUuez_JVboHKbCK6uDYNzXedESHpcRDabk1lrvJ-WrzqbMOHhi-FXJrtrjIkNmJCscf7dbJPi8cHknqA&aep=10&ntc=1&mstk=AUtExfC5jhp6ipw4YNVFdl_fGaboODmsRVhdgHU_AvDDstu-z_djHMAjDf1VBfl1BgH-5txxvT37VqtIhiJnMUt9Hm-pUfV5HMo_CW6AWFXTWRb-pP-Ufq6sCkoyFJAfqS_CnXiDCyRI6jM1oFxRKrvfuzNkAc2CN5W5Q4NXS19engIXHutqBEjPgMOJLK3WcFh5inrQj9QA8fkuUhwxSOs4l9viRYtc96mSHEKq6xglPI3U-wengU_vC86c_q2PNfPdkrn1747BWxBobYMCR8pCzx2dvqptNt2OkarpL7ilutoov_9m919TyiDQcxOaLffM8QGJrbVIDFErNg&aioh=3&csuir=1&cs=0&atvm=2&mtid=BS1tasngNp7-ptQPtJzF8Qs

124

Maybe @jofemodo already knows this problem so this is an un-needed comment from the peanut gallery, but I would look at xwindows log as indicated - in a previous problem having to do with the RPi Touch Display 2 it had an error message that told us exactly what was wrong in the X configuration file.

1 Like
125

I think that is fine. It is very handy that you can turn the buttons on and off.

The problem lies only with the first time; then it seems as if the setting in WebConf is not working.
Maybe a line of explanation next to the setting?

1 Like
126

Do you think it would be technically possible to integrate this device into the official kits, it’s really cheap and compact.

Or is it not possible to have two I2S devices ?

127

Is “SOLO” no longer working?

image
image806×480 77.9 KB

It is perhaps not a good sign that the “S” above the column has been replaced by an “R”, but the device’s help function still lists Solo. However, it does not work.

128

The presets can only be selected via VNC, selection on Zynthian itself shows the new preset, but it still plays the init patch.

image
image118×481 13.4 KB

image

129

By default, strip “solo” toggle has been replaced by “record arm” toggle. But this is now configurable, so you can config the solo toggle or any other mixer toggle to be placed in the strip top position. You can do this from the admin menu. easily.

We still have to update the docs to reflect this.

Regards,

1 Like
130

Not in my zynthians. AFAIK, all presets are available from the zynthian UI. Please, double check this.

BTW, did you download and install the latest BETA SD image, true?

Older bookworm-based images are not longer supported. You must download and install the BETA SD image, based in Trixie.
Please, don’t complain about any issue if you are not running the Vangelis BETA SD image.

Regards,

131

I’m running the latest and updated Vangelis beta.

The presets are available, visible and selectable in Zynthian, but they do not change the actual preset in Vaporizer. That only changes when selected in VNC.

132

Sorry, @HansR ! I can’t reproduce this. It works like a charm in all my zynthians. The preset selection in the zynthian UI are reflected in the native GUI.

Please, try to reproduce starting from scratch (clean all) and check it’s a reproducible issue. If you can reproduce, give a list of steps to reproduce.

Regards,

133

ui_session-20260801144108.log (4.1 KB)

image

134

Regarding how to specify a “list of steps to reproduce an issue”, i would like to comment a little bit because sometimes we find funny things.

An example:

  • Create a synth chain
  • Push any key in the keyboard
  • It doesn’t work

This step list is completely useless.

A better one:

  • Clean ALL
  • Create a synth chain with Dexed in MIDI channel 1. Preset “Vangelis ePiano”.
  • Push any key in the keyboard.
  • It doesn’t produce any sound. The chain’s meter doesn’t show audio activity at all.

This is a little bit better, but it could be better yet. It says nothing about how the MIDI controller is connected and configured. You could add:

  • The keyboard is a USB MIDI controller (Akai MPK Mini mk3) configured in MULTI mode.

A workflow capture video or a snapshot could be very useful, but not always. They doesn’t capture how your zynthian is configured / customized.

Remember:

  • if we can’t reproduce an issue, we can’t fix it.
  • If we can reproduce an issue, it’s almost sure we can fix it.

All the best,

3 Likes
135

Hi @HansR !

I don’t ask for a proof of the issue. I don’t doubt the issue does exist!
What i need is a way to reproduce the issue. A list of steps or a snapshot that captures the issue.

All the best,

1 Like
136

137

It’s not a proof of the issue, it shows the exact steps to replicate it.

What is not clear in the workflow capture?

138

I can’t replicate the issue with this list of steps, sorry.

139
  • Have you tried with a fresh burned image?
  • Have you configured, copied or installed something on the image?
  • Did you change any option from the default value?

Regards,

140

I’d like to ask: How safe it is to backup and restore config? I mean, will it store anything which might got broken along the way? It might restore disconinued functionality, engine information, patchlevel and wiring profiles and whatnot.