168 replies to this topic

[A.A.]

probably because exit was never stop media.

 

@WTE

 

we should follow koen's meta-kodi, now at 18.6 [1]

Possibly just using a .bbappend this time...

 

Keep on with the great work!

 

Cheers

A.A.

 

[1]  https://github.com/k...multimedia/kodi

 

Everything is uptodate and buildung fine. I see no reason to change anything. Your always free like I do to send to Openpli git any changes.

I'll do this with pleasure once the recipe is in OpenPLi development.

Right now the recipe with vuxxo2 patches has disappeared from your fork...

[WTE]

Still not merge: https://github.com/v...-vuplus/pull/72

So have to wait till this happens first.

[A.A.]

@WTE

 

yes, this is clear, let's wait for OpenPLi 8 for this.

 

I am referring to the patches for kodi 18 that were in your zeus-eudev branch.

In the meanwhile there is still to debug and see why it doesn't seemingly start on vuduo2.

 

Thanks for your work

A.A.

Edited by A.A., 7 June 2020 - 22:52.

[WTE]

https://github.com/w...zeus-evdev-keys

 

here I added the patches but in this branch didn't tried build yet.

[A.A.]

@WTE

 

I have enabled debug in advancedsettings.xml but cannot find the logfile.

Do you remember offhand where is it written? Should be

$HOME/.kodi/temp/kodi.log

Seems this kodi-stb is not following the paths documented in https://kodi.wiki/vi...g_file/Advanced.

THX

A.A.

 

P.S. lets' hope serial + GDB will not be necessary...

[A.A.]

@WTE:

 

sorry, silly question.

ah, all paths can be found in /usr/bin/kodi script

 

A.A.

[WTE]

/home/root/.kodi/tmp/

 

You get kodi logo and move through GUI?

[A.A.]

@WTE

 

No, nothing on screen. Just black.

I suppose it stops before writing logs

 

root@vuduo2:~# /usr/bin/kodi: line 223:   864 Bus error               ${KODI_BINARY} $SAVED_ARGS

 

I have found references in the web but they got  Segmentation fault (core dumped) and a crashlog. I don't see any.

 

Edit: enigma2 remains working, no apparent issues with TV

Edited by A.A., 8 June 2020 - 11:04.

[daimon]

Inserting kodi into the build

zgemma h7 no longer boots on both the zeus branch and the develop branch on h9combo everything is ok

[foxbob]

It works for me on my et11000.

[WTE]

 

Inserting kodi into the build

zgemma h7 no longer boots on both the zeus branch and the develop branch on h9combo everything is ok

 

Image to big for the broadcom CFE installation?

[daimon]

I get around the rootfs problem by changing from 2 to 3
in the meta-zgemma h7 config the build is successful
but for some reason it remains still at boot even the bootlogo fails

[A.A.]

@WTE

 

I am puzzled by the strace of kodi-stb, here the last lines

 

--- SIGBUS {si_signo=SIGBUS, si_code=SI_KERNEL, si_addr=NULL} ---
+++ killed by SIGBUS +++

 

apparently a null pointer dereference but I'll need GDB to understand.

[WTE]

Kodi will always make a log. So probably your looking wrong file.

Try to start from commandline.

init 4

kodi --standalone --debug

 

As VU+ is lot of closed source you probably should install libcrypto-compat

[A.A.]

@WTE

 

I can't find any log, I'm pretty sure it is not created. Maybe a memory issue.

Here the full strace: https://pastebin.com/PsS1qAns

 

I will study it overnight, my knowledge about mips syscalls is near zero...I spotted

 

prctl(PR_GET_FP_MODE)                   = -1 EINVAL (Invalid argument)

and PR_GET_FP_MODE (since Linux 4.0, only on MIPS)

But again, I plan to try a debug with GDB and -dbg binaries when I find time.

 

Cheers

A.A.

[WTE]

/lib/tls/bmips5000/libxbmc_base.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)

 

Seems this file need in a static map.

I do not know what libxbmc_base.so is. This is something made by VU I think. TLS is a part from SSL so I think you need to have crypto-compat installed as well

[A.A.]

@WTE

 

argh...I remembered that athoik wrote that we need to enable dvbproxy and reserve some memory range from commandline.

Does it ring a bell?

[A.A.]

/lib/tls/bmips5000/libxbmc_base.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)

 

Seems this file need in a static map.

I do not know what libxbmc_base.so is. This is something made by VU I think. TLS is a part from SSL so I think you need to have crypto-compat installed as well

this lib comes from the (in)famous xbmc-support tarball (kodi-vuplus.inc)

[A.A.]

@WTE

 

the lib is found a couple of lines later

 

openat(AT_FDCWD, "/usr/lib/libxbmc_base.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3

 

I'll try with crypto-compat later on

[WTE]

@WTE

 

argh...I remembered that athoik wrote that we need to enable dvbproxy and reserve some memory range from commandline.

Does it ring a bell?

coherent memory probably

Why VU mipsel need lot of stuff to run Kodi I don't know. Other manufactures need nothing extra for the mipsel boxes.

As lot is closed source it's difficult to see what is wrong.

 

I am pretty sure in /home/root/.kodi/temp/kodi.log is made