Bug 1916104 - Bluetooth: hci0: don't support firmware rome 0x1020200
Summary: Bluetooth: hci0: don't support firmware rome 0x1020200
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1916464 (view as bug list)
Depends On:
Blocks: 1909976
TreeView+ depends on / blocked
 
Reported: 2021-01-14 08:32 UTC by primoz.korosec
Modified: 2021-02-27 22:32 UTC (History)
23 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-02-27 22:32:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel logs (103.19 KB, text/plain)
2021-01-14 08:32 UTC, primoz.korosec
no flags Details

Description primoz.korosec 2021-01-14 08:32:10 UTC
Created attachment 1747320 [details]
kernel logs

1. Please describe the problem:
Bluetooth doesn't work.

2. What is the Version-Release number of the kernel:
5.10.6-200.fc33.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Stopped working after upgrade to the above mentioned kernel version

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Every time I enable bluetooth through gnome settings there is an error when printing dmesg: Bluetooth: hci0: don't support firmware rome 0x1020200
Lsusb lists IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Will try if asked.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
VMware Player's vmmon and vmnet

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 2 Jeremy Nickurak 2021-02-17 18:54:19 UTC
Notably a commit has patch is available in that bugzilla and  in linux-bluetooth, and a fix has been "applied for bluetooth-next". 
 https://lore.kernel.org/linux-bluetooth/CA2C8796-11CA-4E6F-A603-AE764516C850@holtmann.org/t/#u

Maybe some of these needs to be pulled into fedora via patches?

Comment 3 Hans de Goede 2021-02-18 13:52:32 UTC
I've added the upstream patch:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=234f414efd1164786269849b4fbb533d6c9cdbbf

Fixing this as a downstream patch for the Fedora kernels. So this should be fixed in the next F32 and F33 kernel builds, which will likely be the 5.10.18 builds.

Comment 4 Hans de Goede 2021-02-24 08:47:10 UTC
*** Bug 1916464 has been marked as a duplicate of this bug. ***

Comment 5 Hans de Goede 2021-02-24 08:51:22 UTC
This is fixed in kernel-5.10.18-200.fc33, which should become available in the updates-testing repo soon.

If you want you can grab it directly from koji (our buildsystem) here:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1714274


Note You need to log in before you can comment on or make changes to this bug.