I learned how to enable kernel debug flags, this is my result in dmesg when I specifically run
`sudo rfkill unblock [target_rfkill_id]`, where the target id is "asus_wlan" on my laptop. ------ [32267.286227] asus_wmi: asus_wmi_evaluate_method3 called (0x53545344) with args: 0x00010011, 0x00000000, 0x00000000 [32267.286245] asus_wmi: Result: 0x00050000 [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 Furthermore, the idiom for all rfkill messages (bluetooth, phy0, etc) appears to generate two ACPI-BIOS communication messages: Send some kind of preliminary [0x53545344] call, get back 0x00050000 (presumably OK). This appears to be some kind of status check? I don't know hardware and it appears to be proprietary, I can't find information online about this, but this is how every other function worked. Then, do the *actual* set call, e.g. [0x53564544]. Which fails per the silent misdirection, as noted. I have an Asus Vivobook S14 WUXGA OLED 1TB SSD 32GB RAM, should be one of the first results on google atm. I do not have a WLAN LED on my laptop anywhere. This happens on kernel version 6.13.7 for Arch. Haven't tested on ubuntu or NixOS, but fairly certain this is reproducible. --- Again, there's plenty of comments in the kernel source saying that they needed to do this WLAN setting workaround, so there must be *a* reason for this, but I'm more confident now that this is the bug. Again, don't know hardware, so I don't know the fix, as I don't know the original reason for the hackaround. And it seems like all of this documentation is proprietary? I have no idea how people reverse-engineered this before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2092283 Title: wifi soft blocked by asus_nb_wmi on asus vivobook s14 oled Q423SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
