Bluetooth controller not detected on CM4

Bug #1921915 reported by Dave Jones
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pi-bluetooth (Ubuntu)
Fix Released
Medium
Dave Jones
Focal
Fix Released
Medium
William Wilson
Groovy
Fix Released
Medium
William Wilson
Hirsute
Fix Released
Medium
Dave Jones

Bug Description

[Impact]

Without these patches, Bluetooth is inoperable on the CM4

[Test Case]

* Boot an ubuntu image (server/desktop) on a Pi CM4
* "sudo apt update"
* "sudo apt upgrade"
* If on server (not desktop)
  - "sudo apt install pi-bluetooth"
  - "sudo reboot"
* "bluetoothctl"
* "list" (show all available controllers) and verify there is no output
* Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
* "sudo apt install pi-bluetooth"
* "sudo reboot" (required as bluetooth initialization only occurs during udev activation)
* "bluetoothctl"
* "list" and verify there is a single available bluetooth controller
* "scan on" and bring another discoverable bluetooth device in range; verify it is reported under bluetoothctl

[Regression Potential]

The main concern would be the backported versions of pi-bluetooth not integrating well with other packages. We are mitigating this concern by also SRUing Bluez and linux-firmware-raspi2 to focal and groovy.

[Original Description]
Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues:

* The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured)

* The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4".

The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime.

Dave Jones (waveform)
Changed in pi-bluetooth (Ubuntu):
assignee: nobody → Dave Jones (waveform)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pi-bluetooth - 0.1.15ubuntu2

---------------
pi-bluetooth (0.1.15ubuntu2) hirsute; urgency=medium

  * Merged upstream fixes for CM4 and Pi 400 (LP: #1921915)

 -- Dave Jones <email address hidden> Tue, 30 Mar 2021 15:35:28 +0100

Changed in pi-bluetooth (Ubuntu Hirsute):
status: New → Fix Released
Changed in pi-bluetooth (Ubuntu Groovy):
assignee: nobody → William Wilson (jawn-smith)
Changed in pi-bluetooth (Ubuntu Focal):
assignee: nobody → William Wilson (jawn-smith)
Changed in pi-bluetooth (Ubuntu Focal):
status: New → In Progress
Changed in pi-bluetooth (Ubuntu Groovy):
status: New → In Progress
Revision history for this message
William Wilson (jawn-smith) wrote :
Revision history for this message
William Wilson (jawn-smith) wrote :
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Dave, or anyone else affected,

Accepted pi-bluetooth into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pi-bluetooth/0.1.15ubuntu1.1~20.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in pi-bluetooth (Ubuntu Groovy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-groovy
Dave Jones (waveform)
description: updated
Mathew Hodson (mhodson)
Changed in pi-bluetooth (Ubuntu):
importance: Undecided → Medium
Changed in pi-bluetooth (Ubuntu Focal):
importance: Undecided → Medium
Changed in pi-bluetooth (Ubuntu Groovy):
importance: Undecided → Medium
Changed in pi-bluetooth (Ubuntu Hirsute):
importance: Undecided → Medium
Revision history for this message
William Wilson (jawn-smith) wrote :
Download full text (4.7 KiB)

The verification passed for Groovy.

******* On Pi 400 **********

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
     0.1.15ubuntu1.1~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
 *** 0.1.15ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages
        100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
     4-0ubuntu0~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages
        100 /var/lib/dpkg/status
     2-0ubuntu2 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1.1~20.10.1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
 *** 0.1.15ubuntu1.1~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
        100 /var/lib/dpkg/status
     0.1.15ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages
linux-firmware-raspi2:
  Installed: 4-0ubuntu0~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
 *** 4-0ubuntu0~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
        100 /var/lib/dpkg/status
     3-0ubuntu2~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages
     2-0ubuntu2 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages
ubuntu@ubuntu:~$ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:F6:84:4E Pairable: yes
[bluetooth]# devices
[bluetooth]# list
Controller DC:A6:32:F6:84:4E ubuntu [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:F6:84:4E Discovering: yes
[NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M
[NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade
[NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0
[bluetooth]#

********* On CM4 **********
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
  Installed: 0.1.15ubuntu1
  Candidate: 0.1.15ubuntu1.1~20.10.1
  Version table:
     0.1.15ubuntu1.1~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
 *** 0.1.15ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages
        100 /var/lib/dpkg/status
linux-firmware-raspi2:
  Installed: 3-0ubuntu2~20.10.1
  Candidate: 4-0ubuntu0~20.10.1
  Version table:
     4-0ubuntu0~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages
 *** 3-0ubuntu2~20.10.1 500
        500 http://ports.ubuntu.com/ubuntu-ports groovy-upd...

Read more...

tags: added: verification-done verification-done-groovy
removed: verification-needed verification-needed-groovy
Changed in pi-bluetooth (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pi-bluetooth - 0.1.15ubuntu1.1~20.10.1

---------------
pi-bluetooth (0.1.15ubuntu1.1~20.10.1) groovy; urgency=medium

  * Merged upstream fixes for CM4 and Pi 400 (LP: #1921915)

 -- William 'jawn-smith' Wilson <email address hidden> Mon, 26 Apr 2021 09:40:19 -0500

Changed in pi-bluetooth (Ubuntu Groovy):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for pi-bluetooth has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Changed in pi-bluetooth (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers