This bug was fixed in the package bluez - 5.53-0ubuntu3.1
---------------
bluez (5.53-0ubuntu3.1) focal; urgency=medium
* Add support for the pi 400 (LP: #1903048)
-- William 'jawn-smith' Wilson <william.wil...@canonical.com> Mon, 15
Mar 2021 19:25:22 +0000
** Changed in: bluez (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Focal:
Fix Released
Status in bluez source package in Groovy:
Fix Released
Status in bluez source package in Hirsute:
Fix Released
Bug description:
[Impact]
Without these patches, Bluetooth is inoperable on the recently
released Raspberry Pi 400.
[Test Case]
* Boot the Ubuntu Desktop for Pi image on a Pi 400.
* Start the Settings application and switch to the Bluetooth tab
* Verify that Bluetooth is not enabled and attempting to activate it fails
* Enable the -proposed repository for the release (groovy)
* sudo apt update
* sudo apt install bluez
* sudo reboot
* Start the Settings application and switch to the Bluetooth tab
* Verify that Bluetooth is active and that Bluetooth devices (e.g. mice,
mobile phones, headphones, etc.) can connect and operate correctly
[Regression Potential]
Extremely low (on groovy in particular, this has the same version of
bluez as hirsute). The only significant risk is to non-Pi platforms or
dongles which also use the Broadcom 43xx (or Cypress 305) chips for
Bluetooth which might be inadvertently affected by these patches.
[Original Description]
The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
Whilst wifi works happily, Bluetooth fails to operate. This doesn't
appear to be an issue with either the firmware (the latest versions
from upstream Raspbian have been tried), or the kernel (a known-good
raspi kernel has been tested under Ubuntu), but with Bluez itself.
Specifically, tracing the initialization with btmon on Raspbian and
Ubuntu, the stack consistently fails when attempting to "Set Default
PHY" on the latter. Curiously, under Ubuntu the adapter also appears
to lack a MAC address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
