RT3290 Bluetooth not finding any device

Bug #1913859 reported by Piyush Santosh Mhatre
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Piyush Santosh Mhatre

Bug Description

Ubuntu :- 20.04
Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device.
Outout of command :- service bluetooth status

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
     Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
       Docs: man:bluetoothd(8)
   Main PID: 1389 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4514)
     Memory: 2.0M
     CGroup: /system.slice/bluetooth.service
             └─1389 /usr/lib/bluetooth/bluetoothd

Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
lines 1-18/18 (END)

Output of command :- sudo btmgmt info

Index list with 1 item
hci0: Primary controller
    addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x000000
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys
    current settings: powered bondable ssp br/edr
    name Piyush-X55C

Output of command :- bluetoothctl

Agent registered
[bluetooth]# scan on
[bluetooth]# discoverable on
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]#

Output of command :- sudo btmgmt find

Unable to start discovery. status 0x0c (Not Supported)

Output of command :- lspci -knn | grep Net -A3; lsusb

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
    Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055]
    Kernel driver in use: rt2800pci
    Kernel modules: rt2800pci
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of command :-dmesg | grep -i bluetooth

 [ 12.851854] Bluetooth: Core ver 2.22
    [ 12.851883] Bluetooth: HCI device and connection manager initialized
    [ 12.851888] Bluetooth: HCI socket layer initialized
    [ 12.851889] Bluetooth: L2CAP socket layer initialized
    [ 12.851893] Bluetooth: SCO socket layer initialized
    [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1102 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [ 81.668783] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 81.668785] Bluetooth: BNEP filters: protocol multicast
    [ 81.668791] Bluetooth: BNEP socket layer initialized
    [ 1965.556683] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298
    [ 1965.556685] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0
    [ 1965.556687] Bluetooth: DynamicAlloc pci_device_id table at 0x00000000ad8b89c2 with size 64
    [ 1965.556688] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298
    [ 1965.556689] Bluetooth: Convert: vendor=0x1814, device=0x3298
    [ 1965.556690] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0
    [ 1965.556691] Bluetooth: pci_device_id: vendor=0x1814, device=0x3298
    [ 1965.556922] Bluetooth: rtbt_pci_probe(): PCI Dev(0000:02:00.1) get resource at 0xf7d00000,VA 0xffffa64041d80000,IRQ 17.
    [ 1965.556935] Bluetooth: call dev_ops->dev_ctrl_init!
    [ 1965.556951] Bluetooth: call dev_ops->dev_resource_init!
    [ 1965.582792] Bluetooth: RtmpOSIRQRequest(): request_irq (IRQ=17)done, isr_handler=0xffffffffc1274640!
    [ 1968.792846] Bluetooth: hci0: command 0x0c52 tx timeout
    [ 1968.832504] Bluetooth: rtbt_hci_dev_flush(dev=0xffff8ea3907f4000)
    [ 1968.900515] Bluetooth: RFCOMM TTY layer initialized
    [ 1968.900525] Bluetooth: RFCOMM socket layer initialized
    [ 1968.900534] Bluetooth: RFCOMM ver 1.11
    [ 1971.898810] Bluetooth: RtmpOSIRQRequest(): request_irq (IRQ=17)done, isr_handler=0xffffffffc1274640!
    [ 1975.160848] Bluetooth: hci0: command 0x0c1a tx timeout

description: updated
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1913859/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
tags: added: kernel-bug package-conflict
removed: bot-comment
Revision history for this message
Jeremy (wa113y3s) wrote :

I don't think this is an Ubuntu issue, file an issue at github where you got the bluetooth driver

Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

Have you seen the output of bluetoothctl I have given?

Revision history for this message
Jeremy (wa113y3s) wrote :

Yes, you obviously have a driver issue along with a Bluez version that was installed via a snap package that is getting blocked by apparmor

You should run in terminal apport-collect 1913859

no longer affects: ubuntu
tags: added: focal
Changed in bluez (Ubuntu):
status: New → Incomplete
status: Incomplete → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report.

Indeed if you installed the driver yourself then we can't support it via an Ubuntu task, so that makes it 'Invalid'. But it looks like Ubuntu 20.04.1 does have the 'rt2800pci' driver built-in if you install its latest 5.8 kernel. Please try that via:

  sudo apt update
  sudo apt install linux-generic-hwe-20.04
  Reboot.

Then if you still have any issues, please open a new bug by running:

  ubuntu-bug bluez

Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

I ran the command apport-collect 1913859 and it gives me no additional info collected. @Jeremy(wa113y3s)

Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

Thankyou @Daniel I ran command given by you and It replied that the linux-generic-hwe-20.04 is already installed. Then I ran the last command that you have given and it says that I have two versions of blueman one is stable directs to launch pad web site and gives me this :-
[
Lost something?
This page does not exist, or you may not have permission to see it.

If you have been to this page before, it is possible it has been removed.

Check that you are logged in with the correct account, or that you entered the address correctly, or search for it:
]
The other versions bug is submitted succesfully.

Changed in bluez (Ubuntu):
status: Invalid → In Progress
assignee: nobody → Piyush Santosh Mhatre (piyush-m)
Changed in bluez (Ubuntu):
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.