Posts by Grimson

I just did a fresh build from master (commit: b0ac12e) and Bluetooth works without having to change anything.

Thanks.

Quote from milhouse

Can you run the following commands:

Code

systemctl status brcmfmac_sdio-firmware.service | paste
cat /flash/cmdline.txt | paste

and paste the links. Thanks.

Here from the current official build:
TFDH
and from my build with the mentioned patch removed:
VYPL
cmdline.txt has not been modified:

boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet

Ok, here is a reliable way to reproduce it.

Reqs: Raspi 3 without any additional hardware, only connected to a TV, no network or USB devices. Anker Bluetooth speakers to see if anything is found.

Step 1, with a clean image:
1. DD the LE image on a fresh SD.
2. Let it boot, finish the wizard without changing anything.
3. Go into the LE settings, turn on Bluetooth in the Services settings.
4. Go to the Bluetooth screen, it tells you there are no Bluetooth adapters found.
5. Turn on the BT speakers, nothing changes.

Step 2:
1. Build the LE master, commit: 42265e9 at the time of testing.
2. Update with the .tar file and repeat above points 3 to 5, nothing changes

Step 3:
1. Remove the "offending" patch I noted previously.
2. Rebuild LE and update again with the .tar file.
3. Go into the LE settings, turn on BT if you turned it of previously.
4. Go to the BT screen, it tells you that there are no BT devices visible (different message than in Step 1).
5. Turn on the BT speakers, a few seconds later they are visible an can be connected.

Additional info:
lsmod with the current official LE build and BT turned on is missing: hci_uart and btbcm.
dmesg with the current official LE build is missing these:

Bluetooth: HCI UART driver ver 2.3
Bluetooth: HCI UART protocol H4 registered
Bluetooth: HCI UART protocol Three-wire (H5) registered
Bluetooth: HCI UART protocol BCM registered

and ends after:

Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized

Quote from milhouse

Can you both ( Soringo + Grimson) post the /flash/config.txt you are using with LE? RPi3 Bluetooth is working for me...

For testing purposes I used a fresh SD card and the current 6.90.004 image from the downloads page, so my config.txt was completely unmodified. Test builds were created with a clean build from the current master branch and updated using the .tar file, so config.txt hasn't been touched.

Quote from Soringo

Thank you.

No problem.

@Developers
I'm pretty sure I found the culprit, it's this patch:

From bc34eb8e494f45f0a18c56603f3d06e378035fb7 Mon Sep 17 00:00:00 2001
From: Phil Elwell <[email protected]>
Date: Sat, 19 Mar 2016 16:51:37 +0000
Subject: [PATCH 205/212] BCM270X_DT: Remove explicit claiming of UART pins

in "linux-01-RPi_support.patch". If I remove it, and rebuild LE, Bluetooth is working fine.

So, after a lot of comparing the commits between OE and LE without finding anything helpfull I started a shot in the dark and replaced the bootloader and dtb files from LE with the one from OE, and Bluetooth started working. So I did a binary compare and found that the only file that differs between OE and LE is "bcm2710-rpi-3-b.dtb". So something is wrong with the bcm2710-rpi-3-b.dtb file used by LE.

As a workaround you can download the OE 7 beta tar file, extract the bcm2710-rpi-3-b.dtb from it's "3rdparty/bootloader" directory and replace the one on the SD card with it.

Yep, I can confirm that Bluetooth isn't working with the current LibreELEC build, though it does work with the OE7 beta.

Go to the "Services" settings and turn Bluetooth on first.

Quote from zosky

looks like it didn't make it

From the Downloads page:

Quote

NB: Several users have reported an OpenELEC logo still present on the LibreELEC settings app. This is due to Kodi caching the logo in its texture cache. The Kodi caching algorithm will eventually cycle the content in the cache and then the LibreELEC logo will appear

Quote from Ne0

depends on the platform:

Generic:
LibreELEC.tv/linux.x86_64.conf at master · LibreELEC/LibreELEC.tv · GitHub

RPi:
linux.arm.conf
soon to be updated RPi/RPi2: Linux 4.4.6 and Kodi Jarvis updates by MilhouseVH · Pull Request #78 · LibreELEC/LibreELEC.tv · GitHub

WeTek:
LibreELEC.tv/linux.arm.conf at master · LibreELEC/LibreELEC.tv · GitHub

...

Display More

The comments in these conf files are a bit misleading. For example Generic and RPi1/2/3 are at 4.4.6 (the pull request is only for updating the patches not for the kernel itself), you can easily check by looking at the package file: LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

I'm running a build freshly generated from the git master branch on my Pi3 and can't reproduce this issue. Is there anything in the logs? It could be file corruption on the SD card.

Isn't the hard reset option from the LibreELEC settings equal to a clean install. If not ssh into the box, stop the kodi service and manually delete everyhing in /storage. This will give you a clean install, as the whole OS is in a monolithic file so you don't need to worry about any leftover system files.

Thank you!

Quote from chewitt

Do you really need to custom build? .. You get stronger security (not just obscurity) and easier access if you add your SSH public key to authorized_hosts and disable password auth, and you can also set auto-update to manual and disable update notifications.

I'll have a look at replicating OE's behaviour with some nginx redirect fu on the webserver. Some RTFM is required

I'm not a big fan of key based authorization. I prefer strong passwords, IMHO a strong password with a regular change is as (if not even more, think Heartbleed) secure as key based authorization and is less of a hassle when working with different SSH clients on different operating systems.

Additionally with BT on the RPI3 I'll probably turn it into an home automation central, and I don't think you intend to add stuff like this into your official build.

Can't help you with nginx as I'm an apache guy, but thanks for looking into it.

Quote from Tolotos

The official alpha is not available as IMG - how can I create a USB-Stick for installation of a new HTPC from the tar file?
Just format as FAT32 and extract the jar to the stick?

The answer is a few posts above your question.

Quote from xbs

You can also label the partition Storage and use disk=LABEL=Storage

Labels can be duplicated as well, UUIDs are the safest way.

Quote from H0nch0

how did you do this as in use MicroSD just for boot then use the SSD for rest ?
any guide you have would be great

Read here: OpenELEC Mediacenter - OpenELEC Forum - Raspberry Pi USB boot/storage - THE RIGHT WAY! (1/5) it's the same for LE, or any other OS on the Raspy.

Hello,

seeing as almost all the active OE developers have switched here I'm thinking of switching to LibreELEC. But I prefer to build OE/LE by myself, to keep on the edge of things, and more importantly to not have a device with a default SSH password in my home. Additionally I give my (personal) builds a much higher version number to prevent an accidental update to a public build.

Now with OE this is not a problem, with LE this fails because it can't download some sources from sources.libreelec.tv. After checking Index of / I found that the OE webserver defaults any download request into the "devel" directory, while LE webserver quits with an 404 error if the requested directory doesn't exist.

Would you be so kind to change the behaviour of the LE webserver to match the OE one?

If not it's no big deal, just means I'll have to patch the buildsystem myself.

Thanks for reading, no matter how you decide.