LibreELEC does not ship with an Xserver for RPi, it runs Kodi directly on the framebuffer. You can use tvservice as an alternative to xrandr for changing modes and such.
Posts by escalade
-
-
You're mistakenly thinking to edit /etc which you shouldn't as it's read-only. When you have /storage/.config/samba.conf it will take priority. You'll need LibreELEC 8.2 or master for SMB2/3.
-
Can you check output of systemctl status bluetooth? Also try to run /usr/lib/bluetooth/bluetoothd manually.
-
Sounds odd. You can run "createlog" through ssh to populate the directory manually. Also post output of bluetoothctl.
-
-
20170627 has been uploaded let me know if that fixes it.
-
I'm quite sure I found the cause of the issue, a full rebuild is on the way in a few hours
-
As far as I can see from the logs posted earlier, bluetooth is working fine. There's this however:
Code01_KODI.log:00:38:31.574 T:1741681568 ERROR: ## LibreELEC Addon ## bluetooth::monitor::remove_agent ## ERROR: (AttributeError("'NoneType' object has no attribute 'remove_from_connection'",)) 01_KODI.log: File "/home/trondah/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.0-devel/LibreELEC-settings-6336f1e/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/resources/lib/modules/bluetooth.py", line 736, in remove_agent
The only other relevant commit is perhaps upgraded busybox, a new build 20170627 will be uploaded in a moment. Before upgrading, could you just test "bluetoothctl" from the command line and post the output?
-
Finding the problem should be easy because there's only been a few commits since the last release. I'll put out a new build soon.
EDIT: 20170626 uploaded for the RPi, please test. Only downgraded kernel.
As for your ps3 controllers, they should just work. libevdev is just a library it has nothing to do with the kernel or bluetooth.
-
I believe the internal bluetooth simply does not have enough bandwidth. If you search there's been other threads about it.
-
HOW TO:Provide Logfile - LibreELEC (this could be found by putting "Libreelec logfiles share" in the address bar)
BNEP is not needed and has never been included with RPi builds official or otherwise. There is 0 difference in kernel configuration from my previous release. Not excluding the kernel as a possible cause but it seems strange as it's a minor release.
You have a RPi or RPi2? In that case you have an external bluetooth adapter? Always provide full details about your hardware and full logs.
-
Kodi has nothing to do with hardware support. Upload the logs from the "Logfiles" share.
-
Nope, it should simply work, and use your normal internet connection.
Do you use the 'Wait for network' option in the LibreELEC Settings Add-on? It seems to be a necessary thing on intel machines.
This setting simply delays the start of Kodi until network is accessible, usually needed if you are using a shared database. Has nothing to do with Chromium, you should be able to start Chromium without an internet connection and it should work once it's available. Sounds like a local network issue to me, as there is lots of people using the Chromium addon without issue.
-
-
The RPi3 runs snes9x2010 great.
-
Wouldn't that lead to input delay, as your TV would need to upscale the resolution to 1080p? Perhaps not noticeable in Wii games?
-
-
My 3 year old i5 nuc plays Mario Kart pretty good while other games are a bit laggy. I think the latest gen nucs should run Dolphin well.