Kodi windows 10 unable to create gui

2017-11-13, 13:57
(This post was last modified: 2017-11-13, 15:25 by Klojum.)

Klojum

Team-Kodi Member
Posts: 13,609

nickr

Team-Kodi Member
Posts: 19,982

If I have helped you or increased your knowledge, click the ‘thumbs up’ button to give thanks (People with less than 20 posts won’t see the «thumbs up» button.)

(2017-11-19, 17:09)RENATOLORETO Wrote: When I try to obtain updated video drivers systems says thzat I have the lates version of drivers.

maybe your  version of drivers is not comfortable to the kodi？

eat will be nice
but here~

nickr

Team-Kodi Member
Posts: 19,982

If I have helped you or increased your knowledge, click the ‘thumbs up’ button to give thanks (People with less than 20 posts won’t see the «thumbs up» button.)

tom886

Junior Member
Posts: 25

RPi 3B+, freshly installed Raspbian Buster minimal/lite.

When I try to start kodi from console, I get error: «unable to start gui, exiting»

Googling, I found it’s probably the missing xserver. So, what is the minimal package needed for this?

Also, shouldn’t it be a dependency for kodi package?

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Hi,

I have the same issue. Raspberry Pi 3 B+.
From console, the launching Kodi generates an error: ERROR: Unable to create GUI. Exiting
From X, it runs but taks almost 97%CPU and is very slow.

Could you explain more this topic about opensource video drivers VC4 FKMS or VC4 KMS ?
Will it allow a launch from console ?

Cheers,
Orlando

I saw some posts.
I tried some stuff.
Is there a command line to know if VC4 FKMS or VC4 KMS are activated ?

Thanks.

madjo1983 wrote: ↑

Fri Jul 05, 2019 4:56 pm

I saw some posts.
I tried some stuff.
Is there a command line to know if VC4 FKMS or VC4 KMS are activated ?

Thanks.

sudo nano /boot/config.txt

Should appear:
dtoverlay=vc4-kms-v3d

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Is this a better idea to install stretch raspian version instead and use 18.2 Kodi version with usual parameters ?

madjo1983 wrote: ↑

Sat Jul 06, 2019 10:44 am

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Is this a better idea to install stretch raspian version instead and use 18.2 Kodi version with usual parameters ?

Yes.

Hi,

Just got a new RPI4 ARMv8 unit and installed Arch Arm on it with the objective of replacing my old ARMv7 Kodi box with this one, yet I am unable to get Kodi started.
When I enable and start up kodi.service, the process exits with the message:

Code: Select all

ERROR: Unable to create GUI. Exiting

Interesting FATAL point in the kodi.log regarding the matter is:

Code: Select all

2019-10-04 18:23:32.310 T:2977099792   FATAL: CApplication::Create: Unable to init windowing system

Full kodi.log:

https://pastebin.com/yFDekry8

I am using the kodi-rbp4 18.4-2 package. If I switch to kodi-rbp3 or kodi-rbp packages, then it seems that the GUI is somewhat started as the screen goes completely black like it is starting X, but nothing further — not even sounds when trying to navigate around.

The only logs from kodi.service from journal are:

Code: Select all

Oct 04 22:17:29 archpi-v2 systemd[1]: Started Kodi standalone (GBM).
Oct 04 22:17:29 archpi-v2 systemd[312]: pam_unix(login:session): session opened for user kodi by (uid=0)
Oct 04 22:17:34 archpi-v2 systemd[1]: kodi.service: Succeeded.


Full /boot/config.txt is:

Code: Select all

# See /boot/overlays/README for all available options

gpu_mem=320
dtoverlay=vc4-fkms-v3d
dtparam=audio=on

initramfs initramfs-linux.img followkernel

The driver used is xf86-video-fbdev 0.5.0-1… I tried the alarm/xf86-video-fbturbo-git also but the results are the same.
Also checked that the kodi user’s home is set as /var/lib/kodi as I read that it could cause similar issues.

Code: Select all

kodi:x:975:975::/var/lib/kodi:/usr/bin/nologin

I am running out of ideas on what to check as my ARMv7 seems to be running on a similar setup without any issues. Anyone else managed to turn RPI4 ARMv8 into a simple Kodi box?
Any help and tips are very highly appreciated! (wiki links are welcome if relevant )

EDIT: changed the pastebin url for logs as they were from an incorrect service start attempt

2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://envhome/

is mapped to: /root
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://home/

is mapped to: /root/.kodi
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://temp/

is mapped to: /root/.kodi/temp
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://logpath/

is mapped to: /root/.kodi/temp

Bad bad bad. It seems you are trying to run as root. Using the kodi.service via systemctl will not do this so I don’t know how you’re starting it. Also, gbm does not require drivers so you can uninstall the xf86 stuff.

Thank you for the quick reply!
It seems that I made a mistake with copying the logs from an attempt when I was indeed trying to start it up as root, my apologies. Here are the latest logs when systemd starts the application during a fresh reboot:

https://pastebin.com/yFDekry8

(ignore the time-jumping — seems that the system starts off with local time but then jumps to UTC — hence the strange jump in time in the beginning of logs)
Thanks for the xf86 tip, removed them.

I’m not sure what you have going on… it should just work. Did you attempt to migrate any old kodi profiles to this? Recommend you rename your /var/lib/kodi to /var/lib/kodi-old and then:

Code: Select all

# mkdir /var/lib/kodi
# chown kodi:kodi /var/lib/kodi

Then start the systemd service… Are you using HDMI0 or HDMI1? I seems to recall needing to use HDMI0 which is right next to the power supply.

Thanks for the help! Tried the folder replacement but no avail.
Did not try to migrate profiles, want a fresh start.
I am using HDMI-0 as I heard that sometimes HDMI-1 does not supply enough power and yeah, there is no image at all with the HDMI-1 connection, not even the console.

The strange thing is that with kodi-rbp package, all the extensions and resolutions load up normally:

https://pastebin.com/PkT5sTFZ

But the screen remains simply black.

EDIT:
Just for the completion’s sake, I did a fresh Arch arm install on the RPI4 unit and the only additional packets I installed (with their dependencies) were:

Code: Select all

linux-raspberrypi4-headers base-devel kodi-rbp4 wget omxplayer-git xorg-xrefresh xorg-xset

This is how the old RPI3 worked (with its respective rbp3 packages) with Kodi, but not the new RPI4.

Yes, I am 100% sure that it is the RPI4 which I purchased just yesterday, says it also on the board itself + the new layout and connectors in comparison to the old RPI3 models.
Thanks, I shall post to Kodi forums then as well and if I get anywhere, I will update this topic also.

https://forum.kodi.tv/showthread.php?tid=348014

I got the picture on!
After investigating a bit about the overlay options for config.txt, I had to add the cma-256 to vc4-fkms-v3d dtoverlay so that the whole line would read out like this:

Code: Select all

dtoverlay=vc4-fkms-v3d,cma-265

Have not yet tested out playback of any video files, but at least the interface is now operational and I can browse through Kodi’s menus.

EDIT:
Yep, playback is fine, all is working exactly as expected. Thank you so much graysky for helping out on this! Perhaps this cma thingy could also be added to the kodi-rbp4 package notes during installation that in case the normal method does not work, it is worth a shot to try it with this parameter?

That’s fucked up… mine works without that at all… 2 and 4 G versions if that matters.

Code: Select all

# See /boot/overlays/README for all available options
initramfs initramfs-linux.img followkernel

# turn tv on
# write out edid file with
# sudo /opt/vc/bin/tvservice -d /boot/edid.dat
# setting below will load it on boot

gpu_mem=406
hdmi_edid_file=1
dtparam=audio=on
dtoverlay=vc4-fkms-v3d
hdmi_group=2
hdmi_mode=69

Thanks!
Maybe not a great idea to bump the thread with a simple continuation of a conversation, but I also noticed one additional strange thing — namely, I seem to have to keep one of the following installed:

Code: Select all

xf86-video-fbturbo-git
xf86-video-fbdev

If neither of the two is installed, then Kodi simply boots to black screen and nothing further. Kodi service in systemd shows all good and the service is started. I do not use any X nor do I have xorg.conf set up. Go figure.

At least the box is now up — reaching the heat limit pretty frequently as well. Need to modify the case with a tiny fan probably.