From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219786] asus-wmi: WLAN is permanently soft-blocked on S5406SA, but can still connect to networks
Date: Thu, 01 May 2025 12:35:58 +0000 [thread overview]
Message-ID: <bug-219786-215701-PcPLHJ4x00@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219786-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219786
--- Comment #11 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
bugreporter23 in case your wondering, this part of your logs:
[32267.286227] asus_wmi: asus_wmi_evaluate_method3 called (0x53545344) with
args: 0x00010011, 0x00000000, 0x00000000
[32267.286245] asus_wmi: Result: 0x00050000
Shows that a get status (0x53545344) on the wlan-devid (0x00010011) returns
0x00050000 since 0x00050000 has ASUS_WMI_DSTS_BIOS_BIT (0x00040000) set and
more importantly, does not have ASUS_WMI_DSTS_USER_BIT (0x00020000) set, the
device-set (0x53564544) call should also be done on the wlan-devid
(0x00010011).
But the logs show that instead this is being done on the wlan-led-devid
(0x00010012):
[32267.287502] asus_wmi: asus_wmi_evaluate_method3 called (0x53564544) with
args: 0x00010012, 0x00000001, 0x00000000
[32267.287508] asus_wmi: Result: 0xfffffffe
[32267.287511] asus_wmi: asus_wmi_evaluate_method3, (0x53564544), arg
0x00010012 failed: -19
The use of the wlan-led-devid instead of the wlan-devid is caused by
wlan_ctrl_by_user wrongly getting set when the get status call returns
0x00050000 and that is what my patch fixes.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-05-01 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-219786-215701@https.bugzilla.kernel.org/>
2025-05-01 8:09 ` [Bug 219786] asus-wmi: WLAN is permanently soft-blocked on S5406SA, but can still connect to networks bugzilla-daemon
2025-05-01 11:26 ` bugzilla-daemon
2025-05-01 11:36 ` bugzilla-daemon
2025-05-01 12:29 ` bugzilla-daemon
2025-05-01 12:35 ` bugzilla-daemon [this message]
2025-05-01 12:40 ` bugzilla-daemon
2025-05-01 13:18 ` bugzilla-daemon
2025-05-01 13:25 ` bugzilla-daemon
2025-05-01 13:29 ` bugzilla-daemon
2025-05-01 13:41 ` bugzilla-daemon
2025-05-03 20:13 ` 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-219786-215701-PcPLHJ4x00@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.