[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models

William Wilson 1926378 at bugs.launchpad.net
Wed Apr 28 14:56:53 UTC 2021


** Description changed:

  [Impact]
  
   * Without the pi-bluetooth changes in hirsute, bluetooth will not work
  on the Pi 400 or CM4.
  
  [Test Case]
  
   * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
-  * Verify the command `bluetoothctl devices` fails with the
-    error "No default controller available"
+  * "bluetoothctl"
+  * "list" and verify there is no available bluetooth controller
+  * 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
   * Repeat the above steps for the CM4
  
  [Regression Potential]
  
  There are multiple changes being SRU'd, but since the linux-firmware-
  raspi2 and bluez packages are also being SRUd, the risk of regression
  should be fairly low. These changes have worked well in hirsute for some
  time.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1926378

Title:
  SRU pi-bluetooth from hirsute to focal to enable all models

Status in pi-bluetooth package in Ubuntu:
  New

Bug description:
  [Impact]

   * Without the pi-bluetooth changes in hirsute, bluetooth will not
  work on the Pi 400 or CM4.

  [Test Case]

   * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
   * "bluetoothctl"
   * "list" and verify there is no available bluetooth controller
   * 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
   * Repeat the above steps for the CM4

  [Regression Potential]

  There are multiple changes being SRU'd, but since the linux-firmware-
  raspi2 and bluez packages are also being SRUd, the risk of regression
  should be fairly low. These changes have worked well in hirsute for
  some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions



More information about the Ubuntu-sponsors mailing list