Installing the Touch Display plugin

(Yes, I’ve seen other discussion on this topic, but I’m not sure I’ve seen an answer that works … so thanks for hearing me out.)

I made a clean new install of 2.114.

When I install the Touch Display plugin, it gets to 70%, appears to be awaiting input and seemingly stops. After reading some of the comments here, I let it sit for a while (had dinner!), came back, and then refreshed the page. Now the Touch Display plugin shows that it’s installed, so I turned it on. For good measure, I also restarted the Volumio.

However, I don’t get the Volumio display on the screen. Instead I get the “console” display, I can login and execure commands, etc.

So … what is the next step?

Thanks.

So, I switched to 2.041 and the touchscreen display is working fine. The plugin installed without any issues and started right up.

I hope that there will be a successor to 2.114 with issues fixed. This is a great piece of software.

I think I know what goes wrong here, the raspberry pi repo just install stuff which should not be installed. Thanks for reporting we’ll fix it!

Would be cool if chrome did not have libraspberrypi0 as dependency. This breaks boot as the new kernel will break the boot process. I guess missing modules are the problem.

I’ve done a fresh install of the latest version of Volumio, after rebooting with the touchscreen plugin installed I get this
tmp_3618-DSC_00151687093614.JPG

I am trying to fix this by preventing the installation of

raspberrypi-bootloader raspberrypi-kernel

Howeve, nor putting

Package: raspberrypi-bootloader Pin: release * Pin-Priority: -1 Package: raspberrypi-kernel Pin: release * Pin-Priority: -1

in

/etc/apt/preferences

nor blocking their installation by putting them on hold with

echo raspberrypi-bootloader hold | dpkg --set-selections
echo raspberrypi-kernel hold | dpkg --set-selections

Does somebody have an idea on how to fix this situation?

Tried install on my rpi0 (I know it’s not recommended), and experienced 2 install problems:

  • keyboard selection hangs first install (need to be done prior in interractive session, or install should do it in non-interractive way)
  • kernel & firmware are indeed replaced with latest 4.4.50+.
    For this second (critical) issue, maybe a “hackish-way” would be for the plugin install procedure to preserve /boot and restore at the end of install?
    I guess hold may not work because they were not installed with dpkg in the first place in the build…need to check what apt-cache policy gives on a new image)

After restoration of my /boot the plugin failed to start (one cause may be my armv6 device, or it does not detect my HDMI TV, too low gpumem, etc).
I have: [ 139.350] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (seems a common issue)
Full log:cat /home/volumio/.local/share/xorg/Xorg.0.log [ 139.154] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 139.155] X Protocol Version 11, Revision 0 [ 139.155] Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian [ 139.156] Current Operating System: Linux volumio 4.4.9+ #884 Fri May 6 17:25:37 BST 2016 armv6l [ 139.156] Kernel command line: bcm2708_fb.fbwidth=1184 bcm2708_fb.fbheight=624 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2708.boardrev=0x900092 bcm2708.serial=0x60e56668 bcm2708.uart_clock=48000000 bcm2708.disk_led_gpio=47 smsc95xx.macaddr=B8:27:EB:E5:66:68 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0x3 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait smsc95xx.turbo_mode=N [ 139.157] Build Date: 11 November 2016 11:59:59AM [ 139.157] xorg-server 2:1.18.4-2+rpi1 (https://www.debian.org/support) [ 139.157] Current version of pixman: 0.32.6 [ 139.158] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 139.158] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 139.159] (==) Log file: "/home/volumio/.local/share/xorg/Xorg.0.log", Time: Wed Mar 8 08:40:14 2017 [ 139.181] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 139.185] (==) No Layout section. Using the first Screen section. [ 139.185] (==) No screen section available. Using defaults. [ 139.185] (**) |-->Screen "Default Screen Section" (0) [ 139.185] (**) | |-->Monitor "<default monitor>" [ 139.187] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 139.187] (**) | |-->Device "Allwinner A10/A13 FBDEV" [ 139.187] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 139.188] (==) Automatically adding devices [ 139.188] (==) Automatically enabling devices [ 139.188] (==) Automatically adding GPU devices [ 139.188] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 139.189] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 139.189] Entry deleted from font path. [ 139.189] (==) 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 [ 139.189] (==) ModulePath set to "/usr/lib/xorg/modules" [ 139.210] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 139.210] (II) Loader magic: 0x7f840f20 [ 139.210] (II) Module ABI versions: [ 139.211] X.Org ANSI C Emulation: 0.4 [ 139.211] X.Org Video Driver: 20.0 [ 139.211] X.Org XInput driver : 22.1 [ 139.211] X.Org Server Extension : 9.0 [ 139.245] (EE) systemd-logind: failed to get session: PID 1258 does not belong to any known session [ 139.247] (II) no primary bus or device found [ 139.247] (II) LoadModule: "glx" [ 139.249] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 139.325] (II) Module glx: vendor="X.Org Foundation" [ 139.325] compiled for 1.18.4, module version = 1.0.0 [ 139.325] ABI class: X.Org Server Extension, version 9.0 [ 139.325] (==) AIGLX enabled [ 139.326] (II) LoadModule: "fbturbo" [ 139.327] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so [ 139.328] (II) Module fbturbo: vendor="X.Org Foundation" [ 139.328] compiled for 1.18.4, module version = 0.5.1 [ 139.328] Module class: X.Org Video Driver [ 139.329] ABI class: X.Org Video Driver, version 20.0 [ 139.329] (II) FBTURBO: driver for framebuffer: fbturbo [ 139.329] (EE) Fatal server error: [ 139.350] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) [ 139.350] (EE) [ 139.350] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 139.351] (EE) Please also check the log file at "/home/volumio/.local/share/xorg/Xorg.0.log" for additional information. [ 139.351] (EE) [ 139.352] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor [ 139.352] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor [ 139.352] (EE) Server terminated with error (1). Closing log file.Note: first lines seem to show it was built for post 4.4.9 kernel (Volumio’s).

Interesting to hear it worked out-of-the-box on 2.041 though…(never tried before)

Yes, the problem rose because the apt repository for pi’s specific binaries was added. Before it just worked

:blush:
From base 2.041:[code]>sudo apt-cache policy raspberrypi-kernel
raspberrypi-kernel:
Installed: (none)
Candidate: 1.20161215-1
Version table:
1.20161215-1 0
500 http://archive.raspberrypi.org/debian/ jessie/main armhf Packages

sudo apt-cache policy raspberrypi-bootloader
raspberrypi-bootloader:
Installed: (none)
Candidate: 1.20161215-1
Version table:
1.20161215-1 0
500 http://archive.raspberrypi.org/debian/ jessie/main armhf Packages[/code]So nothing to hold from…

While at it, any hint on the other X error I get (Cannot open /dev/tty0 (Permission denied))?
Does the script need to add volumio user to some group for access to /dev/tty0
Does gpumem need to be updated (so that vc_stuff can work)?
Thanks

I think this is an heritage of the newly installed package…

On new image, I started fromvolumio@volumio:~$ sudo apt-get -s install raspberrypi-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: raspberrypi-kernel 0 upgraded, 1 newly installed, 0 to remove and 94 not upgraded. Inst raspberrypi-kernel (1.20170303-1 Raspberry Pi Foundation:stable [armhf]) Conf raspberrypi-kernel (1.20170303-1 Raspberry Pi Foundation:stable [armhf])So it would install the new (ugly) package…

Then created /etc/apt/preferences as you described:[code]volumio@volumio:~$ cat /etc/apt/preferences
Package: raspberrypi-bootloader
Pin: release *
Pin-Priority: -1

Package: raspberrypi-kernel
Pin: release *
Pin-Priority: -1[/code] then put the packages on hold with volumio@volumio:~$ sudo apt-mark hold raspberrypi-kernel raspberrypi-bootloader raspberrypi-kernel set on hold raspberrypi-bootloader set on holdthen try installing to check[code]volumio@volumio:~$ sudo apt-get -s install raspberrypi-kernel
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package raspberrypi-kernel is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘raspberrypi-kernel’ has no installation candidate[/code]New (ugly) package is indeed held back now.

So looks good!..
Now have to try it for good. If this works, then we should probably add those things in the Build.

I think I’ve found a workaround… Creating both as fake packages and installing them, then putting them on hold…
I’ll keep you posted

Yes the equivs thing probably?
Thought I would try it if previous did not work; but previous seems a bit simpler.

Ok, so I confirm install script issues related to raspberrypi-kernel and raspberrypi-bootloader are gone with proposed method: hurray!
I’ll submit a Build PR if you don’t mind, so that this is blocked for good for any other plugins or manual installs.

I’m still with 2 issues:

  • keyboard-configuration install (need to be done before plugin install: would be cool if install script did it in non-interactive way)
  • parse_vt_settings: Cannot open /dev/tty0 (Permission denied) as per this
    (adding volumio to tty group is not enough. seems due to some recent X packages)

@michelangelo,
Actually looked more closely to install log, and it turns-out there are still a few things failing despite the positive return message:[code]Installing Plugin

Plugin Successfully Installed
100%

  • Hide details

Downloading plugin at http://volumio.github.io/volumio-plugins/plugins/volumio/armhf/miscellanea/touch_display/touchdisplay.zip
END DOWNLOAD: http://volumio.github.io/volumio-plugins/plugins/volumio/armhf/miscellanea/touch_display/touchdisplay.zip
Creating folder on disk
Unpacking plugin
Checking for duplicate plugin
Copying Plugin into location
Installing dependencies
Installing Chromium Dependencies
Hit http://archive.raspbian.org jessie InRelease
Get:1 http://archive.raspberrypi.org jessie InRelease [22.9 kB]
Hit http://archive.raspbian.org jessie/main Sources
Hit http://archive.raspbian.org jessie/contrib Sources
Hit http://archive.raspbian.org jessie/non-free Sources
Hit http://archive.raspberrypi.org jessie/main Sources
Hit http://archive.raspbian.org jessie/rpi Sources
Get:2 http://archive.raspberrypi.org jessie/ui Sources [16.3 kB]
Hit http://archive.raspbian.org jessie/main armhf Packages
Hit http://archive.raspbian.org jessie/contrib armhf Packages
Hit http://archive.raspbian.org jessie/non-free armhf Packages
Hit http://archive.raspbian.org jessie/rpi armhf Packages
Get:3 http://archive.raspberrypi.org jessie/main armhf Packages [147 kB]
Get:4 http://archive.raspberrypi.org jessie/ui armhf Packages [57.6 kB]
Ign http://archive.raspbian.org jessie/contrib Translation-en
Ign http://archive.raspbian.org jessie/main Translation-en
Ign http://archive.raspbian.org jessie/non-free Translation-en
Ign http://archive.raspbian.org jessie/rpi Translation-en
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Fetched 243 kB in 44s (5437 B/s)
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
You might want to run ‘apt-get -f install’ to correct these.
The following packages have unmet dependencies:
chromium-browser : Depends: libgnome-keyring0 (>= 3.2.2-2~) but it is not installed
Recommends: chromium-browser-l10n but it is not installable
Installing Graphical environment
Reading package lists…
Building dependency tree…
Reading state information…
libexif12 is already the newest version.
xinit is already the newest version.
xorg is already the newest version.
openbox is already the newest version.
You might want to run ‘apt-get -f install’ to correct these:
The following packages have unmet dependencies:
chromium-browser : Depends: libgnome-keyring0 (>= 3.2.2-2~) but it is not going to be installed
Recommends: chromium-browser-l10n but it is not installable
Download Chromium
Install Chromium
(Reading database … 24400 files and directories currently installed.)
Preparing to unpack …/chromium-browser_48.0.2564.82-0ubuntu0.15.04.1.1193_armhf.deb …
Unpacking chromium-browser (48.0.2564.82-0ubuntu0.15.04.1.1193) over (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Preparing to unpack …/chromium-codecs-ffmpeg-extra_48.0.2564.82-0ubuntu0.15.04.1.1193_armhf.deb …
Unpacking chromium-codecs-ffmpeg-extra (48.0.2564.82-0ubuntu0.15.04.1.1193) over (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Setting up chromium-codecs-ffmpeg-extra (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Processing triggers for mime-support (3.58) …
Processing triggers for man-db (2.7.0.2-5) …
Reading package lists…
Building dependency tree…
Reading state information…
Correcting dependencies… Done
The following package was automatically installed and is no longer required:
libxcb-image0
Use ‘apt-get autoremove’ to remove it.
The following packages will be REMOVED:
chromium-browser
0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.
1 not fully installed or removed.
After this operation, 173 MB disk space will be freed.
(Reading database … (Reading database … 5% (Reading database … 10% (Reading database … 15% (Reading database … 20% (Reading database … 25% (Reading database … 30% (Reading database … 35% (Reading database … 40% (Reading database … 45% (Reading database … 50% (Reading database … 55% (Reading database … 60% (Reading database … 65% (Reading database … 70% (Reading database … 75% (Reading database … 80% (Reading database … 85% (Reading database … 90% (Reading database … 95% (Reading database … 100% (Reading database … 24400 files and directories currently installed.)
Removing chromium-browser (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Processing triggers for man-db (2.7.0.2-5) …
Processing triggers for mime-support (3.58) …
Selecting previously unselected package chromium-browser.
(Reading database … 23625 files and directories currently installed.)
Preparing to unpack …/chromium-browser_48.0.2564.82-0ubuntu0.15.04.1.1193_armhf.deb …
Unpacking chromium-browser (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Preparing to unpack …/chromium-codecs-ffmpeg-extra_48.0.2564.82-0ubuntu0.15.04.1.1193_armhf.deb …
Unpacking chromium-codecs-ffmpeg-extra (48.0.2564.82-0ubuntu0.15.04.1.1193) over (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Setting up chromium-codecs-ffmpeg-extra (48.0.2564.82-0ubuntu0.15.04.1.1193) …
Processing triggers for mime-support (3.58) …
Processing triggers for man-db (2.7.0.2-5) …
Creating chromium kiosk start script
Creating Systemd Unit for Kiosk
Allowing volumio to start an xsession
Disabling Kiosk Service
Adding plugin to registry
Plugin Successfully Installed[/code]To fix these I had to explicitly install libgnome-keyring-common libgnome-keyring0 and chromium-browser-l10n
Looking for the latter, I found this of interest: used those sources, and after all these, plugin install.sh goes well.
So you may want to add these 3 items in your script.

So, with this, install is mostly fine now, but… I’m still stucked for starting X session (even with volumio in tty group) with my HDMI TV hoocked to my PiZero:[code]volumio@volumio:~$ cat /home/volumio/.local/share/xorg/Xorg.0.log
[ 134.250]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 134.257] X Protocol Version 11, Revision 0
[ 134.257] Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian
[ 134.258] Current Operating System: Linux volumio 4.4.9+ #884 Fri May 6 17:25:37 BST 2016 armv6l
[ 134.258] Kernel command line: bcm2708_fb.fbwidth=1184 bcm2708_fb.fbheight=624 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2708.boardrev=0x900092 bcm2708.serial=0x60e56668 bcm2708.uart_clock=48000000 bcm2708.disk_led_gpio=47 smsc95xx.macaddr=B8:27:EB:E5:66:68 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0x3 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait smsc95xx.turbo_mode=N
[ 134.259] Build Date: 11 November 2016 11:59:59AM
[ 134.259] xorg-server 2:1.18.4-2+rpi1 (https://www.debian.org/support)
[ 134.270] Current version of pixman: 0.32.6
[ 134.270] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 134.270] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 134.272] (==) Log file: “/home/volumio/.local/share/xorg/Xorg.0.log”, Time: Thu Mar 9 16:21:21 2017
[ 134.274] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 134.277] (==) No Layout section. Using the first Screen section.
[ 134.277] (==) No screen section available. Using defaults.
[ 134.277] (
) |–>Screen “Default Screen Section” (0)
[ 134.278] () | |–>Monitor “”
[ 134.279] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
[ 134.279] (
) | |–>Device “Allwinner A10/A13 FBDEV”
[ 134.300] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 134.300] (==) Automatically adding devices
[ 134.300] (==) Automatically enabling devices
[ 134.301] (==) Automatically adding GPU devices
[ 134.301] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 134.301] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 134.301] Entry deleted from font path.
[ 134.302] (==) 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
[ 134.302] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 134.302] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 134.303] (II) Loader magic: 0x7f75cf20
[ 134.303] (II) Module ABI versions:
[ 134.303] X.Org ANSI C Emulation: 0.4
[ 134.303] X.Org Video Driver: 20.0
[ 134.303] X.Org XInput driver : 22.1
[ 134.303] X.Org Server Extension : 9.0
[ 134.332] (–) using VT number 2

[ 134.332] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 134.333] (II) no primary bus or device found
[ 134.333] (II) LoadModule: “glx”
[ 134.336] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 134.419] (II) Module glx: vendor=“X.Org Foundation”
[ 134.440] compiled for 1.18.4, module version = 1.0.0
[ 134.440] ABI class: X.Org Server Extension, version 9.0
[ 134.440] (==) AIGLX enabled
[ 134.441] (II) LoadModule: “fbturbo”
[ 134.442] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ 134.443] (II) Module fbturbo: vendor=“X.Org Foundation”
[ 134.443] compiled for 1.18.4, module version = 0.5.1
[ 134.444] Module class: X.Org Video Driver
[ 134.444] ABI class: X.Org Video Driver, version 20.0
[ 134.444] (II) FBTURBO: driver for framebuffer: fbturbo
[ 134.445] (EE)
Fatal server error:
[ 134.445] (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
[ 134.445] (EE)
[ 134.446] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 134.446] (EE) Please also check the log file at “/home/volumio/.local/share/xorg/Xorg.0.log” for additional information.
[ 134.446] (EE)
[ 134.447] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[ 134.447] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[ 134.447] (EE) Server terminated with error (1). Closing log file.[/code]
Any hint for that last bit? (@Saiyato added a bunch of rules and rights to users to start X session for Kodi plugin: unsure what to learn from it).

So I’ve had two installs go wrong on 2.114 when installing the plugin. Is the above fix going to make it into the plugin? Can’t realy follow what the above is telling me. Thanks!

Tried on 2.118 another PANIC and entering kdb. Give up on this should have stayed at plain 2.0. Only updated because it said SMB shares fixed and that still doesn’t work :unamused:

You need to start from a new image.
Configure the keyboard from ssh
Do the /etc/apt/preferences and hold thing as per post #p29639 (this will protect against Panic thing)
Then resolve few dependencies with the additional installs described in post #p29708, and install the actual plugin, then activate it and restart.

Still, after all this, nothing on my display (HDMI TV) due to X config issue: interested if you get through it.
But anyway Volumio still works after all this :wink:

Thanks but if i have to flash my card one more time i’ll cry :smiley:

I’ve gone back to 2.041 for the time being. smb still doesn’t work and that was the only reason I upgraded to 2.114 originally!