Seems indeed that the screen rotation is missing
I’m already looking at it.
everything ok here, v3.3.5.
I am updating now.
after update to v3.3.6 rotation settings are gone.
1 Like
It is an already known issue. I will do a new version soon.
@andre_maier @Wheaten @michel8166
3.3.7beta is available and should fix the missing rotation setting.
1 Like
updated to 3.3.7 beta, all good now 
Super fast as usual!
1 Like
Hi, I’m trying to enable a Hyperpixel 4" touch screen with my rpi 4b running volumio. I’ve tried several times with the recommendations or solutions I’ve found doing some research in the forum and in the web. No success so far. Screen works fine if I load standard RPI OS, so the issue is not with the screen. Latest test was with Touch Display plugin 3.3.7 and Now Playing 0.3.7.
Some errors I see in the live log:
=======================================================
(==) Log file: “/var/log/Xorg.0.log”, Time: Thu May 18 19:56:47 2023
(==) Using config directory: “/etc/X11/xorg.conf.d”
(==) Using system config directory “/usr/share/X11/xorg.conf.d”
info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
==========================================================
error: touch_display: Connecting to the Xserver failed.
info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0
info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings
info: CALLMETHOD: system_controller my_volumio retreiveBackendEventStates undefined
info: CoreCommandRouter::executeOnPlugin: my_volumio , retreiveBackendEventStates
info: Received Get System Version
info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
volumio-kiosk.service: Main process exited, code=exited, status=1/FAILURE
volumio-kiosk.service: Failed with result ‘exit-code’.
attached the full live log.
live log volumio hyperpixel.txt (44.9 KB)
any help will be greatly appreciated.
Regards,
Damian
What did you do to get the display working?
Please post the results of
cat /boot/config.txt
cat /boot/userconfig.txt
ls -al /usr/share/X11/xorg.conf.d
ls -al /etc/X11/xorg.conf.d
Here you are, thanks
======================================
volumio@music-server:~$ cat /boot/config.txt
initramfs volumio.initrd
gpu_mem=32
max_usb_current=1
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
force_eeprom_read=0
include userconfig.txt
dtoverlay=vc4-kms-dpi-hyperpixel4
framebuffer_width=800
framebuffer_height=480
#hdmi_group=2
#hdmi_mode=4
disable_overscan=0
dtparam=spi=on
volumio@music-server:~$
volumio@music-server:~$ cat /boot/userconfig.txt
Add your custom config.txt options to this file, which will be preserved during updates
volumio@music-server:~$ ls -al /usr/share/X11/xorg.conf.d
total 32
drwxr-xr-x 2 root root 4096 May 18 21:17 .
drwxr-xr-x 1 root root 4096 May 18 21:17 …
-rw-r–r-- 1 root root 92 Feb 7 2019 10-amdgpu.conf
-rw-r–r-- 1 root root 1350 Apr 4 07:50 10-quirks.conf
-rw-r–r-- 1 root root 92 Apr 6 2019 10-radeon.conf
-rw-r–r-- 1 root root 1429 Mar 31 2019 40-libinput.conf
-rw-r–r-- 1 root root 2747 Jun 26 2017 70-wacom.conf
-rw-r–r-- 1 root root 647 May 18 19:45 99-fbturbo.conf
volumio@music-server:~$ ls -al /etc/X11/xorg.conf.d
total 16
drwxr-xr-x 2 root root 4096 May 18 21:25 .
drwxr-xr-x 1 root root 4096 May 18 21:22 …
-rw-r–r-- 1 root root 316 May 18 21:25 95-touch_display-plugin.conf
========================================
Please also post the result of
ls -al /boot/overlays/*hyperpixel4*
volumio@music-server:~$ ls -al /boot/overlays/hyperpixel4
ls: cannot access ‘/boot/overlays/hyperpixel4’: No such file or directory
Please make sure to use the exact command (with the asterisks in it):
ls -al /boot/overlays/*hyperpixel4*
or run
ls -al /boot/overlays | grep hyperpixel4
Probably dtparam=i2c_arm=on and dtparam=spi=on have to be commented out when using dtoverlay=vc4-kms-dpi-hyperpixel4.
ok, I’ve installed the drivers as explained in GitHub - pimoroni/hyperpixel4 at pi4-kms-dpi
now I have the overlay file
volumio@music-server:~$ ls -al /boot/overlays/hyperpixel4
-rw-rw-rw- 1 root root 2341 May 18 22:42 /boot/overlays/hyperpixel4.dtbo
I’ve also commented out
dtparam=i2c_arm=on and dtparam=spi=on
now the screen is on but seems like backlight not showing anything.
From log file I can see the following errors:
error: touch_display: Xserver unix domain socket cannot be determined.
error: touch_display: Connecting to the Xserver failed.
error: touch_display: Xserver unix domain socket cannot be determined.
…
volumio-kiosk.service: State ‘stop-final-sigterm’ timed out. Killing.
volumio-kiosk.service: Killing process 1810 (crashpad_handle) with signal SIGKILL.
volumio-kiosk.service: Failed with result ‘exit-code’.
info: CALLMETHOD: user_interface now_playing getPluginInfo undefined
I’ve checked volumio-kiosk.service and it’s running.
any idea of what else I can do ?
thanks!
It could be that the “vc4-kms-dpi-hyperpixel4” is suitable only for Bullseye based systems. Volumio currently is based on Buster so I would suggest to try the non-kms overlay.
there is a legacy version in the links i posted. but it asking for a 2020 / 2021 version in the install
i don’t know how old his screen is.
here are the bash files
hyperpixel4-legacy.txt (36.5 KB)
hyperpixel4.txt (1.3 KB)
ok, so thanks to the updates from @gvolt and @dvo I decided to do a fresh start considering this is based on Buster and that I should use legacy installation for the display. After doing that, screen is still backlighted but everytime I set the kiosk to local it blinks. The error I’m seeing now is the following:
xauth: timeout in locking authority file /home/volumio/.Xauthority
Soliciting pool server 154.70.152.178
Soliciting pool server 185.209.85.222
Soliciting pool server 81.27.192.20
receive: Unexpected origin timestamp 0xe811fff8.ad565cc1 does not match aorg 0000000000.00000000 from server@80.50.102.206 xmt 0xe8120014.9b7f0e75
receive: Unexpected origin timestamp 0xe811fff8.ad54145a does not match aorg 0000000000.00000000 from server@52.65.92.111 xmt 0xe8120014.acd56b5b
receive: Unexpected origin timestamp 0xe811fff8.ad514bc5 does not match aorg 0000000000.00000000 from server@154.70.152.178 xmt 0xe8120014.addfacdb
error: [now-playing-app] App error:
error: [now-playing-app] App error:
xauth: timeout in locking authority file /home/volumio/.Xauthority
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 5.4.0-109-generic armv8l Raspbian
Current Operating System: Linux music-server 5.10.92-v7l+ #1514 SMP Mon Jan 17 17:38:03 GMT 2022 armv7l
Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=E4:5F:01:A1:65:72 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=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh rootwait bootdelay=5 elevator=noop logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=0
Build Date: 04 April 2023 07:50:56AM
xorg-server 2:1.20.4-1+rpt4+deb10u9 (Debian -- User Support)
Current version of pixman: 0.36.0
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: Fri May 19 14:03:37 2023
(==) Using config directory: “/etc/X11/xorg.conf.d”
(==) Using system config directory “/usr/share/X11/xorg.conf.d”
broken atomic modeset userspace detected, disabling atomic
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
No protocol specified
waiting for X server to begin accepting connections .
No protocol specified
there went something wrong with the install time stamp of 0000000 is not oke.
gvolt is better in resolving the touch plugin but i see a error in now playing app i guess it’s the plugin.
with what are you burning the 3.xx version? normaly volumio should create a clock and start it.
it looks that didn’t happen.