Public bug reported:
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.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
New
Bug 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
