FS#74584 - [linux] asus-nb-wmi module failed to probe, causes multimedia keys become unusable
Attached to Project:
Arch Linux
Opened by Ahmad Raniri (ahmadraniri) - Friday, 29 April 2022, 01:42 GMT
Last edited by Toolybird (Toolybird) - Thursday, 14 September 2023, 01:33 GMT
Opened by Ahmad Raniri (ahmadraniri) - Friday, 29 April 2022, 01:42 GMT
Last edited by Toolybird (Toolybird) - Thursday, 14 September 2023, 01:33 GMT
|
Details
Description:
Starting with kernel 5.17.5-arch1-1 and 5.17 before, multimedia keys stop working. After dig into log, I found that asus-nb-wmi module is failed to probe. I try to manually load it with modprobe and insmod but always end up with `modprobe: ERROR: could not insert 'asus_nb_wmi': No such device`. The previous kernel 5.16 and 5.15 LTS work fine until 5.17 came up, So I assume that there's something wrong with it. I had exact similliar issue on fedora 36 with kernel 5.17 and it got fixed, link : https://bugzilla.redhat.com/show_bug.cgi?id=2079125 Additional info: * package version(s) - linux 5.17.5-arch1-1 * config and/or log files etc. - Attached. * link to upstream bug report, if any - I don't have one. Steps to reproduce: - Boot up the 5.17.5-arch1-1 kernel. - Login to DE and wayland compositors - Open pavucontrol. - Press multimedia keys / fn+F10/F11/F12 to toggle mute, set volume down/up, nothing happens - Reboot to 5.15 LTS kernel. - Login to DE and wayland compositors. - Open pavucontrol. - Press multimedia keys / fn+F10/F11/F12 to toggle mute, set volume down/up, it works. |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 14 September 2023, 01:33 GMT
Reason for closing: Upstream
Additional comments about closing: Clearly not an Arch packaging issue. If still happening with latest kernels, please report upstream and/or head to the proper Arch support channels (Forum, etc)
Thursday, 14 September 2023, 01:33 GMT
Reason for closing: Upstream
Additional comments about closing: Clearly not an Arch packaging issue. If still happening with latest kernels, please report upstream and/or head to the proper Arch support channels (Forum, etc)