=== antoine6 is now known as antoine === chesty_ is now known as chesty === cpaelzer__ is now known as cpaelzer === cpaelzer__ is now known as cpaelzer [12:28] juergh, yo ho ... i have a pi3 here that is physically hard to reach, runs UC16 and i'm having a hard time getting bluetooth to work (i'D just re-install UC18 if i could, but would liek to avoid it) ... [12:28] juergh, seems the pi2-kernel snap is missing the required firmware: [12:28] Sep 18 14:22:43 stream kernel: Bluetooth: hci0: BCM (001.002.009) build 0000 [12:28] Sep 18 14:22:43 stream kernel: bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [12:28] Sep 18 14:22:43 stream kernel: Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [12:28] ogra@stream:~$ ls /lib/firmware/brcm/*.hcd [12:28] ls: cannot access '/lib/firmware/brcm/*.hcd': No such file or directory [12:29] do you think we could add it ?? [12:31] ogra@stream:~$ snap list|grep kernel [12:31] pi2-kernel 4.4.0-1139.148 117 latest/edge canonical* kernel [12:31] (stable misses it too, i only just updated to edge now) === cpaelzer__ is now known as cpaelzer [13:27] hey. we don't seem to be providing any BT firmware in xenial. [13:31] yes, thats what i see here ... [13:31] we should though 🙂 [13:44] and I presume you want that in bionic as well? [13:46] UC18 has it ... works fine there [13:46] oh, wait ... well, i personally dont care about classic bionic ... [13:47] not sure if we have many pi users there [13:47] but for UC16 it should work as it does in the other UCs [15:14] ogra: broadcom didn't license that bluetooth firmware for distribution [15:15] jeremy31, and thats the reason why it isnt in 16.04 but in all later releases ? [15:15] 🙂 [15:16] I haven't seen it in any Ubuntu version, I always just got it from a github site [15:17] it is in 18.04 and 20.04 ... (and the respective UbuntuCore releases ...) but not in UC16 [15:19] juergh, so i decided to find a ladder, climb on the roof of our house and replace the UC16 with UC18 on that pi3 ... it is working fine now, so unless someone else complains, just keep it as-is [15:19] I think Jesse Sung made the hex2hcd program that converted the windows firmware to hcd files. I have to get back to work [15:22] (it wasnt my plan to spend a full vacation day for simply attaching a BLE temp/humidity sensor to an existing Pi (and to do climbing sports !!!!), but well ... ) [17:38] ogra: yes, it's a license issue :P [17:40] ogra: i can only find one hcd file (/lib/firmware/brcm/BCM-0bb4-0306.hcd) in focal [17:40] well, i see it in UC18 (bionic based) [17:41] ogra@acheron:~$ ssh 192.168.2.85 [17:41] Welcome to Ubuntu Core 18 (GNU/Linux 5.3.0-1033-raspi2 armv7l) [17:41] Last login: Fri Sep 18 12:25:11 2020 from 192.168.2.48 [17:41] ogra@localhost:~$ ls /lib/firmware/brcm/*.hcd [17:41] /lib/firmware/brcm/BCM43430A1.hcd /lib/firmware/brcm/BCM4345C0.hcd [17:41] ... [17:42] and BLE works perfectly fine there (i run a lot of BLE beacon sensors around the house here, all of them attached to various Pi's running UC18 and node-red) [17:43] are they from linux-firmware-raspi2 ? [17:43] i think so, yeah [17:43] yes, those files come from linux-firmware-raspi2 [17:58] i thought the source of linux-firmware-raspi2 is from https://github.com/raspberrypi/firmware [17:58] but can't find the hcd files there [17:59] i'm curious about their license :) [18:10] wenchien, the source of linux-firmware-raspi2 is several things (which ought to be in separate packages, but time constraints blah blah); anyway, the bluetooth bits are from https://github.com/RPi-Distro/bluez-firmware and yes the licensing is ... "messy"