public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214149] New: Bluetooth not working on MEDIATEK Corp. Device 7961
Date: Mon, 23 Aug 2021 18:32:08 +0000	[thread overview]
Message-ID: <bug-214149-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=214149

            Bug ID: 214149
           Summary: Bluetooth not working on MEDIATEK Corp. Device 7961
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.13.12
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: luxuridegaming@gmail.com
        Regression: No

Created attachment 298445
  --> https://bugzilla.kernel.org/attachment.cgi?id=298445&action=edit
Dmesg

> Bluetooth does not work on MEDIATEK Corp. Device 7961

> Wireless controller in lsusb
Bus 003 Device 003: ID 13d3:3563 IMC Networks Wireless_Device

> Wireless controller in lspci
02:00.0 Network controller: MEDIATEK Corp. Device 7961

> Blueman reports:
blueman-manager 19.55.31 ERROR    Manager:137 on_dbus_name_appeared: Default 
adapter not found, trying first available.

blueman-manager 19.55.31 ERROR    Manager:141 on_dbus_name_appeared: No
adapter(s) found, exiting

> Gnome bluetooth does not respond either

> Systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: disabled)
     Active: active (running) since Mon 2021-08-23 20:01:13 CEST; 8min ago
       Docs: man:bluetoothd(8)
   Main PID: 1994 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 47410)
     Memory: 2.4M
        CPU: 17ms
     CGroup: /system.slice/bluetooth.service
             └─1994 /usr/lib/bluetooth/bluetoothd

Aug 23 20:01:13 ArchZephyrus systemd[1]: Starting Bluetooth service...
Aug 23 20:01:13 ArchZephyrus bluetoothd[1994]: Bluetooth daemon 5.60
Aug 23 20:01:13 ArchZephyrus systemd[1]: Started Bluetooth service.
Aug 23 20:01:13 ArchZephyrus bluetoothd[1994]: Starting SDP server
Aug 23 20:01:13 ArchZephyrus bluetoothd[1994]: Bluetooth management interface
1.20 initialized

> Bluetooth in dmesg
[   29.293856] Bluetooth: Core ver 2.22
[   29.293892] Bluetooth: HCI device and connection manager initialized
[   29.293895] Bluetooth: HCI socket layer initialized
[   29.293897] Bluetooth: L2CAP socket layer initialized
[   29.293900] Bluetooth: SCO socket layer initialized
[   29.890810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.890815] Bluetooth: BNEP filters: protocol multicast
[   29.890819] Bluetooth: BNEP socket layer initialized

> Acording to dmesg and systemctl it looks like bluetooth should be working

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-08-23 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-214149-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox