[Bug 221832] New: MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[Bug 221832] New: MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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.

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Artem S. Tashkinov (aros@gmx.com) ---
This is a really old kernel.

Please install the latest firmware and try either 7.1.6 or 7.2-rc6.

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #2 from IQ (lnxps@bbtex.net) ---
(In reply to Artem S. Tashkinov from comment #1)
> This is a really old kernel.
> 
> Please install the latest firmware and try either 7.1.6 or 7.2-rc6.

same thing: tried, 7.2-rc5, nothing shows in lsusb, WIfi works.

Latest firmware installed, it loads for Wifi but BT is not found.

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #3 from IQ (lnxps@bbtex.net) ---
on the QCNFA765 2230/E card BT worked (it is supposed to be USB attached) but
Wifi didn't (could not init the Wifi card). 

I was thinking maybe there are no USB pins routed to the M.2/E slot on Asus
Vivobook S16, however QCNFA765 has USB BT, unless this is something propietary?

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #4 from IQ (lnxps@bbtex.net) ---
root@A16:~# uname -a
Linux A16 7.2.0-rc5 #1 SMP PREEMPT_DYNAMIC Sun Aug  2 13:19:20 EST 2026 aarch64
aarch64 aarch64 GNU/Linux

root@A16:~# lsusb
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:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.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

root@A16:~# lspci
0004:00:00.0 PCI bridge: Qualcomm Technologies, Inc Device 0111
0004:01:00.0 Network controller: MEDIATEK Corp. Device 0717
0006:00:00.0 PCI bridge: Qualcomm Technologies, Inc Device 0111
0006:01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd.
RTS5772DL NVMe SSD Controller (DRAM-less) (rev 01)
root@A16:~#

why nothing appears in lsusb? If the btusb driver is too old it would at least
show a device id...

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #5 from IQ (lnxps@bbtex.net) ---
extract from dmesg: (it is trying to init wcn7850)

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x512f0011]
[    0.000000] Linux version 7.2.0-rc5 (root@A16) (gcc (Ubuntu 14.2.0-4ubuntu2)
14.2.0, GNU ld (GNU Binutils for Ubuntu) 2.43.1) #1 SMP PREEMPT_DYNAMIC Sun Aug
 2 13:19:20 EST 2026
[    0.000000] KASLR disabled on command line
[    0.000000] Machine model: ASUS Vivobook S 15 X1P-42-100
[    0.000000] earlycon: efifb0 at I/O port 0x0 (options '')
[    0.000000] printk: legacy bootconsole [efifb0] enabled
[    0.000000] efi: EFI v2.9 by INSYDE Corp.
[    0.000000] efi: SMBIOS=0xd4462000 SMBIOS 3.0=0xd445f000
TPMFinalLog=0xd46e0000 ACPI 2.0=0xd47d3018 MEMATTR=0xd0a2a018 ESRT=0xcf3d8c98
TPMEventLog=0xd4771018 INITRD=0xc4845518 RNG=0xd47d3918 MEMRESERVE=0xc484a018
[    0.000000] random: crng init done
[    0.000000] esrt: Reserving ESRT space from 0x00000000cf3d8c98 to
0x00000000cf3d8d48.
[    0.000000] Skipping dt linux,cma-default node in favor for "cma=" kernel
param.
....
[    7.914566] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K,
limit 1024G
[    7.922145] Bluetooth: Core ver 2.22
[    7.922168] NET: Registered PF_BLUETOOTH protocol family
[    7.922170] Bluetooth: HCI device and connection manager initialized
[    7.922174] Bluetooth: HCI socket layer initialized
[    7.922176] Bluetooth: L2CAP socket layer initialized
[    7.922178] Bluetooth: SCO socket layer initialized
...
[    8.140142] Bluetooth: HCI UART driver ver 2.3
[    8.140149] Bluetooth: HCI UART protocol H4 registered
[    8.140150] Bluetooth: HCI UART protocol BCSP registered
[    8.140191] Bluetooth: HCI UART protocol LL registered
[    8.140192] Bluetooth: HCI UART protocol ATH3K registered
[    8.140220] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.140298] Bluetooth: HCI UART protocol Intel registered
[    8.140331] Bluetooth: HCI UART protocol Broadcom registered
[    8.140345] Bluetooth: HCI UART protocol QCA registered
[    8.140346] Bluetooth: HCI UART protocol AG6XX registered
[    8.140353] Bluetooth: HCI UART protocol Marvell registered
[    8.141317] Bluetooth: hci0: setting up wcn7850
...
[    9.335870] mt7925e_git 0004:01:00.0 mt0: renamed from wlan0
[   10.298232] Bluetooth: hci0: command 0xfc00 tx timeout
[   10.298495] Bluetooth: hci0: Reading QCA version information failed (-110)
[   10.298641] Bluetooth: hci0: Retry BT power ON:0
[   12.431550] Bluetooth: hci0: command 0xfc00 tx timeout
[   12.431967] Bluetooth: hci0: Reading QCA version information failed (-110)
[   12.432119] Bluetooth: hci0: Retry BT power ON:1
...
[   14.564761] Bluetooth: hci0: command 0xfc00 tx timeout
[   14.564997] Bluetooth: hci0: Reading QCA version information failed (-110)
[   14.565143] Bluetooth: hci0: Retry BT power ON:2
[   16.696488] Bluetooth: hci0: command 0xfc00 tx timeout
[   16.696679] Bluetooth: hci0: Reading QCA version information failed (-110)
[   18.829711] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[   18.829831] Bluetooth: hci0: command 0xfc00 tx timeout

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #6 from IQ (lnxps@bbtex.net) ---
Firmware loaded:

[ 5246.175029] (NULL device *): Loading firmware from
/lib/firmware/mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin
[ 5246.175030] (NULL device *): Loading firmware from
/lib/firmware/mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
[ 5246.175031] (NULL device *): direct-loading
mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
[ 5246.175032] (NULL device *): direct-loading
mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin
[ 5246.175033] firmware_class: fw_set_page_data:
fw-mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin fw_priv=0000000041074eba
data=000000009415c47a size=1254904
[ 5246.175036] firmware_class: fw_set_page_data:
fw-mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin fw_priv=00000000e254796b
data=00000000380b1f69 size=198112
[ 5246.175165] (NULL device *): Loaded FW:
mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin, sha256:
089dd0252a7eb95feed55950ad0fd9e6f751a07b4cf22273de722b73fa50d49e
[ 5246.175168] firmware_class: cache_firmware:
mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin ret=0
[ 5246.175829] (NULL device *): Loaded FW:
mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin, sha256:
7e4ed27d1e9fe21cdefda35a22da32137b2473fada350617fb603489af19346a
[ 5246.175832] firmware_class: cache_firmware:
mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin ret=0
[ 5246.177579] (NULL device *): Loading firmware from
/lib/firmware/updates/qcom/x1e80100/ASUSTeK/vivobook-s15/qccdsp8380.mbn
[ 5246.177584] (NULL device *): direct-loading
qcom/x1e80100/ASUSTeK/vivobook-s15/qccdsp8380.mbn
[ 5246.177587] firmware_class: fw_set_page_data:
fw-qcom/x1e80100/ASUSTeK/vivobook-s15/qccdsp8380.mbn fw_priv=000000005dd083df
data=000000005f4d150a size=3072424
[ 5246.179319] firmware_class: __free_fw_priv:
fw-qcom/x1e80100/ASUSTeK/vivobook-s15/qcadsp8380.mbn fw_priv=0000000088011a21
data=0000000000000000 size=0
[ 5246.179325] firmware_class: cache_firmware:
qcom/x1e80100/ASUSTeK/vivobook-s15/qcadsp8380.mbn ret=-2
[ 5246.179630] (NULL device *): Loaded FW:
qcom/x1e80100/ASUSTeK/vivobook-s15/qccdsp8380.mbn, sha256:
f98e3c974026f288994c12d218fafea7e77f03f6def183749a07d8a053a310fd
[ 5246.179633] firmware_class: cache_firmware:
qcom/x1e80100/ASUSTeK/vivobook-s15/qccdsp8380.mbn ret=0

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #7 from IQ (lnxps@bbtex.net) ---
I've tried the resolute 7.0.0 repo, this one doesn't even see the PCIe Wifi
component... quite a piece of crap

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #8 from IQ (lnxps@bbtex.net) ---
ps the DTB taken from 7.0.0 x1p42100-asus-vivobook-s15.dtb crashed the boot
process (not video output, screen black)

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

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

[Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16

[bugzilla-daemon]

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

--- Comment #9 from IQ (lnxps@bbtex.net) ---
.
[  121.044682] qcom-iris aa00000.video-codec: loading
/lib/firmware/qcom/x1p42100/ASUSTeK/vivobook-s15/qcvss8380.mbn.xz failed for no
such file or directory.
[  121.044728] qcom-iris aa00000.video-codec: Direct firmware load for
qcom/x1p42100/ASUSTeK/vivobook-s15/qcvss8380.mbn failed with error -2
[  121.044755] firmware_class: __free_fw_priv:
fw-qcom/x1p42100/ASUSTeK/vivobook-s15/qcvss8380.mbn fw_priv=000000001e317614
data=0000000000000000 size=0
[  121.044874] qcom-iris aa00000.video-codec: firmware download failed
[  121.117515] qcom-iris aa00000.video-codec: core init failed
[  122.269583] rfkill: input handler disabled
[  122.617337] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  122.996022] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  124.797661] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  124.896240] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  124.966805] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  125.315919] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  125.365047] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22
[  125.442740] msm_dpu ae01000.display-controller: [drm:adreno_load_gpu [msm]]
*ERROR* Couldn't power up the GPU: -22

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

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