New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kodi fails to start; RPi4; Debian Buster 10.10; aarch64; beta 7.4.1 #4581
Comments
Hi, Pls try to start Kodi as user |
Sure :)
No much luck though: Bug report 674c1438-5300-4d46-92fa-adfd1a274071 |
Pls try |
On RPi, the Kodi build does not support and use the X server. RPi 4 is using the KMS/GBM instead, previous RPi models DispmanX, if I'm not mistaken. As long as the user is in sudo usermod -aG video,render dietpi
kodi --standalone |
Tried a fresh install starting from 7.0.2 with the intention to test these suggestions (thanks!). Looks like it has become stuck after DNS resolution problems I think I saw somewhere else:
Cannot test with it stuck at this point. |
Do you use PiHole or any other AdBlocker? You have issues to resolve global Debian apt repository |
Hmmm, might be my router DNS settings. |
Well you would need to check why you are not able to resolve the global Debian apt repository. Maybe you can give a static IP to the RPi using a different DNS server |
Finally appeared to get through all the DNS failures and so on. Only for this to happen, unfortunately:
Bug report: 89b7423a-2c44-4621-b511-8e61f105d106
Bug report: 89b7423a-2c44-4621-b511-8e61f105d106 |
Can you share the crash log |
OK, here's a strange one. I re-ran I used I rebooted. Kodi is running! |
Sure. Now that I changed SSH servers from Dropbear to OpenSSH, I can SFTP it to this device and ... |
Usually there is no need to switch SSH server. You could have installed OpenSSH client (ID 0) and use SCP 😉 |
Usually there is no need to switch SSH server. You could have installed
OpenSSH client (ID 0) and use SCP 😉
prefer OpenSSH
|
Usually there is no need to switch SSH server. You could have installed
OpenSSH client (ID 0) and use SCP 😉
Unfortunately, the Kodi version, `17.6 Krypton`, is quite old.
FYI DietPi self upgraded from `7.0.2` to `7.3.2`
|
Kodi is installed from Debian repository as you use 64bit. On 32bit, the Raspbian repository is used and it should ship version 18 or something. Not really something related to DietPi. Option would be to switch to Bullseye, use Buster backports or compile it yourself. |
Thanks for the feedback. 64bit is still so very messy in the SBC world. Oh well. It's not so much the age of Kodi itself that is the limitation though. A lack of support for hardware decoding is probably as critical as the version and AFAIK not one in the same thing. Let me know if I can help debug the original issue in this thread. |
Ah sorry, I also completely forgot about the aarch64 thing. Yes in that case, there is not yet a Raspberry Pi build but instead the Debian version (old and X11 based) is installed. Our Kodi start script, used by the autostart option as well, knows that and starts Kodi accordingly via xinit: https://github.com/MichaIng/DietPi/blob/master/dietpi/misc/start_kodi And your first attempt Btw, there is a much newer Kodi available from backports: https://packages.debian.org/buster-backports/kodi apt install -t buster-backports kodi
xinit /usr/bin/kodi --standalone
I was thinking already for a while whether we should install a config on DietPi which lifts the backports priority so that everything is pulled from backports (where available) in the first place. This also includes newer kernel versions on x86_64 systems etc. The only concern was that Raspbian has no backports, so we cannot reliably know which package/software versions are installed only based on the distro version, but need to differentiate between Raspbian and Debian then as well 🤔. |
@Michalng: brilliant summary. Thanks for that detailed effort. I will try to get into the ins and outs of it soon. Cannot continue with the current Kodi Hoping your suggestions will help because the *arr and Jackett installations went like a breeze. If they are that easy to update, incredible! BTW, first glance at the new documentation project is absolutely beautiful compared to the shunted-into-phpBB and eye-straining lime/black style documentation. Big time kudos to all involved. Would like to help at some stage. |
Yes indeed via X11 by default it is not accelerated. But probably when using the KMS DDX it will be 🤔. Try the following: /boot/dietpi/func/dietpi-set_hardware rpi-opengl vc4-fkms-v3d or the full KMS driver: /boot/dietpi/func/dietpi-set_hardware rpi-opengl vc4-kms-v3d-pi4 Also, which desktop do you use? When any X compositing is done, that, that may slow down Kodi on X. On LXDE there should be no composition manager installed, but other desktops have them included in their window manager. |
Not at all. Honestly, happy to use 32 bit as I only have a 4GB RPi4 ... it was just hard to opt for 32 instinctively as it, well, felt backwards ... even though I knew this to not be so much the case is the SBC world.
Ah, I see what you mean there.
Honestly, I just saw
Thanks! Wow, I would like to do that but this DNS malarkey has got me miffed. Just cannot get reliable DNS! Even with my router pointing to
Hmmm, there's a bit too much granularity here, I reckon. Maybe it's just me though. Best not to complain :)
That does sound like a ballache. Seems abnormal that Rasbian doesn't do backports. Debs, Ubuntu, Mint? All do them, don't they? |
No luck I'm afraid. Still running |
No luck here either. So seems like I could start again. What version of Kodi is available for DietPi 32 bit? Does the Kodi version in DietPi 32 bit support hardware acceleration for the RPi4? |
DietPi 32bit on RPi is using Raspberry OS 32bit and the Raspberry repository. There is no special DietPi version as DietPi is not an own OS. It's basically a diet Raspberry OS with some magic scripts.
|
Yes, on Raspbian (Raspberry Pi OS 32-bit and hence our 32-bit RPi image) the Kodi build is a special RPi build with hardware acceleration. |
I do like as many magic scripts as I can use, and the good people of DietPi land are goodly enough to write and maintain! :)
Hmmm, slightly strange version numbe. Equivalent to Kodi 18.7 perhaps? Either way, 32 bit seems the way to go. |
Sounds like it's 32 bit all the way :) |
Its basically Kodi and Chromium where 64-bit builds with RPi GPU acceleration are missing. You can monitor it yourself:
As fast as |
Fair enough for sure. Am currently looking into your automated install support :) |
Wow, 32 bit not going much better. Got all excited about doing the dietpi.txt automated installation. Nope. Earlier, my Dietpi.txt automation did a lot but stopped ahead of installing the bulk of the software packages. Naturally DNS is fine now. Just other problems of course appearing. |
Think I misseed this initially but just trying it now, no luck:
Maybe do I need to add a |
Actually you are on 32bit or 64bit? |
That's 32bit, isn't it? |
Yes, 32bit did not have a buster-backports |
OK, well I'm getting a showstopper bug - Pulse CEC adaptor loading notification appears as normal but no CEC - with the current 32bit version anyway, so it's back to LibreELEC for something functional :( |
There was an issue with the Raspberry OS kernel. Could you check if you can update by running Reference #4613 |
Can do, but for the moment I am trying an The 32 bit raspbian Kodi binary has poor decoding of x265 / HEVC in that it renders with hardware acceleration but too many videos I could play fine with LibreELEC 9.2.7 get picture break up that creates sync issues and sometimes freezes Kodi. |
It's a bit sad that the RPi build of Kodi was not updated for more than a year now: https://archive.raspberrypi.org/debian/pool/main/k/kodi/?C=M;O=D |
That does seem odd, however, might correlate with why OSMC is yet to publish support for RPi4. RASFo employed a video driver guy some time ago. Wonder if he's still working with them.
Kodi 19 Matrix involves the move to Python3 and elimination of proprietary rendering methods, so that may be a factor in why the Raspbian 32 Bit Kodi build is Kodi 18.7. After all, LibreELEC themselves are yet to release version 10, the Kodi 19 Matrix version, and openly states Raspberry Pi 4 will only get a:
Although LibreELEC 10.0 BETA5, actually based on Kodi Matrix 19.1, was released on June 27th.
Agreed, efforts would be best coordinated where human egos and so forth can handle it. At least LibreELEC and 'Team Kodi' seem to work together:
|
LibreELEC has a
Tried a
... will that instruct DietPi to use the Is a reboot required? |
apt purge xserver-xorg-video-fbdev The X server with KMS has some basic GPU acceleration, but especially for video decoding Kodi needs to be built to use the RPi GPU directly. /boot/dietpi/func/dietpi-set_hardware rpi-opengl vc4-fkms-v3d This enables the driver (via device tree overlay) and installs related libraries. Like with every change to |
Thanks for your great support, Michal.
It looks like my options are exhausted.
OSMC night have been the best choice, no RPi4 support.
LibreELEC and dockSTARTer to install downloading apps, but BusyBox doesn't support git, which dockSTARTer requires. Meanwhile, the DeskPi Pro doesn't support LibreELEC so no proper power down, fan control or functioning front USB ports.
DietPi does everything, though I've not had it running with DeskPi Pro support just yet. Everything it seems except keep up with LibreELEC / Kodi ... which as you've diligently explained is probably not feasible due to the dedication required to reach LibreELEC's Kodi housing refinement.
Thank you for all your exceptional support. maybe I'll come back to this nightmare if I ever have more capability.
|
Okay, I'll close the issue for now, as all questions should be answered. Feel free to reopen if required. |
PSU: DeskPi Pro
SanDisk USB stick
The text was updated successfully, but these errors were encountered: