Posts by kall

Quote from bite_your_idols

if you install yourself LE8 into generic device, could you please grab shared library "libass.so.5" and paste here a download link... That would help me a lot...

No worries. I'll try and pull apart LE8 otherwise i'll wait for you to update git

I'm on LE9 Generic.

Hi bite_your_idols.

I can't open Retroarch latest on generic.

/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.

Quote from escalade

kall

I've located the issue (CONFIG_BASH_IS_ASH wasn't enabled in the updated busybox config), this caused rpi-btuart which uses #!/bin/bash to fail.

20170708 uploaded:

Code

linux: update to 4.11.9
retroarch: update to dc521b4
desmume-libretro: update to 73531d7
genesis-plus-gx-libretro: update to 9c10f4f
tyrquake-libretro: update to a0502d1
SABnzbd: update to 2.2.0Alpha2
mame2003-libretro: update to e0a9df4
quicknes-libretro: update to 05a742e
retroarch-joypad-autoconfig: update to 8e68505
reicast: add pr1002 to improve keyboard handling
xf86-video-nvidia: update to 384.47

Display More

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

Seems to be working fine in this one also.

Quote from escalade

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?

Quote from escalade

20170704 uploaded for the rpi please test.

Sill no bluetooth adapter found.

Just a bit more info, just tried with a bluetooth dongle and have no problems at all with bluetoothd recognising and connecting to this.

Definitely seems to be a problem recognising the internal adapter.

Quote from escalade

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

Quote from escalade

And bluetoothctl after startup of the daemon? You did activate bluetooth in LibreELEC settings right? Not doing so would result in the daemon not starting.

Yes, activated in settings, bluetoothctl has no change.

Quote from escalade

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

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

Trying to run bluetoothd manually results in system lockup.

systemctl start bluetooth seems to start it.

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor p
reset: disabled)
   Active: active (running) since Fri 2017-06-30 21:50:21 AEST; 1min 2s ago
 Main PID: 782 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─782 /usr/lib/bluetooth/bluetoothd

Jun 30 21:50:21 LibreELEC systemd[1]: Started Bluetooth service.
Jun 30 21:50:21 LibreELEC bluetoothd[782]: Bluetooth daemon 5.44
Jun 30 21:50:21 LibreELEC bluetoothd[782]: Starting SDP server
Jun 30 21:50:21 LibreELEC bluetoothd[782]: kernel lacks bnep-protocol support
Jun 30 21:50:21 LibreELEC bluetoothd[782]: System does not support network plugi
n
Jun 30 21:50:21 LibreELEC bluetoothd[782]: Bluetooth management interface 1.14 i
nitialized

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.

##############################################
#                 LibreELEC                  #
#            http://libreelec.tv             #
##############################################

LibreELEC (community) Version: devel-20170627
LibreELEC git: a88207b1fb4153cbf9448b59d1553d93400a285a
LibreELEC:~ # createlog
LibreELEC:~ # bluetoothctl
Waiting to connect to bluetoothd...

This just hangs and wont connect.

Quote from escalade

Logs?

This build wont create log files for some reason? I've tried restarting the logging on and off a few times and also done another clean install?

The logfiles dir is just staying empty.

Quote from escalade

20170627 has been uploaded let me know if that fixes it.

I'd like to be able to tell you it fixed it, but unfortunately it still hasn't. Sorry!

Again on a fresh install.

Still no luck with 20170627.

Just tried it on a fresh sd card to be sure aswell.

I'm getting no output at all.

It locks up trying to connect.

LibreELEC:~ # bluetoothctl
[bluetooth]# nnect to bluetoothd...