** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-raspi (Ubuntu Eoan)
** Also affects: linux-raspi2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux-raspi2 (Ubuntu Eoan)
** Also affects: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Eoan)
Importance: Undecided
Status: New
** No longer affects: linux-raspi (Ubuntu Eoan)
** No longer affects: linux-raspi2 (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1862831
Title:
hciattach on rpi4 times out on first attempt
Status in linux-raspi package in Ubuntu:
New
Status in linux-raspi2 package in Ubuntu:
New
Status in linux-raspi2 source package in Eoan:
New
Status in linux-raspi source package in Focal:
New
Bug description:
I've observed this in both armhf and arm64 on:
19.10.1-server
18.04.4-server
core18
It does not seem to happen on rpi3, only on rpi4.
If you want to use Bluetooth on rpi, one must first run:
$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow
On RPI4, this results in a timeout on the first attempt. Reattempting
it right after will work though, 100% of the times I've tried it.
In the failed attempt, the output is:
bcm43xx_init
Initialization timed out.
And the following is the only new message to show up in dmesg when this fails:
[ 270.303691] uart-pl011 fe201000.serial: no DMA platform data
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1862831/+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
