Thanks for the info. I fixed the profile bug and that will be included in the next release.
Unfortunately, for the installation of addons in the wizard, I can only have the addon 'request' installation and the rest of the steps are handled by Kodi directly. For security reasons I surmise they won't let an addon auto install things without the users explicit agreement (which I think is a good idea). I can add some more warnings/info into the wizard to make the process a little clearer.
So i tested this with IAGL version 3.0.0 and with the latest version (3.0.4) and can't recreate this issue. The extraction of archive files seems to work just fine for me. In doing some research, I'd recommend just verifying you have the latest vfs.libarchive/vfs.rar installed and activated in your addons (they're in the LE repository).
(Discussion of similar issue here)
Hello,
I'm the addon author. There looks like there's an issue with vfs.libarchive/Kodi with LE based on the log. The error is:
Create - unsupported protocol(archive) in archive://path_to_zip_file.zip/Which is an error I've never seen. It points to LE not supporting the archive protocol. I'll have to dig into this a little more.
The wiki mentions AMLGX is supported, do you have to build that yourself, or will you be including those eventually?
Thanks for bringing this setup back, it's awesome!
I've put together a script that generates Kodi game addons from the binaries available from libretro directly (no compiling). I've been testing it on Windows/Android/Linux/OSX and it seems to work pretty well, so I've expanded it to LE addons. The git repository for the addons is here.
For Generic LE x86_64 you can install and use the Kodi addon repository here
For ARMHF (RPi, and maybe S905? not sure exactly what is all covered with armhf), you can install and use the Kodi addon repository here
In testing the addons, many work, and some still don't (any addon requiring GL for example doesn't work, so they've been marked broken). The status of the ones I've tested on Linux and OSX are listed in the readme. I've setup the script to build a small number of cores for LE for testing for now, and if they seem to be working I'll open it up to the rest of the cores.
Happy Gaming!
I had a similar problem. I used a dtb from the Device Tree folder on the sd card after flashing the image which solved it.
That did it, thanks. I guess the dtb files are somehow different.
Hi @5schatten,
I've tried installing your build on an S905 box, but can't get it to boot.
This is the box.
Using the dtb file gxbb_p201_2G.dtb from here (renamed to dtb.img)
Just to test, I installed kszaq's latest S905 build, using the same dtb. Everything works, system boots, wireless, bluetooth, etc all work.
I've tried both updating from kzaqs build by putting your generic S905 tar file into the update folder and just installing fresh from the generic S905 img.gz file onto the sd card. In both cases the box just sits at the firmware boot screen and doesn't boot to LE. Is there anything I can do in order to troubleshoot or get boot error logs?
yes, you're right. But lakka's retraroch binary has some additional features such as poweroff option or lakka updater... if a user use the latest lakka will updte and overwrite libreelec installation... I tried that way a lot time ago and some users lost their OpenELEC installation...
To avoid that you can compile Lakka and edit retroarch package file and change just one parameter, then you will get a clean retroarch binary. But I can not compile any linux distro anymore...
The thing is that in new retroarch 1.7.3 there are some settings to "hide/view" some options in menus so I can try to hide "online updater" to avoid users loosing their LE installation... I'm gonna try it out
Lakka/Retroarch recently implemented some new config settings to hide/view a lot of those menu options, including the shutdown and update menus. That might make it more palatable to use for your binaries.
I just released a new RA 8.170.9 version including those missing libs, I tried it out and it worked in a fresh new LE9 alpha build installation.
You can update from kodi's Gamestarter repo or download zip from here: game.retroarch-8.170.9.zip
Also, I tried to get new RA 1.7.3 binary from escalade's/5schatten's releases but I can not make it work in official LE build... Since nowadays I just use my RPi for hyperion/ambilight control (and twice a month to watch some downloaded movies) by the moment 1.7.0 will be the last RA version in gamestarter addon, unless someone offers itself to compile RA using official LE toolchain... sorry...
Isn't lakka built on LE? Or is there some technical reason the binaries from lakka can't be used?
Sorry, I use ES binary from Escalade's build, so I will update if Escalade does.
I'm not sure Escalade is updating his build anymore. 5schatten has been updating a fork:
I'm interested in running a script 'outside of Kodi' on an S905 box I have running LibreElec. I'm running Retroarch in conjunction with Kodi on this box and use a launcher script to exit Kodi then launch the game in Retroarch. Rarely there's a game that doesn't work when launched and the box essentially just hangs. I'm able to ssh into the box and reboot it, or restart Kodi, but I'm interested in doing this from either the remote or from a controller connected via bluetooth.
Does LibreElec already have something included that would allow this? Any help would be appreciated.
I've added support in IARL to launch games if you're using this build. Seems to work pretty well for the systems I tested. Still trying to get it to work with PSP and AdvanceMAME. naibi was also gracious enough to add a retroarch setting in this build to boot back to Kodi instead of emulationstation when you exit Retroarch.
If you set sx05re_exit_to_kodi = True in the retroarch.cfg, you will boot back to Kodi on exit.
I'm attempting to get my chinese knockoff PS3 controllers to work with my S905 box (MXIII II) loaded with the latest kszaq LibreElec build.
After connecting them with a USB cable, Kodi 'sees' the controller and lists it as an available peripheral (the controller shows up as one that I can change the deadzone for in settings). But the mapping function within Kodi doesn't see any button press on the controller except for the center 'pair' button.
ssh'ing into the box, here's what shows up for the controller (shortened for brevity):
xxx:~ # dmesg
...
[ 81.498330@3] usb 1-1: USB disconnect, device number 2
[ 94.617144@3] usb 1-1: new full-speed USB device number 3 using xhci-hcd
[ 94.758175@3] usb 1-1: New USB device found, idVendor=054c, idProduct=0268
[ 94.758201@3] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 94.758216@3] usb 1-1: Product: PS(R) Gamepad
[ 94.758230@3] usb 1-1: Manufacturer: Gasia Co.,Ltd
[ 94.763760@3] sony 0003:054C:0268.0002: Fixing up Sony Sixaxis report descriptor
[ 94.766170@3] input: Gasia Co.,Ltd PS(R) Gamepad as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:054C:0268.0002/input/input5
[ 94.782116@1] sony 0003:054C:0268.0002: input,hiddev0,hidraw0: USB HID v1.11 Joystick [Gasia Co.,Ltd PS(R) Gamepad] on usb-xhci-hcd.0.auto-1/input0
xxx:~ # bluetoothctl
...
[PLAYSTATION(R)3 Controller]# info
Device 00:26:5C:F2:96:B0
Name: PLAYSTATION(R)3 Controller
Alias: PLAYSTATION(R)3 Controller
Class: 0x000540
Icon: input-keyboard
Paired: no
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Huma n Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
Modalias: usb:v054Cp0268d0000
xxx:~ # udevadm info --attribute-walk /dev/input/js0
...
looking at device '/devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:054C:0268.0006/input/input9/js0':
KERNEL=="js0"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:054C:0268.0006/input/input9':
KERNELS=="input9"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="Gasia Co.,Ltd PS(R) Gamepad"
ATTRS{phys}=="usb-xhci-hcd.0.auto-1/input0"
ATTRS{properties}=="0"
ATTRS{uniq}==""
looking at parent device '/devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:054C:0268.0006':
KERNELS=="0003:054C:0268.0006"
SUBSYSTEMS=="hid"
DRIVERS=="sony"
looking at parent device '/devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0':
KERNELS=="1-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usbhid"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}=="03"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bInterfaceProtocol}=="00"
ATTRS{bInterfaceSubClass}=="00"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
looking at parent device '/devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{authorized}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bMaxPower}=="500mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bcdDevice}=="0100"
ATTRS{bmAttributes}=="80"
ATTRS{busnum}=="1"
ATTRS{configuration}==""
ATTRS{devnum}=="5"
ATTRS{devpath}=="1"
ATTRS{idProduct}=="0268"
ATTRS{idVendor}=="054c"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Gasia Co.,Ltd"
ATTRS{maxchild}=="0"
ATTRS{product}=="PS(R) Gamepad"
ATTRS{quirks}=="0x0"
ATTRS{removable}=="unknown"
ATTRS{speed}=="12"
ATTRS{urbnum}=="22"
ATTRS{version}==" 2.00"The controller seems to be at least identified, but no input is read within Kodi.
Are there any extra troubleshooting steps that I can take? Or is there a udev rule that would force this controller to be 'seen' as a PS3 controller?
Also of note, I've used these controllers on an x86 build of LibreElec and they worked without any extra configuration outside of Kodi.
Any help would be appreciated!
I'm having some issues using my generic PS3 controllers with this build. Otherwise seems to work great!
I noticed there were some patches to other LibreElec / Lakka builds to resolve controller issues (see here and here) for Odroid LibreElec project. Wondering if the same patches would fix these issues with the S905 project?
I have a strange issue, wondering if anyone else has seen the same thing.
When launching a game, usually audio will work, but intermittently sometimes audio will not work. Without changing any settings, if I exit Retroarch and retry, some percentage of the time it works.
The retroarch log shows the following when it fails:
RetroArch [ERROR] :: ALSA: Failed to initialize...
RetroArch [ERROR] :: Failed to initialize audio driver. Will continue without audio.Config shows:
audio_driver = "alsathread"
audio_out_rate = "48000"
audio_device = "hdmi:CARD=PCH,DEV=0"
20170216:Code- rebased on latest le8 - kodi updated to latest krypton - mesa updated to latest git - xf86-video-nvidia updated to 378.13 - linux updated to 4.10-rc8 - retroarch updated to latest git
Awesome. Just awesome. Thanks so much for sharing this build with all of us.
New build uploaded.
Works great, thanks for the quick response