MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.89k stars 498 forks source link

Odroid C2 / Kodi crash #1698

Closed dnalor closed 6 years ago

dnalor commented 6 years ago

Creating a bug report/issue:

Required Information:

Additional Information (if applicable):

Expected behaviour:

Kodi starts

Actual behaviour:

Kodi crashes

Steps to reproduce:

start Kodi

Did you submit a dietpi-bugreport?

No

Extra details:

Symptoms: Kodi crashes immediately after starting it (both with startkodi and automatic start) Issue looks similar to #399

Error message:

/usr/local/bin/kodi: 18: /usr/local/bin/kodi: pulseaudio: not found
/usr/local/lib/kodi/kodi-xrandr: Failed to get size of gamma for output default
*** Error in `/usr/local/lib/kodi/kodi.bin': munmap_chunk(): invalid pointer: 0x0000000002b78a28 ***

General information:

Logs

k-plan commented 6 years ago

@dnalor

General information:

  • New installation (DietPi v6.0, Linux DietPi 3.14.79+), up to date according to DietPi-Update

Can you please provide output of:

root@Odroid-C2-Stretch:~# cat /etc/os-release

dnalor commented 6 years ago

@k-plan

root@DietPi:~#  cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Fourdee commented 6 years ago

@dnalor

Thanks for the report, we'll try to replicate.

Fourdee commented 6 years ago

Unable to replicate on fresh install. Runs fine in local testing.

/usr/local/bin/kodi: 18: /usr/local/bin/kodi: pulseaudio: not found

Is fine, reverts to ALSA which is preferred in terms of audio quality and lightweight install.

Kodi is the only additional package installed

Did you install Kodi from dietpi-software? Please confirm kodi-odroid installed: dpkg -l | grep kodi

DietPi uses 720p by default, try changing to 1080p in dietpi-config, then retest.

dnalor commented 6 years ago

@Fourdee

Did you install Kodi from dietpi-software? Please confirm kodi-odroid installed: dpkg -l | grep kodi

root@DietPi:~#  dpkg -l|grep kodi
ii  kodi-odroid                    16.1-6+deb8                             arm64        Kodi - award-winning free and open source (GPL) software media player and entertainment hub (ODROID build)

DietPi uses 720p by default, try changing to 1080p in dietpi-config, then retest.

Tried both, no difference (C2 is connected to a computer monitor) Here's the relevant xorg.log excerpt:

[    35.615] (WW) Falling back to old probe method for fbturbo
[    35.615] (II) Loading sub module "fbdevhw"
[    35.615] (II) LoadModule: "fbdevhw"
[    35.615] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    35.616] (II) Module fbdevhw: vendor="X.Org Foundation"
[    35.616]    compiled for 1.16.4, module version = 0.0.2
[    35.616]    ABI class: X.Org Video Driver, version 18.0
[    35.617] (II) FBTURBO(0): using /dev/fb0
[    35.617] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    35.617] (II) FBTURBO(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    35.617] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[    35.617] (==) FBTURBO(0): RGB weight 888
[    35.617] (==) FBTURBO(0): Default visual is TrueColor
[    35.617] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[    35.617] (II) FBTURBO(0): hardware: OSD FB (video memory: 98304kB)
[    35.617] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[    35.617] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[    35.617] (II) FBTURBO(0): processor: ARM Cortex-A53
[    35.617] (II) FBTURBO(0): checking modes against framebuffer device...
[    35.617] (II) FBTURBO(0): checking modes against monitor...
[    35.617] (--) FBTURBO(0): Virtual size is 1920x1080 (pitch 1920)
[    35.617] (**) FBTURBO(0):  Built-in mode "current"
[    35.617] (==) FBTURBO(0): DPI set to (96, 96)
[    35.617] (II) Loading sub module "fb"
[    35.617] (II) LoadModule: "fb"
[    35.618] (II) Loading /usr/lib/xorg/modules/libfb.so
[    35.620] (II) Module fb: vendor="X.Org Foundation"
[    35.620]    compiled for 1.16.4, module version = 1.0.0
[    35.620]    ABI class: X.Org ANSI C Emulation, version 0.4
[    35.620] (==) Depth 24 pixmap format is 32 bpp
[    35.641] (II) FBTURBO(0): using backing store heuristics
[    35.641] (II) FBTURBO(0): enabled VFP/NEON optimizations
[    35.641] (==) FBTURBO(0): Backing store enabled
[    35.643] (==) FBTURBO(0): DPMS enabled
[    35.656] (II) Loading sub module "dri2"
[    35.656] (II) LoadModule: "dri2"
[    35.656] (II) Module "dri2" already built-in
[    35.657] (II) FBTURBO(0): display controller hardware overlays are unsupported on meson8/gxbb.
[    35.657] (II) FBTURBO(0): Wait on SwapBuffers? enabled
[    35.657] (II) FBTURBO(0): [DRI2] Setup complete
[    35.657] (II) FBTURBO(0): [DRI2]   DRI driver: lima
[    35.657] (II) FBTURBO(0): using DRI2 integration for Mali GPU (UMP buffers)
[    35.657] (II) FBTURBO(0): Mali binary drivers can only accelerate EGL/GLES
[    35.657] (II) FBTURBO(0): so AIGLX/GLX is expected to fail or fallback to software
[    35.657] (==) RandR enabled
[    35.676] (II) SELinux: Disabled on system
[    35.679] (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/lima_dri.so failed (/usr/lib/aarch64-linux-gnu/dri/lima_dri.so: cannot open shared object file$
[    35.679] (EE) AIGLX: reverting to software rendering
[    35.710] (II) AIGLX: Loaded and initialized swrast
[    35.710] (II) GLX: Initialized DRISWRAST GL provider for screen 0
ghost commented 6 years ago

@dnalor Tried to open an issue at the Kodi-Devs? It seems like it is either a problem of KODI itself or your kernel which are you using isn't supported.

See lines where it tries to load modules... and fails somehow.... that's what i see so far.

On several pages, they suggest to use LibreELEC for KODI on C2 (e.g. https://kodi.wiki/view/ODROID)

@Fourdee Nothing against DietPi, as it fits almost everything to the user's xp. But myself think at this point sometimes ppl have to use another solution and not holding on something which can't be easy solved.

Fourdee commented 6 years ago

Appears fine, same results here running GLES under Mali:

[    35.657] (II) FBTURBO(0): using DRI2 integration for Mali GPU (UMP buffers)
[    35.657] (II) FBTURBO(0): Mali binary drivers can only accelerate EGL/GLES
[    35.657] (II) FBTURBO(0): so AIGLX/GLX is expected to fail or fallback to software
Fourdee commented 6 years ago

Marking as closed due to: