RT3290 Bluetooth not finding any device

Bug #1914007 reported by Piyush Santosh Mhatre
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rtbth
New
Undecided
Unassigned

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 1 13:07:08 2021
InstallationDate: Installed on 2020-12-28 (34 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
InterestingModules: bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. X55C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=62c82d41-d10e-48a9-a811-d8abc1309b6a ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X55C.409
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X55C
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55C.409:bd01/09/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX55C:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55C:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X55C
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:

rfkill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for reporting the bug again.

Unfortunately because you're using a driver (rtbth kernel module) that's not from Ubuntu, we can't support it. So that makes this bug 'Invalid'.

I can see however that you didn't get much choice because it seems Ubuntu doesn't offer a driver for RTL3290 bluetooth. This issue is already covered by bug 1189721 so I will group it there.

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

Yeah I know that it might be a driver issue, but there no other option for me and I have gone through the given bug by you and its quite old and available for old kernal versions and I am a noob in these bugs and all and have no knowlwdge about this. I tried there given solution but I got errors in them and as I said (have no knowledge) don't know how to fix it.BTW Thanks.

Changed in bluez (Ubuntu):
status: New → Invalid
Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

Please suggest me a solution for this @Daniel.

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

And yeah in that given bug post there is a solution how to get working RT3290 but my problem is different my adapter is working but the agent Bluetoothctl is giving an error related to blueman so isn't it a different problem? @Daniel

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, you have a different problem caused by a driver that is not supported or provided by Ubuntu. That makes this bug Invalid for the 'Ubuntu' task.

My only suggestions are:

1. Subscribe to bug 1189721.

2. Try replacing the wireless card in the laptop with a different card, ideally made by Intel. Because it looks like RT3290 might never be supported in Linux.

Changed in bluez (Ubuntu):
status: Invalid → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is Invalid for Ubuntu. If you would like to track the problem that is in Ubuntu then please use bug 1189721.

affects: bluez (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Invalid
Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

How do I delete this?

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

Why are you making it invalid simply say it won't gonna fix. Try to understand that bug is different from this.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is 'Invalid' because the problem is not coming from any Ubuntu code. The problem is in the code you downloaded from Github:

  https://github.com/loimu/rtbth-dkms

which is also available in:

  https://launchpad.net/~blaze/+archive/ubuntu/rtbth-dkms

but doesn't seem to be supported either way :(

If you prefer, we can say 'Won't Fix'. That's not completely accurate but has the same effect. A bug being 'Invalid' does not mean it's not a bug. It certainly is a bug, but it is a bug that's not from Ubuntu. So that makes the Ubuntu bug status 'Invalid'.

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

Sorry for my misunderstanding :( so what changes should I make to this bug to make it valid. Because there is no other drivers for it.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It's probably not useful but since it's what you want I have registered https://launchpad.net/rtbth so we can track the problem in Launchpad now.

It's still not a valid Ubuntu bug but you can now track it in Launchpad.

affects: ubuntu → rtbth
Changed in rtbth:
status: Invalid → New
Revision history for this message
Piyush Santosh Mhatre (piyush-m) wrote :

Thankyou very much @Daniel 👍

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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