In a new install of dietpi from the arm7 32bit bullseye image to a Raspberry pi2, after Kodi installation using the dietpi-software, it will not autostart and in the command line a startkodi returns:
failed to open zone.tab
ERROR: Unable to create GUI. Exiting
Any ideas what I should fix?
hi,
can you share your DietPi version? Are you on latest 7.5? can you share as well following.
echo $G_DISTRO_NAME $G_RASPBIAN
Dietpi version is 7.5.2.
root@DietPi:~# echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 0
After some fiddling around mainly with display settings and memory split now Kodi starts but with the following errors:
root@DietPi:~# startkodi
failed to open zone.tab
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
MichaIng
could you have a look pls
Could you show which Kodi version/package is installed?
apt policy kodi
apt policy kodi-bin
Okay, on the ARMv7 image, the Debian Kodi package is pulled, while we have an own RPi accelerated one. We changed it so that the ARMv7 image is pulls our package as well: https://github.com/MichaIng/DietPi/pull/4719
Sadly, while testing, we recognised that RPi just a few hours ago released new libraspberrypi packages with a breaking change, so that our Kodi build does not find the contained libraries anymore (those are now on a different location) 
. I’ll recompile it and let you know once done.
Indeed the Debian Kodi is installed:
root@DietPi:~# apt policy kodi
kodi:
Installed: 2:19.1+dfsg2-2
Candidate: 2:19.1+dfsg2-2
Version table:
*** 2:19.1+dfsg2-2 500
500 https://deb.debian.org/debian bullseye/main armhf Packages
100 /var/lib/dpkg/status
root@DietPi:~# apt policy kodi-bin
kodi-bin:
Installed: 2:19.1+dfsg2-2
Candidate: 2:19.1+dfsg2-2
Version table:
*** 2:19.1+dfsg2-2 500
500 https://deb.debian.org/debian bullseye/main armhf Packages
100 /var/lib/dpkg/status
Today there were some updates that dietpi invited me to apt upgrade:
apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
libatomic1 libepoxy0
The following packages will be upgraded:
ffmpeg libavcodec58 libavdevice58 libavfilter7 libavformat58 libavresample4
libavutil56 libc-bin libc-l10n libc6 libegl-mesa0 libgbm1 libgl1-mesa-dri
libglapi-mesa libglx-mesa0 libpostproc55 libraspberrypi-bin libraspberrypi0
libswresample3 libswscale5 locales
21 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 29.8 MB of archives.
After this operation, 28.0 MB of additional disk space will be used.
After those library updates Kodi will not start at all, as Joulinar correctly noticed in GitHub:
root@DietPi:~# startkodi
/usr/lib/arm-linux-gnueabihf/kodi/kodi.bin: error while loading shared libraries: libmmal_core.so: cannot open shared object file: No such file or directory
yes because RPi devs released a new version of libraspberrypi0 package. This update changed location of shared libraries dramatically and thinks like kodi would need to be compiled again against this new directory structure. This is valid for our own kodi package (I’m using) and I guess for the official kodi package (you are using).
For the time being, there is nothing we can do except waiting on a new kodi version becoming available. At least for our package MichaIng will work on this. But compiling the package is taking time.
Try this one:
cd /tmp
curl -sSfLO https://dietpi.com/downloads/binaries/bullseye/kodi_armv7l.deb
apt install ./kodi_armv7l.deb libraspberrypi0
rm kodi_armv7l.deb
I have tried running above without any success. Both, first with already installed Kodi from dietpi-software center and with the code above, and first Kodi uninstalled from dietpi-software.
dietpi@DietPi:~$ apt policy kodi
kodi:
Installed: 3:19.1-dietpi3
Candidate: 3:19.1-dietpi3
Version table:
*** 3:19.1-dietpi3 100
100 /var/lib/dpkg/status
dietpi@DietPi:~$ kodi
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
The command to start Kodi would be
startkodi
Still the same error
dietpi@DietPi:~$ startkodi
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
pls can you provide some more information on your system
Required Information
dietpi@DietPi:~$ cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=6
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='not applicable'
G_LIVE_PATCH_STATUS[1]='applied'
G_LIVE_PATCH_STATUS[2]='applied'
G_LIVE_PATCH_STATUS[3]='applied'
G_LIVE_PATCH_STATUS[4]='not applicable'
dietpi@DietPi:~$ echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 1
dietpi@DietPi:~$ uname -a
Linux DietPi 5.10.63-v7l+ #1457 SMP Tue Sep 28 11:26:14 BST 2021 armv7l GNU/Linux
Running on a RPI4. I manually upgraded from DietPi Buster to Bullseye following the blog entry.
Can you please try to reinstall Kodi, to assure that also the fKMS driver is used etc:
dietpi-software reinstall 31
reboot
I also see the libva error, but Kodi starts fine despite this.
Still nothing. The Kodi is running (both in ps x) and it makes its startup sound, but nothing on the screen. I have set DietPi to autostart directly to Kodi (user dietpi) from dietpi-config, however it is just showing the terminal with the libra error. Could it be needed to run through a DE?
I will try a fresh install on a new card tomorrow. Was hoping to avoid it through upgrading instead, and so far everything else is working fine.
could you try using user root to start kodi on autostart.
Like if it was running on a different screen 
.
Hello,
This is a guess on my part but could the problem they are having be something to do with the Pi4 having two HDMI outputs? I ask this only because on my Pi3 I did a complete fresh install for Bullseye including installing Kodi and I get the same error but Kodi does load and displays its user interface on the TV.
I am having my own problem though of not being able to navigate using my TV controller anymore since the fresh install of Bullseye and Kodi. This is probably down to something I am doing wrong like a setting that needs changing but at the moment I am lost on how to fix this.
Thank you for DietPi I have been using it for a few years now on a Pi3 and Pi4 it is my goto.
ISquishWorms
Indeed this seems to be the issue, same as here: https://dietpi.com/forum/t/rpi-4-8gb-cant-start-kodi/5729/18
Probably for some reason the second unused screen/HDMI port is used when starting Kodi via GBM from console. Probably it works when actively disabling the second HDMI port, or there is another way to force it using the 1st/foreground screen/port, despite a second one is available.