From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221832] MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16
Date: Tue, 04 Aug 2026 17:45:46 +0000 [thread overview]
Message-ID: <bug-221832-62941-sTv44thfYA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221832-62941@https.bugzilla.kernel.org/>
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.
next prev parent reply other threads:[~2026-08-04 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 20:11 [Bug 221832] New: MT7925 (Foxcon T99H493.03) BT missing in lsusb on Vivobook S16 bugzilla-daemon
2026-08-04 12:23 ` [Bug 221832] " 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 [this message]
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-sTv44thfYA@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