Enabling the native controller support

[NoTarget]

Hey guys,

is it somehow possible to enable the official Frodo gamepad support in xbian?
I can't find this configuration point in the latest release:
http://www.abload.de/img/gamepadbhbot.png

greetings NoTarget

[Koenkk]

We are already on it, see: https://github.com/xbianonpi/xbian/issues/315#issuecomment-14663317

[NoTarget]

Nice! What do you think, how long it's going to take for a release with this function enabled?

[Koenkk]

My pi is already compiling xbmc with SDL and joystick support, if nothing goes wrong, it will be in the xbmc-nightly/Frodo git within a few hours - 8 hours. Just keep an eye on that github issue Instructions on how to install it will also be posted there.

[Koenkk]

Updated : https://github.com/xbianonpi/xbian/issues/315#issuecomment-14663317

[NoTarget]

Already installing it. Thanks guys for the great support!

---

Got an error after installing the nightly, when i want to start XBMC.

"/usr/local/lib/xbmc/xbmc.bin: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory"

i tried it 2 times. After the restore from the backup everything is fine.

[Koenkk]

Looks like a missing library, wil look into it

[NoTarget]

Waiting for a working release so bad. Somthing i can do on my own?

[CurlyMo]

(11th Mar, 2013 02:50 AM)NoTarget Wrote:  Waiting for a working release so bad. Somthing i can do on my own?

Donating enough so we can develop full-time

[Koenkk]

(10th Mar, 2013 11:35 PM)NoTarget Wrote:  Already installing it. Thanks guys for the great support!

---

Got an error after installing the nightly, when i want to start XBMC.

"/usr/local/lib/xbmc/xbmc.bin: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory"

i tried it 2 times. After the restore from the backup everything is fine.

Execute

Code:

sudo apt-get install libsdl1.2debian

[NoTarget]

Code:

xbian@Raspi ~/xbmc-nightly $ sudo service xbmc start
xbian@Raspi ~/xbmc-nightly $ commandline read: xbmc.bin
commandline read: --standalone

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.10 |~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2008  The world wide DirectFB Open Source Community
        (c) 2000-2004  Convergence (integrated media) GmbH
      ----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2012-06-01 00:48)
(!) Direct/Util: opening '/dev/fb0' failed
    --> Permission denied
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
    --> Initialization error!
ERROR: Unable to create GUI. Exiting
(!) [ 6091:    0.000] --> Caught signal 11 (at (nil), invalid address) <--

[Koenkk]

Can you start XBMC with

Code:

sudo /usr/local/lib/xbmc/xbmc.bin

---

The issue is that the xbian user doesn't have permission to /dev/fb0, root does. @CurlyMo can you help us out on this one?

---

Some progress

Code:

sudo usermod -a -G video xbian

But still an error in the xbmc.log

Code:

14:54:10 T:3032182784  NOTICE: Setup SDL
14:54:10 T:3032182784   FATAL: XBAppEx: Unable to initialize SDL: Unable to open a console terminal

[CurlyMo]

I don't think these kind of framebuffer routes is a good idea. That's why XBMC has a custom implementation for the RPi in which they don't directly use the framebuffer.

[Koenkk]

That means SDL is a no go for us?

[CurlyMo]

I think there are some things crossing each other:
1) Our wayland + XBMC experimentation for which we need an SDL
2) Our current (default RPi) XBMC implementation which uses the video driver directly

If you are trying to achieve the first one, then you will probably run into a lot of difficulties. I still would like to test the first build here. If you are trying to add an SDL to the second option then you're indeed doing some wierd things because the whole point of a fluent XBMC for the RPi at this moment is it is built so it can run without the X display driver and SDL.