Screen / Display options for Raspberry Pi?

ahajnal · November 15, 2020, 1:35pm

Many thanks for the fast replies.
I am using a RPI4 with volumio 2.852 and the latest touch plugin 1.2.0
On the waveshare wiki for this display I saw the following comment:

If you use Raspberry Pi 4, you need to remove the line: dtoverlay=cv4-fkms-V3D

…but my config.txt does not contain this line, it looks like this:

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

include userconfig.txt

Volumio i2s setting below: do not alter

dtoverlay=hifiberry-dac

Touch Display gpu_mem setting below: do not alter

gpu_mem=64

gvolt · November 15, 2020, 1:44pm

That’s normal.

/boot/config.txt looks OK.

Could you also post the logs I requested, please?

Are you able to check with version which has been published before (2.834)?

Darmur · November 15, 2020, 2:52pm

did you change the GPU memory assignment?

please try to restore this setting to the default value

ahajnal · November 15, 2020, 3:34pm

The problem is that volumio does not even start when the screen is connected.
If I connect the screen after startup, turn the touch plugin off and on again, I get this:

Nov 15 15:31:29 volumio volumio[1166]: info: Enabling plugin touch_display

Nov 15 15:31:29 volumio volumio[1166]: info: Loading plugin “touch_display”…

Nov 15 15:31:29 volumio volumio[1166]: info: Applying required configuration parameters for plugin touch_display

Nov 15 15:31:29 volumio volumio[1166]: info: PLUGIN START: touch_display

Nov 15 15:31:29 volumio volumio[1166]: info: Loading i18n strings for locale en

Nov 15 15:31:29 volumio sudo[3226]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl daemon-reload

Nov 15 15:31:29 volumio sudo[3226]: pam_unix(sudo:session): session opened for user root by (uid=0)

Nov 15 15:31:29 volumio systemd[1]: Reloading.

Nov 15 15:31:29 volumio systemd[1]: [/lib/systemd/system/mpd.service:18] Unknown lvalue ‘ProtectKernelTunables’ in section 'Service’

Nov 15 15:31:29 volumio systemd[1]: [/lib/systemd/system/mpd.service:19] Unknown lvalue ‘ProtectControlGroups’ in section 'Service’

Nov 15 15:31:29 volumio systemd[1]: [/lib/systemd/system/mpd.service:20] Unknown lvalue ‘ProtectKernelModules’ in section 'Service’

Nov 15 15:31:29 volumio systemd[1]: [/lib/systemd/system/mpd.service:23] Unknown lvalue ‘RestrictNamespaces’ in section 'Service’

Nov 15 15:31:29 volumio systemd[1]: Configuration file /lib/systemd/system/spop.service is marked executable. Please remove executable permission bits. Proceeding anyway.

Nov 15 15:31:29 volumio systemd[1]: Configuration file /lib/systemd/system/spop.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.

Nov 15 15:31:29 volumio sudo[3226]: pam_unix(sudo:session): session closed for user root

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: systemctl daemon-reload succeeded.

Nov 15 15:31:29 volumio sudo[3246]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start volumio-kiosk.service

Nov 15 15:31:29 volumio sudo[3246]: pam_unix(sudo:session): session opened for user root by (uid=0)

Nov 15 15:31:29 volumio systemd[1]: Starting Volumio Kiosk…

Nov 15 15:31:29 volumio systemd[1]: Started Volumio Kiosk.

Nov 15 15:31:29 volumio startx[3251]: X.Org X Server 1.18.4

Nov 15 15:31:29 volumio startx[3251]: Release Date: 2016-07-19

Nov 15 15:31:29 volumio startx[3251]: X Protocol Version 11, Revision 0

Nov 15 15:31:29 volumio startx[3251]: Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian

Nov 15 15:31:29 volumio startx[3251]: Current Operating System: Linux volumio 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l

Nov 15 15:31:29 volumio startx[3251]: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:5A:82:9A vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash quiet 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 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0 snd-bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_headphones=1

Nov 15 15:31:29 volumio startx[3251]: Build Date: 11 November 2016 11:59:59AM

Nov 15 15:31:29 volumio startx[3251]: xorg-server 2:1.18.4-2+rpi1 (https://www.debian.org/support)

Nov 15 15:31:29 volumio startx[3251]: Current version of pixman: 0.32.6

Nov 15 15:31:29 volumio startx[3251]: Before reporting problems, check http://wiki.x.org

Nov 15 15:31:29 volumio startx[3251]: to make sure that you have the latest version.

Nov 15 15:31:29 volumio startx[3251]: Markers: (–) probed, (**) from config file, (==) default setting,

Nov 15 15:31:29 volumio startx[3251]: (++) from command line, (!!) notice, (II) informational,

Nov 15 15:31:29 volumio startx[3251]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

Nov 15 15:31:29 volumio startx[3251]: (==) Log file: “/var/log/Xorg.0.log”, Time: Sun Nov 15 15:31:29 2020

Nov 15 15:31:29 volumio startx[3251]: (==) Using config directory: “/etc/X11/xorg.conf.d”

Nov 15 15:31:29 volumio startx[3251]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”

Nov 15 15:31:29 volumio startx[3251]: modprobe: FATAL: Module g2d_23 not found.

Nov 15 15:31:29 volumio sudo[3246]: pam_unix(sudo:session): session closed for user root

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: systemctl start volumio-kiosk.service succeeded.

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: Volumio Kiosk started

Nov 15 15:31:29 volumio volumio[1166]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam

Nov 15 15:31:29 volumio volumio[1166]: info: CoreCommandRouter::volumioGetState

Nov 15 15:31:29 volumio volumio[1166]: info: CorePlayQueue::getTrack 0

Nov 15 15:31:29 volumio volumio[1166]: info: Done.

Nov 15 15:31:29 volumio volumio[1166]: info: CoreCommandRouter::volumioGetState

Nov 15 15:31:29 volumio volumio[1166]: info: CorePlayQueue::getTrack 0

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: No Raspberry Pi Foundation touch screen detected.

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: Using /boot/config.txt instead of /boot/userconfig.txt.

Nov 15 15:31:29 volumio volumio[1166]: info: touch_display: Un-/commenting gpu_mem settings in /boot/config.txt.

Nov 15 15:31:30 volumio volumio[1166]: info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0

Nov 15 15:31:30 volumio sudo[3288]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/sed -i -e /Option “TransformationMatrix”/d /etc/X11/xorg.conf.d/95-touch_display-plugin.conf

Nov 15 15:31:30 volumio sudo[3288]: pam_unix(sudo:session): session opened for user root by (uid=0)

Nov 15 15:31:30 volumio sudo[3288]: pam_unix(sudo:session): session closed for user root

Nov 15 15:31:30 volumio volumio[1166]: info: touch_display: Touchscreen transformation matrix removed.

Nov 15 15:31:30 volumio volumio[1166]: info: touch_display: Setting screensaver timeout to 120 seconds.

Nov 15 15:31:31 volumio pulseaudio[3357]: Stale PID file, overwriting.

Nov 15 15:31:31 volumio pulseaudio[3357]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message

Nov 15 15:31:31 volumio bluetoothd[751]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource

Nov 15 15:31:31 volumio bluetoothd[751]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink

Nov 15 15:31:31 volumio pulseaudio[3357]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist

gvolt · November 15, 2020, 4:01pm

To avoid a misunderstanding: When the display is connected does Volumio not boot at all? Or does Volumio not finish starting and you see circling balls?

At a first glance this looks normal, too.

What happens when the Touch Display plugin is disabled and you do a cold boot with the display connected?

Darmur · November 16, 2020, 10:30am

does the scree work if you use a standard RaspiOS image?

Barbarian_Gaming · January 15, 2021, 6:25pm

Hello, I also have the OSOYOO 5 Inch DSI diplay but i’m not able to run it from Volumio as i get only a white screen. Can you please tell me how to proceed to troubleshoot the actual problem ? I’ve tried several time to be sure to have properly seated the ribbon cable.

Thanks in advance.

gvolt · January 15, 2021, 7:05pm

I assume you have installed the Touch Display plugin and enabled it. It is possible that some packages the plugin needs did not get downloaded properly during the installation of the plugin. You could try to uninstall and re-install the plugin at first. If that should not help please connect to Volumio via SSH and post the result of

systemctl status -l volumio-kiosk.service

Barbarian_Gaming · January 15, 2021, 9:52pm

Thanks a lot. Yes I have installed the Touch display plugin an enabled it two times to be sure.
Here are the results of the

systemctl status -l volumio-kiosk.service

● volumio-kiosk.service - Volumio Kiosk
   Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled)
   Active: active (running) since Fri 2021-01-15 21:46:22 UTC; 4min 9s ago
 Main PID: 1250 (startx)
   CGroup: /system.slice/volumio-kiosk.service
           ├─1250 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh -- -nocursor
           ├─1273 xinit /etc/X11/Xsession /opt/volumiokiosk.sh -- /usr/bin/X :0 -nocursor -auth /tmp/serverauth.EZNDPwy0uf
           ├─1274 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.EZNDPwy0uf
           ├─1400 /bin/bash /opt/volumiokiosk.sh
           ├─1418 /usr/bin/ssh-agent /opt/volumiokiosk.sh
           ├─1423 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
           ├─1424 /usr/lib/chromium-browser/chromium-browser --enable-pinch --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --simulate-outdated-no-au=Tue, 31 Dec 2099 23:59:59 GMT --disable-pinch --kiosk --no-first-run --noerrdialogs --disable-3d-apis --disable-breakpad --disable-crash-reporter --disable-infobars --disable-session-crashed-bubble --disable-translate --user-data-dir=/data/volumiokiosk http://localhost:3000
           ├─1478 /usr/bin/pulseaudio --start
           ├─1485 /usr/lib/chromium-browser/chromium-browser --type=zygote --noerrdialogs --user-data-dir=/data/volumiokiosk --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
           ├─1490 /bin/sh /usr/bin/start-pulseaudio-x11
           ├─1491 /usr/bin/xprop -root -spy
           ├─1494 /usr/lib/chromium-browser/chromium-browser --type=zygote --noerrdialogs --user-data-dir=/data/volumiokiosk --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
           └─1529 /usr/lib/chromium-browser/chromium-browser --type=renderer --disable-3d-apis --disable-breakpad --disable-pinch --enable-pinch --enable-features=AutofillCreditCardSigninPromo<AutofillCreditCardSigninPromo,AutofillProfileCleanup<AutofillProfileCleanup,DocumentWriteEvaluator<DisallowFetchForDocWrittenScriptsInMainFrame,ExpectCTReporting<ExpectCTReporting,IncidentReportingDisableUpload<SafeBrowsingIncidentReportingService,IncidentReportingModuleLoadAnalysis<SafeBrowsingIncidentReportingServiceFeatures,IncidentReportingSuspiciousModuleReporting<SafeBrowsingIncidentReportingServiceFeatures,MaterialDesignUserManager<MaterialDesignUserManager,NegotiateTLS13<TLS13Negotiation,NetworkTimeServiceQuerying<NetworkTimeQueries,NewAudioRenderingMixingStrategy<NewAudioRenderingMixingStrategy

Jan 15 21:46:22 music startx[1250]: Markers: (--) probed, (**) from config file, (==) default setting,
Jan 15 21:46:22 music startx[1250]: (++) from command line, (!!) notice, (II) informational,
Jan 15 21:46:22 music startx[1250]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jan 15 21:46:22 music startx[1250]: (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 15 21:46:22 2021
Jan 15 21:46:22 music startx[1250]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Jan 15 21:46:22 music startx[1250]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Jan 15 21:46:22 music startx[1250]: modprobe: FATAL: Module g2d_23 not found.
Jan 15 21:46:25 music pulseaudio[1478]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Jan 15 21:46:25 music pulseaudio[1478]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Jan 15 21:46:25 music pulseaudio[1478]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist

gvolt · January 15, 2021, 10:42pm

I guess one of the connections of the display is not ok.

Please double-check the DSI cable is properly seated, especially that it is not tilted in the connectors and that it is seated all the way into the connectors. If re-seating the DSI cable should not help and you you have a second one exchange them to rule out a defective DSI cable.

Also try to inspect the preinstalled yellowish cables between the display and its PCB for possible damages.

In case nothing of the above helps I would recommend to test the function of the display with another OS and / or another Pi.

Edit: Forgot to ask: Do you see the login screen of Volumio (white text, black background) before the screen gets white or is the screen white right after powering on?

Barbarian_Gaming · January 19, 2021, 9:35am

Thanks a Lot. I ordered a new cable to test it out as I get only white screen even during boot phase.
I will keep this post updated when the new cable arrives.

Edit: New cable dosen’t fix it still have to test it an another raspberry pi to see if it’s the screen or the pi

gvolt · January 19, 2021, 9:41am

Hopefully testing with another Pi clears things up. Apart from only trying a different Pi you might also check with another OS.

Barbarian_Gaming · January 25, 2021, 8:25am

Well screen seem to be faulty. Tested an other pie and OS and still the same behaviour so i’m waiting for a refund. Thanks to all of you for your help.

gvolt · January 25, 2021, 8:38am

Too bad! Good luck if / when you are ordering another screen

KSchieding · December 23, 2021, 2:55pm

Hi Everyone… I’m a newbie to Volumio and RPi. I have built a streamer that works great with Qobuz, Volumio, RPi 4, and a USB DAC from Schiit. But, I’d like to put it all in a chassis and install a small screen. Looking for a 3.5-4.5" screen size and I’d prefer the screen to be remote from the RPi (ie. not a Hat). Can I get some recommendations for screens to use?.. The less work I’d have to do with plugins, etc., the better :). Thanks everyone.