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

[email protected]
Newsgroups org.kernel.vger.linux-bluetooth
Message-ID <[email protected]/>
https://bugzilla.kernel.org/show_bug.cgi?id=221832

--- Comment #9 from IQ ([email protected]) ---
.
[  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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.