[Bug 220882] New: mfd_aaeon incorrectly binds on ASUS TUF Gaming A16 (FA608UM), preventing asus_nb_wmi

[Bug 220882] New: mfd_aaeon incorrectly binds on ASUS TUF Gaming A16 (FA608UM), preventing asus_nb_wmi

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220882

            Bug ID: 220882
           Summary: mfd_aaeon incorrectly binds on ASUS TUF Gaming A16
                    (FA608UM), preventing asus_nb_wmi
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: preeny@gmail.com
        Regression: No

I'm not the greatest with this stuff so I'll be honest, ChatGPT was to the
rescue here.

I am running Faustus and Aurora to control keyboard backlight which worked
perfectly, until setting secureboot for a couple of games on Windows (dual
boot, separate physical drives) I had to create a MOK for Faustus so it would
load correctly.

Let me know if I can be of more help.

------------

Chatty G output:

On ASUS TUF Gaming A16 (board FA608UM), the kernel module mfd_aaeon binds early
and prevents asus_nb_wmi from loading. This causes asusd to fail with
"MissingFunction('asus-nb-wmi not found')" and breaks keyboard backlight
control
and other ASUS WMI features.

Symptoms:
- asus_nb_wmi fails with "No such device"
- asusd fails to start

This occurs regardless of Secure Boot state.
Blacklisting mfd_aaeon restores correct behavior.

Expected behavior:
asus_nb_wmi should bind to the device on this system, or mfd_aaeon should not
bind on this DMI match.

Workaround:
blacklist mfd_aaeon

-------

Hardware:

System manufacturer: ASUS
Product name: TUF Gaming A16
Board name: FA608UM

-------

$ dmesg | grep -E "aaeon|asus_nb_wmi|asus_wmi"
[    3.733678] asus_wmi: ASUS WMI generic driver loaded
[    3.738550] asus_wmi: Initialization: 0x1
[    3.738692] asus_wmi: SFUN value: 0x21
[    3.767492] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
[   13.315905] asus_wmi: Unknown key code 0x4f

--------

$ sudo dmidecode -s system-manufacturer
sudo dmidecode -s system-product-name
sudo dmidecode -s baseboard-product-name
[sudo] password for preen:     
ASUSTeK COMPUTER INC.
ASUS TUF Gaming A16 FA608UM_FA608UM
FA608UM

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 220882] mfd_aaeon incorrectly binds on ASUS TUF Gaming A16 (FA608UM), preventing asus_nb_wmi

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220882

Armin Wolf (W_Armin@gmx.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |W_Armin@gmx.de

--- Comment #1 from Armin Wolf (W_Armin@gmx.de) ---
AFAIK the mfd_aaeon kernel module is out-of-tree, meaning that you have to talk
to your distribution regarding this issue.

Maybe you can also tell them that there exists a upstream driver called
upboard-fpga that should handle the pinctrl and LEDs, and that the other
features should be implemented inside the asus_wmi driver itself.

Thanks,
Armin Wolf

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.