

Aside of that, internally that script calls kodi -standalone as well.

Kodi -standalone vs kodi-standalone btw skips one unnecessary wrapper script which starts PulseAudio (not used by default on DietPi) and a failure loop. Never, ever, had this sort of trouble before. more or less every domain in sources.list has failed at one stage or another whilst doing various APT updating within the last two days. Just cannot get reliable DNS! Even with my router pointing to 9.9.9.9 *. Thanks! Wow, I would like to do that but this DNS malarkey has got me miffed. Poking in the dark really, I'm afraid.ītw, there is a much newer Kodi available from backports: Honestly, I just saw xinit on some page somewhere and thought it might have been the missing piece of the puzzle. Now I also understand why it was looking for xterm as default X client 😄. xinit /usr/bin/kodi-standalone should have worked.
KODI UNABLE TO CREATE GUI LINUX FULL
Our Kodi start script, used by the autostart option as well, knows that and starts Kodi accordingly via xinit: Īnd your first attempt xinit kodi-standalone failed because xinit requires a full path to executables. Yes in that case, there is not yet a Raspberry Pi build but instead the Debian version (old and X11 based) is installed.

even though I knew this to not be so much the case is the SBC world. it was just hard to opt for 32 instinctively as it, well, felt backwards.
KODI UNABLE TO CREATE GUI LINUX 32 BIT
Honestly, happy to use 32 bit as I only have a 4GB RPi4. DietPi-Update | APT upgrade, please wait.Īh sorry, I also completely forgot about the aarch64 thing. They have been ignored, or old ones used instead. DietPi-Update | APT update, please wait. Waiting for X server to shut down (II) Server terminated successfully (0). Specify a program on the command line or make sure that /usr/bin Xinit: Unable to run program "xterm": No such file or directory (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. Xinit: unable to connect to X server: Connection refused (EE) Please also check the log file at "/home/dietpi/.local/share/xorg/Xorg.0.log" for additional information. Please consult the The X.Org Foundation support (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (=) Using system config directory "/usr/share/X11/" (WW) warning, (EE) error, (NI) not implemented, (?) unknown. (++) from command line, (!!) notice, (II) informational, Markers: (-) probed, (**) from config file, (=) default setting, To make sure that you have the latest version. Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:9B:1A:BD vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=tty1 root=PARTUUID=6a73df9f-6140-41e8-840e-f9aaa4b6aa1e rootfstype=ext4 rootdelay=10 elevator=deadline fsck.repair=yes rootwait quiet net.ifnames=0

Build Operating System: Linux 5.4.0-54-generic aarch64 DebianĬurrent Operating System: Linux DietPi 5.10.17-v8+ #1421 SMP PREEMPT Thu May 27 14:01: aarch64
