Hi, nie jesteś sam 
Here is thread about this problem:
but still not solve.
It is problem with all Waveshare, all with not standard resolution.
That is expected, see post #89:
Please post the output of
cat /var/log/Xorg.0.log
Thank you.
I will post the log when I get home
Just to be clear: Touch display starts when I remove line: dtoverlay=vc4-kms-… from config.txt
When line is active - Error connecting to Xserver
So for sure it is not a problem with Touch display addon itself.
For some reason the Xserver seems to fail to start with that option.
If you are back home please also post the output of
ls -al /dev/fb*
Here you are:
ls -al /dev/fb*
volumio@volumio2:~$ ls -al /dev/fb*
crw-rw---- 1 root video 29, 0 Dec 4 22:38 /dev/fb0
volumio@volumio2:~$
volumio@volumio2:~$ cat /var/log/Xorg.0.log
[ 17.876]
xorg X Server 1.20.4
X Protocol Version 11, Revision 0
[ 17.876] Build Operating System: Linux 5.4.0-109-generic armv8l Raspbian
[ 17.876] Current Operating System: Linux volumio2 6.1.58-v8+ #1690 SMP PREEMPT Tue Oct 17 15:37:08 BST 2023 aarch64
[ 17.876] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:A8:99:0F vc_mem.mem_base=0x3fc00000 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=ttyAMA10,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= snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 loglevel=0
[ 17.876] Build Date: 04 April 2023 07:50:56AM
[ 17.877] xorg-server 2:1.20.4-1+rpt4+deb10u9
[ 17.877] Current version of pixman: 0.36.0
[ 17.877] Before reporting problems, check
to make sure that you have the latest version.
[ 17.877] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 17.877] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 4 22:38:58 2023
[ 17.880] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 17.880] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 17.884] (==) No Layout section. Using the first Screen section.
[ 17.884] (==) No screen section available. Using defaults.
[ 17.884] (**) |-->Screen "Default Screen Section" (0)
[ 17.884] (**) | |-->Monitor "<default monitor>"
[ 17.886] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 17.886] (==) Automatically adding devices
[ 17.886] (==) Automatically enabling devices
[ 17.886] (==) Automatically adding GPU devices
[ 17.888] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 17.888] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 17.888] Entry deleted from font path.
[ 17.891] (==) 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
[ 17.891] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 17.891] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 17.891] (II) Loader magic: 0x1fdf80
[ 17.891] (II) Module ABI versions:
[ 17.891] xorg ANSI C Emulation: 0.4
[ 17.891] xorg Video Driver: 24.0
[ 17.891] xorg XInput driver : 24.1
[ 17.891] xorg Server Extension : 10.0
[ 17.892] (--) using VT number 2
[ 17.892] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 17.893] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 17.893] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 17.895] (II) no primary bus or device found
[ 17.895] falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
[ 17.895] (II) LoadModule: "glx"
[ 17.898] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 17.913] (II) Module glx: vendor="xorg Foundation"
[ 17.913] compiled for 1.20.4, module version = 1.0.0
[ 17.913] ABI class: xorg Server Extension, version 10.0
[ 17.913] (==) Matched modesetting as autoconfigured driver 0
[ 17.913] (==) Matched fbdev as autoconfigured driver 1
[ 17.913] (==) Assigned the driver to the xf86ConfigLayout
[ 17.913] (II) LoadModule: "modesetting"
[ 17.913] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 17.916] (II) Module modesetting: vendor="xorg Foundation"
[ 17.916] compiled for 1.20.4, module version = 1.20.4
[ 17.916] Module class: xorg Video Driver
[ 17.916] ABI class: xorg Video Driver, version 24.0
[ 17.916] (II) LoadModule: "fbdev"
[ 17.916] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 17.917] (II) Module fbdev: vendor="xorg Foundation"
[ 17.917] compiled for 1.20.3, module version = 0.5.0
[ 17.917] Module class: xorg Video Driver
[ 17.917] ABI class: xorg Video Driver, version 24.0
[ 17.917] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 17.917] (II) FBDEV: driver for framebuffer: fbdev
[ 17.928] (WW) Falling back to old probe method for modesetting
[ 17.928] (WW) Falling back to old probe method for fbdev
[ 17.928] (II) Loading sub module "fbdevhw"
[ 17.928] (II) LoadModule: "fbdevhw"
[ 17.928] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 17.930] (II) Module fbdevhw: vendor="xorg Foundation"
[ 17.930] compiled for 1.20.4, module version = 0.0.2
[ 17.930] ABI class: xorg Video Driver, version 24.0
[ 17.930] (II) FBDEV(0): using default device
[ 17.944] (II) modeset(G0): using drv /dev/dri/card1
[ 17.944] (EE)
Fatal server error:
[ 17.944] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 17.944] (EE)
[ 17.944] (EE)
Please consult the The xorg Foundation support
at http://wiki.xorg
for help.
[ 17.944] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 17.944] (EE)
[ 18.011] (EE) Server terminated with error (1). Closing log file.
[Wheaten] Formatted the code to make it more readable
Please try the following:
Stop the Touch Display plugin.
As root execute
cat >> /etc/X11/xorg.conf.d/99-vc4.conf <<EOL
Section "OutputClass"
Identifier "vc4"
MatchDriver "vc4"
Driver "modesetting"
Option "PrimaryGPU" "true"
EndSection
EOL
Start the Touch Display plugin.
It works
but the question is how to rotate the screen?
Many, many thanks!!!
Please post the output of
/usr/bin/xrandr --display :0 --query
Here you are
volumio@volumio2:~$ /usr/bin/xrandr --display :0 --query
Screen 0: minimum 320 x 200, current 400 x 1280, maximum 8192 x 8192
HDMI-1 connected primary 400x1280+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
400x1280 60.23*+
1280x720 100.00
320x1480 59.32
HDMI-2 disconnected (normal left inverted right x axis y axis)
thank you!
Try to manually rotate the display clockwise by running
xrandr --output HDMI-1 --rotate right
no luck this time:
volumio@volumio2:~$ xrandr --output HDMI-1 --rotate right
Can’t open display
volumio@volumio2:~$ sudo xrandr --output HDMI-1 --rotate right
[sudo] password for volumio:
Can’t open display
Yes, my bad. Command has to read
xrandr --display :0 --output HDMI-1 --rotate right
You are the man!!!
It works - now I have a working display
thank you!!!
well, after quick check it seems Now Playing plugin doesn’t work.
but for now I am really glad I can ‘see’ my Volumio back.
The really added value of RP5 is speed and audio quality.
@gvolt
Many thanks for you time and final solution (at least work around)!!!
Be aware that setting the rotation using “xrandr” does not survive a reboot. To have the rotation set automatically after each boot you currently have to
mkdir /home/volumio/.config/openbox
cat >> /home/volumio/.config/openbox/autostart <<EOL
xrandr --output HDMI-1 --rotate right
EOL
3 Likes
confirmed again - works!!!
if someone want to reuse command for this particular display: Waveshare 400x1280 7.9", the rotate should be left:
xrandr --output HDMI-1 --rotate left
Again many thanks!!!
Depends on how the display is mounted I guess. 
2 Likes
Just in case if someone is wondering how it goes without cooling: I’m using the Pi 5 in combination with a SSD USB expansion (similar like this here) and Allos Piano 2.1 with Kali as reclocker. All in a more or less open setup (see picture)
I missed to order a heat sink so I’m running everything like this for the time being. During the scan of the SSD and simultaneous playback, the temperature rose to 63°C. When idling, it is around 6 °C less
So it doesn’t look like I’m going to have any problems with overheating. Nevertheless, sooner or later I will install a heat sink, because compared to the Pi 3 it is around 10 °C higher, which is certainly better for durability.
In terms of performance, the look and feel of the GUI is noticeably smoother compared to the Pi 3B. There are still some hangs, but I suspect that this is not due to the CPU but rather to bottlenecks in the network (e.g. when I access my NAS) or Volumio itself.
One thing I had forgotten is that I powered the Pi via Allo’s Kali, but now I need 2 power supplies (1x for the Pi and 1x for Kali) due to the higher power requirement. I tried it with just the power supply of the Kali which delivers 4.2 A, but like this the Pi did not boot.
But anyway, all in all a worthwhile change if you come from Pi 3, I think.
One thing I need to get familiar is the power button. If someone made already some experience it would be great to share it here. E.g. I’m not clear what happens to Volumio if I press it? Is it initating a shotdown in Volumio or is it just a hard shut off?
1 Like
it will initiate a clean shutdown