Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221832] New: MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16
Date: Mon, 03 Aug 2026 20:11:10 +0000	[thread overview]
Message-ID: <bug-221832-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 221832
           Summary: MT7925 (Foxcon T99H493.03) BT missing in lsusb on
                    Vivobook S16
           Product: Drivers
           Version: 2.5
          Hardware: ARM
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: lnxps@bbtex.net
        Regression: No

Hi

I installed the Foxcon T99H493.03 2230/E card, Wifi shows up in lspci, however
nothing shows in lsusb. It is a Snapdragon X1P26100 laptop. Wifi works
correctly
(after disabling power management which was giving delays).

Previously it used QCNFA765 2230/E card (Wifi did not work on the stock kernel.

Linux A16 6.14-rc1-1-qcom-x1e #1 SMP PREEMPT_DYNAMIC Sat Feb  8 15:28:53 CET
2025 aarch64 aarch64 aarch64 GNU/Linux

The mt76 driver was updated from git to latest version, still same issue (no BT
usb).

Ideas?

0004:01:00.0 Network controller: MEDIATEK Corp. Device 0717
Subsystem: MEDIATEK Corp. Device 0717
Device tree node: /sys/firmware/devicetree/base/soc@0/pci@1c08000/pcie@0/wifi@0
Flags: bus master, fast devsel, latency 0, IRQ 224
Memory at 7c400000 (64-bit, non-prefetchable) [size=2M]
Memory at 7c300000 (64-bit, non-prefetchable) [size=32K]
Capabilities: [80] Express Endpoint, IntMsgNum 0
Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [200] Advanced Error Reporting
Kernel driver in use: mt7925e_git
Kernel modules: mt7925e, mt7925e_git

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

-- 
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:[~2026-08-03 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 20:11 bugzilla-daemon [this message]
2026-08-04 12:23 ` [Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16 bugzilla-daemon
2026-08-04 15:11 ` bugzilla-daemon
2026-08-04 17:12 ` bugzilla-daemon
2026-08-04 17:41 ` bugzilla-daemon
2026-08-04 17:43 ` bugzilla-daemon
2026-08-04 17:45 ` bugzilla-daemon
2026-08-05  4:17 ` bugzilla-daemon
2026-08-07  2:52 ` bugzilla-daemon
2026-08-07  2:53 ` bugzilla-daemon
2026-08-07 10:34 ` bugzilla-daemon

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-221832-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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