Bluetooth device not working (Raspberry Pi 3 - Leap 42.2)

First, I just want to say thanks for getting a 64 bit version of Linux working on the Pi 3. I’ve been wanting to learn some armv8 64bit assembly, now I have a board and OS to practice on.

I installed this image, openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2017.02.02-Build1.14.raw.xz, yesterday. Everything is working fine now (after fixing the WiFi) except for the bluetooth device. It’s not showing up with the following commands:


edge-case@waterdeep:~> systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-03-16 16:08:59 CDT; 17h ago
     Docs: man:bluetoothd(8)
 Main PID: 1262 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 512)
   CGroup: /system.slice/bluetooth.service
           └─1262 /usr/lib/bluetooth/bluetoothd
edge-case@waterdeep:~> hcitool dev
Devices:
edge-case@waterdeep:~> 
edge-case@waterdeep:~> bluetoothctl 
[bluetooth]# power on
No default controller available
[bluetooth]# exit
edge-case@waterdeep:~> sudo hcitool dev
Devices:
edge-case@waterdeep:~> sudo bluetoothctl 
[bluetooth]# power on
No default controller available
[bluetooth]# 

I checked to see if I was a member of the bluetooth group, I am not, however there is not a bluetooth group in /etc/group. Perhaps OpenSUSE is different from debian in that regard?

Is it a known issue that the internal bluetooth is not working, and are there any solutions to get it working by any chance?

Thank you,
edge-case

On Fri 17 Mar 2017 02:56:01 PM CDT, edge case wrote:

First, I just want to say thanks for getting a 64 bit version of Linux
working on the Pi 3. I’ve been wanting to learn some armv8 64bit
assembly, now I have a board and OS to practice on.

I installed this image,
openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2017.02.02-Build1.14.raw.xz,
yesterday. Everything is working fine now (after fixing the WiFi) except
for the bluetooth device. It’s not showing up with the following
commands:

Code:

edge-case@waterdeep:~> systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled;
vendor preset: disabled) Active: active (running) since Thu 2017-03-16
16:08:59 CDT; 17h ago Docs: man:bluetoothd(8)
Main PID: 1262 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 512)
CGroup: /system.slice/bluetooth.service
└─1262 /usr/lib/bluetooth/bluetoothd
edge-case@waterdeep:~> hcitool dev
Devices:
edge-case@waterdeep:~>
edge-case@waterdeep:~> bluetoothctl
[bluetooth]# power on
No default controller available
[bluetooth]# exit
edge-case@waterdeep:~> sudo hcitool dev
Devices:
edge-case@waterdeep:~> sudo bluetoothctl
[bluetooth]# power on
No default controller available
[bluetooth]#


I checked to see if I was a member of the bluetooth group, I am not,
however there is not a bluetooth group in /etc/group. Perhaps OpenSUSE
is different from debian in that regard?

Is it a known issue that the internal bluetooth is not working, and are
there any solutions to get it working by any chance?

Thank you,
edge-case

Hi
See section 4.1 here (SLES 12 Aarch64 and Leap 42.2 are the same level);
https://www.suse.com/documentation/suse-best-practices/sles-rpi-quick/data/sles-rpi-quick.html


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.38-50-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

I suspect something in my install is incomplete - I get

sudo hciattach /dev/ttyAMA0 bcm43xx 921600
root's password:
bcm43xx_init
Cannot open directory '/etc/firmware': No such file or directory
Patch not found, continue anyway
Set Controller UART speed to 921600 bit/s
Device setup complete

but the bcm43 goodness is in /lib/firmware/brcm

locate bcm43xx
/lib/firmware/LICENCE.broadcom_bcm43xx
/lib/firmware/brcm/bcm43xx-0.fw
/lib/firmware/brcm/bcm43xx_hdr-0.fw

/lib/firmware/brcm also seems to include some audio goodness but I can’t get any audio despite adding dtparam=audio=on to config.txt - is it still the case no audio possible even on the jack? (I expect hdmi likely to take even longer.)

Hi,
same situation for me, Bluetooth device not working. That is my response to systemctl status bluetooth:

systemctl status bluetooth -l
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2017-08-01 12:25:46 CEST; 9min ago
Docs: man:bluetoothd(8)
Main PID: 2692 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 512)
CGroup: /system.slice/bluetooth.service
└─2692 /usr/lib/bluetooth/bluetoothd

Aug 01 12:25:46 linux.suse systemd[1]: Starting Bluetooth service…
Aug 01 12:25:46 linux.suse bluetoothd[2692]: Bluetooth daemon 5.41
Aug 01 12:25:46 linux.suse systemd[1]: Started Bluetooth service.
Aug 01 12:25:46 linux.suse bluetoothd[2692]: Starting SDP server
Aug 01 12:25:46 linux.suse bluetoothd[2692]: Bluetooth management interface 1.10 initialized
Aug 01 12:25:46 linux.suse bluetoothd[2692]: Failed to obtain handles for “Service Changed” characteristic
Aug 01 12:25:46 linux.suse bluetoothd[2692]: Sap driver initialization failed.
Aug 01 12:25:46 linux.suse bluetoothd[2692]: sap-server: Operation not permitted (1)

Give a look at my BD Address, it-s a default address. it seems like openSUSE doesn-t recognize my BLE component.
Can this be a plausible cause?

hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: AA:AA:AA:AA:AA:AA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1520 acl:0 sco:0 events:96 errors:0
TX bytes:1354 acl:0 sco:0 commands:92 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: ‘linux.suse’
Class: 0x000104
Service Classes: Unspecified
Device Class: Computer, Desktop workstation
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)

Thank you all for your support,
Marco

I’m sorry for text errors, but I’m writing from a rpi3 with a 7inches lcd that doesn’t always work well.

Marco

Hi Marco
Is this on leap 42.2?

Hi Malcom,

yes Leap 42.2.

cat /etc/os-release
NAME=“openSUSE Leap”
VERSION=“42.2”
ID=opensuse
ID_LIKE=“suse”
VERSION_ID=“42.2”
PRETTY_NAME=“openSUSE Leap 42.2”
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:opensuse:leap:42.2”
BUG_REPORT_URL=“https://bugs.opensuse.org
HOME_URL=“https://www.opensuse.org/

NOTE: May it could help. few days ago I run sudo zypper dup in the hope of solving the BLE problem.

Hi
OK, weird (since it works fine on SLES 12 RPI), so…

When you run the command;


linux:~ # hciattach /dev/ttyAMA0 bcm43xx 921600
bcm43xx_init
Cannot open directory '/etc/firmware': No such file or directory
Patch not found, continue anyway
Set Controller UART speed to 921600 bit/s
Device setup complete

It’s looking in /etc/firmware (a bug)… so lets make it happy…


mkdir -p /etc/firmware
ln -s /lib/firmware/BCM43430A1.hcd /etc/firmware/BCM43430A1.hcd
systemctl reboot

When the system is back up…


hciattach /dev/ttyAMA0 bcm43xx 921600
bcm43xx_init
Set Controller UART speed to 921600 bit/s
Flash firmware /etc/firmware/BCM43430A1.hcd
Initialization timed out.

hciattach /dev/ttyAMA0 bcm43xx 921600
bcm43xx_init
Patch not found, continue anyway
Set Controller UART speed to 921600 bit/s
Device setup complete

hciconfig -a
hci0:   Type: Primary  Bus: UART
BD Address: B1:57:FB:D1:29:39  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN
RX bytes:654 acl:0 sco:0 events:33 errors:0
TX bytes:419 acl:0 sco:0 commands:33 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT

hciconfig hci0 up
hcitool scan
Scanning ...
XX:XX:XX:XX:XX:XX       iPhone


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

SOLVED!!!

Now BLE works.
Thank you very much Malcom.

Kind regards,
Marco

On Wed 02 Aug 2017 07:16:01 AM CDT, mgoldfinch wrote:

SOLVED!!!

Now BLE works.
Thank you very much Malcom.

Kind regards,
Marco

Hi
Well not really, seems it’s bluez is missing patches so will open a bug
report…


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Hi
Bug reference: https://bugzilla.opensuse.org/show_bug.cgi?id=1051874