GeeXboX

[Cubox-i 4] XBMC/Kodi fails after opkg upgrade

September 30th, 2015

Home › Forums › GeeXboX on ARM SoCs › [Cubox-i 4] XBMC/Kodi fails after opkg upgrade

This topic contains 3 replies, has 2 voices, and was last updated by Warped Rudi 6 days, 17 hours ago.

Viewing 4 posts – 1 through 4 (of 4 total)
  • Author
    Posts
  • #10031

    Amy_Berlin
    Member

    After a fresh install of Geexbox on my Cubox-i 4 (after which I was presented with a working XBMC surface) I attempted an upgrade to get the packages up to date:
    root@geexbox:/# opkg update
    root@geexbox:/# opkg upgrade
    After the following reboot, XBMC (or Kodi, as the case may be) refused to start:

    root@geexbox:/# systemctl status xbmc
    xbmc.service - XBMC Media Center
       Loaded: loaded (/usr/lib/systemd/system/xbmc.service; disabled)
       Active: failed (Result: start-limit) since Wed 2015-09-30 08:32:44 BST; 28min ago
      Process: 516 ExecStart=/usr/bin/runxbmc --standalone -fs -l /var/run/lirc/lircd (code=exited, status=1/FAILURE)
     Main PID: 516 (code=exited, status=1/FAILURE)
    Sep 30 08:32:44 geexbox systemd[1]: Unit xbmc.service entered failed state.
    Sep 30 08:32:44 geexbox systemd[1]: xbmc.service start request repeated too quickly, refusing to start.
    Sep 30 08:32:44 geexbox systemd[1]: Failed to start XBMC Media Center.
    Sep 30 08:32:44 geexbox systemd[1]: Unit xbmc.service entered failed state.
    root@geexbox:/# xbmc
    sh: glxinfo: not found
    XBMC needs hardware accelerated OpenGL rendering.
    Install an appropriate graphics driver.
    Please consult XBMC Wiki for supported hardware
    http://wiki.xbmc.org/?title=Supported_hardware

    Apparently, this is a driver issue. Can anybody tell me how to get glxinfo back?

    Kind regards,

    Amy

    #10032

    Warped Rudi
    Moderator

    You can’t get glxinfo back because you never had it before. Normally you do not execute ‘xbmc’ from a command prompt. The correct way to start it is ‘systemctl start xbmc’. You might want to check if all needed libraries are present by running: ‘ldd /usr/lib/xbmc/xbmc.bin’.

    Also I’m wondering which image you used for your fresh install. The snapshot images from here as well as the ones installed by Ignition do not need much (if any at all) updates via opkg.

    #10033

    Amy_Berlin
    Member

    Dear Rudi,

    thanks for your reply – I used the image provided by SolidRun. So is it generally inadvisable to keep the Geexbox system up to date by regularly updating/upgrading packages?

    Regards,
    Amy

    #10035

    Warped Rudi
    Moderator

    Hi Amy,

    The download link on http://solid-run.com/downloads/ points to a copy of a really ancient image on their own server. I have to ping them to remove it.

    As for opkg: We try to keep it updatable, but there are cases where it just doesn’t work. I.O.W, it doesn’t always figure out all dependencies correctly. Especially in cases where a package A depends on a package B which depends a package C that got a major, incompatible update. This can cause failures like the one you are experiencing right now.

    Also we have currenty not yet decided if there will be an update path from XBMC (13) to Kodi (15). At the moment we have two distinct images:

    http://download.geexbox.org/snapshots/geexbox-kodi-imx6-cuboxi/
    http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/

    So if you start from scratch anyway, I’d suggest to go with Kodi (Isengard 15.2-rc2).

    Edit: The link on the SolidRun page was updated.

Viewing 4 posts – 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Comments are closed.