Posts by kall

    Hi bite_your_idols.


    I can't open Retroarch latest on generic.

    Code
    1. /storage/.kodi/addons/game.retroarch/game.retroarch-Gen: error while loading shared libraries: libass.so.5: cannot open shared object file: No such file or directory


    Showing in log.

    Hi escalade,


    I'm not sure if it's been mentioned but LibreELEC-RPi2.arm-8.2-devel-20170801.img.gz seems to have broken the internal wifi adapter on the Rpi3. It cannot detect any Wifi connections and Libreelec is not giving the option for wireless networks, only wired.

    Enabling logging is not creating the logfiles still as before with the bluetooth problems and I am unable to SSH into the device as I can't connect via ethernet for now.

    I've tried clean installs. I'll roll back to an older version and see how far back the issue goes as I haven't updated for awhile.


    Edit: LibreELEC-RPi2.arm-8.0-devel-20170719 seems to be the last working build. I'll plug into ethernet when I get a chance so I can get logs.

    Thanks mate. Got there in the end and seems to work well.

    I noticed this in your previous log: "09_Journal-cur.log:Jun 28 08:20:21 LibreELEC systemd[559]: brcmfmac_sdio-firmware.service: Failed at step EXEC spawning /usr/bin/rpi-btuart: No such file or directory"


    This could be an indication to what's going wrong, seems related to the bluetooth interface. Could you compare with the working build? Does the service start correctly there?


    Also I've uploaded 20170705 which is a full rebuild with busybox reverted and no libevdev (I don't think that's it but just to exclude that too). If it still doesn't work play around with the rpi-btuart script see why it's failing. Also check that the bluetooth service didn't get disabled in libreelec settings.

    Good news! 20170705 has working internal bluetooth. However, without the libevdev you build into 20170615 my ps3 controller is no good with reicast again. Atleast it's working again though.


    I can roll back to 20170615 if you still want these logs to compare?

    Then I've no clue as to what's the problem. There's no relevant commits since the working build from june 15. There's updated busybox and kernel, both which were reversed in the test builds without success. Might be due to my build system being a rolling distribution, so updated packages there could cause unforeseen issues with packages due to the nature of LE's toolchain. I'll do a build on my older build system some time this weekend to see if that solves it.


    Poking around with bluetoothd (perhaps using strace or adding debugging) might give some clues.

    No worries, i'll have another look over the weekend and see if I can find anything.


    Let me know when you have anymore builds to test.

    Cheers

    Can you check output of systemctl status bluetooth? Also try to run /usr/lib/bluetooth/bluetoothd manually.


    Code
    1. ● bluetooth.service - Bluetooth service
    2. Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor p
    3. reset: disabled)
    4. Active: inactive (dead)

    Trying to run bluetoothd manually results in system lockup.


    systemctl start bluetooth seems to start it.

    However I still can't connect any devices and the adapter still can't be found in Kodi.

    Strange. Manually creating the log works fine. Still no luck through Kodi.


    Code
    1. ##############################################
    2. # LibreELEC #
    3. # http://libreelec.tv #
    4. ##############################################
    5. LibreELEC (community) Version: devel-20170627
    6. LibreELEC git: a88207b1fb4153cbf9448b59d1553d93400a285a
    7. LibreELEC:~ # createlog
    8. LibreELEC:~ # bluetoothctl
    9. Waiting to connect to bluetoothd...

    This just hangs and wont connect.