Login at Kodi Home

pettergulbra · 2015-11-20, 15:40

I think I will try both, starting with the update.
But have to wait until tomorrow, have some children on visit to day. And they want to see an movie I think.
Best not to brake it. :-)

Have to read a little bit how to try OE live session. :-)

Matt Devo · 2015-11-20, 19:17

(2015-11-20, 15:40)pettergulbra Wrote: Have to read a little bit how to try OE live session. :-)

it was changed with v6.0: boot the install media, then at the 'boot:' prompt (which shows for ~5s) type 'live' and press enter

Soli · 2015-11-20, 20:35

Hey Matt, a little OT. I remember vaguely that you use the ps3 remote too. I was just wondering if the ps3 remote sleeps properly when you are suspending the machine?

I usually have a timeout of 90 seconds, but what happens with this timeout if the machine is sleeping?

Btw your wakeup/fan-fix doesn't work in Kodibuntu (kernel 4.1.x). Not a big deal for me, I'll survive the 10 odd seconds with the fan spinning at high speed.

BoxFreak · 2015-11-20, 20:50

(2015-11-13, 22:12)BoxFreak Wrote:
(2015-11-13, 12:34)fritsch Wrote: Nobody knowssss without a Debug Log ...

via: https://www.youtube.com/watch?v=NeqndFdgakE

Very sorry about asking stupid questions like this, but it seems that this happens very occasionally, and I haven't yet invented how to reproduce it. When I do, I'll provide logs. Just wanted to know whether someone else has had this same problem before me.

OK, now it's happening again. Kodi crashed and after gui restarting automatically that kswapd0 is using almost 100% of one core. Log here: http://xbmclogs.com/psdexbqvt

Matt Devo · 2015-11-20, 20:56

(2015-11-20, 20:35)Soli Wrote: Hey Matt, a little OT. I remember vaguely that you use the ps3 remote too. I was just wondering if the ps3 remote sleeps properly when you are suspending the machine?

I usually have a timeout of 90 seconds, but what happens with this timeout if the machine is sleeping?

Btw your wakeup/fan-fix doesn't work in Kodibuntu (kernel 4.1.x). Not a big deal for me, I'll survive the 10 odd seconds with the fan spinning at high speed.

it does under OpenELEC, no idea on Kodibuntu. the PS3 remote is on my dev box so it's constantly being reset etc.

the fan speed workaround was only tested under OpenELEC. The kernel patches to fix the actual issue work correctly under Ubuntu etc, but require you to compile your own kernel currently.

(2015-11-20, 20:50)BoxFreak Wrote: OK, now it's happening again. Kodi crashed and after gui restarting automatically that kswapd0 is using almost 100% of one core. Log here: http://xbmclogs.com/psdexbqvt

that's not a debug log, shows nothing useful

movie78 · 2015-11-20, 22:23

Has anyone try kodi 16 Jarvis beta 1 on their chromebox?

**fritsch** · 2015-11-20, 22:25

Personally I would not run any mainline builds on intel hardware. The EGL rework we were doing - which sadly did not go into v16 - revolutionizes the way intel works on linux.

Perfect Colors without banding, increased throughput (factor 2) and half memory usage.

movie78 · 2015-11-20, 22:31

@fritsch

Thanks for heads up!

Karnis · (This post was last modified: 2015-11-20, 22:35 by Karnis.)

(2015-11-20, 22:23)movie78 Wrote: Has anyone try kodi 16 Jarvis beta 1 on their chromebox?

(2015-11-20, 22:25)fritsch Wrote: Personally I would not run any mainline builds on intel hardware. The EGL rework we were doing - which sadly did not go into v16 - revolutionizes the way intel works on linux.

Perfect Colors without banding, increased throughput (factor 2) and half memory usage.

What fritsch said. I'm using the latest Milhouse build on my Chromebox & the color banding I experienced on the "official" OE 6 is gone.

And it plays BBB 4k @ 60 fps without breaking a sweat. I wish I had a 4K HDTV. Confused

BoxFreak · 2015-11-20, 22:44

(2015-11-20, 20:56)Matt Devo Wrote:
(2015-11-20, 20:50)BoxFreak Wrote: OK, now it's happening again. Kodi crashed and after gui restarting automatically that kswapd0 is using almost 100% of one core. Log here: http://xbmclogs.com/psdexbqvt

that's not a debug log, shows nothing useful

Turning on debugging for a problem that happens once in a week is just not worth it (for my family). Rebooting fixes this problem so I can live with it.

**fritsch** · 2015-11-20, 22:48

You can enable debugging via advancedsettings.xml - that way you won't see anything on screen.

danfloss · 2015-11-21, 12:58

(2015-11-20, 22:34)Karnis Wrote:
(2015-11-20, 22:23)movie78 Wrote: Has anyone try kodi 16 Jarvis beta 1 on their chromebox?

(2015-11-20, 22:25)fritsch Wrote: Personally I would not run any mainline builds on intel hardware. The EGL rework we were doing - which sadly did not go into v16 - revolutionizes the way intel works on linux.

Perfect Colors without banding, increased throughput (factor 2) and half memory usage.

What fritsch said. I'm using the latest Milhouse build on my Chromebox & the color banding I experienced on the "official" OE 6 is gone.

And it plays BBB 4k @ 60 fps without breaking a sweat. I wish I had a 4K HDTV.

Thought Millhouse was for Rpi only

**fritsch** · 2015-11-21, 13:29

Why think so much - if one can read: http://forum.kodi.tv/showthread.php?tid=238393 ? :-)

pettergulbra · 2015-11-22, 12:15

(2015-11-20, 19:17)Matt Devo Wrote:
(2015-11-20, 15:40)pettergulbra Wrote: Have to read a little bit how to try OE live session. :-)

it was changed with v6.0: boot the install media, then at the 'boot:' prompt (which shows for ~5s) type 'live' and press enter

Then I have to update the EZ script first. I don think I have updated that on over a year, not really sure.

I don't really have the need of anything in KodiBuntu, was just to get the possibility to av a web browser in Kodi.
That don't get used much, and still think it will be better to just by an Cast device.
So I think I have to convert back to OE, then there will by a good time to update the script as well.

I see fritch is saying he personaly would not go for any Intel for Kodi mainline, is this because Kodi is better supported by other producers
(Nvidia, Amd)?

nickr · 2015-11-22, 12:45

No because his code is better than mainline.