What are the outputs of
chromium-browser -version
and
systemctl status -l volumio-kiosk.service
?
volumio@volumio2:~$ chromium-browser -version
-bash: chromium-browser: command not found
volumio@volumio2:~$ systemctl status -l volumio-kiosk.service
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled)
Active: active (running) since Sun 2022-02-20 22:14:16 UTC; 8min ago
Main PID: 1160 (startx)
CGroup: /system.slice/volumio-kiosk.service
├─1160 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh – -nocursor
├─1184 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0 -nocursor -auth /tmp/serverauth.9nxgUExXhn
├─1186 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.9nxgUExXhn
├─1249 /bin/bash /opt/volumiokiosk.sh
├─1266 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─1271 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
├─1625 /usr/bin/pulseaudio --start
├─1814 /bin/sh /usr/bin/start-pulseaudio-x11
└─1816 /usr/bin/xprop -root -spy
Feb 20 22:14:16 volumio2 startx[1160]: Markers: (–) probed, (**) from config file, (==) default setting,
Feb 20 22:14:16 volumio2 startx[1160]: (++) from command line, (!!) notice, (II) informational,
Feb 20 22:14:16 volumio2 startx[1160]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Feb 20 22:14:16 volumio2 startx[1160]: (==) Log file: “/var/log/Xorg.0.log”, Time: Sun Feb 20 22:14:16 2022
Feb 20 22:14:16 volumio2 startx[1160]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Feb 20 22:14:16 volumio2 startx[1160]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Feb 20 22:14:16 volumio2 startx[1160]: modprobe: FATAL: Module g2d_23 not found.
Feb 20 22:14:18 volumio2 pulseaudio[1625]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Feb 20 22:14:19 volumio2 pulseaudio[1625]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Feb 20 22:14:19 volumio2 pulseaudio[1625]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist
At least chromium-browser has not been installed and also has probably not been downloaded successfully. This could be e.g. because of DNS problems or Volumio’s data partition has not been fully expanded and therefore there is not enough space to install chromium-browser.
You may check disk space with
df -h
Look for the line starting with “overlayfs”.
typically 16gb
Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio2:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 487M 1.6G 24% /imgpart
/dev/loop0 355M 355M 0 100% /static
overlay 13G 557M 12G 5% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 2.0G 68K 2.0G 1% /dev/shm
tmpfs 2.0G 4.7M 2.0G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs 2.0G 44K 2.0G 1% /tmp
tmpfs 2.0G 0 2.0G 0% /var/spool/cups
tmpfs 20M 24K 20M 1% /var/log
tmpfs 2.0G 0 2.0G 0% /var/spool/cups/tmp
/dev/mmcblk0p1 61M 57M 3.4M 95% /boot
tmpfs 396M 0 396M 0% /run/user/1000
volumio@volumio2:~$
Looks good. So probably a download problem as mentioned above.
yes no plan what I do wrong. get no picture from the HDMI on Volumio 2.xxx
IMHO you need to somehow make it so that the download of the additional software like chromium-browser - which happens during the installation of the plugin - is successful. To me this appears to be the culprit here.
chromium-browser is running in this time, but maybe I can also get Rotary Encoder KY-040 to run on the volumio 3.xxx then I would switch
I can’t follow, could you rephrase this statement:
I got the chromium browser up and running now. hdmi output still no picture. normally nothing has to be in the config or
Could please post the outputs of
cat /var/log/Xorg.0.log
and
systemctl status -l volumio-kiosk.service
again? Or maybe better PM me to not to clutter this thread too much with logs etc.
volumio@volumio:~$ cat /var/log/Xorg.0.log
[ 900.339]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 900.339] Build Operating System: Linux 5.4.0-72-generic armv8l Raspbian
[ 900.339] Current Operating System: Linux volumio 5.10.3-v7l+ #1386 SMP Sun Dec 27 14:05:40 GMT 2020 armv7l
[ 900.339] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1280 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:51:22:DC 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=ttyAMA0,115200 kgdboc=ttyAMA0,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_headphones=1 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=8
[ 900.339] Build Date: 04 January 2022 10:05:34AM
[ 900.339] xorg-server 2:1.20.4-1+rpt4+deb10u4 (Debian -- Support)
[ 900.339] Current version of pixman: 0.36.0
[ 900.339] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 900.339] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 900.339] (==) Log file: “/var/log/Xorg.0.log”, Time: Mon Feb 21 17:16:28 2022
[ 900.340] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 900.340] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 900.340] (==) No Layout section. Using the first Screen section.
[ 900.340] (==) No screen section available. Using defaults.
[ 900.340] () |–>Screen “Default Screen Section” (0)
[ 900.340] (**) | |–>Monitor “”
[ 900.341] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 900.341] (==) Automatically adding devices
[ 900.341] (==) Automatically enabling devices
[ 900.341] (==) Automatically adding GPU devices
[ 900.341] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 900.341] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 900.341] Entry deleted from font path.
[ 900.341] (==) 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
[ 900.341] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 900.341] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 900.342] (II) Loader magic: 0x1fdf80
[ 900.342] (II) Module ABI versions:
[ 900.342] X.Org ANSI C Emulation: 0.4
[ 900.342] X.Org Video Driver: 24.0
[ 900.342] X.Org XInput driver : 24.1
[ 900.342] X.Org Server Extension : 10.0
[ 900.343] (–) using VT number 2
[ 900.343] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 900.344] (II) no primary bus or device found
[ 900.344] (II) LoadModule: “glx”
[ 900.344] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 900.347] (II) Module glx: vendor=“X.Org Foundation”
[ 900.347] compiled for 1.20.4, module version = 1.0.0
[ 900.347] ABI class: X.Org Server Extension, version 10.0
[ 900.347] (==) Matched modesetting as autoconfigured driver 0
[ 900.347] (==) Matched fbdev as autoconfigured driver 1
[ 900.347] (==) Assigned the driver to the xf86ConfigLayout
[ 900.347] (II) LoadModule: “modesetting”
[ 900.348] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 900.348] (II) Module modesetting: vendor=“X.Org Foundation”
[ 900.348] compiled for 1.20.4, module version = 1.20.4
[ 900.348] Module class: X.Org Video Driver
[ 900.348] ABI class: X.Org Video Driver, version 24.0
[ 900.348] (II) LoadModule: “fbdev”
[ 900.348] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 900.348] (II) Module fbdev: vendor=“X.Org Foundation”
[ 900.348] compiled for 1.20.3, module version = 0.5.0
[ 900.348] Module class: X.Org Video Driver
[ 900.348] ABI class: X.Org Video Driver, version 24.0
[ 900.349] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 900.349] (II) FBDEV: driver for framebuffer: fbdev
[ 900.354] (WW) Falling back to old probe method for modesetting
[ 900.354] (EE) open /dev/dri/card0: No such file or directory
[ 900.354] (WW) Falling back to old probe method for fbdev
[ 900.354] (II) Loading sub module “fbdevhw”
[ 900.354] (II) LoadModule: “fbdevhw”
[ 900.354] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 900.355] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 900.355] compiled for 1.20.4, module version = 0.0.2
[ 900.355] ABI class: X.Org Video Driver, version 24.0
[ 900.355] (II) FBDEV(0): using default device
[ 900.355] (II) FBDEV(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 900.355] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 900.355] (==) FBDEV(0): RGB weight 888
[ 900.355] (==) FBDEV(0): Default visual is TrueColor
[ 900.355] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 900.355] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 9600kB)
[ 900.355] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 900.355] (II) FBDEV(0): checking modes against framebuffer device…
[ 900.355] (II) FBDEV(0): checking modes against monitor…
[ 900.355] (II) FBDEV(0): Virtual size is 1920x1280 (pitch 1920)
[ 900.355] () FBDEV(0): Built-in mode “current”
[ 900.355] (==) FBDEV(0): DPI set to (96, 96)
[ 900.355] (II) Loading sub module “fb”
[ 900.355] (II) LoadModule: “fb”
[ 900.355] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 900.356] (II) Module fb: vendor=“X.Org Foundation”
[ 900.356] compiled for 1.20.4, module version = 1.0.0
[ 900.356] ABI class: X.Org ANSI C Emulation, version 0.4
[ 900.356] () FBDEV(0): using shadow framebuffer
[ 900.356] (II) Loading sub module “shadow”
[ 900.356] (II) LoadModule: “shadow”
[ 900.356] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 900.356] (II) Module shadow: vendor=“X.Org Foundation”
[ 900.356] compiled for 1.20.4, module version = 1.1.0
[ 900.356] ABI class: X.Org ANSI C Emulation, version 0.4
[ 900.356] (II) UnloadModule: “modesetting”
[ 900.356] (II) Unloading modesetting
[ 900.357] (==) FBDEV(0): Backing store enabled
[ 900.358] (==) FBDEV(0): DPMS enabled
[ 900.358] (II) Initializing extension Generic Event Extension
[ 900.358] (II) Initializing extension SHAPE
[ 900.359] (II) Initializing extension MIT-SHM
[ 900.360] (II) Initializing extension XInputExtension
[ 900.360] (II) Initializing extension XTEST
[ 900.361] (II) Initializing extension BIG-REQUESTS
[ 900.362] (II) Initializing extension SYNC
[ 900.362] (II) Initializing extension XKEYBOARD
[ 900.363] (II) Initializing extension XC-MISC
[ 900.364] (II) Initializing extension SECURITY
[ 900.364] (II) Initializing extension XFIXES
[ 900.365] (II) Initializing extension RENDER
[ 900.365] (II) Initializing extension RANDR
[ 900.367] (II) Initializing extension COMPOSITE
[ 900.367] (II) Initializing extension DAMAGE
[ 900.368] (II) Initializing extension MIT-SCREEN-SAVER
[ 900.368] (II) Initializing extension DOUBLE-BUFFER
[ 900.369] (II) Initializing extension RECORD
[ 900.370] (II) Initializing extension DPMS
[ 900.370] (II) Initializing extension Present
[ 900.371] (II) Initializing extension DRI3
[ 900.371] (II) Initializing extension X-Resource
[ 900.372] (II) Initializing extension XVideo
[ 900.372] (II) Initializing extension XVideo-MotionCompensation
[ 900.372] (II) Initializing extension SELinux
[ 900.372] (II) SELinux: Disabled on system
[ 900.372] (II) Initializing extension GLX
[ 900.373] (II) AIGLX: Screen 0 is not DRI2 capable
[ 900.461] (II) IGLX: Loaded and initialized swrast
[ 900.461] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 900.461] (II) Initializing extension XFree86-VidModeExtension
[ 900.461] (II) Initializing extension XFree86-DGA
[ 900.462] (II) Initializing extension XFree86-DRI
[ 900.462] (II) Initializing extension DRI2
volumio@volumio:~$ systemctl status -l volumio-kiosk.service
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled; vendor p
Active: active (running) since Mon 2022-02-21 17:16:28 UTC; 2min 59s ago
Main PID: 11258 (startx)
Tasks: 17 (limit: 4915)
CGroup: /system.slice/volumio-kiosk.service
├─ 5690
├─11258 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.s
├─11285 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0
├─11286 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.ohD7HoN
├─11305 /bin/bash /opt/volumiokiosk.sh
├─11329 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─11335 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openb
└─11485 /usr/bin/xbindkeys -f /etc/xbindkeysrc
Feb 21 17:16:28 volumio startx[11258]: xorg-server 2:1.20.4-1+rpt4+deb10u4 (http
Feb 21 17:16:28 volumio startx[11258]: Current version of pixman: 0.36.0
Feb 21 17:16:28 volumio startx[11258]: Before reporting problems, check
Feb 21 17:16:28 volumio startx[11258]: to make sure that you have the la
Feb 21 17:16:28 volumio startx[11258]: Markers: (–) probed, (**) from config fi
Feb 21 17:16:28 volumio startx[11258]: (++) from command line, (!!) noti
Feb 21 17:16:28 volumio startx[11258]: (WW) warning, (EE) error, (NI) no
Feb 21 17:16:28 volumio startx[11258]: (==) Log file: “/var/log/Xorg.0.log”, Tim
1 Like
Please post the output of
cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf
cat /boot/config.txt
and
cat /boot/userconfig.txt
thank you in advance for your help
cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf
cat: /usr/share/X11/xorg.conf.d/99-fbturbo.conf: No such file or directory
volumio@volumio:~$ 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
enable_uart=1
include userconfig.txt
dtoverlay=pi3-miniuart-bt
would have to be fixed then, right?
sudo nano /usr/share/X11/xorg.conf.d/99-calibration.conf
sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf
but what comes in the config? and why doesn’t he load them with the plugin? always went
Yes, but “99-calibration.conf” would not be needed for TV.
Just grab a suitable “99-fbturbo.conf” file:
sudo curl -L https://raw.githubusercontent.com/waveshare/LCD-show/master/usr/share/X11/xorg.conf.d/99-fbturbo.conf-HDMI -o /usr/share/X11/xorg.conf.d/99-fbturbo.conf
This depends on the HDMI screen / TV. For more information on that post the results of
tvservice -m DMT
tvservice -m CEA
and
tvservice -s
ok i did it
in /dev/ after reboot comes back now
error: touch_display: Xserver unix domain socket cannot be determined.
but it’s working now
volumio@volumio:~$ cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf
This is a minimal sample config file, which can be copied to
/etc/X11/xorg.conf in order to make the Xorg server pick up
and load xf86-video-fbturbo driver installed in the system.
When troubleshooting, check /var/log/Xorg.0.log for the debugging
output and error messages.
#The driver is made by Waveshare&Spotpear
Run “man fbturbo” to get additional information about the extra
configuration options for tuning the driver.
Section “Device”
Identifier “Allwinner A10/A13 FBDEV”
Driver “fbturbo”
Option “fbdev” “/dev/fb0”
Option "SwapbuffersWait" "true"
EndSection
tvservice -m DMT
Group DMT has 17 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive
mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive
mode 83: 1600x900 @ 60Hz 16:9, clock:108MHz progressive
mode 85: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
tvservice -m CEA:
Group CEA has 22 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive
mode 93: 3840x2160 @ 24Hz 16:9, clock:297MHz progressive
mode 94: 3840x2160 @ 25Hz 16:9, clock:297MHz progressive
(prefer) mode 95: 3840x2160 @ 30Hz 16:9, clock:297MHz progressive
mode 98: 4096x2160 @ 24Hz unknown AR, clock:297MHz progressive
mode 99: 4096x2160 @ 25Hz unknown AR, clock:297MHz progressive
mode 100: 4096x2160 @ 30Hz unknown AR, clock:297MHz progressive
volumio@volumio:~$
tvservice -s:
state 0xa [HDMI CEA (95) RGB lim 16:9], 3840x2160 @ 30.00Hz, progressive
volumio@volumio:~$
If Volumio’s UI is displayed now, no further setting regarding HDMI would be required in “/boot/userconfig.txt” IMHO. At least the correct resolution 3840x2160 and mode seem to be already set.
If the TV’s backlight should not shut off when the screensaver is activated you might try adding hdmi_blanking=1 to your “/boot/userconfig.txt”.
but it works now was related to volumio@volumio:~$ cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf
Sorry for the confusion
So, you still don’t see Volumio’s UI on the TV?