Re: kodi with framebuffer on cubox-i

2017-10-25 Thread Rainer Dorsch
Hi Jonas,

as you suggested, I created

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879735

for everything which affects kodi on the cubox-i. I summarized the knowledge I 
gained so far, there.

Please follow-up to 879...@bugs.debian.org and  subscribe to it 879735-
subscr...@bugs.debian.org , if you are interested in the discussion.

Thanks
Rainer

On Donnerstag, 5. Oktober 2017 08:09:44 CEST Jonas Smedegaard wrote:
> Quoting Rainer Dorsch (2017-10-04 22:38:58)
> 
> > On Mittwoch, 4. Oktober 2017 10:34:00 CEST Jonas Smedegaard wrote:
> > [...]
> > 
> > > Correction: Debian Kodi is built with --enable-gles on
> > > armel/armhf/arm64.
> > 
> > Good news :-)
> > 
> >> I have no experience (yet) running Kodi on arm (be it framebuffer or
> >> X11), but am quite interested in our official package best possible
> >> covering the needs of our users: In case you (or others following
> >> along here) figure out some build configuration tuing needed then
> >> please do not hesitate to file wishlist bugreports :-)
> > 
> > I am not yet there...
> > 
> >> Heck, even if you have only vague dreams like "awww, please get Kodi
> >> to work from framebuffer on Vivante-based armhf devices" you might
> >> also file a (wishlist!) bugreport about that, to have a well-defined
> >> place to collect the details until substantial enough act on it.
> > 
> > Is there any information which is useful for you which should be
> > appended to the bugreport?
> 
> Don't think of me as the recipient: Think of it as a way to create an
> interest group around a narrow, actionable topic.
> 
> You raised this as a cross-post on two mailinglists somewhat related to
> your topic.  Those are good places to seek help, I just imagine it might
> be even better if then the detailed discussion happening elsewhere only
> among those really interested in that detailed topic (myself included) -
> and I offer a way to do that by use of a wishlist bugreport with the
> kodi package.
> 
> What I imagine is useful is your clues for the puzzle.  And a link to
> the wiki page you might have created for tracking facts about the
> puzzle.
> 
> Ideally, cross-posts to multiple lists come with an explicit invitation
> to which *single* place to follow up.
> 
> 
>  - Jonas


-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-13 Thread Jonas Smedegaard
Quoting Rainer Dorsch (2017-10-03 19:33:15)
> I experimented with kodi on the cubox-i without proprietary 
> extensions. So far no luck yet, but I think I have not yet hit the 
> hard roadblocks...
> 
> First I tried without an X-server directly on framebuffer. How would I 
> tell kodi not to search for an X11 display?

Just a wild guess: Perhaps this related to bug#878324?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-05 Thread Paul Wise
On Fri, Oct 6, 2017 at 3:22 AM, Rainer Dorsch wrote:

> http://paste.debian.net/989216/

Hmm, I'm not sure what the error is. If you can I would suggest asking
on the freenode #etnaviv IRC channel:

https://webchat.freenode.net/?channels=etnaviv

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-05 Thread Rainer Dorsch
On Donnerstag, 5. Oktober 2017 12:32:21 CEST Paul Wise wrote:
> On Thu, Oct 5, 2017 at 4:37 AM, Rainer Dorsch wrote:
> > I checked versions now, I should be good, but the xserver still does not
> > start (started with the Xserver now and look to kodi as a second step).
> 
> Please put the full Xorg log on paste.debian.net.

http://paste.debian.net/989216/

> > rd@xbian:~$ apt-cache policy mesa-va-drivers
> 
> The GPU package is libgl1-mesa-dri, video decoding is a completely
> separate matter, no idea about that but I guess the ffmpeg commit you
> mentioned would have to reach Debian for that.

That is also uptodate:

*rd@xbian*:*~*$ apt-cache policy libgl1-mesa-dri 
*rd@xbian*:*~*$ 

Rainer


-- 
Rainer Dorsch
http://bokomoko.de/
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: kodi with framebuffer on cubox-i

2017-10-05 Thread Jonas Smedegaard
Quoting Rainer Dorsch (2017-10-04 22:38:58)
> On Mittwoch, 4. Oktober 2017 10:34:00 CEST Jonas Smedegaard wrote:
> [...]
> > Correction: Debian Kodi is built with --enable-gles on
> > armel/armhf/arm64.
> 
> Good news :-)
> 
>> I have no experience (yet) running Kodi on arm (be it framebuffer or 
>> X11), but am quite interested in our official package best possible 
>> covering the needs of our users: In case you (or others following 
>> along here) figure out some build configuration tuing needed then 
>> please do not hesitate to file wishlist bugreports :-)
>
> I am not yet there...
>
>> Heck, even if you have only vague dreams like "awww, please get Kodi 
>> to work from framebuffer on Vivante-based armhf devices" you might 
>> also file a (wishlist!) bugreport about that, to have a well-defined 
>> place to collect the details until substantial enough act on it.
>
> Is there any information which is useful for you which should be 
> appended to the bugreport?

Don't think of me as the recipient: Think of it as a way to create an 
interest group around a narrow, actionable topic.

You raised this as a cross-post on two mailinglists somewhat related to 
your topic.  Those are good places to seek help, I just imagine it might 
be even better if then the detailed discussion happening elsewhere only 
among those really interested in that detailed topic (myself included) - 
and I offer a way to do that by use of a wishlist bugreport with the 
kodi package.

What I imagine is useful is your clues for the puzzle.  And a link to 
the wiki page you might have created for tracking facts about the 
puzzle.

Ideally, cross-posts to multiple lists come with an explicit invitation 
to which *single* place to follow up.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Jonas Smedegaard
Quoting Paul Wise (2017-10-05 06:32:21)
> On Thu, Oct 5, 2017 at 4:37 AM, Rainer Dorsch wrote:
> 
> > I checked versions now, I should be good, but the xserver still does not
> > start (started with the Xserver now and look to kodi as a second step).
> 
> Please put the full Xorg log on paste.debian.net.
> 
> > rd@xbian:~$ apt-cache policy mesa-va-drivers
> 
> The GPU package is libgl1-mesa-dri, video decoding is a completely
> separate matter, no idea about that but I guess the ffmpeg commit you
> mentioned would have to reach Debian for that.

Seems to me that ffmeg change is only about speeding up processing (by 
making some data paths shorter) - something else needs to provide the 
actual codecs.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Paul Wise
On Thu, Oct 5, 2017 at 4:37 AM, Rainer Dorsch wrote:

> I checked versions now, I should be good, but the xserver still does not
> start (started with the Xserver now and look to kodi as a second step).

Please put the full Xorg log on paste.debian.net.

> rd@xbian:~$ apt-cache policy mesa-va-drivers

The GPU package is libgl1-mesa-dri, video decoding is a completely
separate matter, no idea about that but I guess the ffmpeg commit you
mentioned would have to reach Debian for that.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Rainer Dorsch
Hi Jonas,

thanks for your response.

On Mittwoch, 4. Oktober 2017 10:34:00 CEST Jonas Smedegaard wrote:
[...]
> Correction: Debian Kodi is built with --enable-gles on
> armel/armhf/arm64.

Good news :-)

> I have no experience (yet) running Kodi on arm (be it framebuffer or
> X11), but am quite interested in our official package best possible
> covering the needs of our users: In case you (or others following along
> here) figure out some build configuration tuing needed then please do
> not hesitate to file wishlist bugreports :-)

I am not yet there...

> Heck, even if you have only vague dreams like "awww, please get Kodi to
> work from framebuffer on Vivante-based armhf devices" you might also
> file a (wishlist!) bugreport about that, to have a well-defined place to
> collect the details until substantial enough act on it.

Is there any information which is useful for you which should be appended to 
the bugreport?

Thanks
Rainer



-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Rainer Dorsch
Hi Paul,

I checked versions now, I should be good, but the xserver still does not start 
(started with 
the Xserver now and look to kodi as a second step).

On Mittwoch, 4. Oktober 2017 11:33:25 CEST Paul Wise wrote:
> On Wed, Oct 4, 2017 at 1:33 AM, Rainer Dorsch wrote:
> > I experimented with kodi on the cubox-i without proprietary extensions.
> 
> Since the CuBox i* series of devices use Vivante GPUs and there are
> reverse engineered libre drivers called etnaviv for these GPUs, you
> should be able to get graphics using solely Debian main and no
> proprietary extensions. 

*rd@xbian*:*~*$ uname -a 
*rd@xbian*:*~*$ 

> I note the etnaviv support for libdrm is in
> Debian buster and later 

*rd@xbian*:*~*$ apt-cache policy libdrm-etnaviv1  
*rd@xbian*:*~*$ 


> and the etnaviv support for mesa is in Debian
> sid and later. 

*rd@xbian*:*~*$ apt-cache policy mesa-va-drivers  
*rd@xbian*:*~*$ apt-cache policy mesa-vdpau-drivers  
*rd@xbian*:*~*$ 


> If you would like this on Debian stretch or earlier you
> would have to backport Linux, mesa, libdrm and possibly some other
> things.
> 
> https://www.solid-run.com/freescale-imx6-family/cubox-i/cubox-i-specificatio
> ns/ https://github.com/etnaviv
> https://packages.debian.org/search?keywords=etnaviv
> https://packages.debian.org/search?suite=sid=filename=contents
> =etnaviv

But Xorg still rejects to start:

[31.067] (EE)  


Any ideas and hints are welcome

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/
[30.239] 
X.Org X Server 1.19.3
Release Date: 2017-03-15
[30.239] X Protocol Version 11, Revision 0
[30.240] Build Operating System: Linux 3.16.0-4-armmp-lpae armv7l Debian
[30.240] Current Operating System: Linux xbian 4.13.0-1-armmp #1 SMP Debian 4.13.4-1 (2017-10-01) armv7l
[30.240] Kernel command line: console=ttymxc0,115200 quiet
[30.240] Build Date: 07 July 2017  08:55:08AM
[30.240] xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
[30.240] Current version of pixman: 0.34.0
[30.240] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[30.240] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[30.241] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct  4 22:28:37 2017
[30.242] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[30.243] (==) No Layout section.  Using the first Screen section.
[30.243] (==) No screen section available. Using defaults.
[30.244] (**) |-->Screen "Default Screen Section" (0)
[30.244] (**) |   |-->Monitor ""
[30.244] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[30.245] (==) Automatically adding devices
[30.245] (==) Automatically enabling devices
[30.245] (==) Automatically adding GPU devices
[30.245] (==) Max clients allowed: 256, resource mask: 0x1f
[30.245] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[30.245] 	Entry deleted from font path.
[30.245] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[30.245] 	Entry deleted from font path.
[30.246] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[30.246] 	Entry deleted from font path.
[30.246] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	built-ins
[30.246] (==) ModulePath set to "/usr/lib/xorg/modules"
[30.246] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[30.246] (II) Loader magic: 0x581f60
[30.246] (II) Module ABI versions:
[30.246] 	X.Org ANSI C Emulation: 0.4
[30.246] 	X.Org Video Driver: 23.0
[30.246] 	X.Org XInput driver : 24.1
[30.246] 	X.Org Server Extension : 10.0
[30.249] (++) using VT number 7

[30.249] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[30.252] (II) xfree86: Adding drm device (/dev/dri/card1)
[30.264] (II) xfree86: Adding drm device (/dev/dri/card0)
[30.264] (II) no primary bus or device found
[30.264] 	falling back to /sys/devices/soc0/display-subsystem/drm/card1
[30.264] (II) LoadModule: "glx"
[30.265] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[30.292] (II) Module glx: vendor="X.Org Foundation"
[30.292] 	compiled for 1.19.3, module version = 1.0.0
[30.292] 	ABI class: X.Org Server 

Re: kodi with framebuffer on cubox-i

2017-10-04 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2017-10-03 21:00:36)
> Hi Rainer,
> 
> Quoting Rainer Dorsch (2017-10-03 19:33:15)
> > I experimented with kodi on the cubox-i without proprietary 
> > extensions. So far no luck yet, but I think I have not yet hit the 
> > hard roadblocks...
> 
> Interesting!
> 
> 
>> First I tried without an X-server directly on framebuffer. How would 
>> I tell kodi not to search for an X11 display?
> [...]
>> Any input and ideas are welcome.
> 
> Girst hit I got web-searching for "kodi framebuffer" was a discussion 
> around "git clone https://aur.archlinux.org/kodi-c2-fb.git;. That git 
> has at its heart the configure options "--disable-x11 --enable-gles".
> 
> Debian kodi package has those options reversed.
> 
> So it seems you need to recompile the kodi package...

Correction: Debian Kodi is built with --enable-gles on 
armel/armhf/arm64.

I have no experience (yet) running Kodi on arm (be it framebuffer or 
X11), but am quite interested in our official package best possible 
covering the needs of our users: In case you (or others following along 
here) figure out some build configuration tuing needed then please do 
not hesitate to file wishlist bugreports :-)

Heck, even if you have only vague dreams like "awww, please get Kodi to 
work from framebuffer on Vivante-based armhf devices" you might also 
file a (wishlist!) bugreport about that, to have a well-defined place to 
collect the details until substantial enough act on it.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-03 Thread Rainer Dorsch
Hi Paul,

many thanks for your response.

On Mittwoch, 4. Oktober 2017 11:33:25 CEST Paul Wise wrote:
> On Wed, Oct 4, 2017 at 1:33 AM, Rainer Dorsch wrote:
> > I experimented with kodi on the cubox-i without proprietary extensions.
> 
> Since the CuBox i* series of devices use Vivante GPUs and there are
> reverse engineered libre drivers called etnaviv for these GPUs, you
> should be able to get graphics using solely Debian main and no
> proprietary extensions. I note the etnaviv support for libdrm is in
> Debian buster and later and the etnaviv support for mesa is in Debian
> sid and later. If you would like this on Debian stretch or earlier you
> would have to backport Linux, mesa, libdrm and possibly some other
> things.
> 
> https://www.solid-run.com/freescale-imx6-family/cubox-i/cubox-i-specificatio
> ns/ https://github.com/etnaviv
> https://packages.debian.org/search?keywords=etnaviv
> https://packages.debian.org/search?suite=sid=filename=contents
> =etnaviv

I forgot to mention that I am running buster, I have not noticed that I need 
mesa from sid though. Will try that later.

It seems for kodi also a recent ffmpeg is needed, commit from 10 days ago:

http://forum.solid-run.com/viewtopic.php?t=363=22466#p22466

Since ffmpeg 3.3.4 in sid and buster, we need to wait for a new release here 
as well.

But getting X up and running would be a worthwhile intermediate goal :-)

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-03 Thread Paul Wise
On Wed, Oct 4, 2017 at 1:33 AM, Rainer Dorsch wrote:

> I experimented with kodi on the cubox-i without proprietary extensions.

Since the CuBox i* series of devices use Vivante GPUs and there are
reverse engineered libre drivers called etnaviv for these GPUs, you
should be able to get graphics using solely Debian main and no
proprietary extensions. I note the etnaviv support for libdrm is in
Debian buster and later and the etnaviv support for mesa is in Debian
sid and later. If you would like this on Debian stretch or earlier you
would have to backport Linux, mesa, libdrm and possibly some other
things.

https://www.solid-run.com/freescale-imx6-family/cubox-i/cubox-i-specifications/
https://github.com/etnaviv
https://packages.debian.org/search?keywords=etnaviv
https://packages.debian.org/search?suite=sid=filename=contents=etnaviv

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: kodi with framebuffer on cubox-i

2017-10-03 Thread Jonas Smedegaard
Hi Rainer,

Quoting Rainer Dorsch (2017-10-03 19:33:15)
> I experimented with kodi on the cubox-i without proprietary 
> extensions. So far no luck yet, but I think I have not yet hit the 
> hard roadblocks...

Interesting!


> First I tried without an X-server directly on framebuffer. How would I 
> tell kodi not to search for an X11 display?
[...]
> Any input and ideas are welcome.

Girst hit I got web-searching for "kodi framebuffer" was a discussion 
around "git clone https://aur.archlinux.org/kodi-c2-fb.git;. That git 
has at its heart the configure options "--disable-x11 --enable-gles".

Debian kodi package has those options reversed.

So it seems you need to recompile the kodi package...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


kodi with framebuffer on cubox-i

2017-10-03 Thread Rainer Dorsch
Hello,

I experimented with kodi on the cubox-i without proprietary extensions. So far 
no luck yet, but I think I have not yet hit the hard roadblocks...

First I tried without an X-server directly on framebuffer. How would I tell 
kodi not to search for an X11 display?

I get in the kodi crashlog:

18:07:24.378 T:2932268592   ERROR: X11 Error: No Display found

As far as I understand is xbian running kodi without X11, but they use a lot 
of proprietary extension on their image for the cubox-i. If nobody else has an 
idea, I could start looking at xbian how they start kodi...

Here is the full kodi crashlog:

rd@xbian:~$ cat kodi_crashlog-20171003_180724.log 
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Tue Oct  3 18:07:24 CEST 2017
 Kodi Options: 
 Arch: armv7l
 Kernel: Linux 4.12.0-2-armmp #1 SMP Debian 4.12.13-1 (2017-09-19)
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
gdb not installed, can't get stack trace.
# END STACK TRACE ###

# LOG FILE ##

18:07:14.152 T:2932268592  NOTICE: special://profile/ is mapped to: 
special://masterprofile/
18:07:14.152 T:2932268592  NOTICE: 
---
18:07:14.152 T:2932268592  NOTICE: Starting Kodi from Debian (17.3 Debian 
package version: 2:17.3+dfsg1-2). Platform: Linux ARM (Thumb) 32-bit
18:07:14.152 T:2932268592  NOTICE: Using Release Kodi from Debian x32 build
18:07:14.152 T:2932268592  NOTICE: Kodi from Debian compiled from 
2:17.3+dfsg1-2 by GCC 6.3.0 for Linux ARM (Thumb) 32-bit version 4.9.30 
(264478)
18:07:14.152 T:2932268592  NOTICE: Running on Debian GNU/Linux buster/sid 
unstable, kernel: Linux ARM 32-bit version 4.12.0-2-armmp
18:07:14.152 T:2932268592  NOTICE: FFmpeg version/source: 3.3.4-2
18:07:14.153 T:2932268592  NOTICE: Host CPU: ARMv7 Processor rev 10 (v7l), 2 
cores available
18:07:14.153 T:2932268592  NOTICE: ARM Features: Neon disabled
18:07:14.154 T:2932268592  NOTICE: special://xbmc/ is mapped to: 
/usr/share/kodi
18:07:14.154 T:2932268592  NOTICE: special://xbmcbin/ is mapped to: 
/usr/lib/arm-linux-gnueabihf/kodi
18:07:14.154 T:2932268592  NOTICE: special://xbmcbinaddons/ is mapped to: 
/usr/lib/arm-linux-gnueabihf/kodi/addons
18:07:14.154 T:2932268592  NOTICE: special://masterprofile/ is mapped to: 
/home/rd/.kodi/userdata
18:07:14.154 T:2932268592  NOTICE: special://envhome/ is mapped to: /home/rd
18:07:14.154 T:2932268592  NOTICE: special://home/ is mapped to: 
/home/rd/.kodi
18:07:14.154 T:2932268592  NOTICE: special://temp/ is mapped to: 
/home/rd/.kodi/temp
18:07:14.154 T:2932268592  NOTICE: special://logpath/ is mapped to: 
/home/rd/.kodi/temp
18:07:14.155 T:2932268592  NOTICE: The executable running is: /usr/lib/arm-
linux-gnueabihf/kodi/kodi.bin
18:07:14.155 T:2932268592  NOTICE: Local hostname: xbian
18:07:14.155 T:2932268592  NOTICE: Log File is located: 
/home/rd/.kodi/temp//kodi.log
18:07:14.155 T:2932268592  NOTICE: 
---
18:07:14.196 T:2932268592   ERROR: DBus: Error 
org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower 
was not provided by any .service files
18:07:16.958 T:2932268592  NOTICE: load settings...
18:07:17.022 T:2932268592  NOTICE: Found 1 Lists of Devices
18:07:17.022 T:2932268592  NOTICE: Enumerated PULSE devices:
18:07:17.022 T:2932268592  NOTICE: Device 1
18:07:17.022 T:2932268592  NOTICE: m_deviceName  : Default
18:07:17.022 T:2932268592  NOTICE: m_displayName : Default
18:07:17.023 T:2932268592  NOTICE: m_displayNameExtra: Default Output 
Device (PULSEAUDIO)
18:07:17.023 T:2932268592  NOTICE: m_deviceType  : AE_DEVTYPE_PCM
18:07:17.023 T:2932268592  NOTICE: m_channels: FL,FR
18:07:17.023 T:2932268592  NOTICE: m_sampleRates : 
5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
18:07:17.023 T:2932268592  NOTICE: m_dataFormats : 
AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
18:07:17.023 T:2932268592  NOTICE: m_streamTypes : No passthrough 
capabilities
18:07:17.023 T:2932268592  NOTICE: Device 2
18:07:17.023 T:2932268592  NOTICE: m_deviceName  : 
alsa_output.platform-sound-spdif.stereo-fallback
18:07:17.023 T:2932268592  NOTICE: m_displayName : Built-in Audio 
Stereo
18:07:17.023 T:2932268592  NOTICE: m_displayNameExtra: Analog Output 
(PULSEAUDIO)
18:07:17.023 T:2932268592  NOTICE: m_deviceType  : AE_DEVTYPE_PCM
18:07:17.023 T:2932268592  NOTICE: m_channels: FL,FR
18:07:17.023 T:2932268592  NOTICE: m_sampleRates : 
5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
18:07:17.023 T:2932268592  NOTICE: