[fritsch]

Tell us :-)

[aesthetiker]

Update to the latest image my box didnt boot up anymore. Only BootLogo and nothing happens.

[fritsch]

No idea - what "the latest" image is ... gather the logfiles via ssh, please.

[aesthetiker]

Sorry OpenELEC-Generic.x86_64-6.0-devel-20151113133714-r21569-g59302ad.tar this one. No connection via ssh is possible network interface didnt respond to ping or anything else. What is the fastest process to recover the box? Openelec backup is available.

[fritsch]

Flash the img and then restore the backup.

[jjslegacy]

As I have said previously I only watch movies on my chromebox 95% of them being full rip blurays (mkv) but latest version from 13th looks good to me. Started and stopped a few movies and jumped around a bit. No problems that I could detect. After a while I did have my stupid refresh rate scramble screen but as said that doesn't appear to be anything kodi related. One of these days I will catch it with a debug just in case but I think it's more projector related

Looks good from my side!

[fab67]

Sorry OpenELEC-Generic.x86_64-6.0-devel-20151113133714-r21569-g59302ad.tar this one. No connection via ssh is possible network interface didnt respond to ping or anything else. What is the fastest process to recover the box? Openelec backup is available.

Same here. freeze while booting, no ssh ...
I need to go back to 10 november version.

[psysfaction]

Sorry OpenELEC-Generic.x86_64-6.0-devel-20151113133714-r21569-g59302ad.tar this one. No connection via ssh is possible network interface didnt respond to ping or anything else. What is the fastest process to recover the box? Openelec backup is available.

Same here. freeze while booting, no ssh ...
I need to go back to 10 november version.

This also happened to me with the latest Isengard build: OpenELEC-Generic.x86_64-6.0.98-fritsch.tar
Running on AsRock Beebox.
I had to go back to the 6.0.95 version.
I couldn't figure out why it could not boot. It just stuck while showing the Kodi logo...

[Milhouse]

I couldn't figure out why it could not boot. It just stuck while showing the Kodi logo...

kodi.log might have told you something.

[Mylo75]

Sorry OpenELEC-Generic.x86_64-6.0-devel-20151113133714-r21569-g59302ad.tar this one. No connection via ssh is possible network interface didnt respond to ping or anything else. What is the fastest process to recover the box? Openelec backup is available.

Same here. freeze while booting, no ssh ...
I need to go back to 10 november version.

This also happened to me with the latest Isengard build: OpenELEC-Generic.x86_64-6.0.98-fritsch.tar
Running on AsRock Beebox.
I had to go back to the 6.0.95 version.
I couldn't figure out why it could not boot. It just stuck while showing the Kodi logo...

Same here OpenELEC-Generic.x86_64-6.0.98-fritsch.tar would not boot for me.

OpenELEC-Generic.x86_64-6.0-devel-20151113133714-r21569-g59302ad boots and seems to work well so far, although I haven't done much testing so far.

I am using n3150 beebox

[Milhouse]

Same here OpenELEC-Generic.x86_64-6.0.98-fritsch.tar would not boot for me.

If you're getting the *Kodi* splash like psysfaction then your system HAS booted - it's only Kodi that's not starting correctly, so you can ssh in and grab the log. If you add

Code:

<loglevel hide="false">1</loglevel>

to advancedsettings.xml then you can enable debug logging for a more detailed kodi.log which may reveal why Kodi isn't starting.

[Mylo75]

Same here OpenELEC-Generic.x86_64-6.0.98-fritsch.tar would not boot for me.

If you're getting the *Kodi* splash like psysfaction then your system HAS booted - it's only Kodi that's not starting correctly, so you can ssh in and grab the log. If you add

Code:

<loglevel hide="false">1</loglevel>

to advancedsettings.xml then you can enable debug logging for a more detailed kodi.log which may reveal why Kodi isn't starting.

Sorry should have said I'm not getting to the Kodi splash screen, just a black screen. Also device not showing up on network at that stage.

[psysfaction]

Same here OpenELEC-Generic.x86_64-6.0.98-fritsch.tar would not boot for me.

If you're getting the *Kodi* splash like psysfaction then your system HAS booted - it's only Kodi that's not starting correctly, so you can ssh in and grab the log. If you add

Code:

<loglevel hide="false">1</loglevel>

to advancedsettings.xml then you can enable debug logging for a more detailed kodi.log which may reveal why Kodi isn't starting.

I can try to do this again tomorrow and see if I can ssh it.
It'l already two in the morning here :-)

[Ney]

Fritch:
I am aware of "no isengard support" . but could it be that the 6.0-fritch build somehow doesnt have the intel legacy turbo fixes? I am starting to get freezes that reminds me of the old turbo freezes, which sucks are are terrible to debug, it's just a stab in the dark and they are probably included, I am just getting a bit annoyed with the old BYT.

[pikachu320]

I'm using the fritch build of openelec for my beebox*, and I have (apparently randomly) crashed of Kodi have while playing video files.
In the crashlog, around the time of the crash, I see:

Code:

WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED

but nothing more interesting. I don't know how to be more verbose than debug.

Here is the log in more details around that specific time: http://xbmclogs.com/pbvselmbd

*I'm running on OpenELEC (unofficial) - Version: 6.0.96-fritsch, kernel: Linux x86 64-bit version 4.3.0

BTW I'm also getting these errors in the logs:

• Code:

  10:07:51 T:140185755109248   ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
  I don't know how to fix this, but it looks like something that can be added on the base image.
  
• Code:

  10:38:22 T:140185755109248   ERROR: GetDirectory - Error getting /usr/share/kodi/sounds/
10:38:22 T:140185755109248   ERROR: GetDirectory - Error getting special://xbmc/sounds/
  For this one, it should be a simple matter of updating the base image and creating a sounds folder in /usr/share/kodi. fritsch, you want to release a bugfix release on this one? It happens when ppl switch to other skins than the default one. I have this issue with multiple skins.