Running Zynthian on Seeed Studio reTerminal

Ok, as root, running

DISPLAY=:0 xrandr --output default --rotate left --reflect normal

I get

xrandr: output default cannot use rotation “left” reflection “none”

Changing :0 to :0.0 has the same effect

Yes! We have success…

In a post pretty equal to my issue (Pi 3 running Manjaro) I did:

mv /etc/X11/xorg.conf.d/99-fbdev.conf /etc/X11/xorg.conf.d/99-fbdev.conf.old

After that, xrandr identified the screen as DSI-1 and I could rotate it as root with>

DISPLAY=:0.0 xrandr --output DSI-1 --rotate right

Thanks for the help!

1 Like

And after adding

Section “Monitor”
Identifier “DSI-1”
Option “Rotate” “right”

to /etc/X11/xorg.conf.d/99-calibration.conf and rebooting, the reTerminal booted into Zynthian correctly rotated!

1 Like


Setup is pretty preliminary, I used a Raspberry Pi DOUBLER to be able to both connect the HifiBerry ADC+DAC Pro and the MIDI-hat for the moment, so it’s a bit “how ya doing” :wink:

I’m also using the seeed reTerminal extension E10-1 cause I’m powering it by a 12V 4A PSU with barrel connector:


Hi, my reterminal is on the way and plan on using it with zynthian. Would you mind explaining what you have done to get it working? I will use the hifiberry adc dac stage.

I find this ReTerminal pretty cool.

Hi jhordies!

I will have to look up what I did, because my ‘professional’ workload has temporary increased a lot the last weeks, this ‘hobby’-project was pushed back for now. But I’m planning on getting started again in a couple of weeks when the workload decreases to normal levels again.

Tomorrow, If I find a gap I’ll look into it and give some more details.

That would be great thanks!
The reterminal arrived today, can’t wait to get it running on zynthian.

Hi again, could you maybe just tell me from the top of your head what you did, I will figure the rest out and document it.


I know that this is an old post, but I would like to share that I’m running Zynthian flawlessly in my reTerminal. It needed some minor adjustments, but nothing too complicated. If someone is still interested, I have the process fresh in my mind, and I could write some kind of a guide. Let me know!

Of course, thanks to all the people involved in this wonderful project! :slight_smile:

Hi, that would be great !
I used my re terminal for another purpose but it is available again now so it could be a nice Xmas toy to play with.
Thank you :blush:

Good! Let me work on it and send you an update here.

Great - I’m very interested in this also, because reTerminal, which I wasn’t aware of till now, is CM4 based, and I want to understand what needs to change to move Zynthian to the CM4.

1 Like

Hi @tunagenes ,

Maybe there’s an easiest way To do it now.

1 Like

In that aspect, it worked out of the box. The things that need to be fixed are related only to the external hardware: the LCD panel, buttons, touchscreen…

1 Like

Hey guys, I’ve finished the guide. I was not sure to where should I put it, so I created a github repo and placed it there:

Zynthian on reTerminal installation

Hope you find it useful! In case of error, please tell me here, and I’ll try to fix it as soon as posible.
Happy Synthing! :slight_smile:


Very nice documentation !
And even with the button config ! Very very cool Thanks !

1 Like

Good morning!

I found an issue when updating to testing (I would like to write a module to integrate my MIDI controller). The thing is that, in stable, everything works flawlessly, but in testing, the touchscreen does not work.

Is not a problem of the UI (I can control it using the buttons), nor the driver of the touch panel (as xinput shows it and evtest logs the correct numbers when I touch it). The log of Xorg does not show any error (I’ve compared both logs, testing and stable, and are basically the same, just some minor changes in the device numbers).

Also, /proc/bus/input/devices shows the TP, sometimes as event3 and others as event2, didn’t see it as event0 yet (could this be the problem?). [UPDATE: I’ve seen it as event0, but without any change in its behaviour]

Moreover, every now and then it seems to work at first, but just only during 2 or 3 seconds.

I’m out of ideas :sweat_smile: Does anyone have had a similar problem? Or has any clue? Every idea is welcomed! Thanks! :grinning:

UPDATE 2: Ok, things are getting stranger… It seems that it works OK at the beginning, on every boot, and when I kill the Xorg process (which Zynthian restarts). BUT, when I touch the lower part of the screen (higher Y axis), it stops working. :astonished: I don’t think that is a faulty device, as in Zynthian stable it works perfectly.

More stranger things: with the TP working, if I print its xinput properties, it says that the device is not enabled (even though it is working):

xinput list-props seeed-tp
Device 'seeed-tp':
	Device Enabled (145):	0

Then, I can ‘break’ it touching the lower Y axis part, and it stops working, as always. BUT, I can enable it again, using:

xinput enable seeed-tp
xinput list-props seeed-tp
Device 'seeed-tp':
	Device Enabled (145):	1

And then, it works again, and I can use the whole screen! :joy: It won’t stop working until the next reboot, when the device is disabled again. I need to check why is it disabled in the first instance, but at least, the problem is easy to workaround.

UPDATE: For those wondering, I ended up adding the following systemd service to fix the problem:

# cat /etc/systemd/system/xinput-enable-tp.service 
Description=Run xinput to enable seeed-tp device

ExecStart=/bin/bash -c 'while ! $(xset q > /dev/null 2>&1); do sleep 2; done; sleep 5; xinput enable seeed-tp'


It waits until Zynthian and Xorg are running, and then, after 5 seconds, it does the xinput trick. It’s not the most elegant solution, but as X is handled by Zynthian, and I don’t want to loose the hack on the next update, I couldn’t come up with a better solution :sweat_smile: